[06:51] <dholbach> good morning
[06:54] <praxy> morning
[07:19] <ArchNET> test
[07:31] <jrbt> hi! ;)
[08:47] <sil2100> Elleo: ping
[08:48] <nhaines> sil2100: pong
[08:48] <nhaines> intercepted!  \o/
[09:09] <Kniple> man-in-the-middle'ed!
[09:10] <JamesTait> Good morning all; happy Friday, and happy International Plastic Bag Free Day! 😃
[09:14] <popey> Kniple: hmm?
[09:14] <Kniple> nothing popey, I just responded late to something.
[09:14] <popey> ah :)
[09:22] <tathhu> öwöw
[09:29] <sil2100> Elleo: do you know how to create the click package for gallery?
[09:56] <SturmFlut> Hmpf, can't find the complete source code for MediaTeks Little Kernel
[10:01] <Elleo> sil2100: not sure, its been a long time since I've done anything with gallery
[10:01] <Elleo> sil2100: will take a quick look see if I can remember
[10:01] <sil2100> Elleo: since bfiller is on holidays today, we released a new deb for gallery and now need the new click uploaded - I could probably find someone that could upload it, but first I need the new click built from trunk
[10:01] <sil2100> Elleo: thanks :)
[10:09] <Elleo> sil2100: I'm assuming from the click-build script that gallery isn't normally built as a fat package or anything? just armhf?
[10:12] <popey> Elleo: it's certainly not a fat package in the store http://popey.mooo.com/mirror/clicks/2015/07/2015-07-03-050001/com.ubuntu.gallery_2.9.1.1183_armhf.click
[10:13] <sil2100> brb
[10:13] <SturmFlut> Oh nice, if you keep all three buttons pressed on krillin/arale it will directly boot into Fastboot mode
[10:13] <Elleo> popey: okay, cool; that makes things simple then
[10:17] <SturmFlut> Oh, no, it's just krillin and probably vegetahd
[10:17] <SturmFlut> arale boots so fast o_O
[10:19] <tathhu> arale?
[10:19] <tathhu> meizu?
[10:22] <jrbt> SturmFlut, how long?
[10:24] <SturmFlut> jrbt: ~22 seconds
[10:24]  * jrbt test with his nexus 4
[10:25] <jrbt> oh.. ok, 22s is fast, my n4 take 14s longer (36')
[10:26] <SturmFlut> jrbt: krillin also takes around 38 seconds
[10:26] <popey> 43 here for krillin
[10:26] <jrbt> holy cow!
[10:27] <popey> Elleo: did you _want_ a fat package for gallery?
[10:28] <Elleo> popey: not if that's not what's normally uploaded, sil just asked me to try and build a gallery click for him as bfiller's not around
[10:28] <popey> ok
[10:43] <Elleo> sil2100: is it okay that I compiled against rc-proposed?
[10:43] <Elleo> sil2100: if not I'll need to reflash a device to stable as the click build script seems to expect to build on device rather than crossbuild in a chroot
[10:45] <Elleo> sil2100: here's the click from that: http://mikeasoft.com/~mike/com.ubuntu.gallery_2.9.1.1208_armhf.click
[10:45] <Elleo> sil2100: do you need me to run  it through any test plan or anything?
[10:51] <sil2100> hm, I think it should be fine
[10:54] <sil2100> popey: to publish a click to the store, do you only need the new click package?
[10:54] <sil2100> Elleo: thanks! :)
[10:55] <Elleo> sil2100: no problem :)
[10:59] <ogra_> SturmFlut, when i did the very first boot optimization work my limit was 1min max boot time ... there is surely still room for optimization to speed it up even more
[10:59]  * ogra_ did only the low hanging fruit bits back then
[10:59] <popey> sil2100: yes :)
[11:00] <ogra_> (though not sure it is worth putting much time into upstart optimization given we'll switch to systemd at some point)
[11:02] <popey> Elleo: sil2100 are all devices now on vivid or wily? (just wondering if building against rc-proposed may cause problems on those devices that are not?
[11:03] <sil2100> popey: all devices are on vivid now, I mean... if you build against stable, you build against vivid
[11:03] <sil2100> So it should be fine
[11:03] <popey> ok
[11:03] <sil2100> Especially that the .deb package has been built against things from rc-proposed
[11:03] <sil2100> My knowledge about clicks is not high enough, but I suppose rc-proposed builds are fine?
[11:04] <sil2100> popey: hmmm, I did find an older click for gallery
[11:04] <sil2100> Without the automatic translation landing
[11:05] <sil2100> I think Bill always built a new one before pushing to the store after a landing, so I would prefer to use the one built by Elleo (if it's safe)
[11:05] <Elleo> sil2100: actually, that click says it has framework 14.10
[11:06] <Elleo> sil2100: so really it should probably be built against 14.10 to be safe
[11:06] <Elleo> sil2100: or have its framework bumped up to 15.04 so it can't be installed on any devices that haven't upgraded
[11:07] <sil2100> I think let's leave 14.10 then... I don't want us to do anything that bfiller isn't aware of
[11:07] <sil2100> Elleo: can you build it somehow against 14.10?
[11:07] <Elleo> is there any channel that still tracks 14.10?
[11:07] <sil2100> hmmm
[11:07] <sil2100> No
[11:08] <Elleo> I don't think I can then :/
[11:08] <sil2100> Elleo: could you check what framework version did http://people.canonical.com/~bfiller/com.ubuntu.gallery_2.9.1.1205_armhf.click have?
[11:08] <sil2100> This is  the one that bfiller generated for testing purposes
[11:09] <popey> you can build in a chroot, can you not?
[11:09]  * popey is guessing :)
[11:10] <Elleo> sil2100: ubuntu-sdk-14.10
[11:10] <sil2100> Yeah, so we'll have to stick with that, as that's what bfiller wanted to use probably
[11:10] <sil2100> hmmm
[11:10] <Elleo> popey: the click-build script in gallery doesn't do crossbuilding
[11:11] <popey> oh
[11:11] <Elleo> popey, sil2100: of course it's entirely possible that script is out of date and there is a way to crossbuild it that I'm unaware of
[11:11] <Elleo> sil2100: might be worth asking artmello when he gets on, I think he's worked on gallery a lot more recently than me
[11:11] <sil2100> I remember some jenkins job somewhere
[11:12] <sil2100> But hmmm
[11:12] <sil2100> Elleo: ok, we'll do so, for now let's hold
[11:12] <sil2100> If he doesn't know, we can always publish the click  that bfiller had for testing
[11:12] <sil2100> Although I would prefer not...
[11:12] <popey> sil2100: http://s-jenkins.ubuntu-ci:8080/job/gallery-app-click/
[11:13] <popey> http://s-jenkins.ubuntu-ci:8080/job/gallery-app-click/263/ has r1205
[11:13] <popey> did you specifically want 1208?
[11:13] <popey> (for translations?)
[11:13] <sil2100> Yes, I checked how bfiller released previous clicks and he seems to rebuild after the deb release
[11:13] <Elleo> sil2100: are you sure bfiller's actually off today? I can't remember him mentioning it but I forget plenty of stuff :P
[11:14] <sil2100> Elleo: it's an US holiday
[11:14] <sil2100> ;)
[11:14] <Elleo> ah, okay
[11:14]  * popey presses the "build now" button so you get a r1280 armhf click if you need it
[11:15] <popey> sil2100: fwiw, the click in bfiller's home directory is binary identical to the one at http://s-jenkins.ubuntu-ci:8080/job/gallery-app-click/263/
[11:16] <popey> so I would say he is providing you with the jenkins-made click
[11:16] <popey> and as such those should be the ones you use.
[11:16] <popey> IMHO
[11:18] <sil2100> popey: thanks :)
[11:18] <sil2100> Yeah, this was the jenkins job I remembered
[11:18] <sil2100> Ok, I slowly move out now for lunch
[11:18] <Elleo> popey: awesome, thanks :)
[11:21] <popey> np
[11:31] <seb128> bah
[11:31] <seb128> "phablet   2658 45.8  0.9 369888  8920 ?        Ssl  09:39 105:51          \_ /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperegistry
[11:31] <seb128> "
[11:31] <seb128> that's eating cpu for hours
[11:31] <seb128> who knows about that sort of issues and what is useful to include as debug info?
[11:32] <seb128> (that's bq on rc-proposed 56)
[11:32] <jibel> seb128, bug 1470750
[11:32] <seb128> jibel, thanks
[11:33] <seb128> it's not a leap second issue
[11:34] <seb128> I updated that device to 56 this morning
[11:37] <popey> sil2100: http://s-jenkins.ubuntu-ci:8080/job/gallery-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.gallery_2.9.1.1208_armhf.click
[11:41] <meles> I tried to install X like discussed on the mailing list. I failed and now I can't open some apps like the camera. I even reset the phone to factory default. Can anybody help me? Output from dmesg is found here http://pastebin.com/78D8dSCW
[11:44] <ogra_> meles, well, re-flash it
[11:45] <ogra_> if you made it writable thats the only sane way to get back to normal
[11:45] <ogra_> *permanently writable that is
[11:46] <ogra_> resetting to factory default assumes your readonly rootfs has never been changed
[11:46] <ogra_> but you likely installed stuff in it
[11:48] <meles> ogra_ flashing like it is described here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/?
[11:48] <ogra_> meles, http://askubuntu.com/questions/602035/how-do-i-use-ubuntu-device-flash-with-the-bq-aquaris-e4-5-and-aquaris-e5
[11:49] <ogra_> well, in fact http://askubuntu.com/a/602037/217953
[11:50] <meles> _ogra ok, thank you!
[12:00] <nocturn> Hi guys, I just got my Meizu MX, but if I turn it on, it stops on theubuntu logo
[12:00] <nocturn> it has been there for over 15 min
[12:01] <nocturn> Can I do anything but send it back?
[12:03] <praxy> nocturn: did you try turning it off completely, and retry ?
[12:03] <nocturn> praxy, yes.  Same result
[12:05] <praxy> nocturn: I'm sure there are things you can try. But I'm not the expert here, I'm sure other people will have some suggestions
[12:05] <praxy> I suppose it's not an issue of it not being charged enough to start
[12:06] <nocturn> praxy, I charged it fully first.  It also gets really hot
[12:10] <praxy> nocturn: I'm trying to find info for you, I hope others here will pitch in :D
[12:10] <praxy> must be no fun to have this issue on a new device though
[12:10] <nocturn> praxy, thanks!
[12:10] <praxy> I don't know if the MX getting hot is normal or not.. I have a BQ
[12:12] <tathhu> praxy: which one? hows battery life?
[12:14] <praxy> tathhu: E5 HD. Battery life is pretty good, slightly worse than my Moto E I think, but not much.
[12:15] <tathhu> what that even means :P
[12:15] <praxy> I think I did 4 or 5 days before needing my last charge, light usage, daily alarm, maybe an hour of calls. Wifi/data off when not needed.
[12:16] <nocturn> praxy, I just booted it with volume up + power to get into recovery mode
[12:16] <nocturn> it just gave an orange logo instead of a red one, that does not look good
[12:17] <tathhu> praxy: thanks, i'm sure my 5's battery life will be about same as i get on my jolla, heavy usage and lasts about aday
[12:18] <jgdx> popey, part of the wpa-ep landed. :)
[12:20] <praxy> nocturn: what are options from the recovery ?
[12:20] <nocturn> only get the orange logo... no options
[12:23] <mpt> seb128, hi, is there anything else I can do to get <https://code.launchpad.net/~mpt/ubuntu-system-settings/1359344-restart-install/+merge/263237> landed?
[12:24] <seb128> mpt, not really, there are like 3 system settings changeset being in line already for landing, it's going to take a bit
[12:24] <seb128> mpt, maybe ask to jgdx if he can batch that with some other of the pending changes
[12:24] <mpt> jgdx, ^^^ ? :-)
[12:26] <praxy> nocturn: I would try again power + volume up or power + volume down
[12:26] <jgdx> mpt, isn't that in a silo already?
[12:26] <jgdx> mpt, do you even silo
[12:27] <jgdx> mpt, In silo ubuntu/landing-022. Packages built. Testing pass. QA needs to sign off.
[12:27] <nocturn> praxy, same result, it says recovery mode than orange logo
[12:28] <jgdx> it's not certain it will land though, we're at the mercy of the trainguards/product team
[12:31] <praxy> nocturn: then I don't know.. you should probably contact Meizu
[12:31] <praxy> nocturn: can you see the device with adb?
[12:33] <nocturn> praxy, will try that next
[12:33] <nocturn> have to install adb first
[12:35] <mpt> jgdx, silo? I can’t even.
[12:36] <mpt> jgdx, thanks for the info though. :-) Where could I look this up for myself next time?
[12:36] <jgdx> mpt, the spreadsheet is the source of information on this process and launchpad won't get notified before it lands. So the spreadsheet: https://wiki.ubuntu.com/citrain
[12:37] <jgdx> mpt, time for a quick question?
[12:37] <mpt> sure
[12:38] <ogra_> nocturn, try that https://lists.launchpad.net/ubuntu-phone/msg13878.html
[12:38] <jgdx> mpt, when load the phone screen in System Settings, it takes a couple of seconds to retrieve the call forwarding settings. Meaning this [1] will always say "Off" until we have one or more settings. That's bad.
[12:38] <jgdx> [1] https://wiki.ubuntu.com/PhoneApp?action=AttachFile&do=get&target=phone-settings-call-forwarding-access.png
[12:38] <jgdx> s/when load/when we load
[12:39] <jgdx> we can't really change that without substantial (relative) changes to the backend, but we can do a lot of things on the frontend.
[12:39] <mpt> jgdx, “Therefore the current settings should be cached, and shown as a summary value for the “Call forwarding” item on the “Phone” screen — “All calls” for CFU on, “Some calls” for CFU off but any other type on, or “Off” for none — only if you have visited the “Call forwarding” screen since the last time the phone was turned on.”
[12:40] <jgdx> that's the substantial bit
[12:40] <mpt> What I meant by that was, if you haven’t visited the “Call forwarding” screen yet, that item should have no summary value at all.
[12:40] <jgdx> mpt, oh. So blank?
[12:41] <mpt> Right. Sorry that wasn’t clear.
[12:42] <jgdx> mpt, okay, makes sense now.
[12:47] <mpt> jgdx, specification updated. <https://wiki.ubuntu.com/PhoneApp?action=diff&rev2=21&rev1=20> I hope it’s clearer now.
[12:49] <jgdx> mpt, yep, thanks.
[12:52] <dholbach> what's the preferred method of copying all my data from one phone to another?
[12:52] <dholbach> popey, ^ what do you normally use?
[12:58] <popey> dholbach: i dont
[12:58] <dholbach> hum
[12:59] <seb128> dholbach, tar & scp ? ;-)
[12:59] <seb128> I would tar the userdir, copy it over and untar
[12:59] <seb128> that doesn't restore your installed applications though nor the click datas
[13:01] <dholbach> thanks seb128
[13:01] <dholbach> I think I just found out how to use ondra's script - maybe that'll work out for me :)
[13:01] <seb128> dholbach, yw
[13:03] <popey> you could do a click list, get the names of all the apps you have installed, and then grab those clicks from my mirror, and install them en masse?
[13:04] <dholbach> yeah, that'd be an idea - although you wouldn't get the data the click package stored or would you?
[13:05] <seb128> you wouldn't not
[13:05] <seb128> no
[13:11] <SturmFlut> Nice, Brian Douglass has won nik90's MX4 competition :)
[13:12] <nik90> SturmFlut: :)
[13:17] <popey> dholbach: I thought you were going to tar up userdir? - that grabs all the data
[13:18] <dholbach> I don't know yet - right now I'm just trying ondra's script - if it fails I might go back to another method
[13:18] <dholbach> earlier I made the mistake of not running it in recovery mode :)
[13:21] <ogra_> SturmFlut, so will we get a special 50GU edition of uappexplorer now ?
[13:21] <ogra_> "optimized for meizu"
[13:22] <SturmFlut> ogra_: I read that the GU setting for arale will be fixed with the next update
[13:22] <ogra_> yep
[13:23] <ogra_> well, "fixed"
[13:23]  * ogra_ isnt a fan of 50GU either ... my device currently runs at something like 55 or 56
[13:27] <sil2100> popey: thanks! Sorry, missed the ping - could you get this click uploaded and moved further down the stream?
[13:27] <sil2100> It's already signed off basically
[13:29] <popey> sil2100: you want gallery 1208 uploaded to the store?
[13:29] <popey> sil2100: where's the QA signoff?
[13:32] <jibel> popey, https://trello.com/c/N3b70CZp/1833-ubuntu-landing-007-gallery-app-bfiller it was in silo 7
[13:32] <sil2100> popey: yeah, it was already signed-off, bill only rebuilds the click afterwads to always point the final release after the .deb is pushed out
[13:32] <sil2100> At least that's what I saw him do
[13:33] <popey> okay
[13:34] <sil2100> popey: thanks! :)
[13:36] <popey> np
[13:45] <popey> sil2100: done
[13:45] <sil2100> popey: yay, thank you our savior
[13:45] <sil2100> :)
[13:47] <SturmFlut> Hmm, krillin Little Kernel has a special, extended version of the Boot Menu, but apparently the key that would have to be pressed during boot doesn't exist on this hardware.
[14:01] <bfiller> sil2100, popey : I can take care of gallery upload to store if it hasn't been done yet
[14:01] <bfiller> was planning on doing that today
[14:07] <popey> bfiller: already done
[14:07] <bfiller> popey: thanks
[14:07] <popey> np
[14:07] <bfiller> popey: bulit the click from trunk?
[14:08] <popey> grabbed it out of jenkins
[14:08] <popey> which built from trunk, yes
[14:08] <bfiller> popey: ok
[14:31] <mpt> mandel, ondra, slangasek, stgraber: Could the graphic shown during flashing contain localizable text?
[14:33] <dholbach> popey, how do I enter recovery mode on an mx4? when I typed 'adb reboot recovery' it restarted and is now showing the Ubuntu logo, but 'adb devices' lists the device as offline
[14:35] <dholbach> power button + vol up takes me to the same thing
[14:35] <popey> not sure..
[14:35] <dholbach> ogra_, ^ do you know?
[14:51] <ogra_> dholbach, no, and nobody from the arale team ever comes online on public IRC
[14:51]  * ogra_ asked like ten times for that now 
[14:51] <dholbach> ok
[14:51] <ogra_> there are actual users with actual probs here now ... and we cant really help :(
[14:52] <ogra_> dholbach, oh, but the recovery has definitely no adb inside ... thats true for all shipped recoveries
[14:52] <ogra_> you would have to flash an open one
[14:52] <dholbach> oh ok
[14:52] <ogra_> (which i dont know where to find for the arale ... only the bq devices are documented on askubuntu currently :/ )
[15:17] <alin> hi
[15:17] <alin> asked yesterday too but did not go very far away...
[15:18] <alin> is normal for an ubuntu meizu mx4 not to show in adb?
[15:20] <brobostigon> alin: i know this is a stupid question, but is developer mode turned on?
[15:20] <alin> yes it is
[15:20] <brobostigon> ok,
[15:21] <ogra_> aldo you have the phablet-tools PPA enabled and the android-tools-adb and libmtp pakages from there installed ?
[15:21] <ogra_> alin, ^^^
[15:22] <ogra_> (also make sure the screen is unlocked else adb wont let you in)
[15:23] <alin> ogra_: I have adroid-tools from opensuse I am not using ubuntu
[15:23] <ogra_> oh, then yoou will have to hack the device ID into that somehow
[15:24] <ogra_> i doubt suses udev and androids adb will be able to find the device
[15:25] <brobostigon> on debian here, i need to be root, for adb to see my device.
[15:25] <ogra_> yeah, thats what udev would handle for you usually :)
[15:25] <brobostigon> yes, definatly, :)
[15:26] <ogra_> alin, try the following:
[15:26] <ogra_> echo 0x2a45 >> ~/.android/adb_usb.ini
[15:26] <ogra_> adb kill-server
[15:26] <ogra_> sudo adb start-server
[15:26] <ogra_> tnen see if adb devices or adb shell shows it
[15:27] <ogra_> also note that the USB of the MX4 has issues with USB3 hubs/ports ... try a 2.0 or even 1.1 one
[15:27] <alin> ogra_: was exactly the opposite
[15:27] <ogra_> the opposite of what ?
[15:27] <alin> ogra_: shows up only on a powered usb 3.0
[15:27] <alin> ogra_: on a usb 2.0 does not show
[15:27] <ogra_> it wont transfer any useful data over 3.0 i fear
[15:27] <alin> ogra_: yes that I noticed too
[15:27] <ogra_> (there are hw issues with that)
[15:27] <alin> ogra_: that is later...
[15:28]  * ogra_ uses a USB 1.1 non-powered hub here ... thats the only reliable connection i can get 
[15:29] <alin> ogra_: blimey all the hubs I have are gone in a box since I move office
[15:29] <ogra_> sadly (as i said) it is a HW issue ... not much we can do in SW to fix that
[15:30] <ogra_> anyway, the above should at least make sure the adb side works fine ...
[15:30] <ogra_> for USB, watch dmesg to see what it does
[15:31] <ogra_> (i get a lot of kernel messages and hardware resets here in case the hub doesnt work)
[15:31]  * ogra_ goes afk
[15:36] <SturmFlut> ogra_, john-mcaleely: Do you know where /sbin/init on phones comes from?
[15:36] <ogra_> SturmFlut, upstart
[15:37] <ogra_> (now really afk)
[15:37] <cle> does anyone can buy meizu mx4 device outside of European ?
[15:38] <alin> cle: in china
[15:38] <SturmFlut> But how does upstart decide if it should boot normally or start /system/bin/factory ? I've been looking for the answer to this for half an hour now.
[15:38] <cle> i have an invite but i'm from Vietnam
[15:42] <john-mcaleely> I had assumed that was in here https://github.com/bq/aquaris-E4.5/blob/aquaris-E4.5-ubuntu-master/ubuntu/initrd/ubuntu-touch-generic-initrd_0.94vivid5_armhf.deb
[15:42] <john-mcaleely> but, I don't actually know
[15:47] <Kniple> One thing that has been bugging me since I got my ubuntu phone: The swedish layout for the keyboard has the ä and ö buttons switched from what its supposed to be...
[15:48] <kenvandine> Kniple, file a bug please
[15:48] <kenvandine> we can get the keyboard layout fixed
[15:48] <kenvandine> Kniple, https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard
[15:49] <Kniple> thanks kenvandine, i'll file a bug. :)
[15:49] <kenvandine> Kniple, thank you!
[15:50] <Elleo> Kniple: if I remember correctly that's actually already fixed, and the fix will appear in OTA 5 :)
[15:50] <Elleo> Kniple: yep, here we go: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1395402 so that fix should appear sometime later this month with the next update
[15:51] <Kniple> oh well, semes I don't need to finish this report then :p
[15:51] <Elleo> :)
[15:53] <Kniple> Excuse my ineptitude with launchpad, but is there an easy way to search bugs related to the touch version?
[15:54] <popey> https://wiki.ubuntu.com/Avengers links to many of the components used in the phone
[15:54] <Kniple> thanks popey
[15:54] <popey> np
[15:54] <Kniple> this community is the best :3
[15:58] <SturmFlut> john-mcaleely: I've finally got it. MTK uses a modified Android init in the initrd that knows how to check if the previous boot stages activated Factory mode.
[15:59] <SturmFlut> john-mcaleely: Which makes sense, because this Factory mode only exists on MTK SoCs
[16:00] <john-mcaleely> sounds fair
[16:01] <SturmFlut> john-mcaleely: It gets even better, they built the API into the kernel, the Boot mode is passed from Little Kernel to the actual Linux kernel and appears in /sys/class/BOOT/BOOT/boot/boot_mode
[16:02] <SturmFlut> and there are actually two factory modes, the normal one and another called "ATE_FACTORY_BOOT"
[16:15] <alin> ogra_: the echo did the trick
[16:39] <robin-hero> Hey all!
[16:41] <robin-hero> After the OTA-4 update the calendar events' dates aren't in the right format. It should be júl. 11., szo 08.00:
[16:41] <robin-hero> http://i.imgur.com/Rh4HcK4.png
[16:42] <popey> hi robin-hero
[16:43] <robin-hero> hi popey
[16:43] <popey> is that Hungarian?
[16:44] <robin-hero> Yes
[16:44] <popey> what is your locale settings in System Settings -> Language & Text set to at the top?
[16:46] <robin-hero> Magyar (Magyarország) -> Hungarian (Hungary)
[16:50] <popey> not sure if that's a bug or not, and where that should be filed. seb128 ^ got any good ideas?
[16:50] <popey> https://en.wikipedia.org/wiki/Date_and_time_notation_in_Hungary doesn't explain it :)
[16:51] <robin-hero> It worked in the previous release
[16:54] <popey> ok, robin-hero perhaps file a bug at https://bugs.launchpad.net/canonical-devices-system-image and we can move it to the most appropriate place.
[16:54] <robin-hero> okay, I'm just trying to find a screenshot which taken before OTA4...
[16:56] <kenvandine> seb128, the fix for bug 1470881 is in proposed, can you remove the block-proposed tag now?
[17:01] <seb128> kenvandine, sure, remove it
[17:01] <kenvandine> thx
[17:04] <mr-tt> is it possible to run regular qt5 apps created with standard qtcreator(not utouch-sdk) on utouch?
[17:09] <SturmFlut> mr-tt: You will probably have to at least use the schroot to create an armhf binary
[17:12] <mr-tt_> SturmFlut: how do i create a utouch chroot on non-ubuntu? or would it be simpler to install a regular ubuntu chroot and run ubuntu sdk from there(can this crosscompile)?
[17:14] <SturmFlut> mr-tt_: Most likely the easiest way is to run Ubuntu 15.04 in a virtual machine.
[17:15] <mr-tt_> SturmFlut: arm ubuntu i guess?
[17:15] <alin> ok... adb shell dies http://paste.opensuse.org/8501852
[17:15] <alin> I still see the device listed
[17:16] <mr-tt_> SturmFlut: how big is an ubuntu arm chroot/vm?
[17:17] <SturmFlut> mr-tt_: The schroot for cross-compiling is 1.7 GB on my machine. A full Ubuntu 15.04 installation in a VM, with the Ubuntu SDK and enough space for your projects, will need several gigabytes.
[17:18] <mr-tt_> i'd rather have an schroot then. is it possible to create that on non-ubuntu?
[17:19] <mr-tt_> SturmFlut: do i use debootstrap to set it up? vivid has no arm repos, so how to do that?
[17:21] <SturmFlut> mr-tt_: you use the schroot utility directly, it comes from Debian. But I have never used it on non-Ubuntu, you will probably need all the configuration files.
[17:22] <SturmFlut> mr-tt_: Oh, and it just came to my mind that you will be needing the "click" utility too, that only comes with Ubuntu I think
[17:22] <mr-tt_> SturmFlut: i thought schroot is only for entering chroots, not downloading/setting them up
[17:24] <popey> click is used to set them up
[17:24] <popey> usage: click chroot [-h] -a ARCHITECTURE [-f FRAMEWORK] [-s SERIES] [-n NAME] {create,destroy,upgrade,install,run,maint,begin-session,end-session,exists}
[17:25] <popey> e.g. sudo click chroot -a armhf -f ubuntu-sdk-15.04 -s vivid create
[17:25] <popey> that kinda jazz
[17:29] <mr-tt_> can i run a precompiled qt5 app from ubuntu touch terminal?(just the files the app needs copied to the phone, not packaged)?
[17:42]  * tathhu is goign to have Aquaris E5 instead of 4.5, weeeeeeeeeee ^^
[17:43] <popey> \o/
[17:44] <tathhu> Should've ordered that in first place, more waiting :((((
[17:47] <tathhu> But yeah, awesome ^_^
[17:47] <tathhu> Oh what i just did..
[17:59] <mr-tt_> if i have the source of a qt5 project(builds with qmake), how do i get that to build for armhf?
[17:59] <mr-tt_> i'd like to turn it into an utouch app
[18:00] <mr-tt_> or at least run it from terminal on the phone
[18:01] <popey> create a chroot on the phone itself, and build in that? thats what ogra_ does
[18:02] <mr-tt_> popey: takes too much space on the phone i think
[18:03] <popey> really>? what you building? KDE? :)
[18:03] <mr-tt_> plus i can't test in on the desktop then
[18:03] <tathhu> popey: can I run plasma 5 on my phone? :P
[18:03] <popey> well, you're kinda asking the impossible
[18:03] <mr-tt_> popey: no just some small example app :)
[18:03] <popey> if you build for desktop, its an i386/armhf binary
[18:03] <popey> if you build for phone it's an armhf binary
[18:04] <popey> i doubt a sample qt app requires too much space on the phone
[18:04] <mr-tt_> popey: so ubuntu sdk can build for armhf?
[18:05] <popey> yes, in a schroot
[18:05] <popey> i do it all the time
[18:05] <mr-tt_> popey: does the sdk automatically install an schroot?
[18:06] <popey> it prompts you to when you start it up for the first time
[18:06] <popey> i need to go and cut the grass, back in a bit
[18:06] <tathhu> SDK = qtcreator + ubuntu-spesific-plugins and stuff?
[18:06] <popey> yes
[18:06] <tathhu> cool
[18:07] <mr-tt_> popey: didn't do that iirc
[18:07] <nik90> mr-tt_: Did you read through the documentation at developer.ubuntu.com ?
[18:07] <mr-tt_> i guess i have to create a target device somehow then?
[18:07] <nik90> mr-tt_: https://developer.ubuntu.com/en/apps/sdk/tutorials/click-targets-and-device-kits/
[18:07] <nik90> mr-tt_: https://developer.ubuntu.com/en/apps/sdk/tutorials/creating-an-sdk-app-project/
[18:07] <nik90> It is explained very clearly how to do this
[18:08] <mr-tt_> nik90: i take a look at it, thanks
[18:10] <SturmFlut> New post: "MediaTek details: Little Kernel", http://sturmflut.github.io/mediatek/2015/07/05/mediatek-details-little-kernel/
[18:10] <SturmFlut> I think I might be the only person outside of china who writes about these things ;)
[18:15] <mcphail> SturmFlut: you are a God amongst men. Great work!
[18:15] <SturmFlut> mcphail: No, I'm a guy with a source code browser ;)
[18:15] <mcphail> SturmFlut: and a lot of patience...
[18:16] <SturmFlut> mcphail: It's the luxury of "being able to work on what you want". If I had to do it for a living, it would probably get bored really soon.
[18:18] <SturmFlut> s/it would/I would/
[18:18] <mcphail> It is great to get stuff like this documented. And especially good that it isn't on XDA with <blink> tags, 17 fonts and centre-justified text
[18:18] <SturmFlut> mcphail: My girlfriend works in marketing, she keeps giving me tips on how to monetize this ;)
[18:19] <mcphail> SturmFlut: to be fair, outside channels like this there may not be much of a market...
[18:20] <SturmFlut> mcphail: Yep. Exactly. And I hate ads on other sites, so I don't want any on mine.
[18:20] <mcphail> SturmFlut: I'm an adblock freeloader, I'm afraid
[18:21] <mcphail> SturmFlut: but I'd click a "Donate" button to keep the content coming
[18:22] <popey> +1
[18:24] <SturmFlut> mcphail: I don't even want that ;) Information wants to be free. I stand on the shoulders of giants, all the tools I use are free and 99% of the things I know were given to me for free. Why on earth should I chose to not give back, for free? I don't even pay for the hosting of that site.
[18:25] <tathhu> What, I can "send" my app on phone an test it there o.o
[18:25] <tathhu> *and
[18:27] <popey> you can run on phone, yes
[18:27] <popey> over usb
[18:27] <SturmFlut> mcphail: Also if I start putting ads on that site or taking donations, I will be encouraged to analyze what my readers want so I can write more content that turns into more ad revenue and more donations... suddenly the whole fun turns into work.
[18:27] <mcphail> SturmFlut: well, your hard work is appreciated. I really enjoy your concise use of English
[18:28] <SturmFlut> mcphail: \o/
[18:29] <tathhu> popey: well this is cool
[18:29] <tathhu> oh i might be do that on jolla too, woops.
[18:29] <tathhu> "and now you tell that"
[18:30] <svij> SturmFlut: anyway it's interesting that you live in the future ;)
[18:30] <SturmFlut> tathhu: Developing apps on the desktop and then sending them to the phone to test them is actually the norm, everybody does it like this.
[18:30] <tathhu> SturmFlut: w000000t
[18:31] <tathhu> :D
[18:33] <SturmFlut> svij: Yeah, that was a stupid mistake, I didn't think that I'd finish this article so quickly. When I realized, the link was already out there, and jekyll makes the date a part of the URL.
[18:33] <svij> SturmFlut: hehe
[18:33] <svij> an update from today on a article from tomorrow is funny ;)
[18:34] <SturmFlut> svij: Pssst, the space time continuum doesn't like these things!
[18:34]  * svij needs to write down his 2 (or actually 4) reviews of the new phones…
[18:34] <svij> SturmFlut: :)
[18:35] <popey> Wibbly wobbly timey wimey
[18:36] <davmor2> popey: Don't blink
[18:36] <davmor2> popey: Don't even blink
[19:35] <SturmFlut> Interesting, fastboot apparently uses 32 bit length fields when flashing. So you can't flash to a partition that's larger than 4 GB.
[20:05] <EdwardMorbius> hello, anyone knows what is signal 18? I have this in unity 8 log after a UI freeze, WARNING **: Unable to get pids for 'unity8-dash' to send signal 18
[20:05] <EdwardMorbius> ApplicationController::resumeApplication FAILED to resume appId= "unity8-dash".
[20:08] <EdwardMorbius> Also "Nested Mir Display Error: Failed to update EGL surface: EGL_BAD_DISPLAY (0x3008)"
[20:09] <SturmFlut> EdwardMorbius: Signal 18 is SIGCHLD
[20:10] <SturmFlut> EdwardMorbius: I think unity8-dash crashed and Unity8 can't find out who to tell about it
[20:10] <SturmFlut> mzanetti: ^^
[20:11] <EdwardMorbius> SturmFlut probably, both of these errors were in the log, including this QML UCDeprecatedTheme: Theme.palette is deprecated. Use ThemeSettings instead.
[20:11] <mzanetti> hmm...ignore the theme warning...
[20:12] <mzanetti> the other probably deserves a bug report
[20:12] <mzanetti> the EGL thing
[20:12] <EdwardMorbius> mzanetti https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1465826
[20:12] <EdwardMorbius> my log and another user's logs are in there.
[20:18] <EdwardMorbius> I also noticed different behavior when UI freezes after OTA-4, before last update when UI froze it would reboot itself soon after, but now after OTA-4 it freezes permanently and I need to power off the phone to resolve it.
[20:18] <mzanetti> oh :(
[20:19] <mzanetti> so this always happens on application switching?
[20:19] <EdwardMorbius> mzanetti from what I noticed usually on application switching, a few times it happened after a notification arrived and I tried opening it.
[20:20] <mzanetti> mhm... ok. that helps. can you please add that to the bug
[20:20] <mzanetti> I assigned it further. hopefully should get some attention now
[20:21] <EdwardMorbius> mzanetti I will add it now
[20:21] <mzanetti> thanks a lot
[20:24] <EdwardMorbius> mzanetti no problem, I added this information to the bug report, I can upload more logs if necessary next time it happens.
[20:28] <mzanetti> EdwardMorbius, what files do you have in /var/crash/ ?
[20:28] <EdwardMorbius> mzanetti hold on I will check
[20:29] <mzanetti> probably easiest if you pastebin "ls -l /var/crash/" somewhere
[20:31] <EdwardMorbius> mzanetti I have three, all are usr_lib_arm_something_unity_scope_runner, two .uploaded and one .crash
[20:31] <mzanetti> EdwardMorbius, no _usr_bin_unity8.32011.crash or _usr_bin_unity8-dash.32011.crash around?
[20:32] <EdwardMorbius> mzanetti no, maybe because the phone had to be powered off?
[20:32] <mzanetti> hmm
[20:33] <mzanetti> well, all you can do now is try catch such a file. maybe log in while it's frozen (if that's possible) or so
[20:33] <mzanetti> we'll try to reproduce. do you have many applications open usually?
[20:33] <SturmFlut> Oh, I was wrong, you can actually flash partitions larger than 4 GB with fastboot.
[20:34] <EdwardMorbius> mzanetti I will try next time it happens, or when I power it on I will immediately check /var/crash. no I dont have many open, usually its a few, browser, telegram, sometimes messaging or music player.
[20:34] <mzanetti> the logs point to file manager often
[20:35] <mzanetti> :)
[20:36] <EdwardMorbius> mzanetti I dont use file manager often and I am certain many of the UI freezes happened without file manager being open.
[20:37] <EdwardMorbius> It is possible I used it when that log was posted, dont remember that far back :D
[20:37] <mzanetti> ok. no problem :)
[20:38] <mzanetti> if you happen to find a way to trigger it intentionally, let us know :)
[20:38] <EdwardMorbius> mzanetti I will but so far it doesnt seem it is triggered by a specific action (application switching seems most common cause)
[20:39] <EdwardMorbius> I will try catching that crash log in /var/crash/, where are mir logs located so I can take a look at them too?
[20:39] <mzanetti> that's all in unity8.log
[20:40] <EdwardMorbius> I see, well I will hunt for it next time then when its fresh :)
[21:00] <nocturn> Hi, My new Meizu MX is bootlooping out of the box, I tried to install a new image, but it exits  on: Failed to enter Recovery
[21:01] <mzanetti> O_o
[21:03] <nocturn> Output from flash-device:
[21:03] <nocturn> http://pastebin.com/kP9HpCG6
[21:04] <SturmFlut> nocturn: That's because the production devices do not start ADB in their recovery
[21:05] <SturmFlut> nocturn: You need a recovery image that has ADB enabled
[21:06] <nocturn> SturmFlut, I downloaded one I though
[21:07] <SturmFlut> nocturn: But you didn't pass it do ubuntu-device-flash
[21:07] <nocturn> I already tried this: https://lists.launchpad.net/ubuntu-phone/msg13878.html
[21:07] <nocturn> this should have installed it: fastboot flash recovery recovery.img
[21:08] <SturmFlut> Hmmmmmmm
[21:08] <SturmFlut> It actually should
[21:08] <nocturn> That command was succesfull
[21:11] <SturmFlut> nocturn: Which version of ubuntu-device-flash do you have?
[21:12] <SturmFlut> nocturn: and which of android-tools-adb
[21:13] <nocturn> ubuntu-device-flash 0.19-0~142~ubuntu14.04.1
[21:13] <nocturn> android-tools-adb 4.2.2+git20130218-3ubuntu36
[21:14] <nocturn> from the SDK PPA
[21:16] <nocturn> SturmFlut, it is strange that it didn't boot out of the box also, I get the spinning ubuntu logo forever
[21:16] <SturmFlut> I have ubuntu-device-flash 0.20-0ubuntu1
[21:16] <SturmFlut> nocturn: You got it and it never booted?
[21:16] <alin> SturmFlut: nocturn one problem I had the phone did not appear on usb at all
[21:16] <nocturn> It went to the spinning logo and stayed there
[21:16] <nocturn> waited 25 minutes, then reset
[21:16] <nocturn> no change
[21:17] <alin> ogra_: pointed out you need a non usb 3.0 port to connect
[21:18] <boiko> Laney: sorry for the late reply on that, we branched telephony-service (and the other affected packages) to do vivid landings, so the build fix for latest tp-qt in telephony-service can land now, I will test/land it monday morning
[21:24] <nocturn> SturmFlut, you have a newer device-flash, are you on Trusty or later?
[21:24] <alin> boiko: so if you have tp-qt do you have any client instalable?
[21:25] <SturmFlut> nocturn: vivid
[21:25] <nocturn> SturmFlut, Trusty here
[21:25] <boiko> alin: you mean on desktop?
[21:26] <boiko> alin: on phones we use telepathy for phone calls and messaging, but we don't currently use/support any other IM protocols
[21:29] <alin> boiko: ok... on phone... I see kind of pitty
[21:29] <boiko> alin: although we have started changes things here and there to have more generic telepathy support, that's not fully done yet
[21:30] <SturmFlut> nocturn: If the phone never worked, I would assume that there's a hardware problem.
[21:30] <boiko> alin: you can tweak telephony-service into allowing other protocols by registering them at /usr/share/telephony-service/protocols/
[21:30] <nocturn> SturmFlut, I will try to RMA
[21:30] <nocturn> Thanks
[21:31] <boiko> alin: and I used to have a experimental VOIP support changes for telephony-service and dialer-app, but they might be outdated by now
[21:32] <boiko> alin: at some point I think we will support more stuff (not sure if everything telepathy supports or a wider subset of what we support now though)
[21:37] <alin> boiko: that would be great... I am thinking more of google stuff
[21:37] <alin> boiko: anyhow I suspect a lot of these are not aligned with this applets everywhere...
[21:44] <alin> I tried usb tethering by enabling rndis but once that is done I cannot receive calls anymore
[21:44] <alin> is that normal?
[21:46] <SturmFlut> "Our Meizu devices also got a new device tarball, now ready for release in the nearest days"
[21:46] <SturmFlut> deviceS?
[23:22] <SturmFlut> New post: "Hacking Ubuntu Touch, Part 8: Fastboot", http://sturmflut.github.io/ubuntu/touch/2015/07/04/hacking-ubuntu-touch-part-8-fastboot/
[23:22] <SturmFlut> I'm on fire!
[23:28] <SturmFlut> ogra_: ^^
[23:40] <nhaines> SturmFlut: I love your stories.  But please be careful about posting them to /r/Ubuntu.  It's against reddit policy to post your own stuff more than 10% of the time (it's considered spamming) and it can get you automatically banned.
[23:40] <nhaines> (I'm approving them when they come through the modqueue but I have nothing to do with reddit-wide shadowbans.)
[23:41] <SturmFlut> nhaines: Oh!
[23:42] <nhaines> Ironically, if someone else does it it's fine.  Weird quirk of reddit.  It's a good way to keep corporations from spamming but sometimes it's not too flexible.
[23:44] <SturmFlut> nhaines: I think I can talk popey into posting the links. I don't use reddit at all, so I'll never be able to "counterbalance" my own posts with other stuff.
[23:46] <nhaines> SturmFlut: probably for the best then.  I don't want to see you get shadowbanned. :)