[00:53] <themikem> Quick question: I've built the current (raring) image, and now I'm trying to move over to the flipped image.  How to I get phablet-dev-bootstrap pointed at the saucy code?  Doesn't seem to be an argument for which branch to use...
[00:54] <themikem> in other words, what command do I run to init a saucy phablet repo?
[01:09] <sebsebseb> hi
[01:14] <RAOF> Hello.
[01:24] <sebsebseb> RAOF: Ubuntu Touch is  simklar to Android since based on that mod ?
[01:24] <sebsebseb> yes ?
[01:25] <RAOF> Not really.
[01:25] <RAOF> Ubuntu Touch is about as similar to Android as Android is to Ubuntu (ie: they use the same kernel)
[01:26] <sebsebseb> RAOF: ok fine
[01:26] <sebsebseb> RAOF: so what about that Ubuntu Edge then?  the Ubuntu on their is usign Ubuntu Touch
[01:26] <sebsebseb> well if those phoens actasuly get made
[01:26] <RAOF> Correct
[01:27] <RAOF> Oh. Ubuntu Touch is like Android in that it's usable on phones and tablets, if that's what you mean.
[01:27] <sebsebseb> yeah I know a bit about it already, but  how differnet is to Android?
[01:28] <RAOF> Everything above the kernel is different
[01:28] <RAOF> As for user-experience, it's... different?
[01:29] <RAOF> It's quite a lot like desktop Unity, if desktop Unity were to be made as a phone/tablet UI?
[01:30] <sebsebseb> yeah seen some screnshots and videos of it
[01:30] <sebsebseb> ,but that's it really
[01:30] <sebsebseb> seems it's like you say Unity for phones
[01:36] <sergiusens> themikem: repo init -b phablet-saucy -u git://phablet.ubuntu.com/CyanogenMod/android.git
[01:36] <sergiusens> if you already have a repo sync for phablet-10.1
[01:36] <sergiusens> just do repo init -b phablet-saucy and repo sync
[03:20] <savedjuli> hi
[04:17] <xboxfanj> So they said the edge will work on sprint and Verizon, is that assuming volte or is it just data only?
[04:32] <Sarvatt> xboxfanj: its 100% assuming volte, it wont work for cdma for phone.
[04:33] <xboxfanj> OK that's what i figured
[04:33] <xboxfanj> Thanks
[04:33] <xboxfanj> Not sure i can gamble on Sprint to do that
[04:34] <xboxfanj> I guess i could buy a used one if they do though
[07:13] <sil2100> gusch: hi!
[07:14] <gusch> sil2100: ho
[07:14] <sil2100> gusch: we encountered some problems with gallery-app AP tests - those look like something changed in the ui-toolkit
[07:15] <sil2100> gusch: on the other hand, it seems not have been introduced just now, since it fails with todays version of ui-toolkit and also with the one from 31th
[07:15] <sil2100> gusch: let me show you a link to those, I'll create a bug report
[07:16] <gusch> sil2100: ok
[07:18] <sil2100> gusch: here are the test results - this test uses the already released ui-toolkit, which is strange
[07:18] <sil2100> gusch: we also got the same failure tooday on SDK tests using the latest daily ui-toolkit, as we run a few Apps tests on SDK stack releases
[07:18] <sil2100> (to make sure it doesn't break anything)
[07:18] <sil2100> Filling out bug
[07:22] <gusch> sil2100: where are the results?
[07:23] <sil2100> gusch: https://bugs.launchpad.net/gallery-app/+bug/1207647
[07:23] <sil2100> gusch: ah! Right, heh ;)
[07:23] <sil2100> gusch: I forgot to paste the link, but the bug has those
[07:23]  * sil2100 needs coffee
[07:26] <gusch> sil2100: omg - SDK changed the tabbar implementation  - I'll check/update the gallery autopilot tests
[07:28]  * sil2100 sighs
[07:28] <sil2100> didrocks: morning!
[07:28] <didrocks> hey sil2100!
[07:29] <didrocks> shouldn't we have some deprecation methods?
[07:29] <didrocks> especially on the sdk
[07:29] <sil2100> didrocks: we have #1207647 blocking the apps and sdk stacks
[07:29] <sil2100> LP: #1207647
[07:29] <didrocks> sil2100: this did block sdk as well, right, as we run their tests?
[07:29] <didrocks> thanks for opening the bug :)
[07:29] <didrocks> asac: not sure if you want to track that one ^
[07:29] <sil2100> didrocks: strange thing, since it didn't block SDK last time!
[07:30] <didrocks> sil2100: was it failing?
[07:30] <sil2100> didrocks: although now SDK clearly fails on gallery-app tess
[07:30] <sil2100> *tests
[07:30] <didrocks> I think we added those in between, right?
[07:30] <didrocks> (like since last time to detect that sdk breaks apps)
[07:30] <sil2100> didrocks: last time no, now it does, but it already released the changed one it seems - since as I wrote in the bug, Apps stack uses the released version of ui-toolkit and fails there ;/
[07:31] <sil2100> didrocks: which is strange as it should fail
[07:31] <sil2100> didrocks: since now SDK fails properly on the gallery-app tests
[07:31] <sil2100> But why didn't it during last release?
[07:32] <asac> lool: where are you?
[07:33] <didrocks> sil2100: btw, you can look at unity8 now as well :)
[07:33] <asac> didrocks: i cant track anything :)
[07:33] <didrocks> sil2100: let me check if we didn't had to set some relax on the treshold in past
[07:33] <asac> i will ask every day i guess
[07:33] <didrocks> asac: come on, you like doing this ;)
[07:33] <didrocks> asac: anyway, we'll push upstream
[07:34] <didrocks> and now there is a bug opened
[07:34] <sil2100> didrocks: already poked Saviq ;)
[07:34] <didrocks> sil2100: Saviq is travelling
[07:34] <didrocks> sil2100: please try bzoltan
[07:34] <bzoltan>  sil2100: yes sir
[07:35] <didrocks> sil2100: no relax, the treshold is 0
[07:35] <bzoltan> sil2100: didrocks:  Before anybody shouting "SDK fails" it would be fun to see the logs...
[07:36] <bzoltan> Kind of tired of watching failures what has nothing to do with the sdk :)
[07:37] <sil2100> bzoltan: there is a bug I pasted to gusch about that
[07:37] <bzoltan> sil2100:  details please
[07:37] <sil2100> One moment
[07:37] <sil2100> bzoltan: https://bugs.launchpad.net/gallery-app/+bug/1207647
[07:37] <sil2100> bzoltan: I don't assume anything! I just fill in bugs ;)
[07:38] <bzoltan> sil2100: I am watching ot
[07:38] <bzoltan> it
[07:38] <gusch> bzoltan: seems like SDK changed the nav-bar implementation, so I'll have to update the autopilot tests
[07:39] <bzoltan> gusch: seems or you know?
[07:39] <gusch> bzoltan: I looked about 1 minute on it - so for now I'm only assuming ...
[07:41] <bzoltan> gusch:  cool... just for the sake of good spirit :) would you be so kind to make sure that you point to the right place before tossing the SDK under the bus :) Recently it become very fashionable to blame the SDK without being sure that the problem is not caused by something else...
[07:41] <bzoltan>  sil2100: ^
[07:42] <sil2100> bzoltan: agreed, but as I said, I don't blame anyone! I just observe and fill in bugs so that everything can be recognized, so I said 2 bug targets ;p
[07:44] <bzoltan> sil2100:  No worries :) Noone got hurt :) I just would like to be very sure that it is really and SDK issue... before we jump on it and spend time to fix some other project's bug
[07:48] <ali1234> why is the compiled kernel suddenly too big for the boot partition on galaxysmtd flipped?
[07:51] <didrocks> gusch: so, who is looking at it a little bit closer?
[07:51] <didrocks> gusch: as this is blocking all stacks as SDK won't publish (as this test failed)
[07:51] <gusch> didrocks: give me 5 minutes, then I'll investiage
[07:51] <didrocks> gusch: ok, thanks, please keep us posted
[07:52] <didrocks> rather than finding who is to blame exactly, let's try to first get the things fixed as top priority
[07:52] <didrocks> unblocking everything
[07:52] <didrocks> then, we can see what we can do :)
[07:57] <ali1234> is a boot.img always a kernel and ramdisk?
[07:57] <Chipaca> yes
[07:58] <timp> gusch, bzoltan I changed the TabBar implementation
[07:58] <timp> I updated the emulators.py in UITK autopilot tests, I was assuming that apps use those, but I'm not really up-to-date on the tests
[07:58] <ali1234> ok, well the last working boot.img i have is 5.8MB... the new one is 10MB and the kernel alone is 8MB
[07:58] <bzoltan> gusch, sil2100: Let's arrange a public humilation session for timp :D
[08:00] <gusch> timp: ok - I'll have a look at your emulator.py and update the gallery tests
[08:01] <timp> gusch: you can see the changes here https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/tabs-restructure/+merge/177131 (search for emulators.py). they are not very big
[08:01] <timp> gusch: I think we should provide something like this as a library that the apps can call
[08:02] <timp> elopio: hi. We moved the discussion about the emulators here
[08:02] <elopio> hey.
[08:03] <timp> elopio: are the emulators from UITK ready to be used by the app autopilot tests?
[08:03] <timp> elopio: my MR that change the tab bar broke the tests in apps
[08:03] <elopio> timp: yes, the filemanager and dropping letters are samples of what needs to be done to use the emulators.
[08:05] <timp> gusch: do you need to do a quick fix now? the better solution seems to use the UITK emulators
[08:06] <gusch> timp: quick fix now (some people seem to be nervous here ;), and then I'll try to use your emulators
[08:06] <asac> ogra_: do you have a maguro?
[08:07] <elopio> gusch: while using the emulators, you can be sure that all the methods you call are going to work always, because they have selftests on the ui-toolkit branch. If a change on the ui toolkit breaks the emulator, it will not land.
[08:07] <timp> gusch: ok, sounds good. get_tabs_bar() seems straightforward to update (remove the New from "NewTabBar"), but I'm figuring out now how you use the result
[08:07] <elopio> timp, gusch: I'm sleeping now :) But I'll be up in ~6 hours in case you need a hand.
[08:08] <timp> elopio: sleep well :)
[08:08] <didrocks> gusch: it's not a question of being nervous or not, it's just how reactive can we be to get issues fixed and having the flow opened again
[08:08] <didrocks> so let's open the gate again! :)
[08:09] <timp> didrocks: did more apps tests break besides gallery?
[08:11] <timp> didrocks: the problem is that autopilot tests of apps make use of internal implemetation details of UITK, which do not need to be stable, but luckily elopio did work to solve that by starting an autopilot library in UITK that other apps can use
[08:11] <elopio> before I go, I think that a good fix for the tests is better in the long run, even if we need to close the daily releases while we get it implemented. I would use this failures as a sign that we have a high priority to use the emulators on the toolkit on all apps.
[08:11] <elopio> ...just sayin' :)
[08:12] <didrocks> timp: not more tests, but maybe more apps :)
[08:12] <popey> ogra_: should we be testing on --ubuntu-bootstrap now?
[08:12] <didrocks> timp: it's something that in any way apps can get access to?
[08:13] <didrocks> if so, sil2100 can unblock the stack and still publish
[08:13] <didrocks> then, next run will ensure that the tests are now running again
[08:13] <didrocks> but that would make the dashboard red
[08:13] <didrocks> so I can see an angry asac next to me :p
[08:15] <timp> didrocks: 10:03:55 < elopio> timp: yes, the filemanager and dropping letters are samples of what needs to be done to use the emulators.
[08:15] <ogra_> asac, indeed i do, what do you need ?
[08:15] <didrocks> timp: thanks, I was disconnected while you wrote that
[08:15] <timp> didrocks: ^ so I guess apps can get access to it, but how to do it I don't know, let's have a look at filemanager and dropping letters
[08:15] <didrocks> yeah
[08:15] <didrocks> so let's not release
[08:15] <timp> didrocks: I don't know all the details. elopio wrote that
[08:15] <didrocks> in case an app do that
[08:18] <ogra_> popey, we should test what utah tests to enhance the automation imho ...
[08:18] <timp> it is a larger MR than I was hoping for, but for filemanager, it is here https://code.launchpad.net/~elopio/ubuntu-filemanager-app/emulators/+merge/177070
[08:19] <ogra_> popey, (which means just flipped atm i guess)
[08:20] <asac> ogra_: folks said maguro is boot looping?
[08:20] <asac> hmm... just installed aug 1
[08:20] <asac> that seems to boot fine
[08:20] <ogra_> asac, rsalveti and i tested that last night and couldnt reproduce
[08:20] <ogra_> right
[08:20] <asac> gema: cant confirm its an issue
[08:20] <asac> gema: installed 0801 and it just worked
[08:20] <asac> gema: guess we need the exact scripts
[08:25] <xnox> ogra_: rsalveti: so yeah, last night's android upload has sqlite back in - both binary and .so
[08:25] <ogra_> xnox, great, thanks
[08:27] <popey> ogra_: ok
[08:27] <gema> asac: did you use phablet-flash?
[08:27] <asac> gema: sure
[08:28] <asac> phablet-flash --pending
[08:28] <gema> asac: ack, will ask rfowler and plars to work together in triaging this, then
[08:28] <gusch> sil2100 bzoltan didrocks timp here the quick fix: https://code.launchpad.net/~schwann/gallery-app/gallery-autopilot-navbar/+merge/178221 (timp can you maybe review it?)
[08:28] <timp> gusch: looks good, approving
[08:29] <didrocks> great! please ping us when the 2 are merged
[08:29] <timp> didrocks: 2? what's the second
[08:29] <timp> ?
[08:29] <didrocks> the filemanager one?
[08:30] <timp> didrocks: that was already merged, elopio referred to that MR so we can see how to use the uitk emulators in apps
[08:30] <didrocks> ah, great :)
[08:30] <didrocks> sil2100: so once the gallery-app is merged, can you please rekick the stack?
[08:30] <didrocks> if it publishes, then we can publish sdk + gallery
[09:01] <tsdgeos> ricmm: you there?
[09:06] <gusch> didrocks sil2100 gallery is merged
[09:08] <JamesTait> Good morning all, happy Friday and happy Ice Cream Sandwich Day! :-D
[09:08] <ogra_>  yay
[09:08] <ogra_> right on the spot for this weather :)
[09:08] <didrocks> gusch: thanks! sil2100 still around?
[09:08] <didrocks> ok, seems not, let me rerun it
[09:09] <didrocks> (done)
[09:48] <slangasek> rsalveti: so I'm trying to figure out whether the NM delta can't really be limited to the policykit policy after all; but with my dpkg-diverted && hacked-up policy, chewie isn't working, and I'm also not seeing any traffic with dbus-monitor --system.  Do you have any hints how to debug this - at least to the point that I can actually see the dbus traffic?
[09:56] <gusch> elopio: I'm trying to use the SDK autopilot emulators in gallery - but need some help, can you?
[10:01] <timp> gusch: 10:07:36 < elopio> timp, gusch: I'm sleeping now :) But I'll be up in ~6 hours in case you need a hand.
[10:01] <gusch> timp: ah - ok - thx
[10:03] <AskUbuntu> Ubuntu SDK: qmlscene shows a blank image - Ubuntu 12.04 | http://askubuntu.com/q/327778
[10:21] <gusch> timp: do you know how the MainView of the toolkit emulators is created? I only get a NoneType ... :(
[10:23] <gusch> timp: or do you know anyone who knows about how to use it (filemanager does not hep me :( )
[10:25] <ogra_> YAY !
[10:25] <ogra_> my first kernel patch since 2.0 times and it works :)
[10:33] <ogra_> asac, todays image build failed with a weird python-minimal errors ... i suspect the buildd is borked
[10:35] <cjwatson> yes, it's the usual panda damage (#ubuntu-release)
[10:35] <ogra_> yeah
[10:35] <ogra_> re-running, lets see
[10:35] <ogra_> if it fails again i'll ask for a reboot
[10:55] <dholbach> did any of the port maintainers (or other people who use a non-official) succeed flashing their devices with  lp:~sergiusens/phablet-tools/flash_change ?
[10:58] <diwic> sforshee, mfisch, hi, so I think PulseAudio needs to talk to powerd to make sure the system does not go into S3 while playing back audio. Do you have pointers to how to accomplish this?
[11:01] <Laney> mardy: please merge lp:~laney/ubuntu-system-settings/new-icon-paths
[11:02] <Laney> that or make those files not hardcode the directory
[11:03] <sforshee> diwic: I can help you out, but I'm not sure I agree that any audio playback should block suspend
[11:04] <diwic> sforshee, well, if you play back audio, you need to wake the CPU up every now and then to read more data and feed it into the DMA buffer?
[11:04] <diwic> sforshee, if the system suspends, audio playback will stop
[11:05] <sforshee> diwic: I would expect this to be a higher-level policy decision that we're playing some class of audio that needs to continue, even if it's to the detriment of battery life
[11:07] <diwic> sforshee, PulseAudio could check what type/class of audio is being played back and only request a wake lock on certain types of audio
[11:07] <sforshee> diwic: so long as PA has that sort of information I guess that's fine
[11:08] <diwic> sforshee, it seems like PA is the one that has the most information about what it is playing back at least
[11:08] <diwic> sforshee, since streams can carry classifications
[11:08] <mardy> Laney: oops, done
[11:08] <sforshee> diwic: so it can tell the difference between e.g. background mp3 playback and sound effects from some app?
[11:09] <diwic> sforshee, yes, at least if the app is well-behaving
[11:09] <mardy> Laney: did you debug that QNetworkAccessManager issue?
[11:09] <diwic> sforshee, and tags its streams accordingly
[11:09] <Laney> mardy: no, but I do have that plugin
[11:09] <sforshee> diwic: I don't want our power management predicated on apps behaving appropriately
[11:09] <Laney> mardy: looks like I might not need it if the design gets simplified
[11:12] <diwic> sforshee, do you have a better suggestion?
[11:13] <rah> this guide https://wiki.ubuntu.com/Touch/Porting says that the ubuntu filesystem is kept within a container
[11:13] <rah> is that still the case?
[11:15] <sforshee> diwic: I would expect whatever implements our media API for apps to make these decisions. Will apps actually talk to PA directly?
[11:16] <dholbach> I'm trying to reply to http://forum.xda-developers.com/showpost.php?p=44197859&postcount=5 - is there any reason calls, sms and 3g should not work on a galaxy nexus (using verizon)?
[11:16] <sforshee> diwic: My expectation would be that apps would have some kind of play_background_audio() API, and part of the implementation of that API would be to request the active state
[11:17] <pmcgowan> dholbach, verizon uses cdma which we do not yet support, if this is in reference to touch images
[11:17] <dholbach> pmcgowan, gotcha
[11:18] <diwic> sforshee, hmm. Do all apps use the SDK? What about "regular" ubuntu software, will they not run on the phone?
[11:19] <diwic> sforshee, I mean, if all apps use the SDK we could pull in some policy layer between the app and PA, but that just makes life harder for applications not using the SDK.
[11:21] <jounih> I'd imagine games and apps that do their own UI components from scratch wouldn't necessarily use the SDK
[11:22] <sforshee> diwic: I really don't know. That's probably a question for tvoss_
[11:23] <diwic> sforshee, well, from the discussions with tvoss_ he said it was okay to do it in PulseAudio
[11:23] <diwic> sforshee, but if you like we could set up some meeting about it if you have concerns about that
[11:23] <sforshee> diwic: I've got to run, but the documentation for powerd's dbus api is at https://wiki.ubuntu.com/powerd
[11:23] <sforshee> diwic: you want requestSysState and clearSysState
[11:23] <diwic> sforshee, thanks
[11:24] <pmcgowan> ogra_, I have a mako stuck at the boot screen
[11:24] <pmcgowan> ogra_, adb sees the device but I cannot shell in, anything to check?
[11:25] <pmcgowan> ogra_, nm it just booted, hmmm
[11:31] <rah> what is the "container" that ubuntu touch runs in?
[11:31] <popey> lxc
[11:32] <pmcgowan> rah, android components are int he container
[11:32] <pmcgowan> in the latest images
[11:32] <rah> pmcgowan: so the arrangement has changed recently?
[11:32] <pmcgowan> rah, around 1 month ago, the so called flip
[11:33] <rah> I see
[11:33] <rah> it looks like just control groups and whatnot
[11:33] <pmcgowan> the previous images had ubuntu in a chroot
[11:33] <rah> I see
[11:33] <rah> so nothing virtual
[11:33] <pmcgowan> no
[11:34] <rah> good :-)
[11:34] <dholbach> sent another call for help with updating ports and testing the new phablet-flash to http://forum.xda-developers.com/showthread.php?p=44206124#post44206124 (just in case anyone here is interested in helping out as well)
[11:39] <ogra_> rah, we boot natively into the ubuntu touch rootfs and fire up androids hardware layer in an lxc container to initialize the hardware ...
[11:39] <rah> ogra_: I see
[11:39] <rah> ogra_: why? :-)
[11:39] <rah> I mean, why use a container?
[11:39] <ogra_> would you prefer the old model of using a chroot for ubuntu ?
[11:40] <rah> why is the choice container or chroot?
[11:40] <ogra_> (running on top of a minimal android)
[11:40] <rah> why not just: execute?
[11:40] <ogra_> because the two systems function totally different
[11:40] <rah> for example?
[11:40] <timp> gusch: sorry, I don't know. I know that elopio created them
[11:41] <ogra_> ubuntu uses udev for managing device nodes (and has a certain standardized linux naming scheme apps rely on) ... android uses ueventd
[11:41] <rah> I see
[11:41] <ali1234> dholbach: why are you still posting the in progress guide? it's not materially different to the old guide in what it tells you to do, and does not work!
[11:41] <ogra_> you cant really use the same /dev for both at the same time without introducing massive issues you would have to hack around
[11:41] <rah> lxc can change mount points?
[11:42] <ogra_> lxc operates like a vm ... even though it isnt one
[11:42] <rah> interesting
[11:42] <rah> do the android components need modification to work with this setup?
[11:43] <ogra_> well, depends what you define as modified
[11:43] <ogra_> we rip out 90% of the android tree anyway since we only use the hardware abstraction layer
[11:44] <ogra_> but yeah, there are some minor additional adjustments
[11:44] <rah> I see
[11:44] <ogra_> i.e. we keep just enough android to make the binary drivers usable :)
[11:47] <davmor2> ogra_: whats with the touch images?   have they just not run enough all the 2.1 images are red on install and boot?
[11:48] <ogra_> davmor2, patience :)
[11:48] <ogra_> seems they just havent started yet
[11:49] <davmor2> ogra_: so just not run long enough then?
[11:49]  * popey has just flashed 20130802.1 here
[11:49] <ogra_> davmor2, the dashboard works asynchronous ... it only updates every n munites
[11:50] <davmor2> popey: I was about to do the same so checked the smoke test first and the see of red didn't fill me full of hope :)
[11:50] <davmor2> ogra_: ah fair enough
[11:53] <ogra_> davmor2, hmm, though looking at the logs it seems like it actually failed to install, seems the tests changed
[11:53] <ogra_> gema, ^^^
[11:53] <popey> gallery app looks broken if launched from the camera app
[11:53] <popey> but works if launched on its own
[11:53] <ogra_> gema, apparently the new "install-and-boot" test failed for all 0802.1 images
[11:53] <gusch> popey: works for me
[11:54] <popey> gusch: on 20130802.1?
[11:54] <gusch> popey: 20130801 ...
[11:54] <ogra_> 02.1 is only 20min old :)
[11:54] <popey> I'm fast ☻
[11:55] <ogra_> yeah
[11:55] <popey> it works after gallery has been launched at least once
[11:55] <popey> but if you flash, open camera, press button in bottom right to launch gallery, it fails
[11:56] <popey> now, is that a camera-app bug or a gallery-app bug? ☻
[11:58] <davmor2> popey: write it as a camera app bug and add gallery to the bug
[11:58] <popey> yeah
[12:00] <popey> https://bugs.launchpad.net/camera-app/+bug/1207720
[12:00] <davmor2> popey: open clock, set city to wolverhapmton, what time does it display?
[12:00] <popey> 1830
[12:00] <popey> (the year)
[12:00] <popey> (kidding)
[12:01] <davmor2> popey: for me utc is saying 12:01 wolves is saying 04:01
[12:01] <popey> davmor2: 13:01
[12:01] <popey> http://popey.com/~alan/device-2013-08-02-130142.png
[12:01] <davmor2> not quite sure what  happened there :)
[12:02] <davmor2> popey: ta I'll add it again and see what happens
[12:03] <popey> i added then tapped on it
[12:03] <davmor2> and now it's right :)
[12:03] <popey> magic
[12:03] <davmor2> popey: must of just been a minor glitch
[12:03] <popey> fat finger syndrome
[12:04] <davmor2> popey: possibly except that under wolverhampton there are 5 listings all of which are wolverhapton in the uk
[12:05] <davmor2> popey: I might of clicked before it had refreshed fully and got some random timezone
[12:06] <davmor2> popey: if I open camera and click on gallery I get the gallery but it takes a couple of attempts at opening
[12:07] <davmor2> popey: flashes grey, closes back to camera, then opens properly
[12:09] <ogra_> linker.c:1095| ERROR: Library 'libmaliinstr.so' not found
[12:09] <ogra_> GRMPF ...
[12:14] <xnox> HM?!
[12:14] <xnox> why would we need maliit on android side? or is this inside ubuntu?
[12:16] <popey> davmor2: i tried 3 times before it would launch
[12:17] <davmor2> popey: is that from a --pending or a --pending --wipe?
[12:17] <popey> its --pending, but it's a clean device
[12:18] <davmor2> popey: okay once we find out what is happening with the m-i-l I'll try a --wipe and see if that replicates it.
[12:22] <ogra_> xnox, android side ... on a galaxy S2
[12:23] <ogra_> cjwatson, heh, i liked "mantra" :) ... thanks for reminding me of the WI ... (/me closes, long done)
[12:25] <ogra_> xnox, seems the camera-app triggers something that wants to use this lib (and indeed falls over with white screen)
[12:33] <gema> ogra_: that means the image doesn't install
[12:33] <ogra_> gema, well, it surely does for popey and me
[12:33] <gema> ogra_: install-and-boot is our test for flashing and doing something small
[12:34] <gema> ogra_: looking
[12:34] <popey> i just did "phablet-flash --pending"
[12:34] <popey> alan@deep-thought:~$ adb shell cat /var/log/installer/media-info
[12:34] <popey> Ubuntu Saucy Salamander (development branch) - armhf (20130802.1)
[12:34] <gema> ogra_: maguro is broken
[12:34] <gema> ogra_: the phone itself
[12:34] <gema> ogra_: int he lab
[12:34] <ogra_> gema, yeah
[12:34] <gema> ogra_: I need paul and rfowler to look into that later today
[12:35] <gema> ogra_: and I don't know about grouper
[12:35] <gema> ogra_: but we enabled this test yesterday, so give us a couple of days to go through the hooks to make it work
[12:35] <ogra_> gema, install-and-boot seems to have failed for grouper and manta too though
[12:35] <gema> ogra_: yep, I see that
[12:35] <ogra_> k
[12:35] <gema> ogra_: plars will fix that
[12:36] <ogra_> yeah, i didnt want to be pushy, just report it :)
[12:39] <dholbach> ali1234, how is https://wiki.ubuntu.com/Touch/PortingFlippedInProgress?action=diff&rev2=13&rev1=1 "not materially different"?
[12:41] <ali1234> dholbach: the instructions for checkout and building a port are identical. those notes only apply *after* you have done that
[12:42] <ali1234> and also they are device specific anyway
[12:43] <dholbach> ali1234, well, there are always going to be device-specific parts - thanks in any case for bringing it up on the mailing list
[12:51] <ali1234> i'm currently trying to build vanilla cyanogenmod to see if it also builds a bloated 8MB kernel
[12:51] <ali1234> but it keeps failing on some proprietary app :(
[12:56] <ogra_> ali1234, woah, 8M ?
[12:56] <ali1234> yeah i know
[12:56] <ali1234> this didn't happen with the unflipped image, when it still worked
[12:56] <ali1234> boot is only 7MB and the ramdisk is another 2MB
[12:56] <ogra_> yeah
[12:56] <ogra_> i havent seen a kernel above 5M yet
[12:56] <ali1234> so somehow i need to trim 3MB from the kernel
[12:56] <ogra_> in android
[12:57] <ogra_> you could repack the ramdisk and remove adbd and libcrypto.so
[12:57] <ali1234> that won't help given that the kernel alone is bigger than boot
[12:58] <ogra_> ah, your boot partition is 8M ? yeah, then it wouldnt
[12:58] <ogra_> i wonder why it got bigger for you though ... its not like we touch kernel configs of ports in any way
[12:58] <ali1234> well for one thing samsung uses a non standard boot.img format
[12:58] <ogra_> (and the configs for the supported devices  comes from packaged kernels)
[12:59] <ali1234> they are probably using lzma or something, to fit their massive kernel in it
[12:59] <ogra_> yeah, i know ... thats what my last mail to the ML was about
[12:59] <ogra_> for the galaxy S2 though
[12:59] <ali1234> anyway, if i can see how vanilla CM does it, i will know what the problem is
[12:59] <ogra_> they do, but that hasnt changed since before the flip
[12:59] <ali1234> if i can get it to build that is
[12:59] <ali1234> er... but it has changed
[13:00] <ogra_> it can only be a change on the CM side
[13:00] <ali1234> the unflipped images also no longer work for me
[13:00] <ogra_> as i said, we dont touch kernel configs ... the porter has to do that himself
[13:00] <ali1234> in the flipped image it uses mkbootimg, that's where it fails
[13:00] <ogra_> but since your kernel gets most likely pulled from CM i would blame them
[13:01] <ogra_> mkbootimg doeesnt have anything to do with the kernel config though
[13:01] <ali1234> the last time i successfully built an ubuntu touch image, it had a boot.img without the "Android!" magic, ie it's a none standard samsung one
[13:01] <ogra_> it is called after your kernel was built
[13:01] <ali1234> exactly
[13:02] <ali1234> the last time i successfully built ubuntu-touch, it didn't use mkbootimg
[13:02] <ali1234> it used whatever tool samsung uses
[13:02] <ali1234> but since i no longer have the source of that version, i can't compare
[13:02] <ali1234> hence trying to build CM
[13:04] <ali1234> it may be as simple as hacking the script to use a different version of mkbootimg, one that uses different compression
[13:04] <ali1234> like maybe they disabled compression on the kernel build and put it into mkbootimg?
[13:04] <ali1234> /home/al/Source/ubuntu-touch/cm/out/target/product/galaxysmtd/obj/STATIC_LIBRARIES/libwebcore_intermediates/Source/WebCore/bindings/V8SVGRectElement.cpp:373:1: internal compiler error: Segmentation fault
[13:04] <ali1234> fun
[13:10] <ogra_> wow
[13:10] <ogra_> gallety app looks really bad on http://reports.qa.ubuntu.com/smokeng/saucy/image/3316/gallery-app-autopilot/  (mako on 0802.1)
[13:12] <ali1234> is "make out/target/product/galaxysmtd/kernel" a valid thing to do?
[13:13] <ali1234> no
[13:13] <ogra_> go into the kernel subdir and call make Image
[13:13] <ogra_> *make zImage
[13:13] <ogra_> (my Z key is wonky)
[13:13] <ali1234> that won't tell me what i need to know
[13:13] <ali1234> well, i suppose it might
[13:13] <ogra_> ah, k
[13:14] <ogra_> i thought you wanted to get a kernel binary quickly
[13:14] <ali1234> supposing i do that and the kernel comes out at 5MB, what then?
[13:14] <ali1234> no, i want to know how cyanogenmod fits an 8MB kernel into a 5MB boot.img :P
[13:14] <ogra_> oh, you should copy the right defconfig file to .config in that dir
[13:14] <ogra_> before building :)
[13:14] <ali1234> and where do i find the right one?
[13:15] <ogra_> in the kernel subdir it should be in arch/arm/configs/
[13:15] <ogra_> usually named after your device
[13:15] <ali1234> yeah with about 5 million others
[13:15] <ogra_> (i,e, i have a cyanogenmod_i9100_defconfig for the galaxy S2 in use)
[13:16] <ali1234> ah yeah
[13:16] <ogra_> knowing the SGS2 is an i9100 makes it easy :)
[13:16] <ali1234> of course there is no guarantee that's the one it actually uses
[13:16] <ogra_> there surely is an xml or .mk file where it is defined what brunch uses
[13:17] <ali1234> CONFIG_INITRAMFS_SOURCE="source/usr/galaxysmtd_initramfs.list"
[13:17] <ali1234> CONFIG_INITRAMFS_COMPRESSION_NONE=y
[13:17] <ogra_> (i never needed it so i never searched)
[13:17] <ali1234> maybe that's why it's so big?
[13:17] <ogra_> nah
[13:17] <ogra_> that would be referring to ramdisk.img only
[13:17] <ogra_> look at the kernel comprerssion instead
[13:18] <ogra_> my SGS2 indeed uses lzma here
[13:18] <ogra_> not sure what you have
[13:18] <ali1234> CONFIG_KERNEL_LZMA=y
[13:18] <ogra_> yeah, the same
[13:20] <ali1234> if i do make zImage i also need to export ARCH and CROSS_COMPILE and so on...
[13:20] <ogra_> i'd check the if CM has made any config changes between 10.1 and 10.2 ... look for something that was modular before and isnt anymore
[13:20] <ali1234> i'm not using 10.2
[13:20] <ogra_> -the
[13:20] <ogra_> you are using phablet-saycy, no ?
[13:20] <ogra_> *saucy
[13:20] <ali1234> yes
[13:21] <ogra_> iirc rsalveti based that on 10.2
[13:21] <ali1234> but saucy doesn't contain repos for galaxysmtd
[13:21] <ogra_> ah. you mean your added stuff points to 10.1 ?
[13:21] <ali1234> yeah, i think so
[13:21] <ali1234> only the parts i changed though
[13:22] <ali1234> breakfast adds 5 repos, 3 of which i changed to my own
[13:24] <ali1234> i rebased my kernel tree on cm-10.1 latest
[13:24] <ali1234> i think i will revert back to exactly what i had last time it worked
[13:25] <ogra_> well, we stopped building unflipped userspace a while ago
[13:25] <ali1234> yes, i mean just revert the kernel source
[13:26] <ogra_> ah
[13:26] <ogra_> yeah
[13:26] <ali1234> trying now
[13:26] <ali1234> do i need to do anything to get a clean build?
[13:29] <ali1234> make  -C kernel/samsung/aries O=/home/al/Source/ubuntu-touch/phablet/out/target/product/galaxysmtd/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /home/al/Source/ubuntu-touch/phablet/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-" zImage
[13:29] <ali1234> is what it actually does
[13:29] <AskUbuntu> Ubuntu Touch OS | http://askubuntu.com/q/327832
[13:29] <oSoMoN> Kaleo: hey, what’s the issue with the font size in QtWebKit?
[13:30] <rsalveti> morning
[13:30]  * rsalveti reading backlog
[13:32] <ali1234> nope. identical kernel source, still doesn't work
[13:32] <rsalveti> slangasek: cyphermox spent quite a few days trying to just disable the policy part of it, and in the end he was still unable to make the indicator to create the connection, that's when he gave up
[13:33] <rsalveti> slangasek: so unfortunately I don't know much more about that specifically, and cyphermox will be back on monday
[13:35] <sergiusens> xnox: maliit != mali
[13:36] <ogra_> ali1234, btw, since your device seems to use the same shitty bootimg design my SGS2 has, you might need the patch i posted to the ML today
[13:37] <ogra_> sergiusens, heh, lol, i didnt even notice that :)
[13:38] <slangasek> rsalveti: ack, understood.  fwiw I got my dbus-monitor issue sorted, apparently there's a wiki page for that (thanks, robert_ancell :) - so the method is being called and NM is seemingly ignoring the request, still working on understanding why this is
[13:39] <Saviq> mhall119, not yet
[13:39] <slangasek> rsalveti: I'd rather do this than add a separate binary package now that we'll have to futz with later, but I'll timebox it so if I don't get it done by Monday we fall back to the really-quick-and-extra-dirty option :)
[13:42] <rsalveti> ogra_: libmaliinstr.so seems to be a blob
[13:43] <Stskeeps> it's a instrumentation extension, can be ignored, not fatal from what i know?
[13:43] <rsalveti> ogra_: phablet-flash is based on 10.1.2 :-) 10.2 is based on AOSP 4.3
[13:43] <rsalveti> Stskeeps: cool, ogra_ ^
[13:44] <rsalveti> slangasek: exactly, that's what we requested cyphermox to do as well, but he had to give up after 2,3 days
[13:45] <rsalveti> and he's back on monday as well, so make sure you sync with him before pushing the quick and dirty one :-)
[13:45] <slangasek> rsalveti: so if cyphermox wasn't able to crack it, I won't feel bad if I also fail - but I'll try all the same. :)
[13:45] <rsalveti> :-)
[13:46] <ogra_> Stskeeps, well, thats the error logcat shows if i try to start the camera app or ant media playback
[13:46] <ogra_> *any
[13:46] <Stskeeps> hmm
[13:47] <Stskeeps> it's not my belief it's anything but a warning, perhaps caused by dlopen
[13:47] <rsalveti> ogra_: just that error?
[13:47] <ogra_> so i assume the SGS2 might actually make use of it
[13:48] <ogra_> rsalveti, one sec, need to boot
[13:50] <ogra_> hmm, odd, now it doesnt boot
[13:51] <rsalveti> ogra_: :-)
[13:51] <ogra_> http://paste.ubuntu.com/5940127/
[13:52]  * rsalveti hugs sforshee, my device was off but still with a bit of battery
[13:52] <rsalveti> could boot and charge :-)
[13:52] <ogra_> oh, powerd got critical shutdown ?
[13:52] <ogra_> nice
[13:53] <rsalveti> landed last week afaik
[13:53] <rah> is ubuntu touch usable?
[13:53] <ogra_> we need to get rid of the charget stuff ...
[13:53] <ogra_> *charger
[13:53] <rsalveti> ogra_: so that's just the linker complaining about the missing library
[13:53] <ogra_> it annoys me massively
[13:53] <rsalveti> that doesn't necessarily cause any issue
[13:53] <rsalveti> ogra_: try stopping the shell and starting just the camera app
[13:53] <ogra_> rsalveti, hmm, k then its something else
[13:54] <ogra_> might be device access issues still
[13:54] <rsalveti> ogra_: or the camera test app from libhybris
[13:54] <rsalveti> right
[13:54] <ogra_> though max said he had camera and media playback working in unflipped
[13:54] <rsalveti> if you see maguro, it'll always complain about missing libraries
[13:54] <ogra_> (he funnily also has gprs working just fine ... but no calls/SMS)
[13:55] <ogra_> rah, there are people using it on a daily basis as their main phone
[13:56] <ogra_> rah, i wouldnt give it to my Mom yet
[13:56] <rah> ogra_: cool thanks
[13:56] <Kaleo> oSoMoN: I suppose the patch supporting the grid unit definition/pixel ratio has not been ported to Qt5.1
[13:56] <Kaleo> oSoMoN: since it won't be necessary thanks to qtubuntu feeding the right information to the whole of Qt
[13:56] <Kaleo> https://bugs.launchpad.net/webbrowser-app/+bug/1207270
[13:57] <oSoMoN> Kaleo: really, qtubuntu has been fixed in this regard? hurray!
[13:57] <Kaleo> oSoMoN: no it has not :)
[13:57] <Kaleo> oSoMoN: but it will be done next week
[13:57] <oSoMoN> then hurray all the same!
[13:59] <dholbach> sergiusens, did you get much feedback on your branch? some success stories? :)
[14:00] <sergiusens> dholbach: not really
[14:01] <dholbach> all right, I'll mail the port maintainers again - will this require a flipped port already?
[14:01] <sergiusens> dholbach: no, it would work with anything
[14:02] <dholbach> gotcha
[14:02] <sergiusens> dholbach: as long as you specify the 2 zips
[14:04] <ogra_> rsalveti, so i think there is something else http://paste.ubuntu.com/5940176/
[14:05] <rsalveti> ogra_: not sure if those are fatal
[14:05] <rsalveti> ogra_: I believe they will happen even if you start with maguro
[14:05] <rsalveti> or mako
[14:05] <mhall119> Saviq: not yet what?
[14:06] <ogra_> hmm k
[14:06] <ogra_> so how do i debug that :/
[14:07] <Saviq> mhall119, not yet tests for HUD
[14:07] <Saviq> mhall119, well, there are some, but testing unity8 itself, not integration
[14:08] <mhall119> ah, ok
[14:08] <rsalveti> ogra_: what is the ui behavior?
[14:08] <mhall119> is that something we can write tests for?
[14:08] <ogra_> white screen
[14:08] <rsalveti> let me check the hybris test here
[14:08] <rsalveti> hm
[14:08] <ogra_> for camera as well as movie playback
[14:08] <rsalveti> so the camera app is not even started somehow
[14:08] <ogra_> right
[14:10] <ricmm> tsdgeos: whats up
[14:10] <tsdgeos> ricmm: https://code.launchpad.net/~aacid/platform-api/mirftbfs
[14:11] <rsalveti> ogra_: I know sergiusens had some camera hal tests already
[14:11] <rsalveti> sergiusens: is that public somehow?
[14:11] <ricmm> tsdgeos: ah shit, so thats why get_native(surface) was failing
[14:12] <ricmm> tsdgeos: lemme test real quick and ill happrove
[14:12] <sergiusens> rsalveti: I have it in a branch, but I broke them yesterday
[14:12] <tsdgeos> ricmm: tbh i have not tested it because i have no clue when taht gets called
[14:12] <rsalveti> ogra_: I can run test_camera here, but it seems I'm not getting anything in the screen (but can take pictures and such)
[14:12] <rsalveti> sergiusens: haha, ok :-)
[14:12] <ricmm> tsdgeos: it gets called on creation of a surface
[14:12] <ricmm> the native type is requested
[14:13] <sergiusens> rsalveti: my tests were headless, so if screen integration is what you were looking for, that's how I broke the tests yesterday, being a GL noob
[14:13] <ricmm> sergiusens: noob
[14:14] <sergiusens> ricmm: yup, and proud :-)
[14:14] <rsalveti> ogra_: try running test_camera
[14:14] <sergiusens> rsalveti: I'll have to do some weekend reading or see if I can get some help from gusch later today/monday
[14:14] <rsalveti> sergiusens: got it, but guess for now just testing if the hal itself is working should be good (for what ogra needs)
[14:14] <ogra_> should it do anything ?
[14:15] <rsalveti> sergiusens: cool
[14:15] <rsalveti> ogra_: press the power button, should take a picture
[14:15] <ogra_> hmm
[14:15] <rsalveti> ogra_: http://paste.ubuntu.com/5940205/
[14:16] <ogra_> mine sits at line 2
[14:16] <ogra_> forever
[14:16] <rsalveti> ogra_: even as root?
[14:16] <ogra_> yeh
[14:16] <ogra_> *yeah
[14:17] <gusch> sergiusens: today?!? not very likely ;)
[14:17] <rsalveti> ogra_: if so, I'd guess it's hanging when trying to connect with the camera service
[14:17] <sergiusens> gusch: I know, hence the /Monday which means next week
[14:17] <rsalveti> ogra_: strace?
[14:17] <sergiusens> :-)
[14:17] <ogra_> rsalveti,  of the test ?
[14:17] <ogra_> one sec
[14:17] <rsalveti> ogra_: yeah
[14:17] <ogra_> sigh
[14:17] <sergiusens> logcat is very verbose with the camera
[14:17] <ogra_> why the heck dont we ship strace by default
[14:18] <rsalveti> ogra_: yeah, both strace and logcat please :-)
[14:18] <rsalveti> ogra_: indeed
[14:18] <rsalveti> it was just like wget
[14:18] <rsalveti> command not found
[14:18] <ogra_> do we have a logcat package ?
[14:18] <rsalveti> hahah
[14:18] <rsalveti> but we have it now because of click packages
[14:19] <ogra_> yeah
[14:19] <rsalveti> ogra_: nops, just use the android binary
[14:19] <ogra_> oh, i thought logcat in the seeds, heh
[14:19] <ogra_> my brain is borked today ... 32C and rising here
[14:20] <slangasek> rsalveti: please review https://code.launchpad.net/~vorlon/ubuntu/saucy/lxc-android-config/nm-divert/+merge/178308 :)
[14:20] <rsalveti> haha, can imagine that's not that common for you
[14:20] <rsalveti> slangasek: sure, lemmecheck
[14:20] <slangasek> rsalveti: successfully tested on mako w/ stock NM
[14:21] <ogra_> http://paste.ubuntu.com/5940226/
[14:22] <ogra_> rsalveti, logcat doesnt move at all when i run the test
[14:23] <rsalveti> ogra_: hm, running logcat as root as well?
[14:23] <ali1234> right. the only difference between CM kernel and ubuntu touch kernel is the addition of the various required config options. these grow the kernel by 3M
[14:23] <ogra_> yep
[14:23] <rsalveti> weird
[14:23] <rsalveti> let me read the strace log
[14:23] <ogra_> i think i dont get through at all
[14:25] <sil2100> jamesh: are you still around?
[14:25] <rsalveti> ogra_: do you have the media service running in the android container?
[14:26] <ogra_> root@ubuntu-phablet:/# ps ax|grep media
[14:26] <ogra_>  1802 ?        Sl     0:00 /system/bin/mediaserver
[14:26] <ogra_> i moved the sensorservice from late_start to main though ...
[14:26] <slangasek> rsalveti: if you're happy with that patch, I'd love it to be uploaded today so we can scratch NM off the list :)
[14:27] <ogra_> but even without it moved it didnt work, so i dont think thats related
[14:28] <rsalveti> slangasek: yup, just doing a clean flash and will test it
[14:28] <slangasek> \o/
[14:29] <rsalveti> ogra_: interesting, comparing with mine (on maguro), the only difference is that it seems I get a reply over binder
[14:29] <rsalveti> and yours get stuck in there
[14:29] <ogra_> yeah
[14:29] <ogra_> thats waht i meant with "i dont get through"
[14:29] <rsalveti> that's the annoying part of not using just the hal, and also depending on a service
[14:29] <ogra_> i blame tvoss
[14:30] <rsalveti> the video playback must be hanging in a similar situation
[14:30] <rsalveti> as that also depends on the mediaservice
[14:30] <gusch> elopio timp can one of you review this? https://code.launchpad.net/~schwann/ubuntu-ui-toolkit/ui-autopilot-fix-toolbar-open/+merge/178311
[14:30] <ogra_> well, i have no sound
[14:30] <ogra_> so i'd blame video playback not working on that fact
[14:31] <rsalveti> yeah, sound would also go via binder
[14:32] <rsalveti> so it seems indeed an issue when trying to talk, over binder, with the media service
[14:32] <rsalveti> and why would that only happen with your port
[14:32] <ogra_> well, and why would the rest of the system work just fine
[14:32] <ogra_> doesnt ubuntuappmanager talk over binder too ?
[14:32] <rsalveti> ogra_: yup
[14:32] <ogra_> right
[14:33] <rsalveti> ogra_: try killing the mediaservice
[14:33] <rsalveti> that would get it restarted
[14:33] <ogra_> so the commmunication is generally possible
[14:33] <rsalveti> and then watch for logcat
[14:33] <rsalveti> indeed
[14:33] <janimo> ogra_, is there no manifest of the inlcuded packages and their versions for preinstalled saucy images?
[14:33] <ogra_> huh ? there should be
[14:33]  * ogra_ checks
[14:34] <ogra_> http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20130802.1/saucy-preinstalled-touch-armhf.manifest
[14:34] <ogra_> janimo, ^^^
[14:34] <ali1234> hmm... nope again
[14:35] <ali1234> identical, and i do mean 100% identical kernel source produces a 6MB kernel under one build system, and a 8MB kernel under another
[14:36] <Tassadar_> ali1234: is that only zImage, or the whole boot.img?
[14:36] <ali1234> both
[14:36] <janimo> ogra_, thanks my bad. I just eyeballed the page without using Ctrl-F :)
[14:36] <ali1234> boot.img is exactly the same file as "kernel" on galaxysmtd
[14:36] <janimo> manifest just hid well among manta, maguro and mako
[14:37] <ogra_> rsalveti, http://paste.ubuntu.com/5940282/ looks all fine
[14:37] <Tassadar_> ah, samsung devices, no idea how are they doing it)
[14:37] <ogra_> Tassadar_, in an awful way
[14:38] <rsalveti> ogra_: indeed, still fails after restarting the service?
[14:38] <ogra_> Tassadar_, its a three stage bootloader
[14:38] <ogra_> rsalveti, yup
[14:39] <ogra_> Tassadar_, with scripts in the middle somewhere
[14:39]  * Tassadar_ goes back to his nexii with 'nope!'
[14:39] <ogra_> heh
[14:39] <rsalveti> ogra_: argh, then guess we'd need more debugging enabled in the media service itself, to see if android is indeed getting the binder requests
[14:39] <rsalveti> what a pain
[14:40] <ogra_> rsalveti, well, its not a high prio
[14:40] <ogra_> i have put enough work time into it
[14:40] <rsalveti> it should all be easier later on once we switch to be only hal based
[14:40] <rsalveti> as that would just be loading the library and doing stuff
[14:40] <rsalveti> yeah
[14:40] <ogra_> the purpose of finding out to whats needed to get it to flipped is fulfilled already
[14:41] <ogra_> and it made me write a kernel patch ...
[14:41] <ogra_> the first one in ten years ... and it worked on first shot ... i'm so proud :D
[14:41] <rsalveti> :D
[14:44] <jodh> rsalveti: FYI, the upstart-local-bridge (the ubuntu side of the property watcher) is now in lp:upstart if you want to pull that and try it out locally.
[14:44] <jGleitz> Hey guys!
[14:44] <jGleitz> Maybe this is very obvious, but I was unable to find documentation about this anyway:
[14:44] <jGleitz> The Ubuntu SDK is said to have the u1db-feature integrated. If I get it right, this is a nice way for apps to store their data and have it available across different devices.
[14:44] <jGleitz> But: How do I use it?
[14:44] <rsalveti> jodh: awesome, will try it today still
[14:44] <rsalveti> looking forward for that :-)
[14:45] <ogra_> oh, i would have expected a slightly more intuitive name
[14:45] <popey> jGleitz: kalikiana is your man
[14:46]  * ogra_ noted you talked about upstart-local-bridge in the foundations meeting ... i wouldnt have gotten the connection to android from that name
[14:46] <jGleitz>  @popey: Thanks! Shat I message him directly via IRC?
[14:46] <jGleitz> *Shall
[14:47]  * dholbach hugs janimo
[14:47] <jodh> rsalveti: note there is no sample .conf file (as we can't know what the path will be), but something like this should work: http://paste.ubuntu.com/5940308/
[14:48] <jodh> rsalveti: we should prolly change that path to /dev/socket/upstart-local-bridge in that .conf and also in the android watcher code of course.
[14:48] <ogra_> jodh, oh, we use the android event elsewhere ... do you plan to keep it ?
[14:48]  * ogra_ will need to update the container stuff then
[14:48] <dholbach> janimo, thanks a bunch for your experience report
[14:49] <jodh> ogra_: it was just a suggestion. Maybe "android-init"?
[14:49] <rsalveti> jodh: awesome, indeed
[14:49] <ogra_> jodh, well, i can rename mine to android-container as well :)
[14:49] <jodh> rsalveti: adding --debug to the command-line could be useful initially too.
[14:49] <rsalveti> jodh: ok
[14:52] <ogra_> janimo, the SF hacks wont be needed anymore once we are on Mir ...
[14:56] <ali1234> this makes no sense
[14:56] <ali1234> the only thing that can be different is the compiler
[14:56] <ogra_> ali1234, well, it is samsung
[14:57] <ali1234> make  -C kernel/samsung/aries O=/home/al/Source/ubuntu-touch/cm/out/target/product/galaxysmtd/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /home/al/Source/ubuntu-touch/cm/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-" zImage
[14:57] <ali1234> this command produces a 8MB kernel in phablet and a 5MB kernel with cyanogenmod
[14:57] <ali1234> kernel/samsung/aries is identical in both cases
[14:57] <ali1234> the only other difference is the compiler used
[14:58] <ali1234> i am now going to test it externally to the repo, just to prove there's no other differences
[14:59] <ogra_> well, its weird
[15:00] <mfisch> Laney: would you have any use for having libglib2.0-bin installed by default ( to get gsettings for example)?
[15:00]  * janimo hugs dholback back
[15:00] <janimo> ogra_, I am looking forward to Mir landing
[15:03] <nexwave-mat1> morning guys
[15:04] <nexwave-mat1> I managed to build for my device on the phablet-saucy branch this morning. Now I'm wondering what the next step to getting the flipped container to boot is?
[15:05] <Chocanto> popey: Hey ! How are you ? :) Since libpoppler is available in saucy-proposed, the poppler-qml-plugin can be compile and packaged without any problems. Then, can we add this package to the coreapps PPA and make autolanding tests for it ? :)
[15:06] <nexwave-mat1> I can ADB straight into ubuntu but have no logcat command...
[15:07] <ali1234> android_prebuilt.git is the one with the compilers, right?
[15:08] <nexwave-mat1> ali1234, yes
[15:08] <popey> Chocanto: yes. fginther is the man you need for that
[15:08] <Chocanto> popey: OK thank you :)
[15:08] <Chocanto> fginther: ping ?
[15:09] <fginther> Chocanto, hello
[15:09] <salem_> sergiusens, ping
[15:09] <sergiusens> salem_: slow pong...
[15:09] <Chocanto> fginther: Hello :) I would like to add a package for core apps
[15:10] <salem_> sergiusens, hey, do you know what is going on with this MR?  https://jenkins.qa.ubuntu.com/job/telepathy-ofono-ci/5/console
[15:10] <sergiusens> salem_: give me a minute and I'll check
[15:10] <salem_> sergiusens, ok, thanks
[15:11] <fginther> Chocanto, libpoppler I see
[15:11] <fginther> or poppler-qml-plugin
[15:11] <Chocanto> fginther: the qml plugin :)
[15:11] <sergiusens> fginther: seems the telepathy-ofono project is broken
[15:12] <sergiusens> salem_: ^^
[15:12] <fginther> Chocanto, I can start the process of adding it. Will ping you when it's ready
[15:12] <fginther> sergiusens, how so?
[15:12] <Chocanto> fginther: Ok, thank you
[15:12] <sergiusens> fginther: no downstream projects
[15:12] <sergiusens> fginther: http://<IP_ADDRESS>:8080/job/telepathy-ofono-ci/
[15:12] <popey> thanks fginther
[15:13] <sergiusens> fginther: just gone...
[15:13] <salem_> sergiusens, broken? how?
[15:13] <sergiusens> salem_: it's not configured to build anything
[15:14] <salem_> sergiusens, ah, you mean the jenkins project:
[15:14] <salem_> ?
[15:14] <mfisch> ogra_: ping
[15:14] <sergiusens> salem_: yeah, sorry
[15:14] <ogra_> mfisch, hey
[15:14] <mfisch> ogra_: surfaceflinger is segfaulting, is there any suggestions to debug?
[15:14] <salem_> sergiusens, who can fix it?
[15:15] <ogra_> mfisch, hmm not really beyond logcat output, syslog, dmesg
[15:15] <mfisch> ogra_: I'm guessing this is the main issue: "F/SurfaceFlinger( 3388): couldn't create EGLContext"
[15:15] <mfisch> it tried a bunch of stuff before that to create one and then gave up
[15:15] <ogra_> no, thats normal
[15:15] <mfisch> ogra_: i thought "F/" was fatal?
[15:16] <fginther> sergiusens, it's jut not configured correctly. I'm guessing it got moved
[15:16] <sergiusens> salem_: I pinged fginther, probably an update of configs that broke it
[15:16] <ogra_> adb shell /system/bin/logcat -D | pastebinit
[15:16] <salem_> sergiusens, ok, thanks!
[15:16] <sergiusens> fginther: oh, I was guessing a push during a build
[15:16] <nexwave-mat1> ogra_, just wanted to say thanks for the help yesterday. I got everything building and am now ready to continue. You free to help some more?
[15:17] <ogra_> nexwave-mat1, not today, i'm rather busy, but i can surely answer one or the other occasional question
[15:17] <nexwave-mat1> ogra_, lol well my next question is after I have a booting build whats the next step?
[15:18] <ogra_> install the zip and see how it behaves
[15:18] <fginther> Chocanto, what is the correct launchpad branch for poppler-qml-plugin?
[15:18] <Chocanto> fginther:  lp:ubuntu-docviewer-app/poppler-qml-plugin
[15:18] <ogra_> you will either end up with a boot loop or it will stop in initrd and give you an adb shell ... or it will boot into the rootfs
[15:19] <nexwave-mat1> ogra_, I did. It boots and I can adb into ubuntu but it seams to be a very stripped down version
[15:19] <nexwave-mat1> not logcat and no /var/log/ directory
[15:19] <fginther> Chocanto, thanks
[15:19] <ogra_> so you see root@ubuntu-phablet ?
[15:19] <ogra_> or do you see root@android ?
[15:20] <ogra_> logcat isnt in $PATH ... you need to call it directly as /system/bin7logcat
[15:20] <ogra_> /system/bin/logcat
[15:20] <nexwave-mat1> ogra_, http://pastebin.com/iQU8Ph9e
[15:21] <ogra_> nexwave-mat1, thats the initrd, it didnt boot
[15:21] <rsalveti> slangasek: happroved your nm lxc-android-config change, mind merging and pushing that?
[15:21] <rsalveti> slangasek: will also remove nm from our ppa
[15:21] <rsalveti> seems it worked as expected :D
[15:21] <ogra_> nexwave-mat1, it did not find your rootfs
[15:21] <nexwave-mat1> ogra_, ok...
[15:22] <ogra_> nexwave-mat1, that happens if your partition name is not in the list
[15:22] <ogra_> i have to add it to the script
[15:22] <nexwave-mat1> ogra_, what do you need from me?
[15:22] <ogra_> nexwave-mat1, find /dev -name *by-name*
[15:22] <ogra_> lets see if thats right
[15:22] <nexwave-mat1> ogra_, can I make any mod right now to get ot to work?
[15:23] <ogra_> nexwave-mat1, yes, but we need the find the names
[15:23] <nexwave-mat1> ogra_, where do I search?
[15:23] <ogra_> ls /dev/disk/by-name and ls /dev/disk/by-partlabel
[15:23] <ogra_> that shoulkd suffice
[15:23] <slangasek> rsalveti: \o/
[15:24] <rsalveti> slangasek: once you push that, let's also spin a new image
[15:24]  * rsalveti removing nm from the ppa
[15:24] <nexwave-mat1> ogra_, I just resotred CM on my phone, can I give you the fstab file instead?
[15:25] <ali1234> ok the prebuilt repos are identical in CM and UT
[15:25] <ogra_> nexwave-mat1, no, that doesnt help
[15:25] <ali1234> so identical kernel source and identical compiler produces different results
[15:26] <ogra_> nexwave-mat1, we need the device names as udev in ubuntu sees them
[15:26] <nexwave-mat1> ok gimme a min ill reflash
[15:26] <ogra_> rsalveti, oh, i'm just finally updating meta for the unity8 drop ...
[15:26] <fginther> Chocanto, poppler-qml-plugin doesn't build yet, the dependency needs to be promoted from proposed
[15:26] <ogra_> rsalveti, i'll better wait then :)
[15:27] <rsalveti> slangasek: removed nm from the ppa, so after pushing the change (and getting it published), sync with ogra_ to spin a new image :-)
[15:27] <rsalveti> so we can test that properly before eod
[15:27] <fginther> Chocanto, http://<IP_ADDRESS>:8080/job/ubuntu-docviewer-app-poppler-qml-plugin-saucy-amd64-ci/1/console
[15:27] <Chocanto> fginther: Jenkin don't have the proposed repo ?
[15:28] <slangasek> rsalveti: lxc-android-config uploaded
[15:29] <ogra_> yay
[15:29] <fginther> sergiusens, I pushed a fix for telepathy-ofono
[15:29] <fginther> Chocanto, no, we don't use proposed
[15:31] <fginther> sergiusens, Chocanto gotta go. I'll be online after a few hours
[15:31] <Chocanto> fginther: Ok, we can wait, it will build when libpoppler will be promoted
[15:32] <ali1234> hmmmmmmmmmmm
[15:32] <ali1234> comparing System.map. guess what the first different offset is...
[15:32] <ali1234> the only difference between these kernels is that the one built by ubuntu has a huge initramfs compiled in to it
[15:32] <cjwatson> That could still take a little while - poppler is in the middle of a transition
[15:32] <ogra_> ali1234, *into* it ?
[15:34] <cjwatson> Though it does look like it's almost there
[15:35] <ali1234> yes
[15:35] <ali1234> c002d4c8 T __initramfs_start
[15:35] <ali1234> c06ad4c8 T __initramfs_size
[15:35] <ali1234> those symbols are consecutive in System.map and the latter is the first one that differs between the two kernels
[15:35] <ali1234> i suppose this is how samsung boot.img differs. instead of the Android! header it's just a raw zImage with compiled in initramfs
[15:35] <ali1234> then ubuntu tries to make that into a boot.img, appending yet another ramdisk
[15:35] <ogra_> you said kernel
[15:35] <nexwave-mat1> ogra_, # ls dev/disk/by-
[15:35] <nexwave-mat1> by-id/    by-path/  by-uuid/
[15:35] <ali1234> yes, kernel, as in zImage
[15:35] <nexwave-mat1> its all I got
[15:35] <ogra_> nexwave-mat1, very bad
[15:36] <nexwave-mat1> ogra_, >.<
[15:37] <ogra_> nexwave-mat1, i fear you have to wait until i fixed bug 1199084 (and indeed that will only work if you have a fully modifyable kernel cmdline
[15:37] <nexwave-mat1> ogra_, http://pastebin.com/iQU8Ph9e
[15:37] <ogra_> yeah thats doesnt help
[15:38] <rsalveti> diwic: you did remove alsa load/store in your image, right?
[15:38] <rsalveti> diwic: I wonder if that's causing issues with maguro with the default image
[15:39] <rsalveti> the device is crashing while initializing the sound, after a second reboot
[15:39] <nexwave-mat1>  ogra_, so nothing we can do at the moment?
[15:39] <ogra_> nexwave-mat1, you can hack up the touch script inside the initrd and see how much further you get with that
[15:39] <diwic> rsalveti, I believe you removed it for me
[15:40] <ogra_> nexwave-mat1, but not having properly labelled partitions will cause other issues later too
[15:40] <rsalveti> diwic: yeah, was thinking of pushing that to the default image
[15:40] <ogra_> rsalveti, ++
[15:40] <rsalveti> will do some more testing here, but will probably push that by default as well
[15:40] <ogra_> i tried it a week ago or so, didnt cause any harm on grouper and maguro
[15:40] <rsalveti> yeah, cool
[15:42] <diwic> rsalveti, sounds good to me too
[15:42] <rsalveti> diwic: ok, cool
[15:45] <janimo> ogra_, my graphics devnode addition was needed even after the device specific .rc
[15:45] <janimo> if it's a known issue on OMAP/SGX it may be the case for other devices too
[15:45] <diwic> rsalveti, for the Audio HAL talking to the baseband/modem, look at http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_hardware_qcom_audio.git;a=blob_plain;f=alsa_sound/AudioHardwareALSA.cpp;hb=HEAD and search for csd_start_playback / csd_stop_playback
[15:46] <ogra_> janimo, oh, sorry, please add it back then
[15:46] <nexwave-mat1>  ogra_, do you know the file location?
[15:46] <ogra_> nexwave-mat1, inside the initrd it is scripts/touch
[15:46] <janimo> ogra_, you can extend the adb shell call to glob ueventd.*.rc to cover all rc, it will add the emulator too
[15:46] <ogra_> janimo, perfect !
[15:47] <nexwave-mat1>  ogra_, sorry, where? on the phone, the zip, source?
[15:47] <ogra_> inside the initrd
[15:47] <ogra_> you need to unpack, edit and repack it
[15:47] <janimo> ogra_, done
[15:47] <nexwave-mat1>  ogra_, in the out directory?
[15:47] <ogra_> thx !
[15:48] <slangasek> ogra_: I'm being ushered out of the meeting room here at the sprint, can I leave it to you to track the lxc-android-config publication and respin the image when the time comes?
[15:48] <ogra_> nexwave-mat1, in your boot.img
[15:48] <ogra_> slangasek, sure, np
[15:49] <slangasek> ogra_: thanks!
[15:49] <ogra_> :)
[15:51] <ogra_> bah, cjwatson has beaten me ...
[15:51] <ogra_> my -meta update is still running ... chromebook is really not the device for that
[15:52] <ali1234> ogra_: http://imagebin.org/266312 left is ubuntu, right is CM. notice that boot.img == kernel == zImage and the difference in size between ubuntu and CM is roughly the same as the size of ramdisk.img
[15:53] <cjwatson> Sorry
[15:54] <rsalveti> diwic: oh, that's ugly
[15:54] <ogra_> cjwatson, heh, no problem :) i'm happy to have computing power back :)
[15:54] <rsalveti> why everything related with qcom must be proprietary
[15:55] <diwic> rsalveti, you think that's ugly? Look at Android 4.3. There, they set up the mixer specially if you're on the T-mobile US network. :-)
[15:55] <ogra_> ali1234, sorry that crashes here while loading
[15:56] <ogra_> i get half the pic loaded and then it dies and i end up  with a broken img icon
[15:56] <ali1234> it's just a png file. reload
[15:56] <ali1234> anyway the bottom line is that boot.img and zImage are identical files
[15:56] <rsalveti> diwic: lol, right
[15:56] <ali1234> and they already contain ramdisk.img
[15:56] <diwic> rsalveti, I don't think we need to worry about that though.
[15:57] <rsalveti> diwic: yeah
[15:57] <ogra_> ali1234, right and thus there should be no initrd inside
[15:57] <rsalveti> but we still need some sort of abstraction to handle that one
[15:57] <ali1234> ogra_: why should there be no initrd inside?
[15:57] <ogra_> it shouldnt be insice the zImage
[15:58] <ogra_> *inside
[15:58] <ali1234> that's what i'm saying
[15:58] <ali1234> it is
[15:58] <ali1234> it shouldn't be, but it is
[15:58] <ogra_> yes, and it shouldnt :)
[15:58] <ogra_> so we agree that we agree :)
[15:58] <ali1234> then when you mkbootimg you're trying to add another copy
[15:58] <ogra_> right, i assume your device might need some special code changes to the mkbootimg stuff then
[15:59] <ali1234> what is android-boot.img actually used for btw?
[15:59] <ogra_> it is the root of the container
[15:59] <ali1234> oh?
[15:59] <ogra_> android doesnt switch its / to the target disk
[15:59] <ali1234> wait
[16:00] <ali1234> so why does it need a copy of the kernel in it?
[16:00] <ogra_> so to boot the container we need to unpack the initrd to get /
[16:00] <ogra_> it doesnt
[16:00] <ali1234> ok
[16:00] <ogra_> oh, wait
[16:00] <ogra_> i'm mixing up things
[16:00] <ogra_> android-ramdisk.img is what i was referring to
[16:00] <ali1234> yeah, i don't care about that, that looks fine
[16:01] <ali1234> android-boot.img is whatever would have been boot.img in cyanogenmod
[16:01] <ogra_> right
[16:01] <ogra_> we dont need it ... we eed ubuntu-boot.img
[16:01] <ali1234> except it isn't, because it ends up with the huge ubuntu ramdisk in it instead of the cyanogenmod one
[16:01] <ali1234> yeah ubutu-boot.img is only in the raring branch
[16:02] <ali1234> in saucy you need android-boot.img instead, or the build crashes
[16:02] <ogra_> funny, my saucy build has ubuntu-boot.img
[16:02] <ali1234> the same error in the same place
[16:02] <ali1234> the only difference is raring asks for ubuntu-boot.img and saucy asks for android-boot.img
[16:03] <ogra_> well, the name shouldnt matter as long as the content is ok
[16:03] <ali1234> what is the content supposed to be?
[16:03] <ogra_> the kernel and the ubuntu ramdisk ... for "normal" android devices
[16:03] <ogra_> samsung is different
[16:03] <ali1234> ok
[16:04] <ogra_> and that difference needs to be ported to
[16:04] <ali1234> well that is what it contains for me, except built in the samsung way
[16:04] <ogra_> right
[16:04] <ogra_> but still the gigantic kernel
[16:04] <ali1234> no
[16:04] <ogra_> oh ?
[16:04] <ali1234> the kernel is only gigantic because it has ramdisk.img as an initramfs
[16:04] <ogra_> which it should
[16:04] <ali1234> it should for samsung, yes
[16:04] <ogra_> well not the kernel
[16:05] <ogra_> the boot.img  should ...
[16:05] <ali1234> there is no boot.img
[16:05] <ogra_> there is android-boot.img
[16:05] <ogra_> which i meant
[16:05] <ali1234> so what exactly is different between boot.img and android-boot.img?
[16:05] <ogra_> nothing, they are the same thing
[16:06] <ali1234> what?!?!?!?
[16:06] <ali1234> why does it need both files then?
[16:06] <ogra_> on all non samsung devices boot.img is what gets installed into your "boot" partition
[16:06] <ali1234> that is the same on samsung
[16:06] <ogra_> its not
[16:06] <ogra_> at least not on my device
[16:06] <ali1234> well it is on mine
[16:06] <ogra_> i have a separate kernel partition
[16:06] <ogra_> and a three stage bootloader
[16:06] <ali1234> anyway, this is my question
[16:07] <ali1234> if i don't have android-boot.img, the build dies
[16:07] <ogra_> in stage2 there is an /init script which switches between normal and recovery initrd
[16:07] <ali1234> if i don't have boot.img, it tries to build boot.img
[16:07] <ali1234> why does it need both?
[16:07] <ogra_> it doesnt
[16:07] <ali1234> yes it does
[16:07] <ali1234> this is the point where it dies
[16:08] <ogra_> it *needs* only one
[16:08] <ogra_> it builds two apparently
[16:08] <ali1234> it will only build one of them
[16:08] <ali1234> if you don't have the other one the build just crashes out
[16:09] <ogra_> well, in any case you need the one that has the ubuntu initrd inside on your device
[16:09] <ali1234> so in other words i just need to copy android-boot.img to boot.img
[16:09] <ogra_> thats the core of flipped images .. that and the lxc container
[16:10] <ogra_> if that gets installed by your zip, right
[16:10] <ali1234> it does
[16:10] <ali1234> android-boot.img is something only required by ubuntu touch
[16:10] <ogra_> yeah, then you need that
[16:10] <ali1234> by "required" i mean that if your device specific makefiles dont have a rule that build android-boot.img, the build fails with "no rule to make target..."
[16:11] <ali1234> that is the only reason it is needed
[16:11] <ali1234> it is apparently not used for anything
[16:11] <ogra_> rsalveti, any reason for that ?
[16:11] <ogra_> ^^^
[16:11] <ali1234> because it then builds boot.img again anyway
[16:11] <ogra_> well, as long as the downloaded initrd ends up in there all is fine
[16:12] <ali1234> i still need to trim about 500kb out of it somehow to fit it in boot
[16:12] <ali1234> but that's better than 3MB
[16:12]  * rsalveti reading
[16:12] <ogra_> did you already drop adbd and libcrypto ?
[16:12] <ali1234> no, i do not know how
[16:12] <ogra_> that alone should cut off more than 1M
[16:13] <ogra_> ali1234, the abootimg package ships scripts for that
[16:13] <ogra_> abootimg-unpack-initrd /path/to/initrd
[16:13] <ogra_> abootimg-pack-initrd <- this called in the same dir you called the above will pack it again
[16:14] <rsalveti> ali1234: android-boot.img is the original android-boot.img
[16:14] <ogra_> you get a directory tree and can just rm stuff in there
[16:14] <rsalveti> with flipped, the final boot.img that gets created is the one for ubuntu already
[16:14] <rsalveti> which contains the ubuntu specific initrd
[16:14] <ali1234> rsalveti: you mean the original android boot.img
[16:14] <ogra_> rsalveti, right, but thats confusing
[16:14] <themikem> Hi all.  I'm trying to build saucy, but I'm running into a "no rule to make target" error for sqlite3.  Any ideas?
[16:14] <ogra_> rsalveti, if we dont need the android one we should just drop it
[16:14] <rsalveti> ogra_: well, the default boot.img and ramdisk.img is now the one from ubuntu
[16:14] <ogra_> right
[16:14] <rsalveti> that's why the android ones are now called android-foobar.img
[16:15] <ogra_> but why do we buuld them at all ?
[16:15] <rsalveti> we need at least the android-ramdisk for the container
[16:15] <ogra_> yeah
[16:15] <ogra_> thats clear
[16:15] <rsalveti> the android-boot image can be dropped
[16:15] <ali1234> rsalveti: the trouble is that my android-boot.img is not the original android one
[16:15] <ali1234> it's the original android kernel + the ubuntu ramdisk.img
[16:15] <rsalveti> I just didn't do that because I wanted to know the original size of the android boot image
[16:15] <rsalveti> so you could compare and such
[16:15] <ogra_> yeah
[16:16]  * ogra_ understands
[16:16] <rsalveti> ali1234: it shouldn't be
[16:16] <ali1234> i know it shouldn't be!!!
[16:16] <ali1234> but it is!!!
[16:16] <ali1234> see my screenshot
[16:16] <rsalveti> give me the output of mka showcommands bacon
[16:17] <ali1234> this device the boot images are weird
[16:18] <ali1234> http://paste.ubuntu.com/5940639/
[16:18] <rsalveti>  /media/rsalveti/home/dev/android/build/saucy/out/host/linux-x86/bin/mkbootimg  --kernel /media/rsalveti/home/dev/android/build/saucy/out/target/product/maguro/kernel --ramdisk /media/rsalveti/home/dev/android/build/saucy/out/target/product/maguro/android-ramdisk.img --base 0x80000000  --output /media/rsalveti/home/dev/android/build/saucy/out/target/product/maguro/android-boot.img
[16:18] <rsalveti> this is how I'm getting mine
[16:18] <rsalveti> so it's using android-ramdisk to build android-boot.img
[16:18] <ali1234> this device does not use mkbootimg
[16:19] <ali1234> it combines the ramdisk and kernel at kernel build time. it puts it in a initramfs
[16:19] <ogra_> rsalveti, samsung generally doesnt use mkbootimg
[16:19] <ogra_> (and you cant unpack them with abootimg etc)
[16:19] <ali1234> so what happens is, i change the samsung makefile to output to android-boot.img instead of boot.img. this works, but includes the ubuntu ramdisk into the kernel
[16:19] <rsalveti> then it must be some sort of specific makefile from your device, which device is that?
[16:20] <rsalveti> so I can check the makefiles
[16:20] <ali1234> galaxysmtd
[16:20] <ali1234> anyway then it tries to make boot.img using kernel and ramdisk.img, but kernel already has ramdisk.img as a initramfs
[16:20] <ali1234> so this means the boot.img ends up huge because it has two copies of ramdisk
[16:21] <ali1234> i mean it's already too big with just one copy of ramdisk, two is right out...
[16:22] <ali1234> now, if android-boot.img is not used anyway
[16:22] <ali1234> then all i need to do is shrink down the ramdisk
[16:23] <ali1234> and then android-boot.img is what i actually want to boot from
[16:23] <ogra_> right
[16:23] <ali1234> since it's the device kernel and ubuntu ramdisk
[16:23] <rsalveti>   running:  mkbootimg --kernel /tmp/targetfiles-VNHHsb/BOOT/kernel --cmdline console=ttyFIQ0,115200 init=/init no_console_suspend --base 0x32000000 --pagesize 4096 --ramdisk /tmp/targetfiles-VNHHsb/BOOT/ramdisk.img --output /tmp/tmpTWPOL0
[16:23] <rsalveti> that ramdisk.img is indeed the ubuntu one
[16:24] <ali1234> the easiest way to achieve this is to not patch the samsung makefile to create android-boot.img. then it will create boot.img and everthing should be good
[16:24] <ali1234> except that then the build will die with "no rule to make android-boot.img"
[16:24] <rsalveti> ali1234: where is the rule that puts the ramdisk inside the kenrel?
[16:25] <ali1234> rsalveti: i have no idea
[16:25] <rsalveti> you don't want to boot from android-boot.img
[16:25] <ali1234> rsalveti: see http://imagebin.org/266312
[16:25] <ali1234> in this case i do
[16:25] <rsalveti> that will only get you android
[16:26] <ali1234> no, it won't
[16:26] <ali1234> it will get me the android kernel and ubuntu ramdisk.img
[16:27] <ali1234> compare the size of android-boot.img on the left and boot.img on the right. then compare the size of ramdisk.img.
[16:27] <rsalveti> right, in that case zImage is the boot image itself
[16:28] <ali1234> right, that's what i've been saying this whole time!
[16:28] <rsalveti> the only way for the ramdisk to be part of that, is from the kernel build scripts
[16:28] <ali1234> yes!
[16:28] <rsalveti> which I'm not so sure if that's indeed happening
[16:28] <ali1234> it is!
[16:28] <ali1234> both the kernels contain initramfs images approximately the same size as the ramdisks
[16:28] <ali1234> verified on System.map
[16:29] <ali1234> you can see a bit of it above the ls output
[16:30] <ali1234> notice that the two zImage's are in the KERNEL_OBJ dirs and are the same files also
[16:30] <ali1234> that dir is only written by the kernel build
[16:30] <ali1234> actually i pasted the full exact "make zImage" command which builds it above
[16:31] <rsalveti> right, but I'm not seeing how the kernel can contain the ramdisk in there
[16:31] <rsalveti> unless the kernel has a custom build rule
[16:31] <ali1234> i don't understand it either!
[16:31] <rsalveti> the only thing I'm seeing in there is that the android-boot, the kernel, recovery and zImage all have the same size
[16:31] <ali1234> but there is no other possible explanation
[16:32] <rsalveti> what could mean is that it couldn't find the recovery when creating those files
[16:32] <rsalveti> and all it created from was the kernel
[16:32] <ali1234> look at the lines above where i grepped System.map
[16:32] <rsalveti> not recovery, but the ramdisk, as the recovery is yet another ramdisk
[16:33] <ali1234> the cyanogenmod build completed without errors
[16:33] <ali1234> i doubt your explanation is likely :P
[16:33] <rsalveti>  /home/al/Source/ubuntu-touch/phablet/out/host/linux-x86/bin/acp -fp /home/al/Source/ubuntu-touch/phablet/out/target/product/galaxysmtd/obj/KERNEL_OBJ/arch/arm/boot/zImage /home/al/Source/ubuntu-touch/phablet/out/target/product/galaxysmtd/kernel
[16:33] <rsalveti> /home/al/Source/ubuntu-touch/phablet/out/host/linux-x86/bin/acp /home/al/Source/ubuntu-touch/phablet/out/target/product/galaxysmtd/kernel /home/al/Source/ubuntu-touch/phablet/out/target/product/galaxysmtd/android-boot.img
[16:33] <rsalveti> /home/al/Source/ubuntu-touch/phablet/out/host/linux-x86/bin/acp /home/al/Source/ubuntu-touch/phablet/out/target/product/galaxysmtd/android-boot.img /home/al/Source/ubuntu-touch/phablet/out/target/product/galaxysmtd/recovery.img
[16:33] <rsalveti> from your logs
[16:33] <rsalveti> that's why
[16:34] <ali1234> yes, it simply copies the files
[16:34] <rsalveti> so the kernel doesn't have the ramdisk in it
[16:34] <rsalveti> it's all just the kernel itself
[16:34] <ali1234> it has an initramfs which is almost exactly the same size as ramdisk.img
[16:35] <davmor2> popey: right I'm going to do a --wipe now and see if I can replicate your camera/gallery issue do you happen to have the bug number handy though?
[16:36] <rsalveti> ali1234: can you confirm that?
[16:36] <ogra_> ali1234, do an md5sum on kernel, android-boot.img and recovery.img ... they are just zImage by the above code
[16:36] <popey> davmor2: one mo
[16:36] <ali1234> ogra_: correct
[16:36] <popey> davmor2: https://bugs.launchpad.net/gallery-app/+bug/1207720
[16:36] <rsalveti> yeah, and it's failing when creating with mkbootimg
[16:36] <ali1234> rsalveti: yes, by looking at System.map
[16:36] <rsalveti> but you both said it shouldn't use mkbootimg
[16:37] <rsalveti> ali1234: give me the output of that
[16:37] <davmor2> popey: thanks
[16:37] <ogra_> well, that tree probably ships a vendor mkbootimg
[16:37] <mfisch> stgraber: do you have system image update changes for me to try today?
[16:37] <ogra_> i'm just judging by behavior of my samsung tree
[16:38] <ali1234> cyanogenmod kernel system map http://paste.ubuntu.com/5940704/
[16:38] <rsalveti> should be part of samsung_aries-common
[16:38] <stgraber> mfisch: I just pushed a new lxc-android-config and initramfs-tools-ubuntu-touch to the archive, ubuntu-touch-generic-initrd will follow in a few minutes
[16:38] <stgraber> mfisch: after that, the next build will give you a working /var/log/upstart
[16:39] <ogra_> stgraber, bah
[16:39] <mfisch> stgraber: okay, I have a hacked recovery that skips checking the signature so I can add my own custom tgz
[16:39]  * ogra_ was waiting for it to land to trigger a new image build
[16:39] <ali1234> ubuntu-touch kernel System.map http://paste.ubuntu.com/5940708/
[16:39] <ali1234> rsalveti: ^f,initramfs
[16:40] <ali1234> notice that it's the first thing with a different (ending) offset
[16:40] <stgraber> mfisch: haha, at some point I'll have to document how to create your own keys so you can just update the archive-master.tar.xz file in the recovery image and then have it flash images signed by an unofficial key (we'll need that for ports too)
[16:41] <mfisch> stgraber: "return 0" at the top of the validation function works pretty well too ;)
[16:41] <mfisch> stgraber: when we will be switching to these images full time?
[16:41] <ogra_> mfisch, after click packages fully landed
[16:41] <rsalveti> ali1234: ogra_: http://paste.ubuntu.com/5940714/
[16:42] <ali1234> yep
[16:42] <ali1234> that's the makefile where i changed boot.img to android-boot.img
[16:42] <mfisch> ogra_ / stgraber: how will click packages deal with the RO folders? do they get installed outside it?
[16:42] <ogra_> yeah
[16:42] <ali1234> in order to make the annoying "no rule to make target..." go away
[16:42] <ogra_> click installs in the rw space
[16:43] <rsalveti> to get the android ramdisk, change INSTALLED_RAMDISK_TARGET to INSTALLED_RAMDISK_TARGET_ANDROID
[16:43] <mfisch> ogra_: but we cannot install any extra packages there I assume
[16:43] <mfisch> ogra_: for example, a chinese build may want some different fonts
[16:43] <ali1234> ok, but why do i need that?
[16:43] <ogra_> mfisch, we can ... but for a chinese img i would do that in a separate image build as debs
[16:44] <rsalveti> ali1234: in case you wanted to generate the original files only
[16:44] <mfisch> ogra_: right, because you also need a new default locate, changes to maliit's conf file, etc
[16:44] <rsalveti> so I don't see how the ramdisk is part of the kernel
[16:44] <rsalveti> that's just the kernel for me
[16:44] <mfisch> ogra_: although that (different build) is not the current plan as I understand it
[16:44] <rsalveti> and your device just copies things around
[16:44] <rsalveti> and then use the original mkbootimg it seems
[16:44] <ogra_> mfisch, right, i think something like we do for desktop would be better for that
[16:44] <ali1234> "# Add ramdisk dependencies to kernel"
[16:44] <rsalveti> which is where it's failing to generate the final image
[16:44] <rsalveti> that's just build dependencies
[16:44] <ali1234> rsalveti: you;re missing the point
[16:44] <ali1234> when i build cyanogen it doesn't fail
[16:44] <mfisch> ogra_: there are many blockers in doing it, I'll CC you on the mail so you can weigh in. thanks
[16:45] <ali1234> it doesn't ever call mkbootimg because boot.img already exists
[16:45] <ali1234> under ubuntu you have to patch the makefile to generate android-boot.img instead of boot.img
[16:45] <ali1234> that means boot.img doesn't exist
[16:45] <rsalveti> then boot.img will just be the plain kernel for you
[16:46] <ali1234> that means it erroneously tries to call mkbootimg on a kernel that already contains a ramdisk
[16:46] <rsalveti> right
[16:46] <rsalveti> now how does it bundles the ramdisk in there?
[16:46] <ali1234> using that makefile you pasted
[16:47] <rsalveti> ali1234: but that's just a copy
[16:47] <rsalveti> not putting the ramdisk together with the kernel
[16:47] <rsalveti> of the zImage
[16:47] <rsalveti> so unless you got a kernel patch for that, it'd just be the pure kernel
[16:48] <ali1234> i guess they must have patched the kernel then
[16:48] <ali1234> but look at the line after "Add ramdisk dependencies to kernel" - that is not referenced anywhere else
[16:49] <rsalveti> I need to better handle the variables there when a device defines BOARD_CUSTOM_BOOTIMG_MK
[16:50] <ali1234> i don't understand how any of this works
[16:50] <ogra_> it is easy for the normal boot.img's
[16:50] <ali1234> i don;t know how the ramdisk got in there
[16:50] <ogra_> but samsung is a special beast
[16:50] <ali1234> but it's pretty clear to me that it has somehow
[16:50] <ali1234> so i have two questions now
[16:51] <ali1234> first, how do i trim the ramdisk without unpacking and rebuilding it?
[16:51] <rsalveti> ali1234: TARGET_KERNEL_BINARIES is just to copy all the files in the out directory
[16:51] <ali1234> and second.... actually there is no second
[16:52] <ogra_> ali1234, i can add a hack to the package so that we ship an additional initrd without adb inside ...
[16:52] <rsalveti>     # write new kernel to boot partition
[16:52] <rsalveti>     /tmp/flash_image boot /tmp/boot.img
[16:52] <ogra_> rsalveti, and i discussed that before
[16:52] <rsalveti> yeah, boot is just the kernel
[16:52] <ogra_> right
[16:53] <ogra_> on my device the partition is even labelled "kernel"
[16:53] <rsalveti> right
[16:53] <ogra_> i thought thats the case on other samsungs too
[16:53] <ali1234> rsalveti: if it is really just a pure kernel, why is it a different size in cyanogenmod and ubuntu, even though it was built with an identical source tree , config, and compiler?
[16:53] <rsalveti> anyway, will investigate this a bit more, need to go for a bit for lunch
[16:53] <ali1234> and what data lies between __irf_start and __irf_end?
[16:54] <rsalveti> not sure, will investigate this a bit more later today
[16:54] <rsalveti> and get a better handling for custom mkbootimg and recovery tools
[16:54] <rsalveti> this device customizes everything it seems
[16:54] <rsalveti> bbl
[16:55] <ali1234> rsalveti: if you need to actually try building it, all my code is on github.com/ali1234 - there's just three repos to switch after breakfast and any branch will do
[16:58] <ogra_> stgraber, initra,fs-tools is now there ... can you do the initrd dance or should it (i'm holding back an img build for it atm)
[16:59] <popey> hmm, nexus4 just spontaneously rebooted
[17:00] <stgraber> ogra_: sure, uploading now
[17:00] <ogra_> thx
[17:00] <stgraber> done
[17:00] <stgraber> (I had it ready for upload, was just waiting for rmadison to confirm the other one was published, though you beat me to monitoring it apparently ;))
[17:05] <ogra_> stgraber, i have a script that rings a bell .and shows a notification .. tracing Packaged.g once a minute ;0
[17:05] <ogra_> ;)
[17:05] <ogra_> *Packages.gz
[17:06] <themikem> Hi all.  I'm trying to build a saucy flipped image, but I'm running into a "no rule to make target" error for sqlite3.  Any ideas?  I don't see sqlite3 source in my local tree anywhere... Missing a repo maybe?
[17:07] <ogra_> did you repo sync today ?
[17:07] <ogra_> it was removed and added back yesterday
[17:08] <themikem> ah.  yes, I've sync'd twice this morning.  I'll try again...
[17:09] <mfisch> fginther: ping
[17:11] <themikem> ogra_: just sync'd.  No dice.  All up to date.
[17:11] <ogra_> did that work with an unflipped build ?
[17:11] <ogra_> also what needs sqlite3 in your build ?
[17:12] <themikem> haven't done an unflipped build of saucy, but raring works.
[17:14] <themikem> still digging into the makefiles to answer that more specifically.  The "needed by" error is coming from the target_files zip in PACKAGING/target_files_intermediates/
[17:16] <davmor2> popey: with --wipe I get the behaviour I've added to the bug but the gallery does actually open,  So I think you are getting the flash be that I see but then nothing, where as for me the app opens.
[17:17] <davmor2> s/flash be/flash bit
[17:17] <Joe_B> Does anyone know of a youtube demo of Touch driving a desktop (not Ubuntu for Android driving a desktop)?
[17:19] <ogra_> Joe_B, that would be made up, no such thing exists yet
[17:19] <Joe_B> Ok, that explains why the demos are ubuntu for android.
[17:19] <mhall119> bzoltan: when will the click package creation be available in QtCreator from Saucy's archives?
[17:19] <ogra_> Joe_B, development on the converged setp will start in october
[17:20] <ogra_> *setup
[17:20] <ogra_> (and will be ready in april)
[17:21] <Joe_B> Great, thanks.
[17:36] <kenshiro> Hi, will Ubuntu Touch be stable in october and installable in Nexus 4? Will it have a whatsapp client?
[17:37] <mhall119> kenshiro: yes to the first
[17:38] <ali1234> hmm even when i hacked the makefiles to produce both boot.img and android-boot.img it still tries to recreate boot.img
[17:38] <mhall119> as for the second, WhatsApp killed the idea of an open source 3rd party app, so it'll be up to them whether you get an official client or not
[17:38] <kenshiro> mhall119 great, thank you ! :-)
[17:38] <ali1234> i guess it really does need to take more care when the build specifies custom bootimg
[17:46] <mhall119> cjwatson: will click packages be gpg signed when submitted?
[17:46] <mhall119> like source debs are
[17:57] <ali1234> i read the other day about image based updates... what happens to any deb packages you have installed if there is an image update?
[17:57] <ali1234> can you even install debs under this system?
[17:57] <kenshiro> Hi, will Naver Line (an instant messaging software like Whatsapp) be available for Ubuntu Touch?
[18:00] <ogra_> ali1234, no
[18:00] <ali1234> so click packages only?
[18:00] <ogra_> kenshiro, if someone ports it
[18:00] <ogra_> ali1234, no :)
[18:01] <ogra_> ali1234, you can swithc to developer mode and then just use deb/apt as yoou are used to
[18:01] <kenshiro> ogra_ ok. Is there any sure port for instant messaging software in Ubuntu Touch?
[18:01] <ali1234> yeah but... how does that work with image updates? do the debs go into a special partition or something?
[18:01] <ali1234> or do you have to reinstall them all (like on n900 blargh)
[18:02] <xnox> ali1234: switch to developer mode, means you use dist-upgrade and cannot use image updates anymore.
[18:02] <ogra_> kenshiro, yes, friends-app is shipped by default, it supports any protocol rlepathy supports ... (someone worked on a whatsapp implementation, not sure what happened to that)
[18:02] <ali1234> i see
[18:02] <ali1234> that makes sense actually
[18:02] <ali1234> so you can opt out of image updates entirely
[18:02] <ogra_> right
[18:03] <kenshiro> ogra_ ok, thank you very much :-)
[18:03] <ogra_> :)
[18:05] <mhall119> ali1234: yeah, you can have either image based updates or deb packages, but not both
[18:06] <mhall119> ogra_: friends-app uses telepathy?
[18:06] <ogra_> which indeed requires that there is never an update to hybris on the android side
[18:06] <ogra_> mhall119, doesnt it ?
[18:06] <mhall119> I don't think so
[18:06] <mhall119> it's not a messaging app
[18:06] <ogra_> oh
[18:07] <ogra_> then i did get that totally wrong
[18:07] <mhall119> it doesn't do chat
[18:07] <mhall119> ogra_: you're thinking of Empathy?
[18:07] <mhall119> which, afaik, we don't have a Touch client for
[18:08] <mhall119> also, the whatsapp telepathy plugin was hackish, it required an app token that had to be stripped out of some other app and which was constantly becoming invalid
[18:10] <ogra_> did he drop the ball ?
[18:10] <ogra_> or does he look for a solution ?
[18:10] <mhall119> he gave up, I think, because it was going to be a constant game of trying to keep the app token updated
[18:10] <ogra_> whatsapp seems to be a needed thing nowadays
[18:10] <ogra_> (never used it)
[18:11] <mhall119> ogra_: I agree, jono reached out to the company to try and get official sanction for the open source app, so they wouldn't have to play token-hunt every few weeks, but they turned it down
[18:11] <mhall119> hopefully they will provide an official client instead
[18:11] <ogra_> ++
[18:14] <ogra_> stgraber, oh, i nearly forgot ... i switched the lxc pre-start.sh to have a pre-start.d with snippets (so QA doesnt need to sed around in the script itself) for QA stuff it would be needed that /var/lib/lxc/android/pre-start.d becomes rw ... could you add it with one of the next uploads ?
[18:16] <rsalveti> ali1234: thanks, will try to build for your target and see what needs changes in there
[18:17] <rsalveti> ogra_: did you trigger a new image already?
[18:18] <ogra_> rsalveti, yep, running ... i had to wait a little because i missed the window before stgraber had uploaded the initrd changes ... and i didnt want to have that out of sync
[18:18] <ogra_> 30-45min
[18:18] <rsalveti> ogra_: great
[18:39] <themikem> ogra_: started over with a fresh tree.  No more sqlite3 errors.  Now I'm getting "QCMetaData.h: no such file or directory" on several packages.  Is this a known issue?
[18:42] <rsalveti> themikem: no, need to grep to see who is requiring that header
[18:43] <rsalveti> might be missing another repository, just do a grep around to see who is including that file
[18:43] <rsalveti> so we can try to understand better the dependencies
[18:43] <themikem> libstagefright
[18:44] <rsalveti> hm, let me check
[18:45] <rsalveti> themikem: can you paste the build log you're getting?
[18:46] <themikem> does it write it to the filesystem somewhere?  If not I need to run it again...
[18:46] <Raznog> Hi, is there a way to emulate ubuntu-phone in a vm or someting like that?
[18:47] <themikem> rsalveti: late for a meeting.  I'll paste it when I get back.
[18:47] <ali1234> rsalveti: actually, i'm going to clean up these repos and then do a brain dump on the ML...
[18:48] <rsalveti> themikem: ok, this file is part of hardware/qcom/media/mm-core/inc
[18:48] <rsalveti> ali1234: ok
[18:56] <Raznog> Hi, is there a way to emulate ubuntu-phone in a vm or someting like that?
[18:59] <ogra_> rsalveti, slangasek, image is ready
[18:59] <rsalveti> ogra_: cool, let me flash that
[18:59] <rsalveti> 02.2?
[19:00] <rsalveti> downloading
[19:00] <ogra_> yeah
[19:28] <ali1234> rsalveti: ok, i cleaned up the repos so my changes are all on top, and posted exactly what i have done to the ML
[19:29] <rsalveti> ali1234: thanks, will try to build it for your device later today
[19:29] <ali1234> thanks
[19:31] <ali1234> i might hack together something to extract the initramfs then we'll know for sure what it is
[19:31] <ali1234> probably there's already a tool for this actually, if it's as standard as it look
[19:32] <dobey> is there an i386 or amd64 build of the touch image that one could run inside virtualbox or something?
[19:32] <sergiusens> dobey: no there isn't
[19:33] <dobey> :(
[19:33] <ali1234> someone hacked one together by hand (install regular ubuntu, add ppas etc)
[19:33] <ali1234> i don't know if they ever got it working properly
[19:33] <sergiusens> dobey: closest is armhf/qemu, but it needs some work
[19:55] <mhall119> sergiusens: who was making click packages for the core apps?
[19:55]  * mhall119 doesn't remmember
[19:56] <sergiusens> mhall119: I am
[19:58] <mhall119> sergiusens: and you will be submitting merge proposals with the click manifests?
[20:00] <mhall119> sergiusens: also, will we be able to provide daily builds using click packages like we currently do with .debs?
[20:02] <sergiusens> mhall119: we have daily builds, just done differently ... I'm creating the manifests on the fly from the debian packaging until we have something that we can merge with (autopilot et.al.)
[20:03] <sergiusens> mhall119: I'm going to be working with fginther for that
[20:03] <mhall119> sergiusens: ok, thanks, as long as somebody is working on it I'm happy :)
[20:03] <mhall119> nik90: ^^
[20:03] <sergiusens> mhall119: I'll propose MRs with the manifests though, they have stabilized
[20:03] <sergiusens> so should be safe to do once
[20:03] <nik90> cool
[20:09] <tux_> funding for edge was 7,995 m a few mins ago, now its 7,962 m
[20:09] <tux_> bit weird
[20:14] <bef0rd> taxman
[20:23] <mhall119> tux_: are you sure you didn't mis-read 7,955 as 7,995?
[20:26] <ali1234> seems plausible
[20:31] <mhall119> Terminal app starting in #ubuntu-touch-meeting
[20:31] <tux_> mhall119, quite possible, been a long day :/
[21:33] <mamenyaka> hello! can someone help me with phablet-saucy? I have boot and adb, but black screen
[21:36] <mamenyaka> sergiusens, rsalveti, ogra_  ^^
[21:53] <john__> hello
[21:54] <john__> can anyone please help me in downloading ubuntu for android