[03:18] <nhaines> >_>
[03:18] <nhaines> Someone should just push "tutanota-webapp" through approval.  :P
[03:30] <nhaines> Ooh, it might've been automatic.  Yay!
[04:47] <rich> hello all...just  installed touch on my d2spr...seems to be working  ok thus far...but i do not have any access to a wifi menu...is thius something i need to do through a terminal window?  any help at all would be much appreciated.
[08:17] <brunch875> Good morning in the morning!
[08:33] <JamesTait> Good morning all; happy I Need A Patch For That Day! 😃
[09:38] <seb128> bfiller, cyphermox, do you know if bug #1456112 is a n-m issue or due to something else?
[09:39] <seb128> dns not changing when switching from carrier data to wifi
[09:39] <seb128> seems like BT enforces the dns to be the wifi ones (for content filtering) and it things bug
[09:52] <seb128> Elleo, hey, just checking with you, but the osk still doesn't have support for quotes or brackets completion right?
[09:52] <seb128> Elleo, I'm looking at doing the string change from bug #1385288
[10:10] <Elleo> seb128: yeah, that's still not implemented
[11:33] <eointierney> Hello wonderful people, aquaris 4.5 owner here, looking for advice.
[11:33] <eointierney> First up, it's buggy as a termite mound, but I'm still fond of it :)
[11:33] <mcphail> eointierney: the bugs are endearing
[11:34] <eointierney> They are certainly expensive :)
[11:34] <eointierney> I want to change some things, like move to duckduckgo as default search engine.
[11:36] <eointierney> The main problem is the lack of documentation, any pointers?
[11:37] <eointierney> I have it hooked up via qtcreator(ubuntu sdk version) and am browsing around.
[11:38] <eointierney> There seem to be some novel wheel designs, though they seem to rotate in one direction only.
[11:41] <mcphail> eointierney: the browser is pretty basic just now. I find it _renders_ extremely well but lacks other features. All the apps are being developed by small teams of people so the imrovements are coming through slowly and steadily. The browser app will be getting a bit of polish with the next update. Put in a bugreport for a feature request. The devs are very responsive and interactive
[11:41] <cwayne> i think there is a way to set the default search engine
[11:41] <cwayne> just not from the UI maybe
[11:41] <cwayne> oSoMoN_, ^
[11:42] <eointierney> Hey, I'll an early adopter, it just needs a little lovin'
[11:43] <eointierney> I'm a little puzzled why so many things are baked in. Also, lack of documentation.
[11:43] <eointierney> And it's a little past bug reports. They device is actually barely functional.
[11:45] <eointierney> I was happy to add a hosts file for simple addblocking, but it's hacky.
[11:45] <ogra_> cwayne, picking the start page is in vivid
[11:45] <ogra_> but not in rtm
[11:45] <eointierney> I should say kludgy.
[11:45] <oSoMoN_> eointierney, mcphail, cwayne: the devel images already have a UI for settings in the browser, which allows changing the default search engine. RTM will be getting it with the next OTA update
[11:45] <ogra_> right
[11:46] <eointierney> I've had a look at changing image but the instructions are unclear, any pointers? I'm happy to eat any dog food right now.
[11:46] <ogra_> eointierney, if you make changes to existing files on the readonly partition, they will be reverted with the next OTA
[11:46] <mcphail> eointierney: the security model is very tight, just now. That locks down /etc/hosts which makes it difficult to edit. Apps would not have direct access to edit /etc/hosts without the blessing of the ubuntu-touch team
[11:46] <eointierney> @ogra, I know, which is why I've a script to do it for me :)
[11:46] <ogra_> :)
[11:47] <mcphail> eointierney: changing to a vivid channel is quite easy, but vivid is coming soon by default anyway
[11:48] <eointierney> @mcphail? How soon? And I'm fond of breaking things, so how would one change channel?
[11:50] <mcphail> eointierney: it only takes a couple of minutes to change channel. I don't have access to a browser just now to give you a link to the doc page but if you search for "ubuntu-touch change channel" it will take you there
[11:50] <mcphail> eointierney: I think vivid is coming by default in about 2 weeks, but I may be being optimistic :)
[11:51] <brunch875> ubuntu-device-flash touch --channel=devel --bootstrap
[11:51] <brunch875> and you'll be using the devel channel!
[11:51] <mcphail> eointierney: I've played with the vivid channels and changed back again. No problems beyond having to run my script to set up /etc/hosts, ringtone etc
[11:51] <brunch875> --bootstrap wipes so, careful
[11:51] <mcphail> brunch875: don't need --bootstrap
[11:52] <brunch875> I believe it does for the BQ devices
[11:52] <mcphail> brunch875: I've never used it...
[11:52] <brunch875> In that case it probably doesn't :D
[11:52] <mcphail> brunch875: i've changed to vivid, vivid-proposed and back to rtm without using the --bootstrap flag :)
[11:53] <brunch875> hacker's gift!
[11:54] <eointierney> So ubuntu-device-flash touch --channel=devel is all I need?
[11:54] <eointierney> I love floss communities :)
[11:54] <seb128> Elleo, thanks
[11:54] <mcphail> eointierney: there are different channels to explore
[11:54] <Elleo> seb128: no problem
[11:54] <eointierney> @mcphail is there a listing?
[11:54] <brunch875> https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/
[11:54] <mcphail> eointierney: there is a command to list them if you search for that page...
[11:55] <Elleo> eointierney: devel-proposed is probably a better choice than devel currently if you're wanting to experiment with new stuff, there hasn't been a promotion to devel in quite a while
[11:55] <brunch875> orrrr I think you can do this
[11:55] <brunch875> ubuntu-device-flash query --list-channels --device=DEVICE
[11:55] <mcphail> that'll be the one
[11:55] <eointierney> Yahoo, so devel-proposed it is.
[11:55] <mcphail> the bq device name is krillin
[11:55] <Elleo> oh actually, the channels were renamed recently
[11:56] <eointierney> Teh Awesomes!
[11:56] <Elleo> eointierney: ubuntu-touch/rc-proposed/bq-aquaris.en might be the best option if you just want newish but fairly stable stuff (that's basically what will become OTA4 when finally ready)
[11:57] <Elleo> devel-proposed is tracking wily now, which isn't much different from that channel at the moment, but could diverge a lot in the future as snappy stuff gets worked on
[11:57] <eointierney> Elleo: thank you, I was about to ....
[12:36] <eointierney> Thank you all, slight improvements noticed but still idiotically dependent on google for search, third-party contact imports, I'm sure much more.
[12:42] <cyphermox> seb128: that smell of a NM bug, thanks. That said, there isn't enough info to know what the real problem is
[12:42] <seb128> cyphermox, k, at least I redirected it at the right place then ;-)
[12:42] <seb128> cyphermox, thanks
[13:15] <jgdx> seb128, there you go :p
[13:15] <seb128> jgdx, context? ;-)
[13:15] <jgdx> seb128, bug comment
[13:15] <jgdx> why not just unsubscribe yourself?
[13:16] <seb128> jgdx, thinking about everybody else subscribed to settings
[13:16] <seb128> or we all need to go unsubscribe
[13:16] <seb128> it's ridiculous
[13:16] <jgdx> seb128, only those who do not filter bugs
[13:17] <seb128> I do filter bugs
[13:17] <seb128> but those come through a change to a settings bug
[13:17] <seb128> so they spam my settings box
[14:37] <nik90> hey guys, is there a way to get Nokia HERE AGPS on vivid-proposed channels on N4?
[14:38] <nik90> I have it on my bq running rtm, but need it for testing purposes on my N4 as well for quick locations test
[14:38] <kenvandine> mandel, remember my rebase of your fix-network and fix-network-errors branches?
[14:39] <kenvandine> mandel, seb128 is testing it  and it's not finding click updates
[14:39] <mandel> kenvandine, yes, the ones done in the sprint, tell me
[14:39] <kenvandine> if he downgrades to the vivid version, there are updates available
[14:39] <mandel> kenvandine, silo? I'l take a look
[14:39] <seb128> document viewer and authentificator are listed with the vivid version
[14:39] <kenvandine> so that network code must be failing
[14:39] <kenvandine> silo 34
[14:39] <mandel> kenvandine, ack
[14:40] <kenvandine> mandel, thx, i don't have time to look at it now and you really wrote that code. i'm sure you understand it best :)
[14:41] <kenvandine> mandel, so just base any fixes for it on my branch, actually on my fix-network-errors branch which is stacked
[14:41] <mandel> kenvandine, got you, I'll do some decen debugging and will find out what is going on
[14:42] <kenvandine> mandel, thanks man!
[14:42] <kenvandine> mandel, always fun to come back from vacation :-p
[14:42] <seb128> mandel, let me know if you can reproduce or if you need more info from my device
[14:44] <mandel> seb128, yes, using krillin or mako?
[14:44] <seb128> mandel, neither, that's a n7
[14:44] <mandel> kenvandine, yes, is like.. 1000 emails, new team, silo not landed.. and shit broken hehe
[14:44] <kenvandine> the usual :)
[14:44] <mandel> seb128, agh, the one  I don't have, but it should not matter
[14:45] <seb128> mandel, yeah, it shouldn't but in case in does I can provide info
[14:45] <mandel> seb128, thx
[14:45] <seb128> I plan to test on an arale as well
[14:45] <seb128> but need to reinstall that first
[15:42] <jgdx> abeato, will you let me know when ResetContexts land?
[15:42] <abeato> jgdx, sure, currently it is in silo 16
[15:42] <jgdx> abeato, nice. Thanks
[15:42] <abeato> np, great that you have already implemented it :)
[15:43] <jgdx> abeato, System Settings is bleeding edge :d
[15:43] <abeato> :D
[17:10] <peat-psuwit> jhodapp: Any progress for https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1452386 ?
[17:19] <jgdx> mpt, hey, did you get to install the silo? If not, let me know.
[18:09] <jhodapp> peat-psuwit, yeah just waiting on a co-worker of mine to merge it
[18:10] <jhodapp> peat-psuwit, already added your patch to my branch, just needs to make it into the archive now
[18:32] <taiebot> nik90: i think ubuntu-device-flash touch --channel=ubuntu-touch/devel/here to get vivid devel with here i did ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed/here to get Agps on willy
[18:33] <nik90> taiebot: ah the /here extension...will try it out.. thnx a lot mate
[18:33] <taiebot> nik90: you are wellcome. Have you got Nexus 4?
[18:34] <nik90> taiebot: yeah I got a Nexus 4 and BQ..
[18:34] <taiebot> nik90: i am not sure my n4 gps is actually working
[18:34] <nik90> taiebot: hmmm...I remember few months back where AGPS worked really well on N4 since I used that to implement clock app location detection.
[18:35] <nik90> I will try flashing and let you know if it works on my end
[18:36] <taiebot> nik90: i get a fix with Agps on here but not anymore on osmtouch
[18:36] <nik90> taiebot: did you check the osmtouch logs? It hasn't been updated in a while and could have broken
[18:41] <taiebot> nik90: when i do sudo dmesg | grep GPS as per https://lists.launchpad.net/ubuntu-phone/msg12532.html i get nothing
[18:42] <nik90> oh nice email thread..bookmarking for future reference..
[18:42] <nik90> my phone is flashing, I will test once that is done
[18:47] <dobey> taiebot: btw, for the sim toolkit app porting, first thing you should probably do is make sure the APIs it needs to use/access are available and accessible on Ubuntu in your app's confined context
[18:49] <taiebot> dobey: you should not put your hopes very high. Coding is not my thing. I do not think i will be able to do it without some help.
[18:50] <dobey> taiebot: well, i don't have high hopes. i don't need a sim toolkit app. :)
[18:50] <taiebot> :P
[18:57] <taiebot> dobey: looking at the Jolla bug report i do think it will have to be worked on on UT https://together.jolla.com/question/1235/sim-toolkit/
[19:07] <nik90> taiebot: I am not getting a location fix on my N4. I tried the sensors app despite now having the HERE support
[19:08] <taiebot> nik90: i do but it is not very precise
[19:10] <nik90> hmm
[19:24] <brunch875> damn, I just realized python omnicompletion works flawlessly on vim
[19:25] <brunch875> but it actually doesn't because vim is compiled with python2 and I'm coding using python3
[19:29] <brunch875> I read that for 15.10 or 16.04 ubuntu will use python3 for default, which will mean vim will be probably also compiled as such
[19:30] <brunch875> know if it's going to be the same for the phone?
[19:30] <brunch875> Convergence is hitting around then... right?
[19:34] <dobey_> brunch875: ubuntu already uses python3 by default, and has for a long time now
[19:34] <dobey_> brunch875: the goal for 16.04 is to get python2 off the default ISO install
[19:35] <brunch875> so typing python should launch python3, right?
[19:35] <dobey_> brunch875: the phone image does not have python2 on it
[19:35] <dobey_> no, typing python will never launch python3
[19:35] <brunch875> not even after they rid python2?
[19:35] <dobey> you will always need to run python3 to run python3
[19:35] <dobey> correct
[19:35] <brunch875> astonishing!
[19:35] <dobey> /usr/bin/python should never be python3
[19:36] <brunch875> you're the fountain of knowledge
[19:36] <brunch875> but then I wonder why they didn't choose to compile vim with python3 instead of python2 on the repos
[19:36] <brunch875> and as always, I'm off for dinner! Read you in a sec!
[19:39] <dobey> i don't know. perhaps the version of vim in the repo is not ported to python3. or the scripts it needs to run are all still python2
[20:33] <brunch875> that's probably it. I tried compiling vim from source but it fails
[20:33] <brunch875> I feel lazy to walk through the errors
[20:34] <brunch875> dobey: why is it that /usr/bin/python should never be python3?
[20:34] <brunch875> What's it going to be after ubuntu gets rid of py2?
[20:41] <dobey> brunch875: ubuntu isn't getting rid of py2
[20:41] <dobey> brunch875: it just won't be part of the default install
[20:41] <dobey> brunch875: everything in the archive doesn't work on py3. if /usr/bin/python was py3, anything that needed python2 would be broken
[20:42] <dobey> not on the ISO != not in the archive
[20:42] <dobey> there are plenty things in the archive, that aren't in the ISO
[20:42] <brunch875> yeah by getting rid of it I meant that
[20:44] <brunch875> you must excuse me as I'm still highly confused :D
[20:44] <brunch875> at least not certain of something wrong
[20:47] <dobey> brunch875: python2 and python3 are not compatible
[20:47] <brunch875> yeah, and a big chunk of the system uses py2
[20:47] <dobey> no, a small chunk of a default ubuntu install does
[20:48] <dobey> a *very* small chunk
[20:48] <brunch875> really?
[20:48] <dobey> yes
[20:48] <dobey> like, only a few packages on the default install
[20:49] <brunch875> I'll research a bit after I grab some sleep
[20:50] <brunch875> otherwise I'll be bugging you tomorrow if I remember ;)
[20:50] <brunch875> ciao
[20:50] <dobey> sure
[20:58] <studio_> hi
[21:00] <popey> hello
[21:00] <studio_> will there be, in the near future, an Ubuntu Phone, which will not be depending on Android?
[21:01] <popey> no
[21:01] <studio_> why?
[21:01] <popey> because we need the drivers to access the hardware
[21:01] <popey> that requires the android kernel
[21:02] <studio_> what about broadcom, if mtk do not like?
[21:02] <popey> We are dependent on the SoC in devices that partners want to ship
[21:03] <popey> if a partner uses a different SoC vendors, great, but we still need the drivers
[21:03] <popey> and they are predominantly non-free binary blobs in an android kernel
[21:05] <dobey> if a vendor builds a 100% open phone that doesn't require binary blobs for a specific kernel version, then we can ship a phone that doesn't have android, maybe
[21:05] <dobey> until there is a totally open phone that ubuntu can run on and use all the hardware, we'll probably need the android lxc and drivers to use the hardware
[21:06] <studio_> i understood non free driver (closed source), but if mtk or other do not like to build drivers for a new real linux-kernel, why not a new "manufacturer"?
[21:06] <popey> 22:02 < popey> We are dependent on the SoC in devices that partners want to ship
[21:07] <popey> we don't choose the SoC
[21:07] <studio_> So, what are the "partners"?
[21:07] <popey> bq, meizu
[21:07] <studio_> only mtk?
[21:07] <dobey> studio_: this has been answered to you many times previously
[21:07] <dobey> please stop asking the same tired old repetitive questions over and over when you've been given the answers already
[21:07] <popey> bq and meizu chose mtk SoC, we didn't
[21:08] <dobey> not all the devices that ubuntu has been ported to use the mtk kit, afaik
[21:08] <dobey> ie, the nexus devices for example
[21:09] <popey> the first devices weren't either.
[21:09] <dobey> the first was galaxy nexus?
[21:09] <popey> Nokia N9
[21:09] <dobey> oh
[21:09] <studio_> dobey, right, but they are not "official" ...
[21:09] <popey> and Asus Transformer TF101
[21:10] <popey> nothing was official
[21:10] <popey> we didn't release N9 or TF101 images
[21:10] <dobey> studio_: if you want a device that doesn't require proprietary drivers, then go win the lottery or something and start a company to do exactly that. or convince google to push their partners to produce open source drivers for their hardware
[21:11] <popey> http://neo900.org/ :)
[21:11] <studio_> dobey, you do net get the point. the rpi is also "proprietary"
[21:12] <dobey> it's not something that can be changed by whining in this channel
[21:12] <dobey> studio_: you don't get the point. stop asking the same crap over and over
[21:12] <popey> studio_: we get it.
[21:17] <studio_> popey, i don't know how to tell, to step someone on their feets. i asked, because i am using different soc devices with linux on it. for exp. arm, sh4 and mips. therefore i do not understand, taht it is a so big problem to get drivers for the linux kernel :(
[21:19] <dobey> studio_: buy hardware and send it to hardcore kernel engineers who can reverse engineer it then
[21:21] <studio_> dobey, i do not understand, when canocial is talking about "partners". what to you understand about "partners"?
[21:21] <popey> 22:07 < popey> bq, meizu
[21:21] <popey> i just answered that
[21:21] <dobey> ffs
[21:22] <studio_> telekom, telefonica, vodaphone, etc. partners for what?
[21:23] <popey> bq and meizu are our hardware partners
[21:24] <dobey> http://www.canonical.com/partners
[21:27] <studio_> http://partners.ubuntu.com/
[21:27] <studio_> ?
[21:27] <dobey> yes that is another url that one might get to from the other site
[21:28] <studio_> as you and read ARM
[21:28] <dobey> ARM do not make all the hardware
[21:29] <dobey> and the kernel runs on the CPU without extra binary blobs already
[21:29] <popey> they don't make the majority of hardware, but license their designs to companies like mtk, qualcomm etc
[21:29] <dobey> the CPU isn't the problem
[21:29] <studio_> but they make the code, aren't teey?
[21:29] <studio_> they
[21:29] <dobey> no
[21:29] <studio_> no?
[21:29] <dobey> ARM doesn't make the binary blobs for Mediatek
[21:30] <dobey> Mediatek makes the stuff for Mediatek
[21:30] <dobey> the SoC chips have more than just the ARM CPU in them
[21:31] <studio_> again, MTK is the one and only manufacturer for ubuntu phones?
[21:31] <popey> no
[21:31] <studio_> :)
[21:31] <dobey> Mediatek, Qualcomm, Broadcom, Apple, etc… license the CPU design from ARM, and build it into their SoC
[21:32] <popey> mtk don't make the phone, they make the soc
[21:32] <dobey> Mediatek don't make phones
[21:32] <dobey> they make SoCs
[21:32] <popey> but you already know this....
[21:32] <dobey> if you want a phone to run ubuntu on that doesn't have a Mediatek SoC, buy a nexus4
[21:33] <dobey> and install the developer image on it
[21:33]  * genii decides to go MIPS64 anyhow
[21:33] <studio_> dobey, i'd like to have a phone, that is not depending from android, that's all.
[21:34] <dobey> studio_: then buy an iphone?
[21:34] <popey> okay well, thats not going to happen with ubuntu any time soon
[21:34] <popey> haha
[21:34] <dobey> or a windows phone
[21:34] <dobey> or win the lottery and build one yourself
[21:34] <popey> http://neo900.org/ or buy one of them
[21:35] <dobey> or yeah, one of those
[21:35] <studio_> dobey, would be nice to have debian on an " i-device" ...
[21:35] <genii> Hehe, FreeRunners
[21:35] <popey> I want a pony.
[21:35] <dobey> or buy an old pre3
[21:35] <dobey> or an old nokia
[21:35] <dobey> or a tizen/meego phone
[21:35] <popey> Nokia N82 is nice.
[21:36] <dobey> i have an N something
[21:36] <k1l> even arm dev boards get shipped with android and android drivers. so demanding a non-android thingy and for a small budget price,... that is winning in lottery
[21:36] <dobey> N86
[21:36] <dobey> really nice phone
[21:37] <k1l> i got a n4, nice too :)
[21:37] <k1l> but cracked my backside the second time now...
[21:37] <genii> k1l: TI used to provide both android and linux boot images and drivers for their OMAP lines.
[21:37] <dobey> i have one of those sitting here too
[21:37] <studio_> k1l, you are a german, you know coolstream receivers, or not?
[21:37] <dobey> and a nexu5
[21:38] <dobey> and a pre3
[21:38] <k1l> a n5 would suit me a little better. but its not enough to made the step to the n5.
[21:38] <dobey> and a samsung t89
[21:38] <dobey> these new phones are too damn big anyway
[21:40]  * k1l thought the same about the n4 comming from the moto milestone
[21:46] <studio_> popey, thank you for answering my question, but i have one last question for today. how much in "MB" is needed from that android stuff for, for exp., the bq e4.5?
[21:51] <dobey> k1l: the n4 is too big :)
[21:51] <dobey> < 100
[21:52] <dobey> probably < 10MB of android stuff on the phone
[21:52] <dobey> the whole phone image is only like 300 MB
[21:52] <k1l> i am quite tall and have large hands. so it fits well. but a friend got the opeplusone. that is a thing
[21:52] <k1l> *oneplusone
[21:53] <k1l> well, the "amount of android" is interesting to know. but its not important since we cant change it anyway.
[21:54] <dobey> well, i'm not an NBA center, but I'm not a horse jockey either. i'm plenty tall and have somewhat lengthy hands, but the n4 is still too big
[21:54] <studio_> dobey, if it is < 10MB would't it be making sense to make a new scatter.txt for the partitition?
[21:54] <dobey> studio_: we don't have a scatter.txt for anything, so no
[21:54] <dobey> studio_: if you want help with the mtk tools then ask mediatek and/or bq
[21:54] <popey> studio_: no idea
[21:56] <studio_> dobey, i thought sturmflut was working about to get more space on the e4.5?
[21:57] <dobey> i don't know what he is doing
[21:57] <dobey> but afaik, he doesn't work for canonical, bq, nor mediatek
[21:58] <dobey> and i don't know what you mean by "more space"
[21:59] <studio_> i know, he's spending his free time to figure out something, same as me ... ;)
[21:59] <dobey> no
[21:59] <dobey> not the same as you. he doesn't keep asking the same questions over and over, even though he's been given answers. he reads the answers and comprehends them :)
[22:02] <studio_> dobey, what do you think, when sturmflut made the new bq phone public? check the date ... i figured out by myself, without help from this chat ...
[22:02] <dobey> huh?
[22:03] <popey> multiple people have pinged us about the E5 HD.
[22:03] <studio_> when?
[22:03] <dobey> i'm pretty sure sturm is in the "ubuntu insiders" program
[22:03] <popey> studio_: why?
[22:04] <dobey> popey: he's trying to get first comment on reddit
[22:04] <studio_> popey, you check all the logs, when did i said many thanks for the bq e5 ... ?
[22:04] <popey> studio_: I don't know what on earth you're talking about
[22:05] <studio_> 13.05.2015
[22:05] <popey> you mentioned the E5, others have mentioned it. What about it?
[22:05] <dobey> popey: he's talking about the fact that he was saying random things about trying to run the e4.5 ubuntu images on an e5
[22:05] <popey> ok
[22:05] <dobey> soomehow that means he knew there was going to be an e5 ubuntu edition
[22:05] <dobey> at least, that's what he's trying to claim
[22:06] <popey> well, that's a reasonable conclusion from the evidence given
[22:06] <dobey> well, "i want to run the e4.5 image on an e5" is a far stretch from "you guys are going to release an e5 with ubuntu on it"
[22:06] <dobey> but sure
[22:07] <dobey> logic can be a very elusive thing for some :)
[22:11]  * mcphail loves it when studio_ appears in his /lastlog. Came for the phone, stayed for the show.
[22:11] <studio_> dobey, i am not talking about to run "random things about trying to run the e4.5 ubuntu images on an e5" i am talking about "https://github.com/bq/aquaris-E5/tree/aquaris-E5-ubuntu-master" and "http://people.canonical.com/~jhm/barajas/recovery-vegetahd.img"
[22:12] <popey> studio_: we get it
[22:12] <studio_> nice :)
[22:16] <mcphail> It would be nice to see a bq phone with 4G (albeit I spend 80% of my week in places where 2G is a luxury)
[22:16] <popey> be nice if we had services that made use of all that bandwidth :)
[22:17] <mcphail> very true
[22:18] <mcphail> popey: but think how fast dekko would refresh...
[22:18] <studio_> mcphail, i don't understand that git, but maybe you can help, it was changed 9 days ago, but what branch? https://github.com/bq/aquaris-E5-4G
[22:18] <popey> would be nice for OTA updates and stuff
[22:19] <mcphail> studio_: I haven't looked at it
[22:19] <studio_> can you take a look on it?
[22:20] <mcphail> studio_: you could git clone it and see what changed. I'm not particularly interested
[22:21] <studio_> i don't understand, you wrote "It would be nice to see a bq phone with 4G"
[22:21] <studio_> hi Benno-007 :)
[22:23] <Benno-007> studio_: greetings
[22:24] <dobey> studio_: it doesn't mean he wants to read through kernel source for the phone
[22:25] <dobey> studio_: and i'm not sure the 4g version identifies the same as the non-4g version
[22:25] <studio_> Benno-007, what do you thing about tutanota? is it another "joke"?
[22:26] <mcphail> studio_: I've got all cores occupied cooking up a 14.10 chroot, I'm afraid. I'll leave the kernel sources to you :)
[22:28] <popey> mcphail: sdl fun?
[22:28] <studio_> mcphail, i no not need "lte" on my phone :) it is just for advertising ...
[22:29] <popey> I could see use of LTE/4G when it's converged device and the apps are large
[22:29] <popey> Or you want to remotely connect to apps running on remote servers
[22:30] <mcphail> popey: just arrived back home to my "real" machine. Might get some time to play with sdl tomorrow but kids are off school (so probably not)
[22:30] <popey> I can imagine using Excel remotely on another host being painful over 3G
[22:30] <popey> mcphail: ok :)
[22:30] <popey> Do you get Monday off?
[22:30] <mcphail> nope
[22:30] <popey> awww
[22:30]  * popey has booked Tuesday off for a long weekend.
[22:31] <popey> Got to take my daughter to a dancing competition on Monday so will probably take my laptop and work during that day
[22:31] <dobey> is there a citrix client for ubuntu on arm?
[22:31] <popey> who says it has to be arm :)
[22:31] <dobey> well, is anyone making x86 phones?
[22:31] <Benno-007> studio_: I'm away and don't know really this project from the UU link.
[22:31] <popey> Lenovo
[22:31] <popey> Asus
[22:31] <popey> (yes)
[22:31] <dobey> ...
[22:32] <mcphail> studio_: have you bought a phone yet?
[22:32] <dobey> well, ok, so 2 people will be able to run a citrix client on their phone :)
[22:32] <popey> :)
[22:34] <dobey> spreadsheet on a phone seems like a generally bad idea anyway though
[22:34] <dobey> i guess if you have a big screen and keyboard plugged in, it would be less painful though
[22:34] <studio_> popey, come on 3g is ok, you are not working via euro isdn ...
[22:34] <dobey> 3g is pretty bad
[22:34] <popey> well indeed, hence me mentioning convergence
[22:34] <mcphail> with an x86 phone you could stream steam...
[22:35] <dobey> 2.5g even is incredibly awful
[22:35] <popey> studio_: I agree, 3g is "ok". but my point was for future features, not today.
[22:36] <studio_> popey, what do you mean with "future", MTK devices based on android drivers?
[22:36] <studio_> ;)
[22:36] <k1l> using your phone longer than one year
[22:37] <dobey> studio_: stop trolling
[22:37] <popey> studio_: i mean exactly what I said
[22:37] <popey> 23:29 < popey> I could see use of LTE/4G when it's converged device and the apps are large
[22:37] <popey> [M#g223:29 < popey> Or you want to remotely connect to apps running on remote servers
[22:37] <studio_> dobey, come on, lets have some fun ...
[22:37] <popey> I can think of better ways to spend my evening
[22:37] <dobey> indeed
[22:38] <dobey> eh, you need lte if you want to watch netflix on your phone :)
[22:38] <popey> I have a cat sat on me, a glass of wine and politicians to shout at on telly :)
[22:38] <popey> ooh, good one
[22:38] <dobey> or youtube or such
[22:39] <k1l> on my contract i can see 1,4 seconds on LTE speed, iirc. must be a very short series then :)
[22:39] <popey> hah
[22:39] <dobey> and i'm about to install a new stereo in my truck, which i will at some point be able to miracast to and it can control my phone from the stereo screen
[22:39] <popey> yeah, that'll change though, no doubt
[22:39] <popey> same as 3g was terribly expensive initially
[22:39] <popey> right now the networks are gouging though
[22:39] <dobey> t-mobile us is awesome though :)
[22:40] <popey> heh, you're properly american with your "trucks" :D
[22:40] <dobey> i only have one
[22:40] <dobey> all my other vehicles are sports cars :)
[22:40] <popey> :)
[22:40] <dobey> (currently)
[22:40] <popey> All my other cars are lego
[22:40] <k1l> matchbox \o/
[22:40] <dobey> heh
[22:41] <studio_> dobey, btw. netflix on the phone or an tablet. are you going to import the player from ubuntu tv to the ubuntu touch devices or not?
[22:41] <dobey> there is no ubuntu tv
[22:41] <popey> wakka wakka wakka
[22:41] <dobey> i don't know why you keep saying "ubuntu tv"
[22:41] <studio_> but the player was nice ...
[22:41]  * mcphail lovingly pinches studio_'s cheeks
[22:41] <popey> haha
[22:42] <dobey> well maybe netflix will ship a client app for ubuntu phones. i don't know. the developer docs and store are there for them to upload it :)
[22:43] <dobey> if they want to
[22:44] <studio_> just for "understanding", ubuntu phone is not ubuntu, ubuntu next is not ubuntu phone, ubuntu tv and ubuntu touch is not continued?
[22:44] <popey> WAT
[22:44] <dobey> ubuntu is ubuntu
[22:44] <popey> I'm gonna say "no"
[22:44] <popey> do I win a prize?
[22:45] <studio_> :)
[22:45] <studio_> lol
[22:45] <dobey> ENOPARSE
[22:45] <studio_> sorry, what is ubuntu phone, what is ubuntu next, and what is ubuntu touch?
[22:46] <popey> Ok, lets go with "yes"
[22:46] <popey> Do i win now?
[22:46] <dobey> ubuntu-touch is a meta package
[22:46] <mcphail> Gah - I forgot how long it takes to install lots of .debs on a spinny hard disk. Was hoping this chroot was going to be ready by bedtime...
[22:46] <dobey> other than that ENOPARSE
[22:48] <k1l> studio_: ubuntu touch is the phone OS  that is in use currently. ubuntu next is the testing iso with mir and unity8 (and snappy packages in future) for developing and testing the new ubuntu that will include the desktop and the phone OS.
[22:50] <dobey> k1l: no it isn't. the phone os is ubuntu
[22:50] <k1l> arent we all ubuntu? :)
[22:51] <studio_> k1l, i nearly understood. i mistakenly installed some ubuntu touch package on my 14.04 and was shocked for exp. the browser, it was the same as on my phone. same was with system settings.
[22:51] <dobey> k1l: there is no "ubuntu touch" product. it is just ubuntu. "ubuntu-touch" is just the metapackage used for the seed for things on the phone image that come from the archive
[22:52] <popey> yeah, -touch was used quite a bit early on until we had a real product name for it
[22:53] <popey> still used in lots of places
[22:53] <k1l> dobey: yeah.
[22:53]  * popey looks at the channel name
[22:53] <popey> and it's fair for people to still use the term, we know what people mean when they talk about it
[22:53] <k1l> dobey: i tried to trimm it down to make it less confusing.
[22:54] <dobey> just imagine sigourney weaver saying "there is no touch. there is only ubuntuuuuuu"
[22:54] <mcphail> studio_: "ubuntu next" would mean my development chroot would have installed by now :(
[22:54] <popey> you need a delorean
[22:55] <dobey> i would have one, but they are still pretty expensive
[22:55] <mcphail> my friend was going to buy delorean's house last year
[22:57] <mcphail> anyway, all built. Night all
[22:58] <popey> o/
[22:59] <studio_> mcphail, i am normally using ubuntu studio and i was happy to see the new gui on 15.10. i was wondering, that the new xfce is not available on the phone, icons are big enough, waren't they?
[23:00] <dobey> because you didn't build a phone image that used xfce
[23:03] <studio_> dobey, is ubuntu studio 15.10 using xfce under mir?
[23:03] <dobey> ubuntu studio don't make phone images
[23:04] <popey> studio_: no
[23:04] <k1l> just big icons dont mean its usable as a phone screen
[23:04] <studio_> ok
[23:05] <k1l> just think about all the right-click and drag&drop stuff
[23:05] <studio_> so ubuntu studio 15.10 is still using x11?
[23:06] <dobey> studio_: #ubuntu-studio is probably the best place to ask about ubuntu studio
[23:07] <dobey> k1l: eh, android has plenty of things that are long-press or DnD, to use
[23:09] <k1l> dobey: yeah, but its different from that "regular desktop" stuff, imho
[23:09] <studio_> dobey, i just want to know if there is any separation from my preferred ubuntu distribution and ubuntu touch.
[23:09] <dobey> not really. just more annoying because i don't have a mouse
[23:10] <dobey> studio_: if your preferred ubuntu distribution is ubuntu studio, then yes, there are plenty of differences between it and ubuntu
[23:10] <popey> studio_: every desktop still uses x11
[23:12] <studio_> dobey, in the past since now it was not. i was able to install, on my desktop, all tools, drivers and kernels.
[23:12] <studio_> ahh, desktop
[23:13] <popey> \o/ bedlington
[23:13] <popey> nn all
[23:17] <dobey> w/e