[00:24] <xenchrarr> When I try to install ubuntu-touch on my meizu mx4 now, I get the error "can't boot recovery image" - how can I fix this?
[00:29] <aceman0455>  Hey everyone. im wondered if anyone has a download link for touch flashable files
[05:54] <pandatrone> good mornin
[05:54] <pandatrone> g
[06:09] <InnerCode> Hey guys, I've installed the SDK as stated on developer.ubuntu.com and effected by this bug. https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1477580 Does someone knows how to fix it? My phone and desktop are up to date.
[08:09] <dholbach> good morning
[08:46] <InnerCode> Hey guys, Goodmorning. I've already asked this question but I disconnect by mistake. So, again: I've installed the SDK as stated on developer.ubuntu.com and effected by this bug. https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1477580 Does someone knows how to fix it?
[08:46] <ubot5`> Ubuntu bug 1477580 in apparmor-easyprof-ubuntu (Ubuntu) "[HTML5] AppaArmor denials to used the system installed UI SDK files, when webapp container used as a launcher" [High,Fix released]
[09:20] <tvoss> mardy, o/
[09:20] <tvoss> mardy, for testing https://code.launchpad.net/~mardy/location-service/last-known-position/+merge/277358
[09:20] <mardy> tvoss: hi!
[09:22] <tvoss> mardy, I would propose to create a test setup that includes an Engine instance, a service::Implementation instance, creating  session and subsequently injecting a reference position into the engine
[09:22] <tvoss> mardy, let me hand you some links to bootstrap the testing setup
[09:22] <mardy> tvoss: thanks
[09:24] <tvoss> mardy, you might want to copy http://bazaar.launchpad.net/~phablet-team/location-service/15.04/view/head:/tests/acceptance_tests.cpp#L576
[09:24] <tvoss> the tests sets up a private testing bus instance, a service and a client
[09:24] <tvoss> and alters the value of an Engine
[09:24]  * tvoss takes note to come up with a common fixture
[09:26] <mardy> tvoss: this link seems helpful indeed; do you want me to create a new cpp file for this test, or should I add it to an existing file?
[09:26] <tvoss> mardy, add to the existing file. We can have a followup MP to split out the file
[09:26] <tvoss> mardy, it's getting a little large :)
[09:27] <mardy> tvoss: OK :-)
[09:54] <om26er> jgdx, Hi!
[09:55] <om26er> jgdx, can you tell what mechanism we use to turn on/off data connection from system settings ? Is there a command line way to do that ?
[10:03] <JamesTait> Good morning all; happy Monday, and happy Button Day! 😃
[11:00] <shawnwang> cd :q
[11:21] <tvoss> mardy, did you have a chance to give https://requests.ci-train.ubuntu.com/#/ticket/651 a spin?
[11:57] <mardy> tvoss: not yet, sorry
[11:58] <tvoss> mardy, no worries, I gave it a spin
[12:12] <jgdx> om26er, hey, yes. /usr/share/ofono/scripts/disable-gprs and /usr/share/ofono/scripts/enable-gprs
[12:12] <jgdx> om26er, we toggle Powered on the ConnMan interface
[12:13] <om26er> jgdx, is the ofono script doing exactly the same thing as the UI ?
[12:13] <jgdx> om26er, yes
[12:13] <om26er> jgdx, great, thanks
[13:03] <mardy> tvoss: I've just updated https://code.launchpad.net/~mardy/location-service/last-known-position/+merge/277358
[13:04] <mardy> tvoss: there's an apparently unrelated change in time_based_update_policy.cpp, but it's quite important
[13:04] <tvoss> mardy, the fix for the uninitialized value?
[13:05] <mardy> tvoss: no, a fix on the accuracy check
[13:05] <mardy> tvoss: the previous code was checking the accuracy only if it was set on both the old and the new positions; but I think we should always update the position if there was no accuracy on the old position
[13:06] <tvoss> mardy, yup, certainly
[13:39] <mardy> tvoss: I want to change debian/source/format to be "3.0 (native)", so that I can easily build the package with pdebuild; can I sneak this change in my current MP, or do you prefer a separate one?
[13:39] <tvoss> mardy, separate one, please
[13:39] <mardy> tvoss: OK
[13:45] <dobey> brendand: hey. sorry, i was on vacation last week. shouldn't there be a helper in unity8 for doing the search and we should use that instead of doing all the work in the scope ap tests?
[13:46] <mardy> tvoss: here it is: https://code.launchpad.net/~mardy/location-service/source-format/+merge/277570
[13:46] <tvoss> mardy, great, thx
[13:48] <brendand> dobey, that would probably be better, yes. i'm not sure what the motivation behind adding the helper into unity-scope-click instead was
[13:48] <brendand> dobey, maybe it was a case of path of least resistance at the time
[13:49] <mardy> tvoss: as for the last-known-position one, I'm preparing a MP against 15.04 (the one you saw was for trunk, just because I happen to be on xenial); as soon as I confirm that it builds on vivid, I'll ping you
[13:50] <tvoss> mardy, ack, I would like to have a silo for testing asap to take it for a spin
[13:50] <dobey> brendand: i can only guess that elopio put it there because unity8 didn't have one yet
[13:52] <mardy> tvoss: I can foresee a problem, though... on the first start, the last known position will be (0, 0); I should add a method is_valid() to the Position class, and don't emit the position changed signal if the cached position is invalid
[13:53] <tvoss> mardy, hmmm, fair point
[13:54] <mardy> tvoss: on a project of mine, I'm initializing the latitute to NaN, to mark a position as invalid; do you think this is fine, or do you have a better idea?
[13:54] <tvoss> mardy, NaN is tricky unfortunately. I would make it an Optional<Position>
[13:55] <tvoss> mardy, that allows for a very simple check, without relying on (potentially brittle) numeric semantics
[13:55] <dobey> brendand: also, you cannot dual-land unity-scope-click
[13:56] <mardy> tvoss: as you wish; for the record, I'm using this: https://gitlab.com/mardy/mappero/blob/master/lib/Mappero/types.h#L113
[13:56] <mardy> tvoss: the isValid() method on line 123 is indeed fishy :-)
[13:56] <tvoss> mardy,  ;)
[13:57] <tvoss> mardy, picky here as I have spent too many hours debugging NaN-induced behavior before ;)
[13:57] <mardy> tvoss: well, if we have this Optional template, then I won't look further :-)
[13:58] <tvoss> mardy, yup, in the code
[14:24] <mardy> tvoss: mmm... using optional there makes the code look weird in many places (mostly because we are inside an Update<>, and an Optional<> makes things pretty weird)
[14:25] <mardy> tvoss: what about checking if the update timestamp is the beginning of times?
[14:25] <tvoss> mardy, let me think about it
[14:25] <tvoss> mardy, why not make the entire update optional?
[14:26] <mardy> tvoss: I guess the real question is why didn't I think of that? :-)
[14:26] <tvoss> mardy, :) it's Monday, and looking at code for too long tends to block clear thinking :)
[14:28] <mardy> tvoss: thanks, this must be it ;-)
[14:29] <brendand> dobey, i just pushed the change, charles took care of the landing
[14:29] <mardy> tvoss: but is core::dbus able to handle this type?
[14:29] <tvoss> mardy, yup
[14:29] <mardy> ok
[14:30] <tvoss> mardy, at least that's my excuse on a Monday :)
[14:30] <mardy> :-)
[14:33] <dobey> brendand: ok, i'll yell at charles :)
[14:34] <brendand> dobey, you can yell at me too but i'll just ignore you if it's not relevant :)
[14:38] <pandatrone> hi all, do you have any idea if there is a way to turn auto focus off on meizu?
[15:21] <jgdx> kenvandine, hey, added some stuff to the indicator mock: https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/mock-wifi-menu-items/+merge/277566
[15:23] <kenvandine> jgdx, ok
[15:24] <jgdx> pete-woods, hey, the wifi panel in uss is missing a section, and it it's empty in the gtk.Menus export from the indicator.
[15:24] <pete-woods> jgdx: that sounds pretty weird
[15:25] <pete-woods> which section is missing?
[15:25] <jgdx> pete-woods, it does. It's there, but there's no label
[15:25] <pete-woods> :/
[15:25] <pete-woods> v. weird indeed
[15:27] <jgdx> pete-woods, i'll make a bug
[15:28] <pete-woods> jgdx: screenshits plz
[15:28] <pete-woods> *shots :$
[15:28] <jgdx> pete-woods, sure, but what of?
[15:29] <pete-woods> the uss screen
[15:29] <pete-woods> the indicator menu
[15:29] <pete-woods> for easy comparison
[15:29] <pete-woods> so I know what went missing
[15:29] <pete-woods> also, is this happening to everyone?
[15:29] <pete-woods> just happened this once to you?
[15:29] <pete-woods> etc
[15:29] <jgdx> pete-woods, the thing is, it's not supposed to show in the indicator
[15:31] <jgdx> pete-woods, and when I said empty, I meant that it's on /com/canonical/indicator/network/phone_wifi_settings but it has no label property
[15:32] <jgdx> pete-woods, check it gdbus call -e -d com.canonical.indicator.network -o /com/canonical/indicator/network/phone_wifi_settings -m org.gtk.Menus.Start [0]
[15:32] <jgdx> {':section': <(uint32 0, uint32 1)>}
[15:33] <jgdx> that's correct, but according to the design spec there should be a label property (now) “Available Wi-Fi networks”.
[15:33] <pete-woods> okay
[15:35] <pete-woods> in a hangout now
[15:35] <pete-woods> but will talk about this more after
[15:36] <jgdx> sure
[16:39] <asac> awe: i am not sure my simpin unlock works... where can i see the log/errors from the ofono thingy on my phone?
[16:40] <awe> syslog
[16:40] <awe> grep for "ofonod"
[16:40] <awe> which phone?
[16:42] <awe> Mirv, hey had a couple Qt questions for you re: https://bugs.launchpad.net/ubuntu-rtm/+source/sync-monitor/+bug/1480877
[16:42] <ubot5`> Ubuntu bug 1480877 in location-service (Ubuntu RTM) "Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices" [High,Triaged]
[16:51] <asac> awe: meizu
[16:51] <awe> rc-proposed?
[16:51] <asac> point is i am sure i know the pin
[16:51] <asac> and the failed attempts counter does not go down
[16:51] <asac> stays at 3
[16:52] <awe> hmmm
[16:52] <asac> awe: where would i see errors if somethig goes wrong during simpin unlock?
[16:52] <awe> syslog, as I mentioned above
[16:52] <asac> Nov 16 17:37:38 ubuntu-phablet ofonod[2960]: mtk_radio_state_changed, slot 0: state: SIM_LOCKED_OR_ABSENT md->ofono_online: 1
[16:53] <awe> is that all?
[16:53] <awe> ( that looks like an error )
[16:53] <asac> hmm. its odd
[16:53] <asac> i dismissed the ping dialog because i didnt want to hard lock it
[16:53] <asac> but now the SIM isnt detected anymore in the UI
[16:53]  * asac reboots
[16:54]  * asac gets the feel something is fishy with that SIM
[16:54] <awe> k
[16:54] <awe> did you hot plug it?
[16:54] <asac> nope
[16:54] <asac> dont do that
[16:54] <awe> good
[16:54] <asac> it was a sim that was in the BQ
[16:55] <awe> ok
[16:55] <asac> when i came back the BQ didnt detect any sim at all
[16:55] <asac> not even my prepaid onces
[16:55] <awe> wow...
[16:55] <asac> so i thought BQ is busted
[16:55] <asac> now i put my normal sim into meizu and its detected, but my simpin doesnt work
[16:55] <asac> now meize doesnt see my normal sim either :(
[16:55] <awe> what image are you running
[16:55] <awe> ?
[16:56] <awe> rc-proposed?  stable?
[16:56] <awe> ( don't tell me xenial )
[16:56] <asac> awe: dunno where that problem is... i am on image...
[16:56] <asac> 15.04 (r6)
[16:56] <asac> didnt upgrade though
[16:56] <asac> so Nov 16 17:54:16 ubuntu-phablet ofonod[2165]: mtk_radio_state_changed, slot 0: state: SIM_LOCKED_OR_ABSENT md->ofono_online: 1
[16:56] <asac> is what i get after reboot
[16:57] <awe> that just means the SIM is locked
[16:57] <awe> ( or absent )
[16:57] <asac> and meizu doenst ask for prompt anymnore
[16:57] <awe> you need to enter the PIN
[16:57] <asac> ok so i really hit the 3 attempts barrier
[16:57] <asac> still i am 100% sure my pin was correct
[16:57] <awe> do you have the PUK?
[16:57] <asac> can a sim reset its PIN somehow/
[16:57] <asac> or maybe the BQ SIM component chocked and sent some bogus data to it :()
[16:57] <asac> i have a PUK
[16:57] <awe> not by itself
[16:57] <asac> but dont know where :(
[16:57] <asac> it must be somewhere buried
[16:57] <awe> unless skynet just woke up on your SIM
[16:58] <asac> i have this sim for like 5 years or so
[16:58] <asac> hehe
[16:58] <asac> well, as i said, the BQ phone seems to have no working SIM slot anymore
[16:58] <asac> my sim was in there
[16:58] <asac> when that happened
[16:58] <awe> mine's about shot too
[16:58] <asac> might be that there was some static involved
[16:58] <asac> is it a common error that the SIM slot break on B
[16:58] <awe> the SIM doors are just about broken for me
[16:58] <asac> Q?
[16:58] <asac> ah... well, i can put stuff in
[16:59] <asac> but it jujst desnt detect anything
[16:59] <asac> non of my 3 sims
[16:59] <asac> maybe it fried all by now :)
[16:59] <asac> damn... i hate trying to find my puk
[16:59] <asac> how do i unlock if i have it?
[16:59] <awe> kinda doubtful that all three fo them broke
[16:59] <asac> seems i am not getting asked for a PUK at least
[16:59] <awe> really?
[16:59] <asac> no i dont get prompted
[16:59] <asac> it just spits out the line above
[16:59] <asac> 17:56 < asac> so Nov 16 17:54:16 ubuntu-phablet ofonod[2165]: mtk_radio_state_changed, slot 0: state: SIM_LOCKED_OR_ABSENT md->ofono_online: 1
[17:00] <asac> if i got to settings -> mobile
[17:00] <asac> i get told it doesnt know my sim
[17:00] <awe> well... I guess if the count wasn't going down, then it won't know to auto-prompt
[17:00] <asac> damn i am late and have to run out
[17:00] <awe> ok
[17:00] <asac> talk soon. nice to meet friends without phone. lets hope we are able to find each other :P
[17:00] <awe> maybe you should ping abeato in the morning ( he's same TZ as you )
[17:00] <asac> hehe
[17:00] <awe> good luck!
[17:00] <asac> thanks  thats good
[17:00] <asac> have to search for the PUK anyway i guess
[17:01] <awe> k
[17:01] <awe> you should be able to get it from your operator
[17:01] <asac> worst case i misuse some old android of my wife
[17:01] <asac> they throw it away and only give it to me
[17:01] <asac> when they hand out the sim
[17:01] <asac> if you loose it they give you a new sim unfortunately
[17:02] <asac> but its ok
[17:02] <awe> well... I'll check my MX4 later and verify that PIN unlocking is working
[17:02] <asac> just nnoying :)\
[17:02] <asac> that would be cool
[17:02] <asac> thanks
[17:02] <awe> we test these pretty thoroughly everytime we release a new ofono
[17:02] <asac> i am sure i can find the puk :P
[17:02] <abeato> asac, does the sim work on another phone?
[17:02] <asac> it worked on the BQ ... then it stopped working on BQ, but so did all other SIMs i had
[17:02] <asac> so the BQ is broken now for sure
[17:02] <asac> because i can still use the other sims in the meize
[17:02] <asac> just not my main one
[17:03] <asac> that was in the BQ phone when it borke
[17:03] <asac> :)
[17:03] <asac> thats all i know
[17:03] <asac> it asked me for sim 3 times on meizu and now its not asking at all
[17:03] <asac> i entered the pin i am using since 10 years :)
[17:03] <asac> so its unlikely wrong
[17:03] <asac> just didnt unlock
[17:03] <asac> ok have to run.  lets chat tomorrow
[17:04] <awe> k
[17:04] <awe> ttyl
[17:04] <greyback_> hey, I've an annoying little issue with my Bq - it seems to think I entered the PIN incorrectly, so is demanding a PUK code.
[17:05] <greyback_> thing is, I never put a SIM into that phone
[17:18] <OerHeks> greyback_, contact BQ perhaps? puk code is related to a sim, not phone AFAIK
[17:20] <greyback_> OerHeks: you're right. So I'm suspecting the phone software (ofono) is confused
[17:58] <asif> hi
[21:30] <enska> I'm trying to find out when the next OS upgrade might come out for Ubuntu touch?
[21:32] <stakewinner00> enska, 18 of november i think
[21:32] <stakewinner00> http://news.softpedia.com/news/ubuntu-touch-ota-8-update-to-launch-on-november-18-495521.shtml
[21:32] <enska> ahh, that soon. That would be rally nice.
[21:33] <enska> And is there some place to announce user comments and bugs?
[21:33] <enska> rally -> really
[21:35] <enska> stakewinner00: thanks for the info. Didn't stumble into that page yet.
[21:36] <stakewinner00> enska, for report bugs?
[21:37] <enska> aww, well, sometimes the phone apps just crash or misbehave..
[21:37] <stakewinner00> https://wiki.ubuntu.com/Avengers there are the bug lists
[21:37] <enska> thanks
[21:39] <stakewinner00> enska, all i know of ubuntu touch is from softpedia :P
[21:39] <enska> :)
[21:39] <enska> thats more what I seem to know. :)
[21:40] <enska> And I'm using this phone daily.
[21:40] <enska> Not very happy with it atm, though...
[21:42] <stakewinner00> enska, I only use the phone for call, use telegram, and listen music, i only care about battery lifetime. But yeah, there are some wrongs thinks, like music app.
[21:43] <enska> yep, background play would nice feature.
[21:44] <ahayzen> enska, we are working on it :-)
[21:45] <enska> good to know. :)
[21:48] <enska> Now
[21:48] <enska> wrong button
[21:49] <enska> thanks for replys, I will start going trough the buglists.
[22:00] <stakewinner00> one question, will ubuntu updates produce some type of "programed obsolescence", I mean, in 10 years, ubuntu update can be bigger than the free space of my phone? For example BQ 4.5 have 8GB of storage, in 10 years an update of ubuntu can be of 9GB for example?
[22:03] <dobey> stakewinner00: possible, but unlikely. we try to keep the core OS small, and phone images are built specific for devices, so aren't filled with drivers for every possible set of hardware
[22:04] <dobey> more likely the hardware will just be too slow and limited for modern software at that point, if it's 10 year old hardware
[22:04] <stakewinner00> dobey, that's good :) I had an ipod touch, but the update was too big, and i don't like to waste money if the hardware still works.