[00:33] <iBelieve> Is there anyone here from the Calendar app team? I've got a question about a feature in it.
[00:59] <annerajb>  iBelieve there is another irc channel for apps dont remmeber which one.
[01:02] <iBelieve> annerajb, thanks, I asked there too (#ubuntu-app-devel), but tried here as well in case any of them hang out here
[01:23] <annerajb> yay progress the bootstrap appears to be working fine. now i just have to get the rootfs installed (assuming it fits inside my tiny space)
[01:32] <nhaines> annerajb: congratulations.  :)
[01:33] <annerajb> nhaines, fun was short lived the bootstrap apparently dosnt know how to mount the rootfs
[01:33] <annerajb> it may have to do with what it says on the wiki The "scripts/touch" file in the ramdisk needs to figure out the data partititon's device file name (like /dev/foo). It might fail for your device and cause the boot process to fail. I've hard-coded the device path for the Desire Z for now, maybe we can set this in the device config at build time later.
[02:12] <Oroku_Saki> is there a wiki for the partition layout explanation???
[02:12] <Oroku_Saki> where things are supposed to be
[02:12] <Oroku_Saki> =)
[02:14] <Oroku_Saki> when I run unity8, I get this... Cant find EGLConfig, returning null config
[02:14] <Oroku_Saki> I have egl.cfg....
[02:16] <annerajb> Oroku_Saki, Not all device node permissions may be covered by this. In particular if you have no graphics coming up and get EGL related errors in logcat, make sure you add a line allowing non-root rw access to the GPU device node. For OMAP/SGX devices the line is something like
[02:16] <annerajb> that's from the wiki
[02:17] <Oroku_Saki> for the udev 70 rules?
[02:18] <annerajb> it looks like it.
[02:18] <Oroku_Saki> MODE="0666" that is what I have
[02:18] <Oroku_Saki> I did it for all lines in my udev.tenderloin.rc from cm
[02:18] <annerajb> Oroku_Saki, did you check that this KERNEL=="pvrsrvkm" matches the kernel module your device uses for gpu??
[02:19] <annerajb> hmmm
[02:19] <Oroku_Saki> well, the touchpad is an adreno, but it doesn't use that module like say the droid 4 maserati.. the touchpad adreno has kgsl and etc all built into the kernel
[02:19] <Oroku_Saki> even tried.  "export QT_QPA_EGLFS_DEPTH=16"
[02:20] <annerajb> can you post a logcat or and dmseg?
[02:20] <annerajb> dmesg*
[02:20] <Oroku_Saki> the entire dmesg?
[02:21] <Oroku_Saki> or output of when I run unity
[02:21] <annerajb> hmm post the entire thing pastebin wont mind lol
[02:22] <Oroku_Saki> just a quick info when I run unity as root.. I get this "QXcbConnection: Could not connect to display"
[02:22] <Oroku_Saki> but when I run as phablet I get the EGL error
[02:23] <annerajb> how are you starting unity?
[02:23] <Oroku_Saki> dmesg.. http://pastebin.com/gFU9jd9f
[02:23] <Oroku_Saki> just running "unity8" =)
[02:25] <Oroku_Saki> phablet@ubuntu-phablet:~$ initctl start unity8 initctl: Unable to connect to Upstart: Empty address ''
[02:27] <annerajb> is the upstart daemon running?
[02:29] <Oroku_Saki> yes.. ? upstart-file-bridge --daemon
[02:29] <annerajb> well i am out of ideas didnt notice anything on the dmesg
[02:30] <annerajb> thought based on a different message under root i guess it could be some sort of permission that phablet dosnt have
[02:30] <Oroku_Saki> I see a constant powerd complaint abut my backlight in my syslog...
[02:30] <Oroku_Saki> other then that.. me too
[02:30] <Oroku_Saki> out of ideas
[02:31] <Oroku_Saki> I cannot android-chroot
[02:31] <Oroku_Saki> 02:12 ?        00:00:00 lxc-wait -n android -s RUNNING
[02:32] <Oroku_Saki> "/proc/-1/root/: No such file or directory"
[02:32] <Oroku_Saki> things are strange now.. I need to wait for a new porting guide or something
[02:33] <Oroku_Saki> is my android-ramdisk.. is that supposed to be mounted somewhere??
[02:34] <Oroku_Saki> I cant mount loop my system.img, so I decided the mntroot in my touchscript should be my actual system partition
[02:34] <Oroku_Saki> lxc boot says success
[02:35] <Oroku_Saki> actually.. "/var/log/upstart# cat lxc-android-boot.log mount: can't find /data in /etc/fstab or /etc/mtab"
[02:37] <Oroku_Saki> "/home/phablet/.cache "doesn't seem to have any logs about unity, or anything really
[02:38] <Oroku_Saki> or upstart
[03:17] <Oroku_Saki> anyone know a way to test EGL\GL?
[03:18] <Oroku_Saki> http://pastebin.com/ec7U4QKt
[03:19] <Oroku_Saki> initctl start ubuntu-touch-session USER=phablet
[03:20] <Oroku_Saki> I do not seem to be missing libOmex libs or libGL* or etc
[03:40] <Oroku_Saki> phablet@ubuntu-phablet:/usr/lib/arm-linux-gnueabihf/qt5/bin$ ./qmlscene __pthread_gettid -2 Cant find EGLConfig, returning null config Aborted
[03:54] <Oroku_Saki> phablet@ubuntu-phablet:/$ sudo qmlscene -platform ubuntu /usr/lib/arm-linux-gnueabihf/qt5/qml/QtMultimedia/Video.qml __pthread_gettid -2
[03:55] <Oroku_Saki> that doesn't crash... screen refreshes.. when the command stops my screen turns to a crazy blue, and stays blue until I rerun the command
[03:56] <Oroku_Saki> actually, blue comes on when this comes up in console: Cant find EGLConfig, returning null config
[03:56] <Oroku_Saki> =)
[06:18] <Wufu> what is the sudo password on ubuntu touch after install?
[06:18] <RAOF> ubuntu, IIRC
[06:21] <Wufu> thanks
[06:22] <Wufu> can u update ubuntu touch with "apt-get upgrade" ?
[06:26] <RAOF> Yes, as long as you're not using the image-based updates system, I think (in that case, the system partition is read-only)
[06:32] <Wufu> every time i sudo it says the password is not "ubuntu"
[06:33] <Nimble> Wufu, the password is phablet.
[06:34] <Wufu> thansk that helped :)
[06:35] <Nimble> np
[06:45] <dholbach> good morning
[07:01] <Oroku_Saki> any reason why I can't logcat?
[07:02] <Oroku_Saki> I see a patch about alog instead of log and smybolic link
[07:33] <Wufu> any one have problem with calling a phone nr that begins with + or * ?
[08:34] <popey> Morning.
[08:35] <annerajb> morning
[08:38] <annerajb> anybody have instructions for repacking the initramfs? Need to modify scripts/touch for my device
[08:39] <ogra_> annerajb, why would you do that ?
[08:39] <annerajb> the scripts/touch cannot find my data partition since i am on a btl/mtd device and it cannot read the partition labels
[08:40] <ogra_> ah, so you end up in an adb shell then ?
[08:40] <annerajb> yup with a message saying that it coudnt find a data partition here is a post on the mailing list about another device that has my same issue
[08:40] <annerajb> https://lists.launchpad.net/ubuntu-phone/msg03502.html
[08:41] <ogra_> pk
[08:41] <ogra_> *ok even
[08:41] <ogra_> annerajb, the abootimg package ships a scritp for this
[08:42] <ogra_> abootimg-unpack-initrd and abootimg-pack-initrd
[08:42] <lilstevie> is there a way to find out why upowerd would be calling for an emergency shutdown? I've looked through logs and with tried to see if there was anything with powerd-cli listen and am still no better off
[08:43] <ogra_> i'll try to get to bug 1199084 this week so you can specify them on cmdline in the future
[08:43] <annerajb> ogra_, thanks :D
[08:44] <JamesTait> Good morning all, happy Youth Day! :-D
[08:45] <annerajb> ogra_, how do you use that command every -h variation i pass to it says ramdisk dosnt exist
[08:45] <ogra_> annerajb, abootimg-unpack-initrd /path/to/initrd.img
[08:46] <ogra_> it will unpack it in your current dir (so better run it in a scratch or tmp directory you crate first)
[08:47] <ogra_> if you run abootimg-pack-initrd in the same place it will pack the contents to an initrd.img again
[08:58] <annerajb> ogra_, abootimg-pack-initrd dosnt work. zcat complains about the img not being in grep format. i am passing it as argument the boot.img
[08:59] <ogra_> abootimg-pack-initrd doe not take any arguments
[09:00] <ogra_> you just need to run it in the same place you ran the unpack
[09:00] <ogra_> it will then create an initrd.img ...
[09:01] <annerajb> ogra_, well i cant run the unpack.
[09:01] <ogra_> ah, you said pack above :)
[09:01] <annerajb> yeah my bad
[09:02] <annerajb> gzip: initrd.img: not in gzip format
[09:02] <annerajb> cpio: premature end of archive
[09:02] <annerajb>  that's what it says
[09:02] <ogra_> so you have the bare initr.img file (or androids ramdisk.img) ?
[09:02] <ogra_> *initrd.img
[09:02] <annerajb> ogra_, i have boot.img renamed in the same directory to initrd.img
[09:02] <ogra_> no
[09:02] <ogra_> boot.img is not an initrd.img :)
[09:03] <ogra_> boot.img usually contaisne bootloader setup kernel and initrd together
[09:03] <annerajb> is that the file i should be modifying? the one that contains the scripts/touch file?
[09:03] <ogra_> initrd.img containse the scripts/touch file
[09:03] <ogra_> boot.img is a container that carries more than just an initrd
[09:03] <ogra_> abootimg -x boot.img
[09:03] <ogra_> try that
[09:04] <ogra_> if your vendor was sane enough to use an android standard boot.img it should work
[09:04] <annerajb> ../boot.img: not a valid Android Boot Image.
[09:04] <ogra_> (and you should end up with three files ... bootimg.cfg, initrd.img and zImage)
[09:05] <ogra_> ah, sad
[09:05] <ogra_> so the other way is to edit it in your build tree
[09:05] <ogra_> and do a rebuild afterwards
[09:05] <ogra_> the ramdisk.img
[09:06] <annerajb> so i edit the script inside ubuntu-root/touch/scripts
[09:06] <annerajb> and then run which target to repack it?
[09:06] <ogra_> you unpack the ramdisk.img ... edit the script in the unpackaged dir and then use the repack command to repack the ramdisk.img
[09:07] <annerajb> ok and then i make a boot.img with that and the cfg and the kernel?
[09:08] <ogra_> no, then you do a rebuild of your zip
[09:09] <ogra_> your device uses a special non standard way of compiling the boot.img ... you need to use the way the build uses
[09:09] <ogra_> (typically samsung does that)
[09:14] <annerajb> so i run brunch epicmtd as normal?
[09:15] <annerajb> wont that override the ramdisk.img?
[09:15] <ogra_> not if you didnt clean it
[09:16] <ogra_> if you did, just run a full build, then edit and run it again (it should only pick up the changes)
[09:19] <popey> ogra_: (been away on vacation for a week so catching up) - should I be testing the ubuntu-system images?
[09:19] <ogra_> popey, as you feel like ... fo rthe normal images we now fullt rely on the dashboard
[09:19] <popey> when are we switching?
[09:19] <popey> (to the image based ones)
[09:20] <ogra_> no idea, we are still missing Mir/lightdm and a full switch to click
[09:20] <popey> ah
[09:20] <ogra_> at least the latter is needed
[09:20] <ogra_> else you cant install/remove stuff
[09:20] <popey> ofc
[09:21] <ogra_> not sure we'll wait for Mir though
[09:21] <popey> gosh, phablet-flash got a lot more chatty ☻
[09:21]  * popey gets tea while it does the work
[09:21] <ogra_> it also got caoomands now
[09:21] <ogra_> *commands
[09:22] <ogra_> plain phablet-flash wont do anything anymore
[09:25] <popey> ogra_: do we have docs somewhere ready for new world order phablet-flash?
[09:26] <ogra_> i dont think so
[09:26] <ogra_> sergiusens wrote a mail i think, but the wikis are outdated
[09:27] <popey> k
[09:31] <dholbach> ogra_, popey: there's not too much on the wiki which needs updating
[09:32] <dholbach> I'll look into it
[09:32] <annerajb> ogra_, that didnt work the brunch epicmtd overwrote my ubuntu-root/scripts/touch
[09:32] <dholbach> https://lists.launchpad.net/ubuntu-phone/msg03687.html is sergiusens' mail
[09:32] <annerajb> ogra_, from what i read a blank initramfs get's downloaded every build
[09:32] <annerajb> and it uses that as a template to make the device specific one
[09:33] <ogra_> annerajb, you should have created a ramdisk.img ... not sure what "your ubuntu-root/scripts/touch" is supposed to be, but it will definitely not be used by anything
[09:33] <popey> dholbach: thanks!
[09:34] <annerajb> i did create a ramdisk.img it was rewrote
[09:35] <annerajb> ogra_, ubuntu-root is a folder on out/target/product/epicmtd/ which contains the initramfs after extraction (the one that get's downloaded online)
[09:35] <annerajb> The android_build repository on phablet.ubuntu.com has all the required changes to create the android zip file. It downloads files for a generic initramfs and puts them in "out/target/product/devicename/ubuntu-root". I think that changes to those files are not automatically put back into the ramdisk
[09:36] <annerajb> that's from the wiki
[09:36] <ogra_> annerajb, right, so you want that initramfs file, not some script
[09:36] <annerajb> oh ok so i want modified the downloaded initramfs
[09:36] <dholbach> ogra_, popey: done
[09:36] <annerajb> and since it's already downloaded is gonna use the one i have?
[09:37] <ogra_> annerajb, right
[09:38]  * ogra_ is afk for ~1h
[10:10] <diwic> ogra_, I'm looking at the audio hal, it tries to /dev/socket/qmux_bluetooth which - when running from outside the container with libhybris - fails with EACCESS
[10:11] <diwic> ogra_, it looks like /dev/socket/qmux_(audio|gps|radio) are set up for groups audio, gps, and radio, but not the bluetooth one
[10:11] <diwic> ogra_, since you did the flipped container stuff I figured you might be the best person to ask
[10:11] <ogra_> bah, sigh, that means we need more android groups in our rootfs
[10:12] <annerajb> ogra_, btw that didnt work ogra it redownloads it every time. even without cleaning any files.
[10:13] <ogra_> so look at the build scripts and disable the download :)
[10:13] <annerajb> yeah already did
[10:14] <diwic> ogra_, so are you the right person to make sure we get a bluetooth group in the android rootfs, and set that group to allow /dev/socket/qmux_bluetooth access? :-)
[10:15] <diwic> the phablet user seems be part of the bluetooth group so outside the container probably things will be working
[10:15] <ogra_> diwic, well, most likely, yes ... what will access that socket ? the prob is not adding the user or making phablet a group member
[10:15] <ogra_> the prob are daemons that dont run as the needed user
[10:16] <diwic> ogra_, well, when opening the audio HAL it tries to access it - most likely that will be the PulseAudio process
[10:16] <ogra_> are we sure everything that accesses the socket directly from the ubuntu side will have the right permissions ?
[10:17] <diwic> ogra_, pulseaudio runs as the phablet user right now.
[10:18] <diwic> ogra_, bluetoothd runs as root, we can guess that might also use the socket perhaps
[10:19] <ogra_> well, root should be fine
[10:19] <diwic> ogra_, and unless some security person thinks pulseaudio should run as something else, I'm happy with having it running as the phablet user
[10:19] <ogra_> yeah, phablet seems ok
[10:19] <diwic> ogra_, other than that I'm not sure who would access the socket
[10:19] <ogra_> i wasnt so sure about direct access ... does pulse actually access the socket itself ?
[10:20] <diwic> ogra_, pulseaudio opens the audio HAL. The audio HAL accesses the socket.
[10:20]  * ogra_ is a bit surprised that we shove sound through a socket on teh ubuntu side instead of just using the sound devices directly 
[10:20] <ogra_> ah, ok, so there is another layer
[10:21] <diwic> ogra_, I don't think we shove sound through it. It's just the proprietary blobs doing stupid things.
[10:21] <ogra_> ok
[10:21] <ogra_> heh
[10:21] <ogra_> as usual
[10:31] <davmor2> morning all by the way
[10:34] <ogra_> diwic, for a test, can you edit /etc/init/lxc-android-config.conf and add a "chmod a+rw /dev/socket/*" right above the lxc-wait line, it should start working then
[10:37] <ikillcypher> hello any developers here ?
[10:37] <annerajb> ogra_,  after modifying it so it dosnt download it and repacking the ramdisk.img when i run brunch it still overwrites it
[10:38] <timp> ikillcypher: I guess so, but even more in #ubuntu-app-devel
[10:38] <ikillcypher> well it is about ubuntu-touch
[10:38] <ikillcypher> so what with ubuntu-app-devel ?
[10:38] <ogra_> annerajb, hmm, are you sure you look at the right ramdisk ?
[10:38] <timp> ikillcypher: #ubuntu-app-devel is more specific, but you can try here also
[10:38] <ogra_> (might probably be called ubuntu-ramdisk.img)
[10:39] <ikillcypher> ogra__ are you a developer ?
[10:39] <annerajb> ramdisk.img in out/target/product/epicmtd/
[10:39] <ogra_> ikillcypher, yes
[10:39] <ikillcypher> it seems like porting ubuntu-touch did not work I sent an email but no responds
[10:39] <ogra_> annerajb, is that the only file with ramdisk in its name in that dir ?
[10:39] <ikillcypher> I have already everything done with the changes patched but when I do brunch I get kernel error
[10:40] <annerajb> ogra_, there is also android-ramdisk.img
[10:42] <annerajb> but android-ramdis.img is the ubuntu one ie. not the one that contains the script/touch init file that moutns /data
[10:43] <ogra_> right, thats supposed to end up in /system/boot/ in your zip
[10:43] <ogra_> while the other is for the boot.img
[10:44] <annerajb> well i guess ill have to pack ramdisk.img by hand
[10:44] <annerajb> oops
[10:45] <annerajb> i mean the whole boot.img
[10:49] <ikillcypher> ogra_, http://pastie.org/private/tgyyfvzawfhj0mz8rl5z8q
[10:50] <ikillcypher> error im facing porting it to my device already did all the patches that was in https://wiki.ubuntu.com/Touch/Porting
[10:50] <annerajb> ikillcypher, did you remove the devicenameParts target?
[10:50] <ikillcypher> remove what?
[10:51] <ogra_> ikillcypher, thats a multi job build ... (waiting for unfinished jobs) ... the error cn be miles above, you need to paste more of the log
[10:51] <ogra_> it is likely that the actual error is just fallout of one that happened earlier
[10:51] <ikillcypher> http://pastie.org/private/pfvmi0fvf7wekllopi63wg
[10:51] <ikillcypher> here full logs
[10:55] <ikillcypher> humm ?
[10:59] <ikillcypher> o.o
[10:59] <smartboyhw> ikillcypher, hey how are you?
[11:05] <ikillcypher> ogra_ ?
[11:11] <diwic> ogra_, gaah. /dev/socket/qmux_bluetooth is a directory, and in there, there is one socket created in each direction.
[11:11] <diwic> ogra_, so I tried a variation on your command, and now the thing does not boot. Reflashing now.
[11:11] <ikillcypher> he seems to be have disappear
[11:12] <ikillcypher> smartboyhw, Im finally getting help on my porting
[11:12] <smartboyhw> ikillcypher, \o/
[11:12] <smartboyhw> Great
[11:12] <smartboyhw> How is your progress?
[11:13] <annerajb> ikillcypher, if you run brunch again do you get the same error?
[11:13] <ikillcypher> who me ?
[11:13] <annerajb> yes
[11:13] <ogra_> ikillcypher, that doesnt look like it builds a kernel at all
[11:13] <ikillcypher> let me try
[11:14] <annerajb> ikillcypher, listen to ogra he has a good point. you should have some kernel build lines aven after having completed a build it still check syscalls and version files
[11:14] <ikillcypher> so what should I do ?
[11:16] <ikillcypher> ogra_, ?
[11:17] <ogra_> dunno, make sure it builds a kernel :)
[11:17] <ikillcypher> o.o dude you are a ubuntu-touch developer
[11:17] <ogra_> go into the kernel dir, copy your defconfig to .config and see if you can do a maunual build
[11:17] <ikillcypher> manual build ?
[11:17] <ogra_> ikillcypher, well, i'm not a sony developer :P
[11:17] <ikillcypher> what
[11:18] <ikillcypher> make_defconfig ?
[11:18] <ogra_> try a manual kernel buid
[11:19] <ogra_> no, copy the defconfig for your device to .config in the toplevel dir of the kernel source tree
[11:19] <ogra_> then run make zImage and see if there are errors
[11:19] <annerajb> ogra_, this is my proc/last_kmsg http://paste.ubuntu.com/5976907/
[11:19] <annerajb>  It says no errors detected so apparently the bootstrap booted fine??
[11:19] <annerajb> I am seeign now a black screen and i have no adb
[11:20] <ogra_> thats a samsung, right ? give it some time, i havent found out yet why adbd comes up so slow on these devices .... if you have no boot loop thats a good sign at least
[11:21] <annerajb> ogra_,  if i have a boot loop will the animation show every loop?
[11:21] <ogra_> well, it will reboot all the time
[11:21] <ogra_> instead of sitting on a black screen with sdb running
[11:21] <ogra_> *adb
[11:21] <ikillcypher> oh fcuk
[11:21] <ikillcypher> there are like two yuga configs files
[11:22] <ikillcypher> one with cm_fusion_yuga
[11:22] <ikillcypher> and one with fusion_yuga
[11:22] <ikillcypher> wtf
[11:22] <annerajb> fun fun
[11:22] <ogra_> annerajb, [    4.223150] arch_reset: attempting watchdog reset
[11:23] <annerajb> kernel stall right?
[11:23] <ogra_> that looks like your kernel commits suicide
[11:23] <annerajb> fuuuuuuuuu
[11:23]  * ikillcypher retry to build
[11:23] <ikillcypher> sorry
[11:23] <ogra_> and i cant see it using the ubuntu initrd
[11:24] <ogra_> look at the lines after [    3.607211] Freeing init memory: 5356K ... there you should see a bunch of thing like starting udev and it would print which disk it mounts etc
[11:25] <ikillcypher> ogra_ how do I manuel build the kernel /
[11:25] <ogra_> [    3.581788] Warning: unable to open an initial console.
[11:25] <ogra_> that one is definitely an issue too
[11:25] <ogra_> ikillcypher, did you copy the config over to .config ?
[11:25] <ogra_> after that just run "make zImage"
[11:25] <ogra_> it should start building
[11:26] <ikillcypher> I really cant find .cofig ?
[11:26] <ikillcypher> .config
[11:29] <ogra_> no, you create it by copying the defconfig there
[11:29] <ikillcypher> so I create a new folder call .config
[11:29] <ogra_> cp /pathto/defconfig .config ... in the toplevel dir of your kerne
[11:30] <ogra_> no, a file
[11:30] <ikillcypher> and copy the two defconfig to it ?
[11:30] <ogra_> no, the one your build uses
[11:30] <ogra_> it surely only uses one
[11:30] <ikillcypher> well it does automatically o.O
[11:30] <ogra_> and you said you did the changes for tehh kernel config when porting ... so the file you edited before is the one
[11:30] <ikillcypher> oh
[11:31] <abimanyu> hi any one know how to debug boot loop?
[11:31] <ogra_> abimanyu, try to get into recovery without powering the device down ... then you can check /proc/last_kmsg from the recovery adb
[11:32] <ikillcypher> ./home/ikillcypher/xperiatouch/kernel/sony/apq8064/arch/arm/configs/cm_fusion3_yuga_defconfig
[11:32] <ikillcypher> that ?
[11:32] <ogra_> if thats the one your device uses for building the kernel, then that, yes
[11:32] <abimanyu> ogra_: i tried that but its only showing messages from bootloader not kernel
[11:33] <ikillcypher> cp /kernel/sony/apq8064/arch/arm/configs/cm_fusion3_yuga_defconfig  .config ?
[11:33] <ogra_> abimanyu, are you sure you didnt power down ?
[11:33] <ikillcypher> ogra_ im not good with bash commands :(
[11:33] <ogra_> abimanyu, last_kmsg lives in ram ... if power is lost you only get info from the current (recovery) boot
[11:34] <abimanyu> ogra_: i have Samsung Tab 2 i am unable to enter recovery without pressing power button
[11:35] <annerajb> ikillcypher, cp /home/ikillcypher/xperiatouch/kernel/sony/apq8064/arch/arm/configs/cm_fusion3_yuga_defconfig /home/ikillcypher/xperiatouch/kernel/.config
[11:35] <annerajb> ikillcypher, then do cd  /home/ikillcypher/xperiatouch/kernel/ && make zImage
[11:36] <ikillcypher> ikillcypher@ikillcypher:~/xperiatouch$  cd  /home/ikillcypher/xperiatouch/kernel/ && make zImage
[11:36] <ikillcypher> make: *** No rule to make target `zImage'.  Stop.
[11:36] <annerajb> ikillcypher, type pwd and paste the output of that command
[11:36] <ikillcypher> ikillcypher@ikillcypher:~/xperiatouch/kernel$ pwd
[11:36] <ikillcypher> /home/ikillcypher/xperiatouch/kernel
[11:37] <ogra_> wrong dir :)
[11:37] <ikillcypher> lol
[11:37]  * annerajb hides
[11:37] <ikillcypher> wtf ?!
[11:37] <ogra_>  /home/ikillcypher/xperiatouch/kernel/sony/apq8064/ is the toplevel dir for your kernel
[11:37] <ikillcypher> so what is the correct directory ? then
[11:37] <ikillcypher> yup it is
[11:37] <annerajb> o so the cp i gave ya is wrong
[11:38] <ikillcypher> cp /home/ikillcypher/xperiatouch/kernel/sony/apq8064/arch/arm/configs/cm_fusion3_yuga_defconfig  /home/ikillcypher/xperiatouch/kernel/sony/apq8064/ ?
[11:38] <annerajb> ikillcypher, cp /home/ikillcypher/xperiatouch/kernel/sony/apq8064/arch/arm/configs/cm_fusion3_yuga_defconfig /home/ikillcypher/xperiatouch/kernel/sony/apq8064/.config
[11:38] <annerajb> yeah
[11:38] <annerajb> use my because yours wont use the .config name after copying
[11:39] <annerajb> after that you can run make zImage inside the sony/apq8064/ directory
[11:39] <ikillcypher> yup I know not that newbie
[11:39] <annerajb> ogra_, any ideas about the initrd thing? how do i know if it's using the ubuntu initrd
[11:39] <ikillcypher> WHAT
[11:39] <ikillcypher> ]Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y
[11:39] <ikillcypher> Cross-compiler tool prefix (CROSS_COMPILE) [] (NEW)
[11:39] <annerajb> lol
[11:40] <ogra_> ikillcypher, oops :)
[11:40] <annerajb> it seems the default config need some updates
[11:40] <ogra_> try:
[11:40] <ikillcypher> Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y
[11:40] <ikillcypher> Cross-compiler tool prefix (CROSS_COMPILE) [] (NEW)
[11:40] <ikillcypher> Local version - append to kernel release (LOCALVERSION) [] (NEW)
[11:40] <ikillcypher> Automatically append version information to the version string (LOCALVERSION_AUTO) [Y/n/?] (NEW)
[11:40] <ogra_> export CROSS_COMPILE="/home/ikillcypher/xperiatouch/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-"
[11:40] <ikillcypher> I Press enter and this happens
[11:40] <ogra_> and then run again
[11:41] <ikillcypher> interuppt the zImage ?
[11:41] <ogra_> yes
[11:41] <ogra_> yo dont want it to mangel your config
[11:43] <ikillcypher> ogra_
[11:43] <ikillcypher> http://pastie.org/private/om2pedfz42vtrodgxr9a
[11:43] <ogra_> are you sure you copied the .config in place ?
[11:44] <ogra_> ls -l ./.config
[11:44] <ikillcypher> ikillcypher@ikillcypher:~/xperiatouch/kernel/sony/apq8064$ ls -l ./.config
[11:44] <ikillcypher> -rw-rw-r-- 1 ikillcypher ikillcypher 14549 Aug 12 19:38 ./.config
[11:44] <ogra_> hmm, ok
[11:44] <ogra_> weird that it asks questions, it shouldnt
[11:45] <annerajb> ogra_, could it be that the device config is old and the new kernel introduced this new flags?
[11:45] <annerajb> actually nvm..
[11:45] <ogra_> well, the device config should be for the kernel version in use ... unless the cyanogenmod tree is wrong
[11:46] <annerajb> i dont think the kernel just added the ability to append kernel release to local version.
[11:46] <ogra_> no
[11:46]  * ikillcypher heartbrokes and hope he is able to port it 
[11:46] <ikillcypher> cause thousands of users will be dying for it so Im not going to give up
[11:47] <ogra_> ikillcypher, wait until sergiusens gets up, he usually has better ideas sbout the android trees than me ...
[11:47] <ikillcypher> how long is that
[11:48] <ikillcypher> it is 19:47 here
[11:48] <ogra_> dunno. just hang around here ... the above line wil have highlighted his name
[11:48] <ogra_> and he usually reads the backlog on IRC
[11:50] <annerajb> ogra_, any ideas on what i could do apart from go under the desk and cry? the wiki said somethings about enabling CONSOLE_ on the kconfig but i have them all enabled.
[11:50] <ogra_> annerajb, i would start trying yo get the ubuntu initrd in use first
[11:51] <annerajb> which one is the ubuntu initrd the rootfs??
[11:51] <annerajb> or the ramdisk.img?
[11:51] <ogra_> it shoul dtheoretically be the ramdisk.img
[11:52] <annerajb> hmm my /system dosnt have scripts/touch
[11:52] <annerajb> let me flash again.
[11:52] <ogra_> and you should see it printing stuff about systemd-udevd  and init should print which disks it tries to mount etc
[11:52] <ogra_> your /system never has scripts/touch
[11:52] <annerajb> yeah like the error i had before. it seems the latest flash broke it
[11:52] <annerajb> oh where is scripts/touch then?
[11:52] <ogra_> inside the initrd
[11:53] <ogra_> (and in a place in the ubuntu rootfs. but thats not of any interest for your issue)
[11:54] <annerajb> where does the initrd reside on /system?
[12:02]  * ikillcypher does not know what to do 
[12:02]  * ikillcypher reboot into windows for the time being
[12:13] <annerajb> ogra_, so i commented too much and it wasnt copying the initrd. still can't get the stupid script/touch to stay modified :(
[12:19] <diwic> ogra_, so I tried manually executing these commands in a root shell, and they indeed resolved the problem that you need to run as root:
[12:19] <diwic> ogra_, "chmod a+rwx /dev/socket/qmux_bluetooth" "chmod a+rw /dev/socket/qmux_bluetooth/*"
[12:23] <ogra_> diwic, heh, i bet -R would have done that too ... but yeah, lets probably do it this way and save additional system users
[12:26] <diwic> ogra_, -R ?
[12:26] <ogra_> rercursive :)
[12:26] <diwic> aha, as a switch to chmod
[12:26]  * diwic is slow today
[12:27] <ogra_> yeah
[12:27] <iKillCypher> ogra_, let me know once that dude is back
[12:27] <diwic> ogra_, opening it up to *any* user, including malicious apps, does not sound like a good idea to me
[12:28] <diwic> ogra_, hum, unless they're blocked by apparmor perhaps
[12:28] <ogra_> diwic, yeah, indeed, but we're also trying to get rid of these hardcoded android UID/GID stuff
[12:29] <diwic> ogra_, I'll just trust that you know more than me on the matter then :-)
[12:29] <ogra_> heh, no, i dont
[12:30] <ogra_> but we cant just use a UID that only exists on ubuntu ... the socket is shared, permission chnages also happen in android
[12:30] <ogra_> so that would force the next android UID into the ubuntu side ...
[12:31] <ogra_> i'm pondering which is the less bitter pill to swallow :)
[12:36] <iKillCypher> ogra_ do you think the porting is possible for my device
[12:36] <iKillCypher> xperia z
[12:36] <iKillCypher> since some others have done it for xerpia z tablet and other xperia devices
[12:36] <ogra_> iKillCypher, if cyanogenmod runs, it should indeed
[12:37] <iKillCypher> should I ask one of the members to join in here freexperia team member ?
[12:38] <ogra_> iKillCypher, did you try running cyanogenmod on your device before starting to port ?
[12:38] <iKillCypher> yeah of cause
[12:38] <ogra_> ok, then porting should work too
[12:38] <iKillCypher> I have even build cm 10.2 and cm 10.1 on my device
[12:39] <iKillCypher> I will try to ask the member to join this channel
[12:41] <themikem> iKillCypher: you might start with mamenyaka's kernel: https://github.com/mamenyaka/android_kernel_sony_apq8064
[12:42] <iKillCypher> what about it
[12:42] <themikem> his Xperia Tablet Z port is on https://github.com/mamenyaka
[12:43] <themikem> you're using the same kernel on your device.  He made the mods necessary to run Ubuntu to the kernel already, and has it integrated with the android build system.  Might be a good reference for what you are trying to do, given the devices are very similar.
[12:44] <iKillCypher> I have made necessary patches to kernel too
[12:45] <themikem> okay, just a suggestion
[12:46] <iKillCypher> well I will pm him then
[12:46] <iKillCypher> thank you
[12:47] <themikem> your build system for the "brunch" command is going to use the defconfig you mentioned earlier.  If you want to mod the config, you need to mod that defconfig file and then run make mrproper in the apq8064 kernel directory
[12:48] <themikem> if you want to use menuconfig, you can run ./make_defconfig.sh cm_fusion3_yuga_defconfig in kernel/sony/apq8064
[12:48] <iKillCypher> huh ?
[12:48] <iKillCypher> well I just want it to brunch properly
[12:48] <iKillCypher> so I dont get what are you trying to sya
[12:48] <iKillCypher> say*
[12:49] <themikem> right, so brunch is using cm_fusion3_yuga_defconfig to build your kernel
[12:49] <themikem> (most likely anyway, you'll need to double check it)
[12:49] <iKillCypher> and ? edit ?
[12:49] <iKillCypher> I did that
[12:49] <themikem> so if you want to modify the kernel configuration, you'll need to modify cm_fusion3_yuga_defconfig
[12:50] <themikem> then run make mrproper in the apq8064 directory, croot, and then brunch
[12:51] <iKillCypher> yup did that ?
[12:51] <iKillCypher> run make mrproper ?
[12:51] <iKillCypher> themikem can you repeat that Im going to boot into ubuntu for now
[12:51] <iKillCypher> in awhile
[12:51] <iKillCypher> brb
[12:52] <themikem> yes, you have to do the "make mrproper" in kernel/sony/apq8064.  The make_defconfig.sh script does all this for you.
[13:20] <daftonrails> Saw this advert F.Y.I. about Ubuntu Edge on ebay .... http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=130965518650&ssPageName=ADME:B:SS:GB:1123
[13:25] <mamenyaka> sergiusens, ogra_ hi! got a moment?
[13:28] <ikillcypher> mapreri, here ?
[13:28] <ikillcypher> what did you tell me just now ?
[13:29] <_polto_> hello
[13:30] <_polto_> "phablet-flash community -d mako" do not work. output: bzr: ERROR: Invalid url supplied to transport: "lp:~mako-image-dev/phablet-image-info/mako": No such person or team: mako-image-dev
[13:30] <Oroku_Saki> "root@ubuntu-phablet:/# ./logcat Unable to open log device '/dev/alog/main' "??? /dev/alog???
[13:30] <_polto_> any idea pls ?
[13:35] <cyphermox> good morning!
[13:38] <ikillcypher> ??
[13:38] <ikillcypher> where did that guy go just now
[13:42] <ikillcypher> o.o :(
[13:44] <_polto_> good morning. sorry to repeat myself for those who  just came in..
[13:44] <_polto_> "phablet-flash community -d mako" do not work. output: bzr: ERROR: Invalid url supplied to transport: "lp:~mako-image-dev/phablet-image-info/mako": No such person or team: mako-image-dev
[13:44] <_polto_> any idea pls ?
[13:44] <ikillcypher> nope
[13:45] <_polto_> and I was surprised by ubuntu-one icon that just login you on the web interface, but do not allow any sync with my phone.
[13:48] <_polto_> also on Nexus4 phone jack does not work. It does on android.
[13:49] <ogra_> _polto_, i dont think you want the "community" in your command there ... mako is officially supported
[13:50] <ogra_> and the sound layer isnt even implemented, dont expect everything to work there :)
[13:50] <_polto_> ogra_, oh, how to get the latest build for nexus4 ?
[13:50] <ogra_> well, sergiusens changed the commands, i dont know what you need for official ... moitting "community" should print you the options though
[13:50] <ogra_> *omitting
[13:51] <ogra_> likely something with "cdimage"
[13:51] <_polto_> ogra_, I got my main phone stolen. So I am evaluating if my ubuntu-phone can become my daily phone.
[13:51] <_polto_> I was not able yet to setup 3G.
[13:52] <ogra_> it should just come up AFAIK
[13:52] <ogra_> (if you dont have a PIN lock in place at least)
[13:53] <ogra_> there might still be UI glitches though ... the indicator showing ot wrong etc
[13:53] <_polto_> ogra_, I did not find how to setup a lock
[13:53] <ogra_> well, does your SIM have  a PIN ?
[13:53] <_polto_> I removed the PIN since the phone is not asking for and do not work with the PIN.
[13:53] <ogra_> ah, k
[13:53] <ogra_> then it should just connect
[13:54] <ogra_> and yoou should see rmnet0 as your network connection if you check from commandline
[13:55] <_polto_> OK. Cellular settings show  the choice 2G or 2/3/4G in gray (not selectable)
[13:55] <ogra_> dont trust the settings app ... nothing is connected to anything there
[13:56] <ogra_> (well, some bits are, but dont ask which)
[13:56] <_polto_> OK :)
[13:56] <ogra_> check with the terminal :)
[13:57] <ogra_> nmcli d
[13:57] <ogra_> should give you the list of devices
[13:57] <ogra_> nmcli c
[13:57] <ogra_> the connections is use (or available)
[13:58] <_polto_> gsm disconnected
[13:58] <ogra_> is this a recent image ?
[13:59] <ogra_> /var/log/installer/media-info has the build stamp on current images
[14:01] <_polto_> ogra_, how could I sync contacts to my phone ?
[14:02] <_polto_> ogra_, 20130811
[14:02] <ogra_> i think that only works for google contacts
[14:02] <ogra_> well, looks like yesterdays image then
[14:02] <_polto_> google contacts are ok, to start
[14:03] <_polto_> my android was synchronised..
[14:03] <_polto_> also I tried OTG USB and HDMI on nexus4, none of them worked. :(
[14:04] <ogra_> no, it wont for 13.10
[14:04] <_polto_> :(
[14:04] <ogra_> thats only planned for 14.04
[14:04] <ogra_> 13.10 id the target for a working phone system ... 14.04 for convergence
[14:05] <popey> hmm, flashing mako my phone is sat at the android guts screen and phablet-flash is telling me INFO:phablet-flash:Flashing system to /home/alan/Downloads/phablet-flash/ubuntu-touch/20130812/saucy-preinstalled-system-armel+mako.img
[14:05] <popey> < waiting for device >
[14:05] <popey> what's it waiting for?
[14:05] <ogra_> the device
[14:05] <ogra_> :P
[14:05] <popey> ☻
[14:05] <popey> its there.
[14:05] <sergiusens> popey: hmmm... are you on saucy?
[14:05] <popey> I've even moved it closer on the desk
[14:05] <popey> yes sergiusens
[14:05] <ogra_> did you use the new syntax ?
[14:06] <sergiusens> popey: just replug it in
[14:06] <popey> its a machine I _just_ upgraded to saucy
[14:06] <popey> yes ogra_
[14:06] <popey> alan     23751  2.0  0.4  63112 14036 pts/5    S+   15:02   0:04 /usr/bin/python /usr/bin/phablet-flash cdimage-touch -b --pendin
[14:06] <sergiusens> popey: replug it in... also see if fastboot devices returns anything
[14:06] <popey> replugged
[14:06] <popey> still sat there
[14:06] <sergiusens> popey: what about running fastboot devices? and then 'sudo fastboot devices'
[14:07] <sergiusens> popey: and did you have custom udev rules before updating?
[14:07] <Oroku_Saki> Hey ogra.. do you know why logcat goes to /dev/alog instead of /dev/log... problems running logcat....
[14:07] <popey> alan@hactar:~/phablet-flash-wrapper$ fastboot devices
[14:07] <popey> no permissions  fastboot
[14:07] <popey> alan@hactar:~/phablet-flash-wrapper$ sudo fastboot devices
[14:07] <popey> [sudo] password for alan:
[14:07] <popey> 04c770facfe7991f        fastboot
[14:07] <Oroku_Saki> I think its a libhybris thing?
[14:07] <ogra_> Oroku_Saki, namespace issues ...
[14:07] <ogra_> our logcat reads from it though
[14:07] <popey> sergiusens: no, didnt touch udev, this laptop has been in a drawer for months
[14:08] <Oroku_Saki> my touchpad shows dev/log and dev/log_main etc... should this work?
[14:08] <sergiusens> popey: so this is a udev issue
[14:08] <popey> its never had the ppa on either
[14:08] <plars> pmcgowan: Do you know who could take a look at bug #1211334. I'm not sure whether the retracer will deal with it successfully or not, we'll see I guess.
[14:08] <sergiusens> popey: what version of android-tools-fastboot do you have?
[14:08] <Oroku_Saki> I am booting off a lvm partition
[14:08] <ogra_> Oroku_Saki, no, the udev rules in ubuntu would move it to /dev/alog (and logcat only looks there with the phablet tree)
[14:09] <popey> sergiusens: 4.2.2+git20130218-3ubuntu14
[14:09] <plars> asac: in case you are interested also, bug #1211334
[14:09] <sergiusens> popey: oh... issue can be if you ever used 'android' _months_ ago :-) and added a rule into your udev that would break the ones in the package
[14:09] <Oroku_Saki> had to add lvm.static and change my initramfs, told it where the data partition was and.. have problems mount loop with /data/system.img so I just told it where my system partition was
[14:09] <popey> its never used android on that laptop
[14:09] <Oroku_Saki> I added udev rules...
[14:09] <ikillcypher> sergiusens, OMG
[14:09] <popey> its never had anything to do with phablet on
[14:09] <ogra_> Oroku_Saki, oyu mean you try to boot your device with lvm on the mmc ?
[14:09] <Oroku_Saki> yep
[14:09] <ikillcypher> you are here waited for you for ages
[14:09] <Oroku_Saki> and it booted.
[14:10] <ogra_> Oroku_Saki, that will surely need a lot of tinkering with the ubuntu initrd then
[14:10] <Oroku_Saki> but... having problems finding out if android is running.. and I get EGL.cfg cannot be found errors
[14:10] <Oroku_Saki> so I thought I would try to run logcat =)
[14:10] <sergiusens> ikillcypher: there are other people here who can help too
[14:10] <Oroku_Saki> I have never been able to successfully do a logcat
[14:10] <Oroku_Saki> =)
[14:10] <Oroku_Saki> in my life
[14:10] <ikillcypher> ogra_, asked me to wait for you
[14:10] <_polto_> so long..
[14:10] <_polto_> :(
[14:10] <_polto_> ogra_, thanks for all the help. I'll try to use it as main OS on my phone for some time.
[14:10] <_polto_> let's see how it works for me.
[14:10] <ogra_> Oroku_Saki, well, if everything worked /system/bin/logcat should just do what you knwo it for
[14:10] <Oroku_Saki> polto, I would help you
[14:11] <Oroku_Saki> but I don't have any supported devices
[14:11] <sergiusens> popey: can you unplug the device, run 'udevadm  monitor' and plug it in again?
[14:11] <Oroku_Saki> that is what is bugging me, it says it cannot find /dev/alog
[14:11] <Oroku_Saki> quantal was the last time I got the gui working
[14:11] <popey> sergiusens: http://paste.ubuntu.com/5977432/
[14:12] <Oroku_Saki> you helped me then.. so.. you got it working.. =)
[14:12] <ikillcypher> ogra_, what was the issue I was facing kernel right
[14:12] <ikillcypher> ?
[14:12] <ogra_> ikillcypher, i just said he might have better ideas :0
[14:12] <ogra_> :)
[14:12] <Oroku_Saki> you had me copy my missing libs and firmware from jb... but my new rom sources do not require that
[14:12] <ikillcypher> well let wait for him to respond then
[14:12] <ogra_> ikillcypher, your kernel doesnt start to build
[14:13] <ikillcypher> :'(
[14:13] <ikillcypher> yeah let hope someone can help me out
[14:14] <ikillcypher> cause I really want to support this devices and make the community happy
[14:14] <Oroku_Saki> ogra_ can you tell me where exactly the android system partition is supposed to be mounted? /system or /android/system.. and the /data partition???
[14:14] <Oroku_Saki> I get confused about the android data partition vs the phablet data partition
[14:14] <ogra_> /system and /data
[14:14] <ikillcypher> anyway im wondering why not write it from scratch ?
[14:14] <Oroku_Saki> so /data should just be my cm-data partition?
[14:14] <ikillcypher> why use cm as based ?
[14:14] <ikillcypher> cm == cyanogenmod ?
[14:14] <ogra_> Oroku_Saki, right
[14:14] <Oroku_Saki> hmmm okay.. well.. that is right
[14:15] <ogra_> Oroku_Saki, though it becomes your / too
[14:15] <Oroku_Saki> what about /android/system does that really matter?
[14:15] <sergiusens> popey: can you append a --property to that command?
[14:15] <Oroku_Saki> also, I don't seem to have an fstab in my android-ramdisk.img
[14:15] <Oroku_Saki> so I added one.. but it didn't seem to help
[14:15] <ogra_> https://wiki.ubuntu.com/Touch/ContainerArchitecture
[14:15] <Oroku_Saki> lxc complains it cannot find mtab or fstab
[14:15] <ogra_> have a read ... that should give you some impression
[14:16] <popey> sergiusens: http://paste.ubuntu.com/5977455/
[14:17] <Oroku_Saki> thanks ogra! time for work.. read it when i get.. to.. "work"
[14:17] <Oroku_Saki> =)
[14:17] <ogra_> :)
[14:17] <Oroku_Saki> looks sweet though... or neat.. thought out real well.. do you know why they flipped it?
[14:18] <Oroku_Saki> touch script is confusing.. wish someone would post one that uses system partitions instead of detecting the data partition based off of a label and or uuid
[14:19] <annerajb> Oroku_Saki, i hardcoded mine it was a pain to do if yuo need help il sent you a diff
[14:19] <ogra_> Oroku_Saki, bug 1199084
[14:19] <Oroku_Saki> thanks! here is mine.. http://pastebin.com/40ZXZk9P I would like to compare it with yours
[14:19] <annerajb> Oroku_Saki, https://github.com/w-flo/android_build/commit/522aee7be3503cb9c6db65b8163cdc3e73fbfc9c#core/Makefile
[14:19] <ogra_> i'll try to get that fixed this week
[14:19] <annerajb> ogra_, :D
[14:20] <Oroku_Saki> I stared at it for at least an hour... =) thanks! the one thing I got stuck on is loop mounting my system.imf
[14:20] <Oroku_Saki> it wouldn't mount.. so I said screw it.. here is my /dev/store/cm-system...
[14:20] <ogra_> Oroku_Saki, uh, dont mix up things
[14:20]  * ikillcypher omg any idea what should I do
[14:20] <ikillcypher> im like staring here
[14:20] <ogra_> Oroku_Saki, the tpuch scripts does many things for mand diffeerent images
[14:20] <ogra_> *touch
[14:21] <ogra_> only one path is the right one
[14:21] <Oroku_Saki> I noticed
[14:21] <Oroku_Saki> mntroot, etc
[14:21] <ikillcypher> and ogra_ why wasnt ubuntu- touch written from scratch?
[14:21] <ogra_> (loop mounting doesnt happen at all in normal flipped)
[14:21] <Oroku_Saki> mntroot should be my /data
[14:21] <annerajb> ikillcypher, probably because the effort it would require it would be gigantic
[14:21] <Oroku_Saki> hmm
[14:21] <ogra_> ikillcypher, because the drivers for the hardware wouldnt be usable this way
[14:22] <Oroku_Saki> mount -o loop,ro ${rootmnt}/var/lib/lxc/android/system.img /android-system
[14:22] <ogra_> annerajb, it wouldnt, but you wouldnt find free drivers for modems or graphics
[14:22] <Oroku_Saki> that is where it wouldn't mount, even with my system.img being there... or anywhere
[14:22] <Oroku_Saki> and.. there is not a system.img in that path...
[14:22] <ogra_> Oroku_Saki, yes, normal flipped images do not loop mount anything
[14:22] <ogra_> and they dont use img files at all
[14:23] <Oroku_Saki> omg confused =)
[14:23] <ogra_> as i said, dont try to make all code paths of the touch script work
[14:23] <ikillcypher> so ubuntu-touch is based on android ?
[14:23] <ogra_> all you want is to add your device to the top level list
[14:23] <lilstevie> ogra_, is there any way to bump up the amount of logging from upowerd? on my device it calls for an emergency shutdown for what seems to be no reason on unplugging it
[14:23] <ogra_> ikillcypher, no
[14:23] <ogra_> lilstevie, there should be a debug option ... no idea how to enable it though
[14:24] <lilstevie> ogra_, :/ okay
[14:24] <Oroku_Saki> @annerajb can you pastebin your touch?
[14:24] <sergiusens> popey: your issue is that I don't have a mako ;-)
[14:24] <Oroku_Saki> I need a cheat sheet
[14:24] <annerajb> yeah
[14:24] <Oroku_Saki> thanks!
[14:24] <ogra_> ikillcypher, ubuntu uses a few binary drivers from android ... and all the bits that are needed to make these drivers operate properly
[14:24] <popey> sergiusens: hah
[14:24] <ikillcypher> rest ?
[14:24] <popey> sergiusens: i can give you ssh access to the laptop if that helps?
[14:25] <annerajb> Oroku_Saki, thought that wont work. since the touch script get's overwritten
[14:25] <sergiusens> popey: nah, the stuff you gave is good
[14:25] <Oroku_Saki> I put it in my initramfs myself
[14:25] <ikillcypher> popey, developer right ?
[14:25] <Oroku_Saki> under /scripts
[14:26] <ogra_> Oroku_Saki, theoreically adding mmcblk0p267 or whatever your /data partition is to the variable at the top which holds the list of lables shoudl eb enough
[14:26] <Oroku_Saki> problem is my /data partition is a logical volume
[14:26] <ogra_> yeah, thats an issue
[14:26] <Oroku_Saki> and the uuid does not show up in by-label or uuid
[14:26] <ogra_> and wont be easy to solve
[14:26] <Oroku_Saki> I did get labels to work on my logical fat32 partition
[14:26] <popey> ikillcypher: hmm?
[14:27] <Oroku_Saki> I think I may be able to add labels to my data and system partition so the labels show up in /dev/disk/by-label
[14:27] <Oroku_Saki> I had the change the 60-persistent rules and remove dm-*
[14:27] <ogra_> well, you should be able to mount by device name ...
[14:27] <ogra_> by just adding it to the list
[14:27] <Oroku_Saki> I just mount by /dev/store or /dev/mapper
[14:28] <Oroku_Saki> the uuid's for ext4 do not match the actual uuid shown by blkid
[14:28] <ogra_> well....
[14:28] <ogra_> partlist="userdata UDA DATAFS USERDATA"
[14:28] <Oroku_Saki> oh yeah... a touch script that works off the blkid would be cool. =)
[14:28] <Oroku_Saki> yeah I say that partlist=
[14:28] <ogra_> just add something that identifies the device there
[14:28] <sergiusens> popey:  cat /lib/udev/rules.d/70-android-tools-fastboot.rules | pastebinit
[14:29] <Oroku_Saki> are those partition labels?
[14:29] <annerajb> i added mtdblock3 to that line and that's what all my changes Oroku_Saki
[14:29] <Oroku_Saki> ahhh
[14:29] <annerajb> Oroku_Saki, they are device names
[14:29] <ogra_> Oroku_Saki, thats a list thats just used with find /dev -name $listitem
[14:29] <ikillcypher> ogra_, sergiusens , popey  : Im facing this error and im trying to port ubuntu-touch to xerpia z once im done I wish I could help in the development :(
[14:29] <Oroku_Saki> my /dev does not show a .. /dev/data
[14:29] <ikillcypher> http://pastie.org/private/jidrdo0dh0wzgtefjhc2rq
[14:29] <ogra_> on first match the loop breaks and the found device is used for mounting
[14:29] <ogra_> Oroku_Saki, why would that matter
[14:29] <Oroku_Saki> I figure its a attribute of the partition
[14:30] <ogra_> find searches in /dev
[14:30] <ogra_> and uses whatever it finds first
[14:30] <popey> sergiusens: http://paste.ubuntu.com/5977496/
[14:30] <annerajb> Oroku_Saki, what i did to find my device name was to boot into recovery mount data and in adb run df -h
[14:30] <ogra_> no matter what subdir it is in
[14:31] <Oroku_Saki> it is getting a list of all the names in /dev
[14:31] <sergiusens> popey: so your udev stuff is fine, in comparison to mine at least, and it seems you get seat
[14:31] <Oroku_Saki> how is it matching that to a name like "datafs or uda"
[14:31] <Oroku_Saki> ?
[14:31] <ogra_> Oroku_Saki, right, so just add a proper match
[14:31] <Oroku_Saki> dm-3 or etc?
[14:31]  * ikillcypher is sad 
[14:31] <Oroku_Saki> since mine say dm-1 dm-4 as virtual device mapper disks
[14:31] <ogra_> find /dev -name dm-3
[14:32] <ogra_> or rather just add dm-3 to the partlist variable
[14:32] <ogra_> and it should juyst magically all work
[14:32] <sergiusens> popey: just for the sake of it grep 4ee0 /lib/udev/rules.d/* /etc/udev/rules.d/* | pastebinit
[14:32] <Oroku_Saki> thanks! one last question.. should I have a system.img in my /data? I don't see how touch script detects my system.img.. I see it in the script.. but
[14:32] <ogra_> no, thats another image type
[14:32] <popey> sergiusens: http://paste.ubuntu.com/5977502/
[14:33] <sergiusens> popey: this should just work! :-/
[14:33] <popey> ☹
[14:33] <Oroku_Saki> "echo "initrd: mounting ${rootmnt}/var/lib/lxc/android/system.img as ${rootmnt}/android/system" >/dev/kmsg || true 		mount --move /android-system ${rootmnt}/android/system"
[14:33]  * popey starts again
[14:33] <Oroku_Saki> that confused me
[14:33]  * ikillcypher is wondering what's with the ignore
[14:33] <sergiusens> popey: can you do this without --bootstrap ?
[14:34] <popey> sure
[14:34] <ogra_> Oroku_Saki, yeah, thats for the OTA images which arent supported for ports atm
[14:34] <ogra_> Oroku_Saki, just ignore all that stuff
[14:34] <Oroku_Saki> thanks!
[14:34] <ogra_> all you need is the device name in the list
[14:34] <Oroku_Saki> confused the hell out of me...  great.. that does work.
[14:35] <Oroku_Saki> it reads my build.prop from my /system
[14:35] <ikillcypher> rawr
[14:35] <Oroku_Saki> but only if I mount system hardcoded
[14:35] <ikillcypher> am I not around :(
[14:35] <Oroku_Saki> so I do.. "mount --bind /android-system ${rootmnt}/android/system 		mount --bind ${rootmnt}/userdata ${rootmnt}/android/data"
[14:35] <ogra_> Oroku_Saki, mounting /system is dealt with by fstab
[14:35] <ogra_> (in ubuntu)
[14:35] <Oroku_Saki> then I have /system and /data linked to /android/system and /android/data
[14:36] <ogra_> no, you dont want that
[14:36] <popey> sergiusens: http://paste.ubuntu.com/5977517/
[14:36] <Oroku_Saki> yeah... I had a feeling you would say that
[14:36] <Oroku_Saki> so system should be mounted automagically?
[14:36] <ikillcypher> sergiusens, popey too busy for me ?
[14:36] <ikillcypher> :(
[14:36] <ogra_> Oroku_Saki, first make sure the initrd gets you into an ubuntu rootfs and adbd is up there ... then we can move on
[14:37] <sergiusens> ikillcypher: you need to ask a specific question, this is high traffic and most of us do this _while_ we work on other things
[14:37] <popey> ikillcypher: I can't help, sorry
[14:37] <ikillcypher> http://pastie.org/private/jidrdo0dh0wzgtefjhc2rq
[14:37] <ikillcypher> that is my question
[14:37] <Oroku_Saki> that part it easy, but I will change it this time my just adding my dm-* to my partition list and report back.
[14:37] <sergiusens> popey: are you using xmir?
[14:37] <ogra_> Oroku_Saki, the setup creates the fstab on first boot using a script, that script will need adjustment too
[14:37] <popey> sergiusens: no, but the desktop isn't logged in
[14:37] <ikillcypher> ogra_, knows what is happening o.o
[14:37] <Oroku_Saki> I dont have an fstab in my android-ramdisk though.. is that bad?
[14:37] <popey> it's a remote machine
[14:37] <ogra_> Oroku_Saki, but first try to get a proper boot :)
[14:37] <popey> as in, it's on the other side of my desk
[14:38] <sergiusens> popey: hmmm... ah, so you need to have _seat_
[14:38] <Oroku_Saki> okay... okay.. getting to far ahead of myself
[14:38]  * popey logs in
[14:38] <Oroku_Saki> also when I try to run android-chroot it complains about /proc/-1/root not being there
[14:38] <popey> sorry sergiusens
[14:38] <ogra_> sergiusens, i wish i could say the same ... today i didnt manage to do anything "while" working on other bits :)
[14:38] <Oroku_Saki> maybe your suggestions will fix that
[14:39] <sergiusens> ogra_: was figured speach, last thing I did yesterday was with my invisible cloke on :-)
[14:39] <ogra_> Oroku_Saki, android-chroot kind of expects that the container is up and running ... i dont think thats the case for you yet
[14:39] <ogra_> sergiusens, haha
[14:39] <Oroku_Saki> lxc-config gripes about no mtab or fstab
[14:39] <ogra_> we need mores such cloaks
[14:39] <Oroku_Saki> so I bet so.. try again after the changes... time for work!! =)
[14:39] <ogra_> Oroku_Saki, right, just get the boot going and we can move on
[14:39] <Oroku_Saki> thanks man!
[14:39] <ogra_> one step at a time
[14:40] <ikillcypher> ok now me >:(
[14:40] <Oroku_Saki> the worst part is: when it works... bored.. the fun part is getting it to work.
[14:41] <ogra_> ikillcypher, well, there isnt much to help with, get your kernel to build, then it will move on (or find out why it doesnt build and fix that)
[14:41] <ikillcypher> and how do I do that ?
[14:41] <ikillcypher> since zImage isnt working
[14:41] <ikillcypher> make zImage
[14:41] <ogra_> Oroku_Saki, should we break it more often so you dont lose interest ?
[14:41] <Oroku_Saki> yes
[14:41] <ogra_> haha
[14:41] <Oroku_Saki> like webos
[14:41] <Oroku_Saki> =)
[14:42] <Oroku_Saki> I at least got openweb os to boot a gui on my maserati phone.. but I lost interest after that....
[14:42] <Oroku_Saki> that and I realized they were using libhybris and working off of ubuntu-touch
[14:43] <Oroku_Saki> and then touch changed a lot.. which left me wondering.. what the hell will happen to open-webos
[14:43] <Oroku_Saki> =)
[14:43] <ikillcypher> ogra_,
[14:43] <ikillcypher> Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y
[14:43] <ikillcypher> Cross-compiler tool prefix (CROSS_COMPILE) [] (NEW)
[14:44] <ikillcypher> DUDE !_! WHY !_!
[14:45] <ogra_> because it wants these set and they arent, usually the build scripts wold set them in your environemnt so nothing would ask forr them i guess
[14:46] <ogra_> did you ever build a CM image manually ? you should probably start with that, make sure you understand whats going on and find out if it happens there as well
[14:46] <ogra_> or even lower and read up about how to build a kernel
[14:46] <pmcgowan> plars, I assigned it to gusch
[14:48] <plars> pmcgowan: thanks
[14:48] <gusch> pmcgowan plars looking at that https://jenkins.qa.ubuntu.com/job/saucy-touch-maguro-smoke-gallery-app-autopilot/72/artifact/clientlogs/ the powerd crashed as well, and dmesg.log reports some thermal problems
[14:49] <plars> gusch: yes, we see that powerd crash pretty frequently
[14:49] <ikillcypher> YES I HAVE BUILD CM MANUALLY
[14:49] <ikillcypher> sorry for the caps
[14:49] <ogra_> ikillcypher, and does it build the kernel there ?
[14:49] <sforshee> plars, gusch: every powerd crash I've looked at has been due to powerd starting before the sensors were ready, and afaik we don't yet have any way to deal with that
[14:50] <ogra_> ikillcypher, so just compare the two kernel trees and find the difference
[14:50] <ikillcypher> http://pastie.org/private/mkmyzeikg5trot50piovoq
[14:50] <ogra_> and if you have it i bet your build will work
[14:50] <ogra_> sforshee, !
[14:50] <gusch> plars: so if that's a thermal issue, then gallery has no chance to fix that ;)
[14:50] <ogra_> sforshee, powerd uses the snesorservice ?
[14:51] <sforshee> ogra_: yes it uses the proximity sensor to turn off the screen during calls
[14:51] <ogra_> sforshee, we *need* to make sure it starts after the container then
[14:51] <sforshee> ogra_: how do we do that?
[14:51] <ogra_> sforshee, we are trying to hunt down an issue where something accesses the sensor service before the container is up since weeks ... the container fails then
[14:52] <Oroku_Saki> oh yeah... my device backlight is under /sys/class/leds...  that has never worked for me.. quantal used to complain
[14:52] <plars> gusch: I'm not sure why they would be having thermal issues, unless the powerd crash could cause that... sforshee?
[14:52] <ogra_> nobody ever thought about powerd i think :)
[14:52] <Oroku_Saki> powerd seems to use /sys/class/backlight
[14:52] <Oroku_Saki> for the lcd backlight
[14:52] <ogra_> Oroku_Saki, it also uses hybris to talk to sensors
[14:52] <sforshee> plars: thermal issues wouldn't be caused by powerd
[14:52] <sforshee> Oroku_Saki: yes, that's the standard kernel framework for backlights
[14:52] <ogra_> no, thermal issues could be caused by ueventd hanging
[14:53] <ogra_> or by rteh sensorservice not being able to start
[14:53] <Oroku_Saki> does the container have to be running for graphics to work (stupid question, I expect yes)
[14:53] <plars> ogra_: we're aware of that, and we kill ueventd to force a restart before running the test
[14:53] <ogra_> Oroku_Saki, rightm thats a yes :)
[14:53] <Oroku_Saki> that is why my egl config can't be found then
[14:53] <Oroku_Saki> like it says in some link somewhere
[14:54] <ogra_> plars, right, it seems though that just having powerd's upstart job depend on the "android" event would fix all this :)
[14:54] <plars> the ueventd eating 100% cpu bug kills the autopilot jobs in general, so if it were that I would expect to see a lot more than those 2 failures
[14:54] <Oroku_Saki> my backlight uses /dev/lm8502 so I added that to udev though it is not in my udev.device.rc it is mentioned in my init.device.rc
[14:54] <Oroku_Saki> I thought that was smart. =)
[14:54] <Oroku_Saki> okay I better go
[14:54] <ogra_> Oroku_Saki, the mpunpoints need to be populated (/system, /data, /vendor and factory) and the container needs to be up for graphics to work
[14:55] <ogra_> *mountpoints
[14:55] <Oroku_Saki> oh
[14:55] <Oroku_Saki> yeah I don't have vendor or factory
[14:55] <Oroku_Saki> what is /android/system for?
[14:55] <ogra_> factory is mostly used for 3G stuff ... likley not important ... and it is often also called efs
[14:56] <ikillcypher> ogra_, that wont work
[14:56] <ogra_> /adnroid/system is for the OTA images
[14:56] <ikillcypher> since it was modified
[14:56] <Oroku_Saki> I guess that is the tmpfs that populates those /system /vendor or etc
[14:56] <ikillcypher> I will try to ask one of the existing ubuntu developer
[14:56] <ogra_> it isnt used in normal flipped images
[14:56] <Oroku_Saki> OTA image.. over the air?
[14:56] <ogra_> yes
[14:56] <Oroku_Saki> you mean the 400mb zip file?
[14:57] <ogra_> Oroku_Saki, https://wiki.ubuntu.com/ImageBasedUpgrades ...
[14:57] <ogra_> thats the next step after flipped images
[14:57] <Oroku_Saki> so having /android is... useless?
[14:58] <ogra_> yes
[14:58] <Oroku_Saki> I see that in my touch script though
[14:58] <ogra_> it doesnt exist on normal flipped images
[14:58] <Oroku_Saki> where it is creating /tmpfs/android, etc
[14:58] <ogra_> the touch script is used for various different image types
[14:58] <ogra_> ignore that part
[14:58] <Oroku_Saki> it looks for /tmpmnt/system.img
[14:58] <ogra_> yes
[14:58] <ogra_> which should never be there on a normal flipped image
[14:59] <Oroku_Saki> so... does this go into affect? # Old flipped model 	elif [ -d /tmpmnt/ubuntu ]; then 		mount --bind /tmpmnt/ubuntu ${rootmnt} 		mountroot_status="$?"
[14:59] <annerajb> Oroku_Saki, hey how did you repack your scripts/touch i can't figure out how to make mine use a modified touch script without the zip being broken
[15:00] <annerajb> the device zip cannot be installed since it's broken somehown if i modify it
[15:00] <Oroku_Saki> unpack gunzip -c ../your-ramdisk-file | cpio -i
[15:00] <ogra_> Oroku_Saki, no
[15:00] <ogra_> nothing of this is used
[15:00] <annerajb> Oroku_Saki, do you run that after getting the zip from brunch? or in between?
[15:02] <Oroku_Saki> I just found it in my initramfs, under /scripts I take the kernel that is in uimage, and split the ramdisk and kernel, unpack the ramdisk, edit touch, pack it, and join the kernel and ramdisk back into a uimage file that is compatible for moboot, my boot loader
[15:02] <asac> bug #1211334
[15:02] <Oroku_Saki> http://www.android-dls.com/wiki/?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
[15:03] <asac> plars: is this reproducible?
[15:03] <asac> e.g. retrying gives the same result?
[15:03] <Oroku_Saki> creating a moboot compatible uImage uses the mkimage command
[15:04] <annerajb> Oroku_Saki, thanks :D
[15:04] <Oroku_Saki> np
[15:04] <gusch> plars: how can I open/use the core dump file?
[15:04] <Oroku_Saki> @ogra_ cat /android-system/boot/android-ramdisk.img | gzip -d | cpio -i fstab*
[15:05] <Oroku_Saki> is that used?
[15:05] <ogra_> Oroku_Saki, not used :)
[15:05] <Oroku_Saki> dang it man! what is used?
[15:05] <ogra_> only the first "find" and the according mount call
[15:06] <ogra_> all the other logic lives inside the rootfs for nromal flipped
[15:06] <Oroku_Saki> so it would then go to here? # Mount the data partition to a temporary mount point 	mount /dev/store/cm-data /tmpmnt 	mount --bind /tmpmnt/ubuntu ${rootmnt
[15:06] <Oroku_Saki> well.. what it would normally say stock?
[15:06] <ogra_> yes
[15:06] <Oroku_Saki> Ahhhhh
[15:06] <ogra_> well, just add it to the list :)
[15:06] <ogra_> the fid should find it by name
[15:06] <ogra_> *find
[15:06] <Oroku_Saki> userdata UDA DATAFS USERDATA SWEET..
[15:06] <Oroku_Saki> okay, thanks!
[15:07] <ogra_> right
[15:07] <ogra_> it mounts that, then bindmounts the ubuntu subdir and just moves on
[15:07] <Oroku_Saki> you should have spent yesterday on here, instead of... doing.. enjoying the sunshine and spending time with your family, blast you!
[15:07] <ogra_> no further mounts mangling or anything
[15:07] <Oroku_Saki> =)
[15:07] <ogra_> haha
[15:07] <ogra_> yeah, i know ... i'm such a lazy bastard
[15:08] <ogra_> not working on weekends and the like :)
[15:10] <ikillcypher> :(
[15:10]  * ikillcypher is SAd
[15:13] <plars> gusch: gdb I would guess
[15:13] <plars> asac: doubtful, we can try, but probably difficult to reproduce
[15:15] <asac> plars: we saw gallery app being flakyt before. I assume this is the reason?
[15:15] <asac> if so, i am sure it will come back. lets retry and see if it goes green
[15:15] <asac> gusch: did the coredump in the bug give you anything useful?
[15:16] <plars> asac: no, this is new
[15:17] <plars> asac: we have not seen this crash in the past runs
[15:17] <asac> ok
[15:17] <asac> plars: if we retry, we wont' loose the log etc.?
[15:17] <plars> asac: it will disappear from the dashboard, but we won't lose it completely
[15:17] <davmor2> ogra_: you mean you don't have a second job working weekends like the rest of us........oh hang on you're going to say taking care of families isn't a second job right ;)
[15:17] <plars> asac: and we can get it back there too
[15:18] <ogra_> davmor2, on the weekends i'm a gardener ... and can opener for my cats
[15:18] <asac> lets see if there is anything useful in the coredump from gusch
[15:18] <ogra_> davmor2, sometimes i'm a cleaning woman
[15:18] <ogra_> :)
[15:19] <balloons> iBelieve, is someone else on the team going to review https://code.launchpad.net/~mdspencer/ubuntu-filemanager-app/sidebar/+merge/178783?
[15:20] <iBelieve> balloons, Arto doesn't have much time, Carlos works on the backend, not the UI, and mhall119 is out of town, so I haven't found anyone to merge it.
[15:22] <iBelieve> balloons, though popey looks like he's back. I'll see if he can do it.
[15:23] <balloons> iBelieve, kk :-)
[15:24] <davmor2> ogra_: see that's 3 extra jobs you hadn't even thought about right :)
[15:24] <iBelieve> popey, could you take a look at the merge requests I've made for File Manager? No one else on the team has had time to review them.
[15:24] <ogra_> davmor2, heh, yeah ...
[15:27] <mpt> didrocks, https://wiki.ubuntu.com/SoftwareUpdates#Phone
[15:27] <didrocks> mpt: thanks!
[15:30] <davmor2> ogra_, popey: if you go to plus.google.com/app/basic/stream on the browser do you get a static window? or can you scroll on it.  In Thursdays image it was fine but on fridays and todays it is static for me
[15:30] <ogra_> davmor2, i can scroll in the non mobile version
[15:30] <ogra_> but it started to hang recently in the mobile version
[15:31] <davmor2> ogra_: twitter is the same so I'm assuming it is to do with the user agent but could be wrong
[15:31] <davmor2> user agent string that is
[15:32] <davmor2> ogra_: also how do you get the desktop version up mine always seems to be the mobile version :)
[15:33] <ogra_> davmor2, i think asac pomoted a new user agent string ... might be thats it is slightly wrong
[15:34]  * davmor2 glares at asac 
[15:36] <popey> iBelieve: will take a look
[15:36] <iBelieve> popey, thank you!
[15:38] <davmor2> asac: is it possible that this breakage coincides with the update to the user agent string?
[15:58] <jdstrand> ChickenCutlass: hey, when audio flinger is moved to HAL, does that mean we'll be using pulseaudio
[15:58] <ChickenCutlass> jdstrand, correct
[15:58] <jdstrand> ChickenCutlass: cool, thanks :)
[15:59] <gusch> asac: I don't get any hint from the core file, but I guess the gallery was built without debug symbols ...
[16:04] <gusch> asac: I just call "gdb /usr/bin/gallery-app /tmp/CoreDump" - any better way to use the core dump?
[16:12] <gusch> plars: I just call "gdb /usr/bin/gallery-app /tmp/CoreDump" - any better way to use the core dump? As gallery  seems to not have debug symbols
[16:14] <annerajb> gusch, there is a way to get stack trace without debug symbols on the crashed binary
[16:14] <annerajb> gusch, but it requires the debug symbols that where stripped from the build.
[16:15] <annerajb> and the segfault line from the dmesg
[16:19] <gusch> annerajb: ok - how do I do that? I'll need quite some help for that ...
[16:19] <annerajb> well you can start by finding the debug symbols of the gallery app assuming they where compile with
[16:19] <annerajb> sometimes they are build with them and stripped after building and saved somewhere else
[16:21] <digossantos> someone online?
[16:21] <gusch> annerajb: I'd then assume the symbols be in a separate package, but there is none
[16:21] <ogra_> no, 336 people idling
[16:22] <annerajb> gusch, you can look at the makefiles see if it's build with symbols
[16:22] <annerajb> also you could compile it yourself with symbols
[16:23] <gusch> annerajb: but then I'd need the exact same version, right?
[16:23] <annerajb> well if it crashes with a newer version then you have symbols if it dosnt the bug was fixed?
[16:23] <digossantos> hello fellows, I'm tring to port ubuntu-touch to the sony xperia s lt26i. I was able to boot and run the shell in the quantal-phablet-mwc image, but any image newer than that gets me to a black screen
[16:24] <gusch> annerajb: the crash happened only once - I'm not able to reproduce it
[16:24] <digossantos> have you ever seen this issue?
[16:24] <annerajb> gusch, then you will have to track the symbols (assuming they are saved somewhere)
[16:25] <annerajb> gusch, i have to head out to get lunch but ask aroud hopefully one of the ubuntu touch developers can tell you where the symbols may be
[16:31] <asac> plars: did you retry the phone-app? e.g. reproducible?
[16:33] <ogra_> asac, do you know if the useragent string in the browser was changed ? i know you had asked for it
[16:33] <ogra_> seems G+ and twitter stopped working in mobile mode now
[16:34] <popey> ogra_: visit http://popey.com/ogra from the phone and I'll tell you what the UA is ☻
[16:34] <ogra_> heh, cool
[16:35] <popey> bah, loads of other people clicking that ☻
[16:35] <Cantide> lol
[16:36] <ogra_> popey, heh, and i just get a 404
[16:36] <popey> yeah, you will, whats your public IP?
[16:36] <ogra_> uh, 87 something ...
[16:36] <ogra_> 80.152.237.3
[16:36] <ogra_> 80 :P
[16:37] <popey> hmm, see no visit today
[16:38] <ogra_> funny ... i see the 404
[16:39] <ogra_> and a search form
[16:39] <popey> on the phone?
[16:39] <ogra_> yes
[16:39] <popey> how strange
[16:39] <ogra_> popey.com blog ...
[16:40] <ogra_> calendar and a ton of links on the right
[16:40] <balloons> plars, asac I'm saddened to see the fixes for weather did not work in the lab. Everything runs locally here for me and on the device ;-(. Do we have videos being produced yet for failures? I don't see anything in the jenkins artifacts
[16:40] <ogra_> and your askubuntu icon
[16:40] <plars> balloons: that doesn't work on the device, only on x86
[16:41] <plars> balloons: it is working for you on a real device?
[16:41] <balloons> plars, ahh, right.. of course :-)
[16:41] <plars> asac: you mean gallery app?
[16:41] <balloons> plars, yes, weather seems to be a network issue completely. it's just plain timing out
[16:44] <popey> ogra_: "Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 Safari/7534.48.3"
[16:44] <popey> so no, not changed
[16:44] <ogra_> popey, www.whatismyuseragent.com
[16:44] <ogra_> :)
[16:44] <ogra_> yeah, i get the same
[16:44] <popey> hah, i get an iis error on that domain ☻
[16:45] <ogra_> lol
[16:45] <Cantide> iis :C==*
[16:45] <ogra_> hmm
[16:45] <ogra_> it gets the IP wrong though
[16:46] <ogra_> ah, no, it doesnt ...
[16:48] <ogra_> popey, well, does G+ work for you ? can you scroll ?
[16:49] <ogra_> all elemnts, links and buttons work
[16:49] <ogra_> but i cant scroll
[16:49] <popey> the phone is painfully slow here
[16:50] <popey> actually just the kb
[16:50] <ogra_> i can even use the swipe gesture that brings in the G+ menu
[16:50] <popey> bah, 500 error loading plus
[16:50] <ogra_> ... which in turn is probably what steals the scrolling
[16:51] <popey> yeah, wont scroll here either
[16:51] <popey> i got to plus via gmail
[16:51] <ogra_> for me it works if i siwtch to the desktop version
[16:53] <davmor2> ogra_: confirmed, popey if you goto plus.google.com/circles then goto home from there you get the desktop version and it works fine.  I have no idea what broke it from Friday on but something did and it needs fixing :)
[16:54] <ogra_> are you sure it worked on friday ?
[16:54] <ogra_> i have the thu. image installed
[16:55] <ogra_> root@ubuntu-phablet:/# cat /var/log/installer/media-info
[16:55] <ogra_> Ubuntu Saucy Salamander (development branch) - armhf (20130808)
[16:55] <davmor2> ogra_: 20130809 was the first day it didn't but I didn't find out till I had logged off,  and thought it might be a temporary issue, so waited till today to confirm
[16:55] <ogra_> well, it doesnt work for me
[16:55] <davmor2> ogra_: thursdays image was fine for me fridays was the first that died for me
[16:56] <ogra_> so it either has borken earlier or it is googles fault
[16:56] <davmor2> ogra_: ah hang on wasn't thursday the day you did 2 images?
[16:58] <davmor2> or was that wednesday,  I'm thinking if it was thursday I might of got the earlier image rather than the later one
[16:58] <ogra_> yeah, there were several on thu.
[16:59] <ogra_> hmm
[17:00] <ogra_> grepping for iPhone in the webbrowser-app source reveals nothing
[17:00] <davmor2> ogra_: so I would of had 0808 so it might of broken on a later build that I picked up on friday hence the difference maybe?
[17:01] <ogra_> yeah
[17:03] <ogra_> aha
[17:03]  * ogra_ finds /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/Extras/Browser/UbuntuWebView.qml
[17:04] <Cantide> neutral to which region?
[17:05] <Cantide> oops, wrong channel, sorry
[17:08] <davmor2> ogra_, popey: muhahaha run the browser from the terminal and enjoy the warning
[17:09]  * ogra_ changed the user agent ... 
[17:09] <ogra_> didnt change anything
[17:11] <davmor2> ogra_: with the new agent string does twitter scroll if so then it might be that gplus changed something
[17:11] <ogra_> dunno, i dont have a twitter account
[17:11] <ogra_> G+ definitely doesnt and kind of gets messed up CSS
[17:12] <ogra_> (using the user agent string from a galaxy S4)
[17:19] <balloons> fginther, if you have a sec, can you help explain what the deal with this not merging is? https://code.launchpad.net/~nskaggs/ubuntu-clock-app/convert-aptests-to-sdk/+merge/179062. The video shows it's not finding the qml file to launch?
[17:19] <awe> b
[17:20] <ogra_> c
[17:20] <awe> cyphermox, ping
[17:20] <awe> ogra_, d
[17:20] <ogra_> awe, f
[17:20]  * awe thinks ogra_ missed a letter in the sequence
[17:20] <awe> ;D
[17:20] <ogra_> owww
[17:29] <asac> plars: zes
[17:31] <plars> asac: hmm, I think you are saying yes to my question earlier? I reran the gallery tests, and they passed this time as I suspected. It could be, as gusch thought, related to the thermal issue, which we now believe to be related to whoopsie pegging out the cpu. Or it could be just a hard-to-reproduce gallery segfault
[17:31] <asac> plars: phone-app needs same attention
[17:31] <asac> i was told fix for this has landed or is about to land
[17:32] <asac> so lets revisit tomorrow and wednesday
[17:32] <asac> if thats gone
[17:32] <plars> asac: sounds good
[17:32] <asac> balloons: your fixes haven't made it into the image? do you know?
[17:33] <balloons> asac, filemanager didn't land into the package, and thus didn't make it into the image. Weather did, and sadly it didn't change anything. inside the lab it appears the test timeout's trying to connect to the weather api
[17:34] <asac> balloons: thats something that goes through network?
[17:34] <balloons> asac, we've made changes to test more specifically for this timeout that should land today.. but i'm not sure what to do for network failures
[17:34] <asac> i assume we have no outward internet connection (for weather)
[17:35] <balloons> asac, plars said it shouldn't be an issue, but it seemingly is.. the api can be flaky so I blamed that, but it definitely works on my device
[17:35] <asac> plars: touch devices have open access to the internet?
[17:35] <asac> in the lab?
[17:35] <plars> asac: for everything but icmp
[17:35] <plars> asac: but that shouldn't be a problem for it
[17:36] <asac> plars: maybe we landed this tunnel through adb?
[17:36] <asac> do we have other tests that access the internet and succeed still?
[17:36] <plars> asac: last I checked, still waiting for a merge in phablet-tools
[17:36] <asac> ok... so thats unlikely the reason
[17:37] <balloons> right, I don't want to cop out that it's a network issue, but the tests literally are timing out on the network updates.. ie, running a search for a city, updating the weather, etc
[17:37] <asac> balloons: guess stay on it for now... you could maybe add something simple like a "wget" test that ensures you can get proper data from some server
[17:38] <asac> plars: can we add that to default?
[17:38] <balloons> asac, heard.. We'll keep adding things to shed some more specific light on what's going on inside the lab
[17:38] <asac> plars: like a wget
[17:38] <plars> asac: we are already doing much more than that at each test run, we are pulling the tests across the network
[17:38] <asac> to know up front hat we can access the internet for sure
[17:39] <balloons> yes, your connecting to lp correct?
[17:39] <asac> plars: dont know... we are not doing that externally, do we?
[17:39] <plars> asac: yes, externally
[17:39] <asac> plars: from where to where?
[17:39] <plars> asac: from the ppa right now, with click, it will be from bzr
[17:39] <asac> those are special places
[17:39] <asac> i would think that code and ppa might be special places in terms of canonical DC
[17:40] <asac> with special rules
[17:40] <plars> balloons: there's some possibility that the device could be super busy with whoopsie eating 100% of the cpu
[17:40] <balloons> plars, well we could bump the timeout's even further.. they are at 30 seconds.. you think more time is needed?
[17:40] <asac> plars: can we find out if whoopsie is running and wait before ruther tests get kicked off?
[17:41] <plars> balloons: have you tried it running locally on a device? or just on x86?
[17:41] <plars> asac: whoopsie is always running
[17:41] <balloons> plars, yes, tested on my device, and m-b-o's also
[17:41] <asac> plars: always processing crashes also?
[17:41] <plars> balloons: ok, I'll add it to my stack of things to try to get to today
[17:41] <plars> asac: no, it's just eating 100% cpu in some tight polling loop right now, new bug
[17:42] <asac> really?
[17:42] <balloons> plars, I'll also push the timeout's to a couple mins each
[17:42] <plars> asac: https://bugs.launchpad.net/touch-preview-images/+bug/1211417
[17:42] <balloons> if that's ok
[17:42] <asac> plars: so you see that locally?
[17:42] <plars> asac: yes
[17:43] <asac> always reproducible? if so go to foundations guys i guess
[17:43] <asac> feels important
[17:43] <plars> asac: yes, om26er  just opened the bug a bit ago, and it is definitely reproducible
[17:43] <asac> i guess thats because we landed whoopsie on phone today?
[17:44] <asac> or is that a regression?
[17:44] <ogra_> whoopsie landed a while ago
[17:44] <balloons> fginther, d'oh I figured out the issue with clock, ty
[17:44] <asac> ok
[17:44] <ogra_> but didnt do much usefule stuff iirc
[17:45] <asac> can we check if we picked up the whoospie upload from today?
[17:45] <asac> https://launchpad.net/ubuntu/+source/whoopsie
[17:45] <asac> see it went up 8hours ago
[17:45] <ogra_> ev only landed the finctional changes recently IIRC
[17:45] <asac> ev: ^^
[17:45] <ogra_> *functional ... :)
[17:45] <ogra_> not fictional :)
[17:45] <asac> ogra_: can you check if we have 0.2.20 on todays image? maybe that is the fix for this issue?
[17:46] <plars> asac: 0.2.20 is on today's image
[17:46] <ogra_> whoopsie	0.2.20
[17:46] <asac> ev: see above... seems whoopsie does some harm to our images :)
[17:46] <asac> and phones
[17:46] <ogra_> according to http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20130812/saucy-preinstalled-touch-armhf.manifest
[17:47] <plars> ogra_: I confirmed it on my device locally as well
[17:47] <om26er> me too
[17:47] <om26er> just after I updated my phone, it picked the latest whoopsie 0.2.20 and the issue happened after that
[17:48] <ogra_> it started to log to syslog on friday
[17:48] <annerajb> ogra_, where i can find a changelog for the nightly images?
[17:48] <ogra_> the other changes just seem to be test related
[17:48] <asac> i think this is the diff that landed today?
[17:48] <asac> http://launchpadlibrarian.net/147375280/whoopsie_0.2.16_0.2.20.diff.gz
[17:49] <ogra_> annerajb, we dont have one yet (whey were only available in the old build system, it is planned to have the changelogs again later)
[17:49] <asac> 16 -> 20
[17:49] <annerajb> ogra_, allrighty
[17:50] <asac> plars: could you file this bug against the whoospie package as well?
[17:50] <ogra_> ++
[17:51] <asac> thx
[17:51] <asac> seems done now
[17:51] <plars> asac: yes, done
[17:52] <om26er> we reported it for whoopsie directly and added touch-preview-images as affects
[17:52] <ogra_> very good
[17:53] <asac> om26er: confusing that we have two targets. in general, the distro packages should be first stop for everything that comes out of the archive
[17:53] <plars> om26er: what works much nicer, when you have a package to open against, is to use ubuntu-bug package_name. Then you can always go back and open a a task against touch-preview-images, etc
[17:53] <asac> right
[17:54] <om26er> plars, right, I was a defect-analyst previously ;) since the problem was on a phone ubuntu-bug would add not much to the bug report
[17:54] <plars> om26er: I can understand the confusion, for phone apps you would typically open against the project, but for ubuntu things we would normally open against the package rather than the project
[17:54] <plars> om26er: wouldn't add much, no, but would open against the package instead of the project, and if there were any logs that they like to get for that package it would grab them automagically
[17:55] <asac> plars: we dont want to do that either anymore
[17:55] <asac> everything that has a package should get a package bug
[17:55] <plars> asac: don't do what?
[17:55] <asac> plars: use the upstrewam project
[17:55] <plars> asac: oh, but I thought we were going away from packages in the apps?
[17:55] <ogra_> yes, and to archive packages
[17:55] <plars> asac: or do you treat the ubuntu package as synonymous with a click package?
[17:55] <asac> plars: oh right. good point. i completely forgot
[17:56] <asac> plars: TBD
[17:56] <ogra_> heh
[17:56] <asac> i guess we dont have a reasonable story there yet
[17:56] <plars> ogra_: right, that would fall under "ubuntu things" for lack of a better term to come to mind
[17:56] <ogra_> yeah
[17:56] <ogra_> click is a different story
[17:56] <plars> indeed
[17:56] <ogra_> without any plans yet i guess
[18:04] <cyphermox> awe: pong
[18:04] <awe> I updated davmor2's bug: https://bugs.launchpad.net/touch-preview-images/+bug/1206888
[18:05] <awe> looks like a race between NM's ofono settings plugin & ofono's provision plugin
[18:05] <awe> so if the NM plugins runs first
[18:05] <awe> all bets are off
[18:05] <davmor2> awe: I'm just overjoyed you could replicate it :)
[18:06]  * awe is glad he can make someone happy on a Monday
[18:18] <davmor2> awe: I'm always happy, well and grumpy, in hayfever season I'm sneezy, 4 more to go and I'm a full set
[18:20] <OrokuSaki> @ugra_ changed my touch "partlist="dm-10 userdata UDA DATAFS USERDATA" booting now
[18:20] <OrokuSaki> @ogra_
[18:20] <OrokuSaki> it worked, I am in phablet
[18:22] <OrokuSaki> @ogra_ cat lxc-android-boot.log mount: can't find /data in /etc/fstab or /etc/mtab
[18:22] <dualinity> and...is Ubuntu Touch worth it yet?
[18:22] <OrokuSaki> system is not populated though...
[18:23] <dualinity> No apps?
[18:23] <OrokuSaki> system partition does not show to be mounted
[18:42] <mfisch> ogra_: are you around or are you at debconf too?
[18:48] <OrokuSaki> I added the /data partition to my fstab.. now it wants the vendor to be added
[18:49] <OrokuSaki> but I don't have a vendor partition
[18:49] <OrokuSaki> so my update-fstab script may not be working?
[18:59] <sergiusens> plars: does this work for you? https://lists.launchpad.net/ubuntu-phone/msg03282.html
[18:59] <sergiusens> plars: I meant -> https://code.launchpad.net/~sergiusens/phablet-tools/lock_makedirs/+merge/179777
[19:07] <annerajb> is android-ramdisk.img being used??
[19:16] <OrokuSaki> @ogra_ I got lxc-android-boot to show success. =)
[19:26] <annerajb> Oroku_Saki, grats :D
[19:27] <_polto_> ogra_, about HDMI on Nexus or any other phone. the presentation video with a screen - it's a fake ? Or does it work on some other model ? Also what is the best supported and powerful hardware to run ubuntu-touch ?
[19:29] <Joe_B> _polto, the presentation was done using ubuntu for android (which is in a working state), ubuntu touch tethering/docking I think is scheduled to begin development in october and april release.
[19:33] <_polto_> Joe_B, Oh. Thanks !
[19:34] <jdstrand> sergiusens: hi! I responded to your manta bug
[19:35] <_polto_> Joe_B,  but  I can not find any download link for ubuntu for android. Is it available ?
[19:35] <jdstrand> sergiusens: if you are available now, I can help you
[19:36] <Joe_B> _polto_: http://news.softpedia.com/news/Ubuntu-for-Android-Will-Not-Be-Released-Before-Ubuntu-Edge-373531.shtml
[19:41] <jdstrand> sergiusens: feel free to comment in the bug too :)
[19:43] <_polto_> Joe_B,  hmmm... I do not see any reasons to let us play with touch, but not with ubuntu for android.  (I co-funded Edge. And I think about buying more of them soon)
[19:45] <Joe_B> _polto_: I'm not with canonical.  I don't know their reasoning.
[19:45] <Joe_B> But I'd assume they're not just being arbitrary.
[19:49] <_polto_> Joe_B, at least not arbitrary. I hope so. :) Just that my main phone was stolen and now I have only the nexus 4 that I was testing with touch, but it's not yet 100% OK for my daily usage. So instead of going 100% android (CM) I would prefer this intermediate solution of ubuntu for android.
[19:52] <OrokuSaki> cat lxc-android-boot.log.... "ln: failed to create symbolic link '/lib/modules': File exists"
[19:52] <OrokuSaki> anyone got any ideas?
[19:52] <OrokuSaki> is that referring to /system/lib/modules or /lib modules?
[19:54] <Nick> it should be /system/lib/modules on android
[20:01] <Joe_B> _polto_, I actually just nabbed an original galaxy nexus from ebay for $80 us to try out touch, android hardware can be had even cheaper.
[20:15] <OrokuSaki> @ogra_ cat unity8.log = Cant find EGLConfig, returning null config
[20:15] <OrokuSaki> android seems to be running now
[20:17] <OrokuSaki> lxc-wait -n android -s RUNNING and no more logs complaints in /var/log/upstart
[20:17] <OrokuSaki> anyone have any ideas?
[20:18] <OrokuSaki> root@ubuntu-phablet:/home/phablet/.cache/upstart# qmlscene = qmlscene: could not find a Qt installation of ''
[20:21] <annerajb> Oroku_Saki, how did you extracted the boot.img?
[20:21] <annerajb> I tried with cpio and it didnt work
[20:21] <OrokuSaki> the boot.img..... ??? hmmmm
[20:22] <annerajb> did you have to extract it?
[20:22] <OrokuSaki> I am using a bootloader to boot, it boots a uImage
[20:22] <annerajb> oh
[20:22] <annerajb> all righty
[20:22] <OrokuSaki> maybe something to do with my kernel console argument?
[20:23] <OrokuSaki> worked in quantal though
[20:23] <annerajb> me?
[20:23] <annerajb> oh your issue
[20:23] <OrokuSaki> yeah.. I think its a Qt5 issue with my adreno gpu?
[20:23] <annerajb> do you get any egl errors like failing to open device?
[20:24] <OrokuSaki> Cant find EGLConfig, returning null config
[20:24] <OrokuSaki> that is in my unity8.log
[20:26] <OrokuSaki> http://gpupowered.org/node/8 I found a link about qt5 stuff... and export QT_QPA_EGLFS_DEPTH=24, but that is TI stuff and I have qualcomm
[20:27] <annerajb> that's for screen resolution that should be unrelated to your issue
[20:27] <annerajb> can you run qt3d (assuming you have it)
[20:28] <OrokuSaki> cant seem to run logcat... Unable to open log device '/dev/alog/main': No such file or directory
[20:28] <annerajb> or if you type qt and tab do you get any binaries
[20:28] <OrokuSaki> qt says command not found
[20:28] <annerajb> Oroku_Saki, http://www.slideshare.net/prabindh/qt5-on-ti-processors slide 8
[20:29] <annerajb> do you get that could not create egl surface
[20:30] <OrokuSaki> how can I be sure my SGX driver is installed?
[20:33] <annerajb> lsmod?
[20:34] <OrokuSaki> yeah.. my kernel doesn't seem to use a module for graphics
[20:34] <OrokuSaki> it is all built into the kernel.. my phones does though.. funny because my tablet and phone have the same gpu
[20:34] <OrokuSaki> phone has a module for graphics, tablet does not
[20:35] <OrokuSaki> qmlscene says it cannot find QT
[20:37] <OrokuSaki> qtconfig: could not find a Qt installation of ''
[20:39] <OrokuSaki> @annerajb qt3d doesn't seem to exist
[20:40] <annerajb> did you copy the vendor blobs?
[20:40] <OrokuSaki> oh snap!
[20:40] <OrokuSaki> no...
[20:40] <annerajb> yay!
[20:40] <OrokuSaki> so take everything in my jellybean vendor and copy over to /vendor?
[20:40] <OrokuSaki> thanks man!
[20:41] <annerajb> there is a script to make your life easy
[20:43] <OrokuSaki> the extract files script?
[20:43] <annerajb> yup
[20:43] <OrokuSaki> on the porting page?
[20:43] <balloons> plars, the build fro weather is finished, if you do make it that far down your list today
[20:43] <OrokuSaki> I just copied my vendor folder over from my jellybean vendor folder
[20:43] <annerajb> not sure if that works but give it a try :P
[20:43] <OrokuSaki> I thought that would do it
[20:43] <plars> balloons: awesome, I'll get to it
[20:44] <annerajb> take a look at your device specific extract-files.sh and check if it's that easy
[20:44] <plars> balloons: did you change anything other than the timeout?
[20:45] <annerajb> Oroku_Saki, in my device it copies files that are not on vendor/ for example EGL get's copied from lib/egl/libGLES_android.so !!!!!!!
[20:45] <balloons> plars, timeouts moved up to 2 mins, and there has been a network error added.. m-b-o did the work on it
[20:47] <OrokuSaki> all vendor blobs made it successfully
[20:48] <OrokuSaki> yep.. it copies files to /system/bin /system/etc/firmware, etc
[20:48] <OrokuSaki> they are all in the rom /system folder
[20:48] <annerajb> all right hopefully you got all the files !
[20:49] <OrokuSaki> powerd restarts over and over again
[20:50] <OrokuSaki> Aug 12 20:49:24 ubuntu-phablet powerd[4867]: No backlight devices found Aug 12 20:49:24 ubuntu-phablet powerd[4867]: Could not read maximum brightness, guessing at dim/bright values
[20:50] <OrokuSaki> my source works on quantal, that I know.... the gui comes up...
[20:50] <rickspencer3> hey, if I have a javascript object that is key value pairs, is there a cooler way to display the values in QML than just updating the text of labels?
[20:57] <annerajb> OrokuSaki, someone was saying earlier that powerd was restarting on canonical test servers earlier and gave a explanation
[20:58] <annerajb> OrokuSaki, thought on your case it says about backlight and brightness
[20:58] <OrokuSaki> I remember that.. but then someone said it shouldn't matter.. it shouldn't prevent me from getting a gui....
[20:58] <OrokuSaki> I am /sys/class/leds/lcd_backlight
[20:58] <annerajb> so you still get the same egl errors from earlier?
[20:58] <OrokuSaki> instead of /sys/class/backlight
[20:58] <OrokuSaki> yeah.. same egl errors
[20:58] <annerajb> damm it
[20:59] <OrokuSaki> what gets me is I should be able to run qmlscene
[20:59] <annerajb> what does it print when you run it?
[21:00] <annerajb> no qt found?
[21:00] <OrokuSaki> qmlscene: could not find a Qt installation of ''
[21:00] <OrokuSaki> qtconfig says the same thing
[21:00] <annerajb> gtg
[21:00] <OrokuSaki> ttyl8r!
[21:00] <OrokuSaki> =)
[21:25] <ArcadiaFrame> hi im interested in porting ubuntu touch to my droid x or htc hero, any advice?
[21:26] <ArcadiaFrame> im kinda new to programming as a whole but willing to learn
[21:28] <masei> Anyone got usb otg working on nexus 4 with ubuntu touch? Nothing is showing in up in dmesg when I connect any usb devices
[21:29] <genii> !porting
[21:29] <genii> Hm.
[22:02] <frankennetbook> hello all... just wonder if someone can help me out, i'm trying to flash a phone i have with ubuntu touch but I'm getting the following error error: device not found ERROR:phablet-flash:Command 'adb shell getprop ro.cm.device ' returned non-zero exit status 255
[22:02] <frankennetbook> anyone know what that might mean?
[22:15] <RobbyF> whats the best way to keep my device updated other than flashing daily?
[22:17] <annerajb> so it seems that modifying the scripts/touch after packing (and repacking it) corrupts the boot.img
[22:19] <annerajb> Oroku_Saki, you got any luck?
[22:26] <IdleOne> Could someone tell me if Touch would run on this http://www.opip.com/product/JXD-P300-7-inch-WSVGA-Screen-Dual-Core-Android-4.0-Tablet-PC-with-GPS-WiFi-Camera-Bluetooth_p18618.html ?
[22:43] <annerajb> IdleOne, apparently there are people working on a port for it. as a guideline if you can run cyanogen mod on a device ubuntu touch should run
[22:44] <annerajb> IdleOne, see this apparently somebody is already working on getting cyanogen mod working on them http://forum.xda-developers.com/showthread.php?t=2399865
[22:44] <IdleOne> annerajb: cool, ty.
[22:44] <annerajb> np
[23:04] <achiang> sergiusens: hi, i'm trying to manually install some demo content on my N4, using a saucy (flipped) image. i'm reading the source of phablet-demo-setup right now, and i see that it only seems to grab the pictures, contacts, and indicator content. however in the PPA, i see music and video content available for saucy...
[23:04] <achiang> sergiusens: what's the story with that?
[23:05] <sergiusens> achiang: that's already installed
[23:05] <achiang> sergiusens: ah, ok
[23:05] <sergiusens> achiang: they are the lens/scopes in there
[23:05] <achiang> sergiusens: ack
[23:05] <achiang> sergiusens: so that includes the shell package too?
[23:06] <sergiusens> achiang: the demo shell stuff? yes
[23:06] <Oroku_Saki> @annerajb not yet... I just do my ramdisk.img file that is part of my uImage
[23:06] <annerajb> lucky you!
[23:07] <Oroku_Saki> my device has 2 kernel options.. 2.6.35 or 3.0.8... 2.6.35 lacks fanotify
[23:07] <Oroku_Saki> so I am rebuilding with 3.0.8.. I was able to make it work last time.. without fanotify and quantal
[23:08] <Oroku_Saki> 3.0.8 lacks.. lots of stuff.. it was never finished
[23:14] <achiang> sergiusens: thank you for the help
[23:37] <achiang> sergiusens: hi, sorry to bug you again, but any clue on why contacts might be busted?
[23:37] <achiang> # dpkg -l | grep contacts
[23:37] <achiang> ii  demo-assets-contacts                                  0.26-0ubuntu1
[23:37] <sergiusens> achiang: it's most likely abandoned
[23:37] <achiang> what does that mean?
[23:39] <sergiusens> achiang: dead code
[23:48] <koegzist> hey can some one help install the ubuntu touch on the nexus 4
[23:48] <koegzist> the phablet flash command isnt working
[23:49] <koegzist> -_-
[23:54] <annerajb> koegzist, how are you writing the command?
[23:54] <annerajb> Oroku_Saki, Werent you having this issue earlier 6.893714] initrd: mounting /dev/block/mtdblock3
[23:54] <annerajb> [    6.898351] initrd: Couldn't find a system partition.
[23:55] <koegzist> no this is my first time on irc ever
[23:55] <koegzist> lol
[23:55] <koegzist> phablet-flash (cdimage-touch|cdimage-legacy|ubuntu-system|community) -b
[23:56] <koegzist> is what im doing
[23:56] <koegzist> whwhile i have android booted under adb
[23:56] <annerajb> koegzist, usually on a shell command if you have things int hat syntax (| | | ) it means choose one
[23:56] <koegzist> o0o0o
[23:56] <annerajb> so you have to choose between cdimage-touch or ubuntu-system or community
[23:56] <koegzist> so on the nexus for what should be choosing?
[23:56] <koegzist> nexus 4***
[23:57] <koegzist> thanks for the help btw
[23:57] <koegzist> :)
[23:58] <annerajb> https://wiki.ubuntu.com/Touch/Install#Step_4_-_Deploying_Image_to_Device
[23:58] <annerajb> it seems you wanna run cdimage-touch
[23:58] <annerajb> thought i am not sure which argument is for your device
[23:58] <koegzist> mako
[23:59] <annerajb> phablet-flash cdimage-touch -d mako -b
[23:59] <annerajb> it seems that's the command you want