[00:34:50] *** Quits: Horwitz (~mich1@p200300EC9BFE1700022268FFFE64E7C4.dip0.t-ipconnect.de) (Ping timeout: 276 seconds)
[00:47:03] *** Joins: Horwitz (~mich1@p200300EC9BC29E00022268FFFE64E7C4.dip0.t-ipconnect.de)
[00:47:03] *** ChanServ sets mode: +o Horwitz
[04:09:38] *** Joins: xenos1984 (~xenos1984@2ace-c3f6-3225-3c91-d480-87c4-07d0-2001.dyn.estpak.ee)
[04:09:38] *** ChanServ sets mode: +v xenos1984
[04:38:15] *** Joins: udovdh (~udovdh@2001:981:a812:0:213:3bff:fe0f:9fb1)
[08:11:18] *** Quits: udovdh (~udovdh@2001:981:a812:0:213:3bff:fe0f:9fb1) (Remote host closed the connection)
[11:41:25] *** Quits: Number6 (~number6@188-141-23-134.dynamic.upc.ie) (Quit: Lost terminal)
[11:48:32] *** Joins: Number6 (~number6@188-141-23-134.dynamic.upc.ie)
[11:48:32] *** ChanServ sets mode: +o Number6
[12:52:48] *** Joins: jandegr (d5db8ebb@213.219.142.187.adsl.dyn.edpnet.net)
[12:52:48] *** ChanServ sets mode: +v jandegr
[16:25:16] <kazer> hi there
[16:26:06] <kazer> jandegr: i've had issues with the 4.0.3 tablet and stf, i've opened a bug : https://github.com/openstf/stf/issues/1105
[16:56:57] <jandegr> kazer I tried to use it a few times, so I already noticed trouble :)
[16:58:03] <jandegr> in the issue it migth be usefull to specify you 3 working devices
[16:58:20] <jandegr> maybe the issue relates to older devices ?
[16:58:45] <jandegr> do you have other older devices you can test ?
[17:30:34] <ilovekiruna> hi kazer
[17:30:47] <ilovekiruna> hi jandegr
[17:30:54] <ilovekiruna> jandegr, how old do you need?
[17:31:09] <kazer> jandegr: no other older device than the 3 phones, although i think that i have another tablet just like this one somewhere
[17:31:40] <kazer> ilovekiruna: we have a phone with os 5.1.1 / sdk 22 working in stf
[17:31:48] <ilovekiruna> kazer: i think it is slowly time to think about FOSDEM again
[17:32:08] <ilovekiruna> I think I should have a phone with ICS and Lollipop
[17:32:21] <kazer> the tablet with 4.0.3 / sdk 15 is not working (no remote screen control possible although stf claims to support > sdk 9 )
[17:34:06] <jandegr> ilovekiruna , as I have discussed with Kazer before, Navit claims to work from android 9 upwards
[17:34:38] <jandegr> and we just suppose it will work on anything below 16 or so, because of too little testing
[17:34:40] <ilovekiruna> jandegr, you mean sdk 9, right?
[17:34:48] <jandegr> ah, yes
[17:35:14] <jandegr> so the oldest I have here is 16 or so
[17:36:08] <jandegr> and avd's for the lower sdk's are not practical
[17:36:19] <ilovekiruna> with my oldest, I have 14 or 15
[17:36:27] <Navit> <jkoan> I can also chack for the oldest device I have
[17:36:36] <ilovekiruna> at least this is what ice cream sandwich seems to be related to these two
[17:36:38] <Navit> <jkoan> *Check
[17:37:24] <jandegr> jkoan I suppose you have the oldest device with your 9 or 10 tablet
[17:37:45] <Navit> <jkoan> Sdk ==9 needed? Or which one do you need?
[17:38:14] <jandegr> brings us to a related issue
[17:38:32] <jandegr> you reported an issue with filebrowseractivity on your tablet
[17:39:11] <jandegr> you said is is android 2.3 but it would be intersting to know if it is 9 or 10
[17:40:07] <jandegr> btw , minsdk in Navit is now set at sdk 9
[17:41:13] <jandegr> I'm sure you all understand my point about what minsdk says and what we actually test on
[17:42:15] <jandegr> btw Kazer has 22, 26 and 28 on STF
[17:43:03] <jandegr> I have 16, 17 and marshmallow (23 or so ?) as real devices
[17:43:16] <Navit> <jkoan> Okay, I will try to look this up. Can't say if I manage it today
[17:44:04] <kazer> yeah hopefully we can find older devices and confirm that 9 is still fine
[17:44:22] <jandegr> and I test on avd's 19, 21 and 28 (the 29 one does not yet work here)
[17:45:00] <jandegr> kazer I would be fine with bumping from 9 to 10 according to the outcome of what jkoan's tablet is
[17:45:45] <Navit> <jkoan> Not lower it? ^^
[17:46:42] <jandegr> jkoan not lower for the regular gradle build, that is made to comply with all google playstore rules
[17:46:57] <jandegr> lower than 9 is armeabi, not supported by google anymore
[17:47:13] <kazer> what about f-droid?
[17:47:28] <jandegr> don't go into the dungeons kazer
[17:47:36] <jandegr> we face the real world
[17:47:45] <jandegr> because we can
[17:48:12] <jandegr> ok, but maybe for such a legacy build on that droid
[17:50:41] <kazer> so i found the other tablet i have, also 4.0.3. same issue
[17:50:47] <kazer> haha jandegr 
[17:51:33] <jandegr> really ? :)
[17:51:56] <jandegr> same brand and model, or just same sdk ?
[17:54:36] <kazer> same brand and model yeah
[17:56:30] <jandegr> kazer I want to test on that 123456789ABCDEF
[17:57:04] <jandegr> a secret prerelease version?
[17:58:42] <Navit> <jkoan> I remember a openstf issue with the same serial, there it was a cheap Chinese device
[18:12:21] <jandegr> I was hoping on a primeur instead :)
[18:12:56] <kazer> jandegr: don't get excited it's just one of the tablet that failed to install the stf component :)
[18:13:29] <kazer> i think that it's a spoofed serial, until it can pull the actual serial from the device
[18:15:19] <Navit> <jkoan> Kazer, probably this helps? https://github.com/nikosch86/stf-poc/blob/master/fix-lava-iris.txt
[18:16:05] <Navit> <jkoan> Sometimes I noticed that adbd on old versions could be buggy, but every time ela reboot helped
[18:17:40] <jandegr> kazer have you treid connecting yourself with adb to that tablet ?
[18:17:45] <jandegr> tried
[18:33:09] *** Quits: jandegr (d5db8ebb@213.219.142.187.adsl.dyn.edpnet.net) (Remote host closed the connection)
[18:36:59] <ilovekiruna> kazer, apart from the issue with sdk, what do you think about fosdem?
[18:43:31] <kazer> ilovekiruna: i think that it'd be great to have you there. We could use the money from opencollective to help with your expenses a bit. have a talk topic in mind?
[18:43:49] <kazer> jkoan interesting let me try
[18:52:58] <kazer> jkoan: no luck
[18:53:21] <Navit> <jkoan> :(
[19:08:27] <kazer> let me know if you can think of another trick :)
[19:09:02] <Navit> <jkoan> Currently not :(
[19:15:25] <kazer> we'll figure it out :)
[19:16:20] <ilovekiruna> kazer: I have two/three ideas
[19:16:28] <ilovekiruna> but wanted to discuss
[19:16:36] <ilovekiruna> one could be our openstf installation
[19:17:01] <ilovekiruna> another one i thought about evaluating FOSS smart assistants which we could use for a speech interface
[19:17:09] <kazer> yep this was my idea as well. stf itself was easy, but we could talk about how we'd hook this up to circleci
[19:17:26] <kazer> > FOSS smart assistants
[19:17:32] <kazer> have an example handy?
[19:17:48] <ilovekiruna> lucida, susi ai , mycroct
[19:17:51] <ilovekiruna> mycroft
[19:17:55] <ilovekiruna> kalliope
[19:18:10] <ilovekiruna> for speech recognition, mozilla deep speech
[19:18:35] <ilovekiruna> deadline for main track talks is 8th of Nov
[19:18:54] <ilovekiruna> lightning talks 22nd of Nov
[19:19:16] <ilovekiruna> probably geospatial devroom somewhen also in Nov
[20:13:05] <ilovekiruna> but i have to admit, I need to test them thoroughly
[20:13:17] <Navit> <jkoan> @KaZeR @ilovekiruna jandegr: my devices: dev_1569873246:[ro.build.version.sdk]: [16] dev_1569873271:[ro.build.version.sdk]: [10] dev_1569873289:[ro.build.version.sdk]: [16] dev_1569873328:[ro.build.version.sdk]: [16] dev_1569873369:[ro.build.version.sdk]: [16] dev_1569873399:[ro.build.version.sdk]: [16] dev_1569873499:[ro.build.version.sdk]: [10] dev_1569873517:[ro.build.version.sdk]: [10]
[20:13:21] <ilovekiruna> so fare I just had an own test with susi ai, which is still pretty rudimentary
[20:15:28] <Navit> <jkoan> Not sure, but this should be what i have. One device missing becaise it dosent charge with micro usb,instead it uses a dc jack. Bit this one should have android 4
[20:16:05] <Navit> <jkoan> I am quite surprised that they are only sdk 10 and 16
[20:16:18] <Navit> <jkoan> Ah, and my Oneplus 3t is of course missing
[20:18:00] <ilovekiruna> jkoan: what do you think about FOSDEM+
[20:18:02] <ilovekiruna> ?
[20:18:26] <ilovekiruna> should I present sth? how do you like my ideas?
[20:21:19] <ilovekiruna> kazer: could I also use addtional translations of navit for hacktoberfest?
[20:21:26] *** Quits: extor (~extor@unaffiliated/extor) (Remote host closed the connection)
[20:21:54] *** Joins: extor (~extor@unaffiliated/extor)
[20:23:10] <Navit> <jkoan> I think openstf as a follow up could be a good idea if we manage to build a full cloud
[20:24:14] <Navit> <jkoan> So that we can accaccess Kazer as well as my devices at the same time
[20:24:43] <ilovekiruna> i hope till then I can also add my implementation based on rpi
[20:25:39] <Navit> <jkoan> But only client with openvpn, right? This would be the same plan as mine
[20:25:52] <ilovekiruna> ofc
[20:26:03] <ilovekiruna> however, first i need to get a base install compile
[20:26:05] <ilovekiruna> automatically
[20:34:20] *** Quits: tryagain (~quassel@217.107.194.18) (Remote host closed the connection)
[22:28:29] <kazer> ilovekiruna: i tested mycroft some time ago, it was also a bit rudimentary at the time. definitely worth revisiting though
[22:28:43] <kazer> ilovekiruna: yep translations totally qualify for hacktoberfest
[23:00:18] *** Quits: xenos1984 (~xenos1984@2ace-c3f6-3225-3c91-d480-87c4-07d0-2001.dyn.estpak.ee) (Quit: Leaving.)