[03:40] <altker128> Hey guys, I had a chance to play with Ubuntu phone on an N4 (OTA-11) and really LOVED what I saw.
[03:41] <altker128> Some quick questions:  Is it possible to:  Have Unity load an app on start-up, lock the app from being killed?  I want the phone/contacts/calendar to always be running and loaded (the first load takes like 10 seconds)
[04:45] <geohot_> anyone working on getting it running on a nexus 6p?
[04:45] <geohot> or android 4 era devices only?
[04:47] <geohot> i see some stuff in libhybris for android 5
[04:47] <geohot> but nothing for 6
[04:55] <geohot> and also, i try to check out repo "fatal: remote error: access denied or repository not exported: /CyanogenMod/android.git"
[04:58] <geohot> err nvm, upgraded phablet-dev-bootstrap
[07:15] <cc> is there anyone use Meizu pro5 ubuntu phone?
[07:55]  * saavento says Hi
[07:59] <drguell> Hi
[08:17] <saavento> hello
[08:17] <popey> hi
[08:17] <saavento> I have a question regarding dim-timeout
[08:17] <saavento> is there a slider
[08:18] <saavento> or has to be modified by dbus
[08:18] <saavento> command
[08:18] <saavento> dimming the screen I mean
[08:18] <saavento> on a m10 tablet
[08:34] <saavento> nevermind I thought i found it via command
[09:30] <mpt> mardy (or anyone else), where would I report a bug in the Yahoo account plug-in? There doesn’t seem to be a relevant bug-reporting link on <https://wiki.ubuntu.com/Avengers>, <https://wiki.ubuntu.com/Touch/Components>, or <https://wiki.ubuntu.com/OnlineAccounts>
[09:38] <Multbrelch> Hi all. When can we expect that Ubuntu Meizo and BQ phones are available? Is there any hope?
[09:39] <Multbrelch> Currently, all phones are 'sold out': http://www.ubuntu.com/phone/devices
[09:56] <mardy> mpt: account-plugins
[10:36] <mpt> thanks mardy, I moved bug 1594743 there and added account-plugins to /Touch/Components
[11:02] <zzarr> dobey, what drivers are reqiured? if I had a GSM modem as UART /dev/ttyACM0 would that work?
[11:58] <ogra_> hmpf
[11:58] <ogra_> i cant get the nearby scope to refresh anymore after a reboot in rc-proposed today
[11:58] <ogra_> on turbo that is ...
[11:58] <ogra_> no bouncy-bar
[12:12] <popey> ogra_: worked for me on second pull
[12:12] <popey> ogra_: first pull lit up the location indicator, second pull made it refresh
[12:12] <popey> and i have a bonus perpetual bouncer
[12:13] <ogra_> i dont get the bouncy bar on second refresh
[12:13] <ogra_> only on first
[12:13] <popey> maybe location not got yet
[12:13] <ogra_> well, today seems to update ... i get aa refresh flicker in the weather icons
[12:14] <ogra_> just not in nearby after the first try
[12:14] <ogra_> as soon as the location icon turns off i also get the bar again
[12:24]  * ogra_ reboots in the hoope that this fixes anything ... 
[12:25] <ogra_> nope, no go ... no nearby for me at all
[12:27] <ogra_> oha !
[12:27] <ogra_> i didnt get the SIM unlock dialog ... so i forgot to unlock the card ... after unlocking everything works
[12:31] <zzarr> hello!
[12:32] <zzarr> I get "could not open MTP-device" when connecting my phone (translated from Swedish)
[12:32] <zzarr> I have a Meizu MX4
[12:36] <zzarr> is there a nice command line that will solve the problem?
[12:36] <zzarr> I just rebooted the phone, but it didn't help
[12:36] <ogra_> well, the MX4 has in general pretty bad USB hardware, could be a HW issue
[12:37] <ogra_> (underpowered, which makes the signal die ... try a shorter cable or a USB 1.1 port/hub  ... )
[12:37] <zzarr> okey, but it have worked before
[12:38] <zzarr> do I understand you correctly, should I power down the phone?
[12:38] <ogra_> no
[12:39] <ogra_> the USB port of the phone is underpowerd due to bad internal wiring
[12:39] <zzarr> typical... I just did
[12:39] <zzarr> ohh
[12:39] <ogra_> a reboot wont solve that :)
[12:39] <zzarr> sure?
[12:39] <ogra_> if you indeed always used the same cable and it always worked it might not be that issue
[12:40] <zzarr> may be the electrons sleep and are more powered when awake? ;)
[12:40] <ogra_> heh
[12:40] <zzarr> just kidding
[12:40] <ogra_> you could shout or use a loud horn to prove that theory
[12:40] <ogra_> i'm sure people around you will like that a lot, try it :)
[12:43] <dobey> zzarr: i don't know exactly, but unless your goal is dialing into a bbs with minicom, a serial interface is probably not enough :)
[12:44] <zzarr> okey dobey, no that was not what I intended
[12:44] <dobey> i'm not sure the radios in any of the supported devices even have an exposed serial interface
[12:45] <zzarr> okey, it's not a matter of altering a device
[12:45] <dobey> mardy: hi. could you re-review https://code.launchpad.net/~dobey/ubuntuone-credentials/signon-plugin-part2/+merge/296716 please? i think i have it working right, now
[12:46] <zzarr> it's if I could take a SBC and build a phone
[12:47] <dobey> zzarr: "phone" is a pretty vague term these days, with wifi calling, and all kinds of voip services being used
[12:48] <mardy> dobey: looking
[12:49] <zzarr> dobey, yes, I know, but I wish to be able to call through the GSM net like any other smart phone
[12:50] <zzarr> and use 4G data transfer
[12:50] <dobey> zzarr: then see what ofono requires and if the gsm radio in question will work with ofono
[12:51] <zzarr> okey, thanks dobey
[12:54] <dobey> mardy: well, almost working right, anyway. somehow managed to casue pay-ui to get into an infinite loop now, but the basic functionality of getting the token from server, storing it in db, and reading it back out, is working; invalidation is still a bit touchy :)
[13:02] <mardy> dobey: reviewed
[13:29] <dobey> mardy: hmm, how can i make sure online-accounts-ui will do the right thing when Setup.exec() is called, and there's already an account?
[13:29] <dobey> seems it's not
[13:30] <mardy> dobey: the right thing would be not to call it :-)
[13:32] <dobey> mardy: yes, well, displaying an entirely blank window, or just doing nothing, when things do call it, is certainly wrong :)
[13:33] <mardy> dobey: indeed it shouldn't, it should just return
[13:33] <dobey> well "just return" == "doing nothing"
[13:34] <dobey> and that seems wrong
[13:34] <mardy> dobey: file a bug on ussoa, please, with OAU_LOGGING_LEVEL=2 OAU_DAEMON_TIMEOUT=9999 online-accounts-service
[13:35] <dobey> mardy: and that's part of the reason why we have to delete the account currently. :-/
[13:36] <mardy> dobey: weird weird, I think I tested it thorughly (though I did it with facebook, not U1)
[13:40] <dobey> hmm
[13:42] <dobey> mardy: ok, weird. so i just added a twitter account, the app loaded, then i went to the twitter site on my PC, and revoked the app. closed twitter app, opened it again, and the page loaded fine.
[13:42] <dobey> yay oauth :-/
[13:43] <mardy> dobey: you just discovered our dirty secret :-)
[13:43] <mardy> dobey: the webapps don't use oauth, it's just a trick to get the cookies from the webview
[13:44] <dobey> oh that is bloody awful
[13:44] <mardy> dobey: IOW, the webapp asks for an account, but doesn't care (or use) the OAuth token: it just gets the cookies from the account webview, and copies them into its own webview
[13:45] <dobey> yeah, i understood
[13:45] <mardy> dobey: I don't like it either, but unfortunately we didn't come out with a better solution
[13:55] <dobey> mardy: ok, so if for one of the scopes which uses online-accounts, if you add the account, then go to that service's web site and revoke the token and refresh the scope, what happens?
[13:58] <mardy> dobey: it depends on the service: if it invalidates all the tokens, the scope should come up with the "Login..." button
[13:59] <mardy> dobey: but often, OAuth tokens are given a very short life (1 hour), so it might be that the service doesn't bother invalidating them
[14:00] <dobey> oh awesome. blank scope
[14:01] <dobey> YouTube scope is authenticated
[14:01] <dobey> Something weird happened
[14:01] <dobey> ERROR: HTTP request timeout
[14:07] <altker128> Hey guys, I had a chance to play with Ubuntu phone on an N4 (OTA-11) and really LOVED what I saw.
[14:07] <altker128> Hey guys, I had a chance to play with Ubuntu phone on an N4 (OTA-11) and really LOVED what I saw.
[14:07] <dobey> mardy: yeah, this is very bad.
[14:07] <altker128> Some quick questions:  Is it possible to:  Have Unity load an app on start-up, lock the app from being killed?  I want the phone/contacts/calendar to always be running and loaded (the first load takes like 10 seconds)
[14:07] <geohot> anyone ported this to arm64 devices?
[14:08] <geohot> have a ubuntu touch build working on my nexus 5, and have cm building on nexus 6p
[14:08] <dobey> altker128: no. that's not really a reasonable way to deal with the app startup time issue either. there is ongoing work for how to solve the various startup time issues
[14:09] <dobey> geohot: the meizu pro5 and bq m10 tablet are both arm64 devices. they are currently using 32-bit runtimes on top of the 64-bit kernel though
[14:09] <geohot> ahh, yea 32-bit runtime is ok
[14:09] <dobey> geohot: arm64 work is ongoing for eventual move to 16.04 based images
[14:09] <altker128> dobey: Fine, but is it possible to preload an app and have it stay running?  Phone/Contacts/SMS are basic apps that should always be running
[14:09] <geohot> i'm flashing 16.04
[14:09] <geohot> seems to work
[14:10] <geohot> aka xenial-preinstalled-touch-armhf.tar.gz
[14:10] <dobey> most stuff won't work on 16.04
[14:10] <dobey> 16.04's gcc is binary incompatible, so packages from the store which use c++ code won't work
[14:11] <dobey> altker128: no, it's not
[14:11] <geohot> ahh, yea i don't need any of the "phone-like" stuff
[14:11] <dobey> altker128: and i don't agree
[14:11] <altker128> dobey: Well, you're not every user.
[14:11] <geohot> i just want ubuntu userspace on android in a clean way
[14:11] <dobey> altker128: neither are you :)
[14:11] <geohot> and a platform to rip out the android binary blobs from
[14:11] <altker128> dobey: Dude, I'm not saying Ubuntu should make this a permanent change, I'm asking HOW to do it.  You're a really combative person.  You should try and figure out why.
[14:13] <dobey> altker128: no, you asked how to do something, which i told you was not doable, and you blame me for disagreeing with your ideology and stating that it is not supported.
[14:14] <dobey> altker128: you could theoretically create upstart jobs to start them, but there is no guarantee the apps will stay running forever. they would still be subject to the lifetime security policies, and would be killed when RAM is low
[14:14] <dobey> there is absolutely nothing "combative" in anything i said
[14:14] <dobey> geohot: not sure which binary blobs you mean there, but plenty are still required to have a useful device
[14:15]  * awe_ thinks of rild, gps, hw media decoding, ...
[14:15] <geohot> really just the camera, i'm using this for a project
[14:15] <geohot> and the android camera is laggy
[14:16] <geohot> want to talk right to the sensor
[14:16] <geohot> gpu and ril can stay
[14:16] <dobey> well good luck with that then :)
[14:17] <geohot> so those 64-bit devices seem to have android 4 images
[14:17] <altker128> geohot: Driving cars?
[14:17] <geohot> :)
[14:17] <altker128> :)
[14:17] <geohot> anyone gotten ubuntu on android 6 image?
[14:18] <geohot> idk how much has changed, was reading libhybris and looks like it should work
[14:18] <altker128> geohot: Did you also look into Jolla?
[14:18] <geohot> the phone?
[14:18] <altker128> geohot: Sailfish OS has been ported to a few other devices as well
[14:19] <geohot> looks like old ones
[14:19] <geohot> i really want the ubuntu userspace
[14:19] <altker128> geohot: Camera start-up time is often laggy since there's a processor in the camera and it's BLOB is often times loaded on start-up
[14:19] <geohot> it's not even the start up time
[14:19] <geohot> it's the frame time
[14:19] <altker128> shot to shot?
[14:19] <altker128> Oh yeah, you need it for video
[14:19] <altker128> latency sensitive
[14:20] <geohot> wave your hand in front of the camera, yea
[14:20] <dobey> geohot: i think android 6 changed enough to break things. 5.1 base should be doable though (pro5 and m10 are 5.1 base i think)
[14:21] <altker128> geohot: The ISP of the SoC is pretty impressive but getting that stream displayed and accessible for analytics often uses CPU / software pathways
[14:21] <altker128> I should say, ISP of most cell phone SoCs
[14:22] <geohot> htc m10
[14:22] <geohot> is 6.0.1 :(
[14:22] <geohot> going to have to just make it work with 6
[14:24] <geohot> though the m9 has the same processor as the 6p
[14:32] <dobey> mardy, dbarth: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594841
[14:39] <dobey> mardy, dbarth: so, given this, i don't think there is any way we can make the changes to u1 work reliably for ota12, and we should table the changes until we can get around this problem
[14:40] <mardy> dobey: makes no sense, honestly :-)
[14:41] <mardy> dobey: you filed one bug with two completely different issues
[14:41] <mardy> dobey: both irrelevant to U1
[14:41] <dobey> mardy: no, i filed a bug with one issue, and many symptoms
[14:41] <dobey> mardy: it's relevant, because this is exactly why we must delete the token
[14:42] <dobey> s/token/account/
[14:42] <mardy> dobey: no, it's a totally different case, U1 doesn't work with cookies
[14:42] <dobey> mardy: the bug isn't about the cookies
[14:43] <dobey> mardy: the bug is that online-accounts is a drastic failure in the failure case of token-based authentication account types
[14:43] <mardy> dobey: OMG
[14:45] <mardy> dobey: please split the bug, the only common thing that these two issues have in common is that "I don't have a clue of how OA works :-)"
[14:46] <mardy> dobey: they are two very valid issues, but one is to be fixed in the Youtube scope (or maybe in unity-scope-{api,shell}), the other deserves more discussion
[14:50] <kz6fittycent> So, I'm having VERY limited success with "scopecreator" and creating a Youtube channel scope...
[14:51] <dobey> mardy: while i'll agree that the fact we can't use OAuth to initiate a web browser session on most sites; this bug isn't about that specific issue. inclusion of that in the description is simply supporting evidence of a larger architectural problem, which the bug is about
[14:51] <mardy> dobey: then please file a but about this big architectural problem, which I still don't get
[14:52] <dobey> i did file a bug about it. it's the bug we're talking about
[14:52] <dbarth> ahem
[14:52] <dbarth> what about using a hangout to talk?
[14:52] <dobey> i really need to go get lunch in a few minutes
[14:53] <dbarth> quicker and you guys can hopefully understand each other better; wdyt?
[14:53] <dbarth> ah nw
[14:53] <dbarth> dobey: i'll read the bug, but ping us back
[14:54] <dobey> dbarth: ok
[16:08] <peat-psuwit> awe_: Have you talked with abeato about oFono?
[16:08] <awe_> peat-psuwit, did you pull-request already get merged?
[16:08] <awe_> s/you/your/
[16:09] <peat-psuwit> awe_: Yes, it's merged.
[16:09] <awe_> ok
[16:09] <awe_> we're working on a fairly large ofono change at the moment for a new handset
[16:09] <awe_> so we expect to land a new version of ofono soon
[16:09] <awe_> although not before the freeze for OTA12
[16:10] <awe_> so the release to the PPA will somewhat be gated by the OTA12 process
[16:11] <peat-psuwit> awe_: OK, then. Thank you.
[16:11] <awe_> so I can't yet give you an exact date it will land, but most likely within the next two weeks
[16:13] <peat-psuwit> awe_: Ok.
[18:22] <bluetoothsound> I am having huge problems with bluetooth sound on my meizu pro5. sound is stuttering a lot and i tested two different bt-receivers. Is this a known bug?
[18:22] <sigvard> i've had this too, same device
[18:23] <bluetoothsound> i tried to find a bugreport about this but can't find one
[18:23] <sigvard> don't know about that, really...
[18:24] <sigvard> try searching for bluez, maybe?
[18:24] <bluetoothsound> the stuttering is much worse, when the system-settings-app is opened and searching for bt devices
[18:24] <sigvard> figures, since the bt radio would be partly bussy with other things...
[18:24] <bluetoothsound> i followed the 'bug filing' link in this channel's status message and went to the 'bluetooth' section
[18:25] <sigvard> excellent! do you have a link so i can + it?
[18:25] <bluetoothsound> no, i didn't file a bug. I tried to find an existent bugreport but didn't find one
[18:43] <ahoneybun> bluetoothsound: sigvard https://wiki.ubuntu.com/Avengers
[18:53] <bluetoothsound> sigvard: i opened a bugreport at https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1594939
[19:10] <sigvard> bluetoothsound: cool
[19:19] <sigvard> ahoneybun: thanks man, really helpfull. in the future too.
[19:21] <bluetoothsound> sigvard: is your pro5 on the stable channel?
[20:44] <mterry> Elleo, heyo, got a moment for a question about how the OSK handles focus / pressing the OSK return button
[20:45] <mterry> Elleo, in particular, I'm trying to trace down where my entry is losing focus after pressing the OSK enter button -- does the OSK do that?  maliit?  or is it part of the qml item's accepted() handling?  I can dig more, just curious if you knew
[20:48] <mterry> Actually, it's not losing focus I guess.  It's just losing the OSK
[20:50] <Elleo> mterry: the OSK won't get removed unless it is either losing focus or its explicitly told to hide, but the OSK doesn't remove focus from things itself (except when the user dismisses it), I believe that's all handled by the toolkit
[20:53] <mterry> Elleo, ok, and Return isn't handled specially?
[20:53] <mterry> maybe this issue is in how the shell manages the input method surface
[20:54] <Elleo> mterry: its not handled specially by the keyboard, I don't know if the UITK is doing anything extra besides emitting accepted() when seeing it
[20:54] <mterry> Elleo, OK thanks for the hints!
[20:54] <Elleo> no problem :)