[08:51] <oSoMoN> Mirv, thanks for https://code.launchpad.net/~timo-jyrinki/webbrowser-app/fix_qt56_qdoc_move/+merge/290830 , I commented on it
[08:58] <Mirv> oSoMoN: likewise
[10:19] <oSoMoN> Mirv, FYI: https://code.launchpad.net/~osomon/webbrowser-app/fix-tabsmodel-ut-qt56/+merge/290862
[10:25] <ogra_> hmpf ... using an external BT kbd i cant really change the layout (seems system-settings always resets itself after the initial selection)
[10:34] <Mirv> oSoMoN: \o/
[13:00] <ogra_> does anyone know where the config for the external keyboard gets stored by system-settings ?
[13:00]  * ogra_ cant change the mapping
[13:08] <ogra_> mzanetti, Saviq, does either of you know ?
[13:09]  * ogra_ would really like to be able to type an "at", a tilde or pipe sign on the external kbdbut apparently teh german layout that is selected now doesnt have alt-gr support :P
[13:12] <mzanetti> ogra_, accountsservice apparently
[13:12] <mzanetti> org.freedesktop.Accounts.User
[13:12] <mzanetti> InputSources
[13:12] <ogra_> ok
[13:13] <ogra_> i guess that i cant change it after the forst selection is a bug :)
[13:13] <mzanetti> you cant change it any more?
[13:14] <ogra_> i have 5 german layouts ... i cant change the order or remove anything ... if i re-open settings it is back to teh five (with "german (macintosh)" selected as default)
[13:50] <dobey> crikey, it's only been an hour since my phone has been off the charger, and it's already lost 11% of the battery charge :(
[15:23] <_hc> hello all, ogra_ sent me here to check in about our (Debian Android Tools Team) new packages for adb, fastboot, etc.  we've stuck to what upstream supports, so they are currently only built on amd64 and i386.  The android-tools source package was ported to build on all Debian archs, including ARM.  we're not porters and we're only on amd64, but we'd love to see these new packages include the porting patches from the android-tools sou
[15:32] <homa> hi my friends
[15:35] <ogra_> ondra, morphis, see _hc above ...
[16:11] <ondra> _hc ogra_ hmm strange, adroid-tools defo build fine on arm, I think one part adbd does not build on mips, but that's only limitation I'm aware
[16:12] <ogra_> ondra, this is about the debian packages ... they use a different source (to produce the same binaries ...)
[16:13] <ogra_> you could theoretically limit ours to adbd and nobody would have to bother with maintaining the desktop side (as we could just regulary sync from debian)
[16:13] <ondra> ogra_ if they use different source then I can't help much. What we have is also deb, it's same as android-tools you ported
[16:14] <ogra_> right
[16:14] <ondra> ogra_ we need our fstools
[16:14] <ogra_> ah
[16:14] <ondra> ogra_ but you can argue we don't really need adb or fastboot, since they can be takes from AOSP anyway
[16:14] <ogra_> well, _hc was asking in #ubuntu-devel ... seems the debian packages are just getting synced to ubuntu
[16:14] <ondra> ogra_ we don't modify it in any way
[16:15] <ogra_> ubuntu-device-flash uses adb and fastboot
[16:15] <ogra_> as well as phablet-shell
[16:15] <ogra_> and teh autopilot tests
[16:15] <ogra_> afai they all depend on teh bainary packages
[16:15] <ondra> ogra_ but no reason they cannot use AOSP build adb and fastboot
[16:15] <ogra_> all i know is that our binary packages have added udev rules to recognize the ubuntu devices
[16:16] <ogra_> ondra, sure, if you want to package that :P
[16:16] <ondra> ogra_ so it's more dependency to make sure there is adb on the machine, but binary wise it could be as well clean aosp build
[16:16] <ondra> ogra_ no thank you :P
[16:16] <ogra_> heh
[16:17] <ondra> ogra_ I think we should be able to keep updating it now, it's relatively clean now, we do minimum changes on top of AOSP code
[16:17] <ogra_> remember we are talking about endusers that possibly want to recover a broken device ... cant really bother them to do a native AOSP install for that
[16:17] <ondra> ogra_ so I can once in a while rebase it to latest AOSP
[16:17] <ogra_> so there need to be packages
[16:17] <ondra> ogra_ yeah agree that step "install Android studio" to recovery Ubuntu phone sounds bad
[16:18] <cwayne> popey, happy birthday!
[16:18] <ogra_> it would be less work for us to have the debian ones .. but they would have to cover all arches and add our udev rules
[16:18] <ogra_> _hc, would that be possible ?
[16:19] <popey> thanks cwayne :)
[16:19] <ogra_> anyway, i'm just the messenger here, all up to you guys :)
[16:19] <ogra_> popey, hey old fart ... happy birthday !
[16:19] <ondra> ogra_ to be honest, now it's not much work anymore, I set makefiles way that adb and fastboot compile clean without any change, just drop aosp code in
[16:20] <ondra> popey happy birthday mate!
[16:20] <ondra> ogra_ messenger who knows more than receiving party :P
[16:20] <ogra_> ondra, sure, all up to you, we just have duplicated binary packages now
[16:21] <ogra_> (i doubt thats an issue though)
[16:21] <ogra_> (the debian ones are slightly differently named)
[16:21] <plars> ondra: around?
[16:22] <_hc> ondra: ogra_: we built the whole SDK close to how Google builds it.  It should be possible to port all the packages to ARM, its just a matter of finding the bulid issues and fixing them.  ANd keep in mind, Google doesn't build adb, fastboot, etc on anything but amd64 and i386
[16:22] <ondra> ogra_ happy to drop adb and fastboot then, if we know debian ones are kept up to date
[16:22] <plars> ondra: havin some trouble with the new udf/adb and rc-proposed - it seems to install ok, but can't adb to the device after. It just shows up in 'unauthorized' state
[16:23] <ondra> _hc so I did build abd and fastboot on arm, from android-tools
[16:23] <_hc> ondra: if you are happy with adb and fastboot only on amd64/i386, you can drop android-tools-adb and android-tools-fastboot now
[16:23] <_hc> ondra: I imagine why it builds easy for you is that the android-tools package just took the source code needed for those exact binaries
[16:23] <_hc> we're building the libs
[16:24] <_hc> and linking to them
[16:24] <ondra> _hc I don't have arm desktop, so not a problem for me, but may be somebody else?
[16:24] <_hc> someone from linaro was complaining loudly that our pacakges do not support ARM, let me dig up the reference
[16:24] <ondra> plars are you sure you have latest u-d-f?
[16:24] <ondra> _hc yeah I only picked to compile code needed for adb and fastboot
[16:25] <plars> ondra: 0.33-0ubuntu1~xenial-staging - is that correct?
[16:25] <plars> ondra: pulled from the sdk ppa
[16:25] <plars> ...for trusty, oddly enough
[16:26] <plars> I'm guessing it's just a copy of the xenial package, but then I had to get some of the deps from the snappy-dev ppa, because they were missing
[16:26] <ondra> plars you can check by running $ u-d-f touch -help
[16:26] <ondra> plars do you see there --adb-keys=?
[16:26] <plars> ondra: yes
[16:26] <ondra> plars and did you do u-d-f --bootstrap?
[16:26] <plars> ondra: yes
[16:27] <ondra> plars because you need to make sure you have latest recovery on the device
[16:27] <ondra> plars what device?
[16:27] <plars> ondra: it's actually a job that alesage is running, as well as others who have devices in ci
[16:27] <plars> ondra: krillin so far, I don't know if anyone has tried arale or others yet
[16:27] <plars> alesage: was that also a krillin you confirmed this on at home?
[16:27] <ondra> plars so I'd say, try to re-run it once more, to make sure you are using right recovery
[16:28] <alesage> ondra where can I find the right recovery
[16:28] <ondra> alesage if you run it once, you have it now installed
[16:28] <plars> ondra: is there a new recovery we need to use during the bootstrap? normally we need to specify an old on with --recovery-image
[16:29] <ondra> alesage it's always issue with ota, which needs latest recovery, we don't have process there to install recovery and then reboot to do rest of ota
[16:30] <ondra> plars alesage right recovery should be in the rc-proposed device tarball, but when you  run u-d-f, you would typically use old recovery already installed on the device
[16:30] <_hc> ondra: here's the disussion https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817823
[16:30] <ubot5`> Debian bug 817823 in ftp.debian.org "RM: android-libcutils android-libcutils-dev android-liblog android-liblog-dev [arm64 armel armhf mips mips64el mipsel powerpc ppc64el s390x] -- ANAIS; old binaries in architectures not allowed anymore" [Normal,Open]
[16:30] <ondra> plars alesage let me test krillin here, I did run u-d-f on it this morning, so it has "supposedly" latest recovery
[16:39] <ondra> plars alesage yeah re-run it pls, I just run it here ( with --wipe --developer-mode) and it's pre-authorised
[16:40] <plars> ondra: it looks like he was running this in the job I can see:
[16:41] <plars> ubuntu-device-flash touch --serial=JB010894 --channel=ubuntu-touch/rc-proposed/bq-aquaris.en --device krillin --developer-mode --password=0000 --recovery-image /var/lib/jenkins/slaves/krillin-02/workspace/ust_rc-proposed_krillin_sanity_PT/recovery.img --wipe --bootstrap
[16:41] <ondra> plars right so there is the issue
[16:41] <plars> ondra: what's that?
[16:41] <ondra> plars  /var/lib/jenkins/slaves/krillin-02/workspace/ust_rc-proposed_krillin_sanity_PT/recovery.img
[16:41] <plars> ondra: that's the old recovery image used for flashing
[16:41] <plars> ondra: you said that was ok, right?
[16:41] <ondra> plars I bet you this recovery has no adb-key provisioning support
[16:42] <plars> ondra: indeed, it certainly would not
[16:42] <ondra> plars that is good to flash, but it will not provision adb-keyts
[16:42] <plars> ondra: so we need a new recovery, that is not locked down
[16:42] <plars> ondra: where can we get such a thing from?
[16:42] <ondra> plars then sorry for confusion, you need new recovery
[16:43] <ondra> plars you want just new recovery with adb enabled?
[16:43] <plars> ondra: yes
[16:43] <ondra> plars if you do not need adb, you can just unpack it from latest device tarball
[16:43] <plars> ondra: no, I need adb
[16:43] <ondra> plars otherwise john-mcaleely build new one with adb enabled
[16:43] <ondra> plars let me look for it
[16:43] <davmor2> ondra: please give it to john-mcaleely to replace his version so all the documentation we have spread all over the universe is still correct many thanks
[16:43] <plars> ondra: nobody can touch these devices easily
[16:44] <ondra> davmor2 he already did, I just need to find it :)
[16:44] <davmor2> ondra: I assume the same place
[16:45] <ondra> davmor2 plars http://people.canonical.com/~jhm/barajas/recovery-krillin-5891faa.img
[16:45] <davmor2> oh ugly names
[16:45] <ondra> davmor2 plars and vegeta http://people.canonical.com/~jhm/barajas/recovery-vegetahd-5891faa.img
[16:45] <ondra> davmor2 I think that's git hash
[16:47] <davmor2> ondra: oh hang on john-mcaleely has already been wonderful the time stamps on the recovery-krillin.img are the same as the 589.... version I assum that means he has updated it
[16:50] <davmor2> ondra: same md5sum too :D
[16:51] <ondra> davmor2 yep, he's very organised! :)
[16:54] <plars> ondra: do you have one for arale?
[16:54] <ondra> plars nope, you will have to ask alextu
[16:54] <plars> alesage: want to rekick your job with that new recovery image?
[16:55] <ondra> plars yeah there is none on his people page
[16:56] <plars> ondra: ack, thanks
[17:01] <mariogrip> mhall119: ping
[17:06] <ogra_> ondra, _hc, i for one use armhf devices a lot for flashing other devices (and with convergence there will likely be more people doing that) ... so armhf should be done at least
[17:07] <ondra> ogra_ which when you spin it around means arm64, since there won't be that many arm32 anymore.....
[17:07] <mariogrip> popey: btw, I have a bq devices that is not in use atm, I could set it up as a Marvin device if that's possible
[17:07] <ogra_> arm64, powerpc or s390 are probably not that important (though please leave the packages arch: any, so if someone wants to port he can pick up there)
[17:07] <mhall119> mariogrip: pong
[17:08] <ogra_> ondra, well, if my testing broker is a raspberry pi 2 i wont run arm64
[17:09] <mariogrip> mhall119: are we having the call today, or move it to Wednesday when kees have time?
[17:09] <ogra_> and thinnking about it we might want/need fastboot on arm64 for snappy in case we do a local flash of bootloader bits
[17:09] <mhall119> mariogrip: we can do both if you have any updates for today, otherwise we can just move it to wednesday
[17:12] <mariogrip> mhall119: I have nothing major news since last call
[17:13] <dobey> mariogrip: you got bt working? ;)
[17:13] <mariogrip> Portcraft got kernel support, oneplus x got wifi and oneplus one got battery/heat fixes
[17:13] <mariogrip> dobey: awww, sorry not yet :(
[17:14] <ogra_> ondra, so thinking about it i think we should just keep our existing packages even if that measn some cuplication
[17:14] <ogra_> *duplication
[17:14] <dobey> mariogrip: ooh, battery/heat fixes? wonder if they are also applicable to n5? battery has been really bad as of late for me, and the phone always seems excessively hot
[17:16] <mariogrip> dobey: Yeah, it seems like it's the android side that is killing the battery (same as oneplus one), so I'll try if it works on n5 also
[17:16] <dobey> cool
[17:16] <dobey> i hope it does :)
[17:19] <mhall119> mariogrip: I'll go ahead and move it
[17:20] <mariogrip> mhall119: ack
[17:26] <mariogrip> mhall119: does skype work on linux?
[17:27] <mariogrip> mhall119: http://www.omgubuntu.co.uk/2016/02/skype-for-linux-group-calls-need-to-update-issue
[17:27] <dobey> mariogrip: should, but possibly not the latest version
[17:28] <davmor2> dobey: iirc the latest version is not compatible with the version currently available for linux there was a big hoohar about it
[17:28] <dobey> davmor2: right
[17:29] <mariogrip> yeah, i guess we can join, but can we join if someone has windows?
[17:29] <dobey> so the linux version "works" but it doesn't "work"
[17:29] <dobey> mariogrip: if they use the really old version of skype that matches the linux version, i guess it would be fine
[17:29] <mhall119> mariogrip: no idea
[17:29] <mhall119> I hope they can do hangouts
[17:29] <dobey> but if they have latest skype on osx/win, i guess it will cause problems
[17:29] <mariogrip> yeah
[17:30] <dobey> hangouts at least does work on pretty much everything though
[17:30] <mariogrip> Skype should make an html5 version
[17:31] <mariogrip> or open there api
[17:31] <dobey> good luck with getting MS to do that :)
[17:31] <mariogrip> they "love" linux now, so why not :P
[17:32]  * davmor2 points dobey to all the recent mit stuff they have been releasing stuff under, and points out this is mostly because they make more suing android builders than making windows
[17:33] <dobey> davmor2: uhm; "all the recent mit stuff" ?
[17:33] <dobey> you mean mono? which was originally under MIT anyway?
[17:34] <dobey> pretty sure IE is not MIT licensed :)
[17:34] <mariogrip> speaking about android, how about runnin the android skype client on chrome with ARC
[17:34] <dobey> go for it
[18:00] <dobey> anyone else notice that ssh (over wifi) to the phone is incredibly slow?
[18:03] <dobey> seems a bit faster with screen unlocked though
[18:13] <dobey> hmm, or just while the screen stays on even
[19:25] <_hc> ogra_: ondra: we're happy to accept patches to get all the Android Tools Team packages running on any arch, we just don't have the time or resources to do it ourselves
[19:28] <plars> ondra: I did see this fly by in recovery.log as it was installing: "Keyring doesn't exist: device-signing"
[19:28] <plars> ondra: here's a full log: https://www.irccloud.com/pastebin/buVavnCX/
[20:03]  * dobey hopes mariogrip's opo battery fix is applicable to n5 too
[20:06] <mariogrip> dobey: :)
[20:07] <dobey> mariogrip: have you had a chance to try it?
[21:29] <mariogrip> dobey: not yet