[00:27]  * snwh is back (gone 00:22:35)
[00:56] <zeokila> Hi there
[00:57] <zeokila> I have a little question
[00:58] <zeokila> Is it normal that I can't find the network configuration screen seen here http://cdn2.mos.techradar.futurecdn.net//art/mobile_phones/Ubuntu/handson/network_list-580-90.jpg
[07:45] <MacSlow> Saviq, didn't want to side-track in the qa-hangout... but I've also https://code.launchpad.net/~macslow/unity-notifications/remove-actionId to clean up the notification's backend-API a bit
[07:46] <Saviq> MacSlow, cool
[07:46] <MacSlow> Saviq, and https://code.launchpad.net/~macslow/unity8/snap-decision-expansion/+merge/172091 seems to be ready too (from my side :)
[07:47] <Saviq> MacSlow, yup
[07:47] <Saviq> MacSlow, /me not gonna review that, as it's in part my code ;)
[07:47] <MacSlow> Saviq, sure... I'll try to get someone else
[07:50] <dholbach> good morning
[07:51] <MacSlow>  hey there dholbach
[07:51] <dholbach> hey MacSlow
[08:39] <JamesTait> Good morning all, happy Second Half of the Year Day! :-D
[11:51] <Onkeltem> Hi all
[11:52] <Onkeltem> I've a desktop computer with a chinese multitouch "frame" and would like to test Ubuntu on it
[11:52] <Onkeltem> I've got*
[11:53] <Onkeltem> Where can I get "iso" to get Ubuntu with touch screen support?
[11:58] <timp> hello
[11:59] <timp> My galaxy nexus stopped working :(
[11:59] <timp> after running phablet-flash -b, it no longer boots ubuntu. When I switch it on I only see the Google logo and a lock at the bottom of the screen
[11:59] <timp> but nothing happens and it doesn't react to anything I do
[11:59] <ogra_> timp, you should use the flipped image (we will switch to it by default today)
[12:00] <timp> ok
[12:00] <timp> what is the flipped image? (perhaps I missed an e-mail about that, I was on holidays last week)
[12:00] <ogra_> timp, we flipped the container model, boot into ubuntu and run android under lxc in a container
[12:00] <timp> ogra_: so phablet-flash --flipped should fix it?
[12:00] <ogra_> yes
[12:01] <ogra_> i just manually flashed the last flipeeed image here, works fine on my maguro
[12:01] <timp> adb root terminates fine, but adb shell gives me this: - exec '/system/bin/sh' failed: No such file or directory (2) -
[12:01] <timp> I am running phablet-flash --flipped now to see if it gets fixed
[12:02] <timp> I guess -b erased my fs
[12:02] <Onkeltem> Does anybody know can I unstall Ubuntu touch on a desktop?
[12:02] <ogra_> hmm, -b usually boorstraps afresh, try booting into recovery
[12:03] <timp> Onkeltem: sorry, I never tried. I guess you can install "normal" ubuntu on it and try out the touch coreapps
[12:04] <timp> Onkeltem: but probably I am not the best person to help you with this
[12:04] <ogra_> Onkeltem, you cant, there is a way to install the UI though (ubuntu touch as a whole currently requires android, but you can install the unity8 UI)
[12:04] <Onkeltem> ogra_: ah, I see. Actually, I only need touch screen support. Sure I would prefer to install some package/drivers on my 12.04 to get it working
[12:05] <Onkeltem> but I have no idea what should I install :)
[12:05] <timp> Onkeltem: did you read https://wiki.ubuntu.com/Touchscreen ?
[12:05] <Onkeltem> timp: what are "touch coreapps"?
[12:06] <Onkeltem> timp: thanks, reading....
[12:06] <ogra_> apps written for ubuntu touch (the phone/tablet OS)
[12:07] <timp> ogra_: hmm, the phone booted into "CMW-based Recovery v6.0.2.8", but my laptop is still pushing files
[12:08] <Laney> happened here too but it worked
[12:09] <timp> maybe here also.
[12:09]  * timp still waiting while looking at a green android
[12:09] <timp> at least no error messages now on my laptop
[12:12] <timp> yeah! it rebooted in ubuntu :)
[12:12] <timp> ogra_: ^ thanks
[12:12] <ogra_> :)
[12:17] <didrocks> ogra_: FYI, we had to revert to 3.9.0-7 as we have some lxc issue with otto due to latest kernel
[12:18] <didrocks> ogra_: just in case you start having troubles with some containers for the phone
[12:26] <ogra_> didrocks, lol, our newest kernel is 3.5 on touch and they are all android kernels, no worries :)
[12:26] <didrocks> ogra_: don't you pivot_root? oh, but you pivot_root to an android kernel?
[12:27] <ogra_> we only use android kernels all over (for booting ubuntu as well as running lxxc)
[12:27] <ogra_> *lxc
[12:28] <ogra_> and they dont get any mainline changes, only patches to add features or to change config
[12:28] <didrocks> ok :)
[12:28] <ogra_> didrocks, but thanks for the heads up
[12:28] <didrocks> no worries :)
[12:29]  * ogra_ wonders if there is a way to close tabs in the browser 
[12:30] <xnox> ogra_: i failed in figuring out a way..... i was expecting it to be similar to closing apps.
[12:31] <ogra_> yeah, that doesnt seem to work ... i was expecting something in the HUD
[12:31] <ogra_> but there is nothing either
[12:32] <ogra_> didrocks, note that when we got the new apparmor into our kernels, we had to hack around an issue in the lxc config
[12:32] <didrocks> ogra_: we had to disable the apparmor profile for otto, I guess because of the same issue :)
[12:32] <ogra_> i think that was a backport of the patchset you guys now have in the generic kernel too
[12:33] <ogra_> yeah
[13:10] <esigolo> have you guys saw the galaxy s4 quick menu ? is identical of ubuntu touch
[13:11] <Onkeltem> they had copystolen it!
[13:19] <user82> esigolo, screenshot?
[13:19] <cjwatson> ogra_: I've deployed my integration of do-zip-android into cdimage; I'm just going to let it run from cron, since that's due to start in 13 minutes anyway, but I'll keep an eye on logs
[13:19] <cjwatson> ogra_: /srv/cdimage.ubuntu.com/utouch-android/ exists now
[13:20] <cjwatson> (Hopefully setting the group-writable bit on everything under that won't matter)
[13:20] <ogra_> cjwatson, well, until we clean up the mess i made in current i guess it will fail at the samme setp of looking for a link as it did the last two days
[13:21]  * ogra_ will switch it back to links in the dir before the build finishes 
[13:21] <rsalveti> ogra_: stgraber: how to the phablet user to access files under /dev/socket/?
[13:21] <cjwatson> ogra_: I didn't look at the reasons behind that, but it won't necessarily fail like that, no.
[13:21] <rsalveti> that's a link to the container fs, but via proc
[13:21] <ogra_> rsalveti, ? can you elaborate ?
[13:22] <rsalveti> ogra_: as a user, you don't have read/write permission to any file under /dev/socket
[13:22] <ogra_> tsdgeos, thats a loink to the actually running container
[13:22] <ogra_> *link
[13:22] <ogra_> err
[13:22] <ogra_> rsalveti, indeed
[13:22] <tsdgeos> ah :D
[13:22] <ogra_> rsalveti, if you wouldnt, ofono wouldnt work
[13:22] <cjwatson> ogra_: Oh.  Yeah, you did make a mess of that, actually :)
[13:22] <rsalveti> ogra_: ofono runs as root
[13:22] <ogra_> cjwatson, i did, before i understood how it works
[13:23] <cjwatson> ogra_: Let me fix that up
[13:23] <ogra_> rsalveti, then we need to change permissions i'd say, i was under the impression having android do that would be fine
[13:23] <cjwatson> ogra_: Why can't it just be a single link to 20130630 now?
[13:23] <ogra_> cjwatson, it definitely can
[13:24] <cjwatson> ogra_: OK, I'll apply that
[13:24] <cjwatson> (done)
[13:24] <ogra_> thanks !
[13:24] <rsalveti> ogra_: I want the phablet user to access /dev/socket/property_service, but it can't even access /dev/socket
[13:25] <rsalveti> ogra_: guess because it's a link to /proc
[13:26] <esigolo> user82: take a look http://www.youtube.com/watch?feature=player_embedded&v=daM-3wF3-_M#at=256
[13:26] <esigolo> 4:16
[13:26] <ogra_> rsalveti, well, proc is accessible, the root subdir issnt for some reason
[13:27] <rsalveti> ogra_: yup, that's why my question :-)
[13:27] <ogra_> rsalveti, i guess we need stgraber for that :)
[13:27] <ogra_> i never noticed that before
[13:31] <rsalveti> ogra_: hm, flashed the latest and got android with adb shell
[13:32] <ogra_> rsalveti, that cant be
[13:32] <rsalveti> ogra_: well, just flash it
[13:32] <ogra_> we even remove the adbd binary on the android side on startup of the container
[13:32] <ogra_> i just did
[13:32] <ogra_> runs fine on both devices i have (maguro, grouper)
[13:33] <rsalveti> yeah, it makes no sense
[13:34] <rsalveti> ogra_: must be something local here, let me reflash
[13:34] <ogra_> looks like you have the wrong boot.img
[13:34] <rsalveti> yeah
[13:35] <rsalveti> once we switch officially we need to get -b working as well, for a quick way to do a clean flash
[13:36] <iBelieve> popey: ping
[13:37] <popey> hey iBelieve
[13:38] <iBelieve> popey, will there be a file manager meeting this Thursday since it is Independence Day here in the US?
[13:40] <popey> iBelieve: sure will
[13:40] <iBelieve> popey, okay. I probably won't be able to be there.
[13:40] <popey> no problem iBelieve
[13:44] <rsalveti> ogra_: working fine after a reflash, something went wrong here
[13:51] <esigolo> is true wifi and bluetooth doe not work at same time on nexus 4?
[14:04] <stgraber> rsalveti, ogra_: right, a user can't see /proc/<pid>/root of a process that doesn't match it's uid, that's one of the many reason why symlinking to /proc/<pid>/root/<something> or bind-mounting it is a bad idea
[14:05] <stgraber> would cp -a work there or are those real sockets where you'd end up pointing to something else than the original socket?
[14:06] <rsalveti> stgraber: right, I believe a cp would already work
[14:06] <ogra_> they are real sockets needed for communication
[14:07] <ogra_> rsalveti, i doubt cp would work, you will lose the endpoint
[14:07] <rsalveti> yeah, not sure, need to try
[14:45] <cjwatson> ogra_: OK, I think I've got it all in shape now, and cdimage understands what's going on well enough to make current a symlink again
[14:46] <cjwatson> ogra_: I'd appreciate confirmation that the resulting images actually work as expected, of course
[14:47] <ogra_> cjwatson, syncing ... we might need to rename the bootimg files though :/ ... unless we change "phablet-flash -b"
[14:47] <cjwatson> ogra_: I didn't change any of the output file names; what's there now is what was there before
[14:47] <cjwatson> So if we need to rename them now then it's unrelated to the work I just did
[14:48] <ogra_> yeah
[14:48] <ogra_> oh, .htaccess seems to be missing icons for the bootimg files ... but thats rather minor
[14:49] <cjwatson> Huh, the AddIcon docs lie
[14:49] <cjwatson> https://httpd.apache.org/docs/2.2/mod/mod_autoindex.html#addicon says I can use a wildcard expression
[14:50] <ogra_> (i didnt look at the file, just at the webpage)
[14:50] <cjwatson> Oh, maybe that needs to be *.bootimg-* rather than .bootimg-* then
[14:50] <cjwatson> Yeah
[14:51] <cjwatson> Fixed
[14:53] <cjwatson> ogra_: So why do the bootimg file names suddenly need to be changed now when they were fine before?
[14:53] <cjwatson> Nothing in phablet-tools seems to have any matches for bootimg ...
[14:54] <ogra_> well, phablet-flash just uses the boot.img notation
[14:54] <ogra_> or -boot-armel+$subarch.img
[14:55] <cjwatson> Oh, you mean to sync up with ubuntu-touch-preview
[14:55] <ogra_> cjwatson, well, phablet-flash -b bootstraps the device via bootloader flashing of img files (versus that actual flashing process that uses zips which contin these img files)
[14:55] <cjwatson> So IOW this never worked in ubuntu-touch?
[14:56] <ogra_> we never used the files from ubuntu-touch for botstrapping yet
[14:56] <cjwatson> It's easy enough to rename them, or to create links.  Which do you prefer?  Does anything currently look at the *.bootimg-* names?
[14:56] <ogra_> but with the full switch and ubuntu-touch-preview going away we need to switch over
[14:57] <ogra_> the do-zip script did ... nothing apart of that
[14:57] <ogra_> links woudl be fine
[14:57] <cjwatson> If nothing other than do-zip-android cared, then we should rename
[14:57] <cjwatson> Because that's now fully incorporated into cdimage
[14:57] <ogra_> i wanted to keep the boot.img files that contain an ubuntu initrd easily distinguishable, until we fully switch
[14:57] <ogra_> thats why i chose a different name
[14:58] <cjwatson> Is that an argument against renaming now?  (Sorry, finding it a bit hard to follow.)
[14:59] <ogra_> cjwatson, no, just rename or link as you like
[15:00] <cjwatson> OK, thanks.  I'll grab some coffee and sort that out
[15:01] <ChristWahyu> hi ;)
[15:01] <cjwatson> Much easier to be sure of things now that this has test cases
[15:01] <cjwatson> Well, a test case
[15:01] <ogra_> :)
[15:02] <ogra_> and much better to only have one image too :)
[15:03] <ChristWahyu> hello ? anyone ?
[15:05] <mhall119> hello ChristWahyu
[15:05] <esigolo> Hello
[15:05] <ChristWahyu> oh, how are you ? :)
[15:06] <esigolo> fine and you?
[15:06] <ChristWahyu> me too :)
[15:08] <esigolo> :)
[15:08] <ChristWahyu> but i wan't to ask how do i adding content like images, videos,etc on my ubuntu touch device ? :)
[15:10] <esigolo> ChristWahyu: https://wiki.ubuntu.com/Touch/ReleaseNotes#Adding_Content
[15:10] <esigolo> ChristWahyu: is a tutorial very easy to follow
[15:10] <esigolo> if you need some more help
[15:10] <esigolo> just ping me
[15:11] <ChristWahyu> ok ;) i will ping you
[15:12] <esigolo> i'm gouing to grab some food now ! but brb
[15:13] <ChristWahyu> all right be careful esigolo :)
[15:16] <ZDmitry> balloons: ping
[15:17] <balloons> ZDmitry, pong, but I might need a min ;-)
[15:17] <ZDmitry> balloons, no problem )
[15:19] <balloons> ZDmitry, go for it ;-)
[15:21] <ZDmitry> balloons, we have MP: https://code.launchpad.net/~hiroshidi/ubuntu-terminal-app/autopilot-header-and-settings/+merge/172287
[15:22] <ZDmitry> but I have some qestions
[15:23] <balloons> ZDmitry, alright, ask away..
[15:23] <balloons> ohh sqlite3 I see
[15:23] <balloons> interesting..
[15:24] <ZDmitry> balloons, first of, is it correct to emulate chanching of orientation by expanding width?
[15:24] <balloons> That's a really good question ZDmitry! I don't think I should answer that myself. We should discuss with the autopilot folks
[15:25] <balloons> I would say yes, but I'm curious what they might say
[15:26] <balloons> So I wouldn't hold anything up and run with that for now, but we'll take it as a question to ask
[15:31] <ZDmitry> balloons, ok. Next question: I wrote functions to work with slider. Unfortunately dragging work in some weird manner, which cause using magic nums in lines 405-408
[15:31] <balloons> ZDmitry, "magic nums"?
[15:32] <balloons> The slider functions are an excellent idea, and I'm going to look to get them added to the sdk emulator
[15:33] <ZDmitry> balloons, I mean slider works perfect, but I want to slide it by 1 value per each iteration
[15:33] <ZDmitry> I have min value - 8 and max - 32
[15:34] <ZDmitry> total 14 values
[15:36] <ichigo-roku> Hi
[15:36] <ZDmitry> balloons, and as you see by code, I have non integral value (1.4 instead of 1) for teration to  get 18 and 19 font size values.
[15:38] <ichigo-roku> Ubuntu Touch will be Android based or more like GNU/Linux on PC ?
[15:38] <popey> Neither ☻
[15:40] <ZDmitry> balloons, so this is the problem. If we throw out condition "1 value - 1 iteration" and make just sliding of the thumb - all works fine!
[15:40] <balloons> ZDmitry, ahh ok.. So the slider really doesn't match up with the values rendered
[15:41] <balloons> ZDmitry, I'll have to run through it myself but I think I get what your saying
[15:42] <ZDmitry> balloons, ok
[15:43] <ogra_> ichigo-roku, ubuntu touch makes use of some android binary drivers and the android kernel, it isnt "android based"
[15:43] <ogra_> apart from the above it is a plain Ubuntu like you have on a PC
[15:43] <balloons> Kaleo, ping. elopio and myself have been working on the ubuntu sdk autopilot emulator and trying to get a couple merge requests in. Thanks for your help in having Juhapekka look at the merges, but he's now out for the week. Is there another person on your team who could help finish the reviews?
[15:44] <balloons> elopio, meet Kaleo .. Kaleo meet elopio :-)
[15:44] <elopio> thanks balloons. Nice to meet  you Kaleo.
[15:48] <ichigo-roku> ogra_, thanks
[15:49] <ogra_> while in the first images this was actually true, in the latest ones android just runs as a process in an lxc container
[15:49] <ogra_> (booting into ubuntu instead of android like it did in teh beginning)
[15:59] <cjwatson> ogra_: OK, I've done that renaming.  Are the other file name discrepancies between ubuntu-touch-preview and ubuntu-touch known and OK?
[16:05] <ogra_> cjwatson, which ones ?
[16:05]  * ogra_ check
[16:05] <ogra_> s
[16:07] <Kaleo> elopio: nice to meet you!
[16:07] <Kaleo> balloons: unfortunately no
[16:07] <Kaleo> balloons: sorry about that
[16:07] <cjwatson> ogra_: saucy-preinstalled-armel+*.zip only in ubuntu-touch-preview; saucy-preinstalled-phablet-armhf.* renamed to saucy-preinstalled-touch-armhf.*, I think; saucy-preinstalled.changelog only in ubuntu-touch-preview; ubuntu_stamp only in ubuntu-touch-preview
[16:08] <ogra_> changelog needs cdimage integration afaik
[16:08] <cjwatson> Sure, my question is whether it's a blocking problem if it isn't there :)
[16:08] <elopio> Kaleo: here I got the review, but he left it in 'Needs information'. We just need somebody to land it.
[16:08] <ogra_> ubuntu stap shouldnt be needed anymore ... phablet-flash should use the dirname and internally (once the RT is processes) we will use /var/log/installer/media-info
[16:09] <elopio> I already changed the bits about the objectName that he suggested.
[16:09] <ogra_> shouldnt be blocking ... just inconvenient until we have it
[16:09] <cjwatson> saucy-preinstalled-armel+*.zip and saucy-preinstalled-phablet-armhf.* -> saucy-preinstalled-touch-armhf.* were the main parts of my question, really
[16:10] <elopio> Kaleo: https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/toolbar_emulator/+merge/171720
[16:10] <ogra_> yeah, thats fine, phablet-flash already covers these
[16:10] <cjwatson> Oh, in fact saucy-preinstalled-armel+*.zip -> saucy-preinstalled-touch-armel+*.zip
[16:10] <ogra_> yeah
[16:11] <ogra_> thats ok
[16:11] <ogra_> i'm a bit wonderig if we shouldnt make boot be armhf+$subarch ... technically there is no armel in it anyore ... but i guess that needs sergiusens to fix that bit in phablet-tools too
[16:11] <ogra_> *anymore
[16:12] <cjwatson> /usr/share/pyshared/phabletutils/settings.py:boot_file_img = '%s-preinstalled-boot-armel+%s.img'
[16:12] <cjwatson> looks like it
[16:12] <sergiusens> ogra_: change it
[16:12] <xnox> hmmm?! ogra_ android bits compiled to armhf?
[16:12] <sergiusens> xnox: no
[16:12] <ogra_> xnox, no, but boot.img being fully ubuntu
[16:12] <xnox> ok.
[16:12] <xnox> thanks.
[16:12] <ogra_> the android armel boot.img is shipped inside the zip in /system/boot nowadays
[16:13] <ogra_> we only use it for the container now
[16:13] <sergiusens> ogra_: only the ramdisk is in /system/boot... boot.img == ramdisk + kernel
[16:13] <Kaleo> elopio: let me see
[16:13] <ogra_> sergiusens, oh, indeed
[16:13] <ogra_> well, tegh armmel bits from boot.img then :)
[16:14] <ogra_> *the armel
[16:14] <Kaleo> elopio: did he finish his review?
[16:14]  * ogra_ wonders whats up with his chromebook kbd ... 
[16:14] <Kaleo> elopio: or do you think he had other comments coming?
[16:18] <cjwatson> sergiusens: It'd be good for the phablet-tools changes that are necessary to fetch the new armhf-ish boot.img path to land before I change cdimage to publish those file names for ubuntu-touch, perhaps?
[16:19] <elopio> Kaleo: yes, he finished and I think there were no more comments. We were talking on friday before he left.
[16:19] <elopio> he said "i will be out of office next week and i am about to eod. i trust you to review and discuss with the sdk people on this :)"
[16:19] <om26er> sergiusens, Hi!
[16:19] <sergiusens> cjwatson: it's not actively used, so it's easier for you to change first, but I'll ping you for good timing in when to do it
[16:19] <elopio> he was refering to the objectName, which I finally worked around, so nothing to discuss :)
[16:20] <sergiusens> om26er: hey
[16:20] <om26er> sergiusens, can we have new release of phablet-tools in saucy (precise ppa as well). please
[16:20] <sergiusens> om26er: what do you mean? that is daily released
[16:21] <sergiusens> om26er: if it failed to do so during the weekend, look at fginther's email ;-)
[16:21] <om26er> sergiusens, seems its not, last release to saucy was 2013-06-22
[16:21] <sergiusens> om26er: on saucy?
[16:21] <om26er> sergiusens, yep, https://launchpad.net/ubuntu/+source/phablet-tools
[16:22] <cjwatson> sergiusens: OK, well, I can do it now (for tomorrow's build), if you like
[16:22] <Kaleo> elopio: I see
[16:22] <Kaleo> elopio: approved then
[16:23] <sergiusens> cjwatson: sure, sounds good to me
[16:23] <sergiusens> om26er: strange, let me check in a bit
[16:23] <om26er> sergiusens, sure, thanks
[16:24] <elopio> Kaleo: awesome. Thanks. He didn't review the other one, so I guess we should wait there.
[16:24] <Kaleo> elopio: which one?
[16:24] <elopio> Kaleo: https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/tabs_emulator/+merge/172153
[16:24] <Kaleo> elopio: right
[16:25] <cjwatson> ogra_,sergiusens: just to double-check, you mean http://paste.ubuntu.com/5817216/ ?
[16:26] <esigolo> ChristWahyu: i'm back ! success?
[16:27] <sergiusens> cjwatson: yes
[16:28] <sergiusens> om26er: the last two merges are from this weekend prior to the release, given the network issue I'm guessing it should land soon-ish
[16:28] <cjwatson> sergiusens,ogra_: thanks, done
[16:29] <om26er> sergiusens, ok, still you would need to copy stuff to the ppa manually ?
[16:29] <sergiusens> om26er: saucy goes to archives
[16:30] <om26er> sergiusens, we also want for precise since the host in the lab has precise installed on it
[16:30] <sergiusens> om26er: I know, don't worry about it ;-)
[16:30] <om26er> sergiusens, cool
[16:37] <esigolo> where can i read the ubuntu-touch roadmap?
[17:07] <lgp171188> Hey, I read Nicholas Skaggs' post on Planet Ubuntu calling for people to write autopilot test cases for the Sudoku game. Is this the right channel to ask questions regarding that?
[17:09] <ogra_> balloons, ^^^ for you :)
[17:09] <balloons> lgp171188, yes, fire away!
[17:13] <zoktar> Hello is there any command line battery monitor that would work on a nexus 7? , id like to check the battery status over ssh.
[17:20] <manoelramon> \msg rsalveti "Oi Ricardo.. tudo bem ?"
[17:22] <esigolo> zoktar: i don't now if upower is working on touch yet
[17:22] <esigolo> zoktar: if you want to give a shot http://askubuntu.com/questions/69556/how-to-check-battery-status-using-terminal
[17:23] <esigolo> or cat /proc/acpi/battery/BAT0/state, cat /proc/acpi/battery/BAT0/info
[17:24] <esigolo> it work on ubuntu don't know if it is working on touch
[17:34] <zoktar> thanks!
[17:35] <esigolo> zoktar: ope
[17:35] <esigolo> nope*
[17:36] <AskUbuntu> Ubuntu Touch Install Problem | http://askubuntu.com/q/315095
[17:41] <esigolo>  http://askubuntu.com/q/315095
[17:44] <xnox> rebootstrapped nexus7 from a full scratch and I'm loving the ubuntu logo and purple background in the clockwork mod.
[18:09] <lgp171188> Hey all, I read Nicholas Skaggs' post on Planet Ubuntu calling for people to write autopilot test cases for the Sudoku game. Is this the right channel to ask questions regarding that?
[18:10] <ogra_> lgp171188, he answered you above when you asked the same the last time
[18:11] <lgp171188> ogra_: I'm sorry I got disconnected and didn't get to see the reply. :(
[18:11] <ogra_> he is "balloons" in here
[18:12] <balloons> ogra_, :-) Thanks
[18:12] <balloons> lgp171188, yes, this is the right channel to ask. what questions do you have? Glad to hear of your interest; I'm happy to help
[18:14] <lgp171188> balloons, I am totally new to Ubuntu touch, seen some demo videos of it, read that apps are being developed for it using the SDK which is based on QML, which I am yet to learn. In case it helps, I have a Galaxy Nexus phone on which I can run Ubuntu touch and the apps. Where and how do I get started?
[18:14] <lgp171188> I will for starters read about the SDK, QML and autopilot. But is there a comprehensive guide that'd help me?
[18:14] <balloons> lgp171188, you sound like a perect canindate :-)
[18:15] <balloons> lgp171188, yes there's a lovely site to get you started
[18:15] <balloons> http://developer.ubuntu.com/
[18:15] <balloons> for qml and sdk apps; http://developer.ubuntu.com/resources/tutorials/getting-started/currency-converter-phone-app/
[18:15] <ogra_> hmm, is the claculator app broken today ?
[18:15] <balloons> and for autopilot; http://developer.ubuntu.com/resources/tutorials/quality/how-to-write-autopilot-tests/
[18:15]  * ogra_ gant get it started when testing todays flipped image
[18:16] <balloons> lgp171188, then for testing specifically this page has the full details, linking to the tutorial and the list of what's needed: https://wiki.ubuntu.com/Touch/CoreApps/Testing
[18:17] <lgp171188> balloons: I will start reading them one by one. Do I need a Ubuntu system running for any of these? Right now I am running Debian unstable and I am ready to create a Ubuntu Saucy VM if needed.
[18:17] <balloons> lgp171188, first things first though right? Have you flash your device? https://wiki.ubuntu.com/Touch/Install
[18:18] <balloons> lgp171188, yea, a saucy vm should suite you just fine. Autopilot (the testing tool) and the sdk are both built against ubuntu saucy
[18:19] <balloons> lgp171188, the folks involved in writing and testing sdk apps hang out here and a few other places #ubuntu-autopilot, #ubuntu-quality. Feel free to work your way through things, asks questions and help out
[18:19] <balloons> glad to have you
[18:20] <lgp171188> balloons, right now I am using Cyanogenmod 10.1 nightlies and I'm slightly scared to switch to Ubuntu touch full-time. Since I am just getting started is there an emulator of sorts that I can use? Of course I could make a Nandroid backup of my cyanogenmod and install Ubuntu touch if that is really needed.
[18:21] <esigolo> ogra_: qemulator is already operatiol?
[18:21] <balloons> lgp171188, if you want to save the phone stuff for later ,you can develop and test ubuntu touch apps from the desktop.. everything works on the desktop too ;-)
[18:21] <esigolo> operational*
[18:22] <balloons> I believe there is also flipped images allowing you to swap between touch and android, but someone else here should explain those
[18:22] <ogra_> blaroche_, lol ... no
[18:22] <ogra_> flipped images mean that you boot into the ubuntu root and android gets started in an lxc container
[18:23] <balloons> lgp171188, so writing a ubuntu sdk app, running it, and testing it using autopilot can all be done on the desktop
[18:23] <ogra_> vs the original approach of booting into android and running ubuntu in a chroot
[18:23] <ogra_> it has nothing to do with switching back and forth or so
[18:23] <lgp171188> balloons, that is great to hear. So I will just setup a Saucy VM and then get started. Thanks for pointing me in the right direction.
[18:23] <ogra_> (flipped is supposed to be the default from tomorrow on btw)
[18:24] <lgp171188> ogra_: So is there a concept of dual boot there?
[18:24] <balloons> ogra_, ty.. I thought so, I was just hoping for more :-)
[18:24] <ogra_> lgp171188, nope, and not planned ...
[18:24] <lgp171188> oh then let me do all my work on the desktop for now :)
[18:25] <balloons> :-)
[18:25] <ogra_> with every step we go forward the ubuntu stuff will even get more intrusive so planning for dual boot would not allow us to do a bunch of stuff
[18:27] <esigolo> ogra_: i can't see any point to dualboot since we have backup images
[18:27] <ogra_> esigolo, right, but people ask about it from time to time
[18:30] <fginther> popey, is there a weekly core-apps meeting?
[18:30] <popey> kinda. we have meetings between dpm mhall119 and myself on monday, and then separate meetings for each team through the week
[18:30] <esigolo> ogra_: we have alot of updates every week
[18:30] <popey> fginther: what do you need?
[18:31]  * Qball likes 13.04 on nexus 7
[18:31] <esigolo> ogra can you imagine installing and configuring the dualboot every ypdate?
[18:31] <esigolo> update*
[18:31] <fginther> popey, I thought it might be useful to be a part of your regular meeting to discuss jenkins needs
[18:32] <popey> great idea
[18:33] <popey> fginther: invited
[18:33] <fginther> popey, thanks
[18:34] <fginther> popey, is there a meeting for stock-ticker?
[18:34] <fginther> this week?
[18:34] <lgp171188> I am trying to install the daily image of Ubuntu touch on my Galaxy Nexus GSM (maguro) just to try out Ubuntu. I'm trying to follow the instructions in the manual installation section and there the image corresponding to my device is required. But when I check the cdimage.ubuntu.com link I find there are multiple images for my device. Which one should I use?
[18:35] <popey> fginther: there are separate meetings for each individual app, listed on the page:- https://wiki.ubuntu.com/Touch/CoreApps/Meetings
[18:35] <mhall119> fginther: 14:30 UTC on wednesday
[18:35] <lgp171188> for example the images have the name preinstalled-maguro, preinstalled-recovery* and preinstalled-system*
[18:35] <fginther> popey, mhall119 thanks
[18:35] <esigolo> lgp171188: it is alot more simple with phablet-flash
[18:36] <esigolo> lgp171188: i'm flashing using a ubuntu virtual machine
[18:36] <lgp171188> esigolo: I got that by reading through the document, but I am on Debian Jessie and I don't have my Saucy VM ready yet.
[18:36] <esigolo> lgp171188: is a galaxy nexus right?
[18:36] <lgp171188> yes
[18:37] <esigolo> lgp171188:
[18:37] <esigolo> saucy-preinstalled-armel+maguro.zip
[18:37] <esigolo> http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
[18:43] <esigolo> lgp171188: zip files :)
[18:43] <esigolo> if you want to do it with CWM
[18:44] <greyback_> sergiusens: ping
[18:45] <sergiusens> greyback_: what up?
[18:45] <greyback_> sergiusens: hey, having trouble flashing flipped saucy to my Galaxy Nexus
[18:46] <sergiusens> greyback_: checksum errors?
[18:46] <greyback_> sergiusens: ah possibly, yes. "Error while downloading, ensure connection"
[18:47] <lgp171188> esigolo: There are references to 2 images in the manual installation. should I use saucy-preinstalled-armel+maguro.zip for both? I am using CWM.
[18:47] <greyback_> sergiusens: I'd read that as it's trying to download something new and fails
[18:48] <sergiusens> greyback_: yeah, the checksum file on the server has a wrong path and my latest_build detection fails to find .x iterations
[18:48] <sergiusens> greyback_: error message could be fixed
[18:48] <greyback_> sergiusens: so it's fixed? I'm downloading again now
[18:48] <esigolo> yes zip for both
[18:49] <lgp171188> esigolo: the same zip?
[18:49] <sergiusens> greyback_: well you can fix the .md5sum files from your download and it should work
[18:49] <esigolo> lgp171188: no
[18:49] <greyback_> sergiusens: okay
[18:50] <esigolo> lgp171188: i think is saucy-preinstalled-phablet-armhf.zip
[18:50] <lgp171188> which one should I use for the 2nd step? the one named phablet?
[18:50] <lgp171188> oh ok I will use that
[18:50] <esigolo> ogra_: can you confirm that?
[18:50] <esigolo> please
[18:52] <esigolo> lgp171188: for me (nexus 4 ) is saucy-preinstalled-phablet-armhf.zip i just want to be sure if that image is for all devices
[18:54] <ogra_> esigolo, sorry, what should i confirm ?
[18:54] <Qball> I am god!
[18:54] <Qball> grass is green?
[18:54] <esigolo> LOL
[18:54] <lgp171188> Got one more doubt here. The manual installation just involves copying files to /sdcard/ as autodeploy.zip and rebooting to recovery? Nothing to flash?
[18:55] <esigolo> saucy-preinstalled-phablet-armhf.zip         is a universal image right ?
[18:55] <esigolo> lgp171188: just copy both to the sdcard
[18:56] <esigolo> flash maguro image first and the armhf
[18:56] <esigolo> rebot and enjoy !
[18:56] <esigolo> reboot
[18:56] <esigolo> just remember to copy you backup image to your pc with adb just in case
[18:56] <ogra_> esigolo, right, the armhf.zip is the ubuntu rootfs and has no hardware related bits in it
[18:56] <esigolo> ogra_: thanks
[18:57] <ogra_> the armel+$subarch.zip files are the corresponding HW specific parts
[18:58] <esigolo> thanks
[18:59] <esigolo> lgp171188: got it ?
[18:59] <lgp171188> downloading the phablet image now. Will flash both one after other and see if things work for me.
[19:00] <esigolo> lgp171188: are going to backup you device with cwm also?
[19:00] <lgp171188> I have taken a nandroid backup
[19:01] <esigolo> lgp171188: great
[19:01] <esigolo> good luck
[19:01] <lgp171188> thanks for the help ogra_ and esigolo :)
[19:01] <ogra_> :)
[19:06] <lgp171188> I flashed the phablet image without any errors. Then on rebooting the phone I got the Google logo and the screen just turned blank after that. What could be wrong? :(
[19:07] <pmcgowan> lgp171188, just reboot again
[19:07] <pmcgowan> there is a race we are fixing
[19:08] <lgp171188> pmcgowan: On rebooting, same thing happens.
[19:08] <lgp171188> but the OS booted successfully now
[19:09] <lgp171188> :)
[19:09] <pmcgowan> good!
[19:12] <lgp171188> I tried to login into the Gmail app and it asked me to install the app. Clicking that gives a network error for an itunes URL. How do I go back to go to the mobile Gmail site?
[19:15] <esigolo> lgp171188: is easy to you https://www.youtube.com/watch?v=tL9g-v4ngqE watch a hands on to learn how to slide foward and back :)
[19:19] <lgp171188> ok one more question  how do I change the time? It shows that I am in London shows the time in London. I am in India. :)
[19:21] <esigolo> lgp171188: toy have to change it from command line https://wiki.ubuntu.com/Touch/ReleaseNotes search for time zone for instruvtions
[19:21] <Gab9281> hello ^
[19:21] <esigolo> hello
[19:21] <Gab9281> okay do someone know some bugs about the touch ubuntu flash on nexus 4
[19:22] <Gab9281> when i do the phablet-flash -b command on the nexus 4 he stay stuck waiting the device
[19:22] <esigolo> after the initial flash?
[19:23] <Gab9281> yup
[19:23] <esigolo> Gab9281: just reboot it manually
[19:24] <Gab9281> i ve already tryed and it stay stuck
[19:24] <Gab9281> i am still gonna do it again
[19:24] <Gab9281> device is found on the adb
[19:25] <Gab9281> but the phablet-flash is still waiting for the device
[19:25] <esigolo> right
[19:25] <esigolo> how did you the flash
[19:25] <esigolo> ?
[19:27] <Gab9281> ive did the flash the same way explained on the website
[19:27] <Gab9281> with the automatic phablet
[19:27] <Gab9281> i ll go verify the unlock mode
[19:27] <esigolo> Gab9281: from the stock rom?
[19:27] <Gab9281> stock rom 4.2.2
[19:28] <esigolo> after flash
[19:28] <Gab9281> it didnt flashed
[19:28] <esigolo> the ubuntu phone don't boot up ?/
[19:28] <Gab9281> it just dont flash
[19:28] <esigolo> are U in recovery mode?
[19:28] <esigolo> right
[19:28] <Gab9281> going in recovery mode
[19:29] <Gab9281> ubuntu droid with a red triangle with an exclamation mark ^
[19:29] <esigolo> Gab9281: Note, 'adb devices' should not show the device as 'offline'. If it does, unplug the device, run adb under sudo on the workstation (sudo adb kill-server; sudo adb start-server), then plug the device back in
[19:30] <esigolo> Gab9281: nexus 4 right ?
[19:30] <Gab9281> yup
[19:31] <esigolo> Gab9281: download the recovery image https://developers.google.com/android/nexus/images#occamjdq39
[19:32] <Gab9281> when i go in recovery mode, theres a droid with a red triangle and an exclamation mark
[19:33] <om26er_> Gab9281, you need to enable android debugging from within android. and then accept the key that appears in the dialog, else adb will show it offline
[19:33] <Gab9281> it is normal ^
[19:33] <Gab9281> it is shown when it is started
[19:33] <Gab9281> as soon he restart with the phablet-flash command
[19:33] <Gab9281> and goes to the bootstrapper menu, it is no more
[19:34] <Gab9281> my phone is opened and it is in the adb devices command
[19:35] <esigolo> Gab9281: are you able to get on the bootloader screen
[19:35] <esigolo> ?
[19:35] <Gab9281> well it goes automatically with the flashing command
[19:35] <Gab9281> and i know how to get to it manually
[19:36] <esigolo> wait are you able to boot up the phone on android ?
[19:36] <Gab9281> yes
[19:36] <esigolo> LOL
[19:37] <Gab9281> what is it ^
[19:37] <esigolo> have u boot it up and see
[19:37] <esigolo> if debug mode is enabled
[19:37] <Gab9281> thats what i did
[19:37] <Gab9281> and it was still waiting
[19:38] <esigolo> disable
[19:38] <esigolo> remove usb
[19:38] <esigolo> enabloe it again and plug
[19:38] <esigolo> accept on dialog box
[19:39] <esigolo> run an adb devices
[19:39] <Gab9281> listed
[19:40] <Gab9281> other terminal with the flash : waiting for device
[19:40] <esigolo> is not listed?
[19:40] <Gab9281> it is listed
[19:40] <esigolo> ok
[19:40] <esigolo> cancel the other terminal please
[19:41] <Gab9281> canceled
[19:41] <esigolo> Gab9281: run it again
[19:42] <Gab9281> phablet-flash -b ^
[19:42] <esigolo> yes
[19:43] <Gab9281> device restarted on bootstrap
[19:43] <Gab9281> terminal showing waiting for device
[19:44] <Gab9281> whats next ^
[19:44] <esigolo> cancel and run it again please
[19:45] <Gab9281> device not on the ad
[19:45] <Gab9281> adb
[19:45] <Gab9281> ps : on bootstrap
[19:45] <esigolo> yes
[19:45] <Gab9281> the device is on the bootloader and no adb
[19:45] <Gab9281> command do not work
[19:45] <esigolo> sudo adb kill-server; sudo adb start-server
[19:46] <Gab9281> done
[19:46] <esigolo> run it again
[19:46] <Gab9281> device not on adb
[19:47] <esigolo> pmcgowan: can you give me a hand here?
[19:47] <esigolo> Gab9281: boot it up
[19:48] <esigolo> run sudo adb kill-server; sudo adb start-server
[19:48] <Gab9281> to put it brief : adb isnt working while in bootloader
[19:48] <esigolo> run the phablet again please
[19:48] <Gab9281> i ll do
[19:49] <Gab9281> working until bootloader pop up
[19:49] <Gab9281> again
[19:49] <Gab9281> stuck on bootloader
[19:49] <esigolo> Sweet Jesus
[19:50] <esigolo> sudo apt-get update
[19:50] <esigolo> sudo apt-get upgrade
[19:50] <esigolo> see if there is any update to phablet-tools
[19:51] <Gab9281> ubuntu core only
[19:52] <Gab9281> running on ubuntu gnome 13.04
[19:52] <esigolo> Gab9281: let me see something hold on please
[19:55] <esigolo> get it back to bootloader screen
[19:55] <esigolo> run and adb devices
[19:56] <ogra_> cjwatson, hmm, there seems to still be an issue with the .md5sum files ... they dont match whats in MD5SUMS
[19:57] <esigolo> Gab9281: have you added the proper ppa ?
[19:57] <esigolo> sudo add-apt-repository ppa:phablet-team/tools right ?
[19:59] <Gab9281> yup
[20:03] <Gab9281> do the phone flash via bootloader ^
[20:06] <ogra_> Gab9281, you can flash the recovery img via bootloader (fastboot)
[20:06] <Gab9281> doing it manually ^
[20:06] <ogra_> yes
[20:08] <ogra_> Gab9281, download http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20130701.2/saucy-preinstalled-recovery-armel+mako.img
[20:08] <ogra_> then: fastboot flash recovery saucy-preinstalled-recovery-armel+mako.img
[20:08] <ogra_> while the phone is at the bootloader
[20:08] <ogra_> afterwards: fastboot reboot recovery
[20:09] <ogra_> that should get you into a recovery session (with ubuntu logo on the screen)
[20:09] <ogra_> then just follow the install wikipage for manual installation
[20:11] <Qball> hmm
[20:13]  * popey thinks perhaps we should add a section to the wiki about what to do in these circumstances? ogra_ ?
[20:13] <popey> given it seems to be a bit of a FAQ
[20:13] <ogra_> popey, yeah
[20:15] <pmcgowan> popey, shall we add it to the install page?
[20:16] <popey> the install page needs to be broken up i think
[20:16] <popey> it seems to cover too much at the moment
[20:16] <popey> maybe a /Touch/Install for the absolute basics and /Touch/Troubleshooting which has very specific error conditions
[20:17] <popey> (and their solutions)
[20:17] <popey> e.g. putting android back on a device shouldn't be on the install page
[20:17] <pmcgowan> popey, sure as long as its clearly linked, I expect folks to be using the install page when they run into these problems
[20:17] <popey> yeah, we can link to the other pages
[20:17] <popey> I'll take a look at re-working it in the morning
[20:18] <pmcgowan> popey, ok, the need hep section is pretty obvious for this
[20:18] <popey> exactly
[20:19] <esigolo> Gab9281: sorry i had a problem with power cord twice
[20:19] <Qball> they are so hard
[20:19] <Qball> http://blog.sarine.nl/wp-content/uploads/2013/03/power-usage.jpg
[20:21] <Gab9281> when i write flashboot flash recovery *image*
[20:21] <Gab9281> it says " waiting for device "
[20:22] <Gab9281> thats where i was stuck with the phablet-flash command xD
[20:22] <ogra_> Gab9281, but you are in bootloader mode on the device ?
[20:22] <Gab9281> i was
[20:22]  * Qball hums spinning wheels
[20:22] <ogra_> (giant android on the screen, huge "START" at the top)
[20:23] <ogra_> try to prefi it with sudo then
[20:23] <ogra_> *prefix
[20:23] <Gab9281> maybe O.o
[20:24] <gab9281> back sorry
[20:26] <gab9281> -_-" sudo brought the recovery
[20:26] <gab9281> it is really the joke O.lo
[20:26] <gab9281> seems like it is -_-"
[20:27] <gab9281> i felt stupid on this one guys : the only problem was the sudo
[20:27] <esigolo> dammmm
[20:27] <esigolo> power cord is killing me
[20:27] <esigolo> sorry gab9281
[20:28] <gab9281> its okay : reminder for the touch/install website : mention sudo when theres need to be
[20:28] <ogra_> there shouldnt (only for fastboot)
[20:28] <gab9281> there was a need of it
[20:28] <ogra_> if you need sudo for adb thats a bug with the udev rules
[20:29] <ogra_> (and should be fixed)
[20:29] <ogra_> please file a bug against android-tools
[20:29] <ogra_> (if you can confirm that adb with sudo works indeed)
[20:34] <binmosa> I just started to write my first app for Ubuntu touch , but I didn't find the option : Projects > Ubuntu > Simple Touch UI in my SDK ?
[20:38] <pmcgowan> binmosa, run the qtcreator from the SDK icon in the dash
[20:45] <balloons> nik90, ping
[20:50] <seanfell> when i connect my nexus to qtcreator on ubuntu 13.04 i am getting this error
[20:50] <seanfell> Detecting device.. /usr/share/qtcreator/ubuntu/scripts/device_search List of devices attached  ????????????	no permissions * found 1 devices. Check device image version.. /usr/share/qtcreator/ubuntu/scripts/device_version
[20:52] <popey> seanfell: try maybe "adb kill-server" then "sudo adb devices" - do you see it listed?
[20:52] <popey> (hi btw)
[20:53] <seanfell> hi, it can see the device
[20:53] <seanfell> * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached  04cdae35e28ea4af	device
[20:53] <seanfell> will try it again mow
[20:54] <seanfell> thank you its conneted must do an update, sean
[20:56] <popey> seanfell: sweet!
[20:56] <seanfell> this is a great place.
[20:56] <popey> Yes, yes it is! ☻
[20:58] <cjwatson> ogra_: They seem to match for me.  Example?
[20:59] <ogra_> cjwatson, i just fixed them manually :P the armhf.zip had the full path in both builds in .md5sum
[20:59] <seanfell> how can i get the sudoku game on it.
[21:00] <cjwatson> ogra_: Ah, well I wish you'd waited so I could see, but perhaps I can fix it based on that
[21:00] <ogra_> cjwatson, had i waited more people would have come here, not being able to install ... i'll save a backup next time
[21:02] <cjwatson> Fair enough
[21:02] <pmcgowan> cjwatson, need that md5sum file? I think I have one
[21:02] <cjwatson> pmcgowan: nah, I see the bug
[21:02] <pmcgowan> k
[21:03] <cjwatson> if somebody could fix bug 1196585 then this sort of thing will be prevented :)
[21:03] <ogra_> cjwatson, sergiusens is on it ...
[21:03] <cjwatson> good
[21:03] <cjwatson> ogra_: fixed in cdimage r1312
[21:03] <ogra_> thanks :)
[21:03] <cjwatson> I expect
[21:04] <cjwatson> might want to check that that matches your expectation based on what you say
[21:04] <cjwatson> *saw
[21:04] <ogra_> well, it should just look like the others :)
[21:05] <nik90> balloons: ping
 *<filename>
[21:06] <cjwatson> sure, I just meant to check that that corresponded to the file you had to fix manually
[21:06] <ogra_> will take a look in the next build
[21:07] <cjwatson> thanks for fixing it up, in any case
[21:07] <cjwatson> specifically, that patch fixes saucy-preinstalled-touch-armhf.zip.md5sum
[21:07] <ogra_> well, i could have fixed the code too ... thanks for doing that
[21:07] <ogra_> yeah, all others are fine
[21:07] <popey> seanfell: add the PPA then install touch-collection
[21:08] <seanfell> ok will give it a go
[21:08] <popey> seanfell: add-apt-repository -y ppa:ubuntu-touch-coreapps-drivers/collection
[21:08] <cjwatson> maybe cdimage.checksums should use os.path.relpath to defend against this in depth; dunno
[21:08] <popey> seanfell: apt-get update
[21:08] <popey> seanfell: apt-get install touch-collection
[21:08] <popey> seanfell: you'll get a bunch of stuff ☻
[21:12] <sergiusens> cjwatson: I'm on it
[21:13] <sergiusens> but it will use the SHA ones
[21:13] <ogra_> yeah
[21:14] <ogra_> saftey first :)
[21:19] <seanfell> super that worked a treat, playing checkers. thanks again.
[21:21] <jondecker76> can I get some help installing Ubuntu Touch on a nexus 7?  I'm following the wiki, but I can't get past the first step of unlocking..  I run `sudo fastboot oem unlock` but I only get the message <waiting for device>.  The tablet is plugged in and developer options turned on and usb debugging turned on.
[21:22] <popey> seanfell: great!
[21:23] <seanfell> must write my first app now. it could take some time.
[22:28] <jondecker76> I'm looking for help getting Ubuntu Touch installed on a Nexus 7.  I'm following the wiki.  ADB can't find my nexus 7, though it shows up in lsusb
[22:29] <jondecker76> I've followed every udev tutorial I could find but adv still can't find the device
[22:29] <jondecker76> *adb
[22:30] <jondecker76> i'm trying to do the Ubuntu Touch installation from Ubuntu 13.04
[22:33] <jondecker76> can anyone here help me out??  Its kind of hard to test and develop software for a growing platform if nobody is willing to help people get set up and running
[22:33] <popey> jondecker76: hey
[22:33] <popey> sorry, you just happen to have dropped by when most people have just gone to bed or left work
[22:33] <popey> jondecker76: try "adb kill-server" followed by "sudo adb devices"
[22:35] <jondecker76> popey - thanks.  Just tried, but it still doesn't show up
[22:36] <popey> is it running android at the moment?
[22:36] <popey> and you've enabled the developer mode etc as per https://wiki.ubuntu.com/Touch/Install ?
[22:37] <jondecker76> yes, it's currently running android
[22:37] <jondecker76> I've been following that exact wiki.  I have added the PPA and installed the required packages
[22:38] <jondecker76> developer mode is enabled, and usb debugging is inabled on the Nexus 7
[22:38] <popey> strange, not seen this. usually killing adb and restarting under sudo works around this
[22:38] <jondecker76> I've completed step 1, I'm currently on step 2 "Device unlock"
[22:39] <jondecker76> I've added some udev rules since nothing would work.  Perhaps I will remove those and give it a fresh start by killing the server first
[22:41] <jondecker76> ok, removed the rules I added to /etc/udev/rules.d, performed a `sudo service udev restart`, then killed the adb server and tried again.  Still no luck
[22:42] <jondecker76> I've been at this all day... I'm absolutely stumped
[22:42] <popey> Well, you've got me beat. Best thing to do would be to post a question on AU..
[22:43] <popey> or return tomorrow in the EU & US mornings when more people will be around
[22:43] <jondecker76> ok, thanks. Will do
[22:43] <popey> I'd like to know what's wrong because we would like to document these kind of edge cases
[22:43] <popey> so do let me know if you figure it out!
[22:44] <jondecker76> Ok I will.  I'll be messing with it all night most likely.
[22:44] <popey> heh
[22:44] <popey> that's the boy!
[22:55] <nate_> hi, can anyone tell me about porting the P5110 Galaxy Tab2? I am trying to build it and always get an error regarding "/out/target/common/obj/APPS/GalaxyTab2Settings_intermediates/src/R.stamp" this file isnt even in located in my local repo
[22:58] <nate_> ls
[23:01] <jondecker76> anyone else with ideas as to why adb/fastbood can't see my Nexus 7?  It shows up clearly in lsusb: Bus 001 Device 008: ID 18d1:4e40 Google Inc.
[23:01] <jondecker76> this is on Ubuntu 13.04
[23:03] <nate_> have you set up USB debugging, jond?
[23:03] <jondecker76> yes, usb debugging is on
[23:05] <nate_> try unplug the device, disable usb debugging, then renable it, and plug it back in
[23:05] <nate_> watch for an RSA notification on the device
[23:06] <jondecker76> hmm.. Now that I'm fully booted, it shows up in adb as "offline"
[23:06] <jondecker76> List of devices attached  015d25685134000c	offline
[23:06] <popey> yay
[23:06] <nate_> are you using a virtual OS?
[23:06] <jondecker76> but when I am in the bootloader (power+vol up + vol down) it does not show up
[23:06] <jondecker76> no, fresh install of ubuntu 13.04
[23:07] <nate_> adb doesnt show up in the bootloader i dont beleive
[23:07] <ali1234> it should do
[23:07] <nate_> it's never worked for me for some reason, only fastboot
[23:08] <jondecker76> fastboot only ever outputs <waiting for device> for me, which is why i'm trying `adb devices` to see if it can even see the nexus
[23:08] <ali1234> make sure you have the latest adb version
[23:08] <jondecker76> it was installed from the PPA in the wiki, so I'm assuming it must be current
[23:09] <jondecker76> now that i'm back at the bootloader, adb devices just returns a blank list again
[23:10] <AskUbuntu> qtcreator adb no permissions | http://askubuntu.com/q/315192
[23:11] <jondecker76> but if I boot up into android, adb devices returns the device in the list (but its listed as offline)
[23:16] <jjohansen> ogra_: so the maguro kernel trace you pointed me at comes from a debug check not taking a condition into account, its not doing anything bad (thankfully)
[23:29] <jondecker76> popey: got it to work.  I didn't realize that when I enabled USB debugging, that I had to be connected to USB to accept a  key.  After I did that everything seems to be working now
[23:58] <chamunks> how painful is the install for this on the nexus4?