[00:01] <Orokusaki> anyone know how to insert a module automatically? I have tried /system/etc/init.d/90userinit.. this runs some commands, but not modprobe as of saucy.. the developer preview worked this way.. I have also recompiled and used init.tenderloin.rc and that doesn't seem to work either.. fustrated.. buy you a beer?
[00:11] <asterismo> hi people
[00:11] <asterismo> i want to know the set of applications that is shipped with ubuntu touch in the current version
[00:12] <asterismo> i'm planning to install it in a Samsung Galaxy Tab 2 p3113, at least the rarinig build, the newer is not quite working yet
[00:12] <asterismo> is there any email application (with PGP support), media player and basic apps?
[00:14] <asterismo> anyone?
[00:18] <RAOF> There isn't an email application.
[00:19] <RAOF> But there are a bunch of basic apps.
[00:19] <stgraber> ogra_, slangasek: ueventd in a polling loop, does that ring a bell?
[00:22] <stgraber> (polling fd=4 which is apparently a socket, I'm assuming netlink)
[00:24] <slangasek> stgraber: yes
[00:25] <slangasek> stgraber: I think I filed a bug about this; killall ueventd worked to let it respawn without the loop
[00:25] <slangasek> anyway, it's an android bug, not high on my list until we have an android source package :)
[00:25] <slangasek> https://bugs.launchpad.net/touch-preview-images/+bug/1190792
[00:26] <stgraber> slangasek: ah, simple enough to workaround then, thanks
[00:55] <stgraber> slangasek: could you pastebin /data/misc/wifi/WCNSS_qcom_cfg.ini?
[00:55] <slangasek> stgraber: from the N4?
[00:56] <stgraber> trying to bring up the wifi by hand, the kernel complains about that file being missing
[00:56] <stgraber> slangasek: yep
[00:56] <stgraber> as part of my loop-mount setup, I wiped /data, so that may explain why it's working for you and not for me (or I'm simply missing whatever usually generates it)
[00:56] <slangasek> stgraber: http://paste.ubuntu.com/5775722/
[00:56] <slangasek> ah :)
[00:59] <stgraber> and success, I've got wifi!
[00:59] <stgraber> so apparently something is supposed to copy /etc/wifi/* to /data/misc/wifi/ when Android starts, except that this part never happened on my phone...
[01:00]  * stgraber tries with a completely blank /data, see if it populates in that csae
[01:00] <stgraber> *case
[01:01] <stgraber> nope, that doesn't help... oh well, I'll just hack around it for now and have the pre-start script copy those over
[02:34] <stgraber> slangasek, rsalveti: so if you want to play with read-only loop-mount for nexus4: http://paste.ubuntu.com/5775889/
[02:35] <stgraber> that'll grab the various files from cdimage, generate a 1.3GB system.img file, push that to the data partition and flash a new bootimg
[02:35] <stgraber> works fine here, except for wifi which I need to manually tweak to get started and unity which doesn't start for some reason (the hybris tests all pass though)
[03:31] <brian_> Hi All.
[03:32] <brian_> I have a Galaxy Note II and would love to finally have Ubuntu running on it.
[03:32] <brian_> Is it possible yet?
[06:14] <arunprasadr> hello folks :) where can i find the source code for all core apps(including browser)?
[07:01] <diwic> hi, how do I enable wifi? Right now I'm on Nexus 4, saucy image, and no networks showing up in the indicator.
[07:01] <dholbach> good morning
[07:12] <diwic> fixed it (thanks askubuntu!)
[07:16] <brian_> Hi All. I have a Note II and was hoping I could install Ubuntu on it. Is that possible or is it not ready yet?
[07:22] <tvoss> mzanetti, can you point gema to the ubuntu touch bug tracker?
[07:23] <popey> Good morning
[07:23] <popey> tvoss: which component?
[07:23] <tvoss> popey, making calls
[07:23] <popey> http://bugs.launchpad.net/phone-app
[07:25] <mzanetti> tvoss: huh? bugs.launchpad.nat?
[07:25] <mzanetti> net
[07:43] <jussi> does ubuntu touch not have a messaging client? or how do I see messages... ?
[07:45] <seb128> jussi, there is a messaging indicator
[07:46] <seb128> jussi, the phone-app should do sms and stuff
[07:46] <seb128> jussi, friends-app does social protocols (facebook, etc)
[07:48] <jussi> seb128: hrm, phone app doesnt seem to have any messages at all. how does that work? I just see keypad and a contacts key.
[07:48] <popey> at the top, swipe across to conversation view
[07:49] <seb128> jussi, the header bar with the title, swipe left/right
[07:49] <seb128> ?
[07:49] <jussi> ahhhhhhhh
[07:50] <jussi> thanks seb128 and popey
[07:50] <seb128> jussi, yw!
[07:56] <seb128> hum, is the phone-app working for others on the saucy grouper image (classic one, not the container flipped one)
[07:56] <seb128> bah, gallery gives a white screen only as well
[07:56] <popey> seb128: not many apps are working on grouper for me
[07:57] <popey> (just flashed with todays daily)
[07:57] <popey> in fact i have yet to find an app that works
[07:57] <seb128> popey, calculator was working for me
[07:58] <popey> not for me
[07:58] <diwic> seb128, popey are you trying with the flipped or unflipped saucy images?
[07:58] <seb128> diwic, unflipped
[07:58] <popey> the one that comes from phablet-flash, which I believe is unflipped
[07:58] <seb128> I think
[07:59] <diwic> the flipped still seems to be in eternal reboot mode for me
[07:59] <seb128> diwic, the one from http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
[07:59] <didrocks> seb128: quite simple, just adb shell in the device
[07:59] <didrocks> seb128: if / looks like an ubuntu FS, you are in the flipped one
[08:00] <diwic> seb128, the unflipped is in /ubuntu-touch-preview and the flipped in /ubuntu-touch I think
[08:00] <seb128> didrocks, http://paste.ubuntu.com/5776423/
[08:01] <diwic> seb128, anyway my Nexus4 arrived yesterday evening, and it seems to work with the flipped image, so now I can start working on enabling something, finally :-)
[08:01] <didrocks> seb128: yeah, this is androidish :)
[08:01] <seb128> diwic, great!
[08:01] <seb128> didrocks, what I though, well it's broken for some reason :/
[08:01]  * seb128 ponders going back to raring image
[08:07] <popey> seb128: https://bugs.launchpad.net/touch-preview-images/+bug/1192068
[08:07] <popey> maybe confirm?
[08:08] <seb128> popey, done
[08:09] <popey> thanks
[08:16] <kalikiana> so… why is shell access not part of the install, but hidden in the release notes?
[08:17] <kalikiana> I literally followed every link until I saw it by chance
[08:19] <popey> kalikiana: you mean ssh installation?
[08:19] <kalikiana> popey, adb shell would've been enough
[08:19] <kalikiana> more specifically the part how to get into the ubuntu shell
[08:19] <popey> ahh
[08:19] <popey> are the release notes not a typical place to put it?
[08:20] <popey> https://wiki.ubuntu.com/Touch/ReleaseNotes#Accessing_the_device_over_ADB seems pretty clear
[08:20]  * popey shrugs
[08:20] <kalikiana> under release notes I would expect things like "3g is hosed" or "app missing"
[08:21] <kalikiana> the "release notes" in this case are more like first steps after install
[08:22] <kalikiana> I'm not saying it's not cleary, it's simply not what the page claims to be
[08:22] <popey> yeah, i can understand that
[08:22] <popey> maybe it needs an "Install" page, a "PostInstall" and "ReleaseNotes"
[08:22] <popey> ?
[08:24] <kalikiana> the first half of the "release notes" page is what should be "PostInstall"
[08:24] <kalikiana> after that come the actual release notes
[08:24] <kalikiana> like known issues, device specific and that stuff
[08:31] <JamesTait> Good morning all, happy Autistic Pride Day! :-D
[08:53] <ogra_> stgraber, nice ! integrating your code should be easy ...
[08:55] <brian_> Is there an OS ready for Note II yet?
[09:58] <didrocks> ogra_: ++
[09:58] <ogra_> :)
[09:59] <didrocks> nice and thanks to avoid me writing such a similar email :)
[10:01]  * ogra_ hasnt used a mail signarute in years .... but is inclined to put "life is not a kindergarten" into his signature ...
[10:01] <didrocks> heh, would be appropriate :)
[11:18] <vadi> Ubuntu Touches Qt Creator is failing to find phonon... is this version of Qt Creator intended as a replacement or a supplement to the original?
[11:20] <popey> vadi: not sure I understand, you're using qtcreator on ubuntu (what version?) and it doesn't find your phone? (which phone?)
[11:21] <vadi> Hey. Using Ubuntu 12.04. I've been using Qt Creator to develop Qt apps, and installed the Ubuntu Touch stuff as I'd like to play with that. Because I now had two icons in the dash (I installed the qt creator originally from a .run installer), I uninstalled the official one
[11:21] <katie> anyone know how to fix this issue when flashing a phone -- 'Error when downloading, ensure connection' -- ?
[11:21] <vadi> I'm trying to build a project I have (unrelated to touch) and it is failing to find phonon, the media framework of qt, that the project requires
[11:21] <vadi> Is it using Qt 5 by chance? I heard that was removed there
[11:22] <popey> vadi: ours is built on qt5, yes
[11:22] <vadi> Ah ok, so I should have kept the old
[11:22] <vadi> Also in the Welcome tab, when I click on the Develop tab, I get a whole lot of unresponsive windows opened. Is this known?
[11:23] <vadi> About four of them...
[11:23] <popey> I have seen that before, yes
[11:23] <vadi> Okay
[11:23] <popey> I had to clear out my .config/QtProject folder to fix that iirc
[11:24] <vadi> Having these two side by side might prove difficult, huh
[11:27] <popey> yeah
[11:32] <tvoss> zsombi, ping
[11:32] <zsombi> tvoss: pong
[11:33] <tvoss> zsombi, mind pinging me the blueprint for the alarm service
[11:33] <zsombi> tvoss: sure, in a sec
[11:33] <zsombi> tvoss: https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api
[11:34] <tvoss> zsombi, thanks :)
[11:34] <zsombi> tvoss: welcome :)
[11:42] <aquarius> did I see the other day that the web browser is now in the archives?
[11:44] <ogra_> yup
[11:46] <aquarius> ogra_, what's the package name? maybe I'm just blind
[11:46] <ogra_> root@ubuntu-phablet:/# apt-cache madison webbrowser-app
[11:46] <ogra_> webbrowser-app | 0.20daily13.06.14-0ubuntu1 | http://ports.ubuntu.com/ubuntu-ports/ saucy/universe armhf Packages
[11:46] <ogra_> root@ubuntu-phablet:/#
[11:47] <aquarius> http://packages.ubuntu.com/search?keywords=webbrowser-app ?
[11:47] <aquarius> shows nothing...
[11:47] <aquarius> um. what's ports.ubuntu.com? :)
[11:47] <popey> that site shows nothing for saucy at all aquarius
[11:48] <aquarius> oh, OK
[11:48] <popey> (I looked too)
[11:48] <aquarius> also, that means it's only in saucy, so nm :)
[11:48] <ogra_> and packages.u.c doesnt show armhf iirc
[11:49]  * aquarius builds
[11:51] <aquarius> nice, new web game works in the browser.
[11:51] <aquarius> apart from not showing web fonts, but that's not a total crisis :)
[11:52] <pmcgowan> hey aquarius hows it going
[11:58] <aquarius> so far, well :)
[11:59] <aquarius> speaking as a bloke who has been working for himself for 12 hours so far. Even I can't screw it all up that fast ;)
[12:01] <tvoss> aquarius, hey dude :)
[12:03] <aquarius> heya tvoss!
[12:04] <tvoss> aquarius, how goes?
[12:04] <sergiusens> ogra_: just saw your last two comments, going to do that now
[12:05] <ogra_> sergiusens, great
[12:05] <ogra_> sergiusens, i think i have an idea whats wrong though ...  but would be good to have you confirming that assumption via adbd in the initrd
[12:09] <aquarius> tvoss, so far, pretty well, I think :)
[12:15] <xnox> ogra_: where abouts does the android-rootfs build lives these days? i'm after latest/greatest/saucy one.
[12:16] <xnox> ogra_: as in all the compilation rules & magic.
[12:16] <ogra_> xnox, you mean the binary images ?
[12:16] <ogra_> see the porting guide ... its all included in the repo
[12:16] <xnox> ogra_: compilation from source to binaries.
[12:17] <ogra_> https://wiki.ubuntu.com/Touch/Porting is how you build it
[12:17] <xnox> ogra_: ok, thanks, reading.
[12:17] <ogra_> but for the package we habe a tarball of the repo
[12:17] <ogra_> http://phablet.ubuntu.com/export/
[12:17] <xnox> ogra_: and that's everything we'd want to build using the android cross-toolchain?
[12:17] <xnox> as a normal deb?
[12:17] <ogra_> so what you want as a first step is add a debian dir to that ...
[12:18] <ogra_> then have debian rules  call . /build/envsetup.sh ...
[12:18] <ogra_> and after that iterate over the four subarches calling "brunch $subarch"
[12:18] <ogra_> the build will be trivial
[12:19] <ogra_> at least the initial build
[12:19] <ogra_> the binaries we need should all end up in the out/ dir then
[12:20] <xnox> ogra_: sounds similarish to how the cross-toolchain is built.....
[12:20] <ogra_> (which would be system.img recovery.img and ramdisk.img per arch)
[12:20] <xnox> ack.
[12:20] <ogra_> (would be good to just dump these into /usr/lib/$packagename-subarch/
[12:20] <ogra_> )
[12:21] <xnox> ogra_: and the export tarballs are generated from the repo checkout?
[12:21]  * xnox likes repo checkouts.
[12:21] <ogra_> somehow, yeas, not sure how exactly though, rsalveti does that, he can surely tell you
[12:23] <sergiusens> xnox: can you login to hespiridium?
[12:25] <sergiusens> xnox: building android is basically, repo sync; source build/envsetup.sh; brunch $device
[12:25] <sergiusens> xnox: http://bazaar.launchpad.net/~phablet-team/touch-preview-images/phablet-build-scripts/view/head:/ubuntu-touch-build
[12:25] <xnox> sergiusens: permission denied. is that the gitweb instance? i'd like to have access to that.
[12:26] <xnox> sergiusens: well sure, it's just I wanna now build it using packaged toolchain ;-)
[12:26] <sergiusens> xnox: yeah, that's where all the git repos are
[12:26]  * xnox goes to poke is
[12:26] <sergiusens> xnox: no one works directly on the server though, just in case :-) But feel free to login asking IS and snoop all you want
[12:27] <xnox> sergiusens: push access?
[12:27] <sergiusens> xnox: yeah, you would get push access :-)
[12:27] <xnox> sergiusens: i'd like to push the cross-building toolchain git repository & repo manifest there....
[12:27] <sergiusens> xnox: today only rsalveti and myself have that
[12:28] <sergiusens> xnox: wait, why the toolchain?
[12:28] <xnox> cause launchpad doesn't support git & it's in github at the moment.
[12:29] <sergiusens> xnox: oh, so not packaged still
[12:29] <xnox> sergiusens: well, it's the debian source package.
[12:29] <xnox> sergiusens: gcc-arm-linux-androideabi from ppa:ubuntu-toolchain-r/test at the moment.
[12:29] <ogra_> xnox, well, we would like it to use the packaged binary of the toolchain
[12:29] <xnox> ogra_: sure.
[12:30] <ogra_> so it doesnt become a part of the build
[12:30] <sergiusens> xnox: we are doing some crazy pull-lp-source and pull-lp-bin magic for stuff that's packaged
[12:31] <sergiusens> xnox: I would prefer we still pull the source package manually for now and then modify the build repo to pick it up from wherever it's installed
[12:31] <xnox> ogra_: i don't have any git hosting at the moment. so i'm thinking where to store it. cause i dislike github. I fully understand that we do not want to bootstrap toolchain during android build, and instead simply build-depends on gcc-arm-linux-androideabi fromt eh archive.
[12:32] <ogra_> ah, k
[12:32] <xnox> sergiusens: no. apt-get install gcc-arm-linux-androideabi and use it from /usr/bin/. Not pull-lp-source nor build anything.
[12:32] <sergiusens> xnox: perfect
[12:33]  * xnox could use git.debian.org mrah.
[12:33] <bfiller> tvoss, Kaleo : hangout? content picking..
[12:33] <sergiusens> xnox: just got confused with the mention of adding it to the repo manifest
[12:33] <xnox> sergiusens: gcc-arm-linux-androideabi has it's own minimalistic manifest to pull correct bionic & headers.
[12:33] <xnox> (5 repos only)
[12:34] <xnox> + android core/build machinery
[12:34] <tvoss> bfiller, I asked the guys to skip this week, all were good
[12:34] <tvoss> bfiller, will work with gusch to answer questions and iron out issues
[12:34] <tvoss> bfiller, next week as usual
[12:34] <sergiusens> xnox: ok, as long as the default build isn't modified, it's all ok... feel free to push and maybe provide an alternative manifest
[12:35] <bfiller> tvoss: ok, jamie and tyler and I are on
[12:35] <xnox> sergiusens: yeah, I'm hoping to host two new git repositories on there and that's all.
[12:36] <sergiusens> xnox: perfectly fine with that
[12:38] <xnox> do we have gerrit yet?
[12:38] <sergiusens> xnox: not yet
[12:38] <xnox> ok.
[12:47]  * ogra_ uploads the last fix to make grouper work in flipped
[12:50] <xnox> ogra_: \o/
[12:50] <ogra_> now its just manta thats missing
[13:05] <Black_Mage> anyone knows about bluetooth support with nexus 4?
[13:28] <nik90> ckpringle: sry to disturb, could you check with jouni regarding the visual desings?
[13:28] <ckpringle> nik90: he isn't online?
[13:28] <nik90> ckpringle: I was told they would be handed over on friday
[13:28] <nik90> ckpringle: no I cant find him in this channel
[13:30] <jounih> nik90: heya
[13:30] <nik90> jounih: hi
[13:31] <nik90> jounih: I was just wondering on the progress of the visual designs
[13:31] <jounih> nik90: the designer's back from holiday now, we should be able to push the timer and stopwatch designs end of today
[13:32] <nik90> jounih: ah nice. Would that been an update to your existing branch?
[13:32] <nik90> the one where we got the clock designs?
[13:32] <jounih> nik90: yep, i'll push to my branch, the same one as before. Do you want me to drop you an email once it's there?
[13:34] <nik90> jounih: yes that would be nice
[13:35] <nik90> jounih: I also had another question regarding the icon assets like the delete icon
[13:35] <nik90> jounih: or would that come as part of a general package for everyone?
[13:37] <jounih> nik90: Kaleo should know more about when the icon theme is landing and how to use it
[13:37] <jounih> it will be a general theme for everyone to use
[13:38] <nik90> jounih: ok
[13:38] <ogra_> sergiusens, aha ... echo 0 >/proc/sys/kernel/panic
[13:38] <ogra_> that should prevent the reboot ...
[13:39] <ogra_> (not sure if the kernel panicing tears down adbd though, i'd rather have the script execution held while adbd is running than poking off the last resort function of the kernel)
[13:40] <ogra_> (it blocks fine on grouper and moguro here, not sure why manta is so different)
[13:47] <gusch> jhodapp: ping
[13:48] <seb128> did anyone look packaging/adding qtsystems (https://qt.gitorious.org/qt/qtsystems) to the touch image?
[13:51] <ogra_> seb128, i guess thats a question to the sdk team ... bzoltan etc :)
[13:52] <seb128> ogra_, does they read this channel or do I better chase them somewhere else? ;-)
[13:52] <JamesTait> tvoss, mhr3: ping re X-Ubuntu-Touch in the .desktop file.
[13:52] <tvoss> JamesTait, about to jump on a call
[13:52] <ogra_> seb128, well, i guess i just pinged bzoltan above :)
[13:52] <seb128> ;-)
[13:52] <seb128> ogra_, bah, can't win ... after reboots and reboots I've working apps on grouper, but no onscreen keyboard :/
[13:52] <bzoltan> seb128: We have qtsystems in the qt5-proper PPA
[13:53] <ogra_> seb128, bah
[13:53] <ogra_> bzoltan, can that move to the archive ?
[13:53] <JamesTait> tvoss, no worries, it can wait. :)
[13:53] <seb128> bzoltan, is that going to be added to the default set of packages/the image at some point?
[13:53] <tvoss> JamesTait, cool
[13:53] <seb128> bzoltan, I would like to use it to get the disk space infos for the system settings info panel
[13:53] <davmor2> seb128: grouper is nexus7 right?
[13:53] <ogra_> yes
[13:53] <seb128> yes
[13:54] <ogra_> seems to be a saucy specific issue there ... i have the same (mis)behavior on flipped
[13:54] <esigolo> there is any progres log or dev status for the final release?
[13:55] <ogra_> esigolo, there are weekly updates to the mailing list
[13:55] <esigolo> ogra_: i'm following I just wondered if there was a website or something
[13:55] <bzoltan> seb128:  I do not know the distro policy, but you know the qtsensors, qt3d, qtlocation, qtfeedback, qtconnectivity, qtsystems, qtpim, qtwayland modules are not released officially with the Qt5, so they are just our packages made from the git source
[13:55] <pmcgowan> seb128, is there an interface in qtmobility for that?
[13:56] <davmor2> seb128: what I found helped was to open the browser,  click on the url, so the keyboard came up and then reboot, I found it more reliably brought up the keyboard in dash then.  The other thing let the n7 boot then give it 30-60 seconds for everything to display before actually unlocking it
[13:56] <ogra_> bzoltan, well, we have the others in the archive, no ? (at least we dont use any qt related PPA anymore) so it should be possible to bring in qtsystems too
[13:56] <pmcgowan> seb128,  QSystemStorageInfo
[13:56] <seb128> pmcgowan, yes, but from what I found on google, qtmobility is for qt 4.8
[13:56] <pmcgowan> oh
[13:56] <davmor2> seb128: I found that if you open it as soon as the display appeared it played up
[13:56] <seb128> pmcgowan, and qtsystems is what is recommended for qt5
[13:56] <bzoltan> seb128: I have the qtsystem from https://launchpad.net/~ubuntu-sdk-team/+archive/ppa
[13:57] <seb128> bzoltan, I will try that, thanks!
[13:57] <pmcgowan> seb128, right
[13:57] <seb128> davmor2, thanks for the tips, will try that
[13:58] <bzoltan> ogra_:  I really do not know why it is not in the archive ... I just made an apt-cache policy ... Mirv could tell us, but he is off for two weeks (bugger)
[13:58] <sergiusens> ogra_: manta is based out of a newer AOSP codebase
[13:58] <ogra_> geez, eho approved that !
[13:58] <ogra_> *who even
[13:58] <seb128> bzoltan, ogra_: that can wait for Mirv to be back
[13:58] <bzoltan> seb128: we even provide the qtsystems5-examples
[13:58] <seb128> bzoltan, I will use the ppa meanwhile, thanks!
[13:58] <ogra_> sergiusens, ah
[13:59] <davmor2> seb128: n7 seems to play up far more than the galaxy nexus for me
[13:59] <seb128> davmor2, weird, the onscreen keyboard works in the browser, not in the app lens though
[13:59] <ogra_> yeah, that might explain ...
[13:59] <bzoltan> seb128:  good luck and feel free to ping me if something is wrong
[13:59] <seb128> bzoltan, thanks, will do
[13:59] <davmor2> seb128: :) told you
[13:59] <ogra_> davmor2, definitely
[14:02] <sergiusens> ogra_: echo "initrd: starting adbd for debugging" >/dev/kmsg || true
[14:02] <ogra_> well, that obviously showed up in your demsg
[14:02] <davmor2> ogra_, sergiusens: any idea when 3g/phone signal strengths will land?  There are a few things that are missing but can be worked around however you're 3g not working due to signal strength isn't obvious till you move 3 feet away from the big steel post and it works fine :)
[14:02] <ogra_> the prob is that it actually moves on after this
[14:02] <sergiusens> ogra_: yeah, true :-)
[14:02] <ogra_> after adbd it should just stop ...
[14:03] <ogra_> and it does so on grouper and maguro for me ... i tested that code on both beforee uploading
[14:03] <ogra_> apparently manta moves on and in the end kills /init (of the initrd) and doesnt find /sbin/init since it didnt find the disk
[14:05] <mhall119> popey: you should get some core app developers on UUPC
[14:05] <popey> ooh!
[14:05] <ogra_> (and i expect "echo 0 >/proc/sys/kernel/panic" to not help with that)
[14:05]  * popey looks at nik90 
[14:11] <sergiusens> ogra_: hmm... I think I found the issue, abootimg is lying to me
[14:11] <ogra_> oh ?
[14:11] <sergiusens> ogra_: abootimg -u says it updates nicely, but I just grabbed it again and it wasn't updated
[14:12] <ogra_> oh, thats evil
[14:12] <sergiusens> let me go with a create
[14:12] <ogra_> it usually complains loudly if there are issues
[14:18] <sergiusens> ogra_: ok, going to recovery to get the last_kmsg was the wrong thing it seems
[14:19] <ogra_> oh, why /
[14:19] <sergiusens> ogra_: look at this http://paste.ubuntu.com/5777232/
[14:19] <sergiusens> ogra_: grabbed it with adb wait-for-device shell cat /proc/last_kmsg|pastebinit
[14:20] <ogra_> yeah, looks fine that way
[14:20] <ogra_> but it still reboots i guess ?
[14:20] <sergiusens> ogra_: yeah system watchdog timer reset
[14:20]  * ogra_ doesnt get why wait wouldnt work, thats a posix function
[14:21] <sergiusens> ogra_: wait did work it seems
[14:22] <ogra_> i'll try to rework the adbd part after the standup so it is an actual panic function, probably that helps
[14:22] <ogra_> oh !
[14:22] <sergiusens> ogra_: going to give you adb wait-for-device shell cat /scripts/touch|pastebinit
[14:22] <sergiusens> ogra_: I added a logline after the wait
[14:22] <ogra_> adb shell find /dev -name userdata|pastebinit ...
[14:22] <ogra_> see what that gives
[14:23] <sergiusens> ogra_: http://paste.ubuntu.com/5777239/
[14:23] <ogra_> ah, we have it twice
[14:23] <ogra_> k
[14:23] <ogra_> i know what to do then :)
[14:28] <awe> ogra_, why are there .bootimg-<device> files in the daily-preinstalled folder?  Are these required or just side-artifacts of the build?
[14:28] <ogra_> side artifact and helpful for hacking them
[14:28] <sergiusens> awe: you don't need them, they should be inside of the .*armel.*zip
[14:28] <ogra_> awe, just ingore them
[14:29] <awe> sergiusens, that's what I figured, but never safe to assume...
[14:29] <ogra_> *ignore too :)
[14:32] <mhall119> ricmm: still having those weird app loading/osk problems on nexus 7
[14:32] <mhall119> on saucy-15 build now
[14:32] <ogra_> same on flipped saucy ...
[14:32] <ogra_> works every nth boot
[14:33] <mhall119> yeah
[14:33] <ogra_> and looks like a race ...
[14:33] <mhall119> can't find any pattern to when it does and when it doesn't
[14:34] <popey> mhall119: i added checkers to the collection ppa and updated the metapackage
[14:34] <mhall119> I've also noticed that taps on the OSK in the dash are falling through to the launcher icons under it again
[14:34] <mhall119> popey: \o/
[14:34] <mhall119> popey: is that 2-player, or with an AI?
[14:34] <popey> both!
[14:35] <popey> i didnt realise till after I uploaded it, that it has a 2 player option
[14:35] <mhall119> nie
[14:35] <mhall119> nice too
[14:35] <mhall119> ricmm: it does seem that the OSK and app issues might be separate issues though, sometimes the keyboard works and the apps don't
[14:37] <mhall119> though I can't recall a time when the opposite was true, that apps worked and the keyboard didn't
[14:38] <ricmm> mhall119: ok, we are working right now on enabling certain things that will make this a non-issue
[14:39] <ricmm> also, once the new notifications land this should be automatically fixed
[14:39] <ricmm> stay tuned today for such developments
[14:39]  * mhall119 is very curious about how the notifications are fixing this
[14:40] <ricmm> the notifications are the culprit, they try to register something out-of-sync with the app manager which causes it to crash mid-way while the shell is coming up
[14:40] <mhall119> ah ha!  now it makes sense
[14:40] <ricmm> which makes it discard the session observers the shell holds, so it never gets the events of apps being started
[14:40] <mhall119> so when can we expect this?
[14:41]  * mhall119 isn't opposed to compiling a few packages from source
[14:42] <zsombi> tvoss: ping
[14:42] <ricmm> mhall119: today perhaps
[14:42] <tvoss> zsombi, pong
[14:42] <zsombi> tvoss: could we have the tomorrow's alarmmeeting ~30 mins or 1h earlier?
[14:43] <rsalveti> stgraber: awesome, will give that a try today, thanks!
[14:44] <mhall119> ricmm: I'll keep hitting F5 on the changelog URL then :)
[14:44] <ogra_> rsalveti, its so trivial that i was tempted to just implement it :)
[14:44] <zsombi> tvoss: otherwise I can be there for 30 mins only :(
[14:44] <mhall119> tvoss: zsombi: would it be possible to get work items for the alarm API assigned to milestones so we can know when they might be ready?
[14:45] <tvoss> zsombi, let me see what google cal says :)
[14:45] <tvoss> mhall119, sure
[14:45] <mhall119> thanks tvoss
[14:46] <zsombi> tvoss: okay, thx :)
[14:47] <rsalveti> ogra_: :-)
[14:47] <rsalveti> xnox: why do you need git access?
[14:47]  * ogra_ triggers the flipped build that should make grouper fully work now 
[14:47] <rsalveti> unhappy about tracking the package in bzr?
[14:47] <rsalveti> or you really need to track that in git?
[14:47]  * mhall119 kisses ogra_ 
[14:48]  * ogra_ kisses mhall119 back
[14:48] <ogra_> so much love here today :)
[14:48] <xnox> rsalveti: https://raw.github.com/xnox/manifest-gcc-arm-linux-androideabi/master/default.xml
[14:48]  * awe wishes we stick to hugs
[14:48] <mhall119> yeah, those are less awkward
[14:49] <rsalveti> xnox: oh, ok, so you need to run repo against this manifest and such, right?
[14:49] <xnox> rsalveti: that's the manifest for debian source package of gcc androideabi cross-toolchain. I could track it in bzr, but that would be cumbersome to maintain.
[14:49] <ogra_> :)
[14:49] <xnox> rsalveti: correct.
[14:50] <davmor2> ogra_: to bring some balance to the channel I hate you all for being so damn good at you jobs.....oh man failed at the last hurdle ;)
[14:50] <rsalveti> xnox: sounds good, we can push your repo there, but you'd need to ask is permission to push it via ssh
[14:50] <ogra_> haha
[14:50] <rsalveti> xnox: and yes, the tarball is created after a clean repo sync
[14:51] <xnox> rsalveti: i think #is gave me permissions now.
[14:51] <rsalveti> xnox: cool, just please be careful when pushing stuff there :-)
[14:51] <xnox> rsalveti: ok, about the tarball. is there a magic target or something?
[14:52] <davmor2> seb128: did you have any joy with the keyboard on the n7 in the end?
[14:52] <xnox> ogra_: rsalveti: at the moment i noticed that brunch builds, well everything. but are all .img needed for flipped container model? e.g. the userdata.img ?
[14:53] <ogra_> xnox, we need system, ramdisk and recovery
[14:53] <rsalveti> xnox: the dump contains the needed files to build all the 4 targets (just missing the binary blobs)
[14:53] <rsalveti> yeah
[14:53] <seb128> davmor2, I plugged an usb keyboard
[14:54] <ogra_> cheater !!
[14:54] <xnox> ogra_: ack. /me ponders if i'll trick the build system into building just those images.
[14:54] <ogra_> xnox, i would bother with the build system for the start ...
[14:55] <rsalveti> yeah, don't worry about that unless you really need to customize it
[14:55] <ogra_> xnox, we can talk again in 15,.04 ....  after you sorted the debian/copyright file
[14:55] <xnox> ogra_:  =))))
[14:55] <ogra_> getting the stuff packaged and building as is should be really quick ... but the surrounding work is hell
[14:57] <xnox> ogra_: as Dan Brown's fans would say, specifically which of the Dante's 9 circles of hell you refer to here =)
[14:58] <ogra_> after taking a look you will realize that all of them are involved :)
[14:58] <ogra_> just a licensecheck over the whole tree sould give you an impression
[14:59] <xnox> well i've seen half of main rebuilt in the scrollback.
[15:00] <stgraber> rsalveti: current known issues with that script is unity not starting (unity8 segfaults) and the wifi not coming up automatically (I'm planning to add a one-line change to the Android wlan script to fix that one)
[15:00] <ogra_> stgraber, it does come up on normal flipped (afaik)
[15:00] <ogra_> so we should (eventually) research whats different there
[15:01] <davmor2> seb128: well there is always one with a thinking out of the box idea isn't there :)
[15:02] <seb128> lol, yeah ;-)
[15:05] <rsalveti> stgraber: seg fault is interesting, weird
[15:05] <seb128> davmor2, btw, I think that was you that was mentioning the screen blinking every now and then when the device is suspended? did you ever open a bug about that?
[15:07] <stgraber> ogra_: right. AFAICT something in Android is supposed to populate /data/misc/wifi with the content from /etc/wifi at boot time. But for some reason that doesn't happen here, so I have to manually do the copy, then I can load the firmware just fine...
[15:07] <davmor2> seb128: Erm I have no idea I think I went to but had no idea what to file it against.  Let me double check though
[15:07] <ogra_> stgraber, thats done by the factory reset function of recovery
[15:08] <seb128> davmor2, https://bugs.launchpad.net/ubuntu-touch-preview/+bugs
[15:08] <ogra_> stgraber, we should see if we can rip that info out there at build time and kind of integrate it in our installer
[15:08] <seb128> davmor2, report here in doubt ;-)
[15:08] <davmor2> seb128: ah nice /me bookmarks the page
[15:09] <seb128> davmor2, https://bugs.launchpad.net/touch-preview-images/+bug/1187867
[15:09] <ogra_> we'll hopefully have in-archive bugs soon
[15:09] <seb128> davmor2, in fact seems like it's reported and you commented on it
[15:09] <ogra_> only a few packages left in the PPA
[15:09] <seb128> ogra_, what component would you bug about this one?
[15:09] <ogra_> powerd
[15:09] <ogra_> or kernel
[15:10] <ogra_> actually i noticed that the screen isnt really off
[15:10] <davmor2> seb128: yeap that would be why I couldn't remember filing it mhall119 beat me to it :)
[15:10] <stgraber> ogra_: not sure that's it though (but certainly something we should look into). mako.rc contains:
[15:10] <stgraber>     # Workaround for conn_init not copying the updated firmware
[15:10] <stgraber>     rm /data/misc/wifi/WCNSS_qcom_cfg.ini
[15:10] <stgraber>     rm /data/misc/wifi/WCNSS_qcom_wlan_nv.bin
[15:11] <stgraber> but I'm not seeing anything that creates those file, so I'm not sure how they're supposed to appear post-boot when init is removing them right after /data is mounted...
[15:11] <ogra_> recovery should create them
[15:11] <stgraber> sure, but then they'd be removed by android at boot time
[15:11] <ogra_> i guess looking at the google script that does a plain android install might help
[15:12] <stgraber> the two lines I pasted earlier come from the init script in post-fs-data
[15:12] <ogra_> there should be something creating them in the device specific init
[15:13] <stgraber> indeed there should be, just not seeing it ;)
[15:14] <mhall119> kenvandine: ping
[15:14] <stgraber> ogra_: ah, there's a comment referring to conn_init, maybe that's what's usually creating those (not sure why it wouldn't be called though)
[15:14] <ogra_> yeah
[15:14] <ogra_> just looking at the code here
[15:16] <ogra_> seems that copies it in place if the files dont exist
[15:16] <ogra_> and it is called from the init.rc
[15:17] <mhall119> Kaleo: hey, are you still working on a way to get commandline args from a QML component?
[15:17] <stgraber> ogra_: before you ask for it, http://paste.ubuntu.com/5777396/
[15:18] <ogra_> stgraber, heh
[15:18] <ogra_> looks fine
[15:20] <stgraber> [    5.871265] fs_mgr: No entries found in fstab
[15:20] <stgraber> [    5.871356] init: fs_mgr_mount_all returned an error
[15:20] <stgraber> not sure if that could be related (some condition not being met in init as a result of that)
[15:20] <stgraber> (those come from dmesg)
[15:20] <kenvandine> mhall119, pong
[15:22] <ogra_> stgraber, well, we can rip fs_mgr out of the init.rc dont worry
[15:22] <mhall119> kenvandine: hiya, couple of things
[15:22] <mhall119> 1) Did you see my screenshot on discourse about the system settings app on a nexus 7?
[15:23] <stgraber> ogra_: yeah, that's probably a good idea, we're not really using it anyway
[15:23] <kenvandine> mhall119, not yet
[15:23] <mhall119> and 2) does/will the Friends backend service update the messaging menu in Touch?
[15:23] <mhall119> kenvandine: http://test.ubuntu-discourse.org/t/system-settings-for-ubuntu-touch-development-is-underway/225/15?u=mhall119
[15:23] <kenvandine> mhall119, ah...
[15:24] <kenvandine> what version?
[15:24] <kenvandine> i think i fixed that yesterday
[15:24] <mhall119> of system-settings?
[15:24] <kenvandine> yeah
[15:24] <kenvandine> it was too wide for the n4
[15:24] <mhall119> whatever was available to install last night
[15:24] <kenvandine> yeah
[15:24] <kenvandine> update today :)
[15:24] <AskUbuntu> Ubuntu Touch on Samsung galaxy Nexus yakjuxw 4.2.1 | http://askubuntu.com/q/309749
[15:25] <stgraber> ogra_: I'll try to add a bogus entry in fstab, see if that makes it happy ;)
[15:26] <ogra_> either that or just use the same code we use to rip ubuntu_chroot out of init.rc
[15:26] <ogra_> (unless thats hardcoded in init.rc)
[15:26] <mhall119> kenvandine: it could use an icon too :)
[15:28] <kenvandine> mhall119, yeah
[15:28] <kenvandine> we know :)
[15:28] <kenvandine> mhall119, if you install signon-ui from saucy-proposed, you can add/remove accounts too :)
[15:28] <mhall119> kenvandine: ah, yes, it fits perfectly now
[15:29] <kenvandine> :)
[15:30] <mhall119> kenvandine: now I just need my social network notifications in my messaging menu
[15:30] <kenvandine> mhall119, yeah yeah... :)
[15:31] <mhall119> and google UOA setup
[15:31] <mhall119> and..
[15:31] <mhall119> and...
[15:31] <mhall119> and....
[15:31] <Asad2005> My nexus 4 build is JDQ39, where can i get the official image to download in my pc just in case ubuntu installation fail
[15:33] <ogra_> there is a link on the install wikipage iirc
[15:33] <stgraber> ogra_: do you have code for the mount_all command in init?
[15:33] <stgraber> ogra_: I'm wondering if the fact that we don't mount the /data partition means that post-fs-data is never triggered which would explain why the rest never happens
[15:34] <ogra_> stgraber, in the initra.fs-tools-ubuntu-touch package
[15:34]  * tvoss is happy to read this: http://www.ubuntu.com/phone/carrier-advisory-group
[15:34] <ogra_> i'm just about to change that to make nexus 10 work with flipped though
[15:35] <ogra_> oh, wait, you mean the android init ? no i didnt touch the android side at all (and would like to avoid that as much as possible, fearing to break any binary blob assumptions)
[15:37] <stgraber> ogra_: I "think" I may have a way around that, trying to now. Replacing the "mount_all fstab.mako" call by a "trigger post-fs-data" call
[15:43] <Black_Mage> anyone knows about bluetooth support with nexus 4?
[15:43] <rsalveti> tvoss: cool!
[15:47] <sergiusens> ricmm: https://launchpad.net/~phablet-team/+archive/mir/+build/4723746
[15:48] <stgraber> ogra_: right, so removing the mount_all line fixed the error in dmesg but didn't resolve the wireless issue...
[15:49] <sergiusens> tvoss: what is that?
[15:49] <sergiusens> goes and posts on g+
[15:51] <stgraber> slangasek: can you paste a "ps faux" of you phone? I want to see if I'm missing some android services here
[15:51] <apw> in the touch browser, when you flick up the URL bar there is such a small separation between the end of the URL and the (x) that is is impossible (for me at least) to get the text cursor to the end of the URL to add characters to it
[15:51] <apw> is this known or should i file a bug
[15:57] <jounih> nik90: I've pushed the new designs for the clock app now
[15:58] <jounih> nik90: lp:~jounihelminen/ubuntu-clock-app/designs
[16:13] <stgraber> ogra_: hey, so where do you currently turn the rootfs tar.gz into the zip file? I'm looking at where to hack to get the new .tar.xz stuff on cdimage (alongside .tar.gz and .zip for now)
[16:13] <ogra_> stgraber, thats a script in my home dir on  nusakan
[16:14] <ogra_> stgraber, /home/ogra/utouch-android/do-zip-android
[16:14] <ogra_> it uses all the stuff in that dir
[16:14] <ogra_> (and was supposed to land in livecd-rootfs once the updater-binary is in the archive
[16:14] <ogra_> )
[16:14] <stgraber> ogra_: ah, ok, so probably not where I want to add my stuff. I think I'll change livecd-rootfs/live-build to generate the .tar.xz for the touch images
[16:16] <ogra_> yeah, livecd-roofs already has code for the initrd generation, just add it before that stuff
[16:21] <slangasek> stgraber: http://paste.ubuntu.com/5777557/
[16:22] <stgraber> slangasek: thanks
[16:22] <stgraber> slangasek: ok, so I'm indeed missing some stuff here, so some trigger in init.rc didn't happen. Will look into that after lunch
[16:24] <ogra_> stgraber, slangasek, there are device specific partitions sometimes /efs for example ... might be the n4 uses such stuff
[16:25] <slangasek> ogra_: sorry, context?
[16:25] <ogra_> compare the mount output on both
[16:25] <ogra_> slangasek, stgraber has issues in his loop setup
[16:25] <slangasek> the n4 doesn't have a /efs
[16:25] <ogra_> on the android side ?
[16:26] <ogra_> root@ubuntu-phablet:/# cat /proc/414/mounts|grep efs
[16:26] <ogra_> /dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
[16:27] <ogra_> gnex definitely does
[16:27] <slangasek> yes, N4 does not
[16:27] <stgraber> ogra_: I'm pretty confident the partition list is correct, my initrd mounts all the partitions that I commented in the fstab and all of those are passed (bind-mounted) by LXC. But I think that the fact that they are pre-mounted is preventing some trigger from happening and causes some services to never start
[16:27] <ogra_> k
[16:28] <stgraber> I've been reading through Google's documentation of their init system and now have a reasonable understanding of how that stuff works and where I may be stuck
[16:49] <rsalveti> stgraber: I think there might be some post fs mount events in the init script
[16:49] <rsalveti> which is probably not called in your case
[16:50] <rsalveti> init.rc:on fs
[16:50] <rsalveti> init.rc:on post-fs
[16:50] <rsalveti> init.rc:on post-fs-data
[16:50] <stgraber> rsalveti: everything appears to be called but the late_start class
[16:50] <AskUbuntu> Terminal app on Ubuntu Touch nexus 4 | http://askubuntu.com/q/309770
[16:50] <rsalveti> stgraber: hm, weird
[16:52] <rsalveti> the class is started by some other actions
[16:52] <rsalveti> class_start late_start
[16:52] <stgraber> rsalveti: tracked it down to "on nonencrypted" not being triggered. Adding a one line change to fix that now
[16:52] <stgraber> rsalveti: ok, fixed, that worked
[16:52] <rsalveti> on nonencrypted
[16:52] <rsalveti>     class_start late_start
[16:52] <rsalveti> yeah
[16:53] <rsalveti> cool
[16:53] <icy_> are there news for ubuntu touch and the gs3?
[16:54] <stgraber> rsalveti: testing an updated version of my script now, hopefully that'll fix most of my current issues
[16:54] <rsalveti> stgraber: cool
[17:00] <stgraber> rsalveti: got the shell running!
[17:01] <rsalveti> stgraber: awesome!
[17:01] <rsalveti> ship it
[17:01] <stgraber> ;)
[17:01] <stgraber> just need to add some code to move /home/phablet to writable storage
[17:01] <rsalveti> indeed
[17:01] <rsalveti> stgraber: are you mounting /var/log/ as tmpfs?
[17:01] <stgraber> nope, bind-mount it to writable storage
[17:02] <rsalveti> ok, cool
[17:27] <stgraber> rsalveti, slangasek: updated version, now boots with working wifi and the unity shell: http://paste.ubuntu.com/5777764/
[17:27] <rsalveti> awesome
[17:28] <slangasek> stgraber: what's 'axel'?  Never heard of this :)
[17:30] <stgraber> slangasek: download splitter, that's what I used for cdimage as it tends to be slow otherwise. It opens 10 http streams for that file which usually is good enough to use all the bandwdith I have here
[17:32] <stgraber> rsalveti: hmm, although I see the list of wifi networks I can't seem to connect to them (don't get prompted for the password). Testing phone calls and SMS now, see if that part works.
[17:33] <rsalveti> hm, wonder if the nm package was updated in the archive
[17:33] <rsalveti> can you use nmcli directly?
[17:34] <rsalveti> cyphermox: ^
[17:35] <stgraber> rsalveti: oh, I have an idea, I guess having /etc/NetworkManager/system-connections read-only doesn't help ;)
[17:35] <rsalveti> :-)
[17:50] <ekcex> is anyone working on a ebook reader for touch?
[17:52] <stgraber> rsalveti: calls and sms work, wifi is much happier too though for some reason can't associate but that may be related to my weird wifi setup
[17:52] <rsalveti> stgraber: ok, good progress then
[17:55] <awe> ogra_, flipped looks pretty good on maguro, although only if I manually run ofono
[17:55] <ogra_> hmm, weird
[17:55] <awe> I'm going to the version we landed yesterday with the SIM retry logic
[17:55] <awe> s/to/try/
[17:57] <awe> ogra_, two other issues a) reboot & shutdown aren't reliable, and I have to pull the battery sometimes and b) the phone is running *really* hot ( and there are lots of kernel log messages about it )
[17:57] <awe> ogra_, that said, SMS in/out, phone calls in/out work
[17:57] <awe> as does 3g
[17:57] <awe> ogra_, oh yea...one other issue... the ringtone sounds pretty bad/occasionally distorted
[17:57] <ogra_> we might still miss some interlinks/permissions in /dev
[17:58] <ogra_> yeah, sound still has issues it seems, on the grouper i dont even get the volume control
[17:58] <awe> lots of ALSA/pulse errors in syslog
[17:58] <ogra_> i fear we clash with alsa UCM profiles that we ship in the distro
[17:59] <ogra_> maguro matches one of the pandaboard versions here ...
[18:00] <ogra_> there are still udev vs ueventd issues we need to solve over time
[18:00] <ogra_> but its awesome that it works at all
[18:00] <awe> ogra_, I'm going to take a look at the radio log next, and then will move on to mako
[18:01] <ogra_> i think mako is far more racy (i wish i had one i could use for working to easier weed that out)
[18:01] <awe> also need to try and figure out why things don't work if started by upstart, but I want to see if mako works at all
[18:01] <awe> ogra_, have you asked for one?
[18:01] <awe> maybe even a short-term loaner?
[18:02] <ogra_> well, i asked for "a phone" prior to the sprint ... and got a maguro :)
[18:02] <awe> might not be a bad investment ( ChickenCutlass...nudge, nudge )
[18:02] <awe> ogra_, anyways nice work
[18:02] <ogra_> thanks, and thanks for testing !
[18:03] <awe> np
[18:04] <awe> ogra_, one last question... is there a foolproof method to shutdown?  I'm concerned about mako 'cause I can't pull the battery ( which is what I've had to do several times w/maguro )
[18:04] <ogra_> reboot -fp
[18:04] <ogra_> (force powerdown)
[18:05] <ogra_> also if you need to get into bootloader/recovery ... upstarts reboot understands  that with the -f switch
[18:05] <ogra_> (reboot -f bootloader .... or recovery)
[18:05] <ogra_> after all the broken shutdown/reboot stuff is a bug though ... not yet sure if it is kernel or upstart
[18:06] <ogra_> (could also be that the container keeps it alive)
[18:09] <awe> ogra_, have you looked into the heat issue?  This is the first time I've actually felt the glass getting hot...
[18:09] <ogra_> not yet, no
[18:10] <ogra_> i dont use the radio here, mine doesnt get hot
[18:12] <slangasek> ogra_: sweet, the latest flipped image does work on grouper... of course, it also spits out a lot of kernel detail to the console now, looks like maybe we should re-enable plymouth? ;)
[18:13] <ogra_> oh, wiwo, thanks for testing, i hadnt even started to rsync
[18:13] <slangasek> hmmm, and also we ought to have a 'quiet' argument
[18:13] <ogra_> s/wiwo/wow/
[18:13] <slangasek> because when powering on the screen, it flickers to text console and shows a bunch of text :P
[18:13] <ogra_> oh ?
[18:13] <ogra_> it didnt do that here with yesterdays image
[18:14] <slangasek> it does here
[18:14] <slangasek> console=tty1?
[18:14] <slangasek> that's part of the new stuff, right, and not something I've accidentally done here?
[18:14] <ogra_> i can point the console somewhere else ... grouper has the prob that it needs an actual console to boot with linux
[18:14] <ogra_> right
[18:15] <slangasek> I don't think it's wrong to point the console to tty1, it's just wrong to have things spewing /to/ the console
[18:15] <slangasek> does this kernel support 'quiet'?
[18:15] <ogra_> i havent tried if it actually needs an existing device or if having a value for console other than "none"  is enough
[18:16] <ogra_> dunno, i would expect most kernels do ... it certainly doesnt have apw's loglevel patch though
[18:16] <ogra_> so even with quiet there will still be stuff printed
[18:16] <slangasek> hmm... quite a lot, yes
[18:19] <slangasek> right, enabling plymouth still makes it unhappy
[18:20] <ogra_> slangasek, it wouldnt if you would run consiole_setup in the initrd
[18:20] <ogra_> (that fixes plymouth)
[18:20] <slangasek> well, one thing at a time
[18:21] <ogra_> all plymouth initd hooks/scripts are diverted
[18:21] <ogra_> so you can just set FRAMEBUFFER=Y
[18:21] <ogra_> and update it
[18:21] <ogra_> that makes it run console_setup
[18:21] <ogra_> *initrd
[18:22] <slangasek> apw: ogra_ says there's a loglevel patch missing for the grouper kernel, that would have something to do with the console spew on boot?
[18:22] <nik90> thanks jounih, will look at the designs
[18:26] <slangasek> interesting; console=tty7 works for the kernel, then panics shortly after upstart starts
[18:32]  * ogra_ wonders why his bip instance just died
[18:32] <slangasek> it was frightened by the netsplit?
[18:33] <ogra_> ah, there was one ?
[18:33] <ogra_> i thought it was the mentioning of apw in the channel that scared it somehow :)
[18:34] <ogra_> since it immediately died after your ping :)
[18:35] <awe> ogra_, so reboot -fp doesn't shutdown the system.  ;(
[18:35] <awe> it caused a reboot, which aborted, followed by a second reboot which was successful
[18:35] <ogra_> hmpf
[18:35] <ogra_> try poweroff -f then
[18:36] <awe> are you tracking bugs yet?  If not, I was planning on writing up my results in an email...
[18:36] <davmor2> ogra_: to annoy the living hell out of you, did it work?
[18:36] <slangasek> I'm not sure 'reboot' honors '-p'
[18:36] <ogra_> yeah, it used to years back
[18:36] <slangasek> 'halt -fp', 'shutdown -fp now', 'poweroff -f'
[18:37] <ogra_> you could turn reboot into poweroff with that
[18:37] <slangasek> right, back before it was upstart and Keybuk read the spec :)
[18:37] <ogra_> yeah :)
[18:38] <awe> poweroff -f seems to have done the trick.  Now let's see if it boots on a power on...
[18:38] <cyphermox> rsalveti: no, NM wasn't updated in the archive
[18:39] <rsalveti> cyphermox: yeah, stgraber found the issue
[18:39] <rsalveti>  /etc/ was mounted as ro
[18:40] <awe> ogra_, it won't boot after 'poweroff -f'.  ;(
[18:40] <awe> this is why I'm gonna be super-careful when testing mako
[18:41]  * slangasek blinks
[18:41] <slangasek> why would that stop it from booting?
[18:41] <awe> cause it didn't shutdown/poweroff properly?
[18:41] <ogra_> there is code in the bootloader that also triggers the charger animation for example ...
[18:42] <awe> pulling the battery is required at this point
[18:42] <ogra_> so it can well be that you make it go stuck ...
[18:42] <ogra_> and the n4 is pretty hottid if you have to take out the battery
[18:42] <awe> which is why I'm skittish about mako.  I guess as long as I don't ever reboot it, I'm fine
[18:42] <rsalveti> you can hold down the power button with mako
[18:42] <rsalveti> you cannot remove the battery, but there's a hardware reset
[18:42] <awe> to what?
[18:43] <awe> Didn't we have problems with mako before which required pulling the battery?
[18:43] <rsalveti> right, that's different
[18:43] <awe> I don't think we ever root caused it?
[18:43] <rsalveti> that was the battery running out of battery completely
[18:44] <rsalveti> and not being able to charge enough to boot the system again
[18:44] <rsalveti> was probably a hardware issue
[18:44]  * awe hopes rsalveti is right, but will still try to avoid rebooting mako while flipped
[18:46] <ogra_> teboot should work fine
[18:46] <ogra_> *re
[18:48] <awe> s/rebooting mako/powering off mako via the command line/
[18:48] <ogra_> yeah
[18:49] <ogra_> slangasek, i dont think we should bother much with flddling with plymouth though ... i think there are too many option switched on in out kernel
[18:50] <ogra_> when i asked rtg to enable the HW console he switched on a ton of other tty related bits, i was planning to go through them to get the same behavior as on all other android kernels we have
[18:50] <ogra_> geez
[18:51] <ogra_> *options switched on
[18:52] <slangasek> well, I'm not worried about plymouth per se right now
[18:52] <slangasek> I'm worried about the junk being printed to the console
[18:53] <ogra_> right
[18:54] <ogra_> i could add a quick hack to kill off the backlight (and power it back on at container startup) ....
[18:54] <ogra_> but that leaves you with a black screen for quite some time
[18:54] <ogra_> not sure thats much better
[18:55] <barry> stgraber: i fixed the infloop and now i'm getting a proper signature error.  try to fix the sig on the blacklist file and let's see if it works
[18:56] <JCBir> hello friend can any one tell is ubuntu is available for micromax a116
[18:57] <sergiusens> JCBir: !devices
[18:57] <sergiusens> !devices
[18:59] <JCBir> it only says for All Nexus devices i am form india and using micromax handset a116
[18:59] <JCBir> canvas HD A116
[18:59] <JCBir> its not for any other android
[19:00] <stgraber> barry: try now
[19:02] <barry> stgraber: sweet! works perfectly
[19:02] <barry> stgraber: it's a little slow getting the xz files.  maybe that's expected.  i need to plumb in some feedback in verbose mode
[19:05] <awe> ogra_, now I'm getting an insufficient permissions error when trying to adb into the phone.  Any ideas?  Another race?
[19:06] <ogra_> no, thats on the PC side
[19:06] <ogra_> adb kill-server; sudo adb start-server
[19:06] <ogra_> i heard reconnecting the cable helps too
[19:07] <awe> ogra_, thanks...fixed
[19:20] <Michael0285-3453> Can anybody help me please? i'm trying to install ubuntu phone on a galaxy nexus, but get stuck after phablet-flash -b
[19:20] <CPCookieMan> Quick question, if I have Android booted, but Ubuntu Phone deployed, how do I get it to boot Ubuntu Phone?
[19:21] <CPCookieMan> I'm trying to port to the Galaxy Nexus LTE (toro).
[19:23] <CPCookieMan> Is there something I should be putting into init.rc?
[19:26] <pmcgowan> Michael0285-3453, whats the problem?
[19:27] <Michael0285-3453> Device detected as maguro Download set to http://cdimage.ubuntu.com/ubuntu-touch-preview//daily-preinstalled/current Starting new HTTP connection (1): cdimage.ubuntu.com Starting new HTTP connection (1): cdimage.ubuntu.com Download directory set to /home/michael/Hentede filer/phablet-flash/saucy-16 Retrieving files The device needs to be unlocked for the following to work Flashing system to /home/michael/Hentede filer
[19:28] <CPCookieMan> Well, is the device unlocked?
[19:28] <pmcgowan> that all looks normal
[19:28] <CPCookieMan> When you boot, under the Google logo, do you see a lock?
[19:28] <Michael0285-3453> yes
[19:29] <CPCookieMan> Guys, I'm so close to Ubuntu Touch, I just need to know the command that actually starts it instead of Android.
[19:29] <pmcgowan> Michael0285-3453, you need to follow the instructions at https://wiki.ubuntu.com/Touch/Install exactly
[19:29] <ogra_> it replaces android ... if your install worked it would boot into ubuntu touch
[19:30] <ogra_> so something wasnt installed properly
[19:30] <Michael0285-3453> i really think i did
[19:30] <CPCookieMan> ogra_ I'm porting, I needed to leave full android in tact so that the system would even boot.
[19:30] <Michael0285-3453> it should be unlocked and i also tried factory reset/data wipe
[19:30] <pmcgowan> Michael0285-3453, so after you got that message did the phablet-flash exit?
[19:30] <ogra_> CPCookieMan, well,  there is no way to run ubuntu touch under android
[19:31] <CPCookieMan> Ok, but could someone send me their init.rc that boots Ubuntu Touch?
[19:31] <Michael0285-3453> the device just goes into fastboot mode
[19:31] <Michael0285-3453> and i get that error
[19:32] <CPCookieMan> Parts of my radio are APKs, that's why I've left Android intact.
[19:33] <ogra_> that wont work
[19:34] <CPCookieMan> Why not? I'm pretty fluent in Linux, I'd think it should. I am just missing the code that makes it start Ubuntu Touch.
[19:34] <pmcgowan> Michael0285-3453, the device needs to be booted into android or ubuntu for phablet-flash to work
[19:35] <pmcgowan> Michael0285-3453, fromt he bootloader can you get it to still boot into android
[19:35] <CPCookieMan> Fine guys, I'll figure it out myself...
[19:36] <Michael0285-3453> pmcgowan thank you very much for helping me. Yes i can boot into android
[19:36] <Michael0285-3453> but the device simply restart itself
[19:37] <pmcgowan> when does it restart, after it boots?
[19:37] <ogra_> CPCookieMan, the code is in the repo tree that you used to build your android image
[19:37] <ogra_> (on phablet.ubuntu.com)
[19:37] <Michael0285-3453> no during phablet-flash -b
[19:38] <Michael0285-3453> it just seems that i'm so close
[19:38] <pmcgowan> do you see it copy to the sdcard on the device?
[19:39] <Michael0285-3453> no, i don't think so
[19:39] <Michael0285-3453> It all goes very fast
[19:40] <CPCookieMan> You can output to a log if you'd like to see it slower
[19:40] <pmcgowan> you have the output in your terminal? you can put it in a pastebin?
[19:41] <Michael0285-3453> this i what follow phablet -b
[19:41] <Michael0285-3453> Device detected as maguro Download set to http://cdimage.ubuntu.com/ubuntu-touch-preview//daily-preinstalled/current Starting new HTTP connection (1): cdimage.ubuntu.com Starting new HTTP connection (1): cdimage.ubuntu.com Download directory set to /home/michael/Hentede filer/phablet-flash/saucy-16 Retrieving files The device needs to be unlocked for the following to work Flashing system to /home/michael/Hentede filer
[19:42] <slangasek> ogra_: yeah, I want us to fix the root issue here and get the text off the console :)
[19:42] <slangasek> ogra_: we should at least issue a 'clear' before starting the container anyway, to clean up any residual console output; we already do this for lightdm on the desktop
[19:42] <ogra_> slangasek, right, that measn a bit of time to invest into disabling option by option and test the kernel
[19:42] <ogra_> *means
[19:43] <slangasek> well, are you sure this isn't just a matter of apw's loglevel sauce patch?
[19:43] <slangasek> that seems like what 'quiet' is supposed to do, and that's an Ubuntu patch
[19:43] <ogra_> no, we dont have any console output in unflipped
[19:44] <ogra_> but upstart wants a hardware console to talk to ... and tegra doesnt offer one in the android defconfig
[19:45] <ogra_> so i asked rtg_ to enable that ... but there were like 20 options enabled additionally in that patch
[19:45] <ogra_> i would also like to get rid of /dev/tty[0-9] again ... we dont need them at all
[19:45] <slangasek> sure; my question is why passing 'quiet' at boot doesn't suppress the kernel output, because that's what 'quiet' is supposed to do - which depends on an Ubuntu patch
[19:46] <ogra_> wellm quiet quietens to info level ... the ubuntu patch makes that critical level
[19:46] <ogra_> our patch just quietens a bit more
[19:46] <rtg_> slangasek, 'cause its not applied to the Nexus kernels. we have almost none of the distro SAUCE patches backported to these kernels.
[19:46] <slangasek> ok
[19:46] <ogra_> but that will not quieten dircet printfs ... of which the android drivers are full
[19:47] <slangasek> so I think we want that patch brought in
[19:47] <ogra_> (since there is no console usually)
[19:47] <slangasek> ogra_: ugh, that's horrible
[19:47] <ogra_> yes, it is
[19:47] <ogra_> android ...
[19:47] <slangasek> I wonder if vt.handoff=7 would do anything on the N7
[19:47] <slangasek> or just explode
[19:48] <rtg_> slangasek, start a bug against linux-{maguro,mako,manta,grouper} so we don't forget.
[19:48] <ogra_> slangasek, try it :) its just an abootimg away :)
[19:48] <pmcgowan> Michael0285-3453, sorry then what after flashing files? that will take some time
[19:48] <slangasek> trying now
[19:50] <CPCookieMan> So they're building with saucy now?
[19:50] <webcommander> Why cant i download and install ubuntu touch on my nexus 4
[19:50] <slangasek> ogra_: do you want to pre-emptively add 'quiet' to your boot options?  Since it ought to be there anyway
[19:50] <CPCookieMan> webcommander, You'll have to give us more than that.
[19:51] <ogra_> slangasek, we can, but thats moot once we have the console removed again
[19:52] <ogra_> as is the whole quiet patching imho ... once i'm done with manta and have it booting i'll go over the kernel options and make it behave right again
[19:52] <slangasek> ogra_: wait, where do you get removing the console?
[19:52] <slangasek> it's just been added
[19:52] <slangasek> do you mean you want upstart changed to work without a console?
[19:53] <ogra_> slangasek, no, i dont want the framebuffer being used
[19:53] <ogra_> as it is on all other android based kernels
[19:53] <slangasek> ok, so where do we point the console?
[19:53] <slangasek> I thought we had no other options on grouper
[19:53] <ogra_> i'm surprised that surfaceflinger works at all to be honest
[19:53] <slangasek> rtg_, ogra_: bug #1192309
[19:54] <ogra_> we dont want fbcon ...
[19:54] <ogra_> and we want to get rid of everything thats not needed to make upstart happy, what we enabled was way to much
[19:54] <slangasek> hmm.
[19:54] <ogra_> i just didnt have the time yet to go over that
[19:54] <slangasek> disabling fbcon makes sense, but then, where does /dev/console go?
[19:55] <ogra_> but imho the grouper kernel needs to behave exactly the same as all other android kernels
[19:55] <slangasek> that's what upstart breaks on - /dev/console spitting errors
[19:55] <slangasek> the other android kernels have a console somewhere other than the main tty
[19:55] <ogra_> well, it doesnt on maguro, mako, manta
[19:55] <Michael0285-3453> pmcgowan sorry, i'm not sure what that means. I dont't think it writes any files to the device. The android system is still intact. Could it be that the device is not rooted?
[19:55] <CPCookieMan> cd ..
[19:55] <ogra_> nothing has fbcon
[19:55] <CPCookieMan> doh
[19:55] <slangasek> I'm not talking about fbcon
[19:55] <slangasek> I'm talking about */dev/console*
[19:55] <ogra_> and i'm pretty sure we can get grouper to do that too
[19:56] <slangasek> mako boots with console=ttyHSL0,115200,n8.  What's the equivalent for grouper?
[19:56] <pmcgowan> Michael0285-3453, it must be, if you go back into android double chekc the device setup instructions
[19:56] <ogra_>  /dev/console usually points to some virtual debugging device
[19:56] <slangasek> so why did the grouper kernel get changed to enable fbcon, instead of doing this?
[19:56] <ogra_> usually /dev/ttyFIQ0
[19:57] <ogra_> (had to look it up)
[19:57] <ogra_> because it didnt work there and upstart fell over
[19:57] <ogra_> but what we enabled was to much
[19:57] <pmcgowan> Michael0285-3453, it needs to be rooted with usb debug turned on for adb to work
[19:57] <ogra_> we dont need 150 ttys and we dont need fbcon
[19:58] <ogra_> the point is that someone needs to go through thse options, disable one by one and find when upstart falls over to find the one option we actually need out of the 20 that were enabled
[19:58] <pmcgowan> Michael0285-3453, if I understand you right, it says flashing the files then the command exits ? otherwise it should copy the files to the device and that takes time
[19:59] <Michael0285-3453> pmcgowan usb debug is turned on but i'm not sure if it is rooted
[19:59] <slangasek> ogra_: um, the option that made upstart not fall over *was* fbcon, because that's what gives upstart a real device to write to that doesn't error out when used
[20:00] <ogra_> i doubt that
[20:00] <slangasek> ogra_: if the conclusion is "we shouldn't use fbcon", then disabling the enabled options one-by-one doesn't help
[20:00] <ogra_> i think it was CONFIG_HW_CONSOLE
[20:00] <ogra_> but i didnt have time to test that tehory yet
[20:01] <ogra_> in any case what was enabled was way to much and i know that i could boot desktop images without any console output in the past
[20:01] <ogra_> so it must be possible on touch as well
[20:05] <ogra_> slangasek, the nit that worries me is that we behave different to all other kernels we have and that can cause probs later, so i want to go back as fasr as i can again
[20:05] <ogra_> and keep the change actually as minimal as possible
[20:05] <slangasek> sure
[20:11] <esigolo> the things are getting hot In São Paulo again
[20:18] <webcommmander> every time i run the phablet-flash -b it runs for a bit and then says 404
[20:19] <esigolo> webcommmander: using proxy ?
[20:19] <webcommmander> no
[20:20] <webcommmander> it identifies my phone type and then it says 404
[20:23] <esigolo> is possible to say wich address to use but i can't remember the command i'm searching
[20:26] <esigolo> phablet-flash -p cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
[20:27] <esigolo> just to see if it works
[20:28] <webcommmander> ok trying it now
[20:30] <webcommmander> it says it does not exist
[20:30] <webcommmander> the directory does not exist
[20:31] <pmcgowan> esigolo, thats for local paths, need to use -u
[20:31] <esigolo> pmcgowan: thanks my mistake
[20:31] <webcommmander> still does not work
[20:34] <pmcgowan> webcommmander, do phablet-flash -u http://thepath
[20:34] <pmcgowan> do you still get 404
[20:35] <webcommmander> ye 404
[20:36] <mterry> What are the changes (or source bzr branch) in indicator-appmenu in ppa:phablet-team/ppa?  I can't find any pointer in the changelog
[20:36] <mterry> sergiusens, ^ ?
[20:39] <pmcgowan> webcommmander, you are doing this on the same system you are talking to me on?
[20:39] <webcommmander> ye
[20:39] <webcommmander> yes
[20:41] <pmcgowan> webcommmander, you got me, phablet-tools version is 0.14daily13.06.12.1-0ubuntu1
[20:41] <pmcgowan> ?
[20:41] <sergiusens> mterry: I think that's a Saviq thing
[20:42] <mterry> sergiusens, ok, you had uploaded the last two, so I jumped to you  :)
[20:42] <webcommmander> how do i check the version
[20:42] <CPCookieMan> Have they updated it to use the Saucy files instead of the Raring files? That messed up a few of my scripts.
[20:42] <sergiusens> mterry: let me check then, but it might of been a copy
[20:42] <mterry> Saviq, if you're still around, what are the changes (or source bzr branch) in indicator-appmenu in ppa:phablet-team/ppa?  I can't find any pointer in the changelog
[20:43] <Saviq> mterry, dunno, don't even know if there are any
[20:43] <Saviq> renato_, any pointers on that ^?
[20:43] <webcommmander> i am updating the phablet-tools
[20:43] <mterry> Saviq, it's got a lot of changes, looking at a diff with saucy.  A lot of hud stuff, etc
[20:44] <sergiusens> mterry: if we need to start using the one from archives we can delete from the ppa
[20:44] <pmcgowan> webcommmander, to check do apt-cache policy phablet-tools
[20:45] <mterry> sergiusens, well I didn't want to do that without understanding the differences / why we have the phablet one
[20:45] <mterry> sergiusens, but it's true that the one in the phablet ppa is uninstallable on saucy (links to libbamf3-0 which doesn't exist)
[20:46] <mterry> Trying to rebuild it, I got a ftbfs
[20:46] <Saviq> mterry, ah, if it's HUD changes, then tedg, can you help?
[20:47] <tedg> mterry, Not sure which version that is, but I think it's old.
[20:47] <mterry> tedg, 13.01.0phablet2 from 5/2?
[20:47] <tedg> mterry, Yup, super old :-)
[20:48] <mterry> tedg, OK, so saucy should be used in preference? I'll just delete from PPA then
[20:48] <tedg> mterry, Sure.
[20:48] <renato_> Saviq, sorry but I did not have any clue about that
[20:48] <tedg> mterry, I'd just say with everything archive should be preferred :-)
[20:49] <mterry> tedg, yeah...  but unity build scripts still use the ppa...
[20:49] <sergiusens> mterry: I can't find the quantal version we used, which probably means I just imported it from way back
[20:49] <tedg> mterry, Heh, can you delete the unity build scripts and tell Saviq to use debian/rules?  ;-)
[20:50] <Saviq> tedg, can you tell didrocks to land unity in distro ;P
[20:50] <sergiusens> Saviq: it already lands ;-)
[20:50] <sergiusens> unity 77
[20:50] <sergiusens> 7
[20:50] <Saviq> sergiusens, good, then we can make sure we drop the build scripts tomorrow :P
[20:50] <Saviq> tedg, ^
[20:51] <tedg> didrocks, Land Unity RIGHT NOW!!!  ;-)
[20:51] <sergiusens> Saviq: is that your blocker?
[20:51] <Saviq> sergiusens, that, too
[20:51] <Saviq> sergiusens, we can't land smart scopes support without that
[20:52] <pmcgowan> tedg, I think its sudo land unity
[20:52] <Saviq> sergiusens, now we're only waiting for notifications, which will be done tomorrow
[20:52] <tedg> pmcgowan, Ah, yes!
[20:52] <Saviq> sergiusens, so yes, tomorrow we cut the cord to ppa:phablet-team for unity8 builds
[20:52] <tedg> sudo -u didrocks land unity
[21:52] <AskUbuntu> Flashing ubuntu on galaxy nexus from Windows pc | http://askubuntu.com/q/309905
[22:26] <stgraber> ogra_, rsalveti, slangasek: alright, so there's nothing wrong with my changes and the wifi. It's just that the wifi driver or our wpa supplicant is unable to associate with my wifi. Running another AP without authentication on 5Ghz worked
[22:27] <stgraber> so http://paste.ubuntu.com/5778573/ works perfectly fine including wifi (at least as well as without my changes)
[22:36] <mhall119> hmmmm, I keep hitting refresh on the saucy-preinstalled.changelog, but it still stays at saucy-16 :(
[22:56] <awe> stgraber, this could be another casualty of the driver-specific wpa_suppl code that Android ships, but we lack...
[22:56] <awe> stgraber, we found 5g wi-fi performance to be very poor in general on the touch devices
[23:00] <stgraber> awe: well, what's surprising here is that it fails to associate on my 2.4Ghz network but works fine on a 5Ghz one, logs from the client/kernel and access point don't say much. The AP says the client never responded and the client says the AP kicked it out, hard to know what happened exactly...
[23:00] <stgraber> running Android's wpa_supplicant seems to be more reliable at associating, but once associated dhcp still won't work and it'll drop the connection after a few minutes
[23:01] <stgraber> I've got a dozen other mobile devices on that AP and they all work fine, so it's a bit weird but I'll wait for some more people to try the container-flipped nexus4, see if we can find patterns
[23:02] <awe> does it work OK with the non-flipped nexus4?
[23:02] <stgraber> never tried ;)
[23:02] <awe> baseline dude...
[23:02] <awe> ;D
[23:02] <stgraber> that phone must have run Android for a good minute, just enough to start adb and wipe it
[23:02] <awe> haha
[23:04] <awe> stgraber, it's not necessarily the delta between our wpa_supplicant and Android's, I believe it's the lack of the Qualcom wpa_supplicant nl80211 driver library...
[23:05] <awe> and the similar BCM library on maguro
[23:05] <awe> anyways, I'm about to flash my nx4 with the flipped image, so I'll let you know how well it works out for me
[23:06] <stgraber> awe: ok, if you want to get the exact same thing I have, use http://paste.ubuntu.com/5778573/
[23:06] <stgraber> awe: that gives you flipped + read-only / with loop-mount
[23:09] <awe> stgraber, at this point I'm just trying to get ogra_ feedback on his base flipped container images.  We need to ensure RILD and all of it's uglieness still works correctly.  So far it looks good, although start-up is still a bit racy
[23:10] <awe> also I managed to crash maguro once today, but in general I haven't see any badness coming from RILD ( at least on maguro ), which is good.
[23:50] <mhall119> does anybody know the reason we don't support CDMA but CyanogenMod does?  It it technical, legal, political?
[23:51] <mhall119> I guess political and legal are kinda the same
[23:58] <vadi> Has anyone had luck downgrading back to qt4 APIs by chance?