[07:15] <dholbach> good morning
[07:26] <cwayne> davmor2, yo
[08:25] <Maple> hey all
[08:25] <Maple> new to ubuntu touch
[08:27] <Maple> Is private Internet access available on touch then?
[08:39] <popey> Maple: you mean vpn?
[08:40] <Maple> yes vpn
[08:41] <popey> Maple: it's not hooked up to the UI yet, but I suspect it will be in the future.
[08:42] <Maple> Is possible to set up from terminal?
[08:57] <popey> Maple: not sure, not tried
[08:58] <Maple> private internet access is the sponsor here?
[08:59] <popey> Maple: Here? This is an irc channel, it doesn't have sponsors...
[08:59] <popey> (other than the people who maintain it [freenode / pdpc] and Canonical who sponsor Ubuntu development)
[09:01] <Maple> Just saw something about them being a sponsor on the login page
[09:01] <Maple> I think lol
[09:02] <popey> Maple: login page of what?
[09:04] <popey> Maple: you're using a web page to view this irc channel? I'm interested to know where that page is.
[09:08] <Maple> lost connection there for a min
[09:08] <Maple> I think they sponsor
[09:08] <Maple> freenode
[09:09] <davmor2> cwayne: Wot not wall
[09:11] <popey> Maple: so they do!
[09:14] <Maple> They should have a channel I spose
[09:15] <Maple> ill try to get hold of em
[09:25] <dholbach> bzoltan, so https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu-touch.vivid needs an upload?
[09:25] <bzoltan> dholbach:  yes, the ubuntu-sdk-qmake-extras needs to be pulled by the ubuntu-sdk-libs-tool in all 15.04 chroots in order to enable the the new templates
[09:26] <bzoltan> dholbach:  usually Mirv does it for the SDK, but he is still out ... and all other regular folks are covered with other duties.
[09:26] <dholbach> bzoltan, I don't know what the latest is in terms of seed changes - touch grew a bunch of processes on their own
[09:26] <dholbach> ogra_, ^ do you know what to do?
[09:27] <ogra_> dholbach, yes,  but i dont have time right now (i told bzoltan in ~2h ... but seems he cant wait)
[09:27] <bzoltan> ogra_:  2 hours I can wait :) But I waited 5 days already
[09:27] <ogra_> you need to merge the seed change and rebuild the meta package after you ran ./update in the source package dir (and adjust the changelog afterwards)
[09:28] <dholbach> ogra_, right, that I know - I was just wondering if there was any more red tape...
[09:28] <ogra_> right, and i told you after two days that every core-dev can do it ... you could just have asked in #ubuntu-devel for a sponsor
[09:28] <dholbach> ogra_, so it can just be sponsored like anything else?
[09:29] <ogra_> yeah
[09:29] <ogra_> its just a universe package
[09:29] <ogra_> (seeds are owned by core-dev though)
[09:29] <dholbach> right
[09:29] <dholbach> I'll take a look
[09:29] <dholbach> thanks
[09:30] <cwayne> davmor2, u wot m8
[09:31] <davmor2> cwayne: WOT NO WALL
[09:31] <bzoltan> Thank you ogra_ and dholbach.
[09:31] <cwayne> davmor2, so was wondering what happened re: the online accounts being broken stuff
[09:31] <cwayne> was the signon-apparmor-extension reverted?
[09:32] <JamesTait> Good morning all; happy Monday, and happy Australia Day! :-D
[09:40] <dholbach> bzoltan, uploaded
[09:40] <bzoltan> dholbach:  that was fast :D
[09:44] <bzoltan> zbenjamin:  I just have flashed a fresh RTM image on my krillin without dev mode... I have no problem adb shelling in when the screen is locked
[09:44] <zbenjamin> bzoltan: ok, i wonder what that change is then
[09:44] <ogra_> depends how you flashed
[09:44] <bzoltan> zbenjamin:  I am not going to ask it :) I am happy with the present situation
[09:44] <ogra_> --developer-mode disables screen lock checks
[09:45] <ogra_> if you flash normally it stays on
[09:45] <bzoltan> ogra_:  I have not used that switch
[09:45] <ogra_> weird
[09:45] <bzoltan> ogra_: i just flashed the 213
[09:45] <ogra_> then you shouldnt get in
[09:46] <bzoltan> ogra_:  the adb was off at first of course, I turned the dev mode on in settings, set the passcode
[09:46] <ogra_> a normal flash wont put the override in place so you should not be able to do the initial connection if you have a locked screen
[09:46] <bzoltan> ogra_:  but after that plug out, plug in ... screen locked and I can adb shell in. But I am extremely happy with that
[09:47] <ogra_> well, that would be a release blocker
[09:47] <ogra_> bzoltan, we are talking abour rtm, right ?
[09:47] <bzoltan> ogra_:  the adb is not on by default... it comes alive after I enabled the dev mode
[09:48] <bzoltan> 2015/01/26 11:30:23 Flashing version 213 from ubuntu-touch/ubuntu-rtm/14.09-proposed channel and server https://system-image.ubuntu.com to device krillin
[09:48] <ogra_> has nothing to do with on by default
[09:50] <ogra_> sergiusens, u-d-f only puts the adb_onlock file in place when developer-mode is set, right ?
[09:51] <sergiusens> ogra_: correct; I can double check, give me a sec
[09:51] <ogra_> bzoltan, did you use --bootstrap ?
[09:51] <bzoltan> ogra_: no
[09:51] <bzoltan> ogra_:  should I?
[09:51] <ogra_> ah, and you flashed that device before with --developer-mode at some point i guess
[09:51] <sergiusens> only on clean installs as well
[09:52] <davmor2> cwayne: it was http://i1.ytimg.com/vi/BPeDzRW9NIQ/maxresdefault.jpg
[09:53] <bzoltan> ogra_:  sure I did
[09:53] <sergiusens> ogra_: ok, so developer-mode enables the two files, adb_onlock and the developer_mode file
[09:53] <sergiusens> ogra_: and password requires a 'format data'
[09:54] <sergiusens> ogra_: all these rules become moot once we ship with a non adbable recovery
[09:54] <sergiusens> ogra_: we can just put those file in the recovery image
[09:55] <sergiusens> ogra_: since it's not even 7AM here, I'll bbl :-P
[09:55] <ogra_> sergiusens, right, i'm just worried we leave that file behind somehow on fresh flashes
[09:55] <ogra_> i think we should perhaps forcefully delete it if dev-mode isnt set during flash
[09:55] <ogra_> i think it isnt even deleted when using --wipe
[09:55] <ogra_> because it lives one dir level up from what gets wiped
[09:56] <bzoltan> ogra_:  I used the wipe
[09:56] <ogra_> bzoltan, right
[09:57] <ogra_> but i bet you have a /userdata/.adb_onlock file
[09:58] <ogra_> even after --wipe
[09:59] <bzoltan> ogra_: sergiusens: I have two concerns: 1) It will be seriously disturbing for app developers that they are forced to manually unlock the screen  whenever they want to run their app from the SDK. But i do understand that it is not a priority :) 2) i just want to run my UITK tests without manual hustle ... and it does involve reboots, so I need to be able to flash the device just as i do now
[10:00] <ogra_> bzoltan, 1) use --developer-mode when flashing
[10:00] <bzoltan> ogra_:  yes i do have the .adb_onlock
[10:00] <ogra_> 2) see 1)
[10:00] <ogra_> 3) put the file in place yourself by touching /data/.adb_onlock from recovery
[10:00] <bzoltan> ogra_:  2) yes, that is what i use... I hope that behavior will not change.
[10:00] <ogra_> no
[10:01] <ogra_> the point is that if you later flash without --developer-mode i think the file needs to be wiped
[10:02] <bzoltan> ogra_:  yes, that sounds logical
[10:02] <ogra_> developers should keep that flag ... if they re-flash to give the phone to someone else and dont use that flag, the file should be wiped so the screen lock check is there for the new user
[10:02] <ogra_> though i guess if you flash to give it away you also use --bootstrap to reformat the partitions
[10:03] <bzoltan> ogra_:  So we expect the developers to jump thru loops and do some magic in order to enable them creating super simple apps? :)
[10:04] <ogra_> bzoltan, ask the security team ... that stuff isnt my desgn, i only implemented it ...
[10:04] <ogra_> long term target is key auth
[10:04] <bzoltan> ogra_:  I know :) I do not shoot the messenger
[10:04] <ogra_> which means you will need to approve a key after each flash
[10:04] <ogra_> on screen
[10:05] <ogra_> thats not much different than unlocking once
[10:05] <bzoltan> ogra_:  and our short term target is to engage ... making such a silly policy is not exactly doing that
[10:05] <ogra_> (you wont have to do it subsequently though )
[10:06] <ogra_> the point is that someone stealing your phone shuldnt be able to adb in when he doesnt know the PW/PIN
[10:06] <ogra_> even if you switched dev mode on
[10:06] <ogra_> (in the UI that is)
[10:07] <ogra_> if you have overridden that at flash time already, we assume you are a developer and leave the feature off completely
[10:07] <ogra_> (i.e. if you use --developer-mode)
[10:07] <bzoltan> ogra_: that is fine.. but under a single connection I would expect the device to be available ... so it is OK to request pin code once I plug in... but not every minute
[10:08] <ogra_> we onyl request it on connect events, if you stay connected you wont have any new unlock request
[10:09] <ogra_> anyway, you'Re a developer, use --developer-mode ... it is for you :P
[10:10] <bzoltan> ogra_:  hmm.. I am a developer, but I do not wish to flash ...
[10:17] <ogra_> bzoltan, so just touch the file then
[10:22] <shuduo> ogra_: i use --developer-mode and --password=phablet to flash devel image but i still can't sudo with password. any idea?
[10:23] <ogra_> shuduo, does unlocking the screen with that pasword work ?
[10:24] <shuduo> ogra_: the unlock pin is set with another 4 digital number
[10:24] <ogra_> well, that means you did set a new password then ... in the wizard i guess :)
[10:24] <ogra_> use the pin with sudo
[10:25] <shuduo> ogra_: great. it works now. thanks!
[10:25] <ogra_> --password=phablet will only work if you keep it set and dont change anything via the UI ... then whatever you  changed to will be used
[10:47] <rpadovani> oSoMoN, o/
[10:47] <oSoMoN> rpadovani, hey!
[10:48] <rpadovani> oSoMoN, I have a couple of questions about https://code.launchpad.net/~rpadovani/webbrowser-app/addressBarFullWidth/+merge/239039/comments/612176
[10:49] <rpadovani> oSoMoN, to fix the module problem I have to add it to debian/control, right?
[10:51] <oSoMoN> rpadovani, yes
[10:52] <rpadovani> oSoMoN, cool, and what about other two errors? I thought eventually and equals were autopilot valid commands
[10:52] <oSoMoN> rpadovani, they are, but you need to import them to use them
[10:54] <rpadovani> oSoMoN, oh, I see - thanks! I also see you reply to all my branches, I'll take care to fix them asap :-)
[10:54] <rpadovani> thanks again!
[10:54] <oSoMoN> cheers!
[11:05] <rpadovani> oSoMoN, sorry to bother again, in debian/control I have to add qtdeclarative5-ubuntu-keyboard-extensions0.1 in Source: webbrowser-app/Section: x11 or Package: webbrowser-app/Architecture: any or both? Or others?
[11:07] <oSoMoN> rpadovani, I think you’ll have to add it to both Source and "Package: webbrowser-app", because when building the package the unit tests are run, and AddressBar.qml is unit-tested
[11:08] <rpadovani> thanks! Just pushed, let see if now works
[11:19] <mardy_> davmor2: hi! When you found bug 1413655, did you have only the U1 account, or others too?
[11:20] <davmor2> mardy_: all of them
[11:20] <davmor2> bar flickr I think
[11:22] <mardy_> davmor2: you mean you had U1 and flickr?
[11:23] <davmor2> mardy_: no I was signed into all of them except flickr
[11:25] <popey> hmm, my flo running 171 ubuntu-touch/ubuntu-rtm/14.09-proposed refuses to connect to any wireless networks...
[11:26] <popey> haha, now it works. Stupid tablet.
[11:26] <dholbach> bzoltan, I think the fix has landed already
[11:27] <bzoltan> dholbach:  Cool, thanks
[11:42] <davmor2> popey: it hates you you just have to hate it back harderererer
[12:05] <sergiusens> bzoltan: the concerns you have you have to take to ogra_ and the security team, not me; I am against all these "features" in the first place (the files to flag access)
[12:05] <ogra_> heh
[12:06] <bzoltan> sergiusens: ogra_: i tried to talk to people before, but it seems to be a solid requirement
[12:06] <ogra_> well, the key support will eventually fix all this
[12:57] <fredericc38> Hi all!
[12:58] <fredericc38> I tried ubuntu touch a couple of months ago and some bugs were really annoying what's about today??
[14:33] <kenvandine> mandel, did you see my comment on they check-hash bug report?  I confirmed our DownloadTracker isn't getting the error signal from udm, i haven't been able to confirm if udm emitted it though
[14:34] <mandel> kenvandine, I missed it, sorry, again in a meeting (gosh) but I'll take a look asap
[14:34] <mandel> kenvandine, AFAIK udm does emit it or else the tests would not pass when building udm :)
[14:35] <kenvandine> if so, then we aren't getting it
[14:35] <kenvandine> mandel, we have a warning if it fails to connect to the signal, which isn't getting logged
[14:35] <kenvandine> and i added some debug output in our callback, nothing
[14:35] <mandel> kenvandine, I'll take a look, no need to worry, I should be able to find the cause really fast
[14:36] <kenvandine> mandel, thx
[14:42] <dobey> mardy_: so, any idea how to fix it so that unconfined click packages actually used "unconfined" as the profile instead of $APPID?
[14:43] <kenvandine> jgdx, i'm anxious to see CI results for your 2 AP fix branches, but I noticed that jenkins isn't subscribed to the review...
[14:44] <dobey> kenvandine: jenkins usually auto-adds itself as a reviewer to any MPs for branches it watches
[14:46] <kenvandine> dobey, i know...
[14:46] <kenvandine> but it didn't for 2 MPs jgdx filed this morning
[14:46] <kenvandine> which is odd...
[14:46] <kenvandine> oh... just now it added it... way late :)
[14:47] <dobey> kenvandine: sometimes it's quite slow :)
[14:47] <kenvandine> doesn't usually take this long :)
[14:47] <bzoltan> ogra_: the last problem is that /userdata/.adb_onlock needs to be created as root :(
[14:48] <ogra_> bzoltan, thats the reason why u-d-f does it for you :)
[14:49] <bzoltan> ogra_:  I mean, I do not want to flash the device just for that
[14:49] <sergiusens> bzoltan: that's a private interface, I wouldn't rely on it for functionality
[14:50] <bzoltan> sergiusens:  ogra_: we need an interface to allow the developer to set that flag
[14:50] <sergiusens> bzoltan: ask the product team and it will make it into our sprint planning
[14:50] <mardy_> dobey: I just sent an email about it
[14:50] <mardy_> dobey: I think that the immediate fix is the one I suggested; let's see if jdstrand_ can play some magics later on
[14:51] <ogra_> bzoltan, this intertface is going away once we switch to key auth
[14:51] <ogra_> not sure it is worth spendin any time on it
[14:51] <ogra_> developers that want to use automation should od the initial flash of the device with --developer-mode
[14:52] <jgdx> kenvandine, yeah, me too
[14:52] <kenvandine> jgdx, there's a merge conflict in your security-privacy-add-sim-unlock-1378883 branch
[14:52] <jgdx> kenvandine, right
[14:52] <bzoltan> ogra_: I could put a simple switch in the SDK UI so the developers could create that file
[14:52] <ogra_> please dont
[14:52] <sergiusens> bzoltan: that's making it easy to enable a security hole
[14:52] <ogra_> that would be a horrid hack and forcing a securioty hole open
[14:53] <bzoltan> ogra_:  I do not :) because I can not
[14:53] <ogra_> good
[14:53] <bzoltan> ogra_:  not bigger than telling the developer to flash the device with --developer-mode
[14:53] <ogra_> juts tell devs they should use --developer-mode on first flash of the device
[14:53] <ogra_> if you dont --wipe or --bootstrap then the file will stay
[14:53] <bzoltan> ogra_: do we tell the developers that it will open the adb connection wide up?
[14:54] <ogra_> we didnt tell the developers at all yet
[14:54] <ogra_> since this interface is actually only for automation
[14:54] <bzoltan> ogra_:  but the u-d-f --help lists the --developer-mode
[14:54]  * ogra_ was actually trying to get the options removed from --help and the manpage ... but i was overruled
[14:55] <bzoltan> ogra_:  I know it is for CI and for me :)
[14:56] <bzoltan> ogra_:  all right, it is fine ... the SDK will tell the developer to unlock the screen each time the unlocked device is pluged in ... after it is unlocked the SDK does all the magic via ssh, so i do not care about the adb anymore ...
[14:57] <ogra_> right
[15:11] <dobey> mardy_: you forgot to add jdstrand_ to cc: list, so i replied to add him and ask his thoughts. hopefully he'll be on soon and have a good suggestion about how to fix it.
[15:12]  * jdstrand_ is here now
[15:12] <jdstrand_> give me a couple minutes
[15:12]  * jdstrand is helping with another phone bug atm
[15:14] <jgdx> kenvandine, fixxd
[15:14] <kenvandine> jgdx, thx
[15:14] <jgdx> kenvandine, this is also a deb run, but feel free to review the sim unlock
[15:14] <kenvandine> jgdx, will do, once CI runs for debs
[15:14] <jgdx> kenvandine, ack
[15:15] <dobey> jdstrand: sure, no problem. thanks
[15:20] <mardy_> dobey: eh, thunderbird should also warn me when I mention people but forget to add them to CC ;-)
[15:23] <seb128> ricmm, hey, seems like your recent platform-api update to vivid made unity8-desktop/amd64 stop starting
[15:24] <seb128> Saviq, greyback_, ^ moved there since he's not on -unity
[15:24] <Saviq> it worked for me, but I did have a qtmir built myself, so might be a rebuild is all that's needed?
[15:25]  * Saviq tries again after having reverted to distro qtmir
[15:25] <ricmm> seb128: whats the error?
[15:26] <seb128> ricmm, dunno, get a blank screen after updating ubuntu-application-api2-desktop
[15:26] <Saviq> hmm still working here
[15:26] <seb128> ricmm, unity8.log has
[15:26] <seb128> "Ubuntu Platform API: Unable to load selected module. -- Aborting"
[15:26] <greyback_> https://code.launchpad.net/~gerboland/platform-api/add-dlerror/+merge/241792 <- this would help for next time
[15:27] <seb128> ricmm, http://paste.ubuntu.com/9883282
[15:27] <seb128> that's the unity8.log
[15:33] <kenvandine> jgdx, what is this connectivity binding used for?  Is it the wrapper for NM?
[15:34] <jgdx> kenvandine, no, it's a wrapper for the private connectivity api trusted apps can use
[15:34] <kenvandine> jgdx, so we can't use the Ubuntu.Connectivity CPI?
[15:34] <kenvandine> s/CPI/API
[15:35] <jgdx> kenvandine, isn't that the public one without sim/modem unlock features?
[15:35] <kenvandine> i really don't know :)
[15:36] <kenvandine> just making sure we aren't re-inventing :)
[15:36] <kenvandine> or... rather had something old that isn't needed anymore
[15:36] <kenvandine> jgdx, i wasn't sure what that was used for in cellular and wifi
[15:37] <jgdx> kenvandine, it's brand spankin' new, 'published' here: https://bugs.launchpad.net/indicator-network/+bug/1374082/comments/7
[15:37] <ricmm> seb128: whats UBUNTU_PLATFORM_API_BACKEND set to?
[15:37] <ricmm> do you have 2.7.0 of -desktop and -test ?
[15:37] <jgdx> kenvandine, we need this in the cellular panel as well, so eventually we should move it into src/ ? https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1414670
[15:38] <seb128> ricmm, how do I check that env variable if unity8 fails to start?
[15:39] <seb128> ricmm, -test is not installed
[15:39] <kenvandine> jgdx, ok, the backend for  Ubuntu.Connectivity is provided by indicator-network, but i guess that private API probably isn't exposed
[15:39] <kenvandine> jgdx, so carry on :)
[15:39] <kenvandine> jgdx, thanks for explaining
[15:39] <jgdx> kenvandine, that's my understanding. :)
[15:39] <jgdx> np
[15:40] <seb128> ricmm, works after installing -test, missing depends?
[15:40] <seb128> Saviq, ^ might explain why it works for you
[15:40] <greyback_> seb128: ricmm: just a note, qtmir is setting UBUNTU_PLATFORM_API_BACKEND to either desktop_mirclient or touch_mirclient, if it hasn't been set already. It decides which based on if DESKTOP_SESSION contains the string "mir"
[15:40] <ricmm> seb128: it was just a guess, but thats odd
[15:40] <ricmm> lemme think about it
[15:42] <seb128> ricmm, christownsend confirms that installing -test makes it work again for him as well
[15:44] <ricmm> seb128: I see whats going on, its my bug/bad
[15:44] <ricmm> :)
[15:44] <seb128> good
[15:45] <ricmm> I'll fix in a sec
[15:45] <seb128> chris is opening a bug report
[15:45] <seb128> thanks
[15:46] <ricmm> ask him to add me to it and ping m
[15:46] <ricmm> me
[15:46] <jgdx> bfiller, I'm seeing this bug https://bugs.launchpad.net/camera-app/+bug/1414682 in the camera app, just flashed my krillin and updated the camera app
[15:49] <ChrisTownsend> ricmm: Hey, I'll enter a bug report against platform-api about desktop breaking.
[15:50] <ricmm> ChrisTownsend: thanks, assign me to it
[15:51] <ChrisTownsend> ricmm: Ok, will do.  Ping me if you want more info or whatever in the bug report.
[15:51] <bfiller> jgdx: is your disk full? also can you do a "click list | grep camera"
[15:51] <jgdx> bfiller, "false alarm", I'
[15:51] <jgdx> bfiller, I deleted my Pictures folder
[15:51] <ricmm> ChrisTownsend: no I already know whats going on, bug is just to track
[15:51] <ricmm> and close
[15:51] <jgdx> updating bug…
[15:51] <bfiller> jgdx: whew
[15:51] <bfiller> :)
[15:51] <jgdx> :D
[15:51] <jgdx> indeed
[15:52] <ChrisTownsend> ricmm: Sweet!
[15:52] <bfiller> jgdx: there is a know but that the controls disapear when switching between front and back cameras until you tap on the viewfinder
[15:52] <bfiller> bug
[15:54] <ChrisTownsend> ricmm: FYI, https://bugs.launchpad.net/platform-api/+bug/1414692
[15:55] <jgdx> bfiller, yeah, I see it.
[15:56] <dobey> cwayne, nhaines: either of you have problems with something hard freezing on n5? past couple of days i've had many cases where the screen wouldn't turn back on, and i couldn't phablet-shell into the device either, and had to reboot
[15:58] <ricmm> ChrisTownsend: thanks
[16:26] <seb128> kenvandine, jgdx, hey, I'm looking at bug #1412523 ... do you have a preference on how the "enable button" logic should be handled? between having the button using a "enabled: <complex list of cases>" or having the different entry widgets doing things on onTextChanged?
[16:26] <seb128> like either we do
[16:27] <seb128> enabled: oldmode=swipe && (if passcode, length = 4, if passphrase, length >0) || oldmode=passcode ...
[16:29] <kenvandine> seb128, i'm fine with the complex list of use cases
[16:29] <seb128> kenvandine, great, thanks
[16:29] <kenvandine> np
[16:40] <pmcgowan> seb128, the data that is used on the battery graph, is that stored in a file somewhere by any chance?
[16:41] <seb128> pmcgowan, it comes from upower and the data are in /var/lib/upower
[16:41] <pmcgowan> seb128, thanks
[16:41] <kenvandine> seb128, i'm landing your focus branch now... just waiting for the ppc build in the silo :/
[16:41] <seb128> kenvandine, great, thanks
[17:03] <jdstrand> bfiller: not sure who will do the camera-app upload for bug #1414625, but can you have whoever does ping me when they do, and I'll add a comment to the store review so future reviewers will know what is going on?
[17:03] <jdstrand> popey: fyi, ^ if you see that, ping me-- adding a read_path to camera-app
[17:04] <pmcgowan> seb128, is there any tool to display those files? i assume the first item is a time stamp
[17:04] <seb128> pmcgowan, no tool that I know, sorry
[17:04] <pmcgowan> seb128, k
[17:05] <seb128> pmcgowan, yeah, it's timestamp, %charge, status
[17:05] <seb128> pmcgowan, there is a new data point written on changes
[17:05] <bfiller> jdstrand: I'll do the camera-app upload
[17:05] <bfiller> jdstrand: and will ping you
[17:05] <seb128> so if you work plugged at 100% charge for 3 days there are no data during this time
[17:05] <pmcgowan> seb128, makes sense
[17:05] <seb128> pmcgowan, are you looking at a specific issue?
[17:05] <pmcgowan> trying to track down some precipitous drops in battery level
[17:06] <pmcgowan> like 30% to 0 in minutes
[17:06] <bfiller> jdstrand: assuming will need changes to camera-app json and a new apparmor-easyprof package?
[17:07] <saidinesh5> Elleo: just a heads up, thanks to a few nice/dirty tricks to the Brute Force Matcher in skeyer it's query time is down to around 200ms for a long word that was taking 5 seconds to compute before...
[17:07] <saidinesh5> The word is the swipeHint of the word beautiful.. Which is around 40 characters
[17:08] <Elleo> saidinesh5: nice :)
[17:08] <saidinesh5> And for normal words the response time is around 27ms
[17:08] <Elleo> sweet
[17:08] <saidinesh5> So i think we've found your hunspell replacer if not anything :p
[17:08] <Elleo> heh
[17:09] <jdstrand> bfiller: just camera-app
[17:09] <jdstrand> bfiller: I haven't updated the bug yet
[17:09] <saidinesh5> (This one is kind of aware of key board layouts too)
[17:09] <popey> jdstrand: if I see it in the store?
[17:09] <Elleo> saidinesh5: cool
[17:09] <jdstrand> popey: yes
[17:09] <bfiller> jdstrand: cool
[17:09] <popey> jdstrand: ok
[17:09] <jdstrand> popey: the camera-app already triggers a manual review becuase of video_files and picture_files policy groups
[17:09] <saidinesh5> Now will have to wait till i get my laptop so that i can test this out on my nexus 7
[17:10] <saidinesh5> With Ubuntu touch
[17:10] <jdstrand> popey: something new is being added, and I wanted to comment on it for posterity
[17:10] <popey> Right ho.
[17:11] <saidinesh5> Also need to optimize the memory requirements of this...
[17:11] <Elleo> saidinesh5: let me know how it works out on the device :)
[17:11] <saidinesh5> Yup
[17:11] <saidinesh5> Oh or i can compile it on the device itself now.... Hold on
[17:12] <Elleo> saidinesh5: what sort of tricks are you doing for those speed ups?
[17:12] <saidinesh5> 3 little tricks mainly
[17:13] <saidinesh5> 1) early return in edit distance method if you're trying to find only k differences...
[17:13] <saidinesh5> 2) if you're trying to find only 5 words, adjust k accordingly based on the results you've collected so far
[17:13] <saidinesh5> 3) if manhattanDistance(input,word) > k don't bother going for editDistance
[17:14] <saidinesh5> And then if word lengths differ by more than k, don't bother computing manhattanDistance either
[17:14] <Elleo> ah, interesting
[17:14] <saidinesh5> Manhattand distance is basically the number of times each character occurs
[17:14] <saidinesh5> In the string
[17:15] <saidinesh5> Difference of that in the two strings i mean
[17:15] <Elleo> yeah
[17:15] <Elleo> what sort of dictionary size are you working with?
[17:15] <saidinesh5> So that's O(n)
[17:16] <saidinesh5> Android dictionary... Around 180000 words maybe?
[17:16] <Elleo> interesting, hunspell's US dictionary is only about 62k entries
[17:16] <saidinesh5> But to search for a word I'm only searching  the words starting with the neighbors of a key
[17:17] <saidinesh5> So my search space is probably the same sized
[17:17] <Elleo> ah, right
[17:17] <saidinesh5> 9 neighbors of a key assuming a grid of keys
[17:17] <Elleo> so there's an assumption that the user is correctly spelling the first character (but possibly missing the key)
[17:17] <saidinesh5> Yeah
[17:18] <saidinesh5> Otherwise the results are too noisy
[17:18] <Elleo> that could fall down on some misspellings like "psychologist" -> "sychologist"
[17:18] <saidinesh5> That's the next todo item actually :p
[17:19] <Elleo> ah, cool :)
[17:19] <saidinesh5> Add a frequently misspelled list of words basically
[17:19] <Elleo> right, seems reasonable
[17:19] <saidinesh5> Mhm
[17:19] <Elleo> but could be a fair amount of work compiling those lists for all languages
[17:20] <saidinesh5> But otherwise, the swipe for psychologist and sychologist is quite different
[17:20] <Elleo> yeah
[17:20] <saidinesh5> I'm sure Google open sourced some words
[17:20] <saidinesh5> Word lists i mean
[17:20] <Elleo> if you do find some existing word lists like that could you point them my way too, would be handy to have a look at
[17:21] <saidinesh5> Oh also totally forgot, for normal words we can search the whole word list btq
[17:21] <saidinesh5> Normal words = ~ 8 characters long
[17:22] <Elleo> ah, right; so these optimisations only get applied to long slow words?
[17:22] <saidinesh5> More like only when the user swipes a word as opposed to types a word
[17:23] <saidinesh5> But yeah will have to look into that change...
[17:23] <saidinesh5> You have access to the sources right?
[17:23] <saidinesh5> Lib/bruteforcematcher.cpp
[17:24] <Elleo> saidinesh5: cool, will have a look
[17:24] <saidinesh5> Also will probably test out simstring library after this
[17:24] <saidinesh5> But need more exhaustive tests first
[17:25] <saidinesh5> Need to find out the average precision and all
[17:25] <Elleo> interesting, hadn't seen simstring before
[17:25] <Elleo> just reading up on it now
[17:25] <saidinesh5> Looks interesting actually it had it's own binary format and
[17:26] <saidinesh5> Mmaps it...
[17:26] <Elleo> will have to have a play with that myself at some point
[17:27] <saidinesh5> Also do you know any way to mmap a QList<QString>
[17:27] <saidinesh5> Can't seem to find any documentation / sample code
[17:28] <saidinesh5> Oh grr no adb on this machine
[17:28] <saidinesh5> And can't ssh without my public key on the device
[17:28] <Elleo> nope, not something I've tried before, not sure if the Qt internals would lend themselves to that sort of treatment well (without risking issues between Qt versions)
[17:29] <saidinesh5> Well there is a QFileDevice:map
[17:29] <saidinesh5> For calling mmap
[17:29] <saidinesh5> It returns a uchar*
[17:30] <saidinesh5> The thing is QString seems to take care of its own memory allocation internally
[17:30] <saidinesh5> So not sure what happens when i a QByteArray
[17:31] <saidinesh5> Do a qdatastream >> qstring i mean
[17:31] <Elleo> yeah, I'd suspect it'd end up effectively doing a read of all the data, so you'd end up with it all in memory anyway
[17:31] <Elleo> that's just a guess though
[17:40] <saidinesh5> Not sure for me there is 2x the string data
[17:41] <saidinesh5> Well 3x or 4x actually cuz of the swipe hints
[17:42] <saidinesh5> Compiling things on the tablet now... Let's see
[17:47] <saidinesh5> Elleo: same 155 ms on the tablet...
[17:47] <saidinesh5> Probably slightly faster on the tablet
[17:48] <saidinesh5> This laptop is about 8 years old...
[17:48] <saidinesh5> Intel core 2 duo....
[17:49] <Elleo> saidinesh5: cool
[17:54] <pmcgowan> mterry, hows progress on that pincode polkit caching thing
[17:54] <mterry> pmcgowan, much more involved than I had thought, but just filed an MP this morning
[17:54] <pmcgowan> mterry, ok, might like to land that if we have it today
[18:06] <dobey> mardy: still around?
[18:26] <taiebot> Waouh conference calling on vivid.
[18:27] <taiebot> do not know when it has landed and i have not tested it yet
[19:27] <kenvandine> is anyone else still seeing bug 1385331?  It says it's fixed in vivid, but I'm still seeing it in both vivid and rtm
[19:29] <kenvandine> and the canonical-system-image task is marked as fixed as well...
[19:30] <kenvandine> pmcgowan, you marked bug 1385331 as fixed, can you confirm it should be?
[19:31] <pmcgowan> kenvandine, oh maybe not since the other mr didnt land yet
[19:31] <kenvandine> pmcgowan, it landed in vivid though
[19:31] <kenvandine> but  i'm still seeing it in vivid too
[19:31] <pmcgowan> kenvandine, yeah but I meant to track for rtm
[19:31] <pmcgowan> ok so not fixed
[19:31] <kenvandine> yeah... but i don't think it's really fixed for vivid either
[19:32] <kenvandine> so that branch might not fix it for rtm either
[19:32] <pmcgowan> thats too bad
[19:32] <kenvandine> yeah... it's rather annoying :)
[19:33] <kenvandine> i just flashed my phone again doing a round of testing and still there :/
[19:38] <ahoneybun> has anyone gotten the red flashing leds?
[19:38] <ahoneybun> on the nexus 4
[20:33] <popey> ahoneybun: yeah, well known "battery dead" state.
[21:11] <mardy> dobey: hi! I'm back, for about 30 mins
[21:13] <dobey> mardy: i put my question in an e-mail in the thread since you didn't reply
[21:14] <mardy> dobey: saw it just now, I'm about to reply
[21:14] <ahoneybun> popey, are you saying I can just charge it back?
[21:15] <dobey> hmm, now my nexus5 seems to be working ok, without the sim, and after updating today
[21:22] <mardy> dobey: I sent the email
[21:23] <kenvandine> mandel, any progress?
[21:24] <mardy> dobey: if PayUI is treated as an ordinary app, it means that it will appear in the UbuntuOne account under the system settings
[21:25] <mardy> dobey: and the user will be able to disable it (then the next time that PayUI starts it will find no enabled accounts, and will use that Setup API to ask the user for the U1 account)
[21:25] <mardy> dobey: I don't find this undesirable, but I thought I'd better state it clearly
[21:26] <ahoneybun> popey, do I have to get a new device?
[21:27] <dobey> mardy: it's not desirable, in that it's not an ordinary app, and we want it to always have access to the account. but i would like to understand why exactly it's not happening that way right now. i suppose due to the fact that it's not an ordinary app, and doesn't have the .desktop file in ~/.local/share/applications/ ?
[21:27] <dobey> ahoneybun: have you tried charging it?
[21:28] <ahoneybun> dobey, left it charging for like 6-7 hours on the wall not pc
[21:28] <ahoneybun> it is on the wall now just blicking red
[21:28] <dobey> ahoneybun: and it won't turn on?
[21:29] <ahoneybun> I can get to the bootloader but can't get to the recovery
[21:29] <ahoneybun> and I can't reset it factory because it cant reboot into the bootloader
[21:30] <dobey> and if you unplug it from the wall, it just dies?
[21:30] <ahoneybun> without the wall I cant get it to go into anything (bootloader)
[21:30] <ahoneybun> nothing
[21:30] <ahoneybun> you have to hold the buttons and then plug it in to get to the bootloader
[21:31] <mardy> dobey: as I wrote in the email, to request permission to use an account (possibly involving the creation of a new account, if one doesn't exist yet) there is a special API
[21:32] <dobey> ok
[21:32] <mardy> dobey: but to use this API you also need a .service file, and that means that your app will appear under the U1 account
[21:32] <mardy> dobey: if you don't want that, the real solution is to add PayUi to the ACL when you create the U1 account
[21:32] <mardy> dobey: it's not a hack
[21:33] <mardy> dobey: either you do it this way, or you do it dynamically, and accept the fact that the user might disable it
[21:33] <dobey> mardy: i'd prefer to do it the way jdstrand suggested in his mail :)
[21:33] <mardy> dobey: but recovering from being disabled is not a single line of code more, so it's not troublesome
[21:34] <ahoneybun> I'm going to a local store to look at their phones dobey and I'm just going to leave it on the charger for some hours
[21:34] <dobey> having to maintain a list of things that can access an account, inside the account plug-in itself, is indeed a "hack"
[21:34] <dobey> ahoneybun: ok, yeah, sounds like maybe an issue with the battery. you could open it up and test the battery i suppose
[21:41] <pmcgowan> anyone know what was fixed in the latest  music app
[21:44] <mardy> dobey: maybe...
[21:45] <mardy> dobey: and if I proposed a MP to make PayUI bahave like a normal app, would you consider it?
[21:46] <mardy> dobey: for an example of how this looks like, you can look at reminders app (though that's even more complicated because it supports multiple accounts)
[21:46] <mardy> dobey: or, in fact, the dash
[21:48] <dobey> mardy: probably not. i was only considering the possibility that it would pop the allow/deny as a temporary means of annoyance to let us get the seed change in, but not something i'd want to keep there. it's an unconfined/trusted app and should always have access to that account
[21:51] <mardy> dobey: ok
[22:13] <comjf> Does anyone have a guide to flash ubuntu phone on the latest amazon phone hardware
[22:14] <comjf> considering it's only 100 dollars now, it makes great hardware to play with ubuntu-phone with
[22:18] <dobey> !devices | comjf
[22:29] <comjf> dobey: so the fact that it isn't listed there means that it's not possible. Am I reading that correctly?
[22:30] <comjf> IF I want to start work on porting it to that device, who do I work with?
[22:38] <dobey> comjf: it means you will need to port it, yes. well, it means you should probably check the XDA developer forums first
[22:38] <dobey> comjf: xda dev forums is probably the best place to get started on porting
[22:39] <dobey> there's some work happening for a new porting guide for ubuntu, but i don't think it's up yet
[22:39] <ahoneybun> dobey, I think I have to get a new phone
[22:39] <ahoneybun> I can get it to the bootloader at least but without recovery I dont know of a way to format it
[22:40] <dobey> ahoneybun: maybe contact google support to see if they can help you figure out what's wrong exactly
[22:40] <ahoneybun> dobey, not sure how
[22:41] <dobey> ahoneybun: first thing i'd do though, is open it up and try to test the battery to see if it's still good
[22:42] <ahoneybun> I don't think I have the tools
[22:42] <ahoneybun> I might have the screwdriver but not to take the case apart
[22:43] <dobey> looks like you need a very small torx driver, and a multimeter at least
[22:43] <ahoneybun> multimeter?
[22:43] <dobey> probably phillips too once case is opened
[22:43] <dobey> well you'd need a multimeter to measure the battery voltage
[22:44] <ahoneybun> oh
[22:47] <ahoneybun> dobey, I need a phone, so I might have to go the mall and get a cheap windows phone
[22:50] <dobey> ahoneybun: ah, well i have plenty of old phones lying around. so when some bug appears that's overly annoying and really gets in my way of using my phone, i can throw my sim in another phone and at least still have actual phone and stuff
[22:50] <dobey> but sure
[22:51] <ahoneybun> dobey, I do not have that, all the other phones are verizon as this is my first GSM phone and everyone else has verizon
[22:52] <dobey> ah
[22:52] <dobey> well, good luck
[22:52] <dobey> time for me to go to the pub :)