[00:09] <awe_> mariogrip, indeed!  looks like progress...
[01:54] <mTeK> How do you try to port a device that is on 5.1, isn't touch based off of 4.4?
[01:55] <Stanley00> mTeK: did you read the porting guide of ubuntu-touch?
[01:56] <mTeK> yes but somewhere I got the Idea that you needed a 4.4 device
[01:57] <Stanley00> mTeK: where did you get that?
[01:58] <mTeK> I don't remember now but I thought that the current touch was based of off 4.4, it's been awhile since I looked into porting it to my device
[02:00] <mTeK> Stanley00:  this must be where i saw it http://www.xda-developers.com/porting-ubuntu-touch-is-as-simple-as-building-cm/
[02:02] <Stanley00> mTeK: I'm so sure with the porting, but in theory, all you need is just the source with all the driver and kernel specific for your phone.
[02:03] <Stanley00> mTeK: I can't find any mention to 4.4 on that page?
[02:03] <mTeK> It says CM 10
[02:03] <mTeK> that's 4.4
[02:04] <mTeK> I guess I should try, I build nighly for CM12 for my device and I have the phablet repo ready, well I need to sync it again. I just need to copy some of the blobs and run it i guess
[02:05] <Stanley00> mTeK: it's from 2013, a lot have changed since there. I think you should stick with the official wiki page since it's safer :3
[02:05] <Stanley00> *since then*
[02:05] <mTeK> Yes I've read that I just must have had this back in the storage part of my brain.
[02:08] <mTeK> Stanley00:  Read setting up your enviroment https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[02:09] <mTeK> its still 4.4.2
[02:10] <Stanley00> mTeK: it's just a reference...
[02:10] <mTeK> No it's not look at the gerrit server, Still at 4.4.2
[02:11] <mTeK> https://code-review.phablet.ubuntu.com/#/q/status:open,n,z
[02:24] <Stanley00> mTeK: hmm... I'm not so sure, you can come back in about 6h, since most developer here is from EU. They can answer you at that time.
[04:53] <jnxd> hello, where do I head to if I find errors in the sites like https://design.ubuntu.com/?
[06:07] <gustav1234x> Hi. Anyone tried Ubuntu Touch on Fairphone 2? https://www.fairphone.com/
[06:10] <gustav1234x> Or FP1 for that matter.
[06:13] <diwic> gustav1234x, is FP2 out yet?
[06:14] <gustav1234x> No. I don’t think so.
[06:16] <diwic> gustav1234x, anyhow, the FP1 does not run Ubuntu Touch AFAIK
[06:16] <diwic> gustav1234x, it's not even listed on https://wiki.ubuntu.com/Touch/Devices
[06:17] <gustav1234x> True. Not sure who gets to edit that page though.
[07:32] <dholbach> good morning
[08:37] <JamesTait> Good morning all; happy Friday, and happy International Day of Non-Violence! 😃
[08:38] <gustav1234x> \o/
[09:05] <tvoss> popey, any thoughts on my proposal for a launchpad project for tracking bugs/feature requests?
[09:13] <mpt> mandel, hi, what URL protocols does the Download Manager allow? The developer.ubuntu.com pages don’t say.
[10:47] <jgdx> mpt, might have better luck asking Elleo or kenvandine.
[10:57] <Elleo> mpt: from a quick glance at the source it looks like it's using QNetworkRequest for transfers which I believe only support HTTP, HTTPS and FTP, although a lot of the code looks like it assumes HTTP/HTTPS, so not certain if FTP works
[11:46] <jnxd> hello, where do I head to if I find errors in the sites like https://design.ubuntu.com/?
[11:48] <svij> jnxd: there is a "Report a bug on this site" on the bottom of the page
[11:50] <jnxd> svij: thanks. don't usually read such things.
[12:26] <mcphail> jnxd: website bugs don't seem to get much love
[12:28] <jnxd> mcphail: well, if it were a wiki, I'd have edited it myself, but this is as far as I can go
[12:29] <mcphail> jnxd: yep
[13:07] <mterry> jibel, your posted logs to bug 1501639 look good.  I assume the bug was fixed in 213?
[13:07] <ubot5`> bug 1501639 in unity8 (Ubuntu) "krillin/devel-proposed fails to boot" [Critical,Fix released] https://launchpad.net/bugs/1501639
[13:12] <jibel> mterry, yes it is fixed. The problem now is different, it is the watchdog rebooting the device because location-service is crashing
[13:12] <jibel> mterry, thanks for the quick fix
[13:14] <mterry> jibel, awesome.  That problem is a different bug, right?  I'll finish off closing 1501639 then
[13:14] <mterry> jibel, (and I didn't even do anything!  it was already fixed when I investigated!  :))
[13:15] <mterry> jibel, oh huh!  I only saw your logs attachment email by LP
[13:15] <mterry> jibel, didn't notice your other comments or wouldn't have asked you  :)
[13:16] <jibel> np
[13:16] <jibel> I reclosed the bug too
[13:16] <mterry> cool
[13:17] <pmcgowan> jibel, hmm, so we decided to leave the system watchdog enabled, but that would result in a boot loop like this one
[13:17] <pmcgowan> for location service crashing
[13:17] <pmcgowan> thats not good
[13:17] <jibel> pmcgowan, indeed, that's not good
[13:17] <pmcgowan> may need to revisit, this is exactly the example I dont want
[13:18] <jibel> pmcgowan, which can the watchdog really fix actually?
[13:18] <pmcgowan> although, will it happen in a released image
[13:18] <pmcgowan> jibel, it can fix an issue where a resource is exhausted after a period of time
[13:18] <pmcgowan> thats about it
[13:18] <jibel> pmcgowan, s/can/case/
[13:19] <pmcgowan> sil2100, ^^
[13:19] <pmcgowan> jibel, tony convinced me not to remove the entire support, just the session version
[13:19] <pmcgowan> but now not so sure
[13:19] <pmcgowan> we cant purposely cause boot loops for non essential services
[13:20] <jibel> pmcgowan, it needs to have some smarts to decide whether or not it's right to reboot
[13:20] <pmcgowan> jibel, indeed, and short of having that nothing is better
[13:20] <pmcgowan> imo
[13:20] <jibel> agreed
[13:20] <pmcgowan> users know to reboot when stuff doesnt work anyway
[13:22] <sil2100> So removal of upstart-watchdog from the seeds then?
[13:22] <pmcgowan> sil2100, I am changing my mind back, we have yet another example, but s it likely in the field is the question
[13:35] <mpt> thanks Elleo
[13:44] <Elleo> mpt: no problem
[13:53] <seb128> dbarth_, hey, libunity-webapps seems to fail to build in wily, is that something for your team? https://launchpadlibrarian.net/219669481/buildlog_ubuntu-wily-i386.libunity-webapps_2.5.0~%2B15.04.20141217.2-0ubuntu1_BUILDING.txt.gz
[13:53] <dbarth_> seb128: yes, let me check
[13:53] <seb128> thanks
[13:55] <dbarth_> seb128: that's the aftermath of the removal of extensions?
[13:55] <seb128> dbarth_, no, I don't think so, probably new glib or toolchain or something exposing a bug
[13:55] <dbarth_> oh ok
[13:55] <dbarth_> alex-abreu: ^^ fyi
[15:03] <umpfqua> hello, sorry in advance if I missed something... I recently loaded ubuntu touch on nexus 4, I used the devel channel according to the table here - https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/ but it seems like other channels (including stable) were updated more recently which doesn't seem right to me
[15:04] <davidcalle> sil2100, ^
[15:06] <davidcalle> umpfqua, in my experience, the action is happening more on rc-proposed these days (new image everyday)
[15:07] <sil2100> umpfqua: hey!
[15:07] <sil2100> umpfqua: the chart says that ubuntu-touch/stable/ubuntu should be used if you want to have a well tested phone
[15:08] <umpfqua> davidcalle: thanks, I'll try that one instead
[15:08] <sil2100> umpfqua: devel doesn't get too much attention... if you want a stable device please use the stable channel, the rc-proposed one can be broken sometimes, so use it on your own risk
[15:09] <sil2100> I think I should remove the 'Track the latest development' rows
[15:09] <umpfqua> sil2100: well, I'm kinda ok trading some stability with latest/greatest developments
[15:10] <sil2100> umpfqua: ok, just remember: rc-proposed images from time to time tend to be broken, for instance we had an issue right now that could make unity8  unbootable
[15:10] <sil2100> On mako
[15:10] <sil2100> We fixed/reverted the issue, but just saying that things like that happen
[15:10] <sil2100> We fix them ASAP but still
[15:10] <umpfqua> sil2100: oh yes, removing that row would have been less confusing
[15:12] <sil2100> Since the closest thing we have to 'track latest development' would be rc-proposed indeed, but since those are high-risk images, not sure if we should recommend those ;)
[15:12] <sil2100> They get QA, but since it's the first place where new things appear, well... it's risky
[15:13] <umpfqua> sil2100: I'm ok with things sometimes breaking (I used to run cyanogenmod nightly before this)
[15:13] <umpfqua> but thanks for the heads up
[15:36] <umpfqua> interesting... couldn't flash through adb, kept saying "device cannot be detected over adb" (but I was seeing it via "adb devices"), so I'm flashing via fastboot just like the first time
[15:50] <umpfqua> anyway, I'm in the latest rc-proposed, thanks for help sil2100 and davidcalle
[15:52] <sil2100> umpfqua: yw :)
[15:53] <davidcalle> umpfqua, np! :)
[15:54]  * tathhu is krilling :o
[15:54] <tathhu> ... no.
[17:16] <dhbiker> what the hell was in the last update for arale on rc.proposed ? :D
[17:16] <dhbiker> feels kinda snappier
[17:19] <tathhu> magic
[17:19] <tathhu> :o
[17:19] <tathhu> please give it back, nip needs it :P
[17:19] <dhbiker> 42megs of magic
[19:40] <BlackJohnny> hi, anyone knows if there is a right way  to create files within an ubuntu scope ? ... i want to cache some images
[19:47] <dobey> BlackJohnny: you can write them into the $XDG_CACHE_HOME directory
[19:47] <BlackJohnny> dobey, thank you for the hit
[19:48] <dobey> you'll have to implement some sort of logic to return file:/// URLs to those cached images, rather than the original URLs in your results, though
[19:48] <dobey> you should also have some cleanup logic, so they don't sit around and waste space forever
[19:59] <JanC> dobey: is $XDG_CACHE_HOME cleaned on reboot?
[20:01] <dobey> no
[20:19] <mhall119> renatu: ping, are you still involved in calendar syncing on the phone?
[20:29] <pmcgowan> mhall119, I dont think syncmonitor should have been removed
[20:29] <pmcgowan> I could be wrong though
[20:30] <mhall119> pmcgowan: I was pinging about something else, actually, Google just informed me that they are going to turn of their XML feeds for calendars, I wanted to make sure we weren't using those feeds for anything in the phone
[20:31] <pmcgowan> mhall119, renatu will know
[20:31] <mhall119> pmcgowan: I guessed, which is why I pinged him :)
[20:31] <nhaines> They're what?  Damn it.
[20:32] <mhall119> nhaines: iCal feeds aren't going to be affected, just XML
[20:32] <kal_cividFajdida> how  i can install whatsapp in ubuntu phone ?
[20:32]  * nhaines checks what he wrote in his book.
[20:32] <popey> kal_cividFajdida: there is no whatsapp for ubuntu phone yet
[20:32] <mhall119> kal_cividFajdida: email WhatsApp and tell them you'd like it if they developed an Ubuntu app
[20:33] <nhaines> Yeah, of course the Lightning plugin uses the XML feed.  *sigh*
[20:33] <mhall119> kal_cividFajdida: unfortunately WhatsApp doesn't have an open API, so nobody is allowed to make an app for except them, so we have to show them that there is enough interested users to justify it
[20:34] <mhall119> nhaines: lightning is still around?
[20:34] <nhaines> Yup.
[20:34] <mhall119> I thought it was abandoned long ago
[20:34] <nhaines> Worked fine in 14.04.
[20:34] <mhall119> maybe I'm thinking of the stand-alone one, Sunbird or something like that/
[20:35] <nhaines> Oh yeah.  I don't think that's stop around but the Thunderbird plugin is.
[20:35] <mhall119> not as of Nov. 18th, if it's using the XML feeds :)
[20:35] <nhaines> I guess not.  :)  Well, that's super annoying.  I guess I'll have to keep an eye on it and figure out what errata I'll need to add to the book.
[20:43] <mterry> awe_, hrm.  My testing this time of silo 23 was decidedly more mixed
[20:43] <mterry> awe_, subjectively it didn't freeze my phone.  But top still shows dbus-daemon taking 90% cpu
[20:43] <mterry> awe_, which might be an improvement on 100% cpu.  Or might be statistical noise
[20:44] <awe_> mterry, there was a definite bug in NM that I fixed
[20:44] <mterry> awe_, yeah no doubt.  Sending duplicate signals is pointless
[20:44] <awe_> running dbus-monitor shows a 2-3x reductions in signals generated when scan completes
[20:44] <awe_> if we're still seeing dbus-daemon pegging the CPU
[20:44] <mterry> awe_, I'm just sad that it doesn't seem to have slain the CPU dragon
[20:44] <awe_> there's more work to do
[20:45] <mterry> awe_, yeah.  Just that the last time I tested this fix it appeared to fix dbus-daemon too.  Must have been a fluke, which got me excited
[20:45] <awe_> mterry, do you have location services on?
[20:45] <mterry> awe_, yess
[20:45] <awe_> and maybe you hadn't before
[20:46] <awe_> when I say on... you've started HERE maps someplace
[20:46] <awe_> if when the HERE location provider starts, it causes NM to scan every 4-5s
[20:46] <awe_> which is overkill in my mind, but I wasn't asked
[20:46] <awe_> anyways, thanks for testing
[20:46] <mterry> awe_, I never open HERE app.  I may not even have it installed
[20:47] <mterry> awe_, and I likely had location data on before too
[20:47] <awe_> ok. then probably not an issue
[20:47] <mterry> awe_, not sure what the delta would be.  ::shrug::
[20:47] <awe_> it's only when the specific here provider starts
[20:47] <awe_> mterry, did you just go walking down central sq this again?
[20:47] <mterry> awe_, well thanks for the fix as is anyway  :)  It might be observation bias, but it appears to not freeze as hard.  Needs a weekend of testing to confirm that
[20:48] <mterry> awe_, yeah
[20:48] <awe_> the big problem with the original bug was lack of a definitive test scenario
[20:48] <awe_> so keep me posted
[20:48] <awe_> and again, as mentioned we might have more work to do on this one
[20:48] <mterry> awe_, central sq is fairly reliable for triggering it.  I usually have to restart my phone after leaving my house because of this bug
[20:48] <awe_> k
[20:48] <awe_> mako or krillin?
[20:48] <mterry> awe_, yeah.  Even with my "+1 great fix" testing before, we were still 30% cpu which seems high  :)
[20:48] <mterry> awe_, mako
[20:49] <dobey> central/kendal are pretty heavy on available wifi points
[20:49] <dobey> harvard too of course
[20:49] <mterry> dobey, yeah, I get like 30 to 50 access points in my list.  a good stress test
[20:49] <awe_> mterry, well... report back what you see over the weekend.  I'm just finishing regression testing on krillin, and need to move to arale next
[20:50] <mterry> awe_, will do!
[20:50] <dobey> mterry: except, now i want food
[20:50] <mterry> :)
[20:51] <dobey> bbq chicken blt at black sheep. mmm
[21:00] <renatu> mhall119, we use webdav
[21:05] <mhall119> that's XML isn't it?
[21:06] <nhaines> On the Internet 2.0, *everything* is XML!  \o/
[21:07] <mhall119> I thought 2.0 meant everything was JSON
[21:07] <nhaines> JSON 2.0 is probably XML too.
[21:08] <akik> json the hockey killer
[21:51] <dobey> mhall119: are they killing xml feeds, or caldav access?
[23:29] <mhall119> dobey: they said "XML feeds"
[23:29] <mhall119> they say iCal is going to continue
[23:38] <nhaines> mhall119: use a Jedi mind trick to convince them to change their minds.
[23:52] <jcstarken> where can i find how to install touch on my galaxy note 10.1 and wii it work ty
[23:53] <mhall119> !devices > jcstarken
[23:53] <ubot5`> jcstarken, please see my private message
[23:53] <mhall119> darn, I always get that wrong and do the PM
[23:53] <mhall119> !devices | jcstarken
[23:53] <ubot5`> jcstarken: You can find the full list of devices, official images, community images, and works in progress at https://wiki.ubuntu.com/Touch/Devices
[23:53] <mhall119> there we go :)
[23:56] <jcstarken> ty