[00:07] <h6w> You probably get asked this question a million times a day, but I've googled for an hour and can't find an answer.   I can only find a 32-bit version for PC.  Is there a 64-bit version, or should I be installing Ubuntu Desktop and then doing apt-get remove ubuntu-desktop; apt-get install ubuntu-touch ??
[00:08] <h6w> Or is there some issue that's stopping it from working on a 64-bit machine?
[01:37] <h6w> No answer, so I've posted it as an askubuntu question.  http://askubuntu.com/questions/705293/ubuntu-desktop-next-has-gone-how-do-i-install-64-bit-ubuntu-touch
[02:03] <lpotter> can't you get a 64bit image here? http://www.ubuntu.com/download/desktop
[02:04] <lpotter> or you want to install touch on a pc?
[02:10] <k1l> he got a intel tablet which is a tablet but with PC hardware build in. and now wants the ubuntu-touch running on that, which afaik doesnt work right now.
[04:26] <sciango> Hi guys, quick question. When creating an app in the Ubuntu SDK that will use GPS, is it better to use QML documentation standards or are there specifics instructions for Ubuntu Touch. I'm trying to RTFM, but I don't know which manual I should start with. If you could point me in the right direction, that would be great.
[06:45] <lotuspsychje> lol whatsapp blocks links to telegram...
[06:46] <k1l> well, didnt MS show how to keep your monopoly? :/
[06:47] <lotuspsychje> k1l: i dont use whatsapp myself mate, just readin the news :p
[06:49] <k1l> was no judging on the users of whatsapp. but whatsapp got a monopoly on the messengers now imho and seems they want to keep it.
[06:49] <lotuspsychje> ah ic
[06:50] <k1l> unfortunately i need to use whatsapp :/
[06:51] <lotuspsychje> k1l: the too many relatives connected problem heh?
[06:51] <lotuspsychje> i cant convince my friends to use telegram neither
[06:52] <k1l> my sportsteam does all the communication and planing about whatsapp groups.
[06:53] <lotuspsychje> yeah its a pain k1l
[07:26] <myweeshift> anybody using touch on  nexus 5?
[07:26] <lotuspsychje> !devices | myweeshift
[07:27] <myweeshift> thanks lotuspsychje, i saw that.
[07:27] <myweeshift> was wondering if its stable/functional enough to be on my primary/only device for at least a few days to check it out.
[07:28] <lotuspsychje> myweeshift: touch should work on n5 but with some issues i think
[07:32] <myweeshift> are some people using touch as their 'daily driver' on mobile?
[07:33] <lotuspsychje> myweeshift: sure BQ 4.5 here
[07:33] <myweeshift> nice
[07:35] <nhaines> No Bluetooth on the N5.  Otherwise, last time I used it, it worked great.
[07:35] <nhaines> ogra_: I think I heard you were going to be at Ubucon Summit!  :)
[07:37] <myweeshift> cool. thanks nhaines.  does the install mess with twrp? or can i hopefully get it loaded and then be able to just use nandroid backups to switch at my leisure?
[07:43] <nhaines> myweeshift: You'll have to flash it manually then.  I used to use MutiROM Manager, but since I upgraded to Android 6.0 it's not compatible.
[07:44] <myweeshift> im still on 5.1.1 and plan on staying there awhile.  maybe ill check out MultiROM then.
[07:49] <myweeshift> nice. that looks pretty straight forward.  thanks!
[07:57] <myweeshift> looks like an easy workaround for 6.0 as well. http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011/page311
[08:19] <dholbach> good morning
[09:16] <rbasak> "Last full charge 95 hours ago"
[09:16] <rbasak> This battery just won't die!
[11:50] <Mozz1> Hi All
[15:25] <sturmflut> Hm, the "good" news is that the krillin/vegetahd kernels ship the MediaTek FM radio driver, the firmware has to be moved to the right place but when you do it the FM radio part comes up and reports itself correctly. I can power up and tune the chip with a single ioctl()
[15:26] <sturmflut> The bad news is: no audio up til now, and the kernel crashes pretty much all the time once you want to actually do something useful
[15:56] <mcphail> sturmflut: that's quite cool, though. Thanks for keeping poking at that kernel
[15:57] <tvoss> sturmflut, you will likely need upper layers of the stack, too, though.
[15:58] <tvoss> sturmflut, I will see what I can do to get you some more insight
[16:01] <davmor2> sturmflut: I am assuming that you have the headset plugged in when you test this right?
[16:04] <davmor2> sturmflut: I discovered when my fm didn't work on an android phone that it only works with a headset plugged in, it uses the ground as an areal and the audio is routed to the headphone jack, might be the case here too
[17:31] <beni_> hei is there any developer
[17:33] <beni_> i need help
[17:34] <beni_> can anyone help me with my ubuntu sdk trouble
[17:36] <beni_> ??
[17:36] <beni_> i need help is anyone online
[17:37] <ogra_> beni_, SDK people are more likely in #ubuntu-app-devel
[18:00] <sturmflut> davmor2: The kernel crashe was me misunderstanding a parameter (I passed 10630 when I should have passed 1063 instead), the too large value triggers some strange bug in the MediaTek kernel code which then either crashes the kernel by itself or leads to a watchdog rebooting the device
[18:04] <davmor2> sturmflut: I was meaning more for getting the audio out
[18:05] <sturmflut> davmor2: AFAICS the output of the FM chip is connected to a regular input of the sound card, and one of the sound card outputs is connected to the input of the FM chip. Audio output is not always routed to the headphone jack, that just seems to be the default because you have to plug in the headphones (antenna) which automatically switches the audio to the headphones. But the Android radio apps can also usually switch to the
[18:05] <sturmflut> loudspeaker or even record the FM signal
[18:05] <davmor2> sturmflut: ah true
[18:06] <sturmflut> When you run "pactl list" on the Aquaris E4.5 you can see "input-fm" and "output-fm_tx"
[18:08] <sturmflut> I've had no luck switching to input-fm though. I think I've initialized the FM chip correctly, unmuted it and tuned it to a station, but don't hear anything
[18:23] <sturmflut> Oh Oh, I have a feeling I know what's going on
[18:59] <tvoss> sturmflut, any progress? :)
[18:59] <tvoss> sturmflut, anything you want me to look at?
[19:04] <sturmflut> tvoss: still fighting with the kernel driver, it doesn't crash anymore at least ;)
[19:10] <studio_> hi
[19:13] <studio_> i was reading about ota-9 and new kernels. So ota-9 will be based on 16.04, and what kernel version is used for the ubuntu-touch devices?
[19:15] <pmcgowan> studio_, ota9 is not on 16.04, we won't move there for some time, certainly not until it releases
[19:18] <studio_> pmcgowan, is this a false message: http://news.softpedia.com/news/ubuntu-touch-ota-9-receives-new-unity-8-next-gen-bluetooth-support-more-496516.shtml ?
[19:19] <pmcgowan> studio_, no thats all good
[19:20] <pmcgowan> we update kernels all the time
[19:20] <ogra_> not to new versions though :)
[19:20] <pmcgowan> correct
[19:22] <studio_> i am confused, i thought after i have seen this video: https://www.youtube.com/watch?v=ru6cQMEt52s all ubuntu-touch devices will be based on xenial?
[19:22] <popey> in the future
[19:22] <popey> not today
[19:23] <studio_> so in 2016?
[19:23] <popey> Yes, we'll likely switch to a new release next year sometime.
[19:23] <studio_> ok
[19:23] <ssweeny> Before or after vivid goes EOL in January(?) :)
[19:23] <popey> But we may not switch to a new kernel.
[19:24] <studio_> so for the nexus it is possible in the moment to install xenial, but not for the bq devices?
[19:25] <popey> it may be possible on various devices, but we don't recommend it
[19:28] <studio_> my device is not a, how to say in english, working / productive device, it is just for learning and playing, so what channel i have to use to try xenial?
[19:29] <popey> devel-proposed I _think_
[19:30] <studio_> is it the pure ubuntu-channel without the bq apps?
[19:30] <popey> i expect so, the bq ones have bq in the name
[19:31] <studio_> cool :) i'll try that on the weekend ...
[19:33] <studio_> popey, i've seen on the video, that your nexus 7 (arm-based) is working with xmir, is that correct?
[19:33] <popey> it was, i reflashed it since
[19:33] <studio_> why?
[19:33] <popey> i reflash my devices all the time
[19:34] <studio_> so now all the "programms" are not working anymore on your device? I mean programms, not apps ...
[19:35] <popey> well, i reflashed it, so they're not installed
[19:36] <studio_> popey, what exactly do you mean with "reflashed" ?
[19:36] <popey> wiped / reinstalled
[19:36] <studio_> with what?
[19:36] <popey> different channels for testing different things
[19:37] <studio_> ah, ok, so you are still using ubuntu-touch?
[19:37] <popey> yes, of course
[19:38] <studio_> ;) sorry for that question ...
[19:43] <studio_> what about this: https://github.com/mbgg/linux-mediatek Did someone here had a success to build a working multi-armv7-kernel for the bq devices?
[19:44] <ogra_> what for would we do that ?
[19:45] <ogra_> none of the drivers could work with it
[19:48] <studio_> ogra_, good question, maybe for an real linux kernel? So why mbgg tried to do that? I think mbgg is working for bq, right?
[19:48] <ogra_> no idea
[19:49] <ogra_> having a linux kernel will gain you a headless non-networked server ... thats all
[19:49] <ogra_> none of the devices will work
[19:50] <studio_> maybe as an iPod-Touch :)
[19:50] <ogra_> well, without audio drivers and screen
[19:51] <studio_> without framebuffer and alsa?
[19:52] <ogra_> well, you might get a framebuffer console to work ... but no touchscreen and yes, no sound without drivers for the chip
[19:54] <studio_> why mkt do not build blobs for the latest kernel for the devices?
[19:55] <ogra_> because nobody pays for that
[19:55] <ogra_> they build blobs for android
[19:55] <tvoss> ogra_, more precisely: shipping hw that is making them money
[19:55] <studio_> who need to pay, bq, meizu or canoncial?
[19:55] <tvoss> and that hw happens to run android :)
[19:56] <ogra_> right, what tvoss said
[19:57] <popey> studio_, same with every single other android device manufacturer. No motivation to port to newer kernels if nobody is paying for the work.
[19:58] <studio_> so again, who needs to pay, to make blobs for the latest linux kernel, bq, meizu or canoncial?
[19:58] <ogra_> popey, well, its not abotu 2porting to new device kernels" it is about porting to non-android systems ;)
[19:58] <popey> well it is both
[19:58] <ogra_> indeed, one bases on the other
[19:59] <popey> studio_, someone needs to pay developers
[19:59] <studio_> both= manufactor and canoncial?
[19:59] <popey> I think you're missing the bigger picture.
[19:59] <ogra_> studio_, usually a manufacturer has a contract with the chip manufacturer ... and that includes what SW gets provides to the device manufacturer
[19:59] <ogra_> *provided
[19:59] <popey> Once devices get more than a couple of years old, they get near-zero revenue from sales of that device, because everyone has moved on to the next generation
[19:59] <popey> once sales dry up there's little motivation to support that device
[20:00] <ogra_> years ?
[20:00] <popey> if that
[20:00]  * ogra_ would have said months :) 
[20:00] <popey> heh
[20:02] <studio_> so, as i understood correct, there will never be an real supported ubuntu-touch device? all is depending from the chip manufactorer?
[20:02] <k1l> the one who wants the new kernels will have to pay the developer to do that.  at the moment that is neiter meizu, nor bq nor canonical.
[20:03] <ogra_> yeah, because neither is interested in running a driver less kernel on old hardware :)
[20:03] <k1l> there are already 3 real supported ubuntu-touch devices
[20:04] <ogra_> yeah
[20:04] <studio_> k1l, also (google) nexus is not supported ...
[20:04] <ogra_> and more to come
[20:04] <k1l> dont confuse "read support" with "not using drivers that were made for another system"
[20:04] <k1l> *real
[20:05] <k1l> studio_: i only mentioned the once that got sold preinstalled
[20:05] <studio_> k1l, what 3 years old devices are supported?
[20:05] <k1l> nexus4
[20:06] <studio_> uname -a ?
[20:06] <popey> are we going to have this lengthy conversation again?
[20:06] <popey> Or shall we just stop it now?
[20:06] <k1l> studio_: why are you hunting about the kernel versions?
[20:06] <studio_> because i am talking about "support"
[20:06] <k1l> studio_: i think you got explained lenghtly that your wish to have the latest kernels is not comming true until you pay developers to do the work
[20:07] <k1l> studio_: no
[20:07] <k1l> there is suport.
[20:07] <ogra_> studio_, what is support in your view ?
[20:07] <studio_> latest kernel, latest bug-fixes
[20:07] <ogra_> (security and bug fixes at a regular base ... no regressions ... )
[20:08] <ogra_> latest kernel will bring in new bugs and regressions
[20:09] <studio_> k1l, what is the release number, including patch version from your kernel on your google device?
[20:09] <ogra_> (and cause additiojnal costs since all drivers need to be ported)
[20:10] <popey> studio_, the same version as the last time you asked.
[20:10] <studio_> popey, i never asked k1l about that!
[20:11] <ogra_> and you think he runs another kernel than the rest of the world ?
[20:11] <popey> If k1l is running Ubuntu then it's the same version as the rest of us.
[20:12] <studio_> popey, i thought an mx4?
[20:12] <studio_> popey, i thought you got an mx4?
[20:12] <popey> i have multiple devices
[20:12] <studio_> so?
[20:12] <popey> so?
[20:12] <studio_> uname -a
[20:12] <popey> Linux ubuntu-phablet 3.4.0-7-mako #1-Ubuntu SMP PREEMPT Thu Sep 3 15:30:20 UTC 2015 armv7l armv7l armv7l GNU/Linux
[20:13] <popey> thats my nexus 4
[20:13] <popey> which is currently powered on and attached to my pc
[20:13] <popey> Linux ubuntu-phablet 3.4.67 #1 SMP PREEMPT Wed Oct 28 09:14:30 UTC 2015 869191d armv7l armv7l armv7l GNU/Linux
[20:13] <popey> that's my bq
[20:13] <popey> my mx4 is broken at the moment
[20:13] <popey> but I know that's 3.10.something
[20:13] <mcphail> popey: did yo break it with a new kernel? ;p
[20:14] <popey> Now listen.
[20:14] <studio_> 3.4 - what is the latest patch? .110?
[20:14] <popey> I broke it with my bum, sitting on it.
[20:14] <popey> no idea studio_
[20:14] <studio_> kernel.org
[20:14] <mcphail> popey: it might not have broken if your kernel had been fully patched
[20:15] <tvoss> rofl
[20:15] <popey> Get back in your box.
[20:16] <studio_> that is, what i do not understand. my desktop version always get the latest kernel patch, but my ubutu-phone not.
[20:16]  * mcphail is interrupting an evening of Nordic Noir with Saga Noren for this entertainment...
[20:16]  * popey googles those
[20:16] <lotuspsychje> mcphail: any news on your battery drain?
[20:17] <mcphail> lotuspsychje: no problems since moving to rc-proposed, but my suspicion is it was dekko notifications which caused it. I'm going to reenable those to test
[20:17] <lotuspsychje> mcphail: ah cool
[20:19] <k1l> studio_: its 3.4.0-7-mako
[20:19] <studio_> another question is, why is the kernel in the ubuntu-touch device a monolithic kernel?
[20:20] <dobey> oh ffs
[20:20] <tvoss> it can only go south from now on
[20:20] <dobey> all linux kernels are monolithic kernels
[20:20] <k1l> studio_: and again: i think you still dont understand that a new kernel will magically solve everything.
[20:20] <tvoss> studio_, by design and on purpose since version 0.0.1
[20:20] <tvoss> studio_, you might want to read up the lengthy mal thread between tanenbaum and torvalds on the topic
[20:20] <k1l> studio_: and your PC comparison doenst work, because you dont have the same driver situation like on the PC. which was explained to you 100 times already?
[20:20] <dobey> if you want a different kernel, try HURD maybe
[20:21] <tvoss> dobey, yeah, that would be awesome :)
[20:21] <studio_> dobey, my,on my desktop, is modular ...
[20:21] <tvoss> studio_, it's not
[20:21] <dobey> no, it is monolithic
[20:21] <lotuspsychje> labyrinth night again..
[20:21] <studio_> itis not? so why i can losd modules?
[20:21] <dobey> lotuspsychje: if only i could balance a glass sphere as well as david bowie
[20:21] <studio_> it is not? so why i can load modules?
[20:22] <tvoss> no need to repeat your question ;)
[20:22] <dobey> because you don't understand what "monolithic kernel" means
[20:22] <dobey> why are you back here trolling again anyway? so you can be banned again?
[20:23] <mcphail> studio_: running HURD on your phone will give the same experience as running HURD on your desktop, if that's what you want?: nothing will work on either!
[20:23] <k1l> dobey: ubuntu people are to friendly :(
[20:23] <studio_> dobey, "monolithic kernel" means, no otion to load modules, all needed modules are compiled direct into the kernel.
[20:24] <mcphail> studio_: no, lovey, it doesn't
[20:24] <ogra_> stno such thing on a phone
[20:24] <dobey> k1l: i know right
[20:24] <tvoss> studio_, you might want to start digging here: https://en.wikipedia.org/wiki/Tanenbaum%E2%80%93Torvalds_debate
[20:25]  * mcphail is getting a bit bored of this and his mind is beginning to wander back towards Scandanavians in leather trousers
[20:25] <lotuspsychje> lol
[20:25] <tvoss> studio_, the original thread on comp.os.minix is *highly* recommended
[20:25]  * tvoss is a little scared now
[20:25] <dobey> ios might be microkernel though? not sure really
[20:25] <dobey> but linux is definitely a monolithic kernel
[20:26] <tvoss> dobey, well, that depends how you classify a mach kernel ... admittedly, it *used* to be called a microkernel
[20:26] <popey> I am pretty sure that's the first time in the near 3 years of this channel existing that anyone has been called "lovey" here.
[20:26] <popey> Well done mcphail
[20:26] <tvoss> it's getting cozy I guess
[20:26]  * ogra_ grins
[20:26] <mcphail> popey: I have a "thing" for studio_
[20:27] <k1l> iOS is at best a "hybridkernel" but still based on monol.
[20:27] <popey> Clearly.
[20:28] <mcphail> But I'm afraid my love for Saga wins out. See you all in an hour, if studio_ hasn't been banned by then
[20:28] <dobey> https://i.imgur.com/6bZMF.png
[20:29] <tvoss> if only irc had inline link preview ;)
[20:29] <dobey> now i want popcorn
[20:30] <dobey> tvoss: it does if you write a client that provides that ;)
[20:30] <tvoss> dobey, obviously ;) my vanilla xchat does not, though. probably should jump over to their irc channel and paste links to stickers requesting the feature
[20:31] <popey> Time to switch to MS Comic Chat.
[20:31] <dobey> or just write an irc client in the sdk that works on the phone, and make everyone happy
[20:31] <tvoss> dobey, fair, and a bouncer that talks to our push infrastructure
[20:31] <tvoss> or better: adjust a bouncer
[20:32] <tvoss> popey, admittedly, the idea is quite cool :)
[20:32] <studio_> maybe it is a beginner question, but where is the differen between a monolithic and an modular kernel? i allways thought android is using an monolithic kernel?
[20:32] <dobey> android uses linux, so yes it's using a monolithic kernel
[20:33] <tvoss> studio_, https://www.google.de/?gfe_rd=cr&ei=8qZgVvedKOaI8Qef6Yu4Bw&gws_rd=ssl#safe=off&q=monolithic+vs+microkernel
[20:33] <dobey> can compile part of the features as loadable modules !+ "modular"
[20:34] <studio_> so a monolithic kernel can be a modular? sorry i am now confused ...
[20:35] <dobey> https://en.wikipedia.org/wiki/Monolithic_kernel#Loadable_modules
[20:35] <tvoss> studio_, think about it like this: monolithic kernel = one giant process running your kernel, microkernel = multiple processes taking over kernel tasks
[20:35] <dobey> since apparently you don't know how to sue a search engine yourself
[20:36] <studio_> dobey, i have seen that, but i do not understand the different to an modular kernel :(
[20:36] <dobey> can load modules != modular kernel
[20:36] <studio_> but monolithic also can load modules
[20:37] <dobey> anyway, loadable modules on a phone are pointless
[20:37] <dobey> it's a waste of storage space for no meaningful benefit
[20:38] <ogra_> well
[20:38] <ogra_> lots of phones have modules in use
[20:38] <studio_> dobey, i tried it with nfs, but no succsess
[20:38] <k1l> studio_: https://de.wikipedia.org/wiki/Monolithischer_Kernel
[20:38] <studio_> https://en.wikipedia.org/wiki/Monolithic_kernel
[20:39] <dobey> if you really want to build all the bits as modules, feel free to recompile your own kernel, break your phone, and not ask for random other people to help fix it when you do
[20:39] <tvoss> dobey, hah, the joys of freedom :)
[20:40] <dobey> tvoss: unfortunately, some people don't understand freedom, but think they are entitled to certain things
[20:40] <studio_> dobey, you can't brake the phone by uplading a kernel and its modules. you need to destroy u-boot.
[20:40] <k1l> freedom means i dont have to pay others to do my work, right? :)
[20:41] <tvoss> k1l, of course, and *your* feature request is the center of the universe
[20:41] <tvoss> ;)
[20:41] <k1l> check
[20:41] <tvoss> dobey, yup, I meant to hint at that
[20:41] <ogra_> feature demand !
[20:41] <ogra_> pfft ... request :P
[20:42] <dobey> a hammer works well too
[20:44] <dobey> or guns. we really like to shoot things over here
[20:46]  * dobey would really like for this new qt to be unblocked already
[20:47] <k1l> will the n4 stay the dev phone for the next time?
[20:48] <k1l> looking at getting a mhl adapter thingy for the "total convergence" :)
[20:48] <ogra_> given it is the only device that can use external displays ...
[20:49] <dobey> and that we don't support the nexus5
[20:49] <dobey> :(
[20:50] <studio_> ogra_, why? isnt the mx4 supporting mhl?
[20:50] <ogra_> nope
[20:50] <studio_> since when?
[20:50] <ogra_> since forever ?
[20:50] <popey> nexus 7 also supports it, so one of two devices
[20:50] <studio_> the specs told mhl is supported?
[20:51] <k1l> mine n4 had a broken mainboard (from been drowned in a lake, i suppose). but i got a old n4 with a broken screen from a friend and combined them to a working one again :)
[20:51] <ogra_> frankenphone :)
[20:51]  * ogra_ has an old n4 like that here too
[20:51] <sturmflut> studio_: No, some external websites said that. Meizu hasn't had MHL since the original MX I think
[20:52] <k1l> as long as it works™
[20:52] <k1l> maybe the typical rumors pre-release?
[20:52] <ogra_> yeah
[20:53] <dobey> at least it should theoretically be possible to get bt working on n5 now
[20:53] <dobey> since we have bluez5
[20:57] <studio_> hmm ... http://www.siliconimage.com/Company/News_and_Events/Press_Releases/2014_02_23_-_Silicon_Image_Announces_New_MHL%C2%AE_Smartphone_Reference_Designs_with_MediaTek/
[20:57] <studio_> i thought that MT6595 can handle mhl ...?
[20:57] <ogra_> if it is wired up internally and the driver supports it ...
[20:58] <dobey> chip != phone
[20:59] <dobey> just like how my i7 cpu can display 4k at 60hz just fine, but the drivers in linux don't do it right
[20:59] <ogra_> well
[20:59] <k1l> studio_: the chip can handle it. but what if there is no connector from the chip to the mainboard?
[21:00] <ogra_> except that your i7 isnt a custom made SoC that was only created for this PC
[21:00] <dobey> it could be :)
[21:00] <ogra_> and just happens to use the intel core
[21:01] <dobey> that soc isn't the whole phone though, just like my intel cpu isn't my whole pc
[21:01] <sturmflut> k1l, studio_ : The MediaTek chip cannot handle it, we've had this discussion on the ML months ago: https://lists.launchpad.net/ubuntu-phone/msg15154.html
[21:01] <k1l> sturmflut: oh come on, dont come with facts :)
[21:02] <k1l> studio_: read that mailinglist post
[21:02] <sturmflut> To my knowledge there isn't a single MediaTek SoC that has MHL support on chip
[21:02] <dobey> and no matter which intel chip i shove in this motherboard, 4k@60hz still won't work correctly in linux, because the drivers don't/won't do it correctly
[21:02] <ogra_> dobey, well, the SoC is 60% of the phone ... compared to your PC it is the CPU, RAM and half your PCI cards :)
[21:02] <sturmflut> They all require external bridges
[21:03] <dobey> ogra_: the cpu is pretty much 60% of my PC :)
[21:03] <ogra_> heh
[21:04] <sturmflut> Bah, giving up on FM radio for today.
[21:04] <ogra_> once you are done they shut down the stations
[21:04] <dobey> well i could compare an Atom instead, which is even more so a SoC design
[21:04] <ogra_> :)
[21:04] <dobey> and we all know how the GMA500 turned out
[21:04] <dobey> aka poulsbo
[21:06] <ogra_> as good as the SGX :P
[21:06] <ogra_> given they are the same after all :)
[21:06] <sturmflut> ogra_: I find it funny that no digital terrestrial broadcast standard has had any success in Germany, yet they want to shut down FM all the time
[21:07] <ogra_> yeah
[21:07] <sturmflut> Also we could transmit data between two Ubuntu phones via short-range FM if this works out
[21:08] <sturmflut> At several kilobits per second
[21:08] <ogra_> thats indeed true and would be a cool thing
[21:08] <ogra_> enough to transfer a vcard or a calendar entry ;)
[21:09] <dobey> you should implement http://bu.mp for ubuntu
[21:09] <sturmflut> FM is the new NFC ;)
[21:09] <dobey> another thing that got bought and murdered
[21:10] <ogra_> didnt smasung do a ripoff ?
[21:10] <ogra_> *samsung
[21:10] <dobey> no idea
[21:12] <dobey> but it was one of the big things of webos, right before HP gave it the axe too
[21:13] <pmcgowan> did someone says poulsbo
[21:13] <pmcgowan> makes me sweat still
[21:13] <ogra_> haha
[21:16]  * k1l still got a hp touchpad :)
[21:19] <sturmflut> Well, enough FM and off to celebrating my new membership status
[21:44] <popey> Hm, anyone know how to get ubuntu-emulator to pass "-no-window" down the stack to qemu?
[21:44] <popey> seems ubuntu-emulator builds a set of parameters which it gives to the real emulator in /usr/share/android/emulator/out/host/linux-x86/bin/emulator-x86
[22:08] <taiebot> Hi is it kown that shorts do not work anymore on rc-proposed?
[22:13] <popey> taiebot, works here
[22:14] <taiebot> popey Yeah it restarted working just realised i had the message like some channels could not get updated for like two days.
[22:17] <taiebot> popey  could it be engadget new website?
[22:17] <popey> taiebot, dunno, i dont have that on my list, can you check the log in ~/.cache/upstart ?
[22:17] <popey> it typically logs quite nicely
[22:17] <taiebot> popey i am still getting some errors occurred during the update
[22:21] <taiebot> popey http://paste.ubuntu.com/13653105/
[22:21] <popey> thats not the official shorts app
[22:21] <popey> that's a preview / beta
[22:22] <taiebot> popey: is it ?
[22:22] <popey> yup