[01:15] <danrik> sooo - does anyone know when is the next ubunntu phone gonna come out?
[01:16] <danrik> I just broke my android - but I want something more serious than bq aquaris.
[01:17] <k1l> did not hear anything more than "soon"
[01:17] <danrik> k1l, ok - then how about best supported phone so far?  nexus 5?
[01:18] <k1l> erm. both nexus 4 and 5 seem to be ok?
[01:22] <DonkeyHotei> nexus5 has no bluetooth and won't play videos
[01:23] <k1l> oh.
[01:23] <k1l> nexus4 was the original dev device.
[01:24] <danrik> k1l, so that leaves only nexus 4?
[01:24] <DonkeyHotei> the meizu mx4 is the next phone
[01:29] <danrik> damn. mx4 is gsm, im on verizon :(.
[02:52] <FR43D14Z> Hello People :D Hay alguien que hable español?
[07:35] <EdwardMorbius> guys I have a serious issue with my BQ, this morning it froze and I powered it off then on and now I am stuck at boot loop at the BQ logo and powered by Ubuntu screen.
[07:43] <EdwardMorbius> now attempting to enter recovery, still waiting at the ubuntu logo
[07:45] <EdwardMorbius> a few bq logo flashes and now it boots "normally"??
[07:46] <ogra_> EdwardMorbius, https://lists.launchpad.net/ubuntu-phone/msg11819.html
[07:47] <EdwardMorbius> ogra I think this has something to do with changed system language
[07:47] <ogra_> from what to what did you change it ?
[07:47] <EdwardMorbius> I switched from english us to english uk and I read on the Internet about someone else getting bootloop after they changed language
[07:48] <ogra_> could you comment on the bu that is mentioned in the above mail ?
[07:48] <ogra_> *bu
[07:48] <ogra_> bah
[07:48] <ogra_> *bug
[07:48] <EdwardMorbius> will do so now, because I had one phone freeze before but I powered it off and on normally
[07:48] <EdwardMorbius> but now I got bootloop
[07:49] <ogra_> oh, you sounded like it booted again above
[07:49] <EdwardMorbius> the option in the gui erase&reset everything will make a full factory reset right?
[07:49] <EdwardMorbius> It did boot but looks shaky to me
[07:49] <ogra_> yes :/
[07:49] <ogra_> define "looks shaky"
[07:49] <EdwardMorbius> indicator date time is bugged and I got to gui some time ago too, attempted a new reboot from gui and again got the bootloop
[07:50] <EdwardMorbius> so I believe factory reset is the way to get everything in the clear again
[07:51] <ogra_> yeah, but at lest you have the ui up to be able to pull down photos etc if needed
[07:51] <ogra_> the factory reset will sort it
[07:53] <EdwardMorbius> didnt have any photos worth saving anyway, restoring all my settings will be a little chore though
[07:53] <ogra_> yeah, we really need a backup tool for this ... one that stores and restores all data and settings
[07:53] <EdwardMorbius> phone resetted and I am commenting on the bug now
[07:53] <EdwardMorbius> yes that would be very helpful
[07:53] <ogra_> thanks !
[07:55] <EdwardMorbius> just posted, too bad I had to reset the phone, I am guessing all the logs are gone now too.
[07:55] <ogra_> yes, but you are the second person that claims it happened after language switch ... that at least gives a pointer
[07:56] <ogra_> (though trying to reproduce it on a development device here doesnt get me the issue)
[07:56] <EdwardMorbius> development device as in nexus 4?
[07:56] <ogra_> no, a pre-production bq
[07:57] <ogra_> same device .... but with android buttons on the glass :)
[07:57] <EdwardMorbius> maybe someone with the production device should attempt it, gremlins inside may be different than in the pre production one.
[07:57] <ogra_> yeah
[07:58] <EdwardMorbius> when device froze I was like "oh I will post some logs as bug report later on" but then :O :D
[07:58] <ogra_> yeah, if you cant boot that wont help :)
[08:00] <EdwardMorbius> I am not touching the system language again :D
[08:00] <ogra_> heh
[08:00] <ogra_> there might be a differnce in how the welcome wizard sets it and how the system settings do
[08:01] <EdwardMorbius> true, someone should check that, it is possibly an oversight
[08:01] <ogra_> riht, i will ... after easter vacation though ... i'm not officially here :)
[08:02] <EdwardMorbius> lets hope no more people get ideas about changing the system language :D
[08:03] <ogra_> yep :/
[08:04] <EdwardMorbius> and that backup tool would be veeery nice if someone can make it
[08:09] <EdwardMorbius> updating apps...
[08:10] <EdwardMorbius> Is it just me or is the Ubuntu Store sometimes a bit slow?
[10:22] <Isotop7> i rootstrock-ng only useable for the supported devices? what would i do if i had a freshly build system.img for my galaxy s4
[10:22] <Isotop7> ?
[10:54] <rickspencer3> good morning all
[10:54] <rickspencer3> shall I assume that everyone is on holiday today?
[10:55] <rickspencer3> except us poor saps from the USA, and then I guess I assume I am the only one crazy enough to be up already?
[10:56] <didrocks> rickspencer3: real part of France is working as well :)
[10:56] <rickspencer3> hey!
[10:56] <didrocks> hey ;)
[10:56] <rickspencer3> bon courage!
[10:57] <didrocks> merci, à toi aussi !
[10:57] <rickspencer3> I was not expecting a response :)
[11:01] <greyback> the heathen land of Ireland also defiant
[11:02] <didrocks> greyback: hey! you keep wanting to be different than the UK, I see ;)
[11:03] <greyback> didrocks: you're lucky there's an ocean between us!
[11:03] <didrocks> greyback: j/k ;)
[11:03] <greyback> :D
[11:05] <rickspencer3> greyback!
[11:05] <greyback> rickspencer3: at your service *hat tip* :)
[11:05] <rickspencer3> o/
[11:05] <rickspencer3> just saying "hi"
[11:06] <rickspencer3> I got up early because I was so worried about the bootloop issue I couldn't sleep
[11:06] <rickspencer3> I imagined hundreds of people factory resetting their phones this morning :/
[11:34] <Isotop7> how do i get my compiled images and the rootfs to my s4 in order to get it up running?
[11:40] <rickspencer3> Isotop7, hey, I feart that the channel may be slightly laggy for you today, I know I lot of people are afk b/c of Easter :/
[11:40] <Laney> dudes, I'm getting "invalid cross-device link" when using the citrain thingy to install a silo
[11:40] <Laney> how go problem fix I?
[11:56] <seb128> Laney, you might want #ubuntu-ci-eng rather
[11:57] <ogra_> Laney, i think robru fiddled with the code very recently ... (last week)
[11:58] <ogra_> probably check if there is a newer version
[11:58] <Laney> where?
[11:58] <ogra_> phablet-team PPA
[11:58] <Laney> I used that Ubuntu archive thing
[12:17] <Laney> ogra_: how did you test that lxc-android-config fix?
[12:18] <ogra_> i made the file writable through writable-paths and rebooted
[12:18] <ogra_> installing lxc-android-config is rather painful so i only tested the chnage
[12:18] <Laney> so touch /userdata/.wriatble_paths; reboot; edit; rm /.../.; reboot; test ?
[12:19] <ogra_> i never touch writable_paths...
[12:19] <Laney> you can just edit it?
[12:19] <ogra_> wget the deb ... reboo to recovery ...
[12:19] <Laney> woah
[12:19] <Laney> what is this?
[12:19] <ogra_> install lxc-android-config chrooted into the rootfs
[12:20] <ogra_> then reboot ...
[12:20] <Laney> O_O
[12:20] <didrocks> it's only a file change, right?
[12:20] <ogra_> thats how to install this package
[12:20] <ogra_> as i said ... painfull
[12:20] <ogra_> thanks to our bindmount farm spanning across partitions
[12:20] <didrocks> you can mount -o remount,rw …, do the change, reboot
[12:20] <ogra_> not to test the package
[12:21] <ogra_> but yeah, to test the change
[12:21] <didrocks> yeah, not the package, but just the 8 char changes in a string file
[12:21] <ogra_> right, that wont tell you if the package did the right thing though ... but is enough o check the change works
[12:22] <Laney> given that you think it does and jibel says it does not ...
[12:22] <ogra_> yeah, i told him i'll research it after the holidays
[12:23] <ogra_> is there a reason why we dont use the same .override mechanism we use in vivid ?
[12:23] <didrocks> seems that all frenchies are trying to make Laney's life hard :)
[12:23] <Laney> conspiracy!
[12:23] <didrocks> ogra_: well, it needs some changes to multiple components to work
[12:23] <didrocks> whoopsie, whoopsie-preferences…
[12:23] <didrocks> not sure you want those changes for rtm
[12:23] <didrocks> (handling transitions…)
[12:24] <ogra_> didrocks, ah, no
[12:24] <didrocks> ogra_: look at the postinsts, you will have fun :p
[12:24] <didrocks> but I think those kind of changes are good, no more "ENABLE" in conffiles
[12:25] <ogra_> i dont really care about conffiles on the phone :)
[12:25] <didrocks> ogra_: well, you have to find a way to transition though?
[12:25] <didrocks> like, how would you transition to the new system with the .override
[12:25] <ogra_> why ? we just replace
[12:25] <didrocks> once moved to vivid?
[12:25] <Laney> how do you preserve the user setting?
[12:25] <didrocks> ok, so the user disabled whoopsie
[12:25] <didrocks> /etc/default/whoopsie have ENABLED=false
[12:25] <didrocks> in vivid-based image, this reflect in the /etc/init/whoopsie.override with "manual"
[12:26] <didrocks> how do you handle that in the touch world?
[12:26] <ogra_> ah, that ... yeah, a simple upstart job does that ... in our upgrade management
[12:26] <didrocks> ok, this happens in recovery, after the unpack?
[12:26] <ogra_> we have that upstart subdir wheer you can drop transition jobs
[12:26] <didrocks> (and before removing files that are not anymore in the new image?)
[12:26] <ogra_> on first boot after upgrade
[12:26] <didrocks> hum
[12:26] <didrocks> but /etc/default/whoopsie would disappear, wouldn't it?
[12:26] <ogra_> or by developer chice on every boot)
[12:27] <didrocks> or we keep it and let the transition job deleting it?
[12:27] <ogra_> yep
[12:27] <didrocks> ogra_: that's the thing based on session-migration or something else?
[12:27] <ogra_> something else
[12:27] <didrocks> (because my session-migration is only executed by session)
[12:27] <ogra_> right
[12:27] <didrocks> ok, was afraid it was going to start too late
[12:28] <ogra_> search for boot in /etc/init on a phone
[12:28] <didrocks> sounds good then, I'm just afraid we forget about it though
[12:28] <didrocks> (and that's just one case)
[12:28] <ogra_> there is a subdir and a job executing th bits indside that subdir
[12:28] <ogra_> both called boot-$something
[12:28]  * ogra_ has no phone cnsole around
[12:29] <didrocks> ogra_: no worry, but I think as long as we have the pre/post* world and this image-based one, we might miss those transitions on one side or the other
[12:29] <ogra_> we surely will
[12:29]  * ogra_ looksforward to snappy
[12:29] <didrocks> ;)
[12:30] <ogra_> getting rid of all the deb mess :)
[12:30] <lemmster> Suppose I want to replace Ubuntu with Android on the Aquaris e4.5 (I need PGP support for email), can I use fastboot flashall with imgs taken from bq's firmware zips for an hard reset?
[12:31] <ogra_> lemmster, i fear thats something you need to ask bq
[12:31] <ogra_> not sure you can install android at all, since the partitioning scheme is different
[12:32] <EdwardMorbius> ogra I believe it can be done because I think I saw someone on Twitter that said he reflashed the phone with Android while he waits for bugs to be fixed in UT
[12:32] <ogra_> and ... well ... there are no android buttons on the glass ...
[12:32] <dbeal> How can I enable ttyUSB/ttyACM usb serial support for host-mode usb (on a Nexus 5)?
[12:32] <lemmster> ogra_: There are manuals on the web to replace android with ubuntu. I would assume the reverse should be possible as well (not that I have tried the former).
[12:33] <lemmster> EdwardMorbius: You still happen to have a ref to the tweet?
[12:33] <EdwardMorbius> ogra that can be solved by using softkeys if firmware allows it and it should I believe
[12:33] <ogra_> lemmster, well, i know that there is a different partitioning scheme applied to ubuntu phones ... it might or might not work
[12:33] <EdwardMorbius> lemmster I will check if I have it somewhere
[12:33] <ogra_> this is definitely not something we exercise in development :)
[12:35] <ogra_> also keep in mind that the flashing of android might perhaps change the partitioning ... i have no idea how the android zips work in this case ... it might prevent you from re-installing ubuntu then
[12:35] <EdwardMorbius> lemmster https://twitter.com/sharkdrink/status/581786668480503808
[12:36] <lemmster> EdwardMorbius: Thanks
[12:37] <EdwardMorbius> lemmster no problem
[12:41] <EdwardMorbius> so I heard on the last Ubuntu live session that the UT actually has another theme inside, the Ambience but currently there is no way you can switch to it, that correct?
[12:45] <Laney> ogra_: do you know of any documentation for this writable-paths file?
[12:45] <Laney> I just checked and after modifying it (even with 'transition') /etc/default/apport is empty on reboot
[12:46] <ogra_> apport
[12:46] <ogra_> ?
[12:47] <Laney> whoopsie!
[12:47] <ogra_> ah
[12:47] <ogra_> :)
[12:47] <Laney> wait WTF now it's not
[12:47] <Laney> now I'm questioning the nature of reality itself
[12:48] <ogra_> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/initramfs-tools-ubuntu-touch/vivid/view/head:/scripts/touch
[12:48] <ogra_> line 336ff
[12:49] <Laney> hex line numbers
[12:49] <ogra_> heh
[12:50] <dbeal> How do I chrt into the lxc container?
[12:50] <ogra_> lxc-console -t0 -nandroid
[12:50] <ogra_> from the running ubuntu
[12:51] <dbeal> Cool
[12:51] <ogra_> (you need ctrl-a-q to exit it)
[13:06] <Laney> ogra_: Could not write configuration: Failed to create file '/etc/default/whoopsie.0NIIWX': Read-only file system
[13:06] <Laney> it's trying to do an atomic write
[13:06] <ogra_> yeah, that wont wrk
[13:06] <Laney> snazzy
[13:08] <ogra_> Laney, that will be a bigger change ... we have a dir for such special cases, but the file needs to be pre-created during build
[13:08] <ogra_> what you want is /userdata/system-data/etc/writable/whoopsie and a bind mount like hostname and localtime use
[13:09] <Laney> I remember this hack
[13:12] <Laney> going to go climbing instead :)
[13:12] <ogra_> enjoy :)
[13:14] <peat-psuwit> rsalveti: ping
[13:19] <dbeal> How do I compile a .ko for the hammerhead kernel?
[13:20] <spazzymoto> hey guys, i hope someone can help me. Im working on the port for the one plus one and im struggling to get the /firmware partition to mount correctly. From what i have read there is a script that runs that updates the fstab on boot? I have tried to correct add some code to out the correct mount options for /firmware in the script /usr/lib/lxc-android-config/update-fstab but have had no luck. Any ideas
[13:28] <ogra_> spazzymoto, that script just grabs the fstab from android and processes it, if you have a /factory entry in your android fstab it will be automatically created
[13:28] <ogra_> err
[13:28] <ogra_> /firmware
[13:31] <spazzymoto> hmm
[13:31] <spazzymoto> i do have it in my fstab.bacon
[13:31] <spazzymoto> but if i check /etc/fstab once booted i dont see an entry for /firmware
[13:32] <spazzymoto> and doing an ls /firmware returns nothing either
[13:32] <spazzymoto> if i manually mount it with /dev/mmcblk0p1 /firmware vfat ro,shortname=lower,uid=1000,gid=1026,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait i can browse the partition
[13:33] <ogra_> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/initramfs-tools-ubuntu-touch/vivid/view/head:/scripts/touch#L408
[13:33] <ogra_> and http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/initramfs-tools-ubuntu-touch/vivid/view/head:/scripts/touch#L82 for the function
[13:35] <spazzymoto> thank you let me have a look at that
[13:39] <ogra_> hmm, looking at this code, i wonder what happens if you have multiple fstab files in that location :)
[13:39] <ogra_> spazzymoto, do you have more than one file that starts with "fstab" in yoour android rootfs ?
[13:41] <spazzymoto> ogra, only 1 file hey
[13:50] <spazzymoto> i do see the message [   16.174895] initrd: mounting /dev/disk/by-partlabel/modem as /root/android//firmware
[13:50] <lemmster> ogra_: FYI: I successfully flashed Android with this MKT Flash Tool on Windows and the bq firmware reset image.
[13:54] <spazzymoto> ah mount: special device /dev/block/platform/msm_sdcc.1/by-name/modem does not exist :( will try change this to /dev/mmcblk0p1
[13:55] <ogra_> lemmster, right, as i said, you might not be able t go back ... better test that before you start usingthe phone ;)
[13:57] <ogra_> spazzymoto, wont that break android then ?
[13:57] <lemmster> ogra_: I will try to go back the moment the features I'm missing are there.
[13:57] <ogra_> you usually dont have /dev/mmcblkX there
[13:57] <dbeal> Is there an Ubuntu Touch that doesn't require Android?
[13:57] <ogra_> dbeal, there is the desktop-next image for PCs
[13:57] <spazzymoto> orga :/ ah i didnt know that
[13:58] <ogra_> spazzymoto, you rather want to make sure your kernel provides /dev/block/platform/msm_sdcc.1/by-name/modem ...
[13:59] <spazzymoto> ogra, thanks for the help. Ill go research on how to make that happen
[13:59] <ogra_> :)
[13:59] <ogra_> spazzymoto, are you sureat all that you need /firmware on the ubuntu side ?
[14:00] <ogra_> usually the modem is completely handled inside the container ... ubuntu talks to it via rild
[14:01] <spazzymoto> i might be on the wrong tack. Im seeing these messages in my dmesg
[14:01] <spazzymoto> [   20.829270] msm_ipc_load_default_node: Failed to load modem [   20.858718] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
[14:01] <ogra_> well, that is something your init.rc in the container should handle i guess
[14:02] <ogra_> the kernel prints messages for both systems ... it is sometimes hard to allocate them to the right one ... but i guess this one comes from inside the container
[14:04] <spazzymoto> ok cool :) let me poke around a bit more. Thanks for putting me on the right path
[14:36] <dbeal> Is there a phone with Ubuntu that doesn't require Android?
[14:36] <dbeal> [02:27] <ogra_> dbeal, there is the desktop-next image for PCs
[14:36] <ogra_> dbeal, no
[14:36] <ogra_> if you want to make any use of the hardware yu wont get around using the binary drivers
[14:37] <dbeal> In my mind, a phone is a small computer.
[14:38] <ogra_> sure
[14:38] <dbeal> So is the problem that, for some specific hardware (e.g., Nexus 5 camera), the only drivers available are within Android?
[14:38] <ogra_> well, if it would just be the camera :)
[14:39] <ogra_> modem, all sensors, gps, camera, graphics chip, audio and video codecs
[14:39] <dbeal> Are those all binary only drivers?
[14:39] <ogra_> yes
[14:40] <dbeal> Is there one for host-mode usb serial support?
[14:40] <ogra_> that really depends on the device
[14:40] <dbeal> Say for example I wanted to connect a Bus Pirate or Aardvark?
[14:41] <dbeal> Arduino also has a usb serial interface.
[14:42] <ogra_> as i said, that competely depends on the device you run on
[14:43] <dbeal> What about this device?
[14:43] <dbeal> [ 1245.529600] usb 1-1: Product: FT232R USB UART [ 1245.529625] usb 1-1: Manufacturer: FTDI
[14:43] <ogra_> no idea
[14:43] <ogra_> what about it
[14:45] <dbeal> I would expect a /dev/ttyUSB* or /dev/ttyACM* entry to appear when connecting a usb serial device.
[14:45] <dbeal> With a module like this.
[14:45] <ogra_> if your kernel supports it, sure
[14:45] <dbeal> usbserial              45100  1 ftdi_sio
[14:45] <dbeal> Would I need to recompile the kernel?
[14:45] <ogra_> and if the USB interface isnt blocked by something the kernel ships
[14:46] <ogra_> i have no idea, really
[14:46] <ogra_> totally depends on your device and how the kernel is set up by default, what it already does with the usb port etc etc
[14:47] <dbeal> I'm pretty new to the Ubuntu Touch architecture, so I'm not entirely sure how the system works with the lxc and how kernel module compilation works.
[14:47] <ogra_> this is a bit like you coming to a car shop, showing a random bolt from your car to a mechanic and asking why the radion doesnt work :)
[14:47] <ogra_> *radio
[14:48] <ogra_> tha also depends on the device ... for the nexus devces we ue normal linux kernel packages in the archive ... the binaries get dynamically pulled in during the build of the android container in the android package ...  for all othr devices we build the kernel during the container build instead of using a binary deb
[14:53] <Denco> Hello everybody, I'm trying to figure out if I have a problem with BQ's Aquaris E4.5 Ubuntu Edition. Is this correct place to try it?
[14:53] <ogra_> you aretrying to figure out ?
[14:53] <dbeal> What is the name of the linux kernel and android container package?
[14:54] <ogra_> dbeal, the android package is called android ... the kernel packages are linux-image-$your-devices-codename (i.e. "mako" for N4 or "flo" for N7)
[14:56] <dbeal> I don't seem to have an "android" package.
[14:56] <ogra_> it is in the ubuntu archive
[14:57] <dbeal> I don't have a linux-image package installed either.
[14:57] <ogra_> installed ?
[14:57] <ogra_> no
[14:57] <ogra_> these bits live all in the device tarball
[14:57] <pmcgowan> Denco, most likely yes
[14:58] <dbeal> Where is the device tarball?
[14:58] <Denco> My BQ's Aquaris lost 13% of battery in two hours after it was fully charged. I made just 2 phone calls in that time, it was just lying on the table the rest of the time. Is this normal?
[14:58] <ogra_> depends on your device once again
[14:59] <dbeal> I have an N5.
[14:59] <ogra_> dbeal, we don have device taballs for N5 ...
[14:59] <ogra_> dbeal, for that i think you need to talk to Tassadar
[14:59] <dbeal> So when I ran a system update this morning, it actually rebuilt the kernel?
[14:59] <ogra_> no
[15:00] <ogra_> it is rebuilt beofore the device tarball hits the server
[15:00] <dbeal> It just downloaded a new container binary?
[15:00] <dbeal> Oh, ok
[15:00] <dbeal> Is there a package I can install to build my own kernel containers?
[15:01] <ogra_> not sure how the N5 is maintained
[15:02] <ogra_> might be there is a hammerhead linuc-image package somewhere, no idea
[15:02] <dbeal> Does the BQ also use Android?
[15:02] <Tassadar> yep, there is
[15:02] <ogra_> "<ogra_> if you want to make any use of the hardware you wont get around using the binary drivers"
[15:02] <ogra_> ^^that applies to all phones ... including the bq indeed
[15:03] <dbeal> linux-hammerhead - Complete Linux kernel for the Nexus 5 (hammerhead).
[15:04] <dbeal> If I have an N5 device, why don't I need to have linux-image-hammerhead installed?
[15:04] <ogra_> because you boot from a boot.img file
[15:04] <Tassadar> https://code-review.phablet.ubuntu.com/gitweb?p=ubuntu/kernel/trusty.git;a=summary this is the kernel source
[15:05] <ogra_> installing the pckage would just waste diskspace ... it wouldnt be used
[15:05] <ogra_> *package
[15:05] <dbeal> Is there any special reason why the N5 is not officially supported?
[15:05] <dbeal> What would I do with the hammerhead kernel package?
[15:06] <ogra_> no, no special reason except that canonical doesnt have N5s
[15:10] <dbeal> I would be fine with the idea of binary drivers, if they were designed as microkernel-style device drivers.
[15:11] <ogra_> well, they are designed as the manufacturer decided ... not much anyone but them can do about that
[15:11] <ogra_> its like nvidia on PCs
[15:12] <dbeal> e.g., each binary driver operates as an independent process that communicates with a parent kernel solely via message passing.  Any process that wanted to talk to the device would then talk directly to the device driver process.
[15:12] <ogra_> (except that the binary drivers provided for android are not linked against linux libc but android bionic)
[15:13] <ogra_> dbeal, what do you do with the binary daemons that are needed to initialize and configure the driver ?
[15:13] <dbeal> It almost seems like the android-as-lxc architecture is a step towards the slippery microkernel slope.
[15:13] <ogra_> (note, they are also not linked against libc and wont run on linux out of the box)
[15:14] <ogra_> it is the most elegant solution we found to the problem ...
[15:15] <ogra_> jolla and firefoxOS have the same issue btw ...
[15:15] <Se7> i don t found anymore the fb messanger...was installed...disinstalled...gone from store :/
[15:16] <dbeal> Good question.
[15:17] <LeousSama> hey
[15:17] <LeousSama> hello
[15:21] <LeousSama> I am developing an Ubuntu Phone application "QML app with C++ plugin (cmake)" but I have so many qml files so I want to separate them by functionality
[15:21] <LeousSama> ApplicationName
[15:21] <LeousSama>     CMakeListes.txt
[15:21] <LeousSama>     ..
[15:21] <LeousSama>     app
[15:21] <LeousSama>         CmakeListes.txt
[15:21] <LeousSama>         ApplicationName.desktop.in
[15:21] <LeousSama>         tests
[15:21] <LeousSama>         mainComponents
[15:21] <LeousSama>             sub directories of mainComponents
[15:21] <LeousSama>                 some files
[15:21] <LeousSama>             some other files
[15:21] <LeousSama>         ApplicationName.qml
[15:21] <LeousSama>     po
[15:21] <LeousSama>         CMakeListes.txt
[15:21] <LeousSama>     ApplicationName.apparmor
[15:21] <LeousSama>     manifest.json.in
[15:21] <LeousSama> but the "mainComponents" folder dose not appear in the project tree and after some searches I found that I must add CMakeListes.txt in every new folder and this:
[15:21] <dbeal> Okay, so you have binary drivers, binary daemons, but you can still build the android lxc kernel?
[15:21] <LeousSama> add_subdirectory(folder_name)
[15:21] <LeousSama> instruction in the parent folder CMakeListes.txt file but I don't if there is more to add and I don't know how to create the CMakeListes.txt
[15:21] <ogra_> LeousSama, please use a pastebin like paste.ubuntu.com
[15:21] <LeousSama> thanks
[15:22] <ogra_> and you might have better luck in #ubuntu-app-devel with that question
[15:22] <LeousSama> ok sorry
[15:22] <ogra_> dbeal, the kernel luckily desnt care about the libc that is used in the rootfs
[15:23] <ogra_> we use a patched android source (see the porting guide from the topic, it explans the kernel changes)
[15:23] <ogra_> so the kernel serves both OSes
[15:24] <dbeal> But are the binary device drivers all compiled into that kernel?
[15:24] <ogra_> no
[15:24] <dbeal> No, that wouldn't make sense, would it?
[15:24] <ogra_> most of them reside as libs in the container
[15:25] <ogra_> or as firmware ...
[15:25] <ogra_> or even as daemons
[15:25] <dbeal> Ok, so the kernel just has to be binary compatible with the binary kernel modules?
[15:25] <ogra_> (which simply include the driver bits)
[15:25] <ogra_> right
[15:25] <ogra_> and the environment has to provide the files in the right places
[15:26] <ogra_> since the binaries usually have hardcoded paths etc
[15:26] <ogra_> ifthey read configs or lod other binary stuff
[15:26] <ogra_> *load
[15:26] <dbeal> Hence the chroot/lxc
[15:27] <ogra_> right
[15:27] <ogra_> https://developer.ubuntu.com/static/devportal_uploaded/136981fa-6287-49d3-9874-06f40b2e4eb7-cms_page_media/380/ubuntu_touch_architecture.png
[15:27] <ogra_> that illustrates it pretty well (a bit outdated though)
[15:28] <dbeal> Are the modules in /system/lib/modules/ binary-only, or are they the ones you can build from source?
[15:28] <ogra_> (and there is a set of arrows missing, the orange par can indeed always talk directly to the kernel too)
[15:28] <dbeal> How do I load or inspect the state of one of the binary-only drivers?
[15:28] <ogra_> however you would do it on android :)
[15:29] <ogra_> differs per device and driver
[15:29] <ogra_> you can enter the running contaner with "lxc-console -t0 -nandroid"
[15:29] <ogra_> and poke around in there if you like
[15:33] <dbeal> It looks like /system/lib/modules looks like it has linux native modules.  I might be able to build something like usbserial or cdc_acm support in.
[15:33] <ogra_> sure, you should be able to drop them there and update the module deps
[15:40] <peat-psuwit> awe_: ping
[15:43] <awe_> peat-psuwit, pong
[15:44] <peat-psuwit> awe_: Now I have a working fix for ofono now, what should I do to create a new plugin for it?
[15:45] <awe_> so we maintain ofono for ubuntu in a github repo
[15:45] <awe_> and would be glad to review new pull-requests
[15:46] <awe_> one thing that's different than standard ofono plugins
[15:46] <dbeal> # mount -oremount,rw /lib/modules mount: cannot remount /dev/loop1 read-write, is write-protected
[15:46] <awe_> is we use our own plugin to dynamically load a rilmodem type device plugin vs. using the std udevng plugin normally used by ofono
[15:47] <awe_> peat-psuwit, here's the git repo: https://github.com/rilmodem/ofono
[15:47] <dbeal> Is it possible to load a .ko from somewhere other than the write-protected /lib/modules?
[15:47] <ogra_> sure, you can use insmod ...
[15:47] <awe_> peat-psuwit, and here's the plugin we use to dynamically load device-specific ofono plugins: https://github.com/rilmodem/ofono/blob/master/plugins/rildev.c
[15:49] <awe_> peat-psuwit, maybe the first step would be to create grab a copy of our repo, apply your changes
[15:49] <awe_> have you just changed the existing code directly?
[15:50] <awe_> ( ie. modified the ril.c device plugin, and rilmodem code itself )
[15:51] <peat-psuwit> awe_: I actually edit drivers/rilmodem/sim.c in function sim_status_cb
[15:51] <peat-psuwit> to call my function that fire another request
[15:52] <awe_> are you familiar with git/github?
[15:52] <peat-psuwit> I also edit gril stuff to support new type of request.
[15:52] <peat-psuwit> awe_: I'm pretty good about git.
[15:53] <awe_> ok.   then probably the best approach would be to clone our git repo, apply your changes to your own branch, then ask abeato or myself to review
[15:53] <awe_> my guess is that you'll probably need to re-work slightly so that it would be acceptable to us
[15:53] <awe_> my guess is you'd probably need a device-specific plugin
[15:53] <awe_> similar to mtk.c or ril.c
[15:54] <awe_> and then some things can be done inline via device quirks
[15:54] <awe_> some things ( like overriding functions )
[15:54] <awe_> might require a new modem driver
[15:54] <awe_> but again, I would get your code into a git branch on github that we could review, and we can progress from there...
[15:55] <peat-psuwit> awe_: Let me upload my version of code to github first.
[15:55] <peat-psuwit> Shouldn't be too long. :)
[15:57] <awe_> ok
[15:57] <awe_> note, we have a lot on our plate at the moment, but will try to squeeze this in as soon as possible
[15:57] <awe_> thanks!
[16:07] <dbeal> How long will the battery last if I am building a kernel?
[16:09] <dbeal> How do I resize my 2G root partition?
[16:13] <dbeal> Should I just append zeros to system.img and run resize2fs?
[16:15] <ahayzen> Hey is there anyway i can emulate what happens when an OOM hits a specific app (I need to be able todo it manually because the music-app has a lifecycle exception at the moment)?
[16:18] <dbeal> # dd if=/dev/zero bs=4096 count=512000 >> /userdata/system.img
[16:18] <Talustus> hm no
[16:18] <Talustus> dd conv=notrunc oflag=append if=/dev/zero of=/path/to/your/file bs=1M count=1024
[16:18] <Talustus> would append 1GB to it
[16:19] <ogra_> ahayzen, i guess tvoss or ricmm could help you ... but i dooubt you will find them online beofre monday/tuuesday
[16:19] <ogra_> dbeal, why do you want to do that ?
[16:19] <ahayzen> ogra_, ah ok i'll ask then thanks :)
[16:19] <ogra_> easter holiday in many european countries :)
[16:19] <dbeal> # resize2fs system.img  resize2fs 1.42.12 (29-Aug-2014) Resizing the filesystem on system.img to 1024000 (4k) blocks. The filesystem on system.img is now 1024000 (4k) blocks long.
[16:20] <dbeal> Would a sparse truncate have been better?
[16:20] <ogra_> why do you do that ?
[16:20] <dbeal> I would like to increase the size of the root partition.
[16:20] <ogra_> yes, why ?
[16:20] <dbeal> I ran out of space while trying to install the kernel source and build dependencies.
[16:21] <ogra_> (i see *what* you do, i was wondering why
[16:21] <ogra_> ugh
[16:21]  * ogra_ quietly points to https://wiki.ubuntu.com/KernelTeam/ARMKernelCrossCompile
[16:21] <Talustus> yeah
[16:21] <Talustus> why compiling a kernel on the device ^^
[16:21] <ogra_> if you compile *on* the device, just create a chroot
[16:21] <Talustus> that would need ages
[16:21] <dbeal> Thank you, I am not sure my battery can last through the full compile.
[16:21] <ogra_> no need to mess up your system and lose updates etc
[16:22] <dbeal> Ok, that seems smarter.
[16:23] <ogra_> on your device in /home/phablet: wget http://cdimage.ubuntu.com/ubuntu-core/daily-preinstalled/current/vivid-preinstalled-core-armhf.tar.gz ...
[16:23] <ogra_> untar .. chroot into the untarred system ... install your build stuff ...
[16:23] <ogra_> but for kernels you really want to cross build on a PC ... easier and faster
[16:24] <Talustus> i guess a single compile on device will nearly eat your bat.^^
[16:24] <ogra_> yeah, you definitely want to keep it on a charger when doing that
[16:25] <ogra_> on a real charger ... not a usb port on your laptop :)
[16:31] <dbeal> Cool
[16:33] <dbeal> Why do system updates require read-only root partition?
[16:33] <ogra_> because the update is a diff between two versions of the rootfs
[16:33] <dbeal> A binary diff?
[16:33] <ogra_> that only works if the rootfs you have isidentical with the one the server used to create that diff
[16:34] <ogra_> yes
[16:34] <dbeal> Why doesn't it use something like dist-upgrade?
[16:34] <ogra_> would you like your update to take 1h while it configures single packages ?
[16:34] <Talustus> and then it fails after 58min and 59s
[16:34] <Talustus> :D
[16:35] <ogra_> nah, it wouldnt fail but it would detect a conffile change and try to ask you a question about it :)
[16:35] <Talustus> ^^
[16:35] <ogra_> (with a pupunder that stays behind the UI indeed)
[16:36] <ogra_> *popunder
[16:36] <ogra_> applying the diff for the whole rootfs usually takes a few seconds
[16:36] <ogra_> while a package by package upgrade takes waaaay longer
[16:39] <dbeal> Ah
[16:41] <dbeal> If I ran dist-upgrade, would it end up with the same upgrade?
[16:42] <ogra_> no
[16:42] <ogra_> and it would break sooner or later
[16:42] <ogra_> apt is fine for installing a few packages when working on the core system ... but not for much more
[16:43] <ogra_> (and with re-flashing the device after your work is done in mind)
[16:44] <dbeal> Is there some kind of strategic Ubuntu move towards binary-only distribution releases?
[16:45] <ogra_> ??
[16:45] <ogra_> what do you mean by binary-only ?
[16:46] <ogra_> all ubuntu releases have always been binary
[16:47] <dbeal> Well, a binary-only release requires the system image to be kept immutable in order for it to participate in an upgrade cycle.
[16:48] <ogra_> ubuntu will surely switch in the long term to image based upgrades, yes
[16:48] <mr_november> Nexus 4 with ubuntu is not being detected on QT creator. it does a device search, detects the phone for a second and then goes back to searching..
[16:48] <ogra_> effectively ubuntu will switch to snappy everywhere at some point
[16:49] <mr_november> I am not able to figure this out. Are there logs on the phone somewhere?
[16:49] <ogra_> mr_november, is the screen unlocked ?
[16:49] <mr_november> Yes
[16:49] <ogra_> and developer mode is enabled ?
[16:49] <dbeal> In order for this upgrade cycle to be tenable, the entire system image would have to remain immutable indefinitely.
[16:49] <mr_november> Yep
[16:49] <ogra_> dbeal, yes, anything wrong with that ?
[16:50] <mr_november> The phone shows battery charging and not charging with same fluctuation
[16:50] <mr_november> As soon as I quit QT creator, the phone charges constantly
[16:50] <ogra_> mr_november, that sounds like a hardware prob ...
[16:50] <mr_november> I have tested the cable
[16:50] <mr_november> I am able to push several files using adb
[16:50] <ogra_> very weird
[16:50] <mr_november> I know!
[16:51] <dbeal> How do I customize the Ubuntu system if its system image must remain immutable?
[16:51] <ogra_> have you checked if you are up to date with all sdk related packages ?
[16:51] <mr_november> I just installed them yesterday from the ppa. also did a dist-upgrade
[16:52] <ogra_> is the bttery level very low or some such ?
[16:52] <mr_november> It is at 80% right now
[16:52] <ogra_> did you tinker in any way with the phone install ?
[16:53] <ogra_> (making it writable, changing system bits)
[16:53] <dbeal> I was not aware of the new Snappy strategy..
[16:54] <ogra_> dbeal, snappy brings 100% upgrade safety ... cant really claim that for apt upgrades ... there are always corner cases where upgrades fail
[16:54] <mterry> chrisccoulson, man, is jenkins down or something?   I was really hoping that the mirserver oxide branch would generate debs overnight.  I've been cross compiling this morning to test.  I already miss working with Qml
[16:54] <mr_november> ogra_, not that I can recall. I have just used adb for pushing files etc.
[16:55] <dbeal> snappy: command not found
[16:56] <ogra_> mr_november, well, it seems like somthing the sdk does causes this ... while i work on the developer mode, this part seems fine to me (adb works) ... i'm not sure ifyou can stillcatch anyone from the sdk team to help in #ubuntu-app-devel (easter holidays all over europe this weekend)
[16:56] <ogra_> dbeal, that only works on a snappy system :)
[16:56] <mr_november> ogra_, I see, thanks though
[16:57] <mr_november> I just noticed that I cannot access the storage through the file explorer
[16:57] <dbeal> This is the first time I'm hearing about snappy and Ubuntu Core.  Does snappy work with Ubuntu Touch?
[16:57] <mr_november> That's new.
[16:57] <ogra_> dbeal, not yet ... snappy is the next evolution step of the technology we developed for the phone ...
[16:57] <dbeal> Is Ubuntu Touch just being snappy-esque with its binary image updates?
[16:58] <ogra_> at some point the phone will move to snappy as a base
[16:58] <dbeal> I see.
[16:58] <ogra_> snappy was developed out of the phon system ... now went its own way and once matured it will return to the phone :)
[17:01] <dbeal> Like a snappy boomerang?
[17:01] <dbeal> Is snappy ready for desktop use?
[17:01] <ogra_> more like a child that has grown up
[17:02] <ogra_> not yet, no
[17:02] <ogra_> the framework interface isnt 100% done yet ... on snappy nothing talks directly to the system and graphical apps require a graphics server framework fist
[17:03] <ogra_> snappy focus is on cloud and IoT currently
[17:03] <dbeal> IoT as in BeagleBone Black?
[17:03] <ogra_> i know mterry did some hackery of dumping a whole desktop into one snap package though
[17:03] <dbeal> Or Intel Edison?
[17:03] <ogra_> right
[17:03] <ogra_> or RPi ...
[17:04] <ogra_> or ninjasphere ...
[17:10] <dbeal> How is a snappy system customized?
[17:10] <ogra_> not at all ...
[17:10] <ogra_> what would you customize ?
[17:11] <dbeal> Anything and everything, I suppose.
[17:11] <ogra_> you would have to create your own image if you wanted that
[17:11] <ogra_> at last for the 100MB or so that the core system is
[17:11] <mterry> chrisccoulson, is there a release of oxide happening anyway?  Or is this mirserver patch the only thing waiting?
[17:12] <mterry> kgunn, btw bug 1439829 is a vivid regression that is pretty serious in terms of being a crash during wizard.  Wanted to put it on your radar
[17:16] <bzoltan> ogra_:  holidays are overrated :) mr_november -> I can try to help if it still does not work
[17:17] <mr_november> Thanks bzoltan
[17:17] <ogra_> bzoltan, nah, holidays are the days where you can program your private projects ;)
[17:17] <mr_november> I am still not getting a stable detect on QT creator
[17:18] <ogra_> bzoltan, sounds a bit like it falls over when establishing ssh on top of the adb connection (iirc thats what you do)
[17:19] <bzoltan> ogra_:  I am done with that for today :) I was hacking on a blckbox wifi sd card what came with chinese labels... not a victory march
[17:20] <bzoltan> mr_november: ogra_ : the device detection does not use much ssh.
[17:20] <ogra_> well, i'm still crying over the G+ apis here ... trying to finish my semi native G+ app sharing bits for photos and videos
[17:20] <bzoltan> mr_november:  so what is the symptom?
[17:20] <mr_november> Sure, I'll try to explain in detail.
[17:21] <mr_november> When I connect the nexus 4 to my laptop using USB, usually everything is fine. I can browse files in the explorer, adb devices lists it, I can even push a large file
[17:21] <mr_november> And the device is charging of course . As soon as I run QT Creator though
[17:22] <chrisccoulson> mterry, the next release is from the current stable branch (https://code.launchpad.net/~oxide-developers/oxide/1.5), which is in here already https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/
[17:22] <mterry> chrisccoulson, I was just wondering if it wouldn't be faster to test this fix in a silo
[17:23] <chrisccoulson> mterry, what sort of hardware are you building on?
[17:23] <mr_november> It starts fluctuating. The charging symbol goes on and off, it disappears and reappears in the file explorer, and the QT creator device log shows 'detecting device' and then detected and then back to detecting
[17:23] <mterry> chrisccoulson, cross compiling on my laptop  :(
[17:23] <chrisccoulson> mterry, this is for testing on the device?
[17:24] <bzoltan> mr_november:  most of the device connectivity is done by simple scripts under /usr/share/qtcreator/ubuntu/scripts/
[17:24] <mterry> chrisccoulson, yah
[17:24] <chrisccoulson> mterry, and vivid?
[17:24] <mterry> chrisccoulson, yeah
[17:24] <mr_november> bzoltan, okay
[17:24] <bzoltan> mr_november:  try the device_search device_version device_wait_for_shell to see if they return smart values or hang or print some crap
[17:25] <chrisccoulson> mterry, I've already got a fully built tree here for vivid/armhf. I could probably create a build for you in about 5 minutes :)
[17:25] <bzoltan> mr_november:  but form what you say it feels that your adbd is unstable or doing something odd
[17:26] <mterry> chrisccoulson, you lovely lovely person
[17:26] <mterry> chrisccoulson, I just wanted to test that mirserver branch
[17:26] <mr_november> bzoltan, I see. I am going to try the scripts
[17:26] <mterry> chrisccoulson, I don't *think* it needs modification per greyback's comments -- the current code checks the return of the eglcontext call
[17:27] <Se7> an app uninstalled leave trace on the device?
[17:27] <chrisccoulson> mterry, it won't be a package though (I have a script that creates a tarball, which provides a wrapper script for testing the new version)
[17:27] <chrisccoulson> but you can probably copy the files wherever
[17:27] <bzoltan> mr_november:  and please check your syslog too. I am afraid that the QtC is just a victim here ... if the system thinks that the usb device was disconnected then it does what you say
[17:28] <bzoltan> mr_november:  and the charging symbol does indicate that it receives current for some time and then it looses it
[17:28] <chrisccoulson> mterry, aha, you need to add an #include <QLatin1String> to all of the modified files :)
[17:28] <chrisccoulson> it fails to build here
[17:28] <mterry> chrisccoulson, ah!  Good ok
[17:29] <mr_november> bzoltan, but the current is stable when qt creator is off
[17:30] <mr_november> also device_search returned a positive result
[17:30] <bzoltan> mr_november:  what about the device_version
[17:30] <chrisccoulson> mterry, how were you doing a cross-build btw? Are you using the packaging? (Note, I haven't tried using that)
[17:30] <mr_november> is my device version 25?
[17:31] <mr_november> bzoltan, also device wait for shell is not in this folder
[17:31] <mterry> chrisccoulson, updated.  Yeah, I was doing a pbuilder build
[17:31] <chrisccoulson> mterry, aha, I'm not sure how much success you would have with that, given that Chromium needs both a target and host compiler
[17:32] <bzoltan> mr_november: /usr/share/qtcreator/ubuntu/scripts/device_wait_for_shell
[17:32] <chrisccoulson> mterry, Oxide supports cross-compiling without the packaging - http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/view/head:/build/toolchain_configs/ubuntu-arm-linux-gnueabihf.cmake :)
[17:32] <chrisccoulson> I did start writing some instructions for it a while ago, but never got around to finishing them (https://wiki.ubuntu.com/Oxide/ArmCrossCompiling)
[17:32] <mterry> chrisccoulson, I've only really dealt with oxide yesterday and today but I already hate it
[17:32] <chrisccoulson> heh
[17:33] <mr_november> bzoltan, device_version result is device_version: 25: ./functions.inc: function: not found
[17:33]  * ogra_ wonders how to tell a webview about the timezone he is in ...
[17:33] <chrisccoulson> mterry, you need a fairly quick machine (I have 16GB of RAM and a Samsung 840 Pro SSD)
[17:34] <bzoltan> mr_november:  you need to be in that directory
[17:34] <ogra_> timestamps in articles in a page i show in the webview always jump around between UTC and my timezone depending on how often i reload
[17:35] <chrisccoulson> mterry, ok, that's linking now :)
[17:35] <mr_november> bzoltan, I am in /usr/share/qtcreator/ubuntu/scripts
[17:35] <mterry> chrisccoulson, sweet
[17:35] <bzoltan> mr_november:  well, if you do not have the functions.inc there then your SDK is prety badly busted
[17:36] <mr_november> functions.inc is there
[17:36] <mr_november> device_search returns 0098f70d1d524baa       device usb:2-1.1 product:occam model:Nexus_4 device:mako
[17:37] <bzoltan> mr_november:  so what `./device_version 0098f70d1d524baa` tells
[17:38] <bzoltan> mr_november: and ./device_wait_for_shell 0098f70d1d524baa
[17:38] <mr_november> hold on
[17:39] <mr_november> The first one returned nothing
[17:39] <mr_november> :|
[17:40] <mr_november> And second returns no such file or directory
[17:40] <mr_november> I think I should reinstall qt creator
[17:41] <bzoltan> mr_november:  I think you should remove all sdk and qtc related packages, check that you do not have any legacy PPAs or old packages and install it from the scratch
[17:42] <mr_november> bzoltan, just to check, I am on precise. Does that matter?
[17:42] <bzoltan> mr_november:  Err :) it does
[17:42] <mr_november> Oh great
[17:42] <bzoltan> mr_november:  you need to get permission from the archeology authorities to use such old SDK
[17:43] <mr_november> Lol
[17:44] <bzoltan> mr_november:  Okey :) at least we have figured out what the problem is. Enjoy your upgrade :) Trusty is cool.
[17:45] <mr_november> bzoltan, Trusty Tahr it is then, thanks
[17:45]  * ogra_ sighs about timezones ...
[17:45] <mr_november> bzoltan, until then, can you help me with something
[17:46] <mr_november> is there a way I can export all my SMSs?
[17:47] <ogra_> so if i click a link, the time is right on the target page when it loads first ... once i reload the page, the timestamp jumps to UTC
[17:47]  * ogra_ doesnt get that ...
[17:48] <ogra_> chrisccoulson, is there any secret property in oxide i could use to tell a webview about the timezone a user is in ?
[17:50] <spazzymoto> ogra, after some playing around it seems the partitions in my fstab.bacon are not mounting in the lxc container. Any ideas on how i can start to debug why?
[17:50] <ogra_> spazzymoto, check syslog and /var/log/dmesg
[18:04] <peat-psuwit> awe_: https://github.com/rilmodem/ofono/pull/174
[18:05] <peat-psuwit> awe_: Sorry for a delay. I was implementing multi-sim, but doesn't work.
[18:06] <peat-psuwit> That code doesn't for 2nd slot, but can be used for 1st one.
[18:06] <awe_> peat-psuwit, so is this a working branch, or do you still have work to do?
[18:06] <awe_> ok
[18:06] <awe_> as mentioned, I won't be able to get to this till next week sometime, but I'll share with abeato
[18:07] <awe_> fyi, you might want to change your description to mention the specific device.  The base rilmodem code works on the nexus4, which is a Qualcomm device
[18:08] <peat-psuwit> awe_: Oh, I forgot that. I'll edit that now.
[18:10] <peat-psuwit> awe_: Done.
[18:10] <awe_> thanks
[18:11] <peat-psuwit> awe_: How should I distribute this in my port?
[18:12] <awe_> well, we need to get the patch right first
[18:12] <awe_> we have try to maintain a single ubuntu read-only filesystem for touch images
[18:12] <awe_> so the idea would be to get your changes into the archive at some point
[18:12] <awe_> but as I mentioned, we need to first review, and I imagine they'll be some changes
[18:14] <awe_> if you really want/need to build a derivative image with custom packages, it's possible, but a lot of work, and you'd need to discuss someone else like maybe ogra_
[18:14] <peat-psuwit> awe_: It'll probably miss vivid's freeze deadline, right?
[18:15] <awe_> well, as ofono is really only used by touch, it's possible you might be able to get it in still, but that's not something I can answer right now
[18:15] <ogra_> for hacks you can ship stuff inside the device tarball
[18:15] <awe_> packages?
[18:15] <ogra_> no, files
[18:15] <awe_> yea, this needs a package
[18:15] <ogra_> and they get bind mounted into the rootfs
[18:15] <ogra_> so you need the "mountpoint files" in the rootfs too for that
[18:16] <awe_> peat-psuwit, again we'll need to review, and that'll have to wait till next week sometime... we have a lot of other work on our plate atm
[18:16] <awe_> so let's talk more next week
[18:16] <awe_> there's not much I can tell you today
[18:16] <peat-psuwit> awe_: That's fine. Thank you!
[18:16] <awe_> np
[18:17] <peat-psuwit> ogra_: You mean extract files in android's tree, and get them included in system image?
[18:18] <awe_> peat-psuwit, you probably don't want to go there...
[18:18] <ogra_> peat-psuwit, in your android tree there is an ubuntu/ subdir ...
[18:18] <ogra_> files in there will get bind mounted over existing files in the ubuntu rootfs if the path patches something existing
[18:18] <ogra_> s/pathes/matches/
[18:20] <peat-psuwit> ogra_: Oh, I miss that. You mean in device tarball, the same one that ships system.img, right?
[18:27] <ogra_> yes
[18:27] <kenvandine> renato___, in case you're around, check out https://code.launchpad.net/~ken-vandine/content-hub/serialized_content_transfers
[18:27] <ogra_> but your target file needs to exist, as i said
[18:28] <ogra_> since it will serve as mountpint for a bind mount
[18:28] <kenvandine> renato___, it's mostly what we discussed, ContentItem.stream is a QByteArray and adds a streamType property for the mime-type
[18:29] <kenvandine> renato___, and i added convenience getter/setter for text which sets the stream to a string and the streamType to plain/text
[18:29] <peat-psuwit> ogra_: Okay, I'll try that.
[18:29] <kenvandine> renato___, i still need to do the same with url, store it in the same stream instead of a separate variable, i'll get to that after i get back from vacation :)
[19:13] <Se7> shit fb app crashed all phone
[20:18] <ogra_> hmm, now i thought there is a new version of popey's stallboard with tedg's voice ... https://appstore.bhdouglass.com/app/tedtalks.mk1973 ...
[20:19] <ogra_> ... but in the end it isnt :)
[20:19] <tedg> :-(
[21:00] <brunch875> Wohooo! New keyboard for 20€. And it's a good one! I'm like a child with a new toy
[21:00] <brunch875> By the way, GPS has stopped working at all for me
[21:00] <brunch875> nothing works, even after factory reset
[21:00] <brunch875> Is there trouble with the servers or am I the only one?


[16:37] <hwpplayer1> Hi people
[17:39] <thgarnie> hi, I noticed that x86_64 ubuntu kernel configuration enables CONFIG_FUNCTION_TRACER on all SKUs. On x86_64 it hads a call on each function by default, do you know why it is enabled?
[17:39] <thgarnie> -hads +adds
[17:44] <thgarnie> Waste about 1.2% time in average on hackbench.
[18:14] <kees> ogasawara, apw: ^^
[18:15] <apw> hwpplayer1: you trade off debugability against performance always
[18:16] <apw> it adds 4 or 5 noops to the top of an untraced function iirf
[18:16] <apw> iirc
[18:16] <thgarnie> no, not on x86_64
[18:16] <thgarnie> that's what the config says
[18:16] <thgarnie> the reality is a call __fentry__
[18:16] <thgarnie> Not sure if it is badly implemented on x86_64 (because you can do mnop-mcount) or because it is hard to do the nop swap.
[18:49] <thgarnie> Correction, the nop is added a runtime instead of using -mnop-mcount. Odd that it didn't happen when PIC is enabled then hum.
[18:50] <thgarnie> Not sure why I see a 1.2% average difference with/without function tracing on hackbench.
[19:14] <hwpplayer1> apw : it is not that easy
[21:51] <jjohansen> sforshee: pull request sent to the ml