[00:08] <utdeb> what needs to be done to bring the lastest version of ubuntu touch to the nexus 10
[00:12] <k1l> see the porting guide
[06:05] <Guest33114> test
[06:05] <nhaines> Guest33114: the message didn't go through.  Try again?
[06:54] <Guest33114> nhaines, :D
[07:01] <nhaines> Guest33114: that worked once on a LUG mailing list.  The guy even replied and said he hadn't gotten any error messages and three people jumped in to say "wait a minute!"
[07:01] <nhaines> I'm really proud of that.  :D
[07:02] <svij> nhaines: troll :P
[07:02] <Guest33114> haha :))
[07:03] <Guest33114> woa unity dash now has an icon
[07:08] <Guest33114> unity8-dash (scopes) icon http://i.imgur.com/JlyL5tn.png
[07:09] <Guest33114> it's the one between the sdk and "?" icons
[07:09] <Guest33114> the orange one with the ubuntu logo
[07:13] <amazoniantoad> Is the Aquaris E5 compatible for AT&T?
[07:52] <mokmeister> amazoniantoad: spec on E5 states support for 2G quad band (850/900/1800/1900) and dual band 3G(900/2100) so I would imagine it at least works on 2G.
[07:53] <zzarr> good morning
[08:21] <robin-hero> Hey, just reported two bugs for Unity8: Could you take a look at it? Thanks.https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1519235 and https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1519234
[08:21] <dholbach> good morning
[09:06] <hasselmm> morphis: regarding bluez5, which channel to flash? ubuntu-touch/rc-proposed/ubuntu-developer or ubuntu-touch/rc-proposed/bq-aquaris.en ?
[09:07] <morphis> hasselmm: as long its rc-propsoed, you're fine :)
[09:07] <hasselmm> morphis: what's the difference between both?
[09:07] <morphis> afaik the content of the custom part, like which apps are preinstalled etc.
[09:08] <hasselmm> ok, so i just need to figure out how to do a backup...
[09:08] <hasselmm> (or how to do an OTA update to proposed)
[09:13] <pixel_> hasselmm, you can change channels without flashing
[09:15] <pixel_> hasselmm, sudo system-image-cli --switch ubuntu-touch/rc-proposed/bq-aquaris.en
[09:15] <pixel_> i think you can add -vv for verbose
[09:15] <pixel_> system-image-cli --help
[09:22] <J0SH1X> Hey guys what is the status of whatsapp for utouch in june there was a announcement from connical this is the last reason why i dont flsah my nexus
[09:28] <J0SH1X> so noone has some infos bout this ?
[10:08] <JamesTait> Good morning all; happy Tuesday and happy Celebrate Your Unique Talent Day! 😃
[10:20] <slvn_> Hello ! I am looking for someone who could test a few .click package app on his device (I don't have a device anymore up-to-date..)
[10:20] <robin-hero> slvn_: Hey, I'm here :)
[10:21] <slvn_> robin-hero,  ok ! thanks !
[10:23] <victor_bq> Hi all!
[10:24] <sturmflut> Good morning oo/
[10:24] <sturmflut> Does anybody know about Telepathy on the phone?
[10:24] <victor_bq> does anyone have issues with Wi-Fi after OTA8?
[10:26] <mcphail> victor_bq: what issues in particular? I have ongoing issues, but not OTA8 specific
[10:28] <mardy> tvoss: hi! is https://code.launchpad.net/~thomas-voss/trust-store/fix-1504022/+merge/278418 essentially the same as the one which was for trunk, or are there changes?
[10:29] <tvoss> mardy, it's the same, sorry for the noise, only different targetbranch
[10:29] <mardy> tvoss: excellent, approving
[10:48] <hasselmm> morphis, pixel_: sorry, distracted by work (who invented that stupid thing?)
[10:49] <lotuspsychje> mcphail: any progress on your issue?
[10:50] <Henry__> hi
[10:51] <mcphail> lotuspsychje: which one? ;)
[10:52] <lotuspsychje> mcphail: battery drain
[10:52] <hasselmm> hmm.... would be good to see a progress indicator while running system-image-cli
[10:52] <hasselmm> thought sudo failed :D
[10:52] <lotuspsychje> mcphail: didnt notice issues here on my bq 4.5 yet
[10:53] <mcphail> lotuspsychje: have had a couple of further episodes of battery drain and some unity8 weirdness. Don't know if they are linked. Spurious input events
[10:53] <lotuspsychje> mcphail: didnt set to defaults yet i presume?
[10:53] <hasselmm> ok, it reboots....
[10:54] <Henry__> quick one: is there any kind of support email for ubuntu touch on BQ E4.5? do want to create account in bugzilla :-(
[10:54] <mcphail> lotuspsychje: no. Still on call until end of week. Might try reflash at weekend but have plans to explore some bottles of malt :)
[10:54] <lotuspsychje> Henry__: best to get bugs resolved is via official bug launchpad
[10:55] <lotuspsychje> mcphail: ok keep us updated :p
[10:56] <Henry__> lotuspsychje: thanks, ok
[10:56] <lotuspsychje> Henry__: check the link bug page on our topic
[10:56] <lotuspsychje> Henry__: or share your issue here in chat?
[10:57] <Henry__> lotuspsychje: is quite simple, after 77 hours of full recharge my battery indicator shows 81% and did not change for last 24h
[10:57] <lotuspsychje> mcphail: ^
[10:57] <lotuspsychje> related to yours?
[10:58] <lotuspsychje> Henry__: OTA8 also?
[10:58] <mcphail> lotuspsychje: don't think so. My battery is charging fine. Just dropping quickly at times for unknown reason
[10:58] <lotuspsychje> right
[10:59] <Henry__> lotuspsychje: yup, but is happening since I have the phone with r21 and updating. And quick drops in battery change I see in graph also
[10:59] <pixel_> hasselmm, :)) i have no idea
[11:00] <lotuspsychje> Henry__: did you go to defaults once?
[11:00] <mcphail> Henry__: have you been getting episodes where your phone seems to be receiving touches, even though you aren't pressing anything?
[11:01] <Henry__> lotuspsychje: had made several reimaging already since that r21, mostly because r25 was completely unstable, so I went from r24 to r26 and now on OTA-8
[11:02] <lotuspsychje> Henry__: could you try an ota8 reset to defaults, maybe were lucky?
[11:02] <Henry__> mcphail: this seems to be happening when I receive SMS - the screen "blinks" several times after and system seems "confused" when I try to swipe down the notification from up
[11:03] <Henry__> lotuspsychje: the "flat" battery charge in graph with obviously incorrect %  I see since the beginning, regardless if I had full re-image or full reset
[11:04] <lotuspsychje> ouch
[11:04] <lotuspsychje> doenst sound good then
[11:04] <lotuspsychje> Henry__: file a bug mate, from topic link
[11:04] <lotuspsychje> its important they know about
[11:05] <Henry__> my bq e.45 last about 110h since full charge, it is just not easy to predict when it discharge and switches off when I can't see the real battery %
[11:05] <Henry__> ok, will fill the bug, have also screenshot of it
[11:05] <Henry__> thanks
[11:05] <lotuspsychje> great
[11:06] <mcphail> Henry__: I've had odd things happen after SMS as well, and battery drain seems higher afterwards until a reboot
[11:06] <mcphail> Henry__: isn't consistent, though
[11:07] <Henry__> mcphail: r25 on my phone was completely useless :-(, but other than this it is fine, I use it as dual-sim "phone", so not really a smart phone ;-)
[11:08] <Henry__> therefore my battery lasts rather long, have everything except wifi and gsm switched off
[11:09] <mcphail> Henry__: OTA7 was good for me, if I turned wifi off before leaving the house. Something is badly wrong with OTA8 on my phone, though
[11:18] <Henry__> lotuspsychje: is there, could you please have a quick look if I did not miss something important on the bug filling? https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1519309
[11:38] <lotuspsychje> Henry__: lookin good mate
[11:38] <lotuspsychje> Henry__: when the devs awake, try to paste bug here to ask if someone knows
[11:40] <Henry__> thanks, someone already asked me for additional info, so I am adding it right now
[11:40] <lotuspsychje> : )
[11:40] <lotuspsychje> mcphail: you might follow the bug also :p
[11:52] <Henry__> mcphail: disaster at my phone was r25 - was afraid to touch the screen to not get freeze or reboot, r24 was perfectly stable. fresh re-image from Bq of r25 made it even worse, 6/10 boots I did not manage to put PINs to my sim cards.
[11:53] <lotuspsychje> Henry__: i only had scope freezes on ota7
[11:53] <lotuspsychje> for the rest works like a charm here
[11:53] <Henry__> mpchail: 3 weeks ago I upgraded from r24 to r26 - was stable, r27 I made a week ago (or so) so far stable - or better say no "new" issues ;-)
[11:54] <morphis> rvr: see my last update on https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519007
[11:54] <Henry__> lotuspsychje: I am not using scopes ;-) Only default App scope and then running apps like phone, clock, contacts and messages - I am really using it "not-as-smartphone" ;-)
[11:55] <lotuspsychje> lol
[11:55] <lotuspsychje> well i pretty like some news scopes and nearby also handy
[11:56] <morphis> Saviq: you already filed bugs for those things you told me yesterday?
[11:56] <rvr> morphis: Reading it
[11:57] <rvr> morphis: Interesting
[11:57] <morphis> rvr: so we need to talk with Tiago about this once he turns up
[11:58] <rvr> morphis: Ack
[11:58] <morphis> rvr: do you follow up with him on this?
[11:58] <rvr> morphis: I'll ping him when he's available
[11:59] <morphis> rvr: thanks
[12:01] <Henry__> lotuspsychje: so, my bug is duplicate to https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471913 from July :-(
[12:01] <lotuspsychje> Henry__: but your device is bq
[12:02] <Henry__> not my decision :-(
[12:03] <Saviq> morphis, not yet, let me file the one I'm certain of
[12:03] <morphis> ok
[12:04] <lotuspsychje> Henry__: but it says, no longer affects unit8 and your on ota8
[12:04] <Henry__> aha
[12:04] <lotuspsychje> contradictional
[12:05] <Saviq> morphis, bug #1519325
[12:06] <Henry__> lotuspsychje: don't know really, I am not expert on it. Put a q there, if the guys think it is duplicate, then they must be right.
[12:08] <lotuspsychje> Henry__: ok well then copy paste your bug into the existing old bug
[12:08] <lotuspsychje> Henry__: and mention your on OTA8 and its not fixxed as the bug says it fixxed
[12:08] <mcphail> Henry__: I've asked for the removal of "MX4" from the title of the other bug
[12:12] <morphis> Saviq: thanks
[12:13] <Henry__> mpchail: suddenly my chrome decided to add the original battery stats picture, will add info about BQ E4.5 as you said
[12:17] <Henry__> mpchail: see it, thanks :-)
[12:18] <Henry__> just as a side issue - anytime happened to you that the you switched on/off different setting from top bar while calling? Seems I somehow made it with my ear when phone decided I do not have it close enough anymore :-(
[12:30] <robin-hero> hey, is there somebody here who uses rc-proposed channel? I can't make screenshot with today's image.
[12:30] <lotuspsychje> robin-hero: whats your device?
[12:31] <robin-hero> Nexus4
[12:32] <lotuspsychje> im on devel-proposed on nexus7
[12:34] <robin-hero> lotuspsychje: okay, just rebooted my phone, and it works again.. hmmm. weird
[12:35] <lotuspsychje> : )
[12:35] <lotuspsychje> mubuntu magic
[12:35] <lotuspsychje> -m
[14:47] <mhall119> sil2100: congrats on becomeing a core dev :)
[14:48] <shadeslayer> ogra_: Should I just follow https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/ for the E5?
[14:48] <shadeslayer> or is there some special flag I need to pass somewhere
[14:58] <sil2100> mhall119: thanks :)
[15:04] <pmcgowan> sil2100, thats awesome
[15:32] <awe> faenil, any feedback on the Qt/location-services testing?
[15:33] <awe> we're discussing hot-fixability in ~30m
[15:33] <faenil> awe: it's a bit early, I only installed it last evening :/
[15:33] <awe> just asking
[15:33] <faenil> awe: yeah, np :)
[15:34] <faenil> awe: but so far, I haven't noticed anything weird
[15:34] <awe> ok
[15:36] <awe> I generally found that it took around 10-12h to max out the match rules, and for the UI to really start freezing bad
[15:38] <faenil> awe: so now there's no propertieschanged signal at all, right?
[15:38] <awe> no
[15:38] <awe> location-services still listens for NM PropsChanged for APs
[15:39] <faenil> because I don't see the propertieschanged signal as usual every 2 mins
[15:39] <awe> the Qt fix removes the listening for them completely
[15:39] <awe> on the system bus?
[15:39] <faenil> user
[15:39] <awe> nm still send them
[15:39] <tvoss> faenil, nm sends them on the system bus
[15:39] <faenil> tvoss: but there's upstart-bridge, isn't there
[15:40] <awe> yes, but the signals are only fwd'd
[15:40] <awe> if someone asks for them
[15:40] <awe> so perhaps the removal of the Qt listening
[15:40] <faenil> awe: ah ok, thanks
[15:40] <awe> got rid of the signals on the session bus as well
[15:40] <tvoss> awe, yup, likely
[15:40] <faenil> I'll switch to the system bus then
[15:48] <shadeslayer> hm apparently not it
[15:52] <faenil> awe: tvoss btw, my current situation is that it's not lagfree, but there's a perceptible stutter
[15:53] <faenil> it's immensely better than before of course
[15:53] <faenil> :)
[15:53] <tvoss> faenil, could you use awe's magic python script to query the system bus for match rules?
[15:53] <tvoss> faenil, also: immensely better is already quite good :)
[15:53] <faenil> tvoss: yeah, it's not a terrible stutter, it just misses a few frames
[15:56] <faenil> awe: sudo or no sudo for the script?
[15:57] <faenil> and does it need any additional modded dbus?
[15:59] <faenil> currently without sudo it fails with "have you enabled Stats"...sounds like I need the modded dbus from your ppa as well..
[16:01] <awe> for which script?
[16:01] <faenil> awe: getallmatch rules
[16:01] <awe> faenil, I'm not looking for you to run that
[16:01] <faenil> awe: ah ok, I thought that's what tvoss asked for
[16:01] <tvoss> faenil, but me :)
[16:01] <tvoss> awe, :)
[16:01] <awe> I'm looking for whether not it improves the eventual UI lockups
[16:01] <awe> ;D
[16:02] <awe> tvoss, are you joining the rtm meeting?
[16:02] <tvoss> faenil, you likely don't have awe's patched dbus daemon
[16:02] <faenil> you guys sort it out :D
[16:02] <tvoss> awe, yeah, gimme 5
[16:02] <faenil> tvoss: yep, exactly
[16:02] <awe> k
[16:02] <faenil> so, should I run the script or not :D
[16:02] <faenil> tvoss: do you need the output?
[16:04] <tvoss> faenil, you can run, but you won't get any output :) so no, leave it as is
[16:05] <faenil> tvoss: of course, I meant "should I install dbus and get the output"
[16:05] <tvoss> faenil, nope :)
[16:05] <faenil> but installing dbus means rebooting, and that slows down the test :D
[16:05] <faenil> ok ;)
[16:06] <awe> well... before you reboot
[16:06] <awe> when do you see the stuttering?
[16:06] <awe> it is every 2m?
[16:06] <awe> is it occasionally?
[16:12] <shadeslayer> ogra_: I guess what I'm asking is, a) how does one build this file http://system-image.ubuntu.com/pool/ubuntu-dcb4f2e9d6bd32edd5c0fda04ba2f6b74d954c0f16d93abe9d1bdcf917982177.tar.xz and b) how would one flash a modified version of that
[16:28] <seb128> kenvandine, jgdx, do you know what's going on with u-s-s CI and those update tests?
[16:28] <jgdx> seb128, yes
[16:28] <jgdx> fixing now
[16:28] <kenvandine> seb128, jgdx is working on that right now :)
[16:29] <seb128> great
[16:29] <seb128> jgdx, kenvandine, thanks! I feel better when we accept things with CI not grumpy ;-)
[16:29] <jgdx> seb128, kenvandine: the fix is to fake the click server, basically. It seems the test devices are so slow, autopilot times out (10sec) while waiting for a response from the click server.
[16:30] <jgdx> there already is a mock click server in there, it just needs some love.
[16:30] <seb128> k
[16:30] <seb128> relying on access to the real server seems buggy anyway
[16:30] <jgdx> very
[16:30] <jgdx> seb128, kenvandine, one thing though: we can supply the code with faked JSON, but it'll ignore it if the click isn't installed.
[16:31] <jgdx> so on desktop, you'll have no clicks and a fake click server isn't much use
[16:31] <kenvandine> we can fake what's installed though
[16:31] <kenvandine> based on an env variable
[16:32] <jgdx> I'm looking at that now, and it feels very wrong kenvandine  :P
[16:32] <jgdx> the prod code will be riddled with environment variable checking
[16:32] <kenvandine> but it'll make for a more reliable test
[16:33] <jgdx> okay, then the question is, what should the code do when it sees an update that it usually ignores due to it not being installed?
[16:33] <jgdx> just consider them as actual updates?
[16:33] <kenvandine> i think our test will just check for the update we expect
[16:34] <kenvandine> and not care about any others found
[16:34] <jgdx> so the env will be a list of click ids to consider?
[16:34] <kenvandine> that's what i was thinking
[16:34] <jgdx> okay, that works
[16:34] <jgdx> what about semantics, what do we call it?
[16:34] <kenvandine> and when running in the tests, we won't find others anyway
[16:35] <jgdx> right
[16:35] <kenvandine> jgdxrocks_0.1 :)
[16:35] <kenvandine> doesn't matter, as long as it doesn't exist in the store
[16:35] <jgdx> :p
[16:35] <jgdx> I was thinking about the actual variable
[16:35] <jgdx> the env variable
[16:36] <kenvandine> USS_TEST_PACKAGES
[16:37] <kenvandine> something like that
[16:37] <jgdx> +1
[16:37] <kenvandine> as a list of app ids
[16:37] <kenvandine> or... actually no
[16:37] <kenvandine> so the response in the fake server is static, hard coded
[16:37] <kenvandine> we should hard code the package
[16:38] <kenvandine> so USS_TEST_MODE=1 or something
[16:38] <kenvandine> otherwise you have to remember what magic string to use for testing locally :)
[16:38] <jgdx> okay, I wonder if I can use AUTOPILOT_ENABLED then
[16:38] <kenvandine> sure
[16:39] <jgdx> that mode fakes a token
[16:39] <jgdx> so I guess it's okay to attach this stuff to it
[16:39] <kenvandine> so reuse that
[17:07] <peat-psuwit> awe: ping
[17:10] <slash> Hello everybody, today i tried to update my nexus 4 rc-proposed as the parameters icon shown a notification
[17:10] <slash> after launching the parameter, i see the app charging and after nothing...
[17:10] <slash> I tried to reboot still the same.
[17:11] <slash> I'm wondering if i can force the upgrade via the terminal ?
[17:25] <slash> For those interested : sudo mount -o remount,rw /dev/loop0 /
[17:25] <slash> I could upgrade and the bug went away :)
[17:31] <peat-psuwit> In ofono's radio-settings, how can the code knows whether SIM is present or not?
[17:32] <awe> peat-psuwit, you need to look at the SimManager interface
[17:33] <peat-psuwit> awe: D-bus?
[17:33] <awe> yes
[17:33] <awe> that's the only way to talk to ofono
[17:33] <awe> try using list-modems
[17:33] <peat-psuwit> awe: I mean, in the code of radio-settings in ofono itself.
[17:34] <awe> peat-psuwit, if another component of ofono needs to know about SIM state
[17:34] <awe> it uses a watch
[17:34] <awe> eg. sim_state_watch
[17:34] <awe> or it queries the sim atom directly
[17:35] <awe> but usually this is done via a watch
[17:35] <awe> peat-psuwit, also... as the device plugin creates atoms based on SIM states
[17:35] <awe> ah... sorry never mind
[17:36] <awe> I'm pretty sure radio-settings is made available regardless of SIM presence
[17:36] <awe> but that could be device specific
[17:38] <peat-psuwit> awe: On my device, setting 3G preference fails without SIM.
[17:38] <mac_> I booting kmsg I get ureadahead-touch main process (1317) terminated with status 5
[17:39] <mac_> anyone can point me what should I look for?
[17:39] <peat-psuwit> If you can remember, my phone needs to set another slot to 2G before set intended one to 3G
[17:39] <peat-psuwit> And if there's no SIM in another slot, it should skip setting it.
[17:40] <awe> peat-psuwit, yes... dual-SIM modem impls can be tricky like this
[17:41] <awe> you'd need to come up with some way to query the other modem
[17:41] <awe> ( assuming your impl provides two modem instances )
[17:41] <awe> this gets tricky from within a single atom running on a specific modem
[17:42] <awe> I think in our case, we provide a way for a mtkmodem atom to query the device plugin
[17:42] <awe> for certain operations
[17:43] <awe> I'd recommend looking at the public functions exported by our mtk device plugin, as well as the usage within the mtkmodem driver
[17:44] <peat-psuwit> awe: My code actually share most of code with ril device plugin, and I don't want to put more code to shared ril plugin.
[17:45] <awe> peat-psuwit, AFAIK, you cannot query the state of the other modem instance ( ie. representing the other SIM ) from within a driver atom
[17:45] <awe> the only way to do it, is via the device plugin
[17:45] <awe> if this won't work for you
[17:46] <awe> then you need to come up with another mechanism
[17:47] <awe> peat-psuwit, if you want more feedback on potential solutions, perhaps it'd be best to write an email describing the problem and send the to the ml, or just myself and abeato directly
[17:49] <peat-psuwit> awe: Thank you.
[17:49] <awe> peat-psuwit, your welcome
[18:25] <attente> Mirv: hey, could you merge this? it brings the branch back up-to-date by re-adding the missing changelog entries: https://code.launchpad.net/~attente/maliit/merge-wily-changelog/+merge/278353
[22:18]  * mcphail thinks there is definitely _something_ odd with battery drain on OTA8. ANother day, another depressing graph - http://themcphails.uk/screenshot20151124_221453130.png
[22:30] <mcphail> Lots of "Nov 24 21:40:18 ubuntu-phablet powerd[974]: void {anonymous}::reset_alarm_clock() found 35 remaining wakeup requests" in syslog. Is it normal to have lots of these?
[22:32] <mcphail> 1241 occurences today so far
[23:24] <jgdx> mcphail, ugh, could you file that? That sounds excessive.
[23:40] <mcphail> jgdx: do you have an alarm set for the morning? Can you give the output of grep "Nov 24" /var/log/syslog | grep reset_alarm_clock | wc -l
[23:55] <mcphail> https://bugs.launchpad.net/ubuntu-clock-app/+bug/1519543