[08:12] <Saviq> humpf I lost wifi on krillin... it seems to connect and get ips and stuff, but no data goes through :|
[08:32] <SturmFlut> If I have a cmake-based Ubuntu Touch app, how can I cross-compile it manually without going through Qt Creator? It seems like Qt Creator sets a lot of variables and uses an armhf chroot, is it possible to replicate this manually in an easy manner?
[08:47] <Saviq> SturmFlut, you can use sbuild (that's what QtC uses) or schroot directly
[08:48] <Saviq> SturmFlut, schroot --list will show you the available chroots (click-foo will be the one that QtC uses)
[08:49] <SturmFlut> Saviq: Excellent, thank you! I didn't even know the schroot command.
[13:14] <ViBE> hi there. could someone help me? i would like to install ubuntu touch on an arm v7 phone. is it possible?
[13:16] <SturmFlut> ViBE: Which model exactly? Is it listed on https://wiki.ubuntu.com/Touch/Devices ?
[13:17] <ViBE> not listed. it's a vodafone smart 4. it's a rebranded alcatel
[13:32] <SturmFlut> ViBE: If it runs Android and has an unlocked bootloader, it could be possible to run Ubuntu Touch. But I am not involved in any porting process
[13:33] <ViBE> fine. and how can I fully backup the phone before?
[13:41] <derek-g> should we expect Ubuntu touch phone in September?
[13:42] <derek-g> does anyone know?
[13:42] <cm-t> Hi, just a question about the lockscreen on #203/mako/devel : "No data sources available", but it is no my first use, I use to see my personnal data like photo, sms, water, call,…
[13:43] <cm-t> is it a know issue (I didnt find about this ecept when it's first useà or should I open a new bug ?
[13:43] <cm-t> s/useà/use)
[13:44] <cm-t> derek-g: I would sound logic it is after october (14.10), but at the moment team are working for a stable version as know as ubuntu-rtm/14.09 (I don't know more)
[13:45] <cm-t> it
[13:45] <cm-t> teams
[13:47] <derek-g> cm-t maan I just can't wait to get it
[13:48] <SturmFlut> derek-g: You can always get a Nexus 4 and just flash it
[13:49] <derek-g> Naah. I want the real deal like mx4.
[15:26] <cm-t> Hi, what is the best channel to talk about unity8-desktop-session ?
[15:41] <labsin> cm-t, ubuntu-devel?
[16:32] <Tassadar> dobey: okay, 215 is on tasemnice. It doesn't have delta update from 210 because...reasons
[16:33] <Tassadar> I've screwed up the tar file when patching it for hammerhead (I've changed paths from "system/*" to "./system/*", which works fine, until you encounter code which checks for .startswith("system/")
[16:34] <Tassadar> so I fixed that, and then I've encountered some other bug in s-i-server, so it took me quite some time to fix it
[16:35] <Tassadar> and the delta update doesn't exist because it tried to generate a file for the the "./system/*" -> "system/*" change, which didn't work out very well (the delta update borked the installed system actually)
[16:42] <dobey> Tassadar: oh, fun!
[16:44] <Tassadar> heh
[16:44] <Tassadar> auto-confirming PIN when user types 4 digits is not a good idea
[16:45] <Tassadar> because my pin has 5 digits
[16:45] <Tassadar> and it can have up to 8 I believe
[16:47] <Tassadar> and it wants the PIN even though no simcard is in ;__;
[16:48] <Tassadar> common, I just want to test if updating from 210 to 215 works :/
[16:52] <Tassadar> anybody knows which package is that PIN screen in? So I can report a bug
[16:56] <popey> unity8
[16:56] <Tassadar> oh, it doesn't work even with 4 digit pin, I guess it is known bug then)
[16:57] <popey> works here
[16:57] <popey> but this is a software pin, not a SIM pin
[16:57] <Tassadar> oh
[16:57] <Tassadar> yeah, that might be the "bug" :D
[18:09]  * saidinesh5 looks at Elleo
[18:23] <Elleo> saidinesh5: sorry, didn't have any time for maliit stuff last weekend, been a bit swamped
[18:24] <Elleo> and I'm disappearing off on holiday now, so won't get much chance to look at that sort of thing until after I get back and have caught up with work
[19:13] <cm-t> labsin: thanks
[19:43] <Elleo> popey: https://plus.google.com/106499911733230138554/posts/jp6xUJB1vUH
[19:44] <Elleo> popey: suffers a bit from programmer art syndrome though
[19:54] <popey> hah Elleo ☻
[21:40] <saidinesh5> Ah Elleo have fun with your holiday
[21:54] <philluminati> I have a nexus 5. I can see the details for it and it says "sound not working very well". Can anyone elaborate on what means and if it's still the case please?
[22:04] <popey> philluminati: Tassadar probably can answer that
[22:04] <Tassadar> the sound is working fine now I think, it was fixed by something I can't remember now
[22:05] <Tassadar> pulseaudio maybe?
[22:05] <philluminati> fantastic! Thank you!
[22:08] <Tassadar> however, the sleep doesn't work - the screen won't turn off
[22:08] <Tassadar> it just turns black, but the backlight is still on
[22:11] <philluminati> umm ok
[22:11] <philluminati> How close would you say you were to a stable version do you think?
[22:14] <Tassadar> Other than the backlight issue, it works as well as on nexus 4 as far as I know
[22:14] <Tassadar> I don't use it daily, so I don't know more
[22:14] <Tassadar> dobey : might tell you something more informative
[22:16] <philluminati> Thank you Tassadar. I think I'm going to try it regardless
[22:21] <dobey> philluminati: sound is working pretty great on my n5
[22:22] <dobey> it doesn't work as well as the nexus 4
[22:22] <dobey> gps doesn't work yet, but all the switches make it "appear" to work
[22:22] <dobey> there's no bluetooth
[22:22] <dobey> power management is not great
[22:23] <dobey> but call quality seems to be on par with n4
[22:23] <dobey> sometimes there is echo/lag for the other person though i think
[22:24] <dobey> but i'm using my n5 daily with ubuntu mostly just fine
[22:25] <dobey> and camera has an issue where images taken with flash are entirely white