[02:10] <ajbrandt1> good evening
[02:32] <ajbrandt1> Anyone have info on music playing in background?
[03:20] <slangasek> popey: fwiw, the QT_QPA_PLATFORM setting traces back to /etc/profile.d/qpa_plugin.sh, which sets either QT_QPA_PLATFORM=ubuntumirclient or QT_QPA_PLATFORM=ubuntu, depending on whether MIR_SOCKET is set in the environment... which it obviously won't be when connecting over adb.  So that seems to be a regression in ubuntu-touch-session.
[03:22] <slangasek> ogra_: ^^ ubuntu-touch-session 0.88 breaks at least some autopilot use cases over adb; how was this tested before upload?
[03:22] <slangasek> ogra_: i.e., nothing sets $MIR_SOCKET, so the shell environment gets set up wrong over adb
[05:07] <lotuspsychje> http://www.omgubuntu.co.uk/2014/01/several-ubuntu-phones-release-2014
[05:07] <lotuspsychje> lets hope they come fast
[06:12] <dazoe> so, nexus 7 (2012), i installed touch on it using the manual instructions on https://wiki.ubuntu.com/Touch/Install and it boots past google logo but sits on a black screen
[06:12] <dazoe> how far back should i go to find one that works
[06:12] <dazoe> ?
[09:12] <nocomp> hi folks
[09:12] <nocomp> i try to get the source on my box
[09:12] <nocomp> for dev a rom
[09:12] <nocomp> i am having prob with the repo sync
[09:12] <nocomp> when i run
[09:12] <nocomp> phablet-dev-bootstrap code/
[09:13] <nocomp> it stopp
[09:13] <nocomp> i gonna dig
[09:20] <nocomp> solved
[09:20] <nocomp> just been stupid
[09:39] <ogra_> slangasek, yes, on all devices with SF and Mir i wonder why they worked then (the landing took 8 weeks for this, but i dont think that specific part of autopilot tests changes within) ... thanks for the upload
[09:40] <ogra_> *changed
[10:36] <nocomp> hi folks
[10:36] <nocomp> i try to compile a rom for i9300
[10:36] <nocomp> galaxy s3
[10:36] <nocomp> any idea why this is not working?
[10:36] <nocomp> nocomp@pirebox:~/ubuntutouch$ breakfast i9300
[10:36] <nocomp> Couldn't locate the top of the tree.  Try setting TOP.
[10:36] <nocomp> bash: build/tools/roomservice.py: No such file or directory
[10:36] <nocomp> ** Don't have a product spec for: 'cm_i9300'
[10:36] <nocomp> ** Do you have the right repo manifest?
[10:36] <nocomp> nocomp@pirebox:~/ubuntutouch$
[10:38] <srujan> http://www.omgubuntu.co.uk/2014/01/how-to-dual-boot-android-ubuntu-touch-on-nexus
[10:39] <srujan> i tired to install ubuntu dual boot on my nexus 4 using the above tut
[10:39] <srujan> but call and wifi functionality are not working
[10:40] <popey> srujan: did it have android 4.4 on it?
[10:40] <srujan> yes
[10:41] <popey> i believe that may be why
[10:41] <popey> https://wiki.ubuntu.com/Touch/DualBootInstallation#Getting_phone_calls_to_work_in_Ubuntu_and_Android_4.4
[10:43] <srujan> Thanks popey
[10:51] <popey> srujan: np
[12:07] <FuLgOrE> hi guys. How is the status about 4.4 rebase?
[12:08] <FuLgOrE> Is it possible to see the status somewhere?
[12:15] <popey> FuLgOrE: i believe it's due to land at the end of the month
[12:58] <FuLgOrE> popey: thank you
[12:59] <FuLgOrE> popey: Is it possible to monitor the status somewhere? I don't want to bother you with my questions
[13:06] <vthompson> all, I'm having issues upgrading click 0.4.12 from the ubuntu-sdk-team ppa. Could anyone help me? http://paste.ubuntu.com/6779871/
[13:31] <popey> vthompson: lemme see if i can reproduce that here
[13:31] <popey> FuLgOrE: i dont know. but the target is end of month, keep an eye on the ubuntu-phone list as we're sending out weekly status updates for various things there
[13:33] <popey> vthompson: oddly I already had that version of click from somewhere
[13:33] <popey> http://paste.ubuntu.com/6779992/
[13:36] <joeashin> is there a release for nexus 5?
[13:37] <popey> joeashin: not yet
[13:37] <joeashin> thx.
[13:43] <shiggitay> ...
[13:51] <vthompson> I resolved my issue by adding a new user "phablet" on my desktop.
[13:53] <popey> oof
[13:53] <popey> thats a bug imo
[13:55] <vthompson> I'll go and file one. I only recently added the ubuntu-sdk-team ppa to my system
[14:04] <sergiusens> popey, https://code.launchpad.net/~sergiusens/reminders-app/cmake_common/+merge/202215
[14:04] <sergiusens> popey, I see you are around ;-)
[14:05] <sergiusens> I was aiming on directly creating a fat package, but it seems to be missing some pieces still
[14:42] <popey> sergiusens: thanks
[14:45] <popey> sergiusens: do i click-buddy it directly on the device or will it work on laptop?
[14:51] <sergiusens> popey, will work on laptop, but will build x86
[14:51] <sergiusens> popey, still need to integrate it with click chroot
[14:51] <sergiusens> popey, although, if you have a working click chroot; doing click chroot click-buddy ... should work ;-)
[14:54] <popey> so probably easier to build on device right?
[14:54] <popey> (I don't have a chroot, and want to test on arm, not x86)
[14:54] <sergiusens> yup
[14:55] <popey> ta
[14:55] <popey> will do a bit later
[15:26] <vthompson> I've been really good at breaking things today. I upgraded my phone to r136 and now it won't boot up with a welcome screen, but I can still "adb shell" to the device. Anyone having similar issues?
[15:35] <popey> vthompson: mine is on #134, will update now and see what happens
[15:36] <vthompson> popey, god speed
[15:36] <popey> hah
[15:36]  * popey voluntarily breaks his phone... for the greater good
[15:40] <popey> vthompson: mine boots to desktop okay
[15:40] <vthompson> popey, hm, maybe I'll reflash
[15:52] <vthompson> popey, reflash worked. I must have been low on battery while upgrading... or some other hiccup
[18:37] <ybon> Getting on first install on Nexus4: "ERROR:phablet-flash:Installation is taking too long or an error occured along the way" (command was "phablet-flash ubuntu-system --channel devel --no-backup") Should I just try again? Thanks :)
[18:39] <ybon> Ah, maybe with --pending
[18:40] <ybon> ah, no
[18:41] <ybon> "phablet-flash: error: unrecognized arguments: --pending" seems this option doesn't exist anymore
[18:44] <cwayne_> ybon, hm, try with -b instead of --no-backup
[18:45] <ybon> cwayne_: thanks :)
[18:46] <ybon> cwayne_: I've clicked on "get back" on the device
[18:46] <ybon> which has now rebooted
[18:46] <cwayne_> ybon, np! hope it helps :)
[18:46] <ybon> and it seems on Ubuntu \o/
[18:50] <cwayne_> woo!
[18:51] <ybon> Trying to connect on the cellular network now :)
[19:01] <ybon> Humm, no cellular connection (even after unlocking the SIM card) and no wifi connection, should I try installing "stable" instead of "devel"?
[19:12] <cwayne_> plars, huh, any idea whats going on? there were a bunch of builds and they're all failing pretty hard
[19:12] <cwayne_> thomi, ping
[19:13] <thomi> cwayne_: hey
[19:14] <cwayne_> thomi, hey, im getting a lot of failures, seems to be something with autopilot introspecting failing to load platform plugin 'ubuntu'
[19:14] <thomi> hmm, got a link?
[19:15] <cwayne_> http://ci.ubuntu.com/smokeng/trusty/touch_custom/mako/134:20140118:20140115.1/6136/ubuntu-ui-toolkit-autopilot/680527/
[19:15]  * thomi reads
[19:16] <thomi> cwayne_: autopilot hasn't changed in a while now. This looks to me like the process we try and launch exits with -6
[19:16] <thomi> probably due to the missing 'ubuntu' platform
[19:16] <thomi> I imagine that platform is provided by the qtubuntu package?
[19:16] <thomi> but I'm just guessing there
[19:16] <cwayne_> looks like there's a lot of issues with the regular touch test cases too
[19:16] <cwayne_> like 0 passes on mako
[19:16] <cwayne_> something is incredibly broken
[19:17] <thomi> ? where do you see that?
[19:17] <thomi> I see 90% pass rate for mako...
[19:18] <thomi> except for this: http://ci.ubuntu.com/smokeng/trusty/touch/mako/20140119%20%3F/6152/ where nothing ran
[19:18] <thomi> so... nothing failed either :)
[19:18] <cwayne_> well, that's still incredibly broken :)
[19:19] <cwayne_> http://ci.ubuntu.com/smokeng/trusty/touch/
[19:19] <thomi> agreed, but there's nothing there for me to look at :)
[19:20] <cwayne_> fair enough :)
[19:20] <thomi> on this run, for example: http://ci.ubuntu.com/smokeng/trusty/touch/mako/20140119%20%3F/6152/ all the console logs are totally empty
[19:50] <jose> hey guys, I cannot sync contacts between syncevolution and google contacts, external transport failure (local, status 20043) is what I get
[19:50] <jose> any ideas?
[20:20] <kflx-mako> hi all, I'm trying to install Ubuntu os on my nexus 4. but i don't know which mako files to download. and can i use cwm to install?
[20:52] <ulkesh> Any word yet on when a build of Ubuntu Touch will be available for the Nexus 7 (2013)?
[20:55] <plars> cwayne: you are talking about the latest mako failure on image 136 I guess?
[20:56] <plars> cwayne: looks like we had a device fall over - I'll swap it out in the configs, and rfowler will need to take a look when he's back in the office again
[20:57] <plars> cwayne: or are you talking about the custom builds? the latest seems a lot beter on those, but the two previous images were pretty bad it seems - nothing changed on the ci side with those
[20:58] <vthompson> balloons, or anyone following the Terminal app's Backspace/Enter bug. I entered a comment with some steps I was able to do to get the app to recognize the keys. The bug is probably an OSK issue and the Konsole plugin author can probably stand down on investigating.
[21:13] <ulkesh> Any word yet on when a build of Ubuntu Touch will be available for the Nexus 7 (2013, called razor I believe)?
[21:15] <sergiusens> popey, yay :-)
[21:16] <popey> sergiusens: thank you
[21:16] <popey> vthompson: thank you
[21:16] <popey> ulkesh: end of the month, hopefully
[21:16] <ulkesh> popey: awesome, thanks a bunch!
[21:17] <sergiusens> popey, we don't really have the infra to build on jenkins yet; but I can build local and upload and discuss the rest with fginther tomorrow
[21:18] <sergiusens> eom -/+ 1 week
[21:20] <popey> great, thanks
[21:23] <sergiusens> popey, if you have the cycles, care to take a stance onto that click-buddy mr? :-)
[21:26] <popey> sergiusens: done, for what my comment is worth ☻
[21:57] <ybon> Ah, seems that my Android version was too recent (4.4.2_r1), do I need to restore Android, then downgrade, or is there a way to downgrade from desktop command line even when Ubuntu Touch is already installed?
[22:05] <ybon> ah, maybe https://wiki.ubuntu.com/Touch/DualBootInstallation#Android4.4Radio
[23:48] <rulip> hello