[00:04] <bkh> well, now I'm stuck in recovery with a message that says "autodeploy.zip not found"
[00:06] <bkh> desktop terminal says it's pushing recovery, but I'm already in recovery, so...
[00:06] <bkh> oh wait, there it goes.
[00:18] <iron_giant> With the current files up I am handing ont he google screen after autodeploy's
[00:18] <iron_giant> *hanging
[02:33] <SamZaNemesis> How can I do kernel debugging? I am trying to add VT support to my kernel but it crashes on boot, and my SoC disables uart on my device
[02:34] <SamZaNemesis> I have a HTC Ville (One S)
[03:06] <Nothing_Much> Anybody know about how to utilize libhybris?
[03:06] <Nothing_Much> *on the desktop
[03:47] <duflu_> Nothing_Much: I don't think it makes any sense on desktop. It exists to utilize Android libraries. Hence we have https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1232962
[03:48] <Nothing_Much> duflu_: Actually I'm on an Arm computer with an Ubuntu desktop
[03:48] <duflu_> Nothing_Much: Oh, interesting case
[03:49] <Nothing_Much> Yeah, I supposedly have Android files in my new /system* folder
[03:49] <Nothing_Much> I'm following a tutorial, but step 1 is complex to me
[03:49] <Nothing_Much> Well
[03:49] <Nothing_Much> It's not really specified what I should do
[03:50] <Nothing_Much> Am I supposed to replace the zImage and config files?
[03:51] <duflu_> Nothing_Much: Try asking rsalveti
[03:51] <Nothing_Much> rsalveti: Is it possible to use libhybris on an Arm Ubuntu desktop?
[03:51] <Nothing_Much> Am I allowed to link my question from an external website?
[03:54] <Nothing_Much> duflu: Can I link to my reddit post about my question?
[03:54] <duflu> Nothing_Much: Go ahead, but your question is now beyond my knowledge
[03:54] <Nothing_Much> http://www.reddit.com/r/linuxquestions/comments/1qam58/how_to_utilize_libhybris_on_ubuntu_desktop_1310/
[08:11] <Myrtti> morning
[08:11] <Myrtti> so
[08:12] <Myrtti> is there anywhere where I can see *all* the past calls and such?
[08:21] <popey> Myrtti: calls?
[08:21] <popey> oh, call log, yes
[08:22] <popey> Myrtti: dialler -> tap the top bar, scroll across to "Call log"
[08:22] <Myrtti> popey: thanks, I though I was starting to imagine things
[08:23] <Myrtti> ... I got stressed over a telemarketer?
[08:23] <Myrtti> nnngghh
[08:25] <Myrtti> thought even.
[09:23] <JamesTait> Good morning all; happy Origami Day! :-D
[09:28]  * ogra_ folds it
[10:58] <davmor2> Morning all
[11:07] <tvoss> Saviq, ping
[11:08] <Saviq> tvoss, /me off today, email please
[11:08] <tvoss> Saviq, ack
[11:57] <abovo> how to run on go clever tablet?
[12:17] <AskUbuntu> plugin any software in to Ubuntu operating system | http://askubuntu.com/q/375402
[12:43] <AskUbuntu> Will the mobile network connection work on the Nexus 7? | http://askubuntu.com/q/375408
[12:44] <swood> attache gamesurge
[13:37] <xnox> rsalveti: is it just me, or initramfs-tools-touch first mounts ${rootmnt} as read only, and then tries to do "mkdir -p" under ${rootmnt}/ ...
[13:38] <rsalveti> xnox: if you're trying the emulator with the current initd, it'll be broken because of the revert done last saturday, I'm fixing it as we speak
[13:39] <xnox> rsalveti: ok. i'll wait for that upload, before I continue testing my new features.
[13:39] <rsalveti> xnox: which features?
[13:39] <xnox> rsalveti: no-loop mounts.
[13:39] <rsalveti> xnox: hm, right, why?
[13:39] <rsalveti> xnox: don't we want to simulate the system-based image?
[13:40] <rsalveti> if you don't want loop-based mounts, it's just better to not use it at all
[13:40] <xnox> rsalveti: because we don't want loop-mounts, they cause shutdown ordering problems. Ideally we'd like to repartition existing devices, but all of them have broken partition tables. With emulator we can finally simulate what we actually want. "system partition" with ubuntu rootfs direct, no loop-mounts, mounted read-only direct, "userdata partition" mounted read-write.
[13:41] <xnox> rsalveti: hence i'm updating initramfs-tools-ubuntu-touch, to support one more type of booting =)
[13:41] <xnox> (well rootfs setup)
[13:41] <rsalveti> xnox: right, but while I agree with the solution, I still believe it's better to simulate what we end up using in our supported devices
[13:42] <xnox> it currectly has loop-mounted rootfs, legacy flipped and no i'm adding non-loop rootfs =)
[13:42] <rsalveti> so people can also use the emulator to test changes in the initrd
[13:42] <xnox> rsalveti: sure. the default for the emulator will stay as the current system-image one.
[13:42] <xnox> rsalveti: non-loop is a demo/preview for evaluation =)
[13:42] <rsalveti> right, fine then :-)
[13:44] <dpm> hi rsalveti, this last weekend I was trying to get a port going, but I encountered some build problems. Do the steps in the "Building Android for Ubuntu" look sensible to you? Anything that I might have missed? -> https://wiki.ubuntu.com/Touch/Devices/galaxysl
[13:45] <rsalveti> let me take a look
[13:46] <dpm> cool, thanks
[13:47] <rsalveti> dpm: first issue, we're using phablet-trusty now (unless you want to start with a saucy-based port)
[13:47] <rsalveti> repo init -u git://phablet.ubuntu.com/CyanogenMod/android.git -b phablet-saucy
[13:48] <dpm> rsalveti, I thought I'd use a stable image for the port, but I can switch to trusty if that's the recommended way
[13:48] <rsalveti> dpm: while testing against something stable is indeed easier, it's better to use our dev release as we can fix possible issues in phablet.u.c :-)
[13:49] <rsalveti> other than that, the instructions all look fine, just need to understand the build failure now
[13:49] <rsalveti> something might be missing
[13:49] <rsalveti> make: *** No rule to make target `/home/dpm/dev/phablet/out/target/product/galaxysl/obj/SHARED_LIBRARIES/libwpa_client_intermediates/export_includes', needed by `/home/dpm/dev/phablet/out/target/product/galaxysl/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/import_includes'.  Stop.
[13:50] <rsalveti> this means that libhardware_legacy_intermediates depends on libwpa_client, but nothing is building libwpa_client
[13:51] <dpm> rsalveti, yeah, it seems to have to do with wpa supplicant, but the sources for wpa supplicant are there. I couldn't figure it out. I tried to do a vanilla build of CM10.1 for this device, and the build succeeded. I'm not sure which part is removed in the Ubuntu build
[13:51] <rsalveti> dpm: see build/core/main.mk, that's where we add the projects we want to build
[13:51]  * dpm looks
[13:52] <rsalveti> dpm: subdirs := \
[13:52] <rsalveti>     abi/cpp \
[13:52] <rsalveti> ...
[13:52] <rsalveti> and we also have a few specifics per device as well
[13:52] <dpm> rsalveti, aha, I think 	external/wpa_supplicant_8_ti \ is missing from subdirs
[13:53] <rsalveti> dpm: right, could be
[13:53] <rsalveti> ifeq ($(TARGET_PRODUCT), cm_manta)
[13:53] <rsalveti> subdirs += \
[13:53] <rsalveti>     system/security/keystore
[13:53] <rsalveti> endif
[13:53] <rsalveti> you can add something similar for your device
[13:56] <rsalveti> dpm: while debugging, you can also use mmm to build the needed project by hand
[13:56] <rsalveti> that will put the dependency in place for you
[13:56] <rsalveti> so you could try mmm external/wpa_supplicant_8_ti
[13:56] <rsalveti> and then calling brunch again
[13:56] <rsalveti> to see if that fixes it
[13:56] <dpm> ok, cool
[13:56] <rsalveti> once you find the missing project, you can add it to the default dependencies
[13:59] <dpm> rsalveti, adding the conditional subdirs worked to fix the initial error, but now I'm getting make: *** No rule to make target `/home/dpm/dev/phablet/out/target/product/galaxysl/obj/SHARED_LIBRARIES/libnativehelper_intermediates/export_includes', needed by `/home/dpm/dev/phablet/out/target/product/galaxysl/obj/SHARED_LIBRARIES/libbt-vendor_intermediates/import_includes'.  Stop. - is it always going to be trial and error, or is there a way to figure out
[13:59] <dpm> any missing subdirs before the build?
[14:00] <rsalveti> dpm: not an automatic way, as you need to check in the Android.mk file to see which dependencies are needed, that's why it's easier to just try and fix as you go
[14:00] <dpm> ok, will do that, thanks!
[14:25] <awafaa> is there a table that shows what components are re-used from AOSP/CM and what is new?
[14:25] <awafaa> I'm thinking of things like AudioFlinger replaced with PulseAudio, SurfaceFlinger with Mir etc
[14:35] <popey> awafaa: not that i'm aware of
[14:36] <dpm> rsalveti, it seems that for my port's build to work, I need to add the external/bluetooth directory from cm10.1, which is not pulled from phablet.u.c - what's the best way to make sure that directory is pulled?
[14:36] <awafaa> popey: ok, in that case could you advise on what else has changed?
[14:42] <popey> awafaa: someone else may be better placed, such as xnox or rsalveti ☻
[14:44] <xnox> awafaa: it's easier to do it other way around. Everything is stock / normal ubuntu. There is android container which has libhybris which is used to access: hw graphics drivers, use surface flinger (unless mir is used), access ritld (phone/sim stuff), camera device.
[14:44] <ogra_> video and audio codecs too
[14:44] <xnox> yeap, thanks ogra_ =)
[14:44] <ogra_> and sensors/GPS indeed
[14:44] <awafaa> excellent, thanks xnox & ogra_
[14:46] <awafaa> and am i correct in saying that system apps are considered apps for system functionality and core are for user experience?
[14:46] <awafaa> im trying to explain why there are the two groups of apps
[14:47] <xnox> awafaa: there are no two groups of apps.
[14:47] <xnox> awafaa: what do you mean by "system apps"
[14:47] <xnox> awafaa: and what do you mean by "core"
[14:47] <popey> the confusion comes across probably because of the core apps (community apps) project
[14:47] <popey> which wasn't the best name
[14:48] <popey> core apps being the ones that we created in collaboration with the community, you can think of "system" apps as the ones internally made (but also open source).
[14:48] <popey> but they're all just apps
[14:49] <awafaa> xnox: basically what popey said
[14:49] <awafaa> thanks for the clarification
[14:51] <xnox> awafaa: no-matter who they are developed by the useful distinction are: pre-installed on the image vs 3rd-party software-store click apps (those that one can download/install)
[14:52] <xnox> awafaa: the former are updated together with the rest of the system image update, latter are upgraded on-demand individually from the store.
[14:53] <awafaa> makes sense, thanks again
[14:53] <popey> well
[14:53] <popey> thats not clear either
[14:53] <popey> because we have put the baked-in apps in the store too ☻
[14:53] <xnox> =) i omitted nity grity detail, about pre-installed clicks =)
[14:53] <popey> ☻
[14:53] <xnox> which is imho a backdoor =)
[14:54] <xnox> well, that's a bad word, "dual upgrade path"
[14:54] <xnox> click apps.
[14:54] <popey> they dont get updated by a system image update
[14:54] <popey> do they?
[14:54] <xnox> oh, i did not know that.
[14:54] <xnox> i thought they are.
[14:54] <popey> we update them through the store
[14:55] <popey> well, the community ones are updated in the store, and also baked into the full image
[14:55] <xnox> popey: which is fetched to the image, at image build-time. such that fresh image has fresh pre-installed clicks.
[14:55] <popey> dont think the camera/dialler etc are though
[14:55] <popey> right, okay, i agree on that
[14:55] <xnox> popey: but if that translates into "upgrade click on delta-system-image upgrade, if new image has newer click" i don't know.
[14:55] <xnox> (and it wasn't upgraded via store yet by the user)
[14:56] <xnox> easy enough to test though. Flash old image, don't sign into store, upgrade to newer image, check version numbers of the installed clicks.
[14:56] <popey> well the image only updates /usr/share/click/pre-installed, not /opt/com.ubuntu.click/... which takes precidence?
[14:56] <popey> yeah
[14:56] <xnox> unless there is an upgrade hook, that does.
[14:56] <xnox> somehow /opt/com.ubuntu.click is updated on first boot from pre-installed.
[14:57] <popey> magic
[14:57] <awafaa> so how would you recommend to measure power usage if using a system image?
[14:59] <popey> awafaa: not sure it's accurate / easy without influencing the results
[14:59] <popey> but /sys/class/power_supply/battery is interesting
[14:59] <popey> cking has done some work profiling power usage, but we haven't focussed our attention on optimising for that yet
[15:00] <awafaa> popey: agree that it's easy to influence. i was curious as to how purely from an informative perspective
[15:01] <awafaa> makes sense, get it working first then get it work well
[15:01] <awafaa> err, get it working well even
[15:01] <popey> awafaa: i wrote a simple script which polls those files for battery level over time
[15:01] <popey> as a cron job every minute
[15:01] <cking> awafaa, http://smackerelofopinion.blogspot.co.uk/2012/11/non-linear-characteristics-in-draining.html
[15:01] <popey> there we go ☻
[15:02]  * ogra_ just goes to system-settings -> battery :P
[15:02] <ogra_> it has a shiny graph and all
[15:04] <cking> and I have some shiny tools in https://launchpad.net/~colin-king/+archive/white
[15:04] <ogra_> :D
[15:22] <awafaa> thanks chaps
[15:32] <davmor2> ogra_: well the android to Ubuntu-touch test seems to be going well so far :)
[15:37] <rsalveti> dpm: you can add as a dependency from your device repository
[15:37] <rsalveti> at device/samsung/galaxysl, check for cm.dependencies
[15:37] <rsalveti> dpm: as long you maintain that repo, you can safely add it there
[15:37] <rsalveti> dpm: or you could also see what is requiring that bluetooth dependency and remove that as well, as we use bluez anyway
[15:38] <dpm> rsalveti, ah, I think the later might make more sense, but for the sake of just getting it to build now, I'll go temporarily for cm.dependencies
[15:38]  * ogra_ watchest the OTA update on his maguro slowly count to 115% 
[15:38] <ogra_> and fail !
[15:39] <ogra_> bah !
[15:39] <rsalveti> ogra_: you didn't bump initrd and android
[15:39] <rsalveti> I'm pushing android now
[15:39] <ogra_> rsalveti, that was #190
[15:39] <rsalveti> already did the initrd
[15:39] <ogra_> #19
[15:40] <ogra_> built 6h ago
[15:40] <rsalveti> sure, but the new systemd rules were not part of that build
[15:40] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20131111.changes
[15:40] <ogra_> they were :)
[15:40] <davmor2> ogra_: r18 ota killed my maguro but phablet flash fixored it admittedly wiping all my data
[15:40] <rsalveti> ogra_: not in the initrd :-)
[15:40] <ogra_> rsalveti, argh !
[15:40] <ogra_> indeed
[15:40] <popey> davmor2: you should have asked in here, we could have fixed without wiping
[15:41] <ogra_> rsalveti, sh*t!!!
[15:41] <ogra_> so 19 will be broken too
[15:41] <rsalveti> ogra_: just pushed a new android respin, once that's done, you can trigger a new image
[15:41] <ogra_> yeah, but thats more than 2h out
[15:41] <davmor2> popey: it was Sunday at 9:30 and I needed my phone back up and running
[15:42] <rsalveti> ogra_: well, not much we can do I guess
[15:42] <ogra_> and removing images doesnt really work well ...
[15:42] <davmor2> popey: other wise I would of :)
[15:42] <ogra_> you have to copy a reverse version over the new image and it will regenerate all diffs
[15:42] <davmor2> popey: plus I couldn't get passed the google logog
[15:42] <popey> davmor2: i know, I had same
[15:42] <ogra_> but i guess that takes nearly as long
[15:42] <popey> davmor2: it's fixable
[15:43] <rsalveti> ogra_: oh, right
[15:43] <rsalveti> awafaa: I think we might have that documented somewhere
[15:43] <davmor2> popey: indeed it almost always is but then I also knew I was doing an android → current UT today too so would be blowing everything away anyway :)
[15:43] <rsalveti> awafaa: we replaced a few components already, but we're still using the android hal for the core components
[15:44] <ogra_> davmor2, popey well, dont upgrade to #19
[15:45] <ogra_> it will have the same prob
[15:45] <popey> :D
[15:45] <popey> I'm not upgrading till you do my friend ☻
[15:45]  * ogra_ guesses once #20 is out he will have to write a long mail to the phone ML
[15:45] <ogra_> what a mess
[15:46] <davmor2> ogra_: so Android current on maguro to Ubuntu Touch 18 worked fine woohoo :)
[15:46] <ogra_> well, image 18 is image 15 in fact
[15:46] <ogra_> just re-labeled
[15:50] <rsalveti> awafaa: https://docs.google.com/a/canonical.com/presentation/d/1WZ07phR2SjvHK1JaNGFakjGCW6Jr8_o33HvKLojQ7hI/edit#slide=id.p
[15:50] <rsalveti> awafaa: a few slides showing the current architecture
[15:53] <awafaa> rsalveti: thanks very much!
[15:53] <rsalveti> we still need to build a wiki page with an up-to-date description of our architecture
[15:56] <xnox> rsalveti: that's really cool presentation!
[15:57] <ogra_> xnox, dont say that to loud else PR will steal him from us !!!
[16:25] <morphis> rsalveti: I recently tried to integrate your work for getting pulseaudio working with UCM on ubuntu touch into our environment
[16:25] <morphis> it mostly works but just can't get pulseaudio to output anything to the speakers
[16:26] <morphis> so I wondered if there is any special configuration needed to set it up correctly
[16:30] <rsalveti> morphis: hm, for basic audio it should just work, once you have the right ucm files in place
[16:30] <rsalveti> even aplay should work (without pulse)
[16:30] <morphis> aplay works fine
[16:30] <morphis> but throuh paplay there is no sound
[16:30] <rsalveti> the other changes we got was just to trigger the modem output/input when you setup a call (which talks with the audio hal)
[16:31] <morphis> yeah I know but that should needed yet for basic audio output
[16:31] <rsalveti> yeah
[16:31] <awesome> hi
[16:31] <rsalveti> morphis: which device?
[16:31] <morphis> maguro/mako/grouper
[16:31] <morphis> it's the same for all
[16:31] <Guest71194> can i install ubuntu touch on galaxy s2 gti 9100?
[16:31] <rsalveti> morphis: let me get the log output from our pulse, just a sec
[16:32] <morphis> rsalveti: slight difference is that we start pulseaudio in system mode
[16:32] <Guest71194> can i install ubuntu touch on galaxy s2 gti 9100?
[16:33] <rsalveti> oh, and we also have additional logic in there to handle jack detection
[16:33] <rsalveti> hm, shouldn't make any difference
[16:33] <morphis> rsalveti: I have that patch already in our setup too :)
[16:33] <rsalveti> cool
[16:34] <Guest71194> assholes
[16:34] <rsalveti> wtf
[16:34] <morphis> hm, seems like I've found one problem
[16:35] <morphis> it seems to work after a restart of the daemon but not when it's automatically started at boot tiem
[16:35] <morphis> interesting, why didn't that worked before
[16:36] <rsalveti> maybe a race with alsa/ucm?
[16:38] <morphis> rsalveti: possible
[16:38] <morphis> trying currently to start it later in the process to see wether the problem results in someone coming in between and changing the configuration
[16:41] <rsalveti> right
[16:45] <tygerlord> hello does someone known touch script here?
[16:50] <tygerlord> touch script try to mount /var/lib/lxc/android/system.img /android-system but where come from this sutem.img, does somebody know?
[16:54] <morphis> tygerlord: it's the android system image which you build with the phablet environment
[16:54] <rsalveti> it's part of the userdata partition, when you're booting using the system-image format
[16:54] <rsalveti> which is indeed the android system image built with the phablet environment
[16:55] <rsalveti> ogra_: do we have a wiki page describing how to use the system-image format?
[16:55] <ogra_> rsalveti, not so sure how much it goes into detail
[16:55] <tygerlord> Ok. I have a system.img on out/target/product/crespo/system.img but i can mount it
[16:56] <ogra_> https://wiki.ubuntu.com/ImageBasedUpgrades
[16:56] <rsalveti> guess first step is trying to run ubuntu-touch just with the flipped container, not using system-image
[16:56] <rsalveti> once you have it all working, you can try to switch to the system-image format (root mounted as ro)
[16:57] <tygerlord> I can't mount it system type is unknow, i've tried ext but fail
[16:59] <rsalveti> that depends how the system.img is created for your device
[16:59] <rsalveti> I believe we're only supporting ext4 based fs atm
[16:59] <tygerlord> touch script dont specify mount type ...
[17:00] <rsalveti> right, but that's because it tries to find out the right format automatically
[17:00] <rsalveti> you said you can't even mount that file in your host
[17:00] <rsalveti> wonder if that is using yaffs2
[17:01] <ogra_> are you sure its a filesystem image and not a sparse image that needs converting first ?
[17:01] <rsalveti> yeah, you're right, from the android side it should still be a sparse image
[17:01] <tygerlord> I don't knwo what  is a sparse image?
[17:01] <ogra_> so you might need sim2img
[17:01] <ogra_> to convert it
[17:03] <tygerlord> Ok thank you very much ogra_ and rsalveti I will try this.
[17:03] <ogra_> good luck
[17:04] <davmor2> ogra_: so is image 20 happening today or will it be tomorrow now?
[17:04] <ogra_> davmor2, it will happen soon
[17:04] <rsalveti> ogra_: you can probably trigger that already
[17:04] <rsalveti> yeah, android was just published it seems
[17:04]  * ogra_ shakes his fist at britney ... stop drinking and taking drugs and process the android package !!!
[17:05] <ogra_> oh, cool
[17:05] <rsalveti> not yet in rmadison
[17:05] <rsalveti> ogra_: should take another 5 mins
[17:05] <ogra_> i have it here
[17:05] <rsalveti> ogra_: ok, it is now :-)
[17:05] <ogra_> buolding :)
[17:05] <rsalveti> go for it :-)
[17:25] <jockerfox> Hi to all, a simple question: Nexus7 vers. 2013 is supported in the future?
[17:26] <morphis> rsalveti: ok, fixed the issue
[17:26] <morphis> starting pulseaudio a little bit later helps
[17:26] <rsalveti> great, so indeed a race
[17:26] <beuno> jockerfox, it isn't currently, and it's unclear still if it will be or not
[17:26] <morphis> rsalveti: one further thing, did you saw something like http://pastie.org/8472401 on the N4?
[17:27] <morphis> rsalveti: right
[17:27] <rsalveti> jockerfox: should be once someone do the port for it
[17:27] <rsalveti> we'll be changing our android baseline version soon, which will help
[17:27] <rsalveti> but we (I don't at least) have the device to test
[17:28] <rsalveti> morphis: saw that a few times already
[17:28] <rsalveti> not sure yet what triggers it though
[17:28] <jockerfox> bueno & rsalveti: ok.. thanks
[17:28] <morphis> rsalveti: I guess it's some shader code which is causing this
[17:29] <morphis> will try to track it with apitrace later
[17:29] <rsalveti> great
[17:32] <morphis> rsalveti: just time consuming ..
[17:32] <Nothing_Much> rsalveti: I was told to ask you whether it is possible to utilize Libhybris on an arm desktop using Ubuntu desktop or not.
[17:33] <rsalveti> Nothing_Much: sure, it all depends on what you want to use with libhybris
[17:34] <rsalveti> if you mean the GL driver, you could create a x11 driver for it, but it might be a bit painful
[17:34] <rsalveti> otherwise you could use mir or wayland, but then you'll need a different desktop environment
[17:35] <Nothing_Much> I just need a GL driver for an SGX 544
[17:35] <Nothing_Much> Mir and Wayland don't work if I just install them
[17:35] <timppa> What's happening with the latest builds? OTA breaks the phone
[17:35] <rsalveti> yeah, not outside the box, you probably need some work to get that going
[17:36] <rsalveti> morphis: do you know if we have any crazy one that created a x11 driver using libhybris?
[17:36] <rsalveti> timppa: if you're using devel-proposed, the next image should fix your issue (which is still building)
[17:37] <rsalveti> but guess you'll need to reflash with phablet-flash
[17:37] <timppa> rsalveti: yes
[17:37] <timppa> rsalveti: thanks
[17:37] <rsalveti> we had an issue with the initrd, that makes the boot to crash
[17:37] <timppa> can it be fixed from busybox?
[17:38] <morphis> rsalveti: maybe grolea did
[17:38] <rsalveti> timppa: nops, as you need to update the initrd udev rules
[17:38] <timppa> ok
[17:38] <morphis> s/grolea/groleo/
[17:38] <rsalveti> morphis: interesting
[17:38] <rsalveti> morphis: to use with sgx?
[17:38] <morphis> I think so
[17:38] <morphis> at least I heard that someone tried it with sgx
[17:39] <rsalveti> cool
[17:39] <timppa> rsalveti: ETA on the build to finish?
[17:39] <rsalveti> Nothing_Much: then you might want to ping groleo to see if he got that to work
[17:39] <morphis> Nothing_Much: watch in #libhybris for him
[17:39] <Nothing_Much> alright
[17:39] <rsalveti> ogra_ started it 40mins ago, should be done in ~20,30 min
[17:40] <timppa> ok
[17:40] <rsalveti> timppa: but you can flash the boot.img from an older image if you have that around
[17:40] <morphis> Nothing_Much: you can also ask thp in #libhybris
[17:40] <timppa> rsalveti: that's ok, I'll wait for the build
[17:40] <Nothing_Much> Thanks, I'll ask them, groleo doesn't seem to be on though
[17:41] <dpm> rsalveti, I managed to build my first port, now let's flash it and see if it works :)
[17:41] <rsalveti> dpm: great
[17:52] <ogra_> the cdimage part of the build is done already ... waiting for system-image to be done processing it
[18:01] <dpm> rsalveti, so right now the phone I want to install the port on has CM 10.1 installed. What are the steps to get the port running, something along the lines of 1) Reboot to recovery and wipe data 2) Flash the zip file resulting from the build 3) Flash saucy-preinstalled-phablet-armhf.zip ?
[18:03] <xnox> dpm: that sounds about right =)
[18:03] <taiebot> Hi guys. What about simcard apps ? Will it be supported by ubuntu-touch ? With my (*%&"£) phone provider when i go abroad i need to normally change few settings in the simcard apps (roaming etc) to get the phone going. I have not been able to enable my phone while i was abroad. Are they going to be supported?
[18:04] <dpm> thanks for confirming xnox, I'll wait for the android backup to finish and then give it a go :)
[18:04] <rsalveti> dpm: yup :-)
[18:04] <dpm> thanks :)
[18:08] <mhr3> ogra_, hilfe, i can't ota update
[18:09] <mhr3> the update progress goes up to 117% and then says that download failed
[18:32] <ogra_> stgraber, hmpf, seems there are issues with OTA upgrades now ...
[18:32] <ogra_> (see mhr3 above and popey also has issues)
[18:33] <stgraber> barry: ^
[18:33] <ogra_> stgraber, http://paste.ubuntu.com/6401140/
[18:34] <ogra_> seems a signing error
[18:34] <barry> ogra_, stgraber keyring problem in trusty channel?
[18:34] <ogra_> stgraber, ah, and my maguro also just went to 104% after 40min downloading :(
[18:34] <barry> (nothing's changed in systemimage since saucy)
[18:34] <t1mp> oh nice, today for the first time I noticed that my galaxy nexus's battery is charging while it is connected to my laptop :)
[18:35] <ogra_> t1mp, dont trust it ... it isnt really charging ... a USB port only provudes 500mA ...
[18:35] <barry> ogra_: but i've also seen some intermittent weirdness, possibly in u-d-m, which i'm still tracking down locally
[18:35] <ogra_> t1mp, if it is on all the time the device will pull more thnan that out of the battery over time
[18:35] <stgraber> barry: http://paste.ubuntu.com/6401152/
[18:36] <t1mp> ogra_: what I noticed is that the battery indicator showed almost empty a few hours ago, and a bit later half full, and now full.
[18:36] <t1mp> ogra_: is the indicator wrong?
[18:36] <barry> fwiw, the progress meters comes straight out of u-d-m.  i just tell the u/i what it tells me
[18:37] <popey> https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1250181
[18:37] <ogra_> t1mp, no, the indicator rightly detects you are attached to a power source
[18:37] <stgraber> barry: so on my side at least, that file sure looks signed
[18:37] <barry> stgraber: it does indeed
[18:37] <t1mp> ogra_: the battery charge shows that the charge increased, and the device has only been connected to my laptop today
[18:37] <stgraber> popey: can you also include "df -h" and "system-image-cli -n"?
[18:37] <ogra_> popey, barry, stgraber i have the same error
[18:37] <ogra_> systemimage.gpg.SignatureError: /android/cache/recovery/device-4694debbd4315d3bc9b5a1ae5fa19887f582647d493a4116104a6271c070e49a.delta-device-6cfc4ca8b0ccfc96a9b2a75a1a104db9340c98ad52e91f573ed0c0c6063d7ff7.tar.xz
[18:38] <ogra_> t1mp, well, if the screen is off it might charge a bit
[18:38] <t1mp> ogra_: but I wasn't really using the device. It was on, but screen on standby mostly.
[18:38] <t1mp> ogra_: ok :)
[18:38] <ogra_> t1mp, but usually you drain more than it charges via USB port if you do something on the device
[18:39] <popey> stgraber: done
[18:40] <stgraber> I just confirmed the signature is also correct on the public mirror, so that's not some kind of corruption there...
[18:40] <barry> let me switch my device to trusty-proposed and see what happens
[18:41] <ogra_> stgraber, could that be caused by anything we did on the weekend ?
[18:41] <ogra_> (rolling back to 15 and calling it 18 etc)
[18:42] <stgraber> ogra_: it's not impossible but if that's the case, I'm not seeing it...
[18:43] <ogra_> stgraber, my r19 download behaved similar ... i canceled it when rsalveti pointed out that 19 would be broken too
[18:43] <ogra_> but i did definitely have around 120% in the progress bar for it too before doing that
[18:43] <stgraber> ogra_: ok, were you at 18 at that point?
[18:43] <ogra_> no, i'm still at 14
[18:44] <stgraber> k
[18:44] <Kaloqn> Hello, I have a question. I am not using ubuntu on my PC because i like to play games, but i don't use my nexus 4 and I want to give it a try :) So I downloaded the zip files from xda topic and flashed them but my nexus 4 is stucked on google logo.
[18:44] <Kaloqn> I flashed them again and still the same. Any solutions?
[18:45] <stgraber> barry: so at this point I have two hypothesis, either the path is somehow requiring more disk space than is available (which seems a bit weird since a full should be preferred in that case since a full definitely fits) or the keyring stored in /var/lib/system-image is somehow wrong
[18:45] <barry> stgraber: i get a signature error too with: system-image-cli --channel trusty-proposed -b 0 -v
[18:46] <stgraber> barry: hmm, ok, same file?
[18:46] <barry> stgraber: checking that now
[18:47] <ogra_> Kaloqn, if you want to use zips (which we dont really encourage for nexus devices since all were switched to system images) better use http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/ instead of a reandom link in a forum
[18:48] <Kaloqn> I got the same touch file as this
[18:48] <stgraber> barry: http://paste.ubuntu.com/6401209/
[18:48] <Kaloqn> I will try to use imges. Is it same as android with sdk?
[18:48] <ogra_> if you use zips (note that many features wont work with that) make sure to flash the files in the right order
[18:48] <stgraber> barry: that's the validation of the signatures of all files involved in a -b 0
[18:49] <ogra_> the device specific zip needs to go first
[18:49] <barry> stgraber: on the server, right?
[18:49] <stgraber> barry: yep
[18:49] <Kaloqn> yeah i did this right
[18:49] <Kaloqn> Is it same with installing it as android with sdk
[18:50] <stgraber> barry: I've also manually rechecked the paths in the various indexes and they seem reasonable
[18:50] <stgraber> barry: what's also odd is that it fails the validation of some random file but didn't fail validation of the channels.json or index.json which are signed by the exact same key (for a second I thought of bad time on the device leading to key expiration)
[18:51] <barry> stgraber: this is interesting.  i tried it again with what will be s-i 2.0 and it didn't sigerror on me.  this is starting to smell like the problem i'm seeing locally, although it looks like saucy and trusty have the same u-d-m
[18:51] <stgraber> so I guess it could be something in the new device-* file which is making u-d-m somehow corrupt the file leading to the validation failure
[18:52] <Kaloqn> WHich imges should I dw? System , recovery and boot?
[18:52] <barry> stgraber: yeah, so what i'm seeing with local testing is that sometimes u-d-m's group downloads give me the file i'm asking for and sometimes it gives me the previously downloaded version of a similarly named file.  in both cases it's a keyring file.  then the sig fails sometimes and other times it succeeds.  it's damn perplexing because i don't *think* there's a race in any of the s-i code.  i just haven't nailed down the problem yet
[18:53] <ogra_> Kaloqn, follow the manual install instructions (see the channel topic)
[18:53] <stgraber> barry: hmm, well, looks like said problem is now hitting everyone somehow ;)
[18:53] <stgraber> barry: is there a flag we can pass s-i to use its own download code?
[18:53] <ogra_> barry, stgraber, up to r14 i could definitely do OTA ... and neither download manager nor system image changed recently
[18:54] <barry> stgraber: yeah, except i just got a good update, so it didn't hit me this time ;/
[18:54]  * ogra_ just checked the manifests of all recent builds 
[18:54] <Kaloqn> ogra_ Thank you very much :)
[18:54] <barry> stgraber: unfortunately, the old download code is gone.  maybe i need to ressurrect that
[18:54] <ogra_> it has to be related to the server side
[18:54] <stgraber> ogra_: right, it's been a known problem between s-i and u-d-m for quite a while, it's just been racy and only affecting barry's test suite up till now
[18:54] <stgraber> ogra_: so no change on the client side doesn't mean it's not where the bug is ;)
[18:55] <ogra_> stgraber, i know that popey was definitely able to do an OTA upgrade to r17 even ...
[18:55] <ogra_> right
[18:55] <barry> ogra_: which is what i'm trying to rule out with local testing.  my test suite just uses an internal http server, so it doesn't seem like that could be it (i'm sure the real server bears no resemblance to my testing server)
[18:55] <stgraber> ogra_: yeah and barry just got 20 flashing on his device after sufficient tries...
[18:55] <ogra_> i'm just saying that something of our doings on the weekend now seems ot expose it
[18:55] <ogra_> heh
[18:55] <ogra_> k
[18:56] <stgraber> ogra_: for all we know it could be some random bytes in the new device-* that make u-d-m unhappy :)
[18:56]  * ogra_ hits retry ... 
[18:56] <barry> stgraber: right
[18:56] <ogra_> (which is painfull over my 2M line)
[18:57] <barry> stgraber: okay, so i'm going to try to reflash my device back to trusty-proposed:16 and see what happens.  i'm on manta, but i bet that doesn't matter
[18:57] <ogra_> barry, you want 15
[18:57] <barry> ogra_: okay cool
[18:57] <ogra_> 16 was already broken iirc
[18:57] <dpm-afk> rsalveti, when trying to flash the image for a port, I did an adb push file.zio to /sdcard/autodeploy.zip, but after rebooting into recovery nothing happened, i.e. the image did not get installed. I didn't flash the recovery, I used the CM9 recovery that was on the phone already. Is this autoinstallation of autodeploy.zip something specific from the ubuntu recovery image? Shall I flash the recovery image to a newer one?
[18:57] <barry> i wonder if mandel_ is around
[18:58] <stgraber> I'm charing my mako and grouper here, they were both dead :)
[18:58] <mandel_> barry, he is :)
[18:58] <stgraber> *charging
[18:58] <barry> mandel_: hi!
[18:58] <mandel_> barry, shoot, I think you had some small problems with u-d-m, right?
[18:58] <mandel_> barry, hello :)
[18:58] <barry> mandel_: did you see my email from last week?  we're seeing weird issues on live devices that have a similar smell: LP: #1250181
[18:59] <mandel_> barry, yes, I did see your email, I wanted to talk with you to get more info
[18:59] <barry> mandel_: okay!  let's try to capture what you need
[19:00] <mandel_> barry, you mentioned that you had a funny timing issues, is that the email we are talking about?
[19:00] <barry> mandel_: that's the one
[19:00] <barry> mandel_: so, let's talk about my local tests first
[19:00] <mandel_> barry, yes, lets do it in private to limit the noise in the channel
[19:00] <rsalveti> dpm-afk: the autodeploy feature might be specific for our recovery
[19:00] <barry> mandel_: +1
[19:01] <rsalveti> dpm-afk: you can flash it manually using the recovery interface
[19:01] <rsalveti> dpm-afk: and in theory you should be able to flash the recovery generated by your build process
[19:01] <rsalveti> but that's not required
[19:01] <sergiusens> rsalveti, dpm-afk it is specific to our recovery, but if you use the phablet-flash community target it will take care of it for you
[19:02] <sergiusens> rsalveti, dpm-afk should work with cyanogenmod based recoveries at least
[19:02] <rsalveti> sergiusens: he's still doing the first-time flash :-)
[19:02] <sergiusens> rsalveti, if it's online it does't matter ;-)
[19:02] <sergiusens> as long as the assets are online
[19:03] <sergiusens> rsalveti, or just phablet-flash cdimage-touch --device-file $OUT/device.zip
[19:03] <sergiusens> dpm-afk, ^^
[19:03] <sergiusens> oh, that may not work with the device option list in place..
[19:03] <ogra_> fancy switches !
[19:07]  * ogra_ sighs, the third time i had to download ... (takes 25min over my 2Mbit line) and it counts to 108% again 
[19:07] <ogra_> barry, is there any chance i can avoid having to do the download over and over ?
[19:09] <barry> ogra_: in system-image 2.0, yes, but that's waiting on solving this problem ;)
[19:09] <ogra_> ah
[19:11] <timppa> is the fixed image available yet?
[19:12] <ogra_> timppa, yes, but the OTA upgrader has issues with it it seems
[19:12] <timppa> ok
[19:12] <timppa> ogra_: I need to run phablet-flash as my phone is unable to boot :/
[19:13] <ogra_> barry, what i notice here is that the percentage is totally jumpy even before it reaches 100% ... it just jumped from 77% to 65%
[19:13] <timppa> there seems to problems for regular downloads as well?
[19:14] <timppa> I have 100Mbps line an d dl keeps stalling...
[19:14] <ogra_> the OTA feature seems broken
[19:14] <ogra_> but i can download it fine
[19:14] <ogra_> just fails to verify the signature after download
[19:15] <barry> ogra_: yes, mandel_ and i will chat about that after we figure out the other problem (could be related, but i don't know).
[19:15] <mandel_> ogra_, it smells to be related
[19:15] <ogra_> well, just wanted to mention it
[19:15] <ogra_> i only recognized it above 100% before
[19:16] <philipp1> Hi everyone,
[19:17] <philipp1> I'm trying to port ubuntu-touch to a Hardkernel odroid; how do install it after building? The reboot-recovery method seems to do nothing.
[19:19] <ogra_> sigh
[19:19] <ogra_> failed again
[19:20]  * ogra_ gives up being super annoyed... 4 days and still no usable image :(
[19:22] <davmor2> ogra_: is that a don't upgrade to r20 it will kill your phone....Oh too late you already have
[19:23] <timppa> system settings are still broken on r20
[19:23] <timppa> :(
[19:24] <timppa> sounds cannot be changed
[19:25] <davmor2> timppa: I think that is an Ubuntu-ui bug
[19:25] <davmor2> timppa: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1248646 iirc
[19:25] <timppa> davmor2: ok
[19:27] <davmor2> timppa: it happens all over not just on settings in other words.  For example if you install and open Solitare Games you get no game chooser either
[19:27] <timppa> ah, I see
[19:28] <timppa> davmor2: Do you know if it would be hard to implement a way to add own ringtones on ro images? ie. /home/phablet/Ringtones to be traversed?
[19:29] <davmor2> timppa: no idea I'm afraid
[19:30] <timppa> davmor2: ok
[19:41] <timppa> :( Unity8 seems to hog 80-100% CPU on r20
[19:42] <timppa>  1780 phablet   20   0  518760 148660  83004 S  90.2  7.8   3:27.41 unity8
[19:43] <timppa> does not want to settle down
[20:17] <xnox> stgraber: rsalveti: i've changed build-emulator-sdcard.sh to fetch tarball from system-image.u.c as that tarball matches sytem-image mounting better (e.g. paths & symlinks are in-place)
[20:17] <rsalveti> xnox: sure, did you add the logic to find the right file name using the right channel?
[20:17] <rsalveti> xnox: in theory we want to use the devel channel, right?
[20:18] <xnox> rsalveti: yes. I've added a small python script that parses devel/mako/index.json and prints the URL of the latest full tarball.
[20:18] <rsalveti> would be nice to have an option to also allow people to specify the devel-proposed one, or a different channel
[20:18] <xnox> rsalveti: and build-emulator-sdcard calls that script to get the url for the tarball.
[20:18] <xnox> rsalveti: yeah, maybe =)
[20:18] <rsalveti> xnox: please add a license to those scripts, if possible
[20:18] <xnox> rsalveti: ack.
[20:20] <rsalveti> but cool, let me test
[20:20] <rsalveti> just need to remember to also install your new python script when updating the android package
[20:27] <xnox> license headers added.
[20:30] <rsalveti> xnox: would also be nice if we could print which version it is using as base, and afaik that info is already part of the json file
[20:31] <rsalveti> but you're expecting the return from that script to be the url, so it might need a bit more changes
[20:31] <rsalveti> xnox: thanks :-)
[20:31] <xnox> rsalveti: yes, I could print it to stderr for example.
[20:32] <rsalveti> yeah, that might already be enough
[20:44] <morphis> rsalveti: btw. one other thing: does the gstreamer hybris work still depend on surface flinger or the ubuntu platform api?
[20:44] <rsalveti> morphis: not anymore
[20:44] <rsalveti> morphis: we still need to fix a couple of critical bugs and do a minor clean-up
[20:44] <rsalveti> then we can push it forward
[20:45] <rsalveti> it's currently depending on the platform-api when you use it with playbin (using gst-lunch)
[20:45] <rsalveti> *gst-launch :-)
[20:45] <rsalveti> basically to request a window/surface
[20:45] <rsalveti> but in the qt use case, it just asks qt to give the surface id
[20:45] <rsalveti> that's why it works even when we use it with mir
[20:46] <morphis> ok, I will give it a try soon
[20:47] <morphis> rsalveti: as basically only the qt case is interesting for me
[20:47] <morphis> (at least for now)
[20:47] <rsalveti> right, cool
[20:48] <rsalveti> jim should be able to fix the remaining critical issues this week still
[20:48] <rsalveti> and after I'm done with the emulator my next task is rebasing/upstreaming hybris
[20:48] <morphis> yeah :)
[20:49] <morphis> but from I've seen the most important part is the compat layer which we have already through the phablet environment
[20:49] <rsalveti> yeah
[20:52] <Nothing_Much> How do I compile libhybris with Android headers?
[21:59] <Nothing_Much> Anybody know how to get the android-version.h to work when compiling?
[22:02] <Stskeeps> check extract-headers.sh
[22:06] <Nothing_Much> Stskeeps: What am I supposed to look for in there?
[22:09] <Nothing_Much> Hang on a sec
[22:09] <Nothing_Much> Where are the headers located in the package: android-platform-headers
[22:10] <Nothing_Much> Oh I got them
[22:11] <Nothing_Much> It's in /usr/include
[22:15] <Pavel_> helo all
[22:15] <Pavel_> i need litel info pls
[22:16] <Pavel_> ?
[22:25] <barry> stgraber, ogra_ well, for mysterious reasons, my test failures have disappeared.  seriously, i can no longer reproduce them and i don't exactly know why.  in any case, i'm going to build a new s-i 2.0 and test it on my device.  i'll be getting back together with mandel_ in the morning to see where we are.
[22:26] <mandel_> I'll do some work on trying to find possible cases where we append to the file bogus data, that could explain the 115% issues that might be related
[22:35] <TechieElf> Any devs active?
[22:37] <popey> TechieElf: wassup?
[22:37] <popey> quite a few people are on vacation today
[22:37] <TechieElf> I'm a student so well, yea. I'm new to the crowd and I've actually taken over the XT907 port
[22:43] <TechieElf> popey, I haven't the slightest clue where to start with this port. I'm not familiar with ubuntu touch's coding or where the previous developers left off