[00:13] <alfonsojon> Hi
[00:13] <alfonsojon> Can Ubuntu Touch be compiled to run on an arm v6 processor?
[00:16] <alfonsojon> I feel Ubuntu Touch could be a great success if it could be used to breathe life into older phones
[00:16] <alfonsojon> I have an entry-level Android device from late 2011 and this thing is barely capable once a few apps are installed.
[00:16] <alfonsojon> Is Ubuntu Touch noticably faster than Android 2.3.7?
[00:22] <mhall119> alfonsojon: I've only run it on Android 4.x capable devices, so I'm not sure
[00:23] <mhall119> Ubuntu won't work on armv6 though, it needs v7
[00:24] <alfonsojon> Darn.
[00:24] <alfonsojon> I should save up for a Nexus 4.
[00:24] <alfonsojon> :)
[00:25] <alfonsojon> If I had money, I would contribute to the Ubuntu Touch in a heatbeat
[00:25] <alfonsojon> but, I'm only 16 and failed at applying for a job. so meh.
[00:32] <annerajb> sergiusens, i dont think it's a issue of space added a copy of the touch script on the boot.img and it worked succesfully if i left scripts/touch intact.
[00:41] <annerajb> well ill talk to ogra since apparently if i change one line of scripts/touch it breaks
[00:42] <sergiusens> annerajb: how are you changing it?
[00:42] <sergiusens> that doesn't make sense
[00:43] <annerajb> sergiusens, i tried everything used a sed on the target that compress the boot.img to change it and repack it. now i am copying the complete file from another place and repacking.
[00:43] <annerajb> sergiusens, this is how it looks like now http://paste.ubuntu.com/5983196/
[00:44] <sergiusens> annerajb: so you unpack, modify, repack?
[00:44] <annerajb> yes
[00:44] <sergiusens> annerajb: can you provide a diff from the original?
[00:44] <annerajb> yes
[00:46] <annerajb> sergiusens, on the original i added only line 28 and it worked 70% of the boot's yesterday
[00:46] <annerajb> this one has a bunch of kmsg gime a min for the diff
[00:47] <annerajb> hmmmm
[00:48] <annerajb> sergiusens, http://paste.ubuntu.com/5983206/
[00:50] <annerajb> sergiusens, i got it i am 99999% when i repack it it's missing +x permission
[00:51] <annerajb> not sure how to set the user group for the initrd but ima set it to 777 and see if it works now
[00:57] <sergiusens> annerajb: line 29 you mean?
[00:57] <sergiusens> annerajb: can't you pass in path to init directly instead of modifying?
[00:57] <annerajb> sergiusens, path="/dev/mtdblock3" that I had only that yesterday and it worked all morning and after a while at night it stopped working
[00:57] <annerajb> sergiusens, like a argument?
[00:58] <sergiusens> yeah, something like this https://github.com/janimo/android_device_huawei_u9200/commit/b3f839844fcb996ded1259a31d270236d3081c9c
[00:58] <sergiusens> but with path=
[01:00] <annerajb> sergiusens, i still have to add another change talking to ogra he set that i need to add a sleep before my moutn because apparently udevdm settle is not working no my device
[01:00] <annerajb> that would put me on the same state as yesterday where i have it booting but the moutn fails because it moutns too fast before device is ready
[01:07] <annerajb> sergiusens, and to finish the night here is a booting dmesg with my touch script after formatting /data http://paste.ubuntu.com/5983266/
[01:08] <sergiusens> [    7.255078] VFS: could not find a valid V7 on mtdblock3.
[01:17] <Guest518> i can finally install ubuntu touch on N7
[01:17] <Guest518> but i don't know
[01:18] <Guest518> what is password root ?
[01:19] <mhall119> Guest518: "phablet"
[01:19] <mhall119> is the sudo password for the default Ubuntu Touch user
[01:21] <Guest518> thanks
[01:22] <Guest518> is possible dual os in n7 . android + ubuntu touch
[02:30] <annerajb> sergiusens, the last pastebin i linked worked flawlessly that message appears to be a warning or something because /data was mouetnd and i could write to it and read it (thought it only had the lost+foudn folder)
[02:40] <sergiusens> annerajb: good
[02:40] <sergiusens> plars: if still around (and yeah, I know... :-P) https://code.launchpad.net/~sergiusens/phablet-tools/lp1211708/+merge/180031
[02:40] <annerajb> i just have to figure out why if i copy the rootfs into /data it breaks -_-
[02:41] <annerajb> i been looking at pastebin online and apparently some devices work fine with that message so it may not be a failure. thought somebody is calling kernel_restart
[02:41] <annerajb> Restarting system.
[02:50] <cjohnston> sergiusens: +1 from me on lp1211708 MP
[02:57] <sergiusens> cjohnston: great, if you approve I'll Happrove
[02:58] <cjohnston> Done
[02:58] <sergiusens> ty
[02:58] <cjohnston> I'm not special though :-)
[02:58] <sergiusens> no one should be :-)
[02:58] <cjohnston> heh
[03:00] <sergiusens> thanks for the review!
[03:00] <sergiusens> ah... Day changed... I'm going to bed!
[03:01] <cjohnston> heh. g'nite
[03:01] <sergiusens> night!
[03:37] <bzoltan1> sergiusens: mhall119:  Could you please give me more details on what features the developer mode blocks? You could file bug too :)
[03:52] <mfisch> bzoltan1: I think they're offline, it's late in their timezones
[03:54] <bzoltan1> mfisch: I hope that they will see my answer when they wake up
[03:57] <mfisch> bzoltan1: surely ;)
[03:58] <bzoltan1> mfisch: at least I see them in the list of nicks who are here :)  So it depends on their client... my pidging beeps when somebody mentions my name :)
[04:44] <RaziRazak> Hi All
[04:50] <RaziRazak> Need guide to install ubuntu-touch to my samsung tab 2
[05:23] <RaziRazak> Alo
[05:23] <RaziRazak> Anybody?
[05:29] <cjohnston> RaziRazak: it isn't one of the supported devices. have you looked at the list of community devices?
[05:31] <RaziRazak> Ooo
[05:32] <RaziRazak> So p5100 are not able to be support by ubuntu-touch is it
[05:33] <cjohnston> https://wiki.ubuntu.com/Touch/Install#Supported_devices_and_codenames
[05:33] <RaziRazak> Any future plan to for p5100?
[05:34] <cjohnston> no idea
[05:34] <RAOF> Depends on whether someone wants to port to the p5100
[05:34] <cjohnston> you can see if anyone from the community is working on it
[05:35] <RAOF> RaziRazak: Oh, https://wiki.ubuntu.com/Touch/Devices says that someone's ported to the p5110.
[05:39] <RaziRazak> P5110 is the model without gsm
[05:40] <RaziRazak> P5100 is the model with gsm
[05:45] <RaziRazak> Hi again
[05:46] <RaziRazak> Disconnected just now
[07:28] <tvoss_> sil2100, ping
[07:31] <sil2100> tvoss_: pong
[07:32] <dholbach> good morning
[07:36] <segastep> Good day! :D
[08:01] <sil2100> tvoss_: did anything happen?
[08:02] <tvoss_> sil2100, nope :) can you add ci and autolanding for lp:content-hub?
[08:03] <sil2100> tvoss_: let me take a look
[08:03] <tvoss_> sil2100, thx, the packaging setup is rough to say the least ;)
[08:04] <sil2100> tvoss_: will we be daily releasing it in the nearest future?
[08:05] <tvoss_> sil2100, might well be, yes
[08:09] <RaziRazak> Does aybody know, p5100 can support ubuntu touch or not?
[08:58] <JamesTait> Good morning all, happy Soyuz TM-25 landing day!
[08:58] <segastep> happy what day ? Hello to btw :D
[09:03] <tvoss_> didrocks, https://code.launchpad.net/~thomas-voss/location-service/upstart/+merge/180068
[09:03] <didrocks> sil2100: mind having a look? ^
[09:04] <sil2100> didrocks, tvoss_: looking
[09:04] <tvoss_> sil2100, great, thx
[09:13] <sil2100> tvoss_: looks ok and builds ok, approved
[09:19] <tvoss_> sil2100, thx
[09:21]  * tvoss_ wonders why the phone is taking 25% RAM on the phone
[09:22] <N33Q> hey is there some way to sync ubuntu touch with windows pc to transfer some data on nexus 4?
[09:24] <ogra_> N33Q, you can use adb push ... or install openssh-server on the phone and use scp/sftp
[09:24] <ogra_> (teh latter via network indeed)
[09:25] <ogra_> tvoss_, because its a phone ?
[09:25]  * ogra_ would prefer if the phone took 100% of ram on the phone :P
[09:26] <ogra_> asac, new image is testing ... FYI
[09:26] <asac> ogra_: i suspect we wont be happy though
[09:26] <ogra_> well, its looking good so far
[09:26] <asac> we have two runaway processes still ... unity8 and whoopsie :)
[09:26] <ogra_> 40 of 40 tests green
[09:26] <asac> yeah... lets hope for a bit of luck i guess
[09:27] <ogra_> oh, whoopsie is still not fixed ?
[09:27] <asac> not sure... didnt see people dancing, so i assumed not
[09:27] <asac> https://bugs.launchpad.net/touch-preview-images/+bug/1211417
[09:27] <asac> ev: news? :)
[09:27] <ev> ogra_: what image is this with?
[09:27] <asac> ev: can we disable it?
[09:28] <ogra_> ev, no image, the tests just started and look all good ... but asac expects us to hit a 100% cpu issue again
[09:28] <asac> or should we kick it out?
[09:28] <asac> ogra_: well, both unity8 and whoopsie have known looping bugs that happen eventually. we have to be very lucky :)
[09:28] <ev> well I'd prefer we see if it's still broken in the tests before we do something drastic like kicking it out
[09:29] <ogra_> ++
[09:29] <asac> people suspect its the part the blocks our images from passsing tests
[09:31] <ev> I've been hammering at it with valgrind and splint all morning. Found some minor niggles, but nothing that would point at memory corruption yet. I haven't been able to reproduce it with the latest phablet-flash cdimage-touch --pending yet, but if I can get it to appear, I'll try downgrading whoopsie to see if that resolves it
[09:31] <ev> I'll have another look at the syslog code, as that's the only big change we've made in quite a while
[09:33] <asac> still i would like to know how we can disable it or if the package has to go out in case we still have a non-green baseline today
[09:34] <ogra_> in /etc/default/whoopsie i'd guess
[09:34] <ogra_> or by overriding the upstart job from another package
[09:34] <asac> ogra_: can we do that without uploading whoopsie itself?
[09:34] <ogra_> the latter, yes
[09:35] <asac> like in an override logic we do during image production?
[09:35] <asac> ok
[09:35] <asac> lets see what happens
[09:35] <ogra_> echo manual >/etc/init/whoopsie.override
[09:35] <ogra_> thats all thats needed
[09:35] <asac> ogra_: curious, where would we put such code?
[09:36] <asac> in another package? or in some image production scripts?
[09:36] <ev> yeah, disabling the job is probably preferable as it wont mess with user's configuration
[09:36] <ogra_> well, since lxc-android-config carries many such things (though all container related) i would put it there too ... since it is definitely temporary anyway
[09:36] <asac> ok, but that requires a full package build etc.
[09:37] <ogra_> but we can also do it at image production from livecd-rootfs
[09:37] <ogra_> everything does
[09:38] <ogra_> all bits that can make changes at that level of an image build are in packages
[09:38] <ogra_> so an upload is unavlidable ... .
[09:38] <ogra_> *unavoidable
[09:40] <asac> ogra_: so image production logic is in packages itself?
[09:40] <asac> no bzr branch ? :)
[09:40] <ogra_> sure, there are bzr upstream braches for the packages :)
[09:41] <asac> hehe
[09:41] <asac> you know what i meant
[09:41] <ogra_> bur yeah, rootfs creation is all in packages
[09:41] <asac> so no
[09:41] <asac> kk
[09:41] <ogra_> image publishing and the whole build management as well as pre and post mangling are in cdimage and not packaged
[09:41] <ogra_> but the build itself uses packaged bits
[09:46] <ogra_> asac, did cypher and chicken talk to you about the bluetooth and indicator changes ?
[09:46] <mpt> didrocks, you can subscribe to <https://wiki.ubuntu.com/SoftwareUpdates> to be notified of revisions. The downside is that you'll be notified of revisions to PC-only parts as well.
[09:46] <didrocks> mpt: do you update it so often?
[09:46] <didrocks> (like should I be scared about the spam? ;)
[09:48] <mpt> didrocks, <https://wiki.ubuntu.com/SoftwareUpdates?action=info> ... it varies. 24 times this month, once last month, not at all in June.
[09:48] <didrocks> mpt: ok, so should be fine, subscribing
[10:01] <annerajb> ogra_, does scripts/touch has some sort of crc??
[10:02] <annerajb> if i modify a line on it. it breaks. at first i thought it was space but i could copy the whole file and it woudnt break as long as i didnt modify the touch script.
[10:02] <annerajb> weird part is that if i modify the touch script. and it's breaking it "works" as soon as i format /data
[10:07] <davmor2> morning all
[10:07] <ogra_> no, there is no hashsum or anything
[10:09] <annerajb> ogra_, well then something really mess up is hiding in my initrd lol. I thought it was permission when repacking it since i never see any of the prinouts of my touch script when it fails just the watchdog.
[10:11] <ogra_> well, it could be that your boot.img gets to big for the partition
[10:11] <ogra_> have you checked that ?
[10:11] <ogra_> (then it might go corrupt on flashing)
[10:12] <annerajb> ogra_, i thought about it that's why i copied the touch script with another name to the boot.img root and it worked fine
[10:13] <annerajb> so i have two touch image files. I also removed lines from the touch/script to see if the smaller size would help (removed the stuff that dosnt work on my cellphone like the find dev)
[10:16] <ogra_> btw, did you try putting path=/dev/.... on your kernel cmdline ?
[10:16] <ogra_> and not editing the script
[10:17] <annerajb> wasnt that not implemented yet and sergiusens was going to work on it?
[10:18] <ogra_> no, i'm going to work on it, but it might already work
[10:18] <ogra_> iirc the kernel exports all cmdline args to the environment ...
[10:18] <ogra_> i'm not sure if it gets handed through to the tough script though
[10:19] <ogra_> but i think it would be owrth to try
[10:19] <ogra_> (though that doesnt fix the sleep issue i guess)
[10:20] <annerajb> ogra_, yeah i can try it it still makes me want to know why is this happening when i modify the script because if i made the script smaller same thing happened and that rules out space which was the only thing worrying me.
[10:20] <annerajb> anyway how do you pass the cmdline args??
[10:21] <ogra_> abootimg -i /path/to/boot.img | grep cmdline
[10:21] <ogra_> first check if there is an existing one
[10:21] <ogra_> then:
[10:22] <ogra_> abootimg -u /path/to/boot.img -c "cmdline=<old cmdline> <your addition>"
[10:22] <annerajb> this is a samsung device abootimg dosnt work
[10:22] <annerajb> boot.img: no Android Magic Value
[10:22] <annerajb> boot.img: not a valid Android Boot Image.
[10:26] <ogra_> oh, then you need to look in your BoardConfig.mk i think
[10:27] <annerajb> BOARD_KERNEL_CMDLINE := console=ttyFIQ0,115200 init=/init no_console_suspend
[10:27] <annerajb> is that no_console_suspend desired?
[10:27] <annerajb> i read on the flipped page about console having to be on or something
[10:30] <ogra_> nah, thats fine
[10:30] <ogra_> so just add a path= there
[10:30] <ogra_> wow, that init=/init is evil ... what a luck ubuntu initrd uses /init by default
[10:31] <ogra_> (usually the kernel would iterate over several locations, that option forces it to only accept /init)
[10:36] <annerajb> ogra_, all right i am building it again it's still using the heavily modified touch script thought.
[10:37] <Oroku_Saki> still building cm-10.1...
[10:38] <Oroku_Saki> my source for cm-10.1 builds fine in UT.. does not with the actual cm-10.1... how funny is that.. I have to cherry pick a patch
[10:39] <Oroku_Saki> for tinyalsa.. I guess that is why
[10:41] <ev> asac, ogra_: what's the jenkins job that was failing due to whoopsie hitting 100% CPU? I'd like to keep an eye on it, rather than waiting for people to come to me.
[10:42] <asac> ev: we dont see it in jenkins yet'
[10:42] <ev> oh right
[10:42] <ev> I thought that's how all this started
[10:42] <asac> ev: it came out of investigations because we saw flakiness... we are about to land a test that ensures the system calms down
[10:42] <asac> that will reveal that
[10:42]  * ev nods
[10:42] <asac> so folks see it locally by just rebooting mako
[10:43] <asac> ev: the test that triggered us looking for sources of noise, is still failing
[10:43] <asac> on mako
[10:43] <asac> which might indicate that its still there
[10:44] <ev> asac: I take it someone is digging to find out definitively?
[10:44] <asac> ev: well, the looping whoopsie is a bug on its own
[10:44] <asac> people are digging in the dark
[10:44] <ev> looping?
[10:44] <asac> the more we can rule out the better
[10:44] <ev> I noticed you referred to it as such before
[10:44] <ev> how is it looping?
[10:45] <asac> ev: that it consumes 100%
[10:45] <ev> oh that bit, right
[10:45] <ogra_> asac, did the testers make sure it isnt upowerd that misbehaves as usual ... and whoopsie only being fallout of that ?
[10:46] <ev> sure, I'm just not yet convinced that it's in whoopsie. valgrind didn't surface anything and I'm not able to as yet reproduce it on the latest proposed mako image
[10:46] <ogra_> (i.e. are you sure whoopsie is the only process at 100%)
[10:46] <asac> ev: but you could reproduce
[10:46] <ev> asac: I was able to briefly reproduce it with the previous proposed image
[10:46] <asac> sure thats enough
[10:46] <ogra_> bug 1190792 has often misled us before
[10:47] <asac> ogra_: but we would see ueventd also going high on top
[10:47] <asac> that wasnt observed from what i remember
[10:47] <ev> ueventd is chewing away at 100% cpu on mine, for what it's worht
[10:47] <ogra_> yes
[10:47] <asac> not saying its not related
[10:47] <ogra_> ev reboot
[10:47] <popey> on my mako when it first showed a high whoopsie cpu, it also had a powerd crash in /var/crash..
[10:47] <asac> what is a problem are those looping things. thats a super grave bug

[10:47] <asac> if you think in the phone context
[10:48] <ogra_> processing .crash files perhaps ?
[10:48] <asac> and the fact that it makes our autopilot tests more flaki (due to UI tests being async with timeouts etc.), doesnt make it less severe :-P
[10:48] <asac> popey: ok powerd crash can explain that
[10:48] <asac> thanks
[10:48] <asac> popey: can you still reproduce?
[10:49] <popey> no, trying
[10:49] <asac> ok good. do you see ueventd?
[10:49] <popey> it didnt happen with todays flash
[10:49] <popey> flashing at the moment
[10:49] <asac> cool.
[10:49] <ogra_> asac, everyone sees ueventd every other boot
[10:50] <asac> guess that will be visible with the settle test then as well :)
[10:50] <asac> i dont see it on maguro
[10:50] <popey> yeah, i have a machine with ueventd at 100% now
[10:50] <popey> but no whoopsie
[10:50] <ogra_> we have reduced the racyness as much as we could, buut the real fix waits for an upstart upload
[10:50] <asac> for me its unity8 keeping my thing hot :)
[10:51] <ogra_> asac, eaxctly, maguro is a lot slower
[10:51] <asac> ogra_: where is that upstart upload?
[10:51] <asac> so we have a fix?
[10:51] <ogra_> so it doesnt see the race trhat often
[10:51] <asac> ogra_: ueventd goes crazy right after boot?
[10:51] <ogra_> asac, the fix is an upstart bridge into the container ... jodh is at debconf so i doubt we'll see it landing this week
[10:52] <ogra_> ueventd goes crazy if udev tries to do something with devices while ueventd hasnt finished yet
[10:52] <ogra_> we need the equivalent of "udevadm settle" for ueventd
[10:52] <asac> ogra_: its a start race condition?
[10:53] <ogra_> which the upstart bridge is supposed to provide
[10:53] <ogra_> yes
[10:53] <asac> ok, so we will see ueventd rumbling right after boot.. thats good
[10:53] <ogra_> only happens on startup and more often on mako
[10:53] <ogra_> but it persists until reboot
[10:53] <asac> righ
[10:53] <asac> t
[10:54] <asac> thats good. adding my test to default will then show runs clearly that suffer from this effect
[10:54] <ogra_> right
[10:54] <asac> and we can retry the test until we hit a boot where we dont see that before we can take any results for serious
[10:55] <ogra_> well, dont the tests all reboot the device before starting ?
[10:55] <ogra_> or does that only happen once ?
[10:55]  * ogra_ thought they use reboot to gain a clean state 
[10:55] <ogra_> so you would have to hook into each tests separately if thats the case
[10:55] <ogra_> *each test
[10:56] <popey> so i just clean flashed and I have a powerd crashdump in /var/crash
[10:56] <ogra_> yeah, powerd needs  to wait for the android event
[10:56]  * ev lunches
[10:57] <ogra_> it accesses the sensorservice ... which it only can after the container is up
[10:57] <asac> ogra_: no ... we run multiple tests in one boot sequence... the reboots are not nicely marked in the dashboard
[10:57] <ogra_> (currently it comes up with dbus ... thats to early, so it crashes until the proximity sensor is there)
[10:58] <asac> i want them to run the default test suite after each boot
[10:58] <asac> and dont continue if that fails
[10:58] <popey> wow, you get quite a few apparmor_parser processes just after boot.. is that one per app?
[10:58] <asac> rather reboot
[10:58] <annerajb> ogra_, the command line parameter was never passed off
[10:58] <annerajb> # cat /proc/cmdline
[10:58] <annerajb> console=ttyFIQ0 no_console_suspend=1 androidboot.serialno=39
[10:58] <ogra_> popey, i think it processes the policy files once on first boot
[10:59] <ogra_> annerajb, check your kernel config, probably it comes from there instead ...
[10:59] <annerajb> ok
[10:59] <popey> ogra_: whats the process for working around the ueventd issue? kill it?
[10:59] <asac> ogra_: DEITY just send us an image from the future :)
[10:59] <ogra_> asac, so my theory is ... powerd dies  (on purpose atm) ... produces a crash file ... whoopsie sees the file and processes it ... which takes 100% cpu
[11:00] <asac> 20130816 touch_ro mako
[11:00] <ogra_> haha
[11:00] <asac> maybe that will show us what we need to change in order to fix it?
[11:00] <asac> :)
[11:00] <ev> ogra_: I've had plenty of powerd crashes on my mako
[11:00] <ev> without it chewing away at 100% cpu
[11:00] <ogra_> hard to compare ... we need to disassemble it :)
[11:00] <ev> basically one every boot :)
[11:00] <ev> right, lunch for reals
[11:00] <asac> ogra_: yeah. thats fine if its that way
[11:00] <ogra_> ev, well, that at least proves my theory of powerd dieing on every boot :)
[11:01] <asac> but we could in testing maybe disable whoopsie and run it explicitely in a more controlled manner at the end
[11:01] <asac> ev: i guess there is a way to stop whoopsie and then run it explicitely once to scrape all .crash files?
[11:03] <asac> ogra_: so that image is scary ... where is a clock offset?
[11:03] <asac> on our image builders? i guess it uses what is in this media-info thing
[11:03] <ogra_> dunno, probably on system-image.ubuntu.com ?
[11:04] <ogra_> media-info isnt touched on system-image images
[11:04] <ogra_> but it provides its own additional stamp on top
[11:04] <asac> yeah whatever that is then
[11:04] <ogra_> (now dont ask me where :P)
[11:08] <asac> ogra_: so flakiness confirmed :)
[11:08] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/image/3512/
[11:08] <asac> Saviq: ^^ :-P
[11:09] <Saviq> asac, told 'ya! :P
[11:09] <asac> ogra_: is there anything else we could do to avoid this ueventd issue until it lands?
[11:09] <Saviq> asac, although it might be that *something* made it worse, for sure
[11:09] <asac> Saviq: yeah no more annoyance for at least 16h :)
[11:09] <asac> Saviq: i am confident that mterry can nail it down if we dont let it go :)
[11:09] <ogra_> https://code.launchpad.net/~ogra/powerd/fix-semsor-race/+merge/180095
[11:10] <asac> at least give us confidence on what is going on
[11:10] <Saviq> yeah
[11:10] <ogra_> asac, no, we cant do much more for ueventd
[11:10] <asac> ogra_: nothing hacky wacky?
[11:10] <dednick> i need to sort out some dependencies for the ubuntu-touch package. It depends on chewie (netowork + sound indicator backends). We need to remove this dependency, but ensure that chewie is still installed on phone for now.
[11:10] <asac> given we have understood the problem and the real fix is coming its a valid approach imo
[11:10] <ogra_> you can add even more sleeps but i doubt that will fix much
[11:11] <ogra_> (and it adds to the boot time indeed)
[11:13] <dednick> i think we need to move chewie from core see to shell seed ?
[11:13] <ogra_> sforshee, mfisch, can one of you approve https://code.launchpad.net/~ogra/powerd/fix-semsor-race/+merge/180095
[11:13] <dednick> or something...
[11:14] <ogra_> dednick, we dont have such a differentiation in the seeds
[11:14] <ogra_> there is just touch and adk
[11:14] <ogra_> *sdk
[11:14] <dednick> ogra_: but there is diff between recommend and depends?
[11:15] <ogra_> dednick, no, we fully suppress recommends ... whats not seeded or a hard dep isnt in
[11:16]  * ogra_ hopes we can clean that up at least for 14.04 
[11:16] <annerajb> ogra_, the kernel had the argument in the config
[11:17] <dednick> sigh, do there's no way we can remove chewie
[11:17] <ogra_> dednick, i think the plan is to remove it soon, but the indicator porting work isnt fully done as i understand
[11:17] <ogra_> annerajb, so try changing it there then :)
[11:18] <dednick> ogra_: yeah, i was hoping we could remove it as a dependency, indicator-network removes chewie... bit of a ballsup.
[11:18] <annerajb> yeah already flashing it
[11:18] <dednick> ogra_: nevermind. will just sort out dep of network then
[11:18] <ogra_> dednick, https://code.launchpad.net/~mathieu-tl/ubuntu-seeds/ubuntu-touch.chewie/+merge/179937
[11:19] <ogra_> dednick, but that will cause regressions until all indicator work is done
[11:19] <dednick> ogra_: ah, ok. thanks.
[11:19] <ogra_> so we either needs approval from asac to allow such a regression (and someone t explain what actually regresses) or we need to wait
[11:21] <asac> my understanding is that indicators will start landing later this week one by one
[11:21] <dednick> ogra_: no, it's ok. i just wanted the ability to install indicator-network for testing, but it conflicts with chewie, so it makes life a bit hard.
[11:21] <asac> i have no idea what this chewie thing would fix us
[11:21] <asac> dednick: can you remove it locally?
[11:21] <ogra_> asac, chewie is the current backend for the current indicators
[11:21] <dednick> asac: with a bit of effort
[11:30] <annerajb> ogra_, it didnt work even thought cat /proc/cmdline shows it there it dosnt seem to get pass to the touch script (or it get's overwritten
[11:31] <ogra_> right
[11:31] <ogra_> i'll try to add a cmdline parser to the script later today
[11:31] <ogra_> to actually fix that open bug
[11:32] <annerajb> ogra_, thanks
[11:32] <annerajb> ima head to work later
[12:09] <sil2100> tvoss_: hmm, do you know why suddenly something from the platform stack wants to pull in libgles2-mesa on the desktop?
[12:09] <sil2100> tvoss_: I mean, do you know of any change that might have resulted with such a change?
[12:09] <tvoss_> sil2100, nope, would need to investigate, too
[12:20] <annerajb> ogra_, let me know when you have the merge so i can pull the diff from it :D
[12:26] <didrocks> sil2100: you have the reason for the "something"
[12:27] <didrocks> /var/log/upstart/otto-setup.log:   Installing libgles2-mesa as Depends of libmirplatform
[12:28] <didrocks> sil2100: I think we don't have libmirplatform installed as well on the desktop, so need to refresh the dependency list ^
[12:28] <sil2100> didrocks: oh, indeed, I didn't know we had such a nifty logging in otto!
[12:28] <sil2100> I mean, forgot about that
[12:29] <sil2100> didrocks: libmirplatform is in the list already btw.
[12:31] <sil2100> didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/add_libmirplatform_extra/+merge/180120
[12:32] <sil2100> didrocks: as for HUD - the manual publishing needs to be held, since the changelog entry in that packaging diff looked wrong, so I edited that
[12:32] <sil2100> didrocks: also, will have to see if we won't have to release unity-lens-apps in the same time with the new libcolumbus bindings
[12:37] <didrocks> sil2100: approved
[12:37] <sil2100> didrocks: thanks
[12:37] <didrocks> yw
[12:56] <sergiusens> sil2100: can you add this to your list for daily release? https://code.launchpad.net/~sergiusens/cupstream2distro-config/unity-mir/+merge/179983 ricmm should be able to answer questions, by the name you can guess what it's for ;-)
[12:56] <sergiusens> sil2100: greyback as well
[12:56] <sergiusens> fginther: reping on ^^
[12:57] <greyback> sergiusens: ack
[12:57] <sil2100> sergiusens: we were just discussing that in -desktop ;)
[12:57] <sil2100> sergiusens: perfect timing
[12:57] <sil2100> sergiusens: so, could you make one small modification there?
[12:58] <sergiusens> sil2100: as many as you want
[12:58] <sil2100> sergiusens: ah! Scratch that, it's fine as it is ;)
[12:59] <sergiusens> sil2100: my only doubt was if I should put it in the mir or unity stack, but since it's glue code for unity to talk to mir, the unity stack felt like the right place to be
[12:59] <sil2100> sergiusens: I'll poke now Francis to prepare all the CI bits
[12:59] <sil2100> sergiusens: I had the same thing, but I personally wanted it in platform
[13:00] <sil2100> sergiusens: but unity8 seems like the right place - the unity8 guys are upstream for it, so I guess it's more sane this way
[13:00] <sergiusens> sil2100: yeah, I had that one in mind too, but then mir should also be in platform (personal opinion)
[13:00] <sil2100> Makes sense
[13:02] <fginther> seb128, ack
[13:05] <didrocks> hum
[13:05] <didrocks> the thing is that the API of Mir is unstable
[13:05] <didrocks> not sure if it's using the server or client one
[13:05] <didrocks> but the server one is ABI unstable
[13:06] <didrocks> I hope the unity-mir API is stable at least?
[13:07] <Saviq> we've passed $10M! :)
[13:07] <ogra_> ++
[13:07] <fginther> sergiusens, one comment
[13:07] <ogra_> only 22 to go
[13:08] <sil2100> sergiusens: ^
[13:09]  * sergiusens fixes
[13:09] <sergiusens> fginther: should that be the default hook?
[13:09] <sergiusens> fginther: I will remove the hook line completely
[13:09] <fginther> sergiusens, that would work
[13:11] <sergiusens> fginther: hmmm, check license headers is not in the default hook, want me to set that?
[13:11] <fginther> sergiusens, yes, that works for this stack
[13:11] <sergiusens> fginther: if projects don't comply, they should start fixing it
[13:13] <sil2100> sergiusens: your branch got merged btw ;/
[13:13] <sil2100> sergiusens: so you'll have to fix it in a separate one
[13:13] <sergiusens> sil2100: how did that happen?
[13:13] <sergiusens> oh, ic
[13:13] <sergiusens> no worries
[13:14] <fginther> sergiusens, argh I must have not flipped the state right
[13:14] <ogra_> sounds like some american lawyer trick
[13:14] <ogra_> "flipping the state right"
[13:15] <fginther> just requires the right amount of $$
[13:15] <ogra_> heh
[13:15] <sergiusens> ogra_: my chromebook is on precise again, blazing fast, rock solid!
[13:15] <ogra_> sergiusens, haha, raring isnt bad either :)
[13:15] <sergiusens> ogra_: but I get fast unity2d :-)
[13:16] <ogra_> sergiusens, we just need to get the Mir guys to make Mir work without the android crap and should get XMir o saucy
[13:16] <ogra_> *on
[13:16] <sergiusens> ogra_: with which drivers are you aiming for? :-)
[13:17] <ogra_> mali
[13:17] <sergiusens> desiring would be a better word
[13:17] <sergiusens> fginther: https://code.launchpad.net/~sergiusens/cupstream2distro-config/unity-mir/+merge/180129
[13:17] <ogra_> the ones i use with the compiz unity on raring atm
[13:18]  * ogra_ uses the manta drivers on his chromebook
[13:18] <sergiusens> ogra_: which would be similar to building this: https://github.com/hrw/chromebook-mali-driver
[13:18] <sergiusens> oh, the manta ones, I have no idea where the ones in that git repo come from
[13:18] <sergiusens> oh, they are the google ones
[13:18] <ogra_> i think copied out of the chromeos rootfs
[13:19] <sergiusens> ogra_: from http://commondatastorage.googleapis.com/chromeos-localmirror/distfiles/mali-drivers-0.45-r96.run
[13:19] <ogra_> anyway, the mantra drivers work fine
[13:19] <ogra_> *manta
[13:19]  * sergiusens needs to try that again
[13:20] <ogra_> but according to tvoss_ there is no way to do gralloc stuff without hybris
[13:20] <ogra_> and there is no android port to the chromebook that i know of
[13:20] <tmoenicke_> mzanetti: ping
[13:21] <fginther> sergiusens, thanks
[13:21] <mzanetti> tmoenicke_: pong
[13:23] <sil2100> fginther: in the meantime...
[13:25] <sil2100> fginther: we added to the platform stack a new project, content-hud, which would need CI and merger prepared
[13:25] <sil2100> fginther: it's daily_release: False now, but will be released in the nearest future
[13:26] <fginther> sil2100, ack, when sergio's merge is finished, I'll deploy all the updates
[13:27] <sil2100> fginther: excellent :) THanks!
[13:31] <tvoss_> ogra_, except for if you have drivers implementing the android HAL (i.e., the interfaces in gralloc.h) compiled against glibc
[13:31] <ogra_> well, i dont ...
[13:31] <plars> balloons: weather app appears to still be failing bad, but getting 1 test passed at least
[13:32] <ogra_> but the android mali drivers work with compiz here
[13:32] <ogra_> without issues
[13:32] <sergiusens> ogra_: you can always fall back to the chromebook ones just in case...
[13:32] <ogra_> yeah
[13:32] <sergiusens> point should be moot thee
[13:32] <sergiusens> *there
[13:32] <ogra_> but i doubt they use gralloc
[13:37] <ogra_> annerajb, http://paste.ubuntu.com/5985004/
[13:42] <annerajb> ogra_, thx ill give it a try later
[13:42] <sergiusens> annerajb: do you still need that sleep?
[13:43] <davmor2> ogra_: what the...... http://reports.qa.ubuntu.com/smokeng/ you're making builds 2 days in the future now what????
[13:43] <ogra_> sergiusens, looks like his flash controller operates slow on start
[13:44] <annerajb> sergiusens, i probably do still need it
[13:44] <ogra_> davmor2, yeah, asac wanted to be able to backport the fixes from friday so we decided to build fridays image in advance
[13:44] <annerajb> but talking to ogra_ yesterday udevdam settle should handle that
[13:45] <sergiusens> ogra_: retroactive bug fixing?
[13:46] <ogra_> sergiusens, pro-retroactive bugfixing indeed :)
[13:46] <ikillcypher> sergiusens, and ogra_ :)
[13:46]  * davmor2 begins to wonder if asac and ogra_ are the new Doctor and his companion with their timey wimey shenanigans 
[13:46] <ikillcypher> looks like ubuntu-touch will be coming to xperia z soon ;)
[13:46] <ikillcypher> bunching 1 hour with no errors yet
[13:47] <annerajb> ikillcypher, :D
[13:47] <ogra_> congrats
[13:47] <ikillcypher> thanks to mamenyaka
[13:47] <ogra_> davmor2, but honestly, that looks like brakage in stgraber's playground
[13:54] <mfisch> ogra_: cool, the sensor is emitting the event now I guess. Thanks for fixing that
[13:54] <ikillcypher> FAILED :(
[13:54] <ikillcypher> OH NO
[13:54] <ikillcypher> cc1plus: all warnings being treated as errors
[13:55] <ikillcypher> home/ikillcypher/xperiatouch/out/target/product/yuga/obj/KERNEL_OBJ/usr/include/video/msm_hdmi_modes.h:214:43: error: narrowing conversion of 'i' from 'int' to 'uint32_t {aka unsigned int}' inside { } is ill-formed in C++11 [-Werror=narrowing]
[13:55] <ogra_> mfisch, np, i was looking for the reason the sensorservice races sometimes for weeks ... luckily sforshee poinyted out that powerd treis to access the proximity sensor
[13:55] <cjohnston> davmor2 sergiusens ogra_, is there a way to get the YYYYMMDD.X build number on an upgrade? essentially what you are seeing there with the build being in the future is that adb shell system-image-cli -b gives the 'version' number, and media-info has the original build number that was installed..
[13:55] <cjohnston> We need a way to get the upgraded build (YYYYMMDD.X) build number instead of the version number
[13:56] <ogra_> cjohnston, ah, yeah, system-image images use their own stamp ... you should read that instead and use media-info for the initial install media info
[13:56] <ogra_> now dont ask me where that stamp lives :P
[13:57] <cjohnston> ogra_: this is checking though to see if the install was upgraded.. So if you started on 20130808 and upgraded to today's build. media-info would still show 20130808
[13:57] <ogra_> yes
[13:58] <ogra_> media-info never changes
[13:58] <ogra_> but there is a separate stamp file the system-image images use
[13:58] <ev> ogra_: any idea if we're still seeing whoopsie at 100% CPU in the lab, even with the latest test?
[13:58] <ikillcypher> ogra_,
[13:58] <ikillcypher> http://pastie.org/private/3rydde6mpycywz54rwchg
[13:58] <ikillcypher> any idea how to fix this
[13:58] <ogra_> ev, nope, ask someone who is near the lab ... i.e. plars
[13:58] <ev> plars: oh hai
[13:59] <cjohnston> ev: we were yesterday
[13:59] <cjohnston> not sure about today
[13:59] <ev> cjohnston: yesterday was a very different day :)
[13:59] <ev> I saw it with yesterday's bits too, just not today's
[13:59] <plars> ev: I am nowhere near the lab, but yes we are
[13:59] <ikillcypher> :'( my errors guys ??
[14:00] <ev> plars: who can I talk to for more information?
[14:00] <plars> ev: me
[14:00] <ev> :)
[14:00] <plars> ev: though I'm not sure I have too much more than you already have, I'm a bit confused that you are not able to reproduce it as easily
[14:00] <plars> ev: for the rest of us, it's hit or miss, but rebooting the phone once or twice should see it for sure
[14:01] <plars> ev: I'm flashing the latest image on my phone locally
[14:01] <ev> plars:  phablet-flash cdimage-touch --pending ?
[14:01] <plars> ev: yes
[14:02] <ogra_> ikillcypher, how often did you try googling it before asking us ? :) ... this is all device specific failures ... either related to the compiler defaults (-Werror) or caused by a config option in your kernel
[14:02] <ikillcypher> ok
[14:02] <ikillcypher> :(
[14:03] <plars> ev: we also have https://bugs.launchpad.net/touch-preview-images/+bug/1190792 that describes eventd doing the same thing to us at time
[14:03] <plars> s
[14:03] <ev> plars: is there anything special you're doing after flashing? Is wifi on?
[14:03] <ogra_> ikillcypher, try to do some research yourself first :)
[14:03] <ogra_> plars, are we 100% sure the whoopsie thing isnt just fallout of ueventd ?
[14:03] <plars> ev: yes, it's flashing, then setting up wifi right away
[14:04] <plars> ogra_: no idea, but that's why I mentioned it to ev just now
[14:04] <mhall119> bzoltan: what do you mean "what features the developer mode blocks"?
[14:04] <ev> ogra_: just trying to find the source to have a look :)
[14:04] <mhall119> do you mean what's blocked when developer mode isn't enabled?
[14:05] <Oroku_Saki> compiling cm-10.1 with 3.0.8.. the real cyanogenmod with android.. mainly to verify I get a screen. Then try again with ubuntu touch
[14:05] <Oroku_Saki> Anyone know a current kernel config for say, mako with ubuntu touch
[14:06] <Oroku_Saki> I looked at phablet git sources, but they all had _NZ set for not used
[14:06] <ogra_> ev, of ueventd ?
[14:06] <ogra_> ev, thats on phablet.ubuntu.com in the gigantic git tree ... or in the android package in saucy
[14:07] <ev> whoop
[14:07] <Oroku_Saki> I brunched mako, and the kernel folder is not there.. prebuild kernel?
[14:07] <bzoltan> mhall119: yes
[14:08] <bzoltan> mhall119: I am going to cut the developer mode to pieces: 1. application development mode 2. platform development mode
[14:08] <mhall119> application developer mode is the same as normal user mode, AFAIK
[14:08] <Oroku_Saki> nevermind, found it
[14:08] <didrocks> barry: if you have any question before my EOD on the wiki rewrite, do not hesitate :)
[14:09] <barry> didrocks: thanks!  and great meeting
[14:09] <didrocks> barry: I hope you won't need any medecine in rereading the etherpad ;)
[14:11] <barry> :)
[14:11] <bzoltan> mhall119:  except it needs ssh access
[14:12] <mhall119> ah, right, and openssh isn't installed by default, and not installable unless you're in platform developer mode
[14:12] <mhall119> bzoltan: can QtCreator's plugin use adb shell instead of ssh?
[14:14] <ogra_> mhall119, that wont be open forever either
[14:15] <Oroku_Saki> kernel requirements for lxc The requirement of kernel config is listing in http://lxc.teegra.net/
[14:15] <ogra_> i would say if you devellop on/with the device ... we expect the device to be in developer mode
[14:15] <Oroku_Saki> hmmm LXC has been in the mainstream kernel since 2.6.29 but there are several configuration options that need to be set so that it can be used.
[14:16] <Oroku_Saki> app armor was put in around 2.6.36 or so, seccomp should be enabled, and cgroups of course
[14:16] <Oroku_Saki> good info
[14:16] <Oroku_Saki> fanotify the same, I was told 2.6.36 is basically a test of new features that are put into the beginning of 3.0 kernel
[14:16] <pmcgowan> mhall119, I generally use the command line to avoid the full developer download, bzoltan going to fix it
[14:18] <Oroku_Saki> AppArmor, seccomp and cgroup confinement consistently to all apps... http://loco.ubuntu.com/planet/592-may-2013-ubuntu-developer-summit-summary/
[14:18] <ikillcypher> haix
[14:18] <ikillcypher> changed int to uint32_t
[14:24] <korda> bom dia
[14:37] <popey> 50
[14:37] <popey> bah
[14:37] <ogra_> 60?
[14:38] <annerajb> ogra_, reboot loop now
[14:38] <bobweaver> 69 ?
[14:38] <ogra_> annerajb, great
[14:38] <ogra_> annerajb, can you get into recovery without powering down ?
[14:38] <annerajb> how?
[14:38] <ogra_> so that you can check /proc/last_kmsg
[14:39] <ogra_> holding the right buttons to get into recovery
[14:39] <ogra_> while it reboots
[14:39] <annerajb> the same way you usually get into recovery?
[14:39] <ogra_> yeah
[14:39] <ogra_> just make sure you dont powerd down ...
[14:39] <ogra_> else the ram console gets flushed
[14:40] <ogra_> (and /proc/last_kmsg would be empty)
[14:40] <annerajb> hmm cant seen to get into recovery -_-
[14:40] <ogra_> annerajb, argh ... there is a typo in the snippet
[14:40] <annerajb> *angry fist*
[14:42] <ogra_> annerajb, there is a ;; missing
[14:43] <ogra_> between line 30 and 31 in the paste
[14:45] <annerajb> all right building another boot.img
[14:47] <annerajb> ogra_, i seem to be having trouble getting into recovery now any ideas why?
[14:48] <ogra_> nope
[14:52] <pmcgowan> ChickenCutlass, do I need to enter a bug on the volume control?
[14:52] <ChickenCutlass> pmcgowan, I guess.  it works from command line.  Not sure why it broke
[14:52] <ChickenCutlass> pmcgowan, need the new indicators anyway
[14:53] <pmcgowan> ChickenCutlass, strange, what handles the button?
[14:53] <ChickenCutlass> pmcgowan, I beleive the server -- chewie or something
[14:53] <pmcgowan> ChickenCutlass, ok so same issue, if sound indicator is landing can wait for that
[14:53] <ChickenCutlass> pmcgowan, right
[14:55] <bzoltan> mhall119:  for sure it can... but keep in mind that adb needs physically connected device ... and my plan is to give development access via usb/wlan too
[14:57] <sergiusens> bzoltan: you will need to do that thinking abuot image based upgrades and read only filesystems
[14:57] <sergiusens> and the fact that adb root will go away, as ogra_ mentioned
[15:10] <mhall119> bzoltan: is the .desktop fix for the QtCreator click package creation in saucy?
[15:11] <beuno> mhall119, o/
[15:11] <beuno> also, wow this is a lot of people here
[15:11] <mhall119> beuno: bzoltan: so we need the QtCreator click creation fixed before we get people using the new MyApps
[15:11] <tedg> beuno, But now that you're here, it is complete.
[15:12] <beuno> that's like twice as scary
[15:12] <sergiusens> beuno: welcome to the high traffic channel
[15:12] <sergiusens> almost as much as #ubuntu :-P
[15:12]  * beuno already regretted joining
[15:13] <balloons> is anyone else having trouble with phablet-test-run? It's not running things on my manta
[15:13] <gatox> mhall119, hi, just to tell you about it, i've been working these days in these 2 apps: http://youtu.be/uYjG8Iq1cD0 - http://youtu.be/65vvhFt57DU - http://youtu.be/F-_Hsl1Ts14
[15:13] <popey> balloons: other than it locking uip mid-test...?
[15:13] <balloons> popey, no it connects and says runs 0 tests
[15:14] <gatox> oh wrong channel
[15:14] <popey> gatox: video unavailable
[15:14] <gatox> weird
[15:14] <balloons> returns ok and ends.. it won't actually run ;-(
[15:14] <gatox> popey, maybe it's not accesible just yet
[15:15] <beuno> gatox is like the worst vacation taker ever
[15:15] <gatox> beuno, jejeejjee
[15:19] <ikillcypher> sergiusens,
[15:19] <ikillcypher> Oroku_Saki,
[15:19] <ikillcypher> Package Complete: /home/ikillcypher/xperiatouch/out/target/product/yuga/cm-10.1-20130814-UNOFFICIAL-yuga.zip
[15:20] <ikillcypher> xD Ubuntu-Touch On Yuga
[15:20] <ogra_> ikillcypher, congrats !!
[15:20] <ogra_> how did you get around the error in the end ?
[15:20] <ikillcypher> like finally mamenyaka helped me
[15:20] <ikillcypher> the guy who ported xperia ubuntu-touched
[15:20] <ogra_> ah, i didnt see him around today
[15:21] <ikillcypher> well google plus mate :D
[15:21] <ogra_> :)
[15:21] <ikillcypher> now I need to figure out how to back up my cm10.1
[15:21] <ikillcypher> and flash this o.o and get it working
[15:21] <ogra_> yeah, you only made the very first step
[15:21] <ogra_> there is still a lot ahead for a fully working port
[15:22] <ikillcypher> well atleast getting it boot was something everyone wanted to see
[15:22] <ikillcypher> fully working port isnt any where near maybe not now but that should be too hard at all
[15:22] <annerajb> ogra_, i had to flash to CWM recovery instead of the ubuntu one to be able to get into recovery
[15:22] <annerajb> got a dmesg
[15:23] <annerajb> ogra_, Kernel panic - not syncing: Attempted to kill init!
[15:23] <ogra_> annerajb, awesome
[15:23] <ogra_> so it mounted
[15:23] <ogra_> can you pastebin ?
[15:24] <ogra_> abd shell cat /proc/last_kmsg | pastebinit
[15:26] <popey> balloons / sergiusens is there any good reason why, when we run phablet-test-run it calls autopilot like this:-
[15:26] <popey>         exec_with_ssh autopilot run -o /tmp/test_results.xml -f xml $TESTSUITE
[15:26] <popey> with -f xml, so the resultant log file is pretty much no use?
[15:26] <popey> (for debugging where the test failures are)
[15:26] <popey> what consumes those xml files?
[15:26] <ogra_> sure they are, just usa an xml editor :P
[15:27] <sergiusens> popey: hmm.... jenkins
[15:27] <sergiusens> popey: just don't call it with xml generation
[15:27] <popey> the xml is truncated, shows no detail of where failures occur, that I've seen
[15:27] <popey> whereas a full autopilot log is actually useful
[15:27] <ogra_> sergiusens, but then you cant read the log in an xml editor !
[15:28] <sergiusens> popey: iirc, don't use -o
[15:28] <popey> but I need -o so it spits a log out that i can collect
[15:28]  * popey fiddles
[15:29] <sergiusens> popey: so what you mention as a problem may be an autopilot issue
[15:29] <mhall119> beuno: where can I upload a new package?
[15:29] <beuno> mhall119, I don't know, lets find out. Can you now not go back to the app and upload a new version?
[15:30] <mhall119> beuno: I'm on https://myapps.developer.ubuntu.com/dev/click-apps/3/
[15:30] <mhall119> do I have to start all over?
[15:30] <annerajb> ogra_, i dont think it mounted since i dont see the initrd print that says mounting
[15:31] <beuno> mhall119, I hope not. Is there a link next to "version number" to add a new version?
[15:32] <mhall119> beuno: there's no link next to version number itself, but there is an "Edit" link to the side of each section, including the "Your App" section which contains the version number
[15:32] <ogra_> annerajb, well, give me a pastebin :)
[15:32] <annerajb> ogra_, http://paste.ubuntu.com/5985400/
[15:32] <beuno> mhall119, ah, that's not very intuitive
[15:32] <mhall119> beuno: a giant "Upload new Package" button would be great
[15:33] <mhall119> clicking the edit button brings me back to the first step in the process too
[15:33] <beuno> hm
[15:33] <beuno> one sec
[15:33] <mhall119> clicking on "Uploading your app" gives me a screen with: "Current version already uploaded. Before a new upload, you must update your application's version."
[15:33] <ogra_> annerajb, hmm, i agree, i guess it is the sleep
[15:33] <mhall119> oh, so I need to actually bump it from 0.1 to 0.2 on the first screen, and only then can I upload a new package?
[15:34] <ogra_> (or the nonexistence of the same)
[15:34] <beuno> mhall119, yeah, although we fixed that. I think it hasn't been deployed yet
[15:34] <annerajb> ogra_, well it's not printing the kmsg so i dont think it executed the mount
[15:34] <ogra_> yes
[15:35] <ogra_> it still dies during the flash initialiyation
[15:35] <mhall119> beuno: bzoltan: also, there's nowhere on the Packaging form in QtCreator to change the version number of the package, how are developers supposed to do that?
[15:35] <annerajb> ogra_, so add a sleep somewhere in there?
[15:36] <beuno> mhall119, yeah, you should file a bug for that. You can edit it in the advanced tab
[15:36] <beuno> mhall119, so yes, first bump the version, then you can upload. That has been fixed and we're deploying the update later today
[15:37] <mhall119> beuno: I assume I can use 0.1.1
[15:37] <beuno> mhall119, yes
[15:38] <beuno> mhall119, it uses debian rules to check if it's newer
[15:38] <ogra_> annerajb, yeah, right before the mount ... start with something radical ... sleep 10 or so ...
[15:38] <mhall119> gah, updating the version number brings me back to the details page, so now I have to go back through everything again to upload a new package
[15:39] <beuno> mhall119, I think
[15:39] <beuno> that with the new version added
[15:39] <mhall119> oh, wait, now there's an Upload link next to the 0.1.1 version number
[15:39] <beuno> you may now have a link to up..
[15:39] <beuno> right
[15:39] <beuno> again, sorry about that, it's fixed just not yet deployed  :)
[15:39] <beuno> and by fixed, I mean it's been like this for years for software center
[15:39] <beuno> and we are slowly improving on it
[15:40] <mhall119> beuno: ok, uploaded the new package, but my app is still in Rejected state, shouldn't that reset when a new version is uploaded?
[15:41] <beuno> mhall119, I think I should of "ask for information" instead of rejected  :)
[15:43] <beuno> mhall119, looks great now!
[15:43] <beuno> aaand I broke something
[15:43] <beuno> :)
[15:46] <mhall119> poor davmor2, we're breaking everything before he even gets a chance :)
[15:46] <beuno> mhall119, I messed up, shouldn't of rejected it
[15:46] <mhall119> can it be un-rejected?
[15:46] <George> yes
[15:46] <davmor2> mhall119: save me breaking it
[15:47] <beuno> mhall119, yeah, I need to fiddle with with some things first
[15:47] <annerajb> ogra_, same thing but this time before the crash i saw system-udevd starting.
[15:47] <annerajb> (ie it crashes before the moutn much earlier
[15:48] <beuno> mhall119, done, back to you now
[15:49] <annerajb> ogra_, where is system-udevd started because i dont seem it on the scripts/touch being started there (so i dont think we are reaching the sleep )
[15:49] <davmor2> beuno: I hope you gave it a thorough review I don't trust that mhall119 as far as I can throw him ;)
[15:50] <beuno> davmor2, he's pretty skinny though
[15:52]  * davmor2 wonders if I can break mhall119 code again it's been a while.......now where did I put that big hammer.......
[15:52] <mhall119> davmor2: I hand-coded XML-RPC data, I'm sure nothing could possibly go wrong
[15:53] <mhall119> published!
[15:53] <mhall119> beuno: now where can I get a public URL to promote it?
[15:53] <davmor2> mhall119: Yay!
[15:55] <davmor2> ogra_: during the android guts on a flash I'm seeing a lot of text appear that didn't before should I be worried about that,  I'll try and jot down the error this time :)
[15:55] <balloons> m-b-o, so weather had some failures again..
[15:55] <ogra_> davmor2, i always have text here
[15:56] <m-b-o> balloons: yes, don'know what happened... wokring on device and locally
[15:56] <davmor2> ogra_: I have the last 3 flashes but didn't up until then
[15:56] <balloons> m-b-o, well there is some new improved ideas we could try for timing
[15:57] <Pandix> hello everybody...may i ask some simple Qs here!? anybody could help with new tablet ubuntu...
[15:57] <davmor2> ogra_: E:Can't open /cache/recovery/ubuntu_command  seems to trigger the text
[15:57] <phablet-chris> I'm wondering why the load avg is so high on my phablet, its not doing anything other than charging, I am logged in via ssh but this is the ouptu from top
[15:57] <phablet-chris> top - 15:56:32 up 19:41,  2 users,  load average: 7.74, 4.62, 4.16
[15:59] <popey> phablet-chris: paste the rest of top to pastebin?
[16:02] <phablet-chris> sure thing http://pastebin.com/Ljgkeqxu
[16:02] <phablet-chris> i just noticed though after I uplugged it the load avg dropped to 1.6 and is decrease
[16:03] <phablet-chris> after I unplugged it
[16:03] <phablet-chris> http://pastebin.com/4HCAZH4g
[16:09] <phablet-chris> that was wierd, after uplugging it went back to normal, so I plugged back in and its still fine. I will keep an eye on it and post to pastebin if I see an anomally
[16:12] <beuno> mhall119, a public URL to your app?
[16:12] <phablet-chris> probably becuase I was trying to play led zepplin 3 on you tube and it was stuck trying to dowlaod :)
[16:13] <popey> dpm: mhall119 pmcgowan added "System apps" to https://wiki.ubuntu.com/Touch/CoreApps/Contents so the non-core "Core" apps (which I called "System apps" - got a better term?) show up on all core apps pages.
[16:14] <dpm> thanks popey
[16:14] <popey> don't think I missed any out.. feel free to let me know (or add) if I did
[16:15] <Pandix> can i install ubuntu phone on any android device???????????
[16:16] <Pandix> and a link to the download page plz...
[16:17] <Pandix> can i install ubuntu phone on any android device???????????
[16:17] <w-flo> Pandix, https://wiki.ubuntu.com/Touch/Devices
[16:17] <Pandix> can i install ubuntu phone on any android device???????????
[16:18] <Pandix> tnx w-flo !
[16:19] <phablet-chris> is there a documentaion page for touch? I'd like to contribute as I use it
[16:22] <popey> phablet-chris: we have a wiki, anyone can edit that
[16:22] <popey> https://wiki.ubuntu.com/Touch is the main page, with other pages under it
[16:22] <popey> if you have suggestions for new pages, just shout or edit away!
[16:22] <phablet-chris> thanks
[16:30] <mterry> Are we planning on using plymouth at all in Touch?
[16:33] <ogra_> mterry, we would either need a new framebuffer driver in plymouth or enable fbcon on all devices (which isnt possible for most ports due to kernel breakage that will occur with the GL driver then)
[16:33] <ogra_> (mali doesnt allow fbcon next to it for example)
[16:33] <mterry> ogra_, do you happen to know offhand the replacement for plymouth-ready in upstart jobs?
[16:35] <ogra_> mterry, no, currently there is a diversion/override for all plymouth bits in the touch images
[16:35] <mterry> ogra_, OK, thanks
[16:35] <ogra_> i imagine we will want some kind of boot splash, and it would be good if that could be plymouth
[16:36] <ogra_> but i guess the only way would be some kind of new framebuffer driver then
[16:36] <ogra_> inside plymouth
[16:36] <balloons> well, I reflashed to stable to get my phablet-test-run working.. heh, now it only gives me an ssh error :-( ssh_exchange_identification: read: Connection reset by peer
[16:36] <mterry> balloons, you might need to run ./run_on_device -s
[16:36] <ogra_> bad peer ... this evil norwegian guy
[16:36] <mterry> balloons, from unity8 trunk
[16:37] <phablet-chris> heres another spike, now I know for sure nothing running other than top. and its unplugged http://pastebin.com/vfKZ7P3h
[16:37] <balloons> mterry, ty, I'll try that
[16:37] <annerajb> w-flo, i wanna thank you for your work on the vision it has helped me on the epic a lot :D
[16:37] <mterry> balloons, (it sets up ssh and ppa stuff on the device)
[16:37] <annerajb> ogra_, i miss any message if you ever sent me one after my last post forgot i was here and closed the laptop and went to get food
[16:38] <ogra_> lucky you then
[16:38]  * ogra_ didnt have food yet :)
[16:38] <ogra_> annerajb, so the sleep didnt help ? i wonder if we just see log spam that prevents us from seeing important stuff
[16:39] <annerajb> w-flo, you had any trouble on the vision while booting from the initrd? (apart from having to hardcode the path)
[16:39] <annerajb> ogra_, i dont think it has gotten to the sleep before it crashes
[16:39] <ogra_> thats weird
[16:39] <annerajb> like the line before the kernel panic is starting system-ueved
[16:43] <annerajb> ogra_,   systemd-udevd[154]: starting version 204
[16:43] <annerajb> that's the last line before the kpanic
[16:44] <ogra_> yeah
[16:44] <ogra_> but you got into adb before
[16:44] <ogra_> so i dont think it crashes out of the touch script
[16:44] <annerajb> i can adb in recovery but not on the loop
[16:44] <ogra_> unless you made any heavy kernel changes
[16:45] <annerajb> i reverted all of them yesterday
[16:45] <ogra_> you could adb when it didnt mount
[16:45] <annerajb> oh yeah when it didnt mount or when it did and /data was empty it worked
[16:45] <ogra_> into the busybox shell ... or couldnt you ?
[16:45] <ogra_> right
[16:45] <ogra_> so i'm pretty sure the logging is out of order thanks to the flash controller
[16:46]  * annerajb glares at samsung
[16:47] <ogra_> are you sure you fixed the typo properly ?
[16:48] <annerajb> case ${x} in
[16:48] <annerajb>                         datapart=*);;
[16:50] <annerajb> was that the right line? ogra_
[16:51] <ikillcypher> OMFG
[16:51] <annerajb> ikillcypher, it worked?
[16:51] <ikillcypher> SUCCESSFULLY PORTED UBUTU-TOUCHED TO XPERIA Z
[16:51] <ikillcypher> HELL YES
[16:51] <annerajb> ikillcypher, lol
[16:52] <ikillcypher> IT BEAUTIFUL MY EYES TEARS
[16:52] <annerajb> your baby
[16:52] <tj____> is ubuntu-touch supported in any form on amd64? the ubuntu-touch package was installable from the default saucy repos after installing from saucy daily desktop ISO. i'm using acer iconia w500 x86 tablet, but after the first boot after installing the ubuntu-touch package and dependencies, it'll just hang on boot
[16:52] <ogra_> ikillcypher, YAY
[16:53] <ikillcypher> wtf there isnt any back key
[16:53] <ikillcypher> uh no back key now Im stuck here o.o in events
[16:53] <annerajb> ikillcypher, you have to learn to use the ui
[16:53] <ogra_> tj____, no, it isnt being tested on x86 at all currently ...
[16:53] <annerajb> ikillcypher, you swip from left to right across the whole screen
[16:53] <annerajb> swipe*
[16:53] <ogra_> tj____, (the plan is to support x86 in the future indeed)
[16:54] <tj____> ogra_, ok thanks
[16:55] <sergiusens> ikillcypher: nice
[16:55] <tj____> hardwarewise the old w500 is finally supported by default ubuntu kernel with saucy, which was nice. i bought it a few years ago and something's always been broken with it (touch screen, bluetooth)
[16:55] <tj____> would be nice to finally put it in use with ubuntu touch ;) maybe i try stock saucy + e17 for now
[16:56] <ogra_> well, if Mir runs you should be able to use unity8 and Mir
[16:56] <ikillcypher> it is abit of an issue
[16:56] <ogra_> just not under the ubuntu-touch rask
[16:56] <ikillcypher> looks like unstable :S
[16:56] <ogra_> *task
[16:57] <tj____> the ubuntu-touch meta package pulled unity8 stuff but afaik no Mir
[16:57] <annerajb> ikillcypher, now you have to start optimizing it :D
[16:57] <ogra_> yeah, Mir on touch is in progress
[16:57] <ogra_> should land soon
[16:57] <ogra_> the point is that the ubuntu-touch meta is currently knitted with an android container in mind
[16:57] <tj____> w500 has an amd APU that works with the KMS radeon driver
[16:57] <ikillcypher> well Im going to flash back cm o.o since this is unstable
[16:58] <ogra_> we need to decouple these two parts fro palin x86 installs to work
[16:58] <annerajb> ikillcypher, remember to post on xda so other people can join in and optimize it
[16:58] <ogra_> *for plain
[16:58] <ikillcypher> I will
[16:58] <tj____> ogra_, ok i see thanks for the info
[16:58] <ogra_> it will happen before release ... until then just using the parts by themselves should work
[16:58] <ikillcypher> how do I screenshot o.o
[16:59] <ogra_> ikillcypher, i think the release notes link from the topic covers screenshots
[17:00] <ikillcypher> whats with my setting turning black
[17:01] <ogra_> ikillcypher, your setting ?
[17:02] <ikillcypher> it is highly buggy on my phone
[17:02] <ikillcypher> open settings makes it black
[17:03] <ogra_> ikillcypher, so debug it :)
[17:03] <ikillcypher> well open browser fixes it
[17:03] <ikillcypher> lol
[17:03] <ikillcypher> dude how do I take screenshot
[17:04] <annerajb> read the change log ikillcypher
[17:04] <ikillcypher> what changelog
[17:04] <ikillcypher> im new o.o remember
[17:05] <annerajb> ogra_, is this the link you where referring too? https://wiki.ubuntu.com/Touch/ReleaseNotes I dont see anything about screenshots
[17:05] <ogra_> hmm, i thought it had something
[17:06] <ogra_> here is another link :)
[17:06] <ogra_> ikillcypher, http://bit.ly/1d7lly1
[17:06] <annerajb> lol
[17:08] <annerajb> ikillcypher, you should add the steps to the wiki page :D
[17:08] <ikillcypher> o.o it is 1am here
[17:08] <ikillcypher> and I have school/work in like 6 hours
[17:08] <ikillcypher> I will probably continue tomorrow
[17:08] <ikillcypher> but first screenshots xD
[17:09] <annerajb> lol
[17:09] <pmcgowan> popey, thanks, we will soon remove share app, and replace phone with the 3 new ones
[17:10] <ikillcypher> can anyone tell me how to take screenshots o.o
[17:10] <annerajb> here ikillcypher
[17:10] <annerajb> http://vladfilippov.com/blog/2013-02-21-ubuntu-touch-preview
[17:10] <davmor2> http://vladfilippov.com/blog/2013-02-21-ubuntu-touch-preview
[17:10] <annerajb> lol
[17:11]  * ogra_ grins
[17:11] <ikillcypher> ikillcypher@ikillcypher:~$ sudo adb devices
[17:11] <ikillcypher> List of devices attached
[17:11] <annerajb> that's a problem lol
[17:11] <balloons> mterry, that didn't change much.. we're back to "Ran 0 tests in 0.000s"
[17:11] <ogra_> at least it is quick
[17:11] <annerajb> lol
[17:12] <balloons> which would indicate the tests may not be installed.. checking again.. this thing has been flash so much ;-)
[17:12] <balloons> ok, yep installed :-)
[17:13] <annerajb> ogra_, you have any further ideas for my device? Since that 10 second sleep on the init hasnt been reached. is there a file that get's called like /init thought /init appears to be a binary
[17:13] <annerajb> wait my bad wrong file is a script
[17:14] <ogra_> yeah
[17:14] <ogra_> i would be surprised if it turned into a binary all of a sudden
[17:14] <ogra_> can you paste  your current touch script ?
[17:14] <bzoltan> mhall119: there is a   "version" field in the manifest file. But the versioning will come as the upgrade mechanism is in place
[17:15] <annerajb> ogra_, yeah
[17:15] <annerajb> ogra_, let me format /data to see if it works -_-
[17:16] <w-flo> annerajb, yes, the initrd was too big to fit into the boot partition, so I had to remove adb. Other than that, hard-coding the data partition device node and enabling the VT and VT_CONSOLE kernel config options was enough (I've heard that's not actually needed though). no time now, back later :)
[17:17] <Parth_> Hi i want to make port of ubuntu touch for sony xperia z.Need help
[17:18] <ogra_> ikillcypher, werent you porting to xperia z ?
[17:18] <annerajb> lol
[17:20] <ogra_> Parth_, i bet ikillcypher would be happy to have someone helping, he just managed his first boot of a buggy port on that device :)
[17:20] <annerajb> Parth_, he just went away i believe or said he was.
[17:20] <Parth_> yes , ill be happy to help
[17:23] <annerajb> Parth_, i dont think ikillcypher is around but if you wanna get started looking at his repositories here they are: https://github.com/ikillcypher?tab=repositories
[17:23] <ikillcypher> damn im tired
[17:23] <ikillcypher> Parth_, ported
[17:23] <ikillcypher> check xda soon I will release
[17:23] <ikillcypher> or maybe in afew hours I need to sleep dude
[17:23] <annerajb> lol
[17:24] <Parth_> ikillcypher: thanks
[17:24] <ogra_> ikillcypher, well, at least point him to your code trees :)
[17:24] <ogra_> or do your zip
[17:24] <ogra_> s/do/to/
[17:24] <ikillcypher> how do add my name to devices/ubuntu site
[17:24] <ikillcypher> I will do that all later
[17:24] <ikillcypher> chill o.o
[17:24] <ikillcypher> it is late here
[17:24] <ogra_> k
[17:25] <ikillcypher> https://wiki.ubuntu.com/Touch/Devices
[17:25] <ikillcypher> https://wiki.ubuntu.com/Touch/Devices can anyone add ?
[17:25] <ikillcypher> Xperia Z - iKillCypher
[17:26] <ogra_> just add yourself
[17:26] <ogra_> (you need to log in)
[17:27] <Parth_> can you share link to your port
[17:28] <annerajb> ikillcypher, you should be able to add to the page there is a edit button at the top
[17:29] <ikillcypher> omg o.o people have pming me for the port
[17:29] <ogra_> ubuntu touch gets you famous :)
[17:29] <mamenyaka> ikillcypher, wtf??????????
[17:30] <ikillcypher> im dozing off here
[17:30] <ikillcypher> o.o
[17:30] <mamenyaka> with what?
[17:30] <ikillcypher> I should thank mamenyaka for error helping
[17:30] <annerajb> and ogra_ and sergiusens lol
[17:30] <ogra_> heh
[17:30] <ikillcypher> mamenyaka I have been up for more then 24 hours
[17:30] <annerajb> and i think Oroku_Saki lol
[17:30] <ogra_> and annerajb
[17:31] <ikillcypher> morning school + work + ubuntu-touch porting
[17:31] <mamenyaka> oh come on really now? that's the kind of person you are?
[17:31] <ikillcypher> what?
[17:31] <mamenyaka> I did everything for you, step by step
[17:31] <mamenyaka> and now this
[17:32] <ikillcypher> now what?
[17:32] <ikillcypher> whats wrong with you o.o I dont get you
[17:32] <mamenyaka> there is a special place for people like you in hell
[17:32] <ikillcypher> I dont get this guy
[17:32] <mamenyaka> and now just go to sleep
[17:32] <ikillcypher> what you need?
[17:32] <timp> a special hell for sleepy people?
[17:33] <mamenyaka> what kind of crap you told these people?
[17:33] <ikillcypher> I really dont get him why is he scolding me for
[17:33] <ikillcypher> I never did o.O
[17:33] <ikillcypher> I thank them for help and you
[17:33] <cloakandpigeon> Can anyone think of a reason I would be able to get SMS/Calls on ubuntu touch (nexus 4) but not be able to connect to data services?  My phone recognizes Rogers as my carrier, but no data.
[17:33] <ikillcypher> ask them
[17:34] <timp> mamenyaka: be nice :)
[17:34]  * timp off.
[17:34] <mamenyaka> I'm nice to nice people
[17:34] <ikillcypher> mamenyaka, why did you scold me for o.o
[17:34] <ikillcypher> I thank you for the errors and ubuntu-development team for the help
[17:34] <mamenyaka> errors?
[17:35] <mamenyaka> are you kidding me?
[17:35] <ikillcypher> what else do you want me to do
[17:35] <ikillcypher> kernel errors everything
[17:35] <ogra_> he means fixes i guess
[17:35] <mamenyaka> everything is what I did for you
[17:35] <ikillcypher> wtf ?!
[17:35] <mamenyaka> hell, you don't even know how to use cd
[17:35] <ikillcypher> holy smoke o.o
[17:35] <ogra_> mamenyaka, ikillcypher credited and praised you here for helping him before
[17:35] <ikillcypher> so you are fighting with me now for credits ?
[17:35] <ikillcypher> wtf
[17:36] <annerajb> mamenyaka, yeah as ogra said he mentioned before you where helping him.
[17:36] <ikillcypher> I came here for the past few days trying to set up and got it into brunch
[17:36] <mamenyaka> I just wnat a little respect for spending my whole day with you
[17:36] <mamenyaka> no no, don't get me wrong
[17:36] <ikillcypher> I respected you
[17:36] <ikillcypher> really o.o
[17:36] <ikillcypher> in what way have I disrespected you
[17:36] <ikillcypher> you have made me and thousands of users happy
[17:36] <mamenyaka> really? saying that I helped you error fixing
[17:37] <ikillcypher> yes errors and github help
[17:37] <mamenyaka> really?
[17:37] <ikillcypher> what more do you want me to say?
[17:37] <ikillcypher> I really dont get you
[17:37] <mamenyaka> I said, everything
[17:37] <mamenyaka> you don;t even know how to change directories in linux
[17:37] <mamenyaka> or to use TAB autocopmplete
[17:37] <ikillcypher> ok then thanks for everything
[17:37] <mamenyaka> or adb
[17:38] <mamenyaka> very well
[17:38] <mamenyaka> that's what I wanted to hear
[17:38] <mamenyaka> after all this disrespect
[17:38] <mamenyaka> now go and bath in all your fame
[17:38] <ikillcypher> uh ogra_ care helping out here I think there seems like some misunderstanding going on
[17:39] <ogra_> ikillcypher, well, if mamenyaka did most of the work you should say so :)
[17:39] <ikillcypher> well he did help me with alot of stuff
[17:39] <ikillcypher> I respected that
[17:39] <ogra_> to me it sounded like he helped you with some kernel fixes
[17:39] <ikillcypher> but I did my part too
[17:39] <mamenyaka> yes, following instructiions
[17:40] <ikillcypher> so both of us are to get the credits here
[17:40] <mamenyaka> yes, you get the credit for having the phone
[17:40] <mamenyaka> but please, it's like a 90% - 10% share of the work
[17:40] <mamenyaka> but I'm fine with that
[17:40] <ikillcypher> lol
[17:40] <mamenyaka> just please don;t tell people that I helped you with some vague errors
[17:41] <mamenyaka> because it was alot more than that
[17:41] <ikillcypher> yes it was mate
[17:41] <ikillcypher> now let break it over
[17:41] <ikillcypher> cause I think thousands of users wont care who got it working but what is working
[17:42] <annerajb> they will care who is going to fix all the issues it has left :D
[17:43] <ogra_> ikillcypher, just make sure to give enough credit for the work on the wikipage ... and make sure you help with the upcoming bugs that will certainly show up soon
[17:43] <mamenyaka> yes, but there are not so many errors, because our devices share the same repos, except for one
[17:43] <mamenyaka> and I fixed most of the stuff in the common repos on my device
[17:44] <mamenyaka> and he is just using them
[17:44] <ogra_> cool
[17:44] <ikillcypher> now I really dont like that
[17:44] <ikillcypher> he is being rude
[17:45] <mamenyaka> just go to sleep please
[17:46] <awe> come on, can we please just all relax a bit?
[17:46] <awe> cyphermox, two ofono MRs landing today with you as reviewer...
[17:46] <awe> don't think we need to do an upload for either
[17:46] <awe> let's let a couple stack up first
[17:47] <ikillcypher> indeed
[17:47] <cyphermox> ok!
[17:47] <awe> thanks!
[17:47] <cyphermox> having lunch now but ill review right after
[17:47] <ikillcypher> mamenyaka,
[17:47] <ikillcypher> [IMG]http://i39.tinypic.com/2rpv8n6.png[/IMG]
[17:47] <cyphermox> made some kickass salad :)
[17:47] <awe> cyphermox, actually though... the first fixes the -dbg packaging, so we might want to upload sometime soon
[17:48] <cyphermox> ok. i can upload right after review
[17:48] <awe> cyphermox, sounds good.  I have some fresh flounder coming out of the frying pan momentarily
[17:48] <awe> ;)
[17:49] <ikillcypher> and mamenyaka
[17:49] <ikillcypher> http://forum.xda-developers.com/showthread.php?p=44621291
[17:49] <ikillcypher> credits given
[17:49] <ikillcypher> tc mate
[17:49] <ikillcypher> cheers everyone
[17:49] <ikillcypher> nights
[17:49] <gordonjcp> awe: sounds good
[17:50] <mamenyaka> ikillcypher, be good, and sorry for overreacting
[17:51] <ikillcypher> im always good my bro
[17:51] <ikillcypher> I have whenever I can
[17:51] <ikillcypher> help*
[17:51] <ikillcypher> ok nights now
[17:52] <awe> mzanetti, just wanted to give you a heads up that I'll be looking at your PIN/retries bug this week; had a few other bugs stacked up ahead of it
[17:52] <hramrach> hello
[17:52] <awe> hopefully this isn't blocking you
[17:52] <hramrach> how do i install Ubuntu touch on an unsupported device?
[17:53] <awe> hramrach, that doesn't sound like a very good idea
[17:53] <sergiusens> mamenyaka: manta currently uses mali drivers btw
[17:53] <awe> if its unsupported, then it requires effort to make it supported.  ;)-
[17:53] <hramrach> I don't have a supported device so it's the best idea
[17:53] <awe> not if it doesn't work
[17:53] <annerajb> hramrach, which device?
[17:54] <hramrach> cubieboard
[17:54] <sergiusens> hramrach: what's the best idea? You either need to port it or use the community supported instance of it
[17:54] <sergiusens> !Devices
[17:54] <annerajb> hramrach, it dosnt appear to be supported by cyanogen mod
[17:55] <hramrach> ubuntu touch is based on Android?
[17:55] <annerajb> ogra_, why do we flash a ubuntu specific recovery?
[17:55] <ogra_> hramrach, it uses the android binary drivers
[17:56] <hramrach> binary drivers for what?
[17:56] <annerajb> ogra_, i had to remove it because it wasnt working could tha thave to do with my kernel panic?
[17:56] <mamenyaka> sergiusens, hi! what?
[17:56] <ogra_> hramrach, devices :P ....
[17:56] <ogra_> hramrach, modem, graphics ... etc
[17:57] <hramrach> I have native drivers. con't it use those?
[17:58] <ogra_> hramrach, what kind of devizce is that ?
[17:58] <hramrach> a devboard
[18:00] <hramrach> I have a 3D GLES accelerator, a screen and a multitouch tablet
[18:00] <ogra_> hramrach, ah ... well, currently the whole setup is built around the assumption that yoou have a minimal android (enough to use the drivers) running in a container and many processes currenntlly talk via libhybris to that container
[18:01] <ogra_> so when porting you will hit issues that we didnt plan for yet
[18:01] <hramrach> well, you can run andriod on hte board too
[18:01] <hramrach> but android is difficult to build becasue it requires certain vintage of ancient compiler which cannt build recent kernel
[18:02] <ogra_> well, i guess porting that way would be easier
[18:02] <ogra_> swimming with the stream ...
[18:02] <ogra_> i think you can surely do a native port but it will likely be a lot more work
[18:03] <hramrach> I wonder what kind of android image do I have
[18:04] <hramrach> anyway, I also have Adam which is listed as WIP
[18:04] <hramrach> so how do I install on somewhat supported device?
[18:05] <ogra_> on a fully supported device yoou use plablet-flash from the phablet tools package and it does everything for you
[18:05] <ogra_> on a community supported device you grab the android zip and tegh ubuntu rootfs zip and flash them as your device requires
[18:06] <hramrach> hmm, anad where is that zip?
[18:07] <hramrach> hmm, WIP means there is no image
[18:07] <ogra_> the official zips for the four supported arches are at http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/
[18:07] <hramrach> so back to how do I Install on unsupported device
[18:07] <ogra_> the unofficial ones are on the devices wikipage
[18:08] <ogra_> https://wiki.ubuntu.com/Touch/Install
[18:08] <ogra_> there is a manual install section
[18:09] <ogra_> note that this assumes a recovery mode that can flash autodeploy.zip files
[18:21] <balloons> iBelieve, ping
[18:21] <iBelieve> balloons, pong
[18:21] <balloons> iBelieve, so the file manager had a couple test run snafus, care to weigh some input with me? :-)
[18:24] <sergiusens> ogra_: community supported devices that are in bold on the wiki can be flash like: phablet-flash community --device [device]
[18:24] <ogra_> oh, indeed !
[18:26] <iBelieve> balloons, hmm, interesting. are the tests being run on a phone or desktop?
[18:26] <balloons> iBelieve, the tests are run on nexus devices
[18:28] <sergiusens> jdstrand: just took a stand at opening a click package on manta grep DENIED /var/log/kern.log greps nothing
[18:28] <pmcgowan> ogra_, who's responsible for promoting the image? I thought todays would go through
[18:30] <ogra_> pmcgowan, it will, i havent found the time to compare all the test results yet
[18:30] <ogra_> pmcgowan, but the next one should be built by now too
[18:30] <iBelieve> balloons, I'm going to try running that test on the desktop but with the app in phone mode (width  = 50gu)
[18:31] <balloons> iBelieve, which test is that?
[18:32] <balloons> test_open_file isn't going to work on the device, so I simply placed a         if model() == "Desktop": wrapper around it until support lands. The other two failures though are not so cut and dry
[18:32] <iBelieve> balloons, any that access places, but specifically the one that failed - ubuntu_filemanager_app.tests.test_filemanager.TestFolderListPage.test_go_home
[18:32] <jdstrand> sergiusens: so the app failed to launch but there are no apparmor denials?
[18:32] <balloons> iBelieve, kk, ty :-)
[18:33] <sergiusens> jdstrand: yes, if I remove the aa-exec app confinement from the desktop file it does launch
[18:33] <sergiusens> let me validate that again
[18:33] <jdstrand> sergiusens: can you paste the output of 'sudo aa-status'?
[18:33] <sergiusens> http://paste.ubuntu.com/5986010/
[18:34] <sergiusens> jdstrand: com.ubuntu.dropping-letters_dropping-letters_0.1.2.2 is what I want to launch
[18:34] <jdstrand> sergiusens: which app are you launching?
[18:34] <sergiusens> or what I'm testing with
[18:34] <jdstrand> ok, so the profile is loading
[18:34] <jdstrand> err
[18:35] <jdstrand> is loaded
[18:35] <jdstrand> sergiusens: can you perform 'sudo sysctl -w kernel.printk_ratelimit=0' and try again?
[18:35] <jdstrand> sergiusens: ie, launch it, then do 'grep DEN /var/log/kern.log'
[18:36] <sergiusens> ah there we go
[18:36] <sergiusens> jdstrand: http://paste.ubuntu.com/5986018/
[18:36] <hramrach> ogra_: I would like to install by extracting the filesystem to somewhere, not using recovery
[18:36] <sergiusens> jdstrand: /dev/mali0
[18:36] <hramrach> but I need a working andriod I guess
[18:37] <hramrach> which I don't have for either device :/
[18:37] <jdstrand> kernel rate limiting ftl
[18:37] <iBelieve> balloons, it failed for me too, but I figured out what it was.
[18:37] <ogra_> hramrach, well, you actually need the android source
[18:37] <sergiusens> jdstrand: I'll update the bug for documenting purposes
[18:37] <hramrach> hmm
[18:37] <ogra_> hramrach, grab the tar.gz from the cdimage link i gave you above ...
[18:38] <ogra_> so you can at least play with it
[18:38] <iBelieve> balloons, because list items don't look right on popovers with a Suru them, we switched to using custom Labels, so the Standard list item's text property (which was used to find places), wasn't being used.
[18:38] <hramrach> there is no android source for specific device, is there?
[18:38] <jdstrand> sergiusens: ok, can you add to /var/lib/apparmor/profiles/com.ubuntu.dropping-letters_dropping-letters_0.1.2.2 the following: /dev/mali[0-9] rw, befoer the last brace, then do: sudo apparmor_parser -r /var/lib/apparmor/profiles/com.ubuntu.dropping-letters_dropping-letters_0.1.2.2 and try again?
[18:38] <jdstrand> sergiusens: this is the complate line:
[18:38] <balloons> iBelieve, so you think you can make a merge to fix both tests? If so, awesome mate
[18:38] <jdstrand>   /dev/mali[0-9] rw,
[18:38] <ogra_> hramrach, there are device and non device specific android bits usually
[18:39] <jdstrand> sergiusens: (ie, we need the trailing comma :)
[18:39] <ogra_> hramrach, a working android consists of both
[18:39] <sergiusens> jdstrand: ack, one sec
[18:39] <iBelieve> balloons, sure, though maybe not right away. I've already fixed it, I just need the time to upload it and create the merge request.
[18:40] <balloons> iBelieve, k, I'll stand by ;-)
[18:40] <jdstrand> I see this is going to be a pain-- ideally we would have an out of process helper so the app didn't need direct access to the device (ala pulseaudio for audio)
[18:40] <jdstrand> 'this' meaning all this device specific accesses
[18:41] <jdstrand> we can at least get the 4 target devices going though
[18:41] <annerajb> jdstrand, like a layer for all device specific access?
[18:41] <ogra_> hramrach, the non device specific bits (as well as the device specific bits for the supported devices) are in the git repo from phablet.ubuntu.com
[18:41] <annerajb> or rather api.
[18:41] <jdstrand> annerajb: yes, but it need to be out of process. a linrary layer isn't enough
[18:41] <jdstrand> s/linrary/library/
[18:41] <sergiusens> jdstrand: app opens, I do get other denieds though
[18:42] <jdstrand> sergiusens: can you paste?
[18:42] <sergiusens> jdstrand: for /dev/ion
[18:42] <sergiusens> jdstrand: http://paste.ubuntu.com/5986036/
[18:42] <hramrach> ok, time to search for device specific bits
[18:42] <hramrach> thanks
[18:43] <jdstrand> sergiusens: please add:
[18:43] <jdstrand>   /dev/ion rw,
[18:43] <sergiusens> jdstrand: just in case the first mali error in there is from the previous run
[18:43] <jdstrand> sergiusens: then try again
[18:43]  * jdstrand nods
[18:44] <sergiusens> jdstrand: success!
[18:44] <jdstrand> \o/
[18:44] <jdstrand> I'll add those to apparmor-easyprof-ubuntu and upload
[18:45] <sergiusens> great
[18:46] <jdstrand> sergiusens: thanks for your help :)
[18:46] <sergiusens> jdstrand: it was all you, I was just a monkey runner ;-)
[18:46] <jdstrand> sergiusens: ah but a monkey with the required device :)
[18:46] <sergiusens> lol
[18:47]  * jdstrand doesn't think sergiusens is monkey at all btw :)
[18:47]  * sergiusens is not sensitive
[18:47] <sergiusens> :-)
[18:48] <annerajb> ogra_, when i get home i am going to flash the ubuntu recovery because that may have something to do with why my device going into a reboot loop (with ubuntu recovery it just crashed)
[18:48] <ogra_> annerajb, ok
[18:50] <annerajb> and take a look at the script change see it has no syntax error. apart from that i am really out of ideas -_- apart from commenting kernel_reboot lol
[18:51] <ogra_> well, if it fails before the sleep all i can imagine is a typo
[18:51] <annerajb> i hope so.
[18:51] <ogra_> it worked before ...
[18:52] <annerajb> i say that so many times working with code lol.
[18:52] <annerajb> it worked (insert time here )ago.
[18:52] <ogra_> except that nothing changed in other code apart from the touch script
[19:03] <cyphermox> awe: your ofono ril patch cleanup branch isn't filed for merge... lp:~awe/ubuntu/saucy/ofono/rilmodem-patch-cleanup
[19:04] <cyphermox> is that expected?
[19:04] <cyphermox> I already have the -dbg one approved and applied locally
[19:04] <awe> cyphermox, yea...my conscience got the better of me, and I decided to do some quick sanity check testing on maguro before proposing
[19:04] <awe> ;)
[19:05] <awe> building now, should propose the MR shortly
[19:06] <mamenyaka> guys, unity8.log: http://paste.ubuntu.com/5986119/
[19:07] <cyphermox> btw you don't need a .PHONY for the dh overrides
[19:07] <awe> cyphermox, OK... I got that from sergiusens
[19:08] <ogra_> ricmm, or sergiusens ... does any of you have an idea why even though everything on the device runs (SF is up, all processes seem to run fine) the session comes up with a grey/black screen ? mamenyaka cant get his device to work and i'm out of ideas ...
[19:09] <awe> cyphermox, per https://wiki.debian.org/DebugPackage
[19:11] <sergiusens> awe: cyphermox I got that from the debian wiki :-)
[19:12] <awe> sergiusens, you're a bit slow today
[19:12] <awe> ^^
[19:12] <sergiusens> ogra_: hybris calls missing mappings perhaps :-)
[19:12] <sergiusens> awe: yeah I saw after :-P
[19:12] <ogra_> hmm
[19:12] <sergiusens> ogra_: a quick test is to run test-(the gl ones)
[19:12] <ogra_> they work
[19:12] <ogra_> mamenyaka, ^^^ right ?
[19:13] <cyphermox> sergiusens: right. I suspect it was just a force of habit addition ;)
[19:13] <sergiusens> ogra_: is an upstart job blocking unity from launching?
[19:13] <ogra_> sergiusens, i see it in the processlist
[19:13] <ogra_> in fact the whole session is up
[19:13] <ogra_> powerd/powerbutton seems to work
[19:14] <sergiusens> ogra_: so, I see something similar on manta for sidestage apps... but I am not focusing time into that
[19:14] <ogra_> yeah, understood
[19:14] <ricmm> ogra_: grey in full? or does he see something at all coming on the screen
[19:14] <sergiusens> ogra_: still... I can't think of anything
[19:15] <sergiusens> ogra_: take a screenshot!
[19:15] <sergiusens> for real
[19:15] <davmor2> ogra_: on the lastest flash if you open the terminal app is it just grey for you?
[19:15] <mamenyaka> sorry
[19:15] <ogra_> ricmm, powerd seems to switch backlight on and off ...
[19:15] <ricmm> mamenyaka: sounds like permissions problems
[19:16] <ricmm> mamenyaka: can you try to run unity8 as root
[19:16] <mamenyaka> okay
[19:16] <ricmm> or the glesv2 example
[19:16] <mamenyaka> that runs well
[19:16] <ogra_> sergiusens, well, mamenyaka would have to :) i'm not sitting on hs lap
[19:16] <sergiusens> ricmm: the example works
[19:16] <sergiusens> ogra_: lol
[19:16] <ricmm> what does well mean?
[19:16] <ricmm> run unity8 as root
[19:16] <ricmm> its failing to find an eglconfig
[19:16] <ricmm> that usually means permission issues
[19:17] <mamenyaka> hah
[19:17] <mamenyaka> would you believe that
[19:17] <mamenyaka> it works now
[19:17]  * ogra_ does belive ricmm 
[19:17] <ogra_> blindly sometimes :)
[19:18] <mamenyaka> but could I run unity8 not as root?
[19:18] <ricmm> mamenyaka: strace unity8 as phablet user then and figure out where the EACCES are
[19:18] <mamenyaka> I mean I have root@ubuntu
[19:18] <ricmm> and sort that with correct udev rules
[19:18] <ricmm> ogra can shed more light on how to setup udev rules for your device
[19:18] <ogra_> yeah
[19:19] <davmor2> ogra_: yeah but you also believe in farther christmas elves and unicorns so you're not setting the level high
[19:19] <ogra_> (we already set everything with graphics group to 0666, i had hoped that was enough)
[19:19] <mamenyaka> so, should I set everything to 0666?
[19:19] <ricmm> mamenyaka: no, you need to strace the failing unity8
[19:19] <ogra_> davmor2, i deny the elves ... but cant deny the unicorns
[19:19] <ricmm> and find out what devices are failing to open
[19:19] <ricmm> so that you can tune the permissions for them in the rules
[19:20] <awe> ogra_, what about ogres?
[19:20] <mamenyaka> where do I get strace from?
[19:20] <ricmm> apt-get
[19:20] <mamenyaka> and where does apt-get get it from?
[19:20] <ogra_> awe, ogres on unicorns, yes, indeed
[19:22] <ricmm> mamenyaka: what do you mean?
[19:22] <ricmm> # apt-get install strace
[19:22] <ricmm> on device
[19:22] <ricmm> from the network
[19:22] <davmor2> ogra_: no ogres on dragons chasing elves on unicorns ;)
[19:22] <ricmm> provision it your network setup with phablet-deploy-networking from phablet-tools
[19:23] <ogra_> nope, no elves
[19:23] <davmor2> man all this talk of 666 now I can't get the omen music out of my head
[19:23] <mamenyaka> of course from the netwrok, I was suggesting I have no network connection
[19:24] <ricmm> no network because of no driver? or because you dont have the UI to set it up
[19:24] <ricmm> if its the later, provision the config with the tools
[19:24] <mamenyaka> the wifi was always broken
[19:24] <ricmm> otherwise fetch the .deb from launchpad and push it to device
[19:25] <mamenyaka> fetching it is
[19:25] <ogra_> davmor2, awe https://lh6.googleusercontent.com/BGmg11iYfZ4iBVhVF-jYTLZSYVjwzTin930rWl1suLQ=w155-h207-p-no
[19:26] <awe> ogra_, thanks for ruining my afternoon... hopefully will erase that from my brain before dinner
[19:26] <ogra_> haha
[19:27]  * awe prefers rabbit flesh
[19:28] <mamenyaka> is this the one? strace_4.8-1ubuntu2_armhf.deb
[19:28] <awe> cyphermox, testing looks good, will propose MR
[19:28] <awe> cyphermox, do you want me to remove the .PHONY?
[19:28] <awe> or should I leave per the debian wiki?
[19:28] <awe> or is the debian wiki wrong
[19:28] <ogra_> mamenyaka, yeah
[19:29]  * awe is full of questions this afternoon
[19:29] <mamenyaka> okay, I have strace
[19:29] <mamenyaka> now how do I run it as phablet?
[19:30] <ogra_> sudo -u phablet -i
[19:31] <mamenyaka> oh my god, what should I do with all the output?
[19:31] <mzanetti> awe: cool, thanks
[19:32] <ogra_> mamenyaka, strace -o all_the_output.log <path to spp>
[19:33] <mamenyaka> path to spp?
[19:33] <mamenyaka> I did strace unity8 > /home/phablet/log
[19:34] <awe> mamenyaka, also a good idea would be to read the manpage;  strace has all kinds of control for limiting which system calls are output
[19:34] <mamenyaka> yes, even the manpage has a lot of that
[19:35] <mamenyaka> http://paste.ubuntu.com/5986228/
[19:35] <ogra_> mamenyaka, *app
[19:36] <ogra_> open("/dev/ump", O_RDWR|O_LARGEFILE)    = -1 EACCES (Permission denied)
[19:36] <ogra_> there is your prob
[19:37] <mamenyaka> great!
[19:38] <mamenyaka> bu
[19:38] <mamenyaka> ACTION=="add", KERNEL=="ump", OWNER="system", GROUP="graphics", MODE="0666"
[19:38] <ogra_> well, check the real file
[19:39] <mamenyaka> what real file?
[19:39] <ogra_> open("/dev/ump", O_RDWR|O_LARGEFILE)    = -1 EACCES (Permission denied)
[19:40] <ogra_> the file it tries to open indeed :)
[19:40] <mamenyaka> ls -l ump
[19:40] <mamenyaka> crw------- 1 root root 243, 0 Aug 14 20:39 ump
[19:40] <ogra_> see
[19:40] <mamenyaka> I see
[19:41] <mamenyaka> so do I add an udev rule for /dev/ump?
[19:41] <ogra_> so why isnt that 666 ? is your udev rule not processed ?
[19:42] <mamenyaka> it's not /dev/ump
[19:42] <mamenyaka> it's simply ump
[19:42] <ogra_> ?
[19:42] <ogra_> you mean it doesnt live in /dev ?
[19:42] <ogra_> udevadm test
[19:43] <ogra_> try that
[19:43] <ogra_> and see if it shows any errors
[19:43] <mamenyaka> syspath parameter missing
[19:43] <ogra_> thats fine
[19:44] <ogra_> i mean the rules it processes
[19:44] <mamenyaka> nothing else
[19:44] <mamenyaka> just some info
[19:44] <mamenyaka> is it a problem if I have more than one  ACTION=="add", KERNEL=="ump", OWNER="system", GROUP="graphics", MODE="0666" in the file?
[19:45] <ogra_> the last one would apply
[19:45] <mamenyaka> then it's okay
[19:45] <ogra_> iirc
[19:45] <ogra_> but you should only have one, delete one
[19:45] <mamenyaka> okay, and if there are similar ones, only with different GROUP?
[19:45] <ogra_> do the other permissions in dev look like the rule was processed ?
[19:46] <mamenyaka> not really
[19:47] <mamenyaka> http://paste.ubuntu.com/5986270/
[19:47] <ogra_> no, not at all
[19:48] <mamenyaka> how can I check the device name it is expecting?
[19:48] <ogra_> how is your udev rules file called
[19:48] <mamenyaka> n8000
[19:48] <mamenyaka> 70-n8000.rule
[19:48] <mamenyaka> s
[19:48] <mamenyaka> you get it
[19:49] <ogra_> getprop ro.product.device
[19:49] <mamenyaka> empty?
[19:49] <ogra_> grep ^ro.product.device= /system/build.prop
[19:49] <mamenyaka> no, it's okay
[19:49] <mamenyaka> wrong shell
[19:49] <ogra_> ah
[19:49] <mamenyaka> GT-N8000
[19:49] <ogra_> aha
[19:49] <mamenyaka> so is this it?
[19:49] <ogra_> yes
[19:50] <mamenyaka> oh well
[19:50] <mamenyaka> I better kill myself
[19:50] <ogra_> 70-GT-N8000.rules
[19:50] <ogra_> thats what you want
[19:50] <mamenyaka> rebooting
[19:59] <mamenyaka> thank you for letting me waste most of your precious time
[19:59] <mamenyaka> it is now working
[19:59] <mamenyaka> damn, I feel silly
[19:59] <ogra_> awesome
[19:59] <mamenyaka> still, font issues, guess I have some other things to do
[20:00] <mamenyaka> isn't there a fix for that?
[20:00] <mamenyaka> I mean apart from reverting the kernel and drivers
[20:00] <ogra_> what exactly, you need to be more specific
[20:01] <mamenyaka> well, it's a known problem for some samsung devices
[20:01] <ogra_> (fonts to big, upside down, all greek etc)
[20:01] <mamenyaka> font is all messed up
[20:01] <mamenyaka> all greek if you wish
[20:01] <mamenyaka> it's misdisplayed
[20:01] <ogra_> ah, yeah, on the galaxy S2 that was solved by going to an older mali driver
[20:01] <mamenyaka> yes, that I want to avoid
[20:01] <ogra_> but then, you dont use mali
[20:02] <mamenyaka> because the older driver just needs libandroid and some many other crap
[20:02] <ogra_> it is definitely the driver though
[20:02] <mamenyaka> there was I think Ricardo Mendosa researching it
[20:02] <mamenyaka> that we need more memory to allocate
[20:02] <mamenyaka> but never got to the end of it
[20:02] <mamenyaka> could you please ask him?
[20:02] <ogra_> well, you talked to him above :)
[20:03] <mamenyaka> oh great
[20:03] <ogra_> (he is ricmm ... )
[20:03] <mamenyaka> ricmm, can you give me all your knowledge about fixing the font issue with samsung?
[20:03] <ogra_> haha
[20:03] <ogra_> in a can
[20:04] <mamenyaka> thank you really much for helping me all the time
[20:04] <ogra_> np
[20:04] <ricmm> mamenyaka: whats the font issue with samsung?
[20:04] <mamenyaka> the font misdisplaying
[20:04] <ricmm> shows fine on my samsung galaxy nexus
[20:04] <mamenyaka> it's like unreadable
[20:04] <ricmm> what device is it
[20:04] <mamenyaka> okay, samsung note 10.1
[20:04] <mamenyaka> or s2
[20:05] <ricmm> 8000 ?
[20:05] <mamenyaka> yes
[20:05] <ricmm> n8000
[20:05] <mamenyaka> I know about reverting to the odler drivers
[20:05] <mamenyaka> but long ago we emailed about increasing some mem allocation
[20:05] <ogra_> mamenyaka, http://people.canonical.com/~ogra/phablet/i9100/img.pngsimilar to that ?
[20:06] <mamenyaka> exactly
[20:06] <ricmm> well n8000 uses mali
[20:06] <ricmm> I'd say just go with ogra's solution
[20:06] <ogra_> ricmm, oh ? it has a pvrsrv device
[20:06] <mamenyaka> I did it once for te unflipped, but it needed libandroid.so and other crap
[20:07] <ogra_> if it is indeed mali i guess the rollback is the only solution atm
[20:07] <ricmm> for the 10.1 N8000 it is a malii 400
[20:07] <ricmm> trying to find the thread
[20:08] <ricmm> mamenyaka: where was this email discussion?
[20:08] <mamenyaka> I am searching for it
[20:09] <mamenyaka> maybe I private mailed you
[20:09] <mamenyaka> after I got the hint
[20:10] <ricmm> I found the email
[20:11] <mamenyaka> great!
[20:14] <ricmm> mamenyaka: can you try running unity8 with QML_DISABLE_DISTANCEFIELD=1
[20:14] <mamenyaka> how exactly?
[20:15] <ricmm> # QML_DISABLE_DISTANCEFIELD=1 unity8
[20:16] <mamenyaka> how do I kill of the other unity?
[20:16] <mamenyaka> QXcbConnection: Could not connect to display
[20:16] <mamenyaka> think I got it
[20:17] <mamenyaka> issue remains
[20:18] <ricmm> then I dont really know, short of reverting to an old driver
[20:18] <mamenyaka> wait
[20:18] <mamenyaka> if I kill unity8, is it enough?
[20:18] <ogra_> edit /usr/share/upstart/sessions/unity8.conf
[20:18] <ricmm> what issue remains, the text garbage?
[20:18] <ricmm> or unity8 running
[20:18] <ricmm> $ stop unity8
[20:18] <ogra_> add:
[20:18] <ricmm> will stop the shell
[20:19] <ogra_> env QML_DISABLE_DISTANCEFIELD=1
[20:19] <ogra_> right under the respawn
[20:19] <ogra_> then just reboot
[20:19] <mamenyaka> stop doesn't work
[20:19] <ogra_> stop only works as phablet user
[20:19] <mamenyaka> great
[20:20] <ogra_> anyway, just edit the file and see
[20:21] <mamenyaka> how does this vi work?
[20:22] <mamenyaka> okay, got it
[20:23] <mamenyaka> oh now what, stuck at bootlogo
[20:24] <mamenyaka> this is repeating in logcat: I/ServiceManager( 1727): Waiting for service SurfaceFlinger...
[20:24] <mamenyaka> I/ServiceManager( 2087): Waiting for service sensorservice...
[20:24] <ogra_> heh
[20:24] <mamenyaka> if I reinstall it will work
[20:24] <ogra_> you want the fixed powerd that wa uploaded today
[20:24] <mamenyaka> oh
[20:25] <ogra_> just add an "and android" to the end of the start on line in /etc/init/powerd.conf
[20:25] <ogra_> and it should work on next boot
[20:27] <click_> hey guys, have some questions as far as porting
[20:30] <mamenyaka> so "start on started dbus and android"
[20:30] <mamenyaka> ?
[20:32] <ogra_> yes
[20:32] <ogra_> that will make it wait until after the container is up
[20:32] <mamenyaka> still stuck
[20:32] <mamenyaka> okay
[20:32] <mamenyaka> I wait
[20:32] <ogra_> currently it tries to access the sensorservice before it is up
[20:32] <mamenyaka> oh, should I have that patch?
[20:33] <mamenyaka> with the sensors
[20:33] <ogra_> no, the above change was the patch
[20:33] <ogra_> you wait for the android event
[20:33] <click_> bassicly i fallowed the port system using this link http://forum.xda-developers.com/showthread.php?t=1908008
[20:33] <click_> however it still boots into cm 10.1
[20:34] <mamenyaka> ogra_, 3 min uptime
[20:35] <mamenyaka> still nothing
[20:35] <mamenyaka> but when I fresh install ,everything just works
[20:37] <ogra_> well, there is another hack you can do
[20:37] <mamenyaka> reinstall?
[20:38] <ogra_> cp /var/lib/lxc/android/rootfs/init.rc /var/lib/lxc/android/overrides/
[20:39] <ogra_> now edit /var/lib/lxc/android/overrides/init.rc ... look for sensorservice
[20:39] <ogra_> and change it from "class late_start" to "class main"
[20:39] <ogra_> then reboot and see
[20:42] <mamenyaka> this is one messed up device
[20:42] <mamenyaka> nothing
[20:42] <mamenyaka> I mean, same thing, stuck on bootlogo
[20:43] <ogra_> even with the sensorservice moved ?
[20:43] <mamenyaka> copied?
[20:43] <ogra_> and edited
[20:43] <mamenyaka> yes
[20:43] <mamenyaka> triple checked
[20:44] <mamenyaka> # cat /var/lib/lxc/android/overrides/init.rc
[20:44] <mamenyaka> service sensorservice /system/bin/sensorservice
[20:44] <mamenyaka>     class main
[20:44] <mamenyaka>     user system
[20:44] <ogra_> yeah, thats fine
[20:44] <ogra_> then i'm out of ideas
[20:44] <mamenyaka> cat /etc/init/powerd.conf
[20:44] <mamenyaka> author "Michael Frey <michael.frey@canonical.com>"
[20:44] <mamenyaka> start on started dbus and android
[20:44] <mamenyaka> well, I will reinstall quickly and edit the QML thing
[20:44] <ogra_> yes
[20:45] <firejim> greetings
[20:46] <firejim> i would like to know if anyone has been working Ubuntu on P5110
[20:46] <mamenyaka> should I downloaded latest saucy or is the current ok?
[20:46] <mamenyaka> aug08
[20:46] <mamenyaka> okay, wrong question, current updated
[20:47]  * ogra_ goes for dinner ...
[20:47] <houseofbean> I've got Ubuntu Touch on a Nexus 4, and I'm thinking about putting the port on my tf101.
[20:49] <firejim> Ubuntu touch its a preview, do we know when the official release will be out?
[20:50] <cyphermox> awe: did you propose the merge?
[20:57] <awe> cyphermox, https://code.launchpad.net/~awe/ubuntu/saucy/ofono/rilmodem-patch-cleanup/+merge/180239
[20:57] <pmcgowan> ivanka, is that you?
[20:57] <ivanka> pmcgowan, it is
[20:58] <ivanka> but train is arriving so am about to go :-)
[20:58] <pmcgowan> oh too bad
[20:58] <ivanka> pmcgowan, you good?
[20:58] <pmcgowan> sure
[20:58] <pmcgowan> ivanka, hope you're enjoying your new gig
[20:58] <mamenyaka> god bless my 300 KB/sec download speed
[20:59] <ivanka> pmcgowan, I am, thank you. :-)
[20:59] <pmcgowan> ivanka, well we miss you
[20:59] <ivanka> pmcgowan, miss you all, of course
[20:59] <ivanka> hehe
[20:59] <ivanka> pmcgowan, thank you
[21:00] <pmcgowan> ivanka, things moving along quite well, should have something good for oct
[21:01] <ivanka> pmcgowan, excellent! I do keep an eye
[21:02] <ivanka> pmcgowan, got to get off the train now - take care and speak soon. All the best!
[21:02] <pmcgowan> ivanka, you too, stop by the channel again!
[21:02] <ivanka> pmcgowan, if my computer is on, I am signed in
[21:02] <ivanka> pmcgowan, see you round!
[21:05] <mfisch> mterry: does seb128 know about account services backing some settings?
[21:10] <mterry> mfisch, he better
[21:10] <mterry> mfisch, i.e. yes
[21:23] <mamenyaka> ogra_, you gotta be kidding me!!!! it works, font issue gone!
[21:23] <mamenyaka> ricmm, font issue fixed!
[21:24] <mamenyaka> ogra_, ricmm noooo, after a little it's getting messed up again
[21:28] <mamenyaka> can you please look at this why wifi is failing to connect? http://paste.ubuntu.com/5986581/
[21:28] <mamenyaka> [  132.702546] c1 connect failed event=0 e->status 1 e->reason 0
[21:29] <mamenyaka> [  132.702629] c1 CFG80211-INFO2) wl_bss_connect_done : Report connect result - connection failed
[21:30] <rickspencer3> mhall119, is there somewhere I can get a definitive pattern for how to put a flickable in a column and have it and it's contents sized properly?
[21:31] <rickspencer3> I feel like I flail around with anchoring and height and stuff every time
[21:36] <ricmm> mamenyaka: what fixed it, my DISTANCEFIELD thing?
[21:36] <mamenyaka> yes
[21:36] <ricmm> and then after a while it breaks
[21:36] <ricmm> thats weird as hell :)
[21:36] <mamenyaka> but anomalies appear as I use it
[21:36] <ricmm> but it suggests memory exhaustion of some sort
[21:36] <mamenyaka> http://kepfeltoltes.hu/130814/screenshot_www.kepfeltoltes.hu_.png
[21:37] <mamenyaka> the word phone
[21:37] <mamenyaka> the keyboard
[21:37] <cyphermox> awe: done
[21:37] <awe> thanks dude!
[21:38] <mamenyaka> ricmm, could you please check out the wifi issue I am having?
[21:38] <ricmm> sorry, cant really do so right now
[21:38] <ricmm> on a deadline
[21:39] <ricmm> mamenyaka: but send me an email with the info and I'll take a look at it later
[21:39] <mamenyaka> ricmm, email address?
[21:40] <mhall119> rickspencer3: I don't think so, not in the Ubuntu SDK documentation anyway, there might be something for generic QtQuick
[21:40] <mamenyaka> thank you so much
[21:40] <rickspencer3> mhall119, hmmm, there must be a pattern for it somewhere
[21:40] <rickspencer3> I'll find it somewhere ;)
[21:41] <ricmm> mamenyaka: ricmm@canonical.com
[21:41] <mhall119> rickspencer3: I only recently figured out the right way to use Flickables and Pages together to make the Header disappear
[21:41] <mhall119> we could definitely use some code-design guides
[21:41] <rickspencer3> that's some cool stuff
[21:42] <mhall119> rickspencer3: if you put your Flickable/Column question into AskUbuntu, we could use it for the Cookbooks on developer.ubuntu.com when it gets a good answer
[21:42] <mhall119> (hint, hint)
[21:42] <rickspencer3> :)
[21:42] <mhall119> since those are pretty much our code-design documents at the moment
[21:43] <SrPx> Hello, is ubuntu-touch a completely different OS or does it run everything you can run on ubuntu itself?
[21:45] <mhall119> SrPx: it's the same Ubuntu core
[21:46] <mhall119>  but not all Ubuntu apps will run on it, because it doesn't use the X11 display server or because they just aren't designed for small screens and touch input
[21:46] <mhall119> but all of the Ubuntu Touch apps will be capable of running on Ubuntu Desktop
[21:46] <mhall119> so, going forward, new apps should be able to run on both
[21:47] <mhall119> and old apps that are ported/upgraded to the new toolkits will too
[21:48] <nik90> rickspencer3: thinking of app for the showdown :P ?
[21:48] <rickspencer3> nik90, schmaybe
[21:48] <rickspencer3> ;)
[21:49] <rickspencer3> I "might" be working on a calorie lookup tool
[21:49] <SrPx> mhall119: so I mean, can I run gcc, git, ghc, node.js etc etc on it?
[21:50] <nik90> rickspencer3: hehe
[21:50] <nik90> rickspencer3: if you are, pls add you app at https://wiki.ubuntu.com/Touch/AppShowdownList
[21:50] <rickspencer3> nik90, will do
[21:50] <nik90> rickspencer3: that's where I am tracking the apps being developed for the showdown.
[21:50] <rickspencer3> :)
[21:51] <rickspencer3> about to head out though
[21:51] <nik90> okay
[21:51] <nik90> mhall119: did you know we have a new app called saucybacon :)
[21:51] <rickspencer3> I met a Ubuntu user at the deli during lunch yesterday, going to go get a drink with him in a bit :)
[21:51] <rickspencer3> good times
[21:51] <nik90> rickspencer3: enjoy
[21:52] <mhall119> SrPx: I haven't tried most of those, but I believe so.  I can (and have) run bzr and gcc on it
[21:52] <mhall119> nik90: yeah, the guy who posted it on Reddit was in here, last night I think
[21:53] <mhall119> rickspencer3: I love wearing my Ubuntu shirts in public, regularly get approached by strangers about it
[21:53] <rickspencer3> yeah
[21:53] <mhall119> my wife hates it though :)
[21:53] <mhall119> kinda spoils date nights
[21:53] <rickspencer3> I had my goobuntu shirt, that gets a lot of questions
[21:53] <balloons> mhall119, haha
[21:54] <balloons> I make my wife wear a ubuntu shirt too.. date night saved!
[21:54] <balloons> :-p
[21:54] <mhall119> speaking of, I need to report a wishlist bug she pointed out using the phone today
[21:59] <sander^home> Will there be a docking station for ubuntu edge? with bluetooth/usb/hdmi/power
[22:08] <balloons> ping boiko
[22:08] <boiko> balloons: pong
[22:09] <balloons> boiko, it seems like calculator no longer lets me use the plus/minus key on the first number
[22:09] <balloons> boiko, I believe it has to do with this merge: https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1210873
[22:09] <boiko> balloons: yes, I was discussing this with the developer, but someone else ended up approving the change
[22:10] <balloons> boiko, :-( Well the autopilot tests agree, and started failing this morning
[22:10] <balloons> shall we back it out?
[22:10] <boiko> balloons: either that or open a bug to track the issue
[22:11] <boiko> balloons: btw, I need to get the autopilot tests enabled for the calculator-app CI and autolanding ASAP
[22:11] <balloons> boiko, I'm opening a bug either way. .I have a small fix to the tests I wanted to make
[22:11] <annerajb> ogra_,  can you send me the diff again i lost the change
[22:11] <boiko> fginther: would it be possible to enable autopilot for ubuntu-calculator-app CI and autolanding?
[22:12] <fginther> boiko, sure I'll give it a test first
[22:12] <boiko> fginther: thanks! :)
[22:12] <balloons> fginther, boiko
[22:12] <balloons> http://91.189.93.70:8080/job/generic-mediumtests/345/
[22:13] <fginther> beat me to it
[22:13] <boiko> balloons: so, tomorrow I have a meeting with the calc guys, I will talk about this problem (and ask the other guys to be more careful when reviewing MRs)
[22:13] <boiko> balloons: fginther: thanks
[22:13] <balloons> boiko, it seems to be reported: https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1210082
[22:14] <boiko> balloons: but that I think is for that +/- button, isn't it? not for pressing the + or the - buttons, but anyway, this will be fixed tomorrow
[22:14] <balloons> boiko, either way, ok.. thanks :-)
[22:15] <balloons> boiko, have a review if you wouldn't mind tonight.. one line change https://code.launchpad.net/~nskaggs/ubuntu-calculator-app/fix-swipe/+merge/180260
[22:16] <boiko> balloons: ok, it looks good, I will just wait for CI to run
[22:23] <balloons> boiko, fginther the negative operand bug and the swipe bug fail on the run :-)
[22:24] <boiko> balloons: so, on your MR the mediumtests didn't run, was that expected?
[22:24] <fginther> balloons, was that a good thing?
[22:25] <balloons> boiko, yes, expected because it's not turned on.
[22:25] <balloons> fginther, well a good thing because that's all that failed was the known issue
[22:25] <boiko> balloons: ok, approved then
[22:26] <balloons> boiko, the trouble is we can't enable them now that they are broken.. but had we had them enabled, we wouldn't have pushed in the broken tests and code :-(
[22:27] <boiko> balloons: nah, just enable them, they guys will have to fix the bug before merging any new code ;)
[22:28] <boiko> balloons: or better, wait until tomorrow, I will bring that up in the meeting and after that we enable it
[22:35] <slangasek> awe, cyphermox: so I have been finding this week that Ubuntu Touch is utterly unwilling to roam internationally for me automatically, and I can't select a network manually to connect to it.  Aside from updating my phone (which I haven't done in a bit, bug #1210347), is there anything else that you'd like me to do testing-wise while I still *am* roaming internationally? :)
[22:36] <awe> slangasek, roam mobile-data wise?
[22:38] <awe> slangasek, 0800 is pretty old in touch terms
[22:38] <slangasek> awe: voice
[22:38] <awe> slangasek, can you bite the bullet and do a fresh install instead of update?
[22:38] <slangasek> awe: made a lot of ofono progress, have you? :)  Ok, I'll update and see if that resolves anything
[22:38] <awe> slangasek, my code's being pulled from the archive now finally
[22:38] <awe> ;)
[22:39] <awe> and although the -dbg package is currently broken, it will be fixed shortly
[22:39] <awe> slangasek, once you update, can you please open a bug for this?
[22:39] <awe> slangasek, we have others canonical folks that are always roaming
[22:40] <awe> so I know it works
[22:40] <awe> the ofono scripts are super useful for helping to diagnose such problems as well
[22:40] <awe> 'specially 'list-modems'
[22:40] <slangasek> yes, I can
[22:40] <awe> you can view the current NetworkRegistration properties which should tell you whether you're registered at all
[22:41] <awe> slangasek, great
[22:42] <awe> slangasek, how much longer will you be 'a roaming'?  ;)
[22:42] <slangasek> awe: until Sunday
[22:42] <slangasek> after that, I can try to "roam" with foreign SIMs that won't actually work in the US :)
[22:44] <awe> haha
[22:44] <awe> ok.  i'm around tomorrow, but off on fri, so if you enter a bug, i'll make sure to take a look tomorrow and maybe we can work on the bug some more
[22:45] <slangasek> awe: ok, sounds good :)
[22:45] <awe> slangasek, have you considered signal strength coverage where you're at?
[22:45] <awe> just curious... signal str also should be available via list-modems
[22:46] <awe> anyhow, just grab the output from 'list-modems', and that'll be a good place to start
[22:54] <slangasek> awe: it's been a consistent problem when my other phone (android, local SIM) has a connection just fine
[22:55] <awe> which phone?  mako?
[22:55] <awe> slangasek, hey... I had to ask
[22:55] <slangasek> awe: oh, hahaha.  I still have ofono disabled with an upstart override since the last bug I was having. :P
[22:56]  * awe has so many menu choices for what to say next floating across his retinas
[22:56] <slangasek> awe: sorry to waste your time ;)
[22:57] <awe> no worries...  you've helped me out many times in the past
[22:57] <awe> but it definitely made me laugh
[22:57] <awe> reminds me of one of the first things i ever learned while working on network protocols
[22:58] <awe> "is it plugged in"
[22:58] <awe> ;)
[22:58]  * slangasek grins