[04:59] <alok_> Hello
[04:59] <alok_> I have few basic queries..
[04:59] <alok_> Please let me know the correct forum to ask these queries for ubuntu touch..
[05:00] <alok_> http://askubuntu.com/questions/511259/porting-ubuntu-touch-filesystem
[05:02] <tbr> daker: I answered a specific question. It works fine on PC...
[05:58] <botnut> hi all
[05:58] <botnut> im looking to get ubuntu touch set up on a tablet and possibly a phone
[05:58] <botnut> any recommendations on what hardware to use?
[05:58] <thelionroars> hi everyone
[05:58] <botnut> something that wont break the bank
[05:59] <thelionroars> my nexus 4 arrived today and the developer version went on straight away
[05:59] <thelionroars> wow... just wow
[05:59] <botnut> can you actually call with it and use it like a regular phone?
[05:59] <botnut> phone, text, sms, mms, email?
[06:00] <nhaines> botnut: for about a year now.  No email though.
[06:00] <thelionroars> I haven't tried yet, but it should be working since a few months ago
[06:00] <thelionroars> is the email app still under development?
[06:00] <nhaines> Actually, everything but mms has been working for over 18 months.
[06:00] <botnut> how about for a tablet?
[06:00] <botnut> which one should i go with for this?
[06:00] <nhaines> MMS has been sort of working (should be 100% now) for about three months.
[06:00] <thelionroars> nexus 7 2013
[06:00] <nhaines> thelionroars: the email app is not part of Ubuntu.
[06:01] <nhaines> botnut: I wouldn't go with a tablet at all until there's a retail one.  But Nexus 7 2013 is the only supported tablet.
[06:01] <botnut> nhaines - how stable is it on the phone and the tablet?
[06:02] <nhaines> No idea about the tablet.  The phone barely crashes, assuming you stick with only promoted builds.
[06:02] <botnut> yes
[06:02] <botnut> just want to go strictly ubuntu across everything i use
[06:03] <botnut> but ive been waiting to hear its stable on the phone and tablets
[06:03] <nhaines> Then I suggest waiting until you can walk into a store (or website) and buy one.
[06:03] <nhaines> Everything available now is for OS and app developers.
[06:04] <botnut> which i am both lol
[06:04] <botnut> but i also want it to work without me having to code something up
[06:04] <nhaines> Oh, well, that's been around for 15 months now.  :)
[06:05] <nhaines> You can also use the emulator on your computer.
[06:05] <botnut> nah thats not what i want
[06:05] <botnut> i use phones, tablets, workstations and laptops daily
[06:05] <botnut> laptops, workstations and servers i use are all linux based
[06:06] <botnut> would like to move my phone an tablet to that as well
[06:06] <botnut> and im not fond of the android based phones
[06:06] <nhaines> Well, it's stable but apps don't exist.
[06:06] <botnut> ahh dont care about apps
[06:07] <botnut> as long asi can do phone, text, mms, sms and basic email
[06:07] <nhaines> So if you load up the emulator and like what you see, you'll know whether or not to buy hardware.
[06:07] <thelionroars> tbh I was really starting to enjoy android, once I knew about f-droid
[06:07] <botnut> if i have to whip up an email client i will
[06:07] <nhaines> Well, like I said, there is no email.
[06:07] <thelionroars> but touch so far looks far superior
[06:07] <botnut> it has a browser though right?
[06:07] <thelionroars> will see how I go after a few days
[06:07] <nhaines> Yup.
[06:07] <botnut> which one?
[06:07] <nhaines> Ubuntu browser.
[06:08] <botnut> its "own" or some firefox or chromium derivative
[06:08] <nhaines> Which you can try in the emulator.
[06:08] <botnut> can i set it up in vm ware player or virtual box?
[06:08] <nhaines> (The Ubuntu 14.04 LTS version of Ubuntu Browser is less than impressive but doesn't reflect what's in the phone builds.)
[06:08] <nhaines> No, you can set it up using the Ubuntu SDK and the included emulator.
[06:09] <nhaines> http://developer.ubuntu.com/apps/sdk/tutorials/using-the-ubuntu-emulator/
[06:09] <botnut> hrmmm ill check that out actually
[06:09] <botnut> good idea
[06:10] <nhaines> If it had maps, working email, and Ingress (and the screen turned off on my phone) I *might* use it every day.
[06:10] <nhaines> Instead, it's dual-boot only for me now.  Although when it didn't destroy batteries I could leave it running Ubuntu over the weekends.  :)
[06:25] <mardy> sergiusens: ping (about untappd)
[06:26] <dholbach> good morning
[06:26] <nhaines> dholbach: moin moin!
[06:26] <dholbach> hi nhaines
[06:27] <nhaines> dholbach: I'm just installing r197 to see if it breaks anything since I tried r187.  :)
[06:29] <ecloud> is this a suitable channel for talking about touch architecture on desktop Ubuntu too?
[06:32] <nhaines> ecloud: I think so.  But it's still a bit early in the morning.
[06:32] <ecloud> yeah it is
[06:34] <nhaines> Well, it's 23:34 for me, but for the core developers, it's early.  :)
[08:10] <tbr> is it a known problem that the clock in the top right corner getts stuck at 00:00? (The clock app still shows the right time though)
[08:11] <ogra_> tbr, yeah, thats a new bug in the last ~8-10 images
[08:11] <tbr> ok
[08:16] <shuduo> hi guys, i found two apps i developed with simple webview of qml are broken in recent builds. i guess something changed for policy_group but i'm not sure it's by design or i should submit bug to lp. anyone can confirm?
[08:16] <ogra_> shuduo, webkit based ?
[08:18] <shuduo> ogra_: what i used is 'import Ubuntu.Components.Extras.Browser 0.1' and specify a url
[08:18] <shuduo> ogra_: here is my code: https://github.com/sangshuduo/doubanfmunofficial/blob/master/DoubanFMUnofficial/DoubanFMUnofficial.qml
[08:19] <pitti> ogra_: I'm on image 197 now (with wiped data, getting first-time wizard now), but adb shell is still root
[08:19] <ogra_> shuduo, right, 0.1 was the old webkit stuff ...
[08:19] <pitti> ogra_: that's an upgrade though, not a fresh install; does that make a difference?
[08:19] <ogra_> shuduo, there were probs with webkit based apps in the recent unreleased images
[08:19] <pitti> ogra_: (I was going to adjust autopkgtset for the new way of enabling ssh)
[08:19] <ogra_> pitti, yes, many moving parts there ... the switched adbd has not landed yet
[08:20] <shuduo> ogra_: what version i should use now? :)
[08:20] <ogra_> i need to make sure to neither regress the SDK nor CI nor the smoke tests
[08:20] <pitti> ogra_: ah, you said "as of image 189", so I thought this was active already
[08:21] <ogra_> shuduo, you shouldnt need to change a thing (as long as we have not dropped the old framework) .... it is a bug in the image that needs fixing
[08:21] <ogra_> pitti, i think you misunderstood me :)
[08:22] <pitti> ogra_: oh, you mean calling PropertyService landed, and that shoudl be used now
[08:22] <ogra_> pitti, as of image 189 you can manage sshd on/off via dbus ... so you dont need a sudo password ;)
[08:22] <pitti> ogra_: ack, thanks; sorry for the misunderstanding
[08:22] <ogra_> i need to land a bunch more of these things first
[08:22] <ogra_> then i can switch adbd
[08:23] <ogra_> shuduo, but if you want to port i think daker wrote a nice tutorial for the 0.2 browser stuff
[08:23] <ogra_> long term you will inded have to do that anyway
[08:23] <pitti> ogra_: so that'll enable ssh permanently, not just for the current run; but I guess we have to live with that
[08:23] <shuduo> ogra_: where i can find the nice tutorial?
[08:25] <shuduo> ogra_: i think i already found it. ;) thanks
[08:28] <ogra_> pitti, right ... phablet shell needs it (it disables it on disconnect though)
[08:29] <ogra_> shuduo, somewhere on http://daker.me/ i think :)
[08:30] <pitti> ogra_: ack, works fine; thanks!
[08:37] <shuduo> ogra_: yes
[08:39] <pitti> ogra_: I replied on the ML for the other problematic bits
[08:51] <nhaines> I noticed in the latest build, the power menu lost the restart option.  What package do I file a bug report against?
[08:58] <jibel> nhaines, unity8
[09:00] <ogra_> pitti, there will be dbus properties to put something like: http://paste.ubuntu.com/8078389/ in place
[09:01] <pitti> ogra_: hm, that easily allows circumventing all that protection, though
[09:01] <pitti> ogra_: create a package with a suid root bash, add-apt-repository it, call it, done
[09:01] <ogra_> which protection ?
[09:02] <ogra_> pitti, before you can do any of that you have to enable dev mode with a password
[09:02] <pitti> ogra_: not giving root privs to adb (to avoid tinkering with the device for random computers you plug it into)
[09:02] <ogra_> before you can access the device you will have to cofirm dev mode with the password
[09:02] <ogra_> you always have sudo ...
[09:03] <ogra_> and nothing stops you to call "passwd -d" after logging in and use sudo passwordless
[09:03] <pitti> ogra_: ah, so "sudo <anything>" with the "ubuntu" password won't go away?
[09:03] <ogra_> not the ubuntu password, no
[09:03] <ogra_> we already ship without password
[09:04] <ogra_> we will also ship with disabled adb by default (soon after all these bits landed) ....
[09:04] <ogra_> adbd wont start if there is no password set ... and you will need to set it to enable dev mode
[09:04] <pitti> ogra_: so what does --enable-developer-mode in ubuntu-device-flash do there?
[09:05] <ogra_> it will toggle the switch
[09:05] <ogra_> but it will soon be bound to a --password option ;)
[09:05] <ogra_> for automated testing we'll need that
[09:06] <ogra_> btw, answered your mail
[09:06] <pitti> yeah, automated testing does not quite fit what a "developer" would want to do; we probably want an --enable-testing-mode for that
[09:07] <ogra_> well, even developers would want to flash with enabled dev mode ...
[09:08] <ogra_> imagine your  icecc build farm that you want to flash daily with the latest image before building :)
[09:08] <ogra_> you dont want that with a ton of autopilot bits enabled ... but just in a normal dev more
[09:10] <pitti> ogra_: right, we don't want to ship autopilot (or enable the apparmor profiles for that) by default; maybe for developers, but that should all be hidden/done by phablet-test-run or adt-run
[09:10] <ogra_> which just calls phablet-config ...
[09:11] <ogra_> and for the bits in phablet-config i cant shield better there are the sudo snippets
[09:11] <volpe> Is this the place to ask for help on getting ubuntu-touch running on a Nexus 10 (I’m stuck in a boot loop) :\
[09:11] <ogra_> (namely the package install bits and the aa-clickhook calls)
[09:12] <nhaines> jibel: thanks!
[09:12] <pitti> ogra_: yeah, I mostly use these; the things that adt-run does on its own are powerd-cli (but that seems to work as phablet), the factory reset, and saving/restoring wifi connectinos
[09:13] <ogra_> pitti, http://people.canonical.com/~ogra/ubuntu-touch/android-tools-adbd_4.2.2+git20130218-3ubuntu24_armhf.deb in case you want to try out the adbd with phablet default
[09:14] <ogra_> i plan to land the last proprty service bits today ...
[09:14] <pitti> ogra_: ah, that's useful, thanks
[09:14] <ogra_> and the phablet-tools changes during the rest of the week
[09:15] <JamesTait> Good morning all; happy Monday and happy Bad Poetry Day! :-D
[09:20] <volpe> Am I right in assuming that if ubuntu installs correctly you don’t get the Normal (4 colour squares) google bootup sequence?
[09:21] <volpe> squares = circles*
[09:21] <nhaines> volpe: typically you just get the Google logo until you get the Ubuntu bootsplash (currently a rotating Ubuntu logo, although I've been told this is not final.).
[09:22] <volpe> nhaines: right, thanks.  I’ve done something wrong then. :\
[09:23] <volpe> volpato1
[09:27] <mpt> “Mon 18, Aug”
[09:27] <mpt> — the Clock app
[09:28] <volpato1> So after doing a: ubuntu-device-flash --wipe --channel=devel --bootstrap — from recovery, I reboot into recovery mode (ubuntu logo in the middle) then reboot with a ubuntu logo spinning (for a bout a minute) then reboot again with the google boot sequence.  (Nexus 10, manta) — Don’t suppose anyone knows any obivous solutions?
[09:28] <nhaines> volpato1: try reflashing from recovery.
[09:30] <volpato1> nhaines: Recovery is the Android fallen over screen or the screen with wipe cache, factory reset options?
[09:32] <nhaines> volpato1: it's the Android with the access patch open.  :)
[09:32] <nhaines> This is actually "Fastboot Mode".
[09:33] <volpato1> nhaines: I’ve tried that multiple times (with —channel=devel, stable, trusty) same result.  Is bootstrap significant?
[09:33] <nhaines> Yes, it's required.
[09:33] <volpato1> tried that each time as well - just wondered if I should try without.
[09:34] <nhaines> Only when it's already working.
[09:34] <nhaines> What device are you running?
[09:34] <nhaines> Oh, there it is... Manta.
[09:34] <volpato1> Yeah manta.
[09:36] <nhaines> volpato1: I did some brief research, but I don't have any further suggestions, sorry.
[09:36] <volpato1> thanks anyway - I’ll keep messing about :)
[09:40] <nhaines> Good luck.  :)
[09:51] <nhaines> Saviq: I shake my fist at your design decision!
[09:51] <Rienzilla> :-)
[09:52] <Saviq> nhaines, no but really, why would you reboot your phone?
[09:52] <nhaines> Saviq: because Ubuntu doesn't have any power management and I have to boot back into Android to get battery life over an hour (or get anything useful done).
[09:53] <Saviq> nhaines, the reboot dialog doesn't fix that does it
[09:53] <nhaines> (On Android, it's because sometimes Android L breaks everything, but for Android 4.4.3 it wasn't too bad.)
[09:53] <nhaines> Saviq: it fixes that I can reboot my phone.
[09:53] <nhaines> So there's that.
[09:54] <nhaines> On Ubuntu, rebooting is less useful, although every so often apps or updates completely break, and then I need to reboot.
[09:54] <nhaines> Noteably if one webapp breaks, that's usually the end of webapps for the rest of the session, although I have noticed that occasionally other apps refuse to start, and then I can't use them until my next boot.
[09:54] <Saviq> nhaines, that's not a "real life" situation, let's just fix the power management (which btw I don't know of a bug about, people have been using their Ubuntu phones daily and I don't know of any particular battery draining problem (although we obviously need to improve, but it's not *tragic*)
[09:55] <Saviq> nhaines, but adding a reboot button really does not help that situation which needs to be fixed regardless
[09:55] <Saviq> nhaines, on Ubuntu *desktop* the only real reason to reboot is upgrades, which on phone happen with a forced reboot anyway
[09:55] <nhaines> A 10% drop in battery charge every 10 minutes is hardware damaging, since it stresses the (non-replaceable) battery in my phone.
[09:56] <Saviq> nhaines, is there a bug about this?
[09:56] <nhaines> Nope, it would be wontfix.
[09:56] <nhaines> Although there might be one anyway.
[09:56] <nhaines> And I reboot my computer all the time to test an Ubuntu live CD or run Windows.
[09:57] <Saviq> nhaines, why would a 10% drop in 10 minutes be a wontfix?
[09:57] <nhaines> What's going to end up happening is I'm going to stop testing Ubuntu because it's damaging my phone and it's a hassle to get back to Android when I'm done.
[09:58] <Saviq> nhaines, again, understand that's not real-life situations
[09:58] <nhaines> Saviq: no idea.  Hammerhead was supposed to be a new supported target starting around June, but now Canonical claims they've never seen their own spreadsheets.
[09:58] <nhaines> Saviq: I do it constantly.
[09:59] <Saviq> nhaines, I don't mean to be blunt, but we're not doing the phone for *you* but for the general user
[09:59] <nhaines> Unfortunately I was on vacation when the change happened, so I couldn't try to bisect the power management problems.
[09:59] <Saviq> nhaines, who does not switch between Ubuntu and Windows, or test Ubuntu live CDs
[09:59] <nhaines> Well here's a real world problem.  Every time I change a setting with my graphics card, I have to reboot before the change takes effect.
[10:00] <Saviq> nhaines, bug#?
[10:00] <nhaines> And I promise you there's not a single person who dual-boots who doesn't switch OSes occasionally.
[10:00] <nhaines> Saviq: no bug.  I presume it's the intended behavior of Linux kernel modules.
[10:00] <Saviq> nhaines, and you consider dual-booting a phone a common use case?
[10:01] <Saviq> nhaines, presumptions like that gets your bug not looked at
[10:01] <nhaines> Saviq: no, but I consider broken apps refusing to launch a reasonable scenario.
[10:01] <mpt> Which project/package is responsible for the “wants to access your current location” prompts? Is it trust-store?
[10:02] <Saviq> nhaines, sure, that needs to be fixed on the platform, rebooting shouldn't be necessary
[10:03] <nhaines> Okay, but I don't have much confidence that it will be.
[10:03] <Saviq> mpt, location-service I believe
[10:03] <Saviq> nhaines, you know that logic is flawed?
[10:04] <nhaines> Saviq: please explain.
[10:04] <Saviq> nhaines, if you not file a bug because you "don't have confidence" in it being looked at
[10:04] <Saviq> nhaines, and then complaining about that bug not being looked at...
[10:05] <nhaines> I haven't filed a bug because I haven't ben able to identify non-random conditions under which it is reproducible.
[10:05] <mpt> thanks Saviq
[10:06] <Saviq> nhaines, unless you're the only person that's affected by this, which is unlikely, maybe others have ideas, workarounds, anything
[10:08] <nhaines> Saviq: possibly, but a lot of bugs are neglected, and with nothing solid to present and very little time to troubleshoot because Ubuntu is harmful to my phone and now even more difficult to work with, I'm not comfortable presenting nebulous bugs with no information to go on.
[10:08] <nhaines> There are surely enough nonsense whining bugs on LP as it is.
[10:09] <popey> nhaines: we never said hammerhead was a target
[10:09] <nhaines> popey: yes you did.
[10:09] <popey> people speculated
[10:10] <popey> [citation needed]
[10:10] <nhaines> popey: it was in your roadmap in February.
[10:10] <nhaines> Google Docs doesn't let itself to citations.
[10:10] <Saviq> nhaines, we've drifted away from the original point though, I still don't think your usecase warrants a reboot button in the dialog
[10:11] <Saviq> nhaines, if you could state your case on the bug, I'll get our UX designers to look at it
[10:11] <nhaines> Saviq: that's as fair as I can ask, although less than I hoped for.
[10:14] <Saviq> nhaines, we all (me as well, most of the Canonical developers) have to understand we're not the main targets for the phone
[10:14] <Saviq> nhaines, and live with some design decisions that improve usability for the majority
[10:14] <nhaines> Saviq: I'm 100% for that.  But I don't think that the option to reboot a phone is unreasonable.  Especially with a system that isn't very stable.
[10:15] <nhaines> (If everything were very stable, that might be a different scenario.)
[10:15] <Saviq> nhaines, again, let's not fix instabilities by adding temporary reboot buttons
[10:15] <Saviq> nhaines, let's instead fix the instabilities
[10:15] <Saviq> nhaines, fortunately it's all open source, there's nothing stopping you from rolling nhaines's version of the phone that adds the reboot button
[10:16] <nhaines> Saviq: I think it's irresponsible to take out such options before the instabilities are fixed.
[10:17] <nhaines> And as a Python programmer, yes, I'm prevented from rollling my own version of the phone.
[10:18] <nhaines> But I'm not stomping my feet because my favorite feature was removed and I'm special.
[10:18] <nhaines> Actually, that's why I don't file bugs that I can't reproduce, either.
[10:18] <Saviq> nhaines, I don't think being a Python programmer prevents you from anything
[10:19] <Saviq> I definitely hope not
[10:19] <nhaines> Saviq: Unity8 is C++ if I understand correctly.  That prevents me from contributing or forking.
[10:19] <nhaines> (This is not a failure of Unity 8)
[10:21] <nhaines> Although I would suggest it's not a failure of me, either.  :P
[10:21] <Saviq> nhaines, there's actually much more QML code than C++
[10:22] <Saviq> nhaines, I don't think a project being in *any* language or a person knowing *any* language (or not knowing one, for that matter) can be considered a fault
[10:22] <nhaines> Saviq: well then we agree on that.
[10:25] <mpt> Ohhh, I love how the icons rotate inside the Camera app’s buttons
[10:25] <mpt> That’s classy
[10:27] <nhaines> Looks like I'll reboot my phone again (hypotheticaly twice but actually only once since Ubuntu doesn't allow it) to check that out.
[10:29] <ogra_> mpt, hmm, is the missing reboot button in the shutdown dialog wanted ?
[10:29] <popey> ogra_: see previous 3 hours of conversation here
[10:29]  * ogra_ had annoying moments on the weekend trying to get hos phone rebooted 
[10:29] <ogra_> oh
[10:29] <ogra_> sorry,, i didnt read that :P
[10:29]  * ogra_ does so 
[10:29] <popey> nhaines: looked through all plans, no mention of hammerhead
[10:30] <popey> i think we speculated about it repeatedly
[10:30] <popey> but never committed to actually porting to it, which is why there's only like 3 of them in the company
[10:30] <nhaines> mpt: a little jerky but a very nice touch!
[10:30] <popey> if we'd committed we'd have bought a _lot_ of them
[10:30] <nhaines> popey: It was mentioned in a roadmap, since Nexus 4s haven't been made for two years.
[10:31] <popey> mentioned != commitment
[10:31] <popey> as I said.
[10:31] <daker> shuduo: http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Web.WebView/
[10:31] <popey> earlier in the year there were many conversations about "what do we do after nexus 4" and a few options were mooted, no commitment is my point
[10:32] <nhaines> I've always presumed that once retail phones it, all developer builds are going to be deprecated very, very quickly.
[10:33] <nhaines> I can't seem to find the right emails, and it's no longer in my Google Drive (which probably means it was replaced or deleted) but the roadmap I saw was very clear that it was, at one time, planned.
[10:33] <nhaines> Not that plans don't (or shouldn't!) change, but it's surely annoying to have people say hammerhead was never mentioned.
[10:34] <tbr> hmm, interesting, it seems like ubuntu touch for some reason changes its IPv4 address very often in combination with my local DHCP server
[10:34] <nhaines> My actual anger is directed at HUD being abandoned.
[10:34]  * tbr suspects a bug but doesn't have the time to investigate it further
[10:35] <popey> nhaines: i didnt say it was never mentioned!
[10:35] <popey> nhaines: I specifically said it was discussed but not a commitment
[10:35] <popey> wait, what? we've gone from reboots to hammerhead to hud..
[10:36] <nhaines> reboots and hammerhead are mere annoyances.  HUD is a betrayal.  :P
[10:36] <nhaines> Or at least really disappointing.
[10:37] <Saviq> nhaines, it will be back, when we get time to redesign it proper
[10:37] <nhaines> Saviq: that will be nice to see.
[10:38] <nhaines> Mostly people were getting an answer more like "there are no plans to work on it in the future."  Which is annoying.
[10:38]  * ogra_ finds reboots annnoying enough that we should leave the button in place til final landing of unity8 
[10:39] <ogra_> it eats my time to try to get out of the battery animation for 5mins ... really not development friendly
[10:39] <popey> yesterday I made a script which takes screenshots on the device.. works quite well, even if I did have to build all of imagemagick to do it
[10:39] <nhaines> Saviq, popey: trust me, if I had any proficiency at hardware programming, I'd be harassing with patches instead of opinions.  :)
[10:39] <ogra_> popey, try to use gstreamer ;)
[10:39]  * ogra_ was playingwith that a bit but other stuff got in my way
[10:39] <popey> this works, i need to wrap it in a qml app
[10:39] <popey> along with 76MB of libs ⍨
[10:40] <ogra_> right, but you need to ship a static imagemagick
[10:40] <popey> could probably trim that down ☻
[10:40] <popey> yes
[10:40] <ogra_> gstreamer is already there
[10:40] <popey> plus a load of other libs
[10:40] <ogra_> and ships a pngsrc and pngenc sink
[10:40] <popey> can gstreamer convert rgbas to pngs?
[10:40] <popey> hmm
[10:40] <popey> will have a play with that later, thanks
[10:41] <popey> problem then is the app wont be able to put the pictures in ~/Pictures where I'd want to
[10:41] <ogra_> i was trying that for capturing videos though ... but stills shouldnt be much different
[10:42] <Laney> gst-launch-1.0 ximagesrc remote=1 num-buffers=1 \! videoconvert \! pngenc \! filesink location=blah.png
[10:42] <Laney> or something
[10:42]  * popey hugs Laney 
[10:43] <ogra_> Laney, wont work with Mir i fear
[10:43] <Saviq> ogra_, I assume you're getting the battery animation because your phone is connected to your laptop? adb reboot not working for you? :P
[10:43] <ogra_> or does ximagesink read from /dev/fb0
[10:43] <Laney> dunno
[10:43] <ogra_> gst-launch-1.0 filesrc location=image.raw ! videoconvert ! pngenc ! filesink location=screenshot.png
[10:43] <ogra_> that migh work though
[10:43] <Laney> what is image.raw?
[10:43] <ogra_> captured by mirscreencast
[10:44] <ogra_> raw rgba data
[10:45] <ogra_> we dont shil gst-lauch though ... you need to actually have a C++ wrapper or some such
[10:45] <ogra_> *ship
[10:45] <popey> yeah, gstreamer1.0-tools isn't installed ☹
[10:46] <Laney> yo uwouldn't actually use that
[10:46] <Laney> but construct the pipeline in code
[10:46] <ogra_> well, you can test the pipe on the desktop
[10:46] <popey> this should of course be baked into mir/unity
[10:46] <ogra_> just grab the raw mirscreencast image from the phone and fiddle with it until you got the right runes
[10:50] <popey> yeah, thats what I did for imagemagick
[10:52] <Laney> you could write a mirimagesrc :-)
[10:58] <ogra_> yes, long term that is what we need
[11:00] <sergiusens> mardy pong
[11:04] <mardy> sergiusens: I suggest you to start from the facebook account plugin, which you can find in lp:account-plugins
[11:04] <mardy> sergiusens: the first steo is to create the .provider file, and see that you can create the account on the desktop
[11:05] <mardy> sergiusens: after that is successful, you can continue by adding a QML plugin for Ubuntu Touch, which would get the username
[11:14] <thelionroars> wifi/usb tethering is not implemented yet?
[11:15] <popey> thelionroars: https://lists.launchpad.net/ubuntu-phone/msg09388.html
[11:17] <thelionroars> ta
[11:17] <ogra_> please file bugs (against dbus-property-service) if you see any issues
[11:18] <thelionroars> thanks, will do
[11:31] <sergiusens> mardy: I'll pick it up later today as it is not work related :-) But I did setup a service-type, service and provider; I used the facebook one as a template and when clicking on the account to enable it (on my trusty desktop) I get an error back saying that the request is missing the client id
[11:31] <sergiusens> mardy: I'll write something more elaborate with pastebins and such closer to my eod
[11:32] <sergiusens> want to land something before the possible traincon 0 I heard might happen today
[11:32] <sergiusens> thanks!
[11:32] <mardy> sergiusens: OK :-)
[11:46] <nik90> jhodapp: ping (unable to play sounds in the clock app)
[11:49] <nik90> t1mp: ping
[11:57] <t1mp> nik90: hello
[11:57] <nik90> t1mp: Hi,
[11:58] <nik90> t1mp: I am using a ListItem.Standard with a control element (checkbox). Since I need to change the color of the text, I use a Label{}. However I am unable to anchor this label to the checkbox to avoid text elide etc.
[11:58] <nik90> t1mp: it says cannot anchor to something which is not parent.
[11:58] <nik90> t1mp: how may I fix this?
[12:00] <t1mp> nik90: you can make the Label anchors.fill: parent maybe?
[12:00] <t1mp> to anchor it to the checkbox you'd need to use a ListItem.Empty and add both the Label and the CheckBox there :(
[12:00] <nik90> hmm :/
[12:01] <nik90> we were using ListItem.Empty before, but the issue with that is that we need to add onClicked signals to both the checkbox and the listitem which is counterintuitive.
[12:01] <t1mp> nik90: we'll have new list items coming up, but not this week
[12:01] <jhodapp> nik90, pong
[12:01] <nik90> t1mp: for now this is okay.
[12:01] <t1mp> hmm
[12:02] <t1mp> zsombi: did you have a look at adding a foreground/text color to the old list items?
[12:02] <nik90> jhodapp: hi, I have a branch which plays a ringtone. it works on the desktop but not on the phone. let me grab the MR link for you
[12:02] <jhodapp> nik90, of the clock app?
[12:02] <nik90> jhodapp: https://code.launchpad.net/~nik90/ubuntu-clock-app/play-sound-preview/+merge/230959
[12:02] <nik90> jhodapp: yes
[12:02] <zsombi> t1mp: no, not this time...
[12:03] <nik90> jhodapp: at first I thought it was an apparmor issue which it was. But jdstrand fixed that apparmor issue and still I don't hear the sound being played by the clock on the phone
[12:03] <zsombi> t1mp: but if someone does, should use the ColorUtils.luminance() to check the theme's background color
[12:03] <jhodapp> nik90, yeah I have a pretty good guess of what it is, one sec
[12:03] <nik90> jhodapp: yay :)
[12:03] <sergiusens> nik90: is the tone in part of the clock apps directory space
[12:04] <sergiusens> jhodapp: might be the same issue we had with paths?
[12:04] <jhodapp> sergiusens, exactly
[12:04] <nik90> sergiusens: directory space? as in does clock have permission to read that folder?
[12:05] <nik90> jhodapp, sergiusens: Btw the ringtones i am playing are in /usr/share/sounds/ubuntu/ringtones
[12:05] <jhodapp> nik90, no, as in media-hub won't play that sound for clock-app because of permission policy within media-hub
[12:05] <nik90> jhodapp: but wasn't it fixed in https://bugs.launchpad.net/media-hub/+bug/1357348
[12:05] <jhodapp> nik90, yep, I can almost guarantee that's the issue now...technically an app is only allowed to play something from its own click *home dir*
[12:06] <nik90> jhodapp: so how do I fix that in the clock app?
[12:06] <sergiusens> nik90: click pkgdir com.ubuntu.clock that is
[12:07] <nik90> sergiusens: ah no we don't ship that folder with the clock app
[12:08] <jhodapp> nik90, you can check what's going on with media-hub by tailing the log while it tries to play that sound: "tail -f /home/phablet/.cache/upstart/media-hub.log"
[12:09]  * nik90 checks that now
[12:09] <jhodapp> you should see a line like "client pkgname: com.ubuntu.music
[12:09] <jhodapp> uri: file:///home/phablet/Music/01 - Gobbledigook.mp3
[12:09] <jhodapp> Client can access content in ~/Music or ~/Videos""
[12:09] <jhodapp> nik90, but it should say client not allow access...
[12:10] <nik90> jhodapp: yup http://paste.ubuntu.com/8079472/
[12:11] <nik90> jhodapp: so what would you advice me to do? Ship that folder internally with the clock app?
[12:11] <jhodapp> nik90, so please ping jdstrand about this and if he is ok with adding another app exception to the media-hub policy
[12:11] <nik90> jhodapp: ah ok
[12:12] <nik90> jdstrand: ping
[12:12] <jhodapp> nik90, he probably won't be online yet...he's on central US time
[12:13] <nik90> jhodapp: ack. I will check with him later
[12:58] <jdstrand> jhodapp: rather than adding an app exception, can we jus say that all apps who can contact the media-hub can access /usr/share/sounds?
[12:58] <jhodapp> jdstrand, yep, was thinking that'd be the solution as well, but wanted to make sure you're ok with that
[12:59] <jdstrand> jhodapp: this is yet more policy in the media-hub, but remember, that will go away once tha apparmor query interface allows media-hub to query an app's access to files
[12:59] <jdstrand> jhodapp: I'm ok with that
[12:59] <jhodapp> jdstrand, awesome...will that query be answered from the trust store?
[13:01] <jdstrand> jhodapp: no, this is for playback, so the truststore wouldn't be involved
[13:01] <jdstrand> jhodapp: but we'll cross that bridge when we come to it
[13:01] <jdstrand> jhodapp: the audio policy group already has:
[13:02] <jdstrand> /usr/share/sounds/** r,
[13:02] <jdstrand> /custom/usr/share/sounds/** r,
[13:02] <jhodapp> jdstrand, ok, but I'm just curious what is adding that functionality...what needs to be implemented and where?
[13:02] <jdstrand> jhodapp: so apps are intended to have playback access to those
[13:03] <jdstrand> jhodapp: basically you big if/else statement turns into: if (app_can_read_file(fn)) { ... } else { EPERM }
[13:03] <jdstrand> the tust-store bit is separate
[13:04] <jhodapp> jdstrand, right, but what's implementing the app_can_read_file(fn) function call?
[13:04] <jdstrand> jhodapp: the libapparmor API
[13:04] <jdstrand> jhodapp: the query interface
[13:04] <jhodapp> jdstrand, ok...who's working on that and any idea of what the timeline might be?
[13:04] <jdstrand> so, it would be more like 'app_can_read_file(pid, file)' or something
[13:05] <jdstrand> jhodapp: jjohansen/tyhicks. not for rtm, possibel for 14.10. I don't know what the actual api will look like
[13:05] <nerochiaro> kenvandine: hi, do you happen to know how can i give my app permission to read pictures from ~/Pictures/camera ?
[13:05] <jhodapp> jdstrand, ok awesome, thanks for the info
[13:07] <kenvandine> nerochiaro, you don't
[13:07] <kenvandine> that's what content-hub is for :)
[13:08] <nik90> jdstrand, jhodapp: Should I create a separate bug report for the above?
[13:08] <nerochiaro> kenvandine: ok, so if I put an Image { source: "foo.jpg" } in my QML app, where does it look for foo.jpg on the file system ?
[13:08] <jhodapp> nik90, sure, assign it to media-hub
[13:08] <kenvandine> current dir
[13:08] <jjohansen> jdstrand, jhodapp: /me and tyhicks are working on the query interface, it is largely done, the kernel interface is fully updated there is a little more to do in the library and there needs to be testing and regression tests written.
[13:08] <jhodapp> nik90, and assign me as well
[13:08] <nerochiaro> kenvandine: i'm just doing some quick testing and i need a simple app to load a random image
[13:08] <kenvandine> or rather relative to the app
[13:08] <jhodapp> jjohansen, nice...do you expect to land it for rtm then?
[13:09] <nik90> jhodapp: I don't think I have permission to assign you. I will ping you with the bug number
[13:09] <jhodapp> nik90, ok thanks
[13:09] <jjohansen> jhodapp: as jdstrand said not for rtm (even if it did there wouldn't be enough time to use it), there are other things being worked on for that atm. It should land for 14.10
[13:10] <jhodapp> jjohansen, alright, awesome
[13:11] <cwayne> jdstrand, ping
[13:11] <jdstrand> cwayne: hey
[13:11] <jhodapp> jjohansen, let me know if you want to use media-hub as an early test of it...I'd be happy to make it be a beta tester :)
[13:12] <jjohansen> jhodapp: of course we want to use naive victims^W^Wbeta testers :)
[13:12] <jhodapp> lol
[13:12] <jhodapp> jjohansen, count me in ;)
[13:12] <cwayne> jdstrand, err actually de-ping for now, sorry :)
[13:14] <jdstrand> cwayne: did you find that bug? to unblock your work, you could add policy to your /var/lib/apparmor/profiles/click_*flickr* file for the path the scopes api is currently giving the app
[13:14] <nerochiaro> kenvandine: just out of curiosity, where is any random app allowed to save its own data ?
[13:14] <nik90> jhodapp: Bug 1358278
[13:14] <jhodapp> nik90, thanks
[13:14] <nik90> jhodapp: yw
[13:15] <jdstrand> pete-woods|lunch: hi! what is the bug number for the scopes api incorrectly adding appname to the path? cwayne wants it, and I'd like to add the 'application-confinement' tag (so I can find it :)
[13:15] <kenvandine> nerochiaro, to it's datadir
[13:15] <kenvandine> or cachedir
[13:15] <kenvandine> ~/.local/share/APP_ID/
[13:15] <nerochiaro> kenvandine: and where would they be ?
[13:15] <jhodapp> nik90, I'll hopefully add that quickly sometime later today
[13:15] <kenvandine> or ~/.cache/APP_ID/
[13:15] <nik90> jhodapp: thnx a lot :-)
[13:15] <jhodapp> np
[13:18] <shuduo> daker: got it. thanks
[13:22] <Chipaca> charles: ping
[13:24] <derek-g> so. RTM get's released soon? nice...
[13:25] <derek-g> so -you can say - things are getting pretty serious.
[13:27] <davmor2> nik90: and this is a clock app you wanted to land today right? ;)
[13:28] <popey> davmor2: shush you
[13:29] <davmor2> popey: I'm just pointing out it's just as well we broke the image for him to have the extra dev time ;)
[13:29] <nik90> davmor2: go away...you are taking away my optimism :P
[13:30] <davmor2> nik90: hahaha,   ah come on dude the clock reboot rocks :)
[13:30] <davmor2> nik90: was that more supportive of your optimism :)
[13:31] <nik90> davmor2: lol :D yes
[13:37] <Chipaca> seb128: please keep me posted about the icons thing, as there are two other branches in two other projects that were writ to enable notifications to use the symbolic icon for those apps
[13:38] <seb128> Chipaca, the warnings issue you mean?
[13:38] <Chipaca> seb128: the symbolic icon thing i mean, https://code.launchpad.net/~chipaca/webapps-core/theme-icons/+merge/230968
[13:38] <Chipaca> oh
[13:38] <Chipaca> seb128: wrong person :)
[13:38] <seb128> Chipaca, k, I was wondering what you were talking about there ;-)
[13:38] <Chipaca> dbarth: please keep me posted about the symbolic icons thing, as there are two other branches in two other projects that were writ to enable notifications to use the symbolic icon for those apps
[13:43] <kenvandine> does anyone know if phonesim supports lockPin in SimManager?
[13:46] <kenvandine> i'm getting operation failed errors when trying it in phonesim
[13:46] <dbarth> Chipaca: yes
[13:46] <kenvandine> but that could be my code :)
[13:47] <dbarth> Chipaca: waiting for matthieu to reply
[13:50] <pete-woods> jdstrand: I don't know. could you raise a bug against unity-scopes-api with the output?
[13:57] <felipealmeida> hello
[13:57] <felipealmeida> how do I create a rootfs for ubuntu touch?
[14:01] <felipealmeida> from scratch
[14:06] <ogra_> felipealmeida, have a look at project-rootstock-ng
[14:07] <felipealmeida> ogra_: doesn't that just flashes a prebuilt rootfs?
[14:07] <ogra_> felipealmeida, bzr branch lp:project-roostock-ng ... it had a scritp to build a rootfs from the ubuntu archive like we do in production
[14:07] <jdstrand> pete-woods: oh, I thought I saw you did that already
[14:07] <ogra_> (welll at least pretty close to that)
[14:08] <felipealmeida> I would like to build the projects, not just the rootfs from prebuilt debs
[14:08] <pete-woods> jdstrand: oh, I thought that was just the actual scope trying to create something it wasn't allowed to create (it's the job of an unconfined process)
[14:08] <ogra_> felipealmeida, there is also rootstock-touch-install, yeah ... but was referring to the other script in that tree
[14:08] <felipealmeida> is there any tool to do that?
[14:08] <anradan> Hello everyone
[14:08] <jdstrand> pete-woods, cwayne: here it is: https://bugs.launchpad.net/unity-scopes-api/+bug/1356409
[14:09] <jdstrand> pete-woods: no, the unconfined check was silenced already
[14:09]  * jdstrand adds tag
[14:10] <felipealmeida> ogra_: btw, is there any serial tty in nexus 4?
[14:10] <pete-woods> jdstrand: can you paste me a link to exactly which error you mean?
[14:10] <jdstrand> pete-woods: ? that bug you filed is very clear
[14:10] <ogra_> felipealmeida, there are hhardware hacks out somewher on the internet to get one enabled afaik
[14:10] <ogra_> (i never needed one9
[14:10] <jdstrand> (1356409)
[14:10] <ogra_> )
[14:10] <felipealmeida> ogra_: how do you debug?
[14:11] <pete-woods> jdstrand: okay. so it's the "cache" path we're talking about?
[14:11] <ogra_> felipealmeida, i rarely have to debug pre-boot stuff ... from initrd on i have adb
[14:11] <pete-woods> jdstrand: sorry. my brain farted when reading your earlier comment. I read version number, instead of appname
[14:11] <felipealmeida> I see, that's exactly what I wanted to debug :)
[14:12] <jdstrand> pete-woods: I'm not sure what you call it in the scopes-api, but it is XDG_DATA_HOME by the xdg spec ($HOME/.local/share/...)
[14:13] <jdstrand> pete-woods: ah, ok. I think we are on the same page now then?
[14:13] <anradan> Sony Xperia Z rooted locked boot loader no recovery I....possible to dual boot Ubuntu and  Android?
[14:13] <pete-woods> jdstrand: yeah. was just being stupid
[14:13] <jdstrand> heh
[14:13] <pete-woods> jdstrand: that bug is on my radar. either me or michi will fix it soon
[14:13] <jdstrand> ack, thanks
[14:14] <jdstrand> I don't know if it is the cause of cwayne's issues, but he is seeing the denial with his scope
[14:14] <jdstrand> cwayne may contact you about that
[14:14] <cwayne> yepyep
[14:16] <jdstrand> cwayne: if you need me to help you with temporarily adding the rule that works around that bug to unblock you, let me know
[14:16] <cwayne> jdstrand, will do, thanks man
[14:17] <jdstrand> np
[14:51] <felipealmeida> hello, I'm having errors with crc32 on project-rootstock-install, any ideas?
[14:51] <felipealmeida> adding android system image to installation ... computed crc32 of 0xa901ce14, expected 0x00000000
[15:48] <jibel> Saviq, I added a test case to bug 1295623 . Symptoms are the same but the test case it  specific to u-s-s.
[15:48] <jibel> s/it/is
[15:54] <dholbach> if you're interested in a discussion about ubuntu app frameworks, we are going to have a hangout in 5m on http://ubuntuonair.com
[15:54] <dholbach> let mhall119 or myself know if you want to join in
[15:56]  * ogra_ is only interested in getting rid of them :P
[15:57] <cwayne> mardy, ping
[15:59] <dholbach> jdstrand, were you interested in the frameworks discussion as well?
[16:02] <Saviq> jibel, unfortunately that's bug #1355263
[16:02] <jibel> Saviq, too bad. I'll continue searching.
[16:03] <Saviq> jibel, thanks
[16:09] <cwayne> mardy, was there ever a silo for that suspected oxide crash when adding an account?
[16:09] <jdstrand> dholbach: I'm interested, but I don't need to drive it
[16:10] <jdstrand> dholbach: more general interest and awareness for click-apparmor and click-reviewers-tools
[16:10] <dholbach> jdstrand, ok
[16:11] <dholbach> jdstrand, we're having the discussion right now, and on the agenda are: 1) where to store info about frameworks, 2) having an API feature changelog, 3) implementing an API scraping tool (for multiple purposes)
[16:12] <jdstrand> yeah, I don't need to be there for that
[16:12] <dholbach> ok cool
[16:12] <jdstrand> for '1' we just need to adjust the url in the click-reviewers-tools
[16:12] <jdstrand> dholbach: ^
[16:12] <dholbach> yep
[16:12] <jdstrand> and that is obviously pretty easy :)
[16:13] <jdstrand> dholbach: it might be good to also store the apparmor json and the upcoming platform-api json in the same place (ie, the equivalent of the frameworks file for apparmor and platform-api)
[16:13] <jdstrand> cause the apparmor one is currently temporary as well
[16:14] <jdstrand> interestingly, it points at the click-reviewers-tools branch
[16:14] <jdstrand> which is fun to think about from a dog chasing its tail point of view :)
[16:14] <dholbach> haha :)
[16:15] <jdstrand> but I don't care where this stuff is store so long as it is documented and easy to update
[16:15] <felipealmeida> simg2img is giving me error of crc
[16:16] <felipealmeida> he expects crc 0
[17:23] <Blueskyder> hi
[17:26] <dobey> hi
[17:31] <Blueskyder> ng.
[17:32] <Blueskyder> .....
[17:42] <john-mcaleely> if I want to find out how long an ubuntu handset will run, is there already a test I could look at?
[17:42] <john-mcaleely> ie, run test, get handset battery duration in hours?
[17:45] <nik90> john-mcaleely: I can't think of any test.
[17:45] <nik90> john-mcaleely: I see some tests in http://ci.ubuntu.com/bootspeed/arch/mako/ which tests the bootspeed of every image released
[17:46] <john-mcaleely> thanks nik90
[17:46] <nik90> john-mcaleely: there is also memory results in that link
[17:46] <nik90> john-mcaleely: yw
[17:47] <john-mcaleely> nik90, I will take a look
[17:48] <dobey> you could run the test that just keeps constantly swiping and tapping on things randomly, on a device, and time it
[17:48] <dobey> problem is you can't test how long the battery is alive, programmatically
[17:48] <john-mcaleely> I think I'm more interested in a 'maxium duration' type test, so doing something fairly minimal
[17:49] <john-mcaleely> and wait for the thing to die :-)
[17:49] <dobey> because if it's connected to usb, it's charging, and you don't know how long it's alive until after it's dead :)
[17:49] <john-mcaleely> dobey, aha, fair point
[17:49] <john-mcaleely> hmm
[17:49] <dobey> well, you need to calculate averages under different conditions
[17:50] <dobey> ie, in the same way that google tests the Nexus phones with Android, to determine the advertised battery life times
[17:50] <john-mcaleely> dobey, yes, that makes sense
[17:50] <dobey> and i think some of those tests are run in radio isolationg
[17:50] <dobey> err, isolation
[17:51] <dobey> which might be hard to do at home :)
[17:51] <john-mcaleely> yes. I wonder if we have a way to configure the handset into some sort of radio-off-but-screen-on mode, and let it sit there
[17:51] <john-mcaleely> hmm
[17:52] <dobey> you could write a tool to do that, yes
[17:52] <dobey> but just turning the radio off on the phone is a different from radio isolation
[17:53] <john-mcaleely> dobey, true. It would be a good first attempt though
[17:54] <dobey> the main problem is logging an accurate time
[17:54] <john-mcaleely> dobey, yeah. someone would need to watch. Maybe a camera?
[17:55] <dobey> yeah, you'd need a camera rig
[17:56] <ogra_> why wuld you need a camera to see when the device dies ?
[17:56] <dobey> anyway, i expect that Bq/Meizu probably already have the testing setups for that, and will be doing testing for battery life
[17:56] <dobey> ogra_: because you need to log it
[17:56] <ogra_> it vanishes from adb too at that point :)
[17:57] <dobey> ogra_: maintaining an ssh connection over the network doesn't work in radio isolation
[17:57] <ogra_> adb is using usb ;)
[17:58] <dobey> ogra_: usb is charging the phone, so it will never die :)
[17:58] <ogra_> you can avoid that
[17:58] <dobey> if you want to make a custom cable i guess
[17:58] <dobey> or try to find a data cable that doesn't do charging
[17:58] <ogra_> that should also be possible via the usb driver ... but yeah, worst case you just use a cable without power
[18:00] <dobey> ogra_: also, the phone needs to be already running to use adb, so it changes the results a bit, as ideally you'd want to start from total power off state, log start time when power button is pressed, and log end time when phone dies
[18:01] <ogra_> yeah, you might be unprecise in the margin of minutes ...
[18:01] <dobey> anyway, i'd just let Bq/Meizu do the work of testing battery life on their phones :)
[18:02] <ogra_> if it is out of context yes ...
[18:02] <ogra_> if it is supposed to bein context with our software i wouldnt expect them to do it
[18:02] <dobey> well
[18:02] <dobey> our job is to write software that doesn't kill battery life
[18:02] <ogra_> right
[18:02] <dobey> their job is to verify battery life for their marketing materials
[18:03] <ogra_> how do you prove it doesnt ;)
[18:03] <dobey> profiling :)
[18:03] <dobey> which is different from testing for marketing data
[18:04] <w00t> and also a good bit device-dependent
[18:05] <dobey> yes
[18:06] <dobey> although apparently my nexus 5 gets better battery life on ubuntu with the backlight never turning off than others with stock android; and i think the battery life is horrible :)
[18:07] <w00t> why does the backlight not turn off?
[18:14] <dobey> w00t: if i knew, it wouldn't be turning off, because i would have fixed it already :)
[18:14] <dobey> err, it would be turning off, rather
[18:15] <dobey> but for some reason on the n5, the backlight will stay on even with screen off
[18:15] <dobey> i think it's a kernel issue. it also stays on when phone is powered off and plugged in to the wall charger
[18:16] <w00t> well, presumably wall charger on utouch is still meaning "is booted up", so you can display charging UI and such
[18:18] <dobey> no, powered off and on wall charger has the same stuff as android. but i did a quick search about it and found some complaints from other people using cyanogenmod and such, with similar problems
[18:18] <dobey> and it seemed to be related to something in the kernel
[18:19] <dobey> it might be "booted" in the sense that it's running the minimal android bits, not sure. but it's definitely not booted into the ubuntu bits
[18:21] <w00t> ok
[18:23] <w00t> dobey: https://github.com/nemomobile/mce/blob/master/mce-hybris.c#L380 <- mce is how sailfish is dealing with this stuff at least (though there's also an interesting dance to coordinate shutdown & stopping of rendering with the QPA plugin in control of the display, assuming ubuntu has something similar for its mir compositor)
[18:25] <dobey> well i don't think mir is running in the powered off state when on wall charger
[18:26] <w00t> no
[18:26] <w00t> we are in charge when in charging mode also, so.. the situations are quite different
[18:27] <w00t> 'we' being sailfish.. :)
[18:32] <dobey> so what does powered off and on wall charger look like on sailfish on a nexus 5 when you tap the power button to see the battery charge state icon?
[18:35] <w00t> dobey: the same as any other device: it'll have our charging screen
[18:36] <w00t> dobey: we're booted into a minimal cut of the OS at that phase (no compositor, just running the charging animation and some other services like mce at that point)
[18:36] <felipealmeida> has anybody seem simg2img returning errors with checksum?
[18:36] <dobey> w00t: video or picture of that?
[18:39] <w00t> dobey: our current one is pretty boring. it's a static image and a battery percentage, so not much to show :-P
[18:39] <felipealmeida> hm, actually, it works even with the error
[18:39] <dobey> w00t: sure. i was just wanting to see something that's actually different from android
[18:40] <w00t> dobey: I don't have an n5 yet. I may be getting one soon, if so I'll be happy to oblige :-)
[18:41] <dobey> ah ok
[19:00] <felipealmeida> which rootfs should I use with phablet-4.4.2_r1 ?
[19:11] <dobey> i wonder why n5 is so slow at installing new images, too. n4 seems to be magnificently faster at that for some reason, which is weird, given the n5 is a fair bit mroe powerful.
[19:15] <stgraber> dobey: nand speed?
[19:16] <dobey> stgraber: i think more likely something changed in later ubuntu images/recovery. i recall it used to be quite a bit faster than it is today
[19:16] <stgraber> nothing that I changed anyway, I haven't touched the main upgrader script in months
[19:16] <dobey> i don't know what the nand speed is on the devices, but seems like it would be wrong for it to be slower on the n5 than the n4
[19:17] <dobey> stgraber: yeah, not blaming. just wondering out loud. i just flashed both my n5 and n4 at the same time, and the n4 was done and running a couple minutes before the n5. and the n5 is staying at the "Google" logo much longer as well
[19:18] <stgraber> the upgrader will typically have to read every file that's part of the update between 2 and 3 times, so nand speed is the main factor there, way over CPU (and yes, it's ridiculous having to read those big files so many times, but busybox tar is a bit limited ;))
[19:19] <dobey> like, it will sit at the "Google" logo screen for well over a minute sometimes :(
[19:28] <Beldar> dobey, Flash it again, it's been known to fail, better that than trying a fix to start with.
[19:30] <dobey> Beldar: it didn't fail
[19:30] <Beldar> dobey, So it boots just sits on the splash?
[19:31] <dobey> Beldar: like i said, it's just incredibly slow
[19:31] <dobey> when it gets around to actually booting into ubuntu, it does, and the apps and stuff work fine (as well as they work on n5 anyway)
[19:32] <Beldar> could be a bad load fail has a wide meaning, like I said. ;)
[19:33] <taiebot> Is it me or scrolling through history in messaging app is very jerky and slow. had look at #1356539 but i do not think its related.
[19:38] <dobey> Beldar: and how would one determine that then? it eventually boots and is running the new image, which does not seem like a "fail" to me
[20:36]  * dobey wonders what the best way to force having a corrupted click package installed, is
[20:42] <kenvandine> jgdx, i'm building armhf debs for libqofono with the valid property on QOfonoSimManager, i'll post them in a bit and email you a link to try whenever you have time
[20:42] <daker> dobey: turn off wifi will it's downloading ?
[20:42] <daker> while*
[20:46] <dobey> daker: i don't want the .click itself to be corrupt. that would probably be uninstallable. i want the installed package to havea  corupt manifest or something
[20:47] <dobey> daker: ie, something that will cause "click list" to print stuff other than package names and versions
[20:47] <dobey> so i can test this bug
[20:48] <dobey> and see how "click list" will fail exactly
[20:48] <dobey> i shouldn't have told you how to fix your broken phone :)
[20:49] <daker> dobey: maybe install a package then corrupt the manifest manually?
[20:50] <dobey> yeah, i guess. tring to find the easiest way to do it on my workstation, rather than poking about in adb on a phone
[20:58] <daker> ah i dont have anyidea how this can be done
[20:58] <dobey> yeah, i'm thinking
[20:58] <dobey> and istringstream is such a pain too
[21:36] <jgdx> kenvandine, wee. Wonderful news!
[22:05] <Blueskyder> hi!
[22:10] <popey> jhodapp: hey, do you care much if a particular website with streaming video works or not?
[22:29] <Saviq> barry, hey, we're looking into refreshing data in the launcher, for clicks we'll have a click hook, can you tell us what's the state-of-the-art approach for running something after image updates?
[22:30] <barry> Saviq: oh interesting.  there really isn't anything because all system updates end in a reboot
[22:31] <Saviq> barry, yeah, we might need to just do it @ unity8 startup, was just wondering if this was solved otherwise
[22:31] <Saviq> barry, like an upstart task ran only after OTA or something
[22:32] <barry> Saviq: it might be something to think about as we extend s-i to non-mobile environments though.  i.e. if your server was updating via images, you wouldn't always need to reboot to apply the update.  then it wouldn't be difficult at all to run a post-installation hook
[22:32] <barry> Saviq: or something like that, yeah
[22:33] <barry> anyway, it's not currently solved by system-image
[22:33] <Saviq> barry, shall I file a bug to track?
[22:33] <barry> Saviq: please do.  i'll triage it
[22:36] <jhodapp> popey, streaming from the browser or streaming from the mediaplayer-app?
[22:36] <popey> jhodapp: browser
[22:36] <jhodapp> popey, I don't care, but the web team will
[22:37] <popey> jhodapp: hah ☻ I thought underneath it used your media bits
[22:37] <jhodapp> popey, not yet, the web team is in the works of adding that
[22:37] <popey> ok
[23:01] <Saviq> barry, bug #v
[23:01] <Saviq> bug #1358528
[23:13] <barry> Saviq: got it, thanks