[00:58] <dagekb> Hello...
[00:58] <dagekb> Where can I find LG Nexus 4, Android 4.2.2? :)
[00:59] <dagekb> When I flashed Ubuntu Touch, it deleted my backup (from CWM)... It have never done this before...
[01:00] <dagekb> ... the backup was my Android 4.2.2, so now it is gone...
[01:10] <dagekb> Found it... :)
[01:10] <dagekb> I was hoping I could try out (and develop) for Ubuntu Touch at the same time I could use Android 4.2. But no?
[01:14] <guest_33200482> nexus 7 and ubuntu touch on it: can i make calls?
[01:29] <mhall119> guest1__: make calls on a Nexus 7?
[01:38] <dragonkeeper> Anyone interested in developing ubuntu touch for i9505 ?
[01:40] <k03ll> mhall119: yep, i was that guest__ finding out if i can make calls on a nexus 7 with ubuntu touch
[01:41] <k03ll> dragonkeeper: i9505 seems to be a samsung device?
[01:41] <dragonkeeper> Yes samsung galaxy s4 i9505 jfltexx
[01:46] <mhall119> k03ll: the nexus 7 is a tablet, not a phone....
[01:46] <mhall119> I suppose you could use VoIP
[01:46] <dragonkeeper> We have twrp , cwm recoverys and cm10.1 already . So as i understand it ubuntu-touch shouldnt be so hard to port over if someone has experience doing it
[01:47] <k03ll> mhall119: 7" isnt big enough, and voip is more than an all time alternative.
[01:47] <mhall119> dragonkeeper: if I had an S4 and was any good at porting, I'd be all over it :)
[01:48] <mhall119> k03ll: I'm make a joke about holding a N7 up to your ear to talk, but I think my brother's Galaxy Note 2 is almost as big
[01:49] <k03ll> the nexus 4 is ubuntus flagship, much cheaper than a s4 and very affordable. i like the new image from ubuntu / canonical
[01:50] <dragonkeeper> Never dev'd for android roms so im here lol, not really a ubuntu fan but it seems to be the closest thing to getting a decent linux system running
[01:50] <k03ll> mhall119: of course, i would use a headset or somthng similiar. im not going to use it as a heavy phone user. just to make some calls and answer incomings
[01:51] <mhall119> dragonkeeper: have you read the porting guide?
[01:52] <mhall119> k03ll: I suppose all it would need is somebody writing a voip client for Ubuntu Touch
[01:52] <mhall119> oh, and audio working on the Nexus 7
[01:52] <dragonkeeper> Just one thing i want to know as your talking about calls, can ubuntu make use of another line. I.e im in a call with 1 person and another person calls me on same number and it appears on screen so i can put 1 on hokd talk to other or merge calls
[01:52] <mhall119> dragonkeeper: that I don't know
[01:53] <mhall119> and I don't have a phone to test it with
[01:53] <dragonkeeper> :[
[01:53] <mhall119> I know, I make that face whenever I see someone doing something cool with their Ubuntu Phone
[01:54] <dragonkeeper> So as i understand it, this uses arm packages from ubuntu repo ? Therefore there must be IR drivers for phones ?
[01:54] <dragonkeeper> I have this s4 and a motorola atrix 4g i want it on
[01:57] <mhall119> dragonkeeper: for the ubuntu side, yes, it uses arm packages from the repos
[01:57] <mhall119> but the kernel and drivers that come from Android, I'm not sure about
[01:58] <dragonkeeper> So if i got a android kernel with , say ,, nfc support  . Then i could use nfc with ubuntu side
[01:59] <mhall119> well no, you'd need both sides to know what's going on
[01:59] <mhall119> you might expose a device in the kernel with the Android support
[01:59] <mhall119> but unless there's something on the Ubuntu side that knows what to do with that device..
[02:55] <rh> hi
[02:57] <rh> has anyone tried to install ubuntu touch on an acer iconia a200?
[02:57] <rh> is it even compatible?
[03:00] <rh> anyone willing to help with a question?
[03:02] <rh> anyone willing to help with a question?
[03:05] <rh> is ubuntu touch compatible with the acer iconia a200?
[03:07] <rh> hi
[03:07] <rh> help?
[03:07] <rh> question?
[03:08] <rh> is there any assistance in this room?
[03:08] <duflu> rh: I don't know if anyone has tried it yet. Likely won't work. All development for ubuntu-touch is being done on Nexus/Galaxy devices
[03:09] <rh> that's unfortunate...
[03:09] <rh> thanks
[04:40] <daniel3> I installed Ubuntu Touch on my Nexus 7, and nothing even opens, none of the apps. :\
[06:19] <dholbach> good morning
[07:37] <c__chp> __
[07:37] <c__chp> anyony there
[08:03] <FunkyPenguin> is there a way of bringing wifi up from adb? using the ui doesn't work for both the secured and unsecured APs here
[08:37] <ttoine> hey
[08:37] <ttoine> I would like to flash my phone and test again ubuntu touch
[08:37] <ttoine> does it manage sim security now ? or I still need to unlock my sim card before ?
[08:42]  * leemeng0x61 anybody?
[09:09] <AskUbuntu> Ubuntu touch install from recovery on nexus 7 3g | http://askubuntu.com/q/305183
[09:11] <ogra> that person should just follow the manual install instructions
[09:34] <daniel3> Too glitchy to even be usable :\
[09:59] <seb128> oSoMoN, mzanetti: hey, I'm doing a packaging review of notes-app before it lands in Ubuntu and I've a small issue
[10:00] <seb128> oSoMoN, mzanetti:
[10:00] <seb128> src/NotesApp/Plugins/cachingprovider.cpp: LGPL (v3)
[10:00] <seb128> src/NotesApp/Plugins/cachingprovider.h: LGPL (v3)
[10:00] <seb128> the project is under GPL for everything else
[10:00] <seb128> is that wanted to use the LGPL for those 2 sources?
[10:00] <seb128> we either need to change them to be GPL or to add a COPYING.LGPL to the source and list them correctly under debian/copyright
[10:01] <seb128> oh, Components/RemovableBG.qml Components/CollapsedNoteDecorations.qml and Components/CollapsedNote.qml as well
[10:02] <oSoMoN> seb128: we’d need confirmation from Ugo who wrote the code, but I’m pretty sure it’s just a copy/paste leftover, this is entirely original code written in-house
[10:02] <oSoMoN> seb128: unfortunately Ugo isn’t working today, he’ll be back on Monday
[10:03] <seb128> oSoMoN, ok, no problem, that can wait monday
[10:03] <seb128> didrocks, ^
[10:05] <didrocks> thanks :)
[10:20] <seb128> oSoMoN, do you want a bug report about that or should I just ping you guys again on monday?
[10:20] <oSoMoN> seb128: please ping Ugo on Monday
[10:20] <seb128> oSoMoN, ok
[10:38] <seb128> oSoMoN, same issue in camera-app with DeviceOrientation.qml ... is that Ugo as well?
[10:44] <asac> bfiller: are you guys doing webapps too?
[10:48]  * ogra grumbles about grouper
[10:55] <cking> where do I file bugs against qml-phone-shell?
[10:59] <nj_> i need some help...i tried the steps given on galaxy nexus 7...all the steps were completed successfully...but i din get ubtuntu touch after rebooting
[10:59] <oSoMoN> seb128: according to bzr annotate, yes
[10:59] <nj_> what could be the possible issue/
[10:59] <nj_> ?
[11:00] <nj_> any help?
[11:01] <seb128> oSoMoN, mediaplayer has the same issue, files are from renato on this one though
[11:01] <kalikiana> cking, going by the precedent probably here https://bugs.launchpad.net/unity/+bug/1163273
[11:01] <seb128> oSoMoN,
[11:01] <seb128> ./tests/unittest/thumbnailtest.cpp: LGPL (v3)
[11:01] <seb128> ./src/qml/sdk/sliderUtils.js: LGPL (v3)
[11:01] <seb128> ./src/qml/sdk/mathUtils.js: LGPL (v3)
[11:01] <cking> Kakadu, thanks
[11:01] <cking> oops
[11:02] <cking> kalikiana, thanks
[11:02] <nj_> i need some help...i tried the steps given for galaxy nexus 7...but i din get ubtuntu touch after rebooting..what could be the issue?
[11:02] <oSoMoN> seb128: I believe renato should be online very soon, feel free to bug him about it
[11:02] <seb128> k
[11:02] <nj_> okay..
[11:07] <nj_> hey,,i am not sure about this...but this could be a lame question as well....still...after pushing the images into device do i also have to install them through install zip from sdcard option?
[11:09] <nj_> hey,,i am not sure about this...but this could be a lame question as well....still...after pushing the images into device do i also have to install them through install zip from sdcard option?
[11:12] <nj_> hellooo
[11:16] <eax> Hey there - is there an ETA on tethering and 3G/LTE?
[11:41] <lilu> hello, i'm looking for a tablet model with external USB device support that is capable of running Ubuntu. could anyone give me some hint please?
[11:59] <xqee> hello
[11:59] <xqee> can  i put ubuntu on jay-book 9905 ?
[12:11] <adc> Hi! I got stuck when trying to install the developer preview on my Nexus 4, using the install instructions from the wiki. I'm running Debian Jessie, and added the 'raring' repo to my sources.list. After enabling USB debugging, the device showed up in 'sudo adb devices'. I went ahead and executed 'sudo phablet-flash -b'. The files were downloaded just fine, and 'raring-preinstalled-{recovery,system,boot}-armel+mako.img' were flashed without warnings
[12:26] <didrocks> oSoMoN: FYI http://paste.ubuntu.com/5741741/, you can see what you can work on to get your components better :)
[12:27] <didrocks> oSoMoN: basically the apps have license issues as seb mentionned, so I'll keep this stack frozen for now
[12:27] <didrocks> (to avoid spamming the archive with packages we can't NEW)
[12:32] <adc> My issue was resolved by restarting the adb server with 'adb kill-server', and pushing the stock rom to the device.
[12:33] <oSoMoN> didrocks: would you mind sharing this paste with a wider audience (i.e. send an e-mail) so that all maintainers are aware of what they need to address?
[12:34] <didrocks> oSoMoN: as soon as Unity and touch migrates to the release pocket, I'm doing that
[12:34] <didrocks> oSoMoN: it's already written TBH :p
[12:38] <Moviuro_> Hi all! Where do i get the file to flash on my phone? :)
[12:39] <k1l> Moviuro_: the topic mentions a wiki overview page, where you find install instructions for supported and community supported devices
[12:39] <jaywink> does ubuntu touch already support pin unlocking or should I remove the pin question from my sim? Planning on going dogfooding mode today :)
[12:40] <Moviuro_> Thanks k1l
[12:53] <ogra> jaywink, no PIN support yet ... it is being worked on though
[12:54] <jaywink> ogra, thnx
[13:06] <ogra> oh you silly silly grouper
[13:07] <tassadar_> ogra: it's still giving you hard time? :/
[13:10] <ogra> tassadar_, yeah, trynig to find the one option that makes it boot
[13:12] <tassadar_> heh
[13:39] <didrocks> mterry: @pocketsphinx: yeah, the work was duplicated
[14:07] <didrocks> sil2100: see my comment about multiverse on julius, if you can discuss about it with tedg :)
[14:08] <tedg> didrocks, ?  Julius, we're not using it anymore?
[14:08] <didrocks> tedg: aren't you? why are you recommending it then? ;)
[14:08] <tedg> didrocks, bug?
[14:08] <tedg> :-)
[14:09] <rickspencer3> cyphermox, have you seen that this bug is assigned to you?
[14:09] <rickspencer3> https://bugs.launchpad.net/touch-preview-images/+bug/1183065
[14:09] <rickspencer3> it's making my phone unusable outside the house
[14:09] <rickspencer3> which, you know, for a mobile phone, is kinda a deal breaker :)
[14:09] <didrocks> tedg: we don't do bug I heard? :p
[14:09] <tedg> didrocks, Yeah, I don't think we need that.  The sphinx voxforge stuff should be enough.
[14:10] <didrocks> tedg: ok, let me prep a branch
[14:10] <tedg> Double checking with pete-woods ^
[14:10] <didrocks> tedg: I had to remove temporarly the upstart job for unity-panel-service btw
[14:10] <tedg> didrocks, Hmm, why?
[14:10] <didrocks> tedg: I dropped a note to get that back
[14:10] <didrocks> tedg: I noticed some troubles when I exited my session
[14:10] <didrocks> unity went back through the panel service
[14:11] <didrocks> (there was also a segfault, but that was bamf)
[14:11] <didrocks> tedg: so no worry, it needs more testing, just needed to release :)
[14:11] <ogra> didrocks, the touch images (all of them, even on cdimage) build with --no-install-recommends
[14:11] <ogra> so i guess it just didnt show up that tthere is a stale recommends
[14:12] <didrocks> ogra: interesting :)
[14:12] <didrocks> ok
[14:12] <ogra> yeah, fixing that bit will be another horrid transition :)
[14:13] <tedg> didrocks, Hmm, interesting.  Did you enable it?  It should be basically off until we update gnome-session.
[14:13] <tedg> Which we should do :-)
[14:13] <didrocks> tedg: not for unity-panel-service
[14:14] <tedg> didrocks, But it was "start on started unity" so it should only start when the unity upstart job starts.
[14:14] <tedg> Hmm, perhaps even if it blocks it records the start.
[14:14] <didrocks> tedg: yeah, I just noticed this behavior, but I'll retest properly
[14:15] <tedg> Anyway, yes.  That's fine.  Happy things are out :-)
[14:15] <didrocks> me as well :)
[14:15] <tedg> We can refine more now.
[14:15] <didrocks> thanks!
[14:15] <didrocks> right
[14:17] <didrocks> tedg: https://code.launchpad.net/~didrocks/hud/remove-julius-caesar/+merge/168078
[14:17] <didrocks> sil2100: FYI ^
[14:19] <ogra> the romans will hate you !
[14:19] <sil2100> didrocks: ACK
[14:19] <didrocks> ogra: :)
[14:21]  * tedg wonders why LP is taking so long on the diff
[14:23] <ogra> it is roman too ?
[14:23]  * tedg thought it was Russian, Soyuz, right?
[14:29] <pete-woods> didrocks: tedg is absolutely correct, we no-longer need to package julius, we managed to switch over to using sphinx for voice recognition
[14:34] <cyphermox> rickspencer3: I have seen it, jason told me yesterday
[14:34] <rickspencer3> cyphermox, do you know what the cause is? any ideas?
[14:35] <cyphermox> not really. it could be the background scanning, but it seems to me like you should be seeing the same kind of battery drain on a laptop as well if it was the case
[14:38] <asac> ogra: how is container flip going? whats your risk assessment and predicted landing time as of now?
[14:40] <ogra> asac, mako and maguro should boot out of the box now, i wasted the whole day on grouper trying to find the kernel options that break it (massively time consuming and not done yet) ...
[14:40] <ogra> beyond this, the hybris/appmanager/platform-api issues seem to be harder to resolve than expected
[14:40] <asac> ogra: nice!! those kernel options, what were those about?
[14:40] <asac> can you write a shell script that tests that those options are available?
[14:41] <asac> runtime shell script
[14:41] <ogra> asac, well, the kernel goes into an endless reboot loop atm, init dies
[14:41] <ogra> with no further info ...
[14:41] <asac> ic
[14:41] <ogra> but i can boot an nexus7 desktop kernel (which then fails on all the other userspace bits since it misses the needed optionns for touch)
[14:41] <asac> ogra: what options did you find missing so far?
[14:42] <ogra> well, we changed a lot for the desktop kernel ... the diff between the configs is 800 lines (with cruft though ... actually changed lines should be around 200 or so)
[14:43] <ogra> i'm sure its a combo of only a few options, but finding the right one is hard and eats time
[14:44] <ogra> (and the n7 doesnt charge in recovery, so it dies every few hours and i need to re-charge)
[14:44] <ogra> i will have grouper working after the weekend
[14:44] <ogra> for manta i havent seen any tests at alll yet
[14:44] <ogra> on maguro i have the ofono/rild stack working since yesterday ... but it is still a bit racy
[14:45] <ogra> sound/pulse will still need love
[14:45] <ogra> nob ody touched that yet
[14:46] <jcastro> will phablet-flash at some point just switch me over to saucy or do I need to do manual things?
[14:47] <ogra> it will just switch you over
[14:47] <ogra> one way or the other
[14:49] <asac> is this channel logged?
[14:49] <rickspencer3> asac, yes
[14:49] <asac> cool. found it
[14:50] <rickspencer3> asac, http://irclogs.ubuntu.com/2013/06/07/%23ubuntu-touch.txt
[14:50] <rickspencer3> ^ I've created a singularity
[14:53] <BobbyEsco> hello
[14:53] <BobbyEsco> anybody home?
[14:54] <ogra> most of us ...
[14:54] <ogra> ... except the ones that arent
[14:54] <asac> rickspencer3: you see this battery bug? bug 1183065 ?
[14:55] <asac> rickspencer3: can you attach a syslog after seeing this symptoms to the bug?
[14:55] <rickspencer3> asac, sure
[14:55] <rickspencer3> I'll need to do it in a few hours since my phone is flat out of batteries now ;)
[14:56] <BobbyEsco_> so whats the status for ubuntu touch for android??
[14:56] <ogra> what is ubuntu touch for android ?
[14:57] <BobbyEsco_> ubuntu os on android
[14:57] <rickspencer3> BobbyEsco_, hi, we call that Ubuntu for Android
[14:57] <rickspencer3> or affectionately, U4A
[14:57] <ogra> well, that has no touch in it :)
[14:57] <BobbyEsco_> ooh ok, thanks for the correction
[14:58] <ogra> (not only in the name )
[14:58] <rickspencer3> BobbyEsco_, unlike Ubuntu Touch, U4A requires deep partnership with the phone manufacturer
[14:58] <asac> rickspencer3: you know its funny ... my galaxy nexus is here on wifi on my table now in its 4th or 5th day :)
[14:58] <rickspencer3> BobbyEsco_, and as ogra points out, you'll get a standard Ubuntu desktop running from your phone
[14:59] <asac> i am close to vouch for not adding any features if i get 3-4 days and can browse and can receive phone calls :)
[14:59] <rickspencer3> I think it's 12.04 LTS running Unity 2d iirc
[14:59] <ogra> asac, you are not roaming around
[14:59] <asac> this device never lasts longer than a day with android
[14:59] <asac> with same usage profile
[14:59] <asac> ogra: probably, but i am comparing same use case with android :)
[14:59] <ogra> well, we dont really run much yet
[14:59] <asac> well. to be fair it doesnt have a SIM ... just wifi checking a few times a day what the battery is and using the shell a bit
[15:00] <asac> right.
[15:00] <ogra> start a few apps that also make use of sensors etc
[15:00] <ogra> android runs a ton of that stuff in bg
[15:00] <asac> hence i said: i vouch to see if we can somehow add nothing that will bring us donw
[15:00] <asac> :)
[15:00] <ogra> haha
[15:00] <ogra> we surely could ... but i guess that wouldnt really give good usability
[15:00] <asac> i dont want to see so much dirt that we loose 2 more days :)
[15:01] <ogra> i guess we'll use one at least
[15:01] <ogra> s/use/lose/
[15:06] <rickspencer3> asac, cyphermox is there a way I can just tell the phone to never use the configured wireless and just stay on my cellular data?
[15:06] <rickspencer3> and in that way, not have the nm go crazy and drain my battery?
[15:07] <asac> rickspencer3: that feature exists in a few forms
[15:07] <asac> rickspencer3: hammer: you can just remove the wifi module (if we dont build it in the kernel)
[15:07] <rickspencer3> that sounds rather drastic
[15:07] <cyphermox> rickspencer3: I think you can just disable wifi : nmcli nm wifi off
[15:07] <asac> also ... if we use NM there is this setting you know from indicator to disable/enable wireless
[15:07] <rickspencer3> ah
[15:07] <asac> yeah... thats the cli :)
[15:07] <rickspencer3> turning off wifi sounds correct
[15:07] <asac> nice
[15:08] <ttoine> hi
[15:08] <rickspencer3> asac, I don't think we have a setting in the indicator to turn wifi off yet
[15:08] <ttoine> is ubuntu touch managing sim card security now ?
[15:08] <cyphermox> I'm still very doubtful it's actually NM doing things wrong... I reflashed the raring image just now on mako to dig into it
[15:08] <rickspencer3> though, it wouldn't be the furst time I as surprised if we did
[15:08] <jcollado> Hello. I've just installed the touch image in a nexus7 and wanted to use the terminal to run some example autopilot tests
[15:08] <cyphermox> rickspencer3: renato has a code branch that does this
[15:08] <asac> rickspencer3: right. hence my vague statement. didnt know it was encoded in our cli. so thats great answer
[15:09] <jcollado> but I don't get any virtual keyboard and if I plug a USB keyboard it doesn't work either.
[15:09] <cyphermox> but the wifi driver is broken and won't allow you to turn wifi back on
[15:09] <rickspencer3> oh
[15:09] <rickspencer3> cyphermox, can I turn wifi back on from the terminal?
[15:09] <asac> cyphermox: do you have a feeling why we see bug 1183065 ?
[15:09] <asac> is that scanning going wield?
[15:09] <cyphermox> which is also what steers me to say that the battery drain is also likely driver related
[15:09] <jcollado> I think the terminal window isn't getting the focus because the square looks empty instead of full. Any advice to troubleshoot this?
[15:10] <cyphermox> rickspencer3: no... when the device gets turned off there's some firmware loading issue or something that prevents the device coming back to ready to be used
[15:10] <rickspencer3> ok
[15:10] <rickspencer3> so I won't do that :)
[15:10] <cyphermox> sorry :(
[15:11] <rickspencer3> cyphermox, it might be good to mention a couple of these things in the bug report so folks know it is being addressed
[15:16] <awe_> ttoine, no support for SIM PIN/PUK yet
[15:16] <asac> cyphermox: i think android always rmmods wifi drivers
[15:16] <asac> cyphermox: if they disable wifi
[15:17] <asac> so most likely the normal disable code path is not tested
[15:17] <asac> we try software disable, right?
[15:17] <asac> if so ... definitely worth trying unload on disable
[15:17] <awe_> asac, cyphermox, we should look at the Android WifiManager and see how it's done
[15:17] <asac> i really think they are aggressive
[15:17] <asac> and rmmod it
[15:17] <asac> i think it was at some point even in the compatibility spec
[15:17] <asac> that you ned to have wifi module as a module :)
[15:18] <awe_> I'm not sure the module is removed
[15:19] <asac> awe_: in android?
[15:19] <beidl> they surely did rmmod the wifi module on older phones (found this on my 3 year old HTC Desire) in Android
[15:19] <cyphermox> awe_: it's going to be hard to rmmod a module when it's builtin...
[15:19] <asac> beidl: i really believe it was even the default code path
[15:19] <cyphermox> asac: ^
[15:20] <asac> cyphermox: but its probably our decision to build that in?
[15:20] <cyphermox> that said, when you nmcli nm enable false ; nmcli nm enable true, the device comes back
[15:20] <cyphermox> asac: no
[15:20] <cyphermox> it's always a builtin afaik
[15:20] <asac> cyphermox: we use the upstream defconfig?
[15:20] <ttoine> awe_, thanks. so I have to unlock my sim in android before flashing, true ?
[15:20] <awe_> by default the drivers are builtin
[15:20] <asac> cyphermox: thats mako?
[15:20] <cyphermox> rickspencer3: ^ feel free to turn off wifi as I mentioned earlier, if you can live with 3G being off temporarily as you bring wifi back up
[15:21] <cyphermox> asac: yeah, mako
[15:21] <cyphermox> so it looks like a missing netlink event or something
[15:21] <awe_> ttoine, correct
[15:21] <rickspencer3> cyphermox, ok, that sounds like a good work around
[15:21] <rickspencer3> I'll try it later today and update the bug report with the work around if it works
[15:22] <cyphermox> ok
[15:22] <cyphermox> I'll add the details o nthe bug
[15:22] <awe_> cyphermox, does the bug exist, or are you in the process of creating it?
[15:23] <cyphermox> well, a bug for power management w.r.t wifi does exist
[15:24] <awe_> yes, but I think that's associated with scanning
[15:24] <cyphermox> awe_: also, confirming the issue is with the indicator for listing wifi scan results..
[15:24] <cyphermox> right
[15:24] <awe_> is there a bug that says "powering off wifi is broke"?
[15:24] <cyphermox> it's associated by scanning because the driver is brain dead
[15:24] <cyphermox> I don't know
[15:24] <cyphermox> renato_: ^ ?
[15:24] <awe_> cyphermox, you have to remember the driver was written specifically for Android, not a generic Linux distro
[15:25] <cyphermox> awe_: how hard can it be to write a driver that just works?
[15:25] <awe_> and thus there are assumptions about what userspace does that effect how the driver works
[15:25] <cyphermox> it's not like there are many different ways to speak to those devices... it's either nl80211 or wext
[15:25] <awe_> cyphermox, it's not a question of how hard, it's a question of what platform it was targeted to
[15:25] <cyphermox> it's not using a different way to deal with this, it's just half-baked
[15:25] <awe_> we also have to figure what to do about the driver-specific wpa_supplicant code too
[15:26] <cyphermox> it's just incomplete because it's all they ever needed, they only added the bare minimum to make it do stuff
[15:26] <awe_> correct, the drivers were built to certify Android devices
[15:27] <cyphermox> I know
[15:27] <awe_> that's why we've seen issues with CRDA, et al.
[15:27] <cyphermox> it's just annoying anyway to run into all these issues that should have been fixed years ago already
[15:27] <awe_> why should they have been fixed?
[15:27] <rickspencer3> they are not issues
[15:28] <rickspencer3> it sounds like, it's just unnecessary functionality for what the driver was written for ;)
[15:28] <awe_> correct
[15:31] <ttoine> awe_, thanks
[15:31] <awe_> ttoine, np
[15:40] <mhall119> nik90: btw, I had to move the alarm api meeting to Tuesday, can you still attend?
[15:41] <cyphermox> rickspencer3: I brought up the issues to jasoncwarner, perhaps someone else can look into the driver while I focus on NM and wpasupplicant?
[15:42] <cyphermox> I'm trying to finish writing the patch to let NM know about ofono connections and autoconnect 3G when possible
[15:42] <cyphermox> (at the same time)
[15:48] <vthompson> names
[15:50] <asac> awe_: so
[15:50] <asac> 15:49 < bhoj> 15:47:20> asac, that was the approach at some point of time for
[15:50] <asac>               sure. The code is still there in
[15:50] <asac>               hardware/libhardware_legacy/wifi/wifi.c
[15:50] <asac> he also said that its not like that by default anymore though
[15:50] <asac> so just FYI
[15:51] <awe_> asac, thanks... I kinda figured that out by the presence of "legacy" in  the directory name
[15:51] <xnox> using ListItem.ValueSelector how to set the "default" value?
[15:52] <asac> awe_: ah... wasnt sure you found the code
[15:52] <asac> so nevermind
[15:52] <awe_> asac, k thanks
[16:06] <MASTER260> Hey, just wondering if anyone's been working on porting Ubuntu for tablets over to Android-86.
[16:07] <MASTER260> *Android-x86.
[16:09] <slangasek> ogra: can you turn up the upstart log priority?  (booting with --debug, or calling 'initctl log-priority debug' early in boot)
[16:09] <ogra> me ?
[16:09] <MASTER260> So... does anyone know?
[16:10] <ogra> slangasek, you can just update the cmdline with abootimg
[16:11] <ogra> abootimg -u /dev/disk/by-partlabel/boot -c "cmdline=--debug"
[16:11] <ogra> something like that
[16:11] <slangasek> ogra: sorry, I was apparently reading some rather stale scrollback here from yesterday wrt file events... I was suggesting you do that in order to debug why the file event wasn't doing anything for you
[16:11] <slangasek> ogra: but maybe you've moved on from that :)
[16:12] <ogra> ah, well, i tried to get grouper going today ... since 90% of the team have that platform ...
[16:12] <ogra> so that we get more testing and dev help ....
[16:13] <ogra> but had to stop for getting the charging code into the initrd now
[16:14] <MASTER260> So... I guess no one knows...
[16:14] <ogra> MASTER260, there is no support for x86 yet ... someone would have to get x86 support into the android tree on phablet.ubuntu.com first
[16:15] <ogra> pathes will be gratefully accepted ;)
[16:15] <MASTER260> Is anyone working on that?
[16:15] <ogra> no
[16:15] <ogra> at least not that i'm aware
[16:16] <MASTER260> Oh.
[16:42] <mhall119> ogra: correct me if I'm wrong, but isn't our x86 plan to use Mir and Unity 8 on top of the standard Ubuntu kernel and drivers, and not using Android?
[16:43] <ogra> mhall119, not sure that would work on an x86 phone ...
[16:43] <ogra> for tablets it probabbly would
[16:43] <ogra> -b
[16:45] <ogra> but if we have to have x86 android for phones i dont see any issues to also pull in tablet stuff there
[16:45] <ogra> (and get better HW support)
[16:45] <mhall119> for Android HW anyway
[16:45] <ogra> right
[16:46] <ogra> it is definitely "wanted" but nobody has time for working on it ... to get it fast someone from the community would have to step in
[17:02] <rickspencer3> cyphermox, I'm ready to repro that bug and get the syslog
[17:03] <rickspencer3> do I just repro it, and then grab the syslog, or do I need to enable logging or anything first?
[17:04] <rickspencer3> maybe I can just adb pull what is already there?
[17:23] <cyphermox> rickspencer3: It would be better if you enabled debugging in NM
[17:23] <cyphermox> let me get the command line
[17:23] <rickspencer3> ok
[17:24]  * rickspencer3 cancels upload of current syslog
[17:24] <cyphermox> sudo python /usr/lib/NetworkManager/debug-helper.py --nm debug --domains=core,wifi
[17:24] <rickspencer3> cyphermox, ack
[17:24] <rickspencer3> may take me a while to get to it
[17:24] <cyphermox> you'll need python-dbus on the phone for that, it seems to be missing here at least
[17:24] <cyphermox> sure
[17:25] <rickspencer3> oh
[17:25] <cyphermox> I'll fix that with my next upload
[17:25] <rickspencer3> that's annoying :)
[17:43] <rickspencer3> cyphermox, can I enable the debugging via ubuntu_chroot shell?
[17:46] <sergiusens> rickspencer3: debugging nm and ofono? If it is, look at my comment here https://plus.google.com/100264483712374857174/posts/3o1tjYo9Ghx (sorry just joined so may not be related)
[17:46] <rickspencer3> hi sergiusens
[17:47] <rickspencer3> I'm trying to get a syslog for cyphermox to help track down that power eating bug
[17:48] <sergiusens> rickspencer3: so what are you enabling debugging for?
[17:48] <rickspencer3> sergiusens, because cyphermox asked me too
[17:48] <rickspencer3> :)
[17:48] <sergiusens> rickspencer3: it's generally just going into the upstart job and setting the debugging flag
[17:48] <sergiusens> rickspencer3: in /etc/init/ofono.conf add a -d to the ofono cmd
[17:49] <sergiusens> rickspencer3: in  /etc/init/network-manager.conf add a  --log-level=DEBUG
[17:49] <sergiusens> rickspencer3: your syslog will be happily logging lots there
[17:50] <rickspencer3> so make it exec ofonod -d --noplugin=atmodem
[17:50] <rickspencer3> ?
[17:50] <awe_> sergiusens, you never answered my question yesertday about the cause of the roaming bug
[17:50] <awe_> did you create a bug for it?
[17:50] <sergiusens> awe_: yeah, I shared it with you yesterday and you said thanks :-)
[17:50] <awe_> cyphermox, no CDMA support in touch, nor is it currently planned
[17:50] <sergiusens> awe_: I was just fetching it for rickspencer3 .... but #1188404
[17:51] <sergiusens> bug #1188404
[17:51] <sergiusens> argh
[17:51] <sergiusens> https://bugs.launchpad.net/touch-preview-images/+bug/1188404
[17:51]  * sergiusens wonders where the bot is
[17:52] <nik90> mhall119: i can still attend.
[17:52] <sergiusens> rickspencer3: yes to your question above
[17:53] <mhall119> nik90: aweseme
[17:53] <mhall119> nik90: I won't be around, I'm hoping popey will be there though
[17:53] <awe_> sergiusens, I thought you said you discovered the root cause?
[17:54] <awe_> sergiusens, also what *happens* when you enabled roaming?
[17:54] <nik90> mhall119: oh you wont be there
[17:54] <rickspencer3> sergiusens, so, er, pico doesn't let me actually save the file :/
[17:54] <mhall119> nik90: unfortunately no, I'm off that day, but i don't want to delay it any further
[17:55] <nik90> mhall119: okay. But you should definitely sometime come to the design meetings on thursday :)
[17:58] <sergiusens> rickspencer3: oh, are you root?
[17:58] <rickspencer3> yeah
[17:58] <rickspencer3> I'm using ubuntu_chroot shell
[17:58] <sergiusens> awe_: when I enabled roaming, cpu usage of ofono tends to 0
[17:58] <rickspencer3> adb root
[17:59] <rickspencer3> adb shell
[17:59] <rickspencer3> ubuntu_chroot shell
[17:59] <rickspencer3> root@ubuntu-phablet:/etc/init#
[17:59] <awe_> sergiusens, ah ok.  I didn't quite understand your wording
[17:59] <rickspencer3> sergiusens, is there a better way to edit files on the phone?
[18:00] <cyphermox> awe_: I know, I was telling them to have fun playing with the code if they want to make it work
[18:00] <awe_> so sergiusens, more importantly... did data work?
[18:00] <sergiusens> rickspencer3: I use vi...
[18:00] <awe_> cyphermox, k
[18:00] <sergiusens> awe_: ahh... I'm fearful to try, but I'll give it a shot
[18:01] <awe_> well you did try
[18:01] <sergiusens> rickspencer3: I just vi and ssh in... should work... I did all this yesterday with the ubuntu-terminal-app
[18:01] <awe_> I mean you enabled & attached, right?
[18:01] <awe_> if you get a super expensive cell phone bill, expense it
[18:01] <sergiusens> awe_: let me give you some output :-)
[18:02] <awe_> we need to testing roaming at some point, and I bet the bill will be cheaper than an airplane flight
[18:02] <awe_> ( besides, we really don't use much data... so try and ping, and then bring it down )
[18:03] <sergiusens> I'm attached... NetworkReg says I'm roaming, adding to the bug
[18:03] <sergiusens> rickspencer3: you can edit the file on your desktop and adb push it to the phone too
[18:03] <rickspencer3> sergiusens, that;s a good idea
[18:04] <rickspencer3> I want to figure out how to do with with vi though
[18:04] <rickspencer3> I have a hate/hate relationship with vi
[18:04] <rickspencer3> meh, I'll just pull and push it ;)
[18:05] <sergiusens> rickspencer3: ah... yeah, you either love it or hate it
[18:06] <awe_> I hate vi, but learned some basic skillz with it along time ago
[18:06] <rickspencer3> honestly wish I thought of pulling and pushing before
[18:06] <awe_> at one point ( back in the day ) it was the only editor guaranteed to be on a machine
[18:06] <awe_> ( hmm, sounds familiar )
[18:07] <sergiusens> rickspencer3: if it weren't root things you wanted to do, you could also just sftp from nautilus and do it with a bling :-)
[18:08] <sergiusens> awe_: roaming works https://bugs.launchpad.net/touch-preview-images/+bug/1188404/comments/3
[18:08] <sergiusens> awe_: just need to solve the thing when roaming isn't allowed :-)
[18:12] <awe_> sergiusens, ack
[18:12] <awe_> I'm looking at it now
[18:14] <rickspencer3> hmmm
[18:15]  * rickspencer3 goes to repro bug
[18:29] <jcastro> hey guys, is audio from the browser supposed to work?
[18:29] <jcastro> I tried html5.grooveshark.com with hopes of having a music player; the entire site works great other than no audio
[18:31] <ChickenCutlass> jcastro, not yet.  It will soon
[18:32] <jcastro> ah excellent.
[18:32] <jcastro> The grooveshark html5 client is pretty sharp.
[18:37] <kenvandine> how usable is saucy on the nexus7 now?  would i regret switching to it today?
[18:38] <kenvandine> i really need the new webcred stack on it :)
[18:38] <bcurtiswx> is friends built on saucy?
[18:38] <kenvandine> bcurtiswx, of course :)
[18:38] <kenvandine> ogra, ^^
[18:40] <bcurtiswx> do i need to phablet-flash frequently still, or no?
[18:41] <kenvandine> i do daily
[18:41] <kenvandine> not sure how important that is
[18:41] <kenvandine> it's just part of my morning ritual :)
[18:41] <bcurtiswx> mine always gives me a not enough data warning, but if i -b it works
[18:41] <kenvandine> it's nice now that our settings don't get lost
[18:42] <bcurtiswx> but i think -b removes my settings, right?
[18:42] <kenvandine> yeah, remove the zip files
[18:42] <kenvandine> i think so
[18:42] <kenvandine> i never do that
[18:42] <bcurtiswx> what zip files do i remove ?
[18:42] <sergiusens> -b bootstraps
[18:42] <sergiusens> and wipes
[18:43] <bcurtiswx> kenvandine, which zip files would I remove ?
[18:43] <kenvandine> i only did it when i switched from quantal to raring
[18:44] <kenvandine> the raring ones just keep getting overwritten
[18:44] <kenvandine> but the quantal ones were lingering
[18:44] <kenvandine> cyphermox, i hear you switched to saucy... how did that work for you?
[18:47] <rickspencer3> sergiusens, cyphermox https://launchpadlibrarian.net/141892521/syslog
[18:47] <cyphermox> pretty good? any specific question in mind?
[18:49] <bcurtiswx> should we expect any major differences at this point?
[18:50] <sergiusens> bcurtiswx: well the shell has evolved quite a bit
[18:50] <bcurtiswx> neat
[18:52] <kenvandine> cyphermox, i need to test the webcred stack
[18:52] <kenvandine> which has landed in saucy
[18:52] <kenvandine> i don't want to rebuild it all for raring :)
[18:53] <kenvandine> cyphermox, how do you flash saucy?  manually push the zip files and do it in recovery?
[18:53]  * sergiusens shuts down as no more battery power
[18:54] <sergiusens> kenvandine: you want saucy flipped or saucy unflipped?
[18:54] <kenvandine> unflipped
[18:54] <kenvandine> safest path :)
[18:54] <bcurtiswx> what does that even mean?
[18:54] <sergiusens> kenvandine: let me send and email
[18:54] <kenvandine> sergiusens, thanks
[18:59] <mhall119> Music app team meeting starting soon in #ubuntu-touch-meeting
[19:00] <balloons> nik90, ping
[19:01] <nik90> balloons: pong
[19:02] <balloons> nik90, hey :-) So i'm flooding the projects with bug reports to help squash the autopilot testing needs.. And it's clock's turn ;-) Did we get a shortlist of features that need tested?
[19:03] <balloons> ahh no I'm pre-empting we'll be talking about in 30 mins in the meeting :-p
[19:03] <nik90> balloons: hehe
[19:03] <balloons> nik90, we'll talk then
[19:03] <balloons> haha
[19:03] <nik90> balloons: just about to ask
[19:04] <nik90> balloons: yeah
[19:04] <balloons> my head is spinning today
[19:04] <balloons> sry mate
[19:04] <nik90> no worries
[19:24] <slangasek> ogra: so, you may be interested to know that with upstart 1.8-0ubuntu4 (not in the latest daily yet), if you boot with --write-state-file, 'telinit u' will spit out a snapshot of upstart's state to /var/log/upstart/upstart.state
[19:24] <slangasek> ... though if I happen to do this while there's a nested init running under ubuntu_chroot, I get a kernel panic
[19:24] <slangasek> ... and it seems to only take effect on the second 'telinit u' (raising a bug about this)
[19:24] <slangasek> xnox: ^^ have you played much with --write-state-file?
[19:26] <penk_> what's the best way to keep display on?
[19:26] <xnox> slangasek: only briefly. It did work in simple system init with/without session inits.
[19:26]  * slangasek nods
[19:27] <slangasek> ogra: it seems the fix for disabling ubuntu_chroot hasn't landed in the dailies; does that have to wait for us to be building the android bits in LP?
[19:30] <slangasek> fun, sensorservice has gotten itself in a busy loop polling/reading the wrong fd
[19:31] <slangasek> ChickenCutlass, ogra: how could I report a bug on sensorservice for this?
[19:32] <ChickenCutlass> slangasek, that's a great question
[19:32] <slangasek> :-)
[19:34] <slangasek> hmm, completely reproducible, too... killed it off, it respawned with the same behavior
[19:35] <mhall119> Clock app team meeting starting now in #ubuntu-touch-meeting
[19:41] <cyphermox> rsalveti: you aware of current suspend issues with raring?
[19:41] <cyphermox> there are these entries is rickspencer3's logs:
[19:41] <cyphermox> Jun  7 11:34:01 ubuntu-phablet kernel: [ 1165.839462] power_suspend_late return -11
[19:41] <cyphermox> Jun  7 11:34:01 ubuntu-phablet kernel: [ 1165.839493] dpm_run_callback(): power_suspend_late+0x0/0x68 returns -11
[19:41] <cyphermox> Jun  7 11:34:01 ubuntu-phablet kernel: [ 1165.839493] PM: Device power.0 failed to suspend noirq: error -11
[19:42] <cyphermox> could definitely explain the power drain if the device keeps trying to suspend and come back
[19:43] <awe_> cyphermox, rsalveti is off today
[19:43] <cyphermox> oh
[19:43] <awe_> cyphermox, these should probably go to the attention of sforshee
[19:43] <cyphermox> yeah
[19:43] <awe_> ( aka powerd upstream )
[19:43] <awe_> ;D
[19:44] <cyphermox> bah
[19:44] <cyphermox> it's not conclusively screaming "wifi" at me though
[19:44] <sforshee> we need to figure out what device power.0 is
[19:44] <sforshee> which device does this happen on?
[19:45] <cyphermox> sforshee: mako
[19:45] <cyphermox> full log at https://launchpadlibrarian.net/141892521/syslog
[19:46] <sforshee> darn, I don't have the mako kernel locally. I'll have to clone it.
[19:47] <AskUbuntu> Ubuntu Touch on SII phone | http://askubuntu.com/q/305394
[19:48] <rtg_> sforshee, mako is a branch in ubuntu-saucy
[19:48] <sforshee> rtg_, okay. Actually I don't even have saucy locally since I haven't been doing kernel work recently :-P
[19:48] <rtg_> sforshee, so, you've turned into a kernel slacker ?
[19:49] <sforshee> guess so
[19:49] <sforshee> powerd now owns me
[19:50] <Djdomrep> hi guys
[19:54] <sforshee> cyphermox, awe_: [  178.372104] active wake lock smd_sns_dsps, time left 198
[19:54] <sforshee> something like this is in the log each time that happens
[19:56] <sforshee> arch/arm/mach-msm/smd_pkt.c:    "smd_sns_dsps"
[19:57] <awe_> SMD Packet Driver
[19:57] <awe_> provides a binary SMD non-muxed packet port interface
[19:58] <sforshee> awe_, is this the comm interface between the modem and app cpus?
[19:58] <awe_> no idea
[19:58] <cyphermox> could also be bluetooth on the mako
[19:58] <awe_> I talk to RILD
[19:58] <cyphermox> but I don't see why it would muck around so much with nothing paired and all
[19:59] <awe_> references to the modem in the source, so doubt it's BT
[19:59] <sforshee> it's in the core msm architecture code
[19:59] <cyphermox> just sayin', SMD is used for bluetooth too :)
[19:59] <sforshee> so I doubt it's bluetooth
[19:59] <cyphermox> alright
[20:00] <cyphermox> sforshee: do you think this could be a cause for battery drain?
[20:00] <awe_> well if it's preventing suspend from happening, yea
[20:01] <sforshee> cyphermox, I'd have to look more closely. If this is just occasional then no, but if it happens consistently then yes
[20:01] <awe_> cyphermox, was 3g data enabled?
[20:01] <awe_> was/is
[20:02] <cyphermox> awe_: no idea
[20:02] <cyphermox> this is rickspencer3's log
[20:02] <cyphermox> my guess is yes :)
[20:03] <sforshee> cyphermox, awe_: It only happens occasionally, so I don't think it's to blame
[20:04] <sforshee> I suspect this sends messages over the shared memory interface between the ARM cores in the SoC, and that it takes a wake lock when a new message arrives until it is read
[20:04] <cyphermox> ok
[20:05] <sforshee> I take that back
[20:05] <sforshee> at one point in the log that lock looks like it's held for a very long time
[20:07] <cyphermox> mmkay
[20:08] <rickspencer3> awe_, I put the steps I followed with the log in the bug report
[20:08] <cyphermox> just trying to figure out what might cause battery drain from those logs, if suspend might be one cause, and whether there's anything wireless related there
[20:08] <awe_> thanks rickspencer3
[20:08] <sforshee> cyphermox, awe_: so there's a suspend at 788.752601 but not another one until 1061.360628
[20:09] <sforshee> okay, so that wake lock isn't to blame for that
[20:10] <sforshee> userspace has suspend disabled
[20:10] <sforshee> so maybe the phone was being used
[20:10] <cyphermox> yeah
[20:12] <sforshee> so between 1090.730962 and 1223.482984 userspace has autosuspend enabled with the kernel, but the device is constantly waking up and going back to sleep
[20:13] <sforshee> it never stays suspended for more than a few seconds
[20:13] <sforshee> cyphermox, awe_: ^
[20:13] <rickspencer3> sforshee, could that be because I kept turning it back on?
[20:13] <rickspencer3> I had it in my hand the whole time
[20:13] <rickspencer3> and I was running top
[20:14] <sforshee> rickspencer3, no because then powerd would have disabled autosuspend
[20:14] <rickspencer3> I kept checking to see if I was getting the bug
[20:14] <rickspencer3> sforshee, fwiw, it's pretty simple to reproduce, but it requires going outside ;)
[20:15] <rickspencer3> or I guess you just kill your wireless
[20:15] <cyphermox> heh
[20:15] <cyphermox> wireless is useful...
[20:15] <cyphermox> I've been removing the connection file
[20:16] <sforshee> oh you know what, it's probably just that the timer the kernel uses stops ticking during suspend
[20:16] <sforshee> so suspends appear to take no time at all
[20:16] <balloons> nik90, I don't think I can assign a milestone to the autopilot bugs for clock app
[20:16] <balloons> give me a few mins and they will all be up though.. I'm sure you noticed the tag needs-autopilot-test
[20:17] <balloons> nik90, or if you want to simply add them all yourself that works :-)
[20:17] <nik90> balloons: I already started reporting the bugs :P
[20:17] <balloons> I'll let you be then :-)
[20:17] <nik90> hehe
[20:17] <balloons> ty niel
[20:17] <balloons> err.. tab complete.. ty nik90
[20:17] <niel> haha
[20:17] <mhall119> lol
[20:17] <niel> ;)
[20:17] <mhall119> no love for niel
[20:17] <balloons> nope..
[20:17]  * balloons revokes his ty to niel
[20:17] <niel> pings for days
[20:18]  * balloons hands niel an "I'm sorry" cookie. It has red frosting
[20:18] <niel> hehe
[20:18]  * niel stuff it in his face
[20:18]  * nik90 is rofl
[20:18]  * niel then eats ice cream
[20:21] <sforshee> that smd_sns_dsps does occur a lot more often than I'd like to see it, so we should figure out what's causing it
[20:22] <sforshee> maybe something to do with sensors
[20:22] <cyphermox> sforshee: see anything in the logs that would say something's amiss with wifi? I can't see anything wrong
[20:23] <sforshee> cyphermox, not obviously, but since it's a fullmac device (I assume) most of the stuff is happening inside the hw
[20:24] <sforshee> so we really don't have visibility into what might be going on there
[20:25] <cyphermox> sforshee: looking for something meaningful in powertop now
[20:27] <sforshee> cyphermox, I have to go pick up my kids, but I'll be back in about 30 minutes
[20:28] <cyphermox> sforshee: sure
[20:28] <cyphermox> I actually found something interesting
[20:28] <cyphermox> 26.3% ( 64.0)   [wcnss_wlan] <interrupt>
[20:29] <awe_> cyphermox, so...just thinking, we know powering off wifi doesn't work right now, correct?
[20:29] <awe_> so it's always on?
[20:29] <awe_> if so, that's going to kill the battery
[20:29] <awe_> my maguro eats battery like no tomorrow if wifi is enabled
[20:30] <awe_> ( stock android )
[20:30] <cyphermox> wifi can be disabled
[20:30] <cyphermox> it's just not being disabled in the way the driver expects it to be
[20:30] <awe_> can it be powered off?
[20:30] <nik90> balloons: done.https://launchpad.net/ubuntu-clock-app/+milestone/coreapps-13.10-month-3
[20:31] <mhall119> Terminal app team meeting starting now in #ubuntu-touch-meeting
[20:31] <awe_> I thought that was the bug we were talking about with renato?
[20:31] <cyphermox> awe_: I think ifconfig wlan0 down is possibly enough
[20:31] <balloons> nik90, awesome. I'm excitied to see all the core apps running with autopilot :-
[20:32] <nik90> balloons: me too. No more regressions
[20:32] <awe_> cyphermox, have you confirmed?
[20:32] <awe_> I know that's the way it's supposed to work, but hey... this is an Android driver
[20:32] <cyphermox> awe_: it's not the easiest thing to confirm when you need to be plugged in because yo ucan't use wifi
[20:33] <awe_> not sure I understand
[20:34] <cyphermox> using adb is skewing powertop results
[20:34] <cyphermox> looks like bringing the device down is "fixing" it, so perhaps there's something to fix in NM
[20:35] <cyphermox> I need to do it a couple of times to make sure
[20:35] <awe_> ok
[21:11] <slangasek> stgraber, ogra: so if we did have udev handling all the firmware events for us... we would want /dev bind-mounted into the android container, right?
[21:12] <slangasek> assuming, for the moment, that udev could be made to do a reasonable job of this in place of ueventd
[21:14] <stgraber> slangasek: so the reason why we don't usually do that is because of the console and pts devices which we typically want to be per-container, but as Android isn't spawning getty anyway and we can always mount a tmpfs on /dev/pts, I think that's doable
[21:16] <slangasek> stgraber: so what makes the pts devices per-container?  looking here, both instances of /dev/pts have near-identical contents
[21:16] <slangasek> http://paste.ubuntu.com/5743129/
[21:17] <slangasek> (not sure why one has /dev/pts/0 and the other has /dev/pts/1?)
[21:17] <slangasek> do these ptses actually exist in different namespaces?
[21:17] <slangasek> ptys, I mean
[21:17] <stgraber> slangasek: actually, I was wrong, we don't need a tmpfs. We just need /dev/pts to exist, which will be the case anyway. LXC mounts a new devpts instance on it at container startup time.
[21:17] <slangasek> ok
[21:20] <slangasek> stgraber: so if I want to bind mount /dev for a test, where should I do that?
[21:22] <stgraber> slangasek: easiest way would be to add "mount -o bind,ro /dev $LXC_ROOTFS_PATH/dev" to /var/lib/lxc/android/pre-start.sh in place of the "mkdir -p $LXC_ROOTFS_PATH/dev/pts"
[21:23] <slangasek> ok
[21:24] <slangasek> let's see how badly this blows up! :)
[21:28] <Jamper91> Hi
[21:35] <Jamper91> i have a problem, installing Ubuntu Touch, after i wirte the command phablet-flash -b, and download all things the console say " device detected as maguro..... download set to .... THE DEVIES NEEDS TO BE UNLOCKED FOR THE FOLLOWINg TO WORK" after that, the console say: waiting for devices
[21:37] <stgraber> slangasek: my hope is that mounting read-only will avoid any dammage to the Ubuntu side, however I'm not sure whether that won't also prevent writing to the actual entries. If that's the case, you'll have to drop the ,ro
[21:37] <slangasek> stgraber: 'ro' shouldn't prevent writing to the devices, that's controlled by 'nodev'
[21:39] <stgraber> slangasek: indeed and those that aren't devices are sockets so aren't affected by ro either. LXC may be unhappy though as it'll likely fail to setup console and the ttyX devices but I'd probably have to see the error to figure out how to workaround it.
[21:40] <slangasek> ok
[21:56] <sforshee> ricmm, am I right to assume that on_new_proximity_event() in powerd will not run on the glib main loop?
[22:45] <slangasek> stgraber: strange; with a bind mount, /proc/$(pidof /init)/root/dev is almost completely empty... something else seems to be overmounting it?
[22:46] <stgraber> slangasek: it very well could be that android is mounting a devtmpfs
[22:46] <stgraber> slangasek: look at  /proc/$(pidof /init)/root/proc/mounts
[22:46] <slangasek> cat: /proc/485/root/proc/mounts: No such file or directory
[22:47] <stgraber> cat /proc/485/mountinfo then, that should work
[22:47] <slangasek> yeah... was looking at that, but it's hard to read :)
[22:48] <slangasek> 60 59 0:5 / /dev rw,relatime shared:2 - devtmpfs udev rw,size=956896k,nr_inodes=156914,mode=755
[22:48] <slangasek> 39 60 0:25 / /dev rw,nosuid,relatime shared:10 - tmpfs tmpfs rw,mode=755
[22:48] <stgraber> sadly we don't have a 3.8+ kernel on the phone yet, otherwise we could just use lxc-attach, that'd make things much easier to debug ;)
[22:48] <slangasek> remind me what those columns mean?
[22:49] <slangasek> first column is the mount "id", second column is the mount id of the parent?
[22:49] <stgraber> mount_id, parent_id, major_minor
[22:49]  * slangasek nods
[22:49] <stgraber> so that shows a tmpfs being mounted on top of the bind mount
[22:50] <slangasek> right
[22:50] <stgraber> I'm assuming that's hardcoded somewhere in Android's init as I don't remember seeing that or proc or sys in the fstab
[22:51] <slangasek> yes, it doesn't seem to be in init.rc
[22:52] <slangasek> stgraber: so there's a way to make the container be unable to mount, right?
[22:55] <slangasek> stgraber: strings /var/lib/lxc/android/rootfs/init doesn't mention udev or devtmpfs, so I wonder where this could be hard-coded
[22:59] <ninjastick> Hola :)
[23:01] <ninjastick> I was wondering if a Desire HD is capable of running the Ubuntu for phones? Everything I find mentions dualcore phones
[23:02] <stgraber> slangasek: we could prevent the mount if we had apparmor. Short of that, the only other way we can do that is by dropping cap_sys_admin but that'll likely result in a lot of other things failing.4~
[23:08] <ninjastick> Does anyone know where to find a list of compatible devices?
[23:11] <slangasek> ninjastick: https://wiki.ubuntu.com/Touch/Devices
[23:14] <ninjastick> slangasek: Ah, thanks alot! I can see the Desire HD isn't on there...
[23:14] <ninjastick> Since the normal HTC Desire is on there, the DHD must be capable of running it aswell...
[23:16] <slangasek> ninjastick: each device requires porting, device names tell you virtually nothing about what kernel drivers are needed.  So someone would need to prepare an image for this specific device - but there's nothing about Ubuntu Touch that requires a dual-core, so there's no reason I know of that it wouldn't run on your device
[23:19] <ninjastick> I'm aware that it needs porting, I was looking at it spec-wise :) Most of the things I look at just mention the supah-doopah powers of Ubuntu Touch and dual-core devices, so I had an idea that it was made for dual-cores. And the HTC Desire appears to be a lot more popular than the HTC Desire HD was, so.. Well.. I might aswell just start looking for a new phone :P
[23:22] <ninjastick> Anyway, thanks alot for the help ^^
[23:22] <ninjastick> Cheers!


[08:34] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4414 Updates pocket
[15:08] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4408 Successfully built
[21:49] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4415 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[22:15] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4415 UNAPPROVED queue
[23:06] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4415 Generating diffs
[23:07] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4415 UNAPPROVED queue
[23:16] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4415 Proposed pocket