[00:06] <sergiusens> TechieElf, I don't really want to get into researching what he spun off upon; maybe you can use the porting guide and brind in his device specific and vendor specific parts?
[00:08] <TechieElf> sergiusens: But it appears that all the source is present? Also, I've compared the files inside the two phablet zips and they're all the same, just some vary in size by small amounts. I need to "flip" this anyway so how do I go about doing so?
[00:10] <sergiusens> TechieElf, just follow the porting guide
[00:10] <sergiusens> TechieElf, but instead of brunching for your device just add the device repo from the manifest in that guys github
[00:10] <sergiusens> TechieElf, same thing for the binary blobs
[00:12] <TechieElf> sergiusens, I've done that. That's where I am now. Added his repo, blobs included. Now what? I still suffer an ungodly boot loop :P
[00:13] <TechieElf> Maybe this helps, his port still uses saucy-preinstalled-phablet-armhf.zip
[00:13] <sergiusens> TechieElf, so you did not do curl -L -o .repo/local_manifests/phablet.xml -O -L https://raw.github.com/razrqcom-dev-team/android_local_razrqcom/phablet/phablet.xml
[00:14] <TechieElf> sergiusens, actually I have.
[00:14] <sergiusens> TechieElf, I'm not sure what the implications of  <remove-project name="CyanogenMod/android_build" /> are
[00:15] <TechieElf> Apparently they are replaced with ubuntu counterparts?
[00:15] <TechieElf> I noticed further into the xml
[00:15] <sergiusens> TechieElf, and then this <project path="build" name="STS-Dev-Team/android_build" remote="gh" revision="phablet" >
[00:15] <sergiusens> TechieElf, clearly might have the wrong build rules
[00:16] <sergiusens> TechieElf, that's why I said; only keep the DEVICE and VENDOR parts
[00:16] <sergiusens> manually check the diffs from the BUILD part with what is latest
[00:16] <TechieElf> sergiusens: How do I go about that?
[00:17] <sergiusens> use a diff tool (I use meld)
[00:18] <sergiusens> git clone git@github.com:STS-Dev-Team/android_build.git
[00:19] <sergiusens> and diff that against the 'build' dir you'd get if you haven't done the manifest addition
[00:20] <sergiusens> TechieElf, or just check https://github.com/STS-Dev-Team/android_build/commits/phablet
[00:21] <TechieElf> It looks like STS merged with CM so it shouldn't be a problem?
[00:22] <sergiusens> TechieElf, or merge back the changes from git://phablet.ubuntu.com/CyanogenMod/android_build.git into the tree you have
[00:26] <TechieElf> sergiusens: I'm lost.
[00:27] <sergiusens> TechieElf, reason for which I mentioned you should start from scratch from the guide to get a feel of the whole thing
[00:27] <TechieElf> sergiusens: so should I breakfast instead of using his manifest?
[00:28] <sergiusens> TechieElf, if it's on cyanogen, yes, if not, create a manifest similar to that but only with the vendor and device parts
[00:29] <TechieElf> sergiusens, it's an officially supported cm device so it should be.
[00:38] <TechieElf> Oh my, the lovely 15GB phablet-dev-bootstrap download :D
[00:46] <sergiusens> TechieElf, no need to delete it
[00:46] <TechieElf> But I already contaminated it with the old files?
[00:46] <sergiusens> TechieElf, just remove the manifest in .repo/local_manifests/
[00:47] <TechieElf> sergiusens: Oh alright
[00:50] <TechieElf> sergiusens: "Trying dependencies-only mode on a non-existing device tree?" comes out from breakfast
[01:06] <matv1> Sorry if I have overlooked infof but can Anyone tell me the exact status of the email core app?
[01:06] <matv1> acoording to lp its no longer under active development. Does that mean an email solution is abbandoned as a canonical driven effort and left up to the community? If so, that point should maybe made more clear.
[01:24] <helbuns> hey guys, im trying to install ubuntu touch in a galaxy nexus on ubuntu 13.10. my error hangs on "wating for device" after "sudo fastboot oem unlock". im fuly updated and a fresh install. my phone in usb debugging on developer unlocked.
[01:31] <helbuns> any idea i should try? i guess another computer?
[01:41] <matv1> helbuns what is the device screen showing?
[01:44] <helbuns> it shows no change
[01:44] <helbuns> it just stays on fastboot like it wasnt sent anything
[01:52] <matv1> helbuns what does the terminal command 'adb devices' output
[02:02] <ivo3> Hello, I need some help related to UT porting to new device
[02:02] <ivo3> I followed porting guide, was able to boot UT - but I am stuck with some mount/partition problems
[02:03] <ivo3> Is there anybody that can help?
[02:03] <ivo3> I am trying IFC6410 - I have working Android 4.1 for it
[03:28] <helbuns> my ubuntu touch seems to be stuck on "Rom may flash stock recover on boot" am i supposed to put input at this time??
[03:29] <helbuns> my host says waiting for install to finish on device do not unplug
[05:09] <AskUbuntu> ubuntu touch for aakash 2 ubislate tablets | http://askubuntu.com/q/380194
[08:10] <Nothing_Much> Could somebody let me know whenever it's possible to actually like.. use libhybris on the Ubuntu desktop?
[08:49] <AskUbuntu> How to change the Ubuntu installation to read-write mode on a mobile device | http://askubuntu.com/q/380258
[10:33] <mkozjak> hi
[10:41] <mkozjak> phablet-flash ubuntu-system --channel devel // will this ensure i'll get the latest image?
[10:42] <mkozjak> oh, devel-proposed
[11:25] <om26er> ogra_, Hi! got a minute ?
[11:25] <om26er> or a few seconds.
[11:26] <ogra_> shoot
[11:26] <om26er> ogra_, I think I got a bit lost while trying to add unity8-autopilot to seed. If you come close to the seed code in the coming days can you please also add it to the seed ? :)
[11:26] <ogra_> yeah, no prob
[11:26] <om26er> thanks
[11:31] <arunkumar413> Can I port ubuntu touch to any android mobile
[11:31] <arunkumar413> Or are there any prerequisites
[11:33] <ogra_> arunkumar413, see the link in the channel topic
[11:33] <ogra_> (the porting guide)
[11:34] <janimo> arunkumar413, the prerequisites are having a working android build and the sources to it and the kernel, so you can add the ubuntu specific changes
[11:35] <arunkumar413> Working android build? What does this means.
[11:35] <janimo> arunkumar413, the device you want to port to successfully runs android
[11:36] <arunkumar413> I have an android mobile and I want to port touch to it
[11:37] <mardy> does anyone know how to get the (standard) output of a click application? http://askubuntu.com/questions/380310/how-to-get-the-output-stdout-stderr-of-a-click-application
[11:41] <AskUbuntu> How to get the output (stdout/stderr) of a click application? | http://askubuntu.com/q/380310
[11:42] <janimo> ogra_, do you know if flashing kitkat on the N4 would prevent it being flashed with 4.2 again? radio/bootloader issues
[11:43] <ogra_> mardy, ~/.cache/upstart/$APP_ID.log
[11:43] <janimo> I'd like to try 4.4 but make sure I can still flash Ubuntu's 4.2 based image
[11:43] <ogra_> janimo, no idea, but i wouldnt see why fastboot would be replaced by such an upgrade
[11:44] <janimo> ogra_, indeed, I just want to be extra cautious :)
[11:44] <ogra_> you should still be able to fastboot flash
[11:44] <janimo> right, I did not know whether fastboot has some default where it won't allow radio or bootloader downgrades though
[11:44] <mardy> ogra_: thanks! Would you like to reply in askubuntu, so I can increase your karma? ;-)
[11:45] <janimo> ogra_, do you know if anyone has an N5 and is building the ubuntu kernel for it, in case touch is ported to it?
[11:46] <mardy> ogra_: ah, it seems to be  ~/.cache/upstart/application-click-$APP_ID.log, precisely
[11:46] <ogra_> janimo, nope, dont know ... i have an N5 but that will stay on android ... until i get a company N5
[11:48] <ogra_> mardy, done
[11:52] <mardy> ogra_: thanks!
[12:03] <mardy> jdstrand: ping
[12:10] <jdstrand> mardy: hey
[12:11] <mardy> jdstrand: hi! I just wrote a comment to bug 1245903
[12:12] <jdstrand> mardy: ack. I have it queued up. I'll make the adjustment
[12:13] <mardy> jdstrand: thanks
[12:14] <jdstrand> np
[12:15] <leosam> Hi! I tried to build the ubuntu touch emulator on saucy and followed the instructions on the wiki. When running "phablet-dev-bootstrap emulator" I get an error could not verify the tag 'v1.12.7' (can't check signature: public key not found).. can anyone help?
[13:01] <pitti> salem_, boiko: would you mind top-approving https://code.launchpad.net/~pitti/dialer-app/drop-connected-tests/+merge/194837 ? I re-started a jenkins run, seems the failure in otto got fixed
[13:02] <boiko> pitti: sure
[13:02] <pitti> boiko: that way this trivial thing doesn't need two runs; thanks!
[13:10] <pitti> boiko: btw, please don't let the PS "approval" in https://code.launchpad.net/~pitti/dialer-app/maguro-tests/+merge/193774 fool you: tests didn't run on maguro, I asked fginther
[13:12] <pitti> boiko: wrt. drop-connected-tests, do you want to do something similar for messaging-app? its connected_tests also really don't do much
[13:15] <boiko> pitti: yeah, I guess they are obsolete too, but I can remove them myself if you have other stuff to do, don't worry
[13:16] <pitti> boiko: ack
[13:16] <pitti> boiko: I'm mostly asking because I'll send MPs for moving the tests to py3 soon
[13:16] <pitti> boiko: turns out connected_tests would need some update, the phonesim tests should mostly work (trying right now)
[13:16] <pitti> boiko: I have a patch for dialer-app already (trivial)
[13:17] <pitti> boiko: these are blocked by https://code.launchpad.net/~robru/autopilot/drop-upa/+merge/196034 and bug 1253627, but once these land, we can move a lot of tests to py3
[13:17] <pitti> boiko: (mostly FYI for you at this point)
[13:17] <mkozjak> what am i supposed to choose when phablet-flash ubuntu-system --channel devel --bootstrap reboots my phone? where is the image stored?
[13:23] <boiko> pitti: yep, we need the emulators ported indeed
[13:23] <boiko> pitti: I will do the removal of connected tests right now (before I forget it)
[13:23] <pitti> boiko: no porting to do, just shipping them where py3 can find them
[13:23] <pitti> boiko: thanks
[14:01] <nik90> mkozjak: you do not need to choose anything
[14:02] <nik90> mkozjak: just let the process complete
[14:02] <nik90> mkozjak: although I am not sure about the bootstrap option
[14:05] <mkozjak> nik90: there's no progressbar or anything
[14:05] <mkozjak> but it doesn't matter anymore, i crapped everything up
[14:22] <cwayne> cjwatson, is the ${id} part in a click hook pattern be modified? i.e. if i want just the app basename, without the com.ubuntu.developer.<user>?
[14:23] <cwayne> like in my click hook's target, could i specify something like ${id|cut -d. -f1
[14:23] <cjwatson> Why would you want that?  You aren't supposed to pick that name apart.
[14:23] <cjwatson> And no, you can't do that
[14:24] <cwayne> cjwatson, because i'm trying to make click hooks for account-plugins, which expect a directory <base>/qml-plugins/<provider-name>
[14:24] <cwayne> where provider name would be *somewhere* in the ${id}
[14:24] <cjwatson> Why wouldn't the provider name just be the whole id?
[14:24] <cjwatson> If it needs a short name then that should be inside the file
[14:25] <cjwatson> It's critically important that the id not be mangled or shortened for symlinks, because that opens the possibility of clashes.
[14:25] <cjwatson> So you need to find another way, I'm afraid.
[14:25] <cwayne> cjwatson, because the provider is going to be something like 'fitbit', or 'google'
[14:25] <cwayne> not com.ubuntu.developer.cwayne18.account-plugin-fitbit
[14:25] <cjwatson> (Consider com.ubuntu.developer.<user-1>.name, com.ubuntu.developer.<user-2>.name
[14:25] <cjwatson> )
[14:25] <cjwatson> If you need a short name then you need to put that inside the file, not rely on the file name.
[14:25] <cjwatson> And modify account-plugins to support that if need be.
[14:26] <cjwatson> Then account-plugins can do something domain-specific to deal with clashes; click doesn't have the domain-specific knowledge to do that
[14:29] <cwayne> mardy, ping
[14:29] <mardy> cwayne: hi!
[14:30] <cwayne> mardy, heya!  i'm working on the account-plugin click-hooks again, and i've run into a bit of an issue with the qml-plugins dir
[14:30] <ScopeParking> Qu. Is it possible to connect to a HTTP Server with ubuntu-touch ?
[14:31] <cwayne> mardy, namely, that o-a expects the dir structure to be qml-plugins/<provider-name>, but click hooks won't support naming like that
[14:33] <chinmaya_n> ScopeParking: how could we view websites with out that??
[14:34] <ScopeParking> ok .. your right !
[14:34] <ScopeParking> leaves .. disgruntled.
[14:34] <brendand> what's the current status of unity8, is it still a seperate app or is it actually a desktop yet?
[14:34] <mardy> cwayne: I'm going to deeply change that
[14:35] <cwayne> mardy, ah, to what? :)
[14:35] <mardy> cwayne: well, I didn't think it over completely yet
[14:36] <mardy> cwayne: first of all, I'll allow plugins to be a binary file (in case someone wants to encrypt application keys inside them)
[14:36] <cwayne> mardy, so one binary instead of 4 separate files?
[14:37] <mardy> cwayne: oh, no, the xml files will still be needed
[14:37] <cwayne> yeah, that makes sense
[14:38] <mardy> cwayne: I'm thinking of moving qml plugins to /usr/share/accounts/qml-plugins/<click-id>.qml, and then have binary plugins somewhere under /usr/lib -- then you choose which one to use
[14:38] <cwayne> hmm
[14:39] <cwayne> mardy, but some qml-plugins require more than one file
[14:39] <mardy> cwayne: I guess we can't do anything about it, unless click starts supporting that
[14:40] <mardy> cwayne: actually you are right, it's probably better to fix click before introducing this, so to be able to use /usr/share/accounts/qml-plugins/<click-id>/Main.qml
[14:41] <cwayne> mardy, right.  so we'd need two things right? a) click to support multiple files (or just a recursive option), and b) u-s-s-o-a to look in /usr/share/accounts/qml-plugins/<click-id>
[14:44] <ogra_> nik90, happpy birthday !!!!
[14:45] <mkozjak> nik90: gonna try installing again via phablet-flash ubuntu-system --channel devel --no-backup now again
[14:45] <mkozjak> nik90: should there be some progress bar at once?
[14:45] <mkozjak> nik90: happy birthday, btw, if it's your birthday
[14:47] <Ursinha> popey, hello :) so, I have a weird bug here in mako img r27, after a while whenever I'm using facebook webapp and click on a link, the browser tries to open file:///usr/share/webbrowser-app/'https:.....' instead of the link directly
[14:47] <Ursinha> how can I debug this? is this known?
[14:48] <nik90> ogra_: thnx :)
[14:48] <nik90> mkozjak: thnx
[14:49] <ogra_> Ursinha, probably oSoMoN can help
[14:49] <mkozjak> nik90: about the progress bar when installing, should it be displayed?
[14:49] <ogra_> (he works on the browser afaik)
[14:50] <oSoMoN> Ursinha, interesting, I haven’t seen this issue before, can you file a bug at https://bugs.launchpad.net/webbrowser-app/+filebug with steps to reproduce?
[14:51] <nik90> mkozjak: I generally install using phablet-flash ubuntu-system --channel devel --no-backup
[14:51] <nik90> mkozjak: generally you see some loading text in the boot
[14:51] <daker> Ursinha: i think it's a bug, i have seen the same thing some days ago; the browser tries to open /usr/share/webbrowser-app/MYURL
[14:52] <Ursinha> daker, yes, that
[14:52] <Ursinha> daker, I have a nexus 4, or mako
[14:52] <mkozjak> nik90: --no-backup is deprecated, --bootstrap is advised to be used instead (whatever that is)..
[14:52] <Ursinha> not sure it makes a difference though
[14:52] <nik90> mkozjak: ah..I wasnt aware of that
[14:53] <mardy> cwayne: yep
[14:53] <Ursinha> oSoMoN, sure, will file a bug. Can you point me to instructions to collect more information so I can attach them to the bug?
[14:53] <nik90> mkozjak: I am installing an image soon..will check it out
[14:54] <mkozjak> nik90: ok!
[14:54] <mkozjak> nik90: i'm trying this on galaxy nexus
[14:54] <cwayne> mardy, well..
[14:55] <cwayne> ~/.local/share/qml-plugins/<click-id> that is :)
[14:55] <mardy> cwayne: absolutely :-)
[14:55] <cwayne> mardy, but let me know if there's any way i can help test to get this sorted out sooner than later :D
[14:58] <mkozjak> nik90: oh yeah, i just had to wait, it's installing now
[14:58] <nik90> mkozjak: I was just about to say that
[14:58] <nik90> mkozjak: I just reach ed the loading screen
[14:59] <nik90> mkozjak: but for sometime it was in the boot menu and I wasnt sure what to do :P
[14:59] <mkozjak> nik90: the problem is there's nothing of indicators when the image is transferred, and that confused me
[14:59] <mkozjak> yes, that's exactly what it felt like :D
[15:00] <oSoMoN> Ursinha, not sure there’s much additional debug output we can get for this type of bug, the webkit inspector is not gonna help in this case
[15:00] <Ursinha> oSoMoN, right, okay
[15:01] <oSoMoN> Ursinha, however if we have a way to reproduce reliably, it should be relatively easy to fix
[15:03] <daker> oSoMoN: well i remember the browser tries to open /usr/share/webbrowser-app/something when using upstart-app-launch webbrowser-app --inspector
[15:03] <Ursinha> daker, interesting, will try that here
[15:04] <daker> Ursinha: http://daker.me/2013/11/web-apps-remote-debugging-on-ubuntu-touch.html
[15:04] <Ursinha> daker, thanks!
[15:29] <Pintknocker> Afternoon folks
[15:30] <Pintknocker> Can anyone help me with ubuntu touch installation on my nexus 7(2013)
[15:32] <ogra_> Pintknocker, there is no image for the 2013 model
[15:32] <ogra_> (unless someone on the xda forums did a port yet)
[15:33] <Pintknocker> ah okay thanks for the help
[15:33] <Pintknocker> I was running the phablet commands when I noticed Unsupported device
[15:33] <Pintknocker> thought that there was some way around that , thanks anyways ;D
[15:33] <Pintknocker> Good afternoon
[15:33] <ogra_> right, the officially supported N7 is the tegra one ...
[15:34] <ogra_> the 2013 model simply completely changed the architecture ... that requires a complete new port
[15:34] <Pintknocker> Any clues on how long till the whole touch system is released?
[15:34] <ogra_> how do you mean ?
[15:34] <ogra_> it was released with 13.10
[15:35] <Pintknocker> but it still under development
[15:35] <Pintknocker> the releases are devel releases correct?
[15:35] <ogra_> and the source is public for all bits and pieces in case someone wants to do a port to different HW
[15:35] <ogra_> well, the 13.10 release is called v1.0
[15:35] <ogra_> though indeed, thats rather focusing on giving app developers a base and the like
[15:36] <ogra_> 14.04 should be closer to what endusers want
[15:36] <Pintknocker> I see
[15:36] <Pintknocker> Well seems like I just need to be patient and await the upcoming versions
[15:36] <ogra_> (13.10 is usable as a daily driver if you can live with the rough edges though)
[15:37] <Pintknocker> Ive seen some rough comments on this one (when it comes to bugs and whatnot)
[15:37] <Pintknocker> Still wanted to give it a try
[15:37] <Pintknocker> Can you tell me if it allows you to have development environments like javajdk
[15:38] <Pintknocker> on this tablet version
[15:38] <ogra_> you can make the image writable and install anything you like from the ubuntu archive
[15:38] <Pintknocker> Awesome
[15:39] <Pintknocker> Probably seems like not such a good thing to go for but I bought it mainly not to carry my Laptop around allday plus the cables to recharge it
[15:39] <ogra_> by default it is pretty locked down though ... and tehroretically you should do development on a PC ... but that doesnt mean we didnt put in a switch for the hardcore hackers ;)
[15:40] <Pintknocker> and was going for ubuntu to find a way to develop on it
[15:40] <Pintknocker> I see xD
[15:40] <Pintknocker> Yea I know I should do so on a PC but oh well
[15:41] <Pintknocker> At the end of the day the HW we find in these devices is quite good (almost as good as netbook . not as good tho sometimes)
[15:41] <ogra_> yeah
[15:41] <Pintknocker> and Id like to see ways to take advantage of that you know..
[15:42] <ogra_> yeah
[15:42] <Pintknocker> Alright ogra_ thanks for your help, I really appretiate it ;)
[15:42] <ogra_> np :)
[15:43] <Pintknocker> Good afternoon
[16:29] <medmans> hi
[16:29] <medmans> i like to be a ubuntu touch developer , can u help me with some advices ?
[16:30] <Ursinha> oSoMoN, daker, https://bugs.launchpad.net/webbrowser-app/+bug/1253703
[16:31] <daker> Ursinha: exactly what happened to me
[16:31] <oSoMoN> Ursinha, thanks, I’ll look into it after UDS sessions
[16:32] <Ursinha> daker, interesting thing is that running with upstart-app-launch makes it easily reproducible
[16:32] <Ursinha> oSoMoN, thanks
[16:32] <daker> Ursinha: yes
[16:32] <Ursinha> ogra_, what's the number of the current image on devel? (not -proposed)
[16:33] <ogra_> Ursinha, r10
[16:34] <Ursinha> ogra_, is it numbered differently than -proposed?
[16:34] <Ursinha> -proposed is (was?) r27
[16:34] <popey> proposed is currently 27
[16:34] <popey> we just haven't released any of the images from 11-27
[16:35] <Ursinha> O_O
[16:35] <nille_> hi everybody...anyone got ubuntu-system trusty running on a nsxus 4?
[16:35] <popey> yes
[16:35] <Ursinha> okay, so this bug I just found is somewhere between 11 and 27...........
[16:36] <nille_> Unfortunately it didn work out for mei, neither using phablet flash nor installing it manually.
[16:37] <jdstrand> rsalveti: hey, do you know if there is a bug on the goldfish apparmor trace? we know about it and can of course reproduce it, but can't find the bug on it
[16:37] <nille_> Installing recovery works but after installing the preinstalled-touch-zip it just hangs after rebooting, showing "Google" and the open lock
[16:38] <rsalveti> jdstrand: yeah, I don't think I saw one for that either
[16:38] <popey> nille_: it takes a while
[16:38] <jdstrand> ok, we'll just file a new one
[16:38] <ogra_> nille_, you want to use phablet-flash ubuntu-system --channel trusty -d mako -b
[16:38] <nille_> For now I'm waiting about 2 or 3 hours
[16:38] <ogra_> do not fiddle with the zips, they are obsolete, we do not test them
[16:39] <nille_> orga_: thanks...I'm gonna try this :)
[16:39] <ogra_> they are just an interim product that people doing a new port to an unsupported device can use
[16:39] <nille_> sry...'ogra_'
[16:39] <ogra_> :)
[16:44] <popey> Ursinha: yeah, confirmed your bug here, i have two phones, one on 10, one on 27
[16:44] <Ursinha> popey, I wasn't able to reproduce it with r10, but I haven't tried to do it via shell
[16:45] <popey> 10 worked fine here
[16:45] <Ursinha> good
[16:45] <Ursinha> I added that to the bug
[16:45] <Ursinha> it's somewhere between 11 and 27
[16:49] <AskUbuntu> Wifi issue on nexus 4 16GB | http://askubuntu.com/q/380435
[17:08] <nille_> ogra_: Using "phablet-flash ubuntu-system --channel trusty -d mako -b" exits with an error: ...booting...FAILED (status malformed (0 bytes))...ERROR:phablet-flash:Command 'fastboot boot /tmp/tmp2HdNfV/partitions/recovery.img' returned non-zero exit status 1
[17:08] <nille_> Any idea what I can do?
[17:09] <ogra_> is the device actually in fastboot mode while that hgappens (biug android on screen with a huge "START" above it)
[17:23] <staplesauce> How smooth is Ubuntu Touch supposed to run on the Galaxy Nexus? I'm seeing a bunch of performance issues after my first install. The UI is very sluggish and the touchscreen inaccurate.
[17:24] <staplesauce> Also, some of the things listed on the stats page as working are not. Neither the front or rear camera seem to be functional.
[17:32] <nille_> ogra_:No it's in the recovery mode when I start the phablet-flash script...I can't start the script in Fastboot mode (adb cannot find any devices in taht mode)
[17:33] <ogra_> nille_, well, it should reboot and switch to fastboot can you see it with adb devbices ?
[17:33] <ogra_> *devices
[17:34] <ogra_> staplesauce, which image did you use ?
[17:34] <ogra_> staplesauce, maguro is generally a bit sluggish, but it got better with more recent images
[17:34] <staplesauce> Let me check which image
[17:34] <ogra_> the rear camera always worked for me (for pics, video recording is generally broken atm)
[17:34] <nille_> ogra_: yes ,sorry, I start the script in recovery mode, It runs, than the nexus reboots to fastboot and than the mentioned error appears
[17:35] <ogra_> nille_, that sounds a bit like a bad cable connection ...
[17:35] <ogra_> sergiusens, ^^^^ any other idea ?
[17:36]  * sergiusens reads
[17:36] <ogra_> error: ...booting...FAILED (status malformed (0 bytes))...ERROR:phablet-flash:Command 'fastboot boot /tmp/tmp2HdNfV/partitions/recovery.img' returned non-zero exit status 1
[17:36] <ogra_> thats the error he sees
[17:36] <nille_> Hm, ok, but shouldn't it be possible to copy the mako.touch-zip zo the sd card and select install tip in the recovery mode?
[17:36] <sergiusens> nille_, ogra_ is this a mako or maguro?
[17:37] <staplesauce> ogra, Ah, I see. I'm on 13.10 (r100)
[17:37] <ogra_> mako
[17:37] <nille_> mako
[17:37] <nille_> :)
[17:37] <sergiusens> nille_, ogra_ the clic ommand says mako, but you guys are talking about maguro
[17:37] <sergiusens> ack
[17:37] <ogra_> sergiusens, i'm also talking to staplesauce
[17:37] <sergiusens> ogra_, sorry, tired eyes :-)
[17:37] <ogra_> staplesauce, run: system-image-cli --channel trusty -b 0
[17:38] <sergiusens> nille_, from the logs, you'll see a device*.xz download, can you open that and grab the recovery.img in there?
[17:38] <ogra_> staplesauce, via adb .. that will get you the latest trusty image ... it has a bunch more fixes
[17:38] <staplesauce> orga, I'll give that a go now. Thank you!
[17:38] <ogra_> oh, and probably append -v to it
[17:39] <ogra_> else it stays completely quiet
[17:42] <sergiusens> nille_, also, forgot the error you got when the phone was locked, but it's unlocked right?
[17:42] <sergiusens> ogra_, do you remember the error you get when running this on locked devices
[17:42] <sergiusens> ?
[17:42] <ogra_> hmm, no, thats to long ago ...
[17:42] <ogra_> im an old man ...
[17:45] <nille_> sergiusens: yes, it's unlocked - I sused Cyanogen before
[17:48] <nille_> Ok, what should i do with the recovery.img?
[17:50] <nille_> sry sergiusens: ok, i extracted the recovery.img. Should I copy it via adb? If yes? Where should I copy it?
[17:50] <sergiusens> nille_, just reboot into fastboot and try to manually boot it
[17:51] <sergiusens> nille_, also, did you do any re partitioning work at all?
[17:53] <nille_> Nope, just did a factory reset...
[17:54] <nille_> sergiusens:ehm..sorry, how can I manullay boot the recovery.img?
[17:54] <sergiusens> nille_, once you extracted the file
[17:54] <nille_> *manully
[17:54] <sergiusens> fastboot boot recovery.img
[17:56] <nille_> sergiusens:...ok, tried that, result: downloading...booting...FAILED (status malformed (0 bytes)). And the devices is in recovery mode after that
[17:57] <sergiusens> nille_, wow, it failed and it worked? :-)
[17:57] <nille_> sergiusens: Amazing, eh? =)
[17:58] <sergiusens> nille_, ok, there's one thing you can do, but it would require you to flash that recovery.img instead of booting it
[17:58] <sergiusens> nille_, and wrt to the sympton, my answer is, I have no idea why that happens, fastboot is rather closed
[17:58] <sergiusens> nille_, could be from a bad cable to something wrong in the bootloader
[18:00] <nille_> sergiusens...ok, is there a way to do something like md5 check for the copyied files on the device? Or can I download them from the device and than do a check?
[18:01] <nille_> sergiusens:...sry, didn't read your previous post...yes, I have no problem with flashing the recovery.img if I know what i have to do
[18:05] <sergiusens> nille_, fastboot flash recovery recovery.img
[18:05] <sergiusens> then boot into recovery
[18:07] <sergiusens> then do the phablet-flash but without the bootstrap but with --system-image-ready
[18:07] <sergiusens> nille_, now that I see, the --system-image-ready might only be in trunk, so yuo may need to run it from bzr branch lp:phablet-tools
[18:09] <nille_> sergiusens:..ok, so that would be phablet-flush ubuntu-system --channel tristy -d mako --system-image-ready ?
[18:10] <sergiusens> nille_, yes, just typo fix your cli ;-)
[18:16] <nille_> sergiusens: ...yes, would be better...but phablet-flush says: phablet-flash: error: unrecognized arguments: --system-image-ready
[18:17] <sergiusens> nille_, that's why I said you might need trunk
[18:17] <ogra_> hmm, what phablet-tools version do you have installed ?
[18:17] <ogra_> right
[18:36] <cyphermox> rsalveti: have you tried downgrading wpasupplicant after all? for me after downgrading you still need to give NM a kick to try to connect to the GSM context... so not wpa's fault
[18:37] <cyphermox> not sure what other bugs there were and how to reproduce them
[18:39] <ogra_> cyphermox, random shutdowns on mako ... no network at all on maguro
[18:40] <ogra_> (and the random shutdowns seems to show some wlan related stuff in dmesg)
[18:57] <cyphermox> I know, I saw the output... but there is no bug open AFAIK
[18:58] <cyphermox> and has anyone tried to downgrade wpasupplicant on the systems showing this issue?
[18:58] <doanac`> rsalveti, sergiusens: is there a ppa for the emulator or is it only working on Trusty? I tried building it, but the instructions didn't produce an emulator binary
[18:59] <sergiusens> doanac`, just trusty; building from android should work if you are on the trusty branch
[18:59] <sergiusens> doanac`, you can download the deb from trusty
[18:59] <rsalveti> doanac`: the deb from trusty is fine
[19:00] <doanac`> ah - clever. thanks
[19:00] <rsalveti> doanac`: we'll be pushing it in a ppa soon
[19:00] <doanac`> virtual beers for everyone
[19:00] <sergiusens> doanac`, I think the plan is to do the same thing we do with phablet-tools, but supporting precise and saucy
[19:03] <nille_> sergiusens: hmm, ok, just tried to get the phablet-tools from trunk. Do I really need to create a launchpad id/account to get trunk?
[19:04] <sergiusens> nille_, no, just bzr branch lp:phablet-tools
[19:07] <nille_> sergiusens: trying bzr branch lp:phablet-tools I got 'Permission denied (publickey).'
[19:07] <nille_> sergiusens:...sry for troubling you with all that :-/
[19:09] <sergiusens> nille_, are you on ubuntu?
[19:11] <nille_> sergiusens: yes, saucy
[19:11] <cwayne> wouldn't it be easier to just add the phablet-team/tools ppa? isn't that much closer to trunk than whatevers in saucy universe
[19:12] <sergiusens> cwayne, well I'm on trusty, and the fix I talk about is not in yet for some reason
[19:14] <nille_> At hte very start of my attempts to get ubuntu on my nexus I did a 'add-apt-repository ppa:phablet-team/tools' already
[19:23] <mandel_> slangasek, ping
[19:23] <slangasek> mandel_: hi there
[19:24] <mandel_> slangasek, hello! so I just heard about the media service and I had some feed back from some of the developers that are working on the podcast applications (two diff ones)
[19:24]  * jdstrand is looking at a booted emulator using qcow2 images
[19:25] <slangasek> mandel_: ah, I was merely the guy summarizing the track, let me find you who actually is working on the media service
[19:25] <jdstrand> lets see if I can use snapshot
[19:25] <mandel_> slangasek, I'm going to provide a SDK plugin for downloads and they mentioned that it would be nice for the media service to be able to play downloading files from my daemon
[19:25] <mandel_> slangasek, cool, would be nice to talk about this stuff
[19:27] <slangasek> mandel_: so I don't know what session this came out of or who added it to my notes, there are no obviously-named sessions on the core track.  I guess ChickenCutlass or rsalveti will know something about where this came from
[19:27] <mandel_> slangasek, ok, else I can always make noise in the mailing lists :)
[19:28] <rsalveti> jdstrand: awesome
[19:28] <rsalveti> slangasek: mandel_: jhodapp is owning the media service
[19:28] <rsalveti> let me get a link for the session we had
[19:28] <mandel_> thx
[19:29] <rsalveti> mandel_: http://summit.ubuntu.com/uds-1311/meeting/22088/client-1311-media-service/
[19:30] <jhodapp> mandel_, need some assistance?
[19:31] <mandel_> jhodapp, kinda, in this cycle I'm going to provide a QML plugin for the download daemon that we have atm in the phone (does si upgrades and click packages downloads) so that app developers can use it
[19:31] <mandel_> jhodapp, some of the app developers (podcasting clients mainly) mentioned that they would like to be able to tell the media service to play a nor fully performed download
[19:31] <mandel_> jhodapp, so that, my daemon downloads and yours plays the podcasts
[19:32] <mandel_> jhodapp, we might need to either ignore that or think about it :)
[19:32] <slangasek> rsalveti: ah... you had me summarizing sessions that were on the client track!  ohnoes
[19:32] <jhodapp> mandel_, you want to be able to have podcast clients play a podcast without being fully downloaded, is that right?
[19:33] <mandel_> jhodapp, well, yes, but it is not me perse, I'm just working on the download manager, the developers mentioned that
[19:34] <mandel_> jhodapp, I just provide a way to perform a download in the background so that it is not stopped when the app is not longer in the foreground
[19:34] <rsalveti> slangasek: true, because that was in theory part of core
[19:34] <rsalveti> the session was using the wrong track, sorry :-)
[19:35] <jhodapp> mandel_, can you point me to some of these developers? I'd like to discuss this further with them
[19:35] <rsalveti> cyphermox: seems we're unable to reproduce that bug today, so it might just be a heisenbug
[19:35] <mandel_> jhodapp, sure I can, I talked with netcurli and Elleo
[19:36] <jhodapp> mandel_, perfect, thanks
[19:36] <ogra_> slangasek, lots of our sessions were falsely added to client instead fo core
[19:36] <mandel_> jhodapp, no problem, let me know if there is anything I need to change in the udm or if the API needs to improve in some way
[19:36] <jhodapp> netcurli, Elleo, ping me when you get a chance
[19:36] <jhodapp> mandel_, will do, thanks
[19:37] <mandel_> no problem
[19:37] <rsalveti> ogra_: just so everybody know what we're doing this cycle
[19:38] <rsalveti> :P
[19:38] <ogra_> heh
[19:38] <ogra_> we should just re-assign the WIs to the prropriate track owner ;)
[19:39] <ogra_> *appropriate
[20:08] <Patriot07> does anyone happen to have ubuntu-touch running on a nexus 5?
[20:08] <BHSPiMonkey> No support for the 2013 Nexus 7 yet, still?
[20:10] <keb> it ran on motorola defy+ :P 12.04 if i remember right
[20:40] <nille_> sergiusens, ogra_: thanks a lot for your help...switched back to precise on my desktop and tried the phablet-flash tool again...and now I Ubuntu is running on my nexus 4...although it seems I cannot connect to my AP using WPA...
[20:41] <ogra_> hmm, and i guess your desktop isnt set up wireless ? else you could just use phablet-network to copy the connection info
[20:41]  * cwayne wonders if we should move phablet-network into phablet-config
[20:42] <ogra_> cwayne, only if you update the wiki too :P
[20:42] <cwayne> no deal!
[20:42] <ogra_> haha
[20:42] <cwayne> jk, i'll add that to my task list
[20:42] <cwayne> i think it'd be good to have a cleanup of phablet-tools and related docs anyway
[20:43] <ogra_> yeah
[20:43] <sergiusens> cwayne, we should, but there are too many scripts depending on it
[20:43] <sergiusens> go get udbflash
[20:43] <cwayne> sergiusens, ah, i didn't realize that
[20:43] <cwayne> udbflash??
[20:43] <sergiusens> udbflash --channel developer-proposed
[20:44] <sergiusens> cwayne, just playing around with go...
[20:44] <cwayne> oh
[20:44] <sergiusens> coulding think of a better name
[20:44] <sergiusens> actually, it's go get launchpad.net/phablet-tools/udbflash
[20:46] <cwayne> go go gadget phablet-flash
[20:47] <sergiusens> your team must be renamed the catch phrase team :-P
[20:47] <sergiusens> anyways, doesn't do much yet; just flashes what you would flash everyday and lists all avail channels
[20:48] <cwayne> still sounds good so far :)
[21:02] <netcurli> jhodapp: ping
[21:03] <Ursinha> popey, I see here that the notification icons and the settings they should lead to are mismatched
[21:04] <Ursinha> like gps opens bluetooth settings, incoming opens battery, and others
[21:04] <Ursinha> is that expected? looks like a bug
[21:05] <jhodapp> netcurli, pong
[21:07] <netcurli> so, I am the developer of a podcast app, and we mentioned yesterday to mandel_ that it would be nice for the mediaservice to be able to play unfinished downloads
[21:08] <netcurli> so that it doesn't get confused with the total time of the audio file for example
[21:09] <jhodapp> netcurli, yeah
[21:10] <jhodapp> netcurli, the first question I would have for mandel_ then is where would such a file get downloaded to by the udm for the podcast case?
[21:14] <jhodapp> netcurli, I assume you're already familiar with how exactly a podcast works? I assume there's a standard way of getting the metadata of a particular podcast...the question is can you get that from the server before you've finished downloading the file?
[21:16] <popey> jhodapp: the metadata about the file or the metadata about the episode?
[21:16] <jhodapp> popey, the episode
[21:16] <netcurli> that should be in the feed
[21:16] <netcurli> theoretically
[21:16] <popey> jhodapp: a podcast is simply an xml file which has an <enclosure> tag which specifies a url to the audio/video file
[21:16] <jhodapp> netcurli, ah yes, I do remember that now...it's been years :)
[21:16] <popey> e.g. http://podcast.ubuntu-uk.org/feed/mp3
[21:17] <popey> Ursinha: sounds like a bug
[21:19] <jhodapp> netcurli, it shouldn't be a problem then to coordinate this info for podcast playback via the media service
[21:21] <netcurli> so the download manager tells the app were the file gets downloaded to and the app then tells the media service the file path and the metadata?
[21:22] <jhodapp> netcurli, something like that, I'll have to give it some more thought for a proper design
[21:25] <jhodapp> netcurli, I'll think about it some and get back to you
[21:25] <netcurli> ok
[21:38] <krunkpirate> Hello All
[21:39] <krunkpirate> Anybody messed with this much on the port to toroplus? I imagine not since the sprint gnex is getting old.
[21:54] <Ursinha> popey, should I file a bug against what? (better: how do I find out to which project/package should I file a bug against, re. touch stuff)
[22:02] <popey> Ursinha: https://wiki.ubuntu.com/Avengers has a good list of where to file bugs
[22:03] <Ursinha> popey, should I tag it avengers?
[22:08] <Ursinha> well, maybe no as I'm not in that list hehe
[22:08] <brendand> this page has a couple of issues: https://unity.ubuntu.com/getinvolved/development/unity8/
[22:08] <brendand> where can i file bugs?
[22:18] <popey> brendand: not sure who owns that site maybe ask in #ubuntu-unity when people are around (european/US working hours), or file a question under http://askubuntu.com/questions/tagged/unity
[22:23] <jdstrand> rsalveti: fyi, bug #1253802 with updated run-emulator.sh attached
[22:38] <Ursinha> ok, not sure if the projects are the right ones, but there you go: bug 1253810 and bug 1253804
[22:39] <cwayne> \o/
[22:39]  * cwayne runs his click app in the emulator :D
[22:39] <daker> \o/
[22:40] <popey> *\o/*
[22:40] <popey> Ursinha: will try and confirm when I get back to my phone
[22:40] <cwayne> now if only the power button worked so i could see if the usermetrics worked...
[22:40] <Ursinha> thanks popey
[22:41] <cwayne> is there a programmatic way to show the lockscreen
[22:50] <cwayne> mterry, hey!
[22:50] <mterry> cwayne, heyo~
[22:50] <mterry> heyo! even
[22:50] <cwayne> mterry, is there a programmatic way to show the lockscreen?
[22:51] <mterry> cwayne, yah...  once we split.  There's a programmatic way to hide the lockscreen today, but not show
[22:53] <mterry> cwayne, is that helpful?  Do you need something today?
[22:56] <mterry> cwayne, I have to jet.  we can talk tomorrow
[23:00] <RobbyF> Is there an email client yet?
[23:01] <RobbyF> more specifically with push notifications
[23:04] <popey> Ursinha: confirmed
[23:04] <popey> RobbyF: no
[23:04] <Ursinha> popey, does that happen on r10 as well?
[23:05] <cwayne> RobbyF, not yet
[23:05] <popey> Ursinha: no
[23:05] <Ursinha> maybe it's a good idea to tag the bugs "regression"? or that's irrelevant for you?
[23:06] <popey> yeah, it's a regression
[23:08]  * popey updates the bug
[23:15] <Ursinha> popey, last question :) are you able to save alarms in the clock app? there's a bug about it and it seems to be fixed (as in the package with the merged branches is the one in r27) but I can't save the alarm unless I change its day of week
[23:15] <popey> no
[23:16] <Ursinha> bug 1236390
[23:16] <popey> oh, lemme test again
[23:16] <popey> yeah, it doesnt work
[23:17] <Ursinha> popey, try to change the day-of-week
[23:18] <popey> huh
[23:18] <Ursinha> hehe
[23:18] <popey> yeah, that worked
[23:19] <Ursinha> now try to edit it and change to the current day
[23:19] <Ursinha> it won't let you :)
[23:19] <Ursinha> or, it will pretend it did, but nothing will change
[23:19] <popey> yeah, i changed the day
[23:19] <popey> it let me
[23:20] <Ursinha> but in the alarm list it remains with the old day
[23:20] <popey> no
[23:20] <popey> it changed
[23:20] <nik90> Ursinha: the alarm page will only let you set alarms in the future
[23:20] <nik90> Ursinha: perhaps by choosing today, the time is in the past
[23:21] <Ursinha> nik90, makes sense, but it's a bug because I might want to set it to next week, right?
[23:21] <Ursinha> or everyday, which falls in the same case (same day of week in the next week)
[23:21] <nik90> Ursinha: then you need choose weekly alarms
[23:21] <nik90> or daily alarms
[23:22] <Ursinha> nik90, right, but if I want to set an alarm to same day next week I can't
[23:22] <Ursinha> it should display an error message at least
[23:23] <nik90> Ursinha: +1 to the error message
[23:23] <nik90> I am just waiting on design to give us a official way of displaying error messages
[23:23] <nik90> been waiting for weeks now :)
[23:23] <Ursinha> nik90, right, got it
[23:23] <nik90> but you are right
[23:24] <nik90> I remember balloons also pointing this out during autopilot testing
[23:24] <Ursinha> nik90, should we file a bug so we won't forget this happens and why?
[23:24] <nik90> there is already a bug about the missing error messages
[23:24] <nik90> in clock, weather app
[23:26] <Ursinha> nik90, do you agree it is a bug to forbid creating one time alarms in the current day-of-week? or to be able to do this we use daily and remove all other days (seems wrong)
[23:27] <Ursinha> as you're not specifying the day of month, if the time is supposedly in the past so it's next week
[23:27] <Ursinha> there's no other option :)
[23:28] <nik90> Ursinha: currently one-time alarms can only be created for that week
[23:28] <Ursinha> nik90, is that a feature? :)
[23:28] <nik90> creating alarms on specific days 2 weeks later or a month later is still not supported due to the alarms SDK limitations
[23:29] <Ursinha> right, this should be written somewhere so people don't get confused like I did and start filing bugs or bugging you guys :)
[23:29] <nik90> hehe
[23:29] <nik90> it is a bug though
[23:29] <Ursinha> can I file it?
[23:29] <nik90> file it and I will ensure that it is taken to the SDK devs asap
[23:30] <Ursinha> yay, thanks :)
[23:30] <Ursinha> but I'm more concerned that the alarm doesn't work at all
[23:30] <nik90> me too :(.. but I have done everything neeeded for alarms in the clock app
[23:31] <nik90> the alarms notifications has to be done by the indicator date time service
[23:31] <nik90> which is a different upstream package
[23:31] <nik90> now that UDS is over, I will try to contact the respective devs and request them to fix the issue
[23:31] <Ursinha> thanks muchly nik90 :)
[23:32] <Ursinha> I'm currently depending on my significant other alarm clock to wake up in the morning hehe
[23:34] <Ursinha> popey, when I modify the alarm to the current d-o-w it still displays the former one in the alarms list
[23:35] <nik90> np Ursinha
[23:36] <Ursinha> nik90, bug 1253836
[23:40] <nik90> Ursinha: thnx
[23:50] <TechieElf> Anyone working in the same time zone as me? ;D need some help sorting out build errors again
[23:52] <TechieElf> Any devs active? I'm going from old-style to flipped and I need help with a build error.