[02:49] <shengchieh> hi, guys. I met a mir exception error when bootup on a arm device. so i try to rebuild mir with ./cross-sompile-chroot.sh but the built library can be lunched functional on arm target. Does any one has the same experience and know how to solve it?
[03:21] <shengchieh> hi, guys. I met a mir exception error when bootup on a arm device. so i try to rebuild mir with ./cross-sompile-chroot.sh but the built library can not be lunched functional on arm target. Does any one has the same experience and know how to solve it?
[03:24] <guest42345> shengchieh, try #ubuntu-mir
[03:25] <shengchieh> thanks, i'll ask it at mir channel
[07:05] <tsdgeos> ogra_: faenil did contact sil2100 already i didn't feel like doing it again
[07:13] <dholbach> good morning
[07:14] <justCarakas> good morning @dholbach
[07:15] <dholbach> hey justCarakas
[07:43] <ogra_> tsdgeos, awesome
[08:33] <faenil> tsdgeos: yeah sil2100 said he'd look into it asap
[08:34] <sil2100> Syncing the xorg packages? Yes, that's on my today's TODO list :)
[08:36] <Kniple> Hey Guys, I've noticed a problem, if you leave the settings screen open on for example Updates, lock your phone, open it again (with passcode) the "back" arrow doesnt work. I have to close the settings "app" to be able to return to the menu. Is this something anyone else has experienced? (Meizu MX4)
[08:38] <faenil> sil2100: awesome thanks :)
[08:39] <ogra_> Kniple, sounds like it would be worth to report on launchpad
[08:39] <Kniple> Yeah, i've been thinking about it.
[08:39] <Kniple> :D
[08:39] <Kniple> Need to test it out more though (currently aint got hte phone on me)
[08:40] <Kniple> I'll run a series of tests when I get home, and file a bug if it seems to be a problem.
[08:54] <JamesTait> Good morning all; happy Fresh Breath Day! 😃
[09:23] <bq-e5-noob> im looking for a bluetooth headset for my new bq-e5. do u have a recommendation? or does it work with any headset?
[09:27] <popey> bq-e5-noob: in theory any should work
[09:28] <bq-e5-noob> do u use one? if so, wich one?
[09:31] <popey> I do not.
[09:38] <bq-e5-noob> popey: ok
[10:22] <cimi> seb128, you coming to london for a sprint in few weeks?
[10:22] <seb128> cimi, yes
[10:22] <cimi> seb128, ok, my kbd can wait then
[10:22] <cimi> :)
[10:22] <seb128> sure
[10:22] <seb128> morphis is going to be there as well I think
[10:24] <oSoMoN> brendand, hey, I came across https://code.launchpad.net/~canonical-platform-qa/messaging-app/fix_send_button/+merge/267163 and I’m curious about that fix that landed, can you elaborate on this? (FTR we have the same kind of workaround in the browser’s autopilot emulators)
[10:26] <brendand> oSoMoN, i believe a patch was made to autopilot so that it ignores the component version in the name
[10:27] <brendand> oSoMoN, so it should no longer be necessary and will in fact break code that uses that workaround
[10:27] <brendand> oSoMoN, which is unfortunate
[10:28] <Elleo> brendand: are you getting errors like this in your ~/.cache/upstart/maliit-server.log when those system tests are failing? http://pastebin.ubuntu.com/12012820/
[10:28] <brendand> Elleo, oh - not sure - i'll check
[10:28] <Elleo> brendand: because that's what I'm seeing, which suggests an issue with the unity8 restart as maliit isn't able to connect to unity8 after the first restart
[10:28] <Elleo> well, after the second restart
[10:29] <Elleo> the first one seems to be fine, then after that it seldom connects again
[10:29] <brendand> Elleo, yeah i do - i can do another run and see if it corresponds precisely with the failure occuring
[10:29] <Elleo> brendand: yeah, that'd be good, it's looking pretty likely
[10:30] <brendand> Elleo, can it be fixed?
[10:30] <brendand> Elleo, i know restarting unity8 so much is slightly unusual but it *could* happen in normal usage i guess
[10:31] <Elleo> brendand: I'm not sure why it's happening yet :/ maliit seems to get restarted when unity8 is restarted, which should be enough to let it make a connection
[10:32] <Elleo> brendand: based on what I recall from the upstart scripts maliit shouldn't get started until unity8 reports itself accepting connections
[10:33] <Elleo> brendand: might need to find someone with a bit more unity8/upstart knowledge to poke this as well though, as it's not anything maliit specific, that's the standard error that the qt-ubuntu mir platform integration stuff spits out when it can't connect
[10:33] <brendand> oSoMoN, looks like you use it in close_tab
[10:34] <Elleo> brendand: although interestingly after the tests have finished the keyboard displays under normal usage
[10:34] <brendand> Elleo, afaict it seems to display in the test too
[10:35] <Elleo> brendand: interesting, it didn't display in the tests I just ran
[10:35] <Elleo> brendand: that error might be just from unity8 disappearing then, rather than from the attempt to restart
[10:35] <brendand> Elleo, i could be wrong about that, but i thought i remember the screenshots showing it...
[10:35] <oSoMoN> brendand, yes. Will you submit a patch for webbrowser-app, or do you want me to take care of it?
[10:38] <brendand> oSoMoN, i don't think we use close_tab, so could you?
[10:39] <oSoMoN> brendand, ok
[10:39] <oSoMoN> brendand, do you have a reference to the autopilot commit that fixed this behaviour?
[10:41] <Elleo> brendand: after restarting my phone the keyboard is now showing up in all the tests, so something else odd was happening previously :/
[10:42] <brendand> oSoMoN, i believe it's https://bugs.launchpad.net/autopilot/+bug/1337004
[10:49] <brendand> Elleo, i think i found a smoking gun right before the failure - WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled
[10:49] <brendand> Elleo, i didn't see the other error though
[10:50] <brendand> Elleo, mmm. actually that might be a red herring - i see it earlier in the log when it worked too...
[10:51] <sil2100> pitti: hey! Do you know when the new libboost1.58 migrates?
[10:52] <pitti> sil2100: presumably in half a year or so :-(
[10:52] <pitti> http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.58.html
[10:52] <pitti> it's entangled with a gazillion g++ transitions
[10:52] <sil2100> :<
[10:52] <ogra_> mpt, whats the difference between "alert" and "alarm" roles ?
[10:53] <ogra_> seems you are saying in https://wiki.ubuntu.com/Sound#primary-output that "alert" should always be the default role (if no other one is active)
[10:54]  * ogra_ doesnt like that gcc5 stuff ... i think we should just roll back to gcc 4.9 :P
[10:55] <mpt> ogra_, yes, but I was just writing what ted told me. <https://wiki.ubuntu.com/Sound?action=diff&rev2=137&rev1=136>
[10:56] <ogra_> mpt, ah ... we should have a "blame-ted" tag on the wiki ;)
[10:57] <ogra_> i dont mind what the default role is, but it is hard to understand the difference between alarm and alert without further explanation how they are different
[11:04] <sergiusens> ogra_: in your email you mention manta, is it just there or does it really work?
[11:05] <ogra_> sergiusens, no idea, it is there :)
[11:05]  * ogra_ hasnt booted a manta in 1.5 years or so
[11:08] <brendand> Elleo, this time i didn't see the error from the pastebin at all :/
[11:08] <Elleo> brendand: that error's normal
[11:08] <Elleo> brendand: I'm suspecting something more autopilot introspection related
[11:09] <Elleo> brendand: (the active subview error that is)
[11:17] <morphis> seb128: yeah I will be there
[11:19] <sergiusens> ogra_: right, I tried rc-proposed and see a screen blanking issue (I think manta had this issue before as well)
[11:20] <ogra_> sergiusens, yeah, i think davmor2 can tell you about it :)
[11:21] <sergiusens> davmor2: did you recap on manta at all or are you abiding to its neglection even for fun?
[11:23] <sergiusens> ogra_: fwiw, I powered krillin just now and I really prefer the form factor over arale; the only gotcha is the camera IMO
[11:24] <popey> shame it doesn't have more RAM
[11:24] <ogra_> well, my gotcha is the RAM as well :)
[11:24] <ogra_> ha
[11:24] <morphis> sergiusens: and in comparison with vega one on the camera side??
[11:25] <popey> it's almost impossible to share a photo because the phone runs out of RAM when you have app + gallery + content-hub open
[11:25] <ogra_> sergiusens, though it is funny to specifically hear you say that :)
[11:25]  * ogra_ remembers when we first met you had this gigantic samsung phablet as phone :) 
[11:25] <morphis> popey: never tried that yet
[11:26] <sergiusens> popey: I have that issue on arale too! It's frustrating not to share a photo of my beer drinking to get other people envious :-P
[11:26] <sergiusens> morphis: I don't have a vegeta
[11:26] <sergiusens> morphis: but I think that phone is also bigger
[11:26] <ogra_> welll, the lowmemorykiller on all our devices is completely unconfigured ...
[11:26] <ogra_> we just run with the defaults the android init.rc files apply on boot
[11:26] <popey> its a serious flaw
[11:27] <sergiusens> ogra_: fix it!
[11:27] <ogra_> and afaik all of the phones use the very same values, regardless of the amount of ram they have
[11:27] <ogra_> sergiusens, i  only started lookking into that last weekend :)
[11:27] <popey> so it's fixed?
[11:27] <sergiusens> ogra_: so one more weekend and it's fixed :-P
[11:27] <ogra_> oh, and the overcommit settings are totally bonkers too
[11:27] <ogra_> i'm still trying out different settings ;)
[11:28] <ogra_> once i find good values i'll popose a fix
[11:28] <morphis> sergiusens: yeah ... that seems to be the compromise
[11:29] <ogra_> the prob is also that lowmemoorykiller kind of applies android standards ...
[11:29] <morphis> really thinking if I should go and buy just the krillin
[11:29] <morphis> regardless of the not-so-good camera module
[11:29] <ogra_> (headless apps, apps that are just empty zygote processes etc ... all that stuff doesnt exist in our setup)
[11:44] <sergiusens> morphis: the other downside for krillin, for me at least, is the radio; we only get edge in the americas (except for brasil and uruguay I think)
[11:45] <morphis> ah
[11:45] <morphis> that should be the problem here in EU :)
[11:50] <davmor2> sergiusens: manta has a weird issue if you leave the screen on for a while it flashing like crazy
[11:54] <sergiusens> davmor2: thanks for confirming, we had this issue before and required fixing in mir, so I guess it's not going to happen soon
[11:54] <davmor2> sergiusens: I think the priorities are else where to be honest
[11:57] <sergiusens> davmor2: when I said 'soon' I was being ironic and really meant never ;-)
[11:58] <davmor2> sergiusens: see now I don't know if you are being ironic or not ;)
[12:09] <sergiusens> davmor2: :-)
[12:10] <sergiusens> davmor2: since I have your attention, what is the stable channel for krillin again?
[12:10] <davmor2> https://wiki.ubuntu.com/QATeam/ChannelsToFlash
[12:13] <sergiusens> davmor2: thanks!
[12:14] <davmor2> sergiusens: pleasure
[12:17] <jgdx> greyback, hi, could you take a look at displays api [1] and the display api [2]? [1] http://goo.gl/F3srUl [2] http://goo.gl/PnxGF4
[12:17]  * jgdx couldn't figure out how to use pad.lv to link to specific file
[12:24] <greyback> jgdx: yep, thanks!
[12:32] <jgdx> greyback, not sure what you feel about having to marshall between system settings and mir on resolutions.
[12:36] <Savvy> Hello guys
[12:36] <Savvy> As far as I understood, you don't use git to manage the repos?
[12:36] <ogra_> we use launchpad ...
[12:37] <ogra_> while that provides support for git and bzr, most bits are in bzr
[12:37] <Savvy> I see
[12:37] <Savvy> Is the ubuntu layer built on top of the android layer?
[12:38] <ogra_> no ... they are built separately and the android bits run in a container that ubuntu fires up durin the boot process
[12:39] <Savvy>  I see
[12:39] <Savvy> Last question :b
[12:39] <Savvy> Do I have full access to the hardware when using ubuntu touch?
[12:39] <ogra_> define full access
[12:40] <ogra_> screwdriver and soldering iron ?
[12:40] <ogra_> datasheets ?
[12:41] <jgdx> did you know that capacitors in a dc circuit have infinite resistance?
[12:42] <ogra_> (and if in SW, in which context, app access or tinkering on the cmdline/terminal ?)
[12:42] <ogra_> you need to be a bit more specific with that one :)
[12:42] <Savvy> With full access I mean if I can take phone calls with my WiFi adapter
[12:42] <Savvy> Or toast bread with my bluetooth one
[12:43] <ogra_> if the android driver supports it and if you write an app that can handle it, sure :)
[12:43] <Savvy> Without rescrictions as android non root imposes
[12:44] <Savvy> Exactly ogra
[12:44] <Savvy> No apps
[12:44] <ogra_> you have full sudo access, like on every other ubuntu install :)
[12:44] <Savvy> My QUESTION is
[12:44] <Savvy> Sorry caps, phone
[12:44] <ogra_> (which means there is no "non-root" scenario)
[12:45] <Savvy> Iif the android layer remained the basis for the distro ( I know this makes no sense tech speaking regarding distro meaning) and hence there would still be some restrictions but you already answered no
[12:46] <Savvy> And now you answered it all with no no-sudo scenarios, ok :b tyvm
[12:46] <ogra_> well, the whole set of drivers lives inside the container, you have full access to it and all ...
[12:46] <ogra_> but after all there are binary blob drivers in that android container, to which we dont have the source either
[12:47] <ogra_> (some at least)
[12:48] <ogra_> so you have full root access, can do anything you want outsiude and inside the container but on HW level only within the bounds of what you can do with the binaries
[12:49] <ogra_> (you will not be able to modify the graphics or modem drivers ... )
[12:50] <ogra_> (beyond the knobs they provide already indeed)
[13:25] <greyback> jgdx: hey, the Mir api gives read/notify access to all the Display related data I think you need.
[13:25] <greyback> I don't think we need to duplicate all that via dbus really
[13:25] <greyback> the only thing we need dbus for is to modify the display state
[13:26] <greyback> would you agree?
[13:27] <jgdx> greyback, how would system settings read a given setting on a display exactly?
[13:28] <jgdx> s/exactly/from mir
[13:30] <greyback> jgdx: qtubuntu is a wrapper around mirclient, allowing Qt to work with Mir. Right now it doesn't allow access to mirclient apis directly by apps. QtUbuntu would need modifying allow access to the mir display configuration for system settings
[13:31] <greyback> there is an api called "native interface" which qtubuntu could use to export access to mirclient data, and system settings would use this
[13:32] <jgdx> greyback, I though that was hard/impossible to make secure…
[13:32] <jgdx> either way, if that's possible—great!
[13:33] <greyback> jgdx: this would be for read/notify access
[13:34] <greyback> we'd still need the dbus api to make changes
[13:34] <jgdx> greyback, yup. This means the dbus apply method needs to be expanded slightly.
[13:35] <jgdx> to include scale
[13:41] <greyback> jgdx: "scale" is something mir doesn't have
[13:42] <greyback> I need to see what we can do so
[13:43] <jgdx> greyback, that's why I originally left it out.
[13:43] <jgdx> it could be gsettings
[13:43] <greyback> Yeah
[13:44] <greyback> jgdx: ideally, we'd like to save the scale per physical monitor, no?
[13:44] <greyback> and selected resolution, orientation...
[13:44] <jgdx> greyback, that's what I read from the spec
[13:45] <greyback> jgdx: so that data needs to be stored somehow that unity8 can read it and apply immediately
[13:46] <greyback> jgdx: I'll need a little time to come up with a proposal
[13:46] <greyback> have thinking to do
[13:46] <jgdx> greyback, roger.
[13:48] <jgdx> greyback, want to mention that scaling is probably set on the seat's config, not system wide.
[13:49] <greyback> jgdx: akc
[13:49] <greyback> ack
[14:50] <kenvandine> mandel, have you had any luck figuring out what's up with the fix-network branch?
[17:08] <kenvandine> jgdx, can you fix the merge conflict in your hotspots branch?  https://ci-train.ubuntu.com/job/ubuntu-landing-046-1-build/45/console
[17:08] <jgdx> kenvandine, i fixed that
[17:09] <jgdx> IIRC
[17:09] <jgdx> kenvandine, are you doing a rebuild?
[17:09] <kenvandine> jgdx, yeah... just now
[17:09] <kenvandine> might be a new conflict
[17:10] <kenvandine> i just landed those autopilot fixes
[17:10] <jgdx> give me a minute
[17:10] <kenvandine> jgdx, with your two branches, i'm seeing intermittent keyboard failures
[17:10] <kenvandine> RuntimeError: Keyboard is not on screen
[17:10] <kenvandine> ubuntu_system_settings.tests.test_wifi.WifiEnabledTestCase.test_connect_to_hidden_network
[17:11] <kenvandine> jgdx, i got that twice
[17:11] <kenvandine> out of 5 runs
[17:11] <kenvandine> i don't think it has anything to do with our tests
[17:11] <jgdx> kenvandine, where?
[17:11] <kenvandine> on my krillin
[17:11] <jgdx> really.. ow
[17:11] <kenvandine> i just landed that silo
[17:12] <kenvandine> i hadn't seen the keyboard error lately
[17:12] <kenvandine> so surprising
[17:17] <jgdx> kenvandine, hm, that was supposed to merge cleanly. Anyway, pushed r1496
[17:17] <kenvandine> no worries
[17:17] <kenvandine> so you haven't seen that keyboard error?
[17:18] <kenvandine> jgdx, must be a race
[17:18] <kenvandine> maybe the keyboard isn't shown in time
[17:19] <jgdx> kenvandine, I haven't run those two branches at the same time.
[17:19] <kenvandine> i doubt it has anything to do with those branches
[17:19] <kenvandine> i think it's just that more tests pass now :)
[17:21] <jgdx> what a fun game
[17:29] <kenvandine> jgdx, it's impressive to see how low the system load is staying during tests now
[17:29] <kenvandine> we were really thrashing it before
[17:30] <jgdx> kenvandine, 90 buses would do that :p
[17:30] <kenvandine> indeed
[17:37] <jgdx> kenvandine, that osk hide feature, that'll work even though the osk has already been hidden, right?
[17:37] <kenvandine> yeah
[17:37] <kenvandine> i think so
[17:39] <kenvandine> jgdx, i've reproduced it by running just the one individual test too
[17:54] <jgdx> kenvandine, that's great.
[18:06] <kenvandine> jgdx, oh my... the storage tests are failing on my krillin because it takes 14 seconds to open the about->storage page
[18:07] <jgdx> kenvandine, doesn't take that long on my device.. 9 secs
[18:07] <jgdx> okay, long though
[18:07] <kenvandine> yeah, it's much faster on my arale
[18:07] <kenvandine> slow as hell still
[18:07] <kenvandine> but really slow on my krillin
[18:08] <jgdx> that's not acceptable no
[18:08] <jgdx> so that's the reason for the failures.. but why does dbus croak?
[18:08] <kenvandine> there's a dbus timeout before it loads :/
[18:08] <kenvandine> i think it's a 10 second timeout
[18:08] <jgdx> ugh.. is what's causing the slowness a dbus sync call?
[18:08] <kenvandine> yeah
[18:09] <kenvandine> i bet that's why we've been seeing some of those failures in about the other day
[18:09] <jgdx> i'd put money on that too
[18:09] <kenvandine> i'm going to file a bug about the slowness
[18:09] <jgdx> thanks
[18:10] <kenvandine> we need to fix that regardless
[18:10] <kenvandine> but probably not trivial
[18:11] <jgdx> maybe it's a regression
[18:11] <kenvandine> i just counted 9 seconds on my mako
[18:11] <kenvandine> maybe
[18:12] <kenvandine> wow, the number of deprecation warnings being logged is crazy
[18:14] <kenvandine> jgdx, i think those deprecations is the problem
[18:14] <kenvandine> 856 of those logged just loading the storage page
[18:15] <kenvandine> and it seemed to wait until it finished logging all those before showing the page
[18:15] <kenvandine> i counted 6 seconds while it was spewing the log
[18:15]  * jgdx chokes on a blueberry
[18:17] <jgdx> not seeing that on desktop using vivid+overlay
[18:25] <kenvandine> jgdx, bingo
[18:25] <jgdx> what'd i win!
[18:25] <jgdx> ?
[18:25] <kenvandine> i updated the storage related stuff to import 1.3 and fixed the deprecations
[18:25] <kenvandine> now takes 7 seconds to load on my krillin
[18:25] <kenvandine> that's down 7 seconds!
[18:25] <kenvandine> this sucks!
[18:26] <jgdx> nice! :) Thankfully our tests elegantly caught that regression :p
[18:26] <kenvandine> we have deprecations all over the place :/
[18:26] <jgdx> what import is that?
[18:35] <kenvandine> Ubuntu.Components and Ubuntu.Components.ListItems
[18:35] <kenvandine> bumped to 1.3
[18:35] <kenvandine> and fixed the UbuntuShape usage
[18:37] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/1_3_deprecations/+merge/267241
[18:37] <kenvandine> jgdx, ^^ that fixes enough to make the tests pass reliably
[18:38] <kenvandine> but we need to do that throughout settings :/
[18:38] <jgdx> kenvandine, ack
[19:18] <kenvandine> jgdx, ok, i have a branch that should update everythign to 1.3 :)
[19:18] <kenvandine> lets hope it works
[19:19] <jgdx> kenvandine, sweet!
[19:19] <kenvandine> at least the about panel works completely and tests pass with it
[19:19] <kenvandine> need to get a build to confirm the rest
[19:20] <jgdx> I just made an autopilot test that goes to hotspots, tries to enable, get prompted that wifi is off, accepts prompt (thus enabling wifi) and asserts that both wifi and hotspot is enabled
[19:20] <jgdx> then made the ui do that
[19:20] <kenvandine> tests driven development!
[19:20] <jgdx> word(s)!
[19:21] <jgdx> kenvandine, 86 imports of 0.1 :S
[19:21] <kenvandine> and some 1.0, 1.1 and 1.2
[19:21] <kenvandine> i updated them all to 1.3
[19:22] <kenvandine> in that 1_3_deprecations branch
[19:22] <kenvandine> and fixed the UbuntuShape deprecations
[19:22] <kenvandine> not sure if there are more
[19:22] <jgdx> need another +1?
[19:22] <kenvandine> we'll see
[19:22] <kenvandine> not yet..
[19:49] <jgdx> kenvandine, I want to push those design changes to my hotspots branch to get debs.
[19:49] <kenvandine> hmm
[19:49] <kenvandine> i'd rather keep that separate
[19:49] <jgdx> but that means that silo 46 is going to become real unstable for a while
[19:50] <jgdx> why?
[19:50] <kenvandine> did you see the chatter in the other channel?
[19:50] <jgdx> nop
[19:50] <kenvandine> pmcgowan suggested we try to land it next week then fix the bugs the week after
[19:50] <jgdx> right
[19:50] <kenvandine> so push it to a new branch that prereqs the old branch
[19:50] <jgdx> oay
[19:50] <kenvandine> so we can land the old UI if needed
[19:50] <jgdx> okay
[19:51] <pmcgowan> kenvandine, we still need to freeze strings
[19:51] <pmcgowan> so UI changes cant muck with those
[19:51] <kenvandine> yeah
[19:52] <kenvandine> i'm not sure we'll be ready to land the redesign in time though
[19:52] <kenvandine> so i don't want to risk that
[19:52] <kenvandine> i'd rather land the existing design for ota6
[19:52] <kenvandine> then the redesign for ota7
[19:52] <kenvandine> or at least have that option
[19:52] <jgdx> I think that's bad.
[19:52] <kenvandine> if the redesign is in good shape like monday
[19:52] <kenvandine> then reconsider
[19:53] <kenvandine> jgdx, i just want to have that option
[19:53] <jgdx> kenvandine, moving the ui is super confusing, don't you think? And two releases are more than one
[19:53] <kenvandine> true
[19:54] <kenvandine> but do we really want to delay landing the feature on that?
[19:54] <kenvandine> jgdx, the redesign isn't really huge
[19:54] <kenvandine> so maybe it'll be ready in time for the freeze :)
[19:54] <jgdx> it's about fixing the other issues as well, right?
[19:54] <kenvandine> yeah
[19:54] <kenvandine> but those aren't really UI issues
[19:55] <kenvandine> if you create a separate MR for it, we can consider both as landing candidates
[19:55] <kenvandine> hopefully shooting for the redesign
[19:55] <jgdx> Sure thing
[19:55] <kenvandine> no extra work this way :)
[19:56] <jgdx> All three indicator bugs are affecting ui :p
[19:56] <kenvandine> but we don't need to change our UI to fix the bugs :p
[19:56] <kenvandine> afaik
[19:57] <jgdx> right! Eeh what bugs? :p
[20:23] <muka> is tethering available yet? 'adb shell android-gadget-service enable rndis'  is not working. I'm running debian thought.
[20:24] <muka> I wrote small script that works but conn. is slow.
[22:52] <Telumehtar> I have just ordered a Meizu MX4 Ubuntu Edition. Anyone here have one?
[22:52] <popey> \o/
[22:52] <popey> yes
[22:52] <Telumehtar> Are you enjoying it?
[22:54] <popey> of course :)
[22:55] <Telumehtar> I just have to wait two weeks for it to arrive, apparently. Assuming it really trashes that long.
[22:55] <Telumehtar> takes. Apologies I am typing on a Nexus 6
[22:57] <Telumehtar> Is there a site with changelog for the OTA updates?
[23:07] <k1l_> https://wiki.ubuntu.com/Touch/ReleaseNotes/OTA-5
[23:07] <k1l_> Telumehtar: ^
[23:12] <Telumehtar> Many thanks k1l_. Exploring the wiki now