[00:12] <popey> mariogrip, does bluetooth work on ubp-5.1.1 on OPO?
[00:13] <mariogrip> popey: Not yet, haven't looked at it.
[04:55] <extraymond> Hi! Does nexus 7(2013version) support gps? I can't use here map on it.
[04:56] <extraymond> I'm on rc-proposed/bq-aquaris-en channel
[07:13] <lotuspsychje> anyone up to work @ canonical homebased worldwide?
[07:13] <lotuspsychje> https://ldd.tbe.taleo.net/ldd03/ats/careers/requisition.jsp?org=CANONICAL&cws=1&rid=1066
[07:17] <lotuspsychje> and another one
[07:18] <lotuspsychje> https://ldd.tbe.taleo.net/ldd03/ats/careers/requisition.jsp?org=CANONICAL&cws=1&rid=1017
[07:22] <lpotter> I would, but I just got a job...
[07:22] <lotuspsychje> lpotter: nice one, congrats
[07:34] <lpotter> :D thanks
[07:49] <dholbach> good morning
[08:45] <yahn> popey, I just saw your post on g+ about running UT on the OnePlus One. Were you able to do that using the info from https://wiki.ubports.com/w/OnePlus_One ?
[08:56] <yahn> mariogrip, are you around?
[09:03] <popey> yahn, yes and no, I also needed the boot.img and recovery.img out of one of the tarballs on that page, and manually installed those via fastboot
[09:03] <popey> yahn, log from this irc channel a couple of days ago will have the conversation between me and mariogrip
[09:03] <yahn> popey, thanks :)
[09:04] <popey> yahn, http://irclogs.ubuntu.com/2016/01/04/%23ubuntu-touch.html#t10:34
[09:04] <yahn> popey, much appreciated
[09:20] <yahn> popey, do you happen to have a link that works to that boot.img mariogrip asked you to use? The link in the irc log doesn't appear to work.
[09:20] <yahn> the device_bacon.tar.xz file
[09:25] <yahn> popey, nevermind, I've got it now.
[09:32] <Sleep_Walker> hi
[09:34] <Sleep_Walker> I have problem connecting my Android tablet to WiFi hotspot provided by ubuntu touch phone (Aquaris E4.5 Ubuntu), notebook connects to my phone without problem and tablet works perfectly for any other network
[09:34] <Sleep_Walker> is that known problem?
[10:00] <yahn> It lives! Ubuntu on my OnePlus One
[10:00] <yahn> and it looks gorgeous
[10:15] <yahn> OK I'm seeing how this whole scopes thing works now...it's a very cool idea
[11:17] <wligtenberg> My Sony BT keyboard keeps disconnecting, it connects for a while, but I have not yet been able to actually type anything with it. (Which is a bummer, since I wanted to test the convergence stuff)
[12:33] <ondra> mterry why do you want to build art?
[12:33] <ondra> mterry otherwise art is supported for all
[12:34] <ondra> mterry once you run $ .  build/core/envsetup.sh
[12:34] <ondra> mterry call $ lunch
[12:34] <ondra> mterry and select for what you want to build
[12:34] <ondra> mterry then you can compile what you need
[12:38] <mariogrip> yahn: I'm here now
[13:09] <yahn> mariogrip, it's OK I managed to get UT installed on my OnePlus One
[13:09] <yahn> thanks for the work you've put into it
[13:11] <mariogrip> :)
[13:24] <mterry> ondra, hello!  I didn't want to build art especially, but when I run make or make recoveryimage, that art makefile gets used somehow
[13:27] <mcphail> wligtenberg: out of interest, does your keyboard work properly on the rc-proposed channel?
[13:28] <wligtenberg> mcphail: I haven't tried. I will see if I can change channels later today (using a Nexus4 by the way)
[13:28] <mcphail> wligtenberg: I think rc-proposed has bluez5. I was wondering if that would magically fix it
[13:29] <wligtenberg> mcphail: I will look into switching channels
[13:32] <wligtenberg> nexus4 is mako, right?
[13:33] <wligtenberg> yep
[13:33] <ondra> mterry it loads all makefiles for whole aosp project
[13:33] <ondra> mterry but make sure you run lunch first
[13:34] <mterry> ondra, I did
[13:34] <mterry> ondra, and I'm running this all on my normal dev laptop right?
[13:34] <ondra> mterry and this is AOSP or phablet?
[13:35] <mterry> ondra, uh...  I did "repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git"
[13:35] <ondra> mterry ok for what device is this?
[13:35] <wligtenberg> mcphail: switching channels as we speak :)
[13:35] <mterry> ondra, armhf (krillin I guess is my testing device)
[13:36] <ondra> mterry you need to choose right branch. this will probably sync something undefined
[13:36] <ondra> mterry OK for krilin you need to sync different code
[13:36] <ondra> mterry that tree is for AOSP devices like Nexus 4, 7,...
[13:37] <mterry> ondra, well sure.  I have a nexus 4 I can use
[13:37] <mterry> ondra, to keep it simple, I'll stay on this branch and use nexus 4
[13:38] <ondra> mterry OK then run $ repo init -b phablet-4.4.2_r1
[13:38] <ondra> mterry then repo sync
[13:38] <wligtenberg> just curious, are you guys trying to get an Android Run Time working on Ubuntu, or what?
[13:39] <mterry> ondra, what if I've already done a sync?  is that fine to switch or do I need to reset?
[13:41] <mterry> wligtenberg, me?  no, just the Android low level stuff that we use for Ubuntu Touch (drivers and such)
[13:43] <wligtenberg> mterry, ok, also cool, but I saw ART flashing by and was thinking what you guys would be doing. :)
[13:44] <mterry> ondra, also... when I'm syncing, I get a lot of "git repository not found" messages.  Thus I have to use -f to get through it all.  Is that expected?
[13:44] <mterry> Maybe that's because I haven't been using the phablet branch
[13:45] <wligtenberg> mcphail: mmm, that is even worse... There BT just switches off...
[13:46] <ondra> mterry yeah just run sync again
[13:46] <ondra>  no harm
[14:02] <mcphail> wligtenberg: :(
[14:07] <wligtenberg> mcphail: shall I switch to the devel channel, to see if that helps?
[14:08] <mcphail> wligtenberg: no - the devel channel isn't for real people like you and me ;)
[14:08] <wligtenberg> mcphail: I ran the devel channel previously as well
[14:08] <wligtenberg> mcphail: It is not my normal device, just for playing with ubuntu
[14:10] <mcphail> wligtenberg: I'm not sure the devel channel actually works, most of the time. The usable improvements come through in rc and rc-proposed
[14:11] <wligtenberg> mcphail: ok, previously it worked most of the time. Sometimes it had bugs like not being able to install apps :)
[14:12] <mcphail> wligtenberg: I think it has be re-purposed since the old "working" days ;)
[14:13] <wligtenberg> mcphail: ok, you convinced me, I will stay out of that channel :)
[14:14] <mcphail> wligtenberg: I can't rememebr who looks after bluetooth (? is it awe_ ?), but I'm sure they would be interested in bug reports for your keyboard
[14:15] <awe_> mcphail, I'm not really the maintainer, but do work on BT
[14:15] <awe_> we're about to land Bluez5 in OTA9 ( which is already in rc-proposed )
[14:16] <awe_> if things don't work, then yes, a bug report would be super helpful
[14:16] <mcphail> awe_: good guess then :) ! wligtenberg has a bt keyboard which drops connection in OTA8.5 but doesn't work at all in rc-proposed
[14:16] <wligtenberg> awe_ on my nexus4 rc-proposed, bt just switches off
[14:16] <awe_> although any fixes will probably be deferred to OTA10
[14:16] <awe_> wligtenberg, randomly?
[14:17] <wligtenberg> awe_ I don't mind, not my daily driver :)
[14:17] <wligtenberg> awe_ yes, just after some time, it disables bt again
[14:18] <wligtenberg> awe_ I am looking at the bt bugs, to see if this has already been reported
[14:18] <awe_> k
[14:18] <awe_> https://wiki.ubuntu.com/DebuggingBluetooth
[14:18] <awe_> if you do report a bug, please read the above first, so you can provide us with the best info
[14:18] <wligtenberg> According to the link in the topic, I should be looking here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bugs
[14:19] <awe_> yes
[14:19] <wligtenberg> ok
[14:19] <awe_> wligtenberg, does this appear to be a regression?
[14:19] <awe_> ie. does this appear to be new behavior that's shown up recently?
[14:20] <wligtenberg> awe_, yes, this was not happening before. Previously I was able to turn it on (and it would stay on) and I would be able to connect to my Sony BT keyboard, but then I was unable to use the keyboard.
[14:20] <awe_> we updated the kernels for all of our devices first, with the BT stack backported
[14:20] <awe_> then in after OTA8, we released the bluez5 userspace to rc-proposed
[14:20] <awe_> so that it would land for OTA9
[14:20] <wligtenberg> awe_, I was using OTA 8.5, with the previous results, with ubuntu-touch/rc-proposed/ubuntu I have the issue that BT turns itself off
[14:22] <awe_> ok, just to be clear.  With OTA8.5, no problem, but with latest rc-proposed, the problem occurs?
[14:23] <awe_> we knew that there'd be some pain updating to bluez5, but it was something we had to do, as bluez4 was ancient, and unsupported
[14:23] <wligtenberg> awe_, to be precise, with OTA 8.5 (another problem), but the automatically switching off bt, is a problem introduced when switching from OTA 8.5 to rc-proposed.
[14:23] <awe_> got it
[14:23] <awe_> so please file a bug
[14:24] <awe_> and then ping me with the bug #
[14:24] <wligtenberg> yeah, I am looking if it is already reported, too many BT not working reports...
[14:24] <awe_> as I'd like to ensure that we tag it with "bluez5", so it gets a higer priority
[14:25] <awe_> wligtenberg, yea... the bug list is a bit out of control.  Don't spend too much time on looking for a dup
[14:25] <awe_> we'll tag your bug which will make it easier to track
[14:25] <wligtenberg> ok, I will browse for a bit
[14:26] <pmcgowan> wligtenberg, that sounds specific to n4 perhaps
[14:26] <pmcgowan> although I think it works here, let me see
[14:26] <awe_> pmcgowan, bluez5
[14:26] <wligtenberg> pmcgowan, that could be specific, I don't know :)
[14:26] <awe_> ie. it works with new kernel + bluez4
[14:26] <awe_> but not with new kernel + bluez5
[14:26] <pmcgowan> yeah but I have had proposed working for some time, let me check
[14:27] <awe_> wligtenberg, so also to be clear... at some point, your keyboard stops working, and when you check the BT indicator, it's moved to "off"?
[14:27] <awe_> on it's own?
[14:27] <awe_> when this happens, has the screen gone off at all
[14:28] <awe_> just wondering if the device may have suspended
[14:28] <wligtenberg> awe_, Currently, it never discovers the keyboard
[14:28] <awe_> with rc-proposed?
[14:28] <wligtenberg> awe_, yep
[14:28] <awe_> ok, sounds like another bug
[14:28] <awe_> what device are using then, to notice that BT has been disabled?
[14:29] <wligtenberg> I am looking at the Bluetooth settings menu
[14:29] <wligtenberg> hit the button, get green checkmark, after a while it switches to grey again
[14:30] <awe_> ah... so it sounds like BT is never being "enabled"
[14:30] <awe_> when you flip the toggle
[14:30] <awe_> how long is "after a while"
[14:30] <awe_> ?
[14:30] <wligtenberg> awe_, that could indeed also be the case, but then it takes a while to realize that it is off
[14:30] <awe_> right, but can you pair any other BT device after you flip the toggle?
[14:31] <wligtenberg> awe_, 30s
[14:31] <awe_> got it, so yea.. it sounds like enabling BT is failing
[14:31] <awe_> which is why you can't pair your kybd
[14:31] <wligtenberg> awe_, I have not tried anything else, I could try to find my old jawbone...
[14:32] <awe_> well... if you flip the toggle, and it flips back after 30s
[14:32] <awe_> then I doubt that'll work
[14:32] <awe_> I'll flash my N4 and try from my end
[14:32] <wligtenberg> awe_, I agree :)
[14:33] <wligtenberg> awe_, If I run bluetoothctl on the device and enter show, it says no default controller available
[14:33] <pmcgowan> awe_, there is a similar report for flo, did we not update those kernels?
[14:34] <awe_> pmcgowan, no; asked morphis about this yesterday and the kernel for flo was updated when we updated the mako kernel
[14:34] <pmcgowan> ok
[14:35] <awe_> pmcgowan, and it's not the kernel
[14:35] <awe_> this broke when bluez5 userspace was released to the PPA
[14:35] <awe_> probablty related to rfkill
[14:35] <morphis> wligtenberg: can you share your syslog? that would help to get a better picture
[14:36] <awe_> morphis, I've asked him to file a bug and pointed him at the wiki page already
[14:36] <awe_> morphis, I'm flashing my N4 now too
[14:36] <morphis> good
[14:36] <awe_> pmcgowan, here's our current list of bluez5 related bugs: https://bugs.launchpad.net/ubuntu/+source/bluez/+bugs?field.tag=bluez5
[14:36] <mcphail> awe_: as an aside, are you interested in tagging historic bugs (such as #1435040) as bluez5 if they are still present in rc-proposed?
[14:37] <awe_> mcphail, 'bluez5' is for bugs related to bluez5
[14:37] <mcphail> awe_: so only for regressions from bluez4, rather than things which bluez5 didn't fix?
[14:38] <awe_> anything else should just have a 'Canonical System Image' task, and it'll be prioritized by the product team
[14:38] <awe_> mcphail, ack
[14:38] <mcphail> OK
[14:38] <wligtenberg> morphis, sure
[14:38] <morphis> wligtenberg: as when the ctrl isn't available there is really something wrong
[14:38] <mterry> ondra, so far no "git repository can't be found" messages with the phablet branch!  :)  Hopefully it will build well too then
[14:46] <wligtenberg> awe_ morphis: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1531515
[14:46] <wligtenberg> morphis, syslog is attached there
[14:46] <awe_> wligtenberg, thanks!
[14:46] <morphis> wligtenberg: thanks
[14:48] <wligtenberg> awe_, morphis: You guys thanks, I would love to use an Ubuntu phone as a daily driver AND use it for "normal" computing, that would seriously kick but :)
[14:48] <wligtenberg> awe_, morphis: and if my bug report can be improved, let me know
[14:48] <morphis> wligtenberg: :-D
[14:49] <wligtenberg> seriously, I backed the Ubuntu Edge campaign...
[14:49] <wligtenberg> that would have been such an awesome device...
[14:49] <awe_> indeed, but manufacturing a device is a super expensive proposition
[14:49] <BOHverkill> +1
[14:50] <wligtenberg> awe_ I know, it is just such a pity that it didn't go through
[14:50] <wligtenberg> hardware, is hard
[14:50] <awe_> we're still working like crazy on convergence.... but will have to wait for an OEM to step to the plate and spec the right hw
[14:50] <awe_> lmao
[14:50] <awe_> uh yea, you are correct sir
[14:50] <awe_> ;D
[14:52] <wligtenberg> awe_, yeah, you want some decent specs then, which would be rather ridiculous for a normal phone. But I can totally picture using a phone as a computer while plugged in, it would also ease all the syncing issues you have when using multiple devices.
[14:53] <wligtenberg> awe_, but to also be able to test the convergence stuff, I bought an hdmi cable for my nexus4, it works fine, but no keyboard (or mouse) to test it with, yet...
[14:53] <awe_> wligtenberg, fyi... I just did a fresh flash of my nexus4 and BT works fine for me
[14:53] <wligtenberg> awe_ mmm
[14:53] <awe_> have you done any other modifications to your nexus4?
[14:54] <wligtenberg> nope, just flashed ubuntu
[14:54] <awe_> ie. is it still read-only filesystem?
[14:54] <wligtenberg> I have put it in devel mode, that is all
[14:54] <awe_> can you add your system-image details to the bug?
[14:54] <wligtenberg> sure
[14:54] <awe_> eg. system-image-cli -i
[14:54] <wligtenberg> rebooting it now, just to be sure
[14:55] <wligtenberg> you never know when a reboot helps ;)
[14:55] <wligtenberg> (although it isn't windows)
[14:56] <wligtenberg> ok, that seems to have helped...
[14:56] <awe_> wligtenberg, there may be a race condition; I'll try a couple of reboots on my end to see if I can reproduce
[14:56] <wligtenberg> it was now turned on after boot, and I turned it off and on again now for testing
[14:58] <wligtenberg> bluetoothctl, now show info
[14:58] <wligtenberg> so it seems on this boot, bt works
[14:59] <awe_> wligtenberg, do you have a valid SIM in the phone?
[14:59] <wligtenberg> awe, nope
[14:59] <awe_> ok
[14:59] <awe_> just wanted to be sure we have a similar setup
[15:02] <wligtenberg> awe_, I have now paired my keyboard
[15:03] <wligtenberg> awe_, and it works! (so that is progress from OTA 8.5!)
[15:05] <awe_> wligtenberg, I haven't been able to reproduce yet
[15:05] <awe_> I'll reboot a few more times, then will probably mark the bug as Incomplete
[15:06] <wligtenberg> awe_, sure, it might have been a fluke
[15:06] <awe_> can you update the bug and indicate that a reboot seems to have fixed the problem?
[15:06] <wligtenberg> awe_, already done that :D
[15:06] <awe_> cool, much thanks for the help!
[15:06] <wligtenberg> Just tested the hdmi as well, but that is now not changing the screen as well as before. (It now stays phone shaped)
[15:07] <wligtenberg> awe_ you are most welcome. The more people testing it, the better it will become.
[15:07] <awe_> indeed
[15:08] <wligtenberg> No I just need a BT mouse :)
[15:08] <wligtenberg> and then show off at some local OSS/Linux gig
[15:09]  * mcphail loves this channel
[15:09] <wligtenberg> awe_, just curious, are you working for Canonical?
[15:10] <ondra> mterry when you synced master, that manifest is something old form 4.0 days, so god knows what you were building :)
[15:10] <ondra> mterry you need to run full build first ($ make) then you can iterate through only portions of the build e.g. $ make recoveryimage
[15:10] <mterry> ondra, I've added the -b argument needed to the Touch/Gerrit wiki, so hopefully future poor souls don't make the same mistake
[15:11] <mterry> ondra, oh yeah?  OK, I had started with just recoveryimage and hit a build failure was about to look
[15:11] <mterry> Will go back and do full make
[15:11] <ondra> mterry yeah, I thought it was always there since 4.4.2 port
[15:11] <mterry> Also seems I need g++-4.8
[15:11] <ondra> mterry I'd expect make recoveryimage to fail in clean build env
[15:12] <ondra> mterry yeah, we need same dependencies as aosp
[15:12] <ondra> mterry I have android 5.1.1 tree running well
[15:12] <ondra> mterry but recovery is only missing part in that tree
[15:20] <awe_> wligtenberg, yex
[15:20] <wligtenberg> awe_, lucky you :)
[15:22] <awe_> wligtenberg, thanks
[15:22] <wligtenberg> awe_, yeah I think Canonical is a nice place to work. Pretty cool, if you can work on Ubuntu for work.
[15:23] <wligtenberg> awe_, I always have to squeeze in my OSS work
[15:30] <RTE89> hi there. Is there a way to use Mega on an Ubuntu phone? The site insists that I download the Android app, and there's no alternative in the store.
[15:30] <dobey> what is Mega?
[15:33] <mterry> tedg, any progress on that ubuntu-app-launch protocol redesign?
[15:33] <ogra_> dobey, the successor of Super and predecessor of Hyper :P
[15:34] <tedg> mterry: Yes, still need a final review by tvoss, he's promised today though :-)
[15:34] <mterry> tedg, cool
[15:34] <mterry> tedg, I'll stop bugging you about it and let you ping me when you're ready  ;)
[15:35] <dobey> ogra_: i think Megalodon was the last one. Never was a Hyperladon
[15:35] <ogra_> just wait ...
[15:37] <ogra_> dobey, it is a file sharing service from a german guy who was in jail multiple times in germany for data theft and credit card data abuse ...
[15:37] <dobey> oh that mega
[15:37] <ogra_> (i never got how people could ever trust his services with his data ...)
[15:37] <dobey> yeah
[15:38] <dobey> or why people treat him like a savior
[15:38] <ogra_> s/his/their/
[15:38] <dobey> well, it's his data now ;)
[15:38] <ogra_> haha, yeah
[15:39] <ogra_> anyway, i'd expect them to offer some html based access even without app ... but RTE89 is gone ...
[15:39] <dobey> yeah
[15:40] <dobey> ogra_: they probably have a crappy web site that just says to install the android app, because our browser has "Android" in the user-agent
[15:40] <dobey> so might need a custom webapp to tweak the user-agent, to be able to use that
[15:41] <dobey> on the other hand, file sync services don't really fit well with the security and filesystem model of the ubuntu phone, either
[15:43] <ogra_> yeah
[15:44] <dobey> i'm glad i don't have to deal with making ubuntu one file sync work on the phone :)
[16:35] <peat-psuwit> mariogrip: Does your system-image server contain this patch? http://bazaar.launchpad.net/~ubuntu-system-image/ubuntu-system-image/server/revision/283
[16:37] <mariogrip> peat-psuwit: no, not at the moment
[16:40] <mariogrip> peat-psuwit: I can update it now
[16:42] <peat-psuwit> mariogrip: Thank you. Incremental update won't happen if the patch isn't there.
[16:44] <mariogrip> oh wait, i added that change myself some time ago
[16:45] <peat-psuwit> mariogrip: Ok.
[16:45] <mariogrip> but this patch has more fixes so ill add it anyway
[16:49] <peat-psuwit> sil2100: According to your latest change in system-image server, how can one force regeneration of keyring file without actually changing the keyring tarball itself?
[16:51] <mariogrip> peat-psuwit: Now it's up to date
[16:53] <peat-psuwit> mariogrip: I'm afraid that's not enough. After studying the code, the keyring file won't be re-generated without changing the actual keyring tarball.
[16:58] <mariogrip> peat-psuwit: I can fore it to do it, i can remove the "if it exist"
[16:59] <peat-psuwit> mariogrip: In code? I think it won't work. The file will always be regenerated.
[17:00] <peat-psuwit> mariogrip: Maybe just delete the file instead?
[17:13] <popey> mariogrip, does that mean I'll get an OTA update on my OPO at some point soon? :)
[17:15] <mariogrip> peat-psuwit: Fixed now, now the keyring is correct
[17:15] <mariogrip> popey: Jup :)
[17:15] <mariogrip> popey: what channel are u on?
[17:15] <popey> good question
[17:16] <peat-psuwit> mariogrip: Thank you very much.
[17:17] <mariogrip> peat-psuwit: np :)
[17:18] <mariogrip> popey: the command I told u the other day was for stable
[17:18] <popey> mariogrip, channel: ubuntu-touch/stable
[17:18] <peat-psuwit> popey: I think you'll need to flash your OPO with ubuntu-device-flash to flash your device with new keyring file, then OTA should works immediately.
[17:19] <mariogrip> there haven't been any new stable release yet btw
[17:19] <popey> ok
[17:20] <mariogrip> the stable channel follows the stable channel on system-image.ubuntu.com
[18:12] <mterry> ondra, just a follow-up, after installing some packages and fixing a compile error, everything built fine.  And I seem to be able to build / install the recovery image just fine.  Thanks for your help!
[18:13] <mterry> I left notes on the steps needed to go from zero to build on the Touch/Gerrit wiki
[18:26] <Craig> Can someone direct me to where I can post ideas and suggestions for Ubuntu Touch developers?
[18:27]  * ogra_ guesses the mailing list would be a good start
[18:29] <dobey> s/Touch//
[18:29] <dobey> file bugs too i guess
[18:29] <ogra_> right, wishlist bugs are a good way too
[18:30] <Craig> A mailing list? That's to receive newsletters from them, right? But where can I post ideas and suggestions to the developers?
[18:30] <ogra_> a mailing list is to discuss matters by email
[18:31] <ogra_> https://lists.launchpad.net/ubuntu-phone/
[18:32] <Craig> Thank you. I'll check that out.
[18:33] <ogra_> you can join it here https://launchpad.net/~ubuntu-phone
[18:42] <ahayzen> Hi, has auto brightness become really unstable recently for anyone else?
[18:43] <ahayzen> and how can i find out why it isn't currently working?
[18:45] <Lamprophony> hello, I wanna know how to do a webapp for ubuntu touch
[18:48] <ondra> mterry cool :)
[18:49] <dobey> Lamprophony: #ubuntu-app-devel is probably the better channel :)
[18:51] <Lamprophony> Thnx
[19:03] <Craig> ahayzen, I'm using Nexus 7 and it took me a while to notice my thumb was at times covering the light sensor and changing the screen brightness.
[19:33] <n1cky> my scrollback buffer isn't big enough to read if anyone had anything to say about building on 5.x sources
[19:33] <n1cky> I'm still interested in building touch for a nexus 6, shamu
[19:34] <n1cky> is there a ml thread or anywhere else where i can read about building on newer sources?
[19:34] <dobey> there's been some work on building on 5.x source, but not sure how far along it is
[19:34] <dobey> ondra: ^^ any idea on that?
[19:35] <n1cky> dobey: are you @ canonical?
[19:35] <pmcgowan> its quite far along but not done or ready to release
[19:36] <dobey> yes
[19:36] <dobey> in so much as one whom telecommutes is "at" a place of employ :P
[19:37] <n1cky> pmcgowan: I don't mind if i hit some bugs, but does not ready to release necessarily mean internal?
[19:37] <n1cky> poor phrasing; what i mean to ask is if that prerelease work is public or not
[19:37] <n1cky> dobey: thats a nice gig.
[19:38] <pmcgowan> n1cky, good question I will find out if its available, I don't now myself off hand
[19:41] <dobey> yep
[19:42] <dobey> afaik it's all public, just not widely announced since it's not working fully yet
[19:42] <dobey> i think there's maybe still some issues with libhybris and such?
[19:42] <pmcgowan> there is work for 64 bit support at the same time
[19:42] <pmcgowan> which definitely has hybris implications
[19:45] <dobey> and that, yeah
[19:46] <dobey> n1cky: really though, for a 32-bit phone, if you can get the necessary requirements for ubuntu to work properly, enabled in the kernel, then i think building it should be pretty much fine
[19:46] <dobey> n1cky: that is, making sure the stuff the 4.x build enables, is also built in the 5.x source