**** BEGIN LOGGING AT Tue Oct 17 03:00:03 2017
Oct 17 05:04:34 <Herrie> Morning!
Oct 17 05:05:06 <Herrie> Tofe: Look what just hit upstream ;) https://github.com/openembedded/openembedded-core/commit/28d2d47f2a4fc3eb649cf58e82bce0525ab0bc74
Oct 17 05:05:19 <Herrie> So a simple bump at our end in layers.txt will address it :)
Oct 17 05:13:45 <Tofe> Herrie: hehe, good :)
Oct 17 06:24:39 <MartinHov> Morning!
Oct 17 06:30:08 <MartinHov> Herrie: I see the testing dirs for qemux86 have been cleaned up (old bins have been removed) - but no new image available yet. Perhaps there was a disc space problem - which now might be solved
Oct 17 06:52:36 <Tofe> Morning:)
Oct 17 07:24:37 <Herrie|Laptop> Morning
Oct 17 07:25:03 <Herrie|Laptop> MartinHov: Yeah we ran out of space while rsync-ing so I deleted some files and restarted r-sync
Oct 17 07:27:22 <MartinHov> Herrie: thanks
Oct 17 07:40:32 <Herrie|Laptop> I just kicked off a new build with the wpa_supplicant fix ;)
Oct 17 08:48:02 <Tofe> Herrie|Laptop: I've had a look at our current bluez extension in luna-webappmanager, and a first arises: why don't we just use connman-qt5 instead of directly calling bluez?
Oct 17 08:48:07 <Tofe> +question
Oct 17 08:48:41 <Tofe> connman is supposed to be generic and handle bluez4 and bluez5, right?
Oct 17 08:48:52 <Herrie|Laptop> Tofe: Yes correct
Oct 17 08:48:57 <Herrie|Laptop> Well up to 1.32
Oct 17 08:49:03 <Herrie|Laptop> After 1.32 they dropped BlueZ4
Oct 17 08:49:07 <Tofe> yes right
Oct 17 08:49:32 <Tofe> but you see what I mean: we shouldn't bother calling bluez directly, when we already have a nice qt5 layer ready to use
Oct 17 08:50:26 <Tofe> in the same way, webos-connman-adapter seems dedicated to wifi, but for no good reason: as it calls connman, it could very well handle bluetooth as well
Oct 17 08:52:01 <Tofe> I don't know yet if it would help rewriting it using Qt5 and libconnman-qt5
Oct 17 08:52:03 <Herrie|Laptop> Tofe: I think webos-connman-adapter is there mainly to provide ls2 interface
Oct 17 08:52:21 <Herrie|Laptop> So apps can do certain luna-service calls
Oct 17 08:52:23 <Tofe> Herrie|Laptop: yes, and the latter could be used by settings too
Oct 17 08:52:39 <Herrie|Laptop> Tofe: Yes, but for QML we could use the qtconnman bits directly no?
Oct 17 08:52:51 <Herrie|Laptop> Without bothering about the webos-connman-adapter
Oct 17 08:52:56 <Tofe> yes correct
Oct 17 08:53:01 <Herrie|Laptop> We should see what API webos-connman-adapter provides
Oct 17 08:53:09 <Herrie|Laptop> I suspect it's mainly to check network status
Oct 17 08:53:11 <Tofe> but the webappmanager extension are just useless imho
Oct 17 08:53:28 <Herrie|Laptop> Some apps on legacy used to check networkstatus
Oct 17 08:54:06 <Tofe> Herrie|Laptop: is settings the only app that uses the webappmanager wifi and bluetooth extensions ? or do legacy apps also use it?
Oct 17 08:55:52 <Tofe> I'd rather extend the LS2 wifi API, add a similar bluetooth LS2 API, do it in webos-connman-adapter, and in the latter eventually use connman-qt5 if it helps (not sure about that)
Oct 17 08:56:12 <Tofe> and drop the webappmanager wifi & bt extensions
Oct 17 08:59:19 <Herrie|Laptop> Tofe: BT might be used in LNC
Oct 17 08:59:22 <Herrie|Laptop> Not sure about that
Oct 17 08:59:25 <Herrie|Laptop> But not by apps
Oct 17 09:00:47 <Tofe> Herrie|Laptop: https://github.com/webOS-ports/luna-next-cardshell/blob/master/qml/Connectors/BluetoothService.qml uses a directy DBus connection to bluez
Oct 17 09:00:52 <Herrie|Laptop> Tofe: OK
Oct 17 09:00:58 <Herrie|Laptop> Then it's Settings only
Oct 17 09:01:08 <Tofe> for the wifi, it uses LS2...
Oct 17 09:01:27 <Tofe> kind of a waste of energy here :) let's migrate all this to connman-qt5's QML
Oct 17 09:01:28 <Herrie|Laptop> There were some issues that nizovn mentioned in the past. He wasn't too happy with the plugin & qml variants
Oct 17 09:01:34 <Herrie|Laptop> They didn't always sync properly
Oct 17 09:01:36 <Herrie|Laptop> Or soemthing
Oct 17 09:02:15 <Herrie|Laptop> Tofe: I can scan legacy apps to see where they call com.palm.wifi and com.palm.connectionmanager
Oct 17 09:02:25 <Tofe> I just wonder why people avoided using connman for BT, it's a bit strange isn't it ?
Oct 17 09:02:25 <Herrie|Laptop> See what it's actually being used for in apps
Oct 17 09:02:33 <Herrie|Laptop> Do we really need extensive LS2 interface?
Oct 17 09:03:03 <Herrie|Laptop> Wouldn't it be easier to just directly use the connman-qt5 bits and only provide basic functionality via webos-connman-adapter?
Oct 17 09:03:11 <Herrie|Laptop> Should make it less prone for errors as well?
Oct 17 09:03:13 <Tofe> Herrie|Laptop: well, no, I mainly want to see if someone else uses the webappmanager extensions
Oct 17 09:03:18 <Herrie|Laptop> And less code to maintain ?
Oct 17 09:04:07 <Tofe> Herrie|Laptop: I agree, that's my target too
Oct 17 09:05:00 <Tofe> It's just that if we don't provide a LS2 API for BT, then the current settings app will definitely not work
Oct 17 09:05:26 <Tofe> Maybe it's just a matter of planning in the right order
Oct 17 09:07:12 <Herrie|Laptop> Tofe: I checked navigator.BluetoothManager and navigator.WifiManager on GitHub and only used by our Settings app
Oct 17 09:07:20 <Tofe> ok, that's good
Oct 17 09:08:34 <Tofe> Herrie|Laptop: currently we only have bluez4 installed in the image ? or both 4 & 5 ?
Oct 17 09:08:35 <Herrie|Laptop> I checked whole of GitHub, so there is nobody else using it somehow either
Oct 17 09:08:42 <Herrie|Laptop> Tofe: Only 4
Oct 17 09:08:49 <Herrie|Laptop> I don't think you can do 4 & 5 at the same time
Oct 17 09:08:53 <Tofe> ah ok
Oct 17 09:08:56 <Tofe> well well
Oct 17 09:09:16 <Tofe> then we'll have to migrate all this together
Oct 17 09:09:35 <Herrie|Laptop> JaMa offers: https://github.com/webOS-ports/meta-webos-ports/pull/245/commits/7bdd9634d5eacf289f4d4966ca7b19d6f05327d5
Oct 17 09:09:44 <Tofe> our current connman already has dropped bluez4 ?
Oct 17 09:09:56 <Herrie|Laptop> Tofe: Ehm let me check
Oct 17 09:12:16 <Herrie|Laptop> Tofe: Seems JaMa updated us to 1.33 so we're without BlueZ4 support already it seems, since last version is 1.31 with BlueZ4 support and there's no patch in our layer or oe-core to add BlueZ4 functionality back
Oct 17 09:12:31 <Herrie|Laptop> So I guess we could just switch to BlueZ5 and take it from there
Oct 17 09:12:53 <Herrie|Laptop> While we're at this, we might want to see if it makes sense to use mer's ConnMan
Oct 17 09:13:00 <Herrie|Laptop> Since we use their oFono & VoiceCall too
Oct 17 09:13:20 <Herrie|Laptop> And their qt connman bits too
Oct 17 09:13:51 <Tofe> Herrie|Laptop: if I understood correctly, sailfishos uses it and has a kind of frankenconnman with both bluez support
Oct 17 09:13:58 <Herrie|Laptop> Tofe: Correct
Oct 17 09:14:06 <Herrie|Laptop> They don't use upstream and have a ton of patches
Oct 17 09:14:11 <Herrie|Laptop> I'm not sure what's their reasoning
Oct 17 09:14:29 <Herrie|Laptop> Seems Slava Monich is doing a lot of commits & cherry picks
Oct 17 09:14:37 <Tofe> Herrie|Laptop: I'm not fond of "ton of patches" approach :p
Oct 17 09:14:52 <Herrie|Laptop> Tofe: Me neither, but they must have them for a reason probably
Oct 17 09:15:12 <Tofe> but they have a Bluetooth certification, so I guess that makes the transition to bluez5 more complex
Oct 17 09:16:25 <Herrie|Laptop> SailfishOS you mean?
Oct 17 09:16:38 <Tofe> yes
Oct 17 09:16:48 <Herrie|Laptop> Tofe: I'd say more the 3.4 hard kernel requirement
Oct 17 09:17:16 <Tofe> ah, yes, thatt's a good reason too :)
Oct 17 09:19:56 <Tofe> the main annoying this with connman is that it's nearly impossible to test out of a device
Oct 17 09:20:02 <Tofe> thing*
Oct 17 09:20:19 <Herrie|Laptop> Tofe: Yeah...
Oct 17 09:20:39 <Herrie|Laptop> Might be good to get in touch with Slava and figure out why they deviate so much from upstream ConnMan
Oct 17 09:21:08 <Herrie|Laptop> Might be valid reasoning. Just seeing we're using their oFono, VoiceCall etc, it might make sense to use their ConnMan too because they might interact better
Oct 17 09:21:33 <Tofe> could be
Oct 17 09:22:13 <Herrie|Laptop> But seems they're still on 1.31 for most part
Oct 17 09:22:17 <Herrie|Laptop> + tons of patches
Oct 17 09:49:32 <Tofe> Herrie|Laptop: https://bpaste.net/show/4d76fe696999
Oct 17 10:00:05 <Herrie|Laptop> Tofe: OK that's useful :()
Oct 17 10:00:07 <Herrie|Laptop> :)
Oct 17 10:03:59 <Herrie|Laptop> Seems quite some stuff made it to 1.35 as well
Oct 17 10:05:37 <Herrie|Laptop> Difficult call to make without testing...
Oct 17 10:27:16 <Herrie|Laptop> Tofe: There seems little specific for voicecall or ofono in Mer's ConnMan
Oct 17 10:28:10 <Herrie|Laptop> At least from what I can see here while scanning quickly
Oct 17 10:29:43 <JaMa> Herrie|Laptop: 2 more build failures http://errors.yoctoproject.org/Errors/Build/47549/
Oct 17 10:31:42 <Herrie|Laptop> JaMa: Seems that for the qtcharts you'll need your own patch :P https://patchwork.openembedded.org/patch/143142/
Oct 17 10:32:06 <Herrie|Laptop> Adopted for qtcharts of course :P
Oct 17 10:35:46 <Herrie|Laptop> Let me do a quick test for those 2
Oct 17 10:59:23 <Herrie|Laptop> JaMa: I added this one: https://github.com/webOS-ports/meta-webos-ports/commit/05e646ad1c5eaee913a5672033d20438fe7e626f
Oct 17 10:59:37 <Herrie|Laptop> I had errors while building clean
Oct 17 10:59:42 <Herrie|Laptop> This solves it
Oct 17 11:03:10 <JaMa> for which branch?
Oct 17 11:03:17 <Herrie|Laptop> JaMa: pyro
Oct 17 11:03:27 <Herrie|Laptop> For me clean build of Pyro wouldn't work somehow :S
Oct 17 11:03:30 <JaMa> it's included in oe-core/rocko
Oct 17 11:03:40 <JaMa> didn't you remove meta-systemd from your bblayers.conf?
Oct 17 11:04:36 <JaMa> I bet you did when testing some rocko build, but you should put it back as it provides this recipe and then revert this
Oct 17 11:04:36 <Herrie|Laptop> JaMa: I only touch layers.txt :P
Oct 17 11:05:00 <Herrie|Laptop> JaMa: I have separate folders on my machine for Rocko & Pyro
Oct 17 11:05:11 <JaMa> this is in webos-ports-setup/conf/bblayers.conf
Oct 17 11:05:12 <Herrie|Laptop> I.e. LuneOS\pyro and LuneOS\rocko
Oct 17 11:05:25 <JaMa> then check your bblayers.conf in those dirs
Oct 17 11:05:32 <JaMa> pyro should have meta-systemd
Oct 17 11:05:39 <Herrie|Laptop> JaMa: qtcharts and qtnetworkauth work for me now with: https://github.com/Herrie82/meta-qt5/commit/09280b5b89aad3e7782c7c3536ec18ceccd260e1 For the other 2 issues, these are not qt5 specific?
Oct 17 11:05:54 <JaMa> and it has ./meta-systemd/recipes-core/systemd/systemd-machine-units_1.0.bb
Oct 17 11:06:28 <JaMa> is this commit the same one you gave me yesterday?
Oct 17 11:06:38 <JaMa> od did you fix those 2 qt* related?
Oct 17 11:06:53 <Herrie|Laptop> JaMa: Yeah 1 SRCREV was wrong and added gold fix
Oct 17 11:06:54 <Herrie|Laptop> https://github.com/webOS-ports/webos-ports-setup/blob/testing/conf/bblayers.conf
Oct 17 11:07:00 <JaMa> ok
Oct 17 11:07:01 <Herrie|Laptop> That one doesn't have meta-systemd :P
Oct 17 11:07:19 <JaMa> it has, see line 20
Oct 17 11:08:09 <Herrie|Laptop> JaMa: Hmmzm weird
Oct 17 11:08:27 <Herrie|Laptop> Seems a local issue then
Oct 17 11:08:49 <Herrie|Laptop> I have 2 versions of bblayers.conf in my pyro folder which aren't equal :P
Oct 17 11:11:05 <Herrie|Laptop> Ok fixed that locally
Oct 17 11:11:13 <Herrie|Laptop> Will remove this from pyro then in meta-webos-ports
Oct 17 11:45:46 <Herrie|Laptop> Tofe: I guess we're OK to move to BlueZ5 then, since BlueZ4 is effectively not working anyway already?
Oct 17 11:46:00 <Tofe> Herrie|Laptop: that's a way to put it :)
Oct 17 11:46:18 <Tofe> Herrie|Laptop: I propose we stay on the same connman for the moment
Oct 17 11:47:29 <Herrie|Laptop> Tofe: Rocko offers 1.34
Oct 17 11:47:33 <Herrie|Laptop> We're on 1.33
Oct 17 11:48:24 <Herrie|Laptop> Changelog is at: https://01.org/connman/blogs/pflykt/2017/connman-1.34
Oct 17 11:49:44 <Tofe> Herrie|Laptop: there are minor fixes for bluetooth, but I don't anything necessary for now; and rocko isn't a good place to experiment yet, as it's less stable than pyro
Oct 17 11:49:56 <Tofe> +see
Oct 17 11:51:06 <Herrie|Laptop> 1.35 changes aren't that shocking it seems: https://01.org/connman/blogs/pflykt/2017/connman-1.35
Oct 17 11:51:30 <Herrie|Laptop> Tofe: Well we can just bump connman
Oct 17 11:51:39 <Herrie|Laptop> Without rest of Rocko
Oct 17 11:52:06 <Tofe> why not
Oct 17 11:53:12 <Herrie|Laptop> Seeing the number of fixes might be worth it
Oct 17 11:53:19 <Herrie|Laptop> Let me do a quick local build for connman to test
Oct 17 11:53:21 <Herrie|Laptop> And I'll PR it
Oct 17 12:01:12 <JaMa> I've bumped oe-core a bit for wpa security fixes and few other changes, new builds are in queue now
Oct 17 12:01:28 <Herrie|Laptop> JaMa: Thnx I did the same already for testing this morning
Oct 17 12:01:35 <Herrie|Laptop> Good to see it got onto OE so quickly :)
Oct 17 12:01:45 <Herrie|Laptop> Now the long wait for router patches :P
Oct 17 12:02:19 <JaMa> router isn't so important as the client devices
Oct 17 12:02:35 <JaMa> lets see how long until it's on the TVs :)
Oct 17 12:02:46 <JaMa> and e.g. roomba
Oct 17 12:03:26 <Herrie|Laptop> JaMa: I understood that both need patching, but clients are most critical
Oct 17 12:03:38 <Herrie|Laptop> And of course most Android devices won't receive an update as usual
Oct 17 12:03:51 <Herrie|Laptop> This is one of the few things Apple does right...
Oct 17 12:04:24 <JaMa> because Apple has only handful of devices to take care of
Oct 17 12:04:30 <Herrie|Laptop> JaMa: True ;)
Oct 17 12:04:46 <Herrie|Laptop> Google is catching up finally with the way they structure things
Oct 17 12:04:52 <Herrie|Laptop> Anyway our home is Apple free :P
Oct 17 12:05:06 <JaMa> our as well
Oct 17 12:05:20 <JaMa> gtg, bbl
Oct 17 12:14:05 <Herrie|Laptop> Tofe: I can get both 1.34 and 1.35 to build
Oct 17 12:14:11 <Herrie|Laptop> With 1.35 we can drop 2 patches :P
Oct 17 12:14:32 <Herrie|Laptop> https://github.com/openembedded/openembedded-core/blob/rocko/meta/recipes-connectivity/connman/connman/CVE-2017-12865.patch and https://github.com/openembedded/openembedded-core/blob/rocko/meta/recipes-connectivity/connman/connman/0001-firewall-nftables-fix-build-with-libnftnl-1.0.7.patch
Oct 17 12:49:33 <Tofe> Herrie|Laptop: but we have our own connman recipe already ?
Oct 17 12:49:47 <Herrie|Laptop> Tofe: So it's your call. Seeing 1.35 doesn't have much critical changes except for some CVE and minor things we could just as well do 1.35 right away and not be bothered for a while :)
Oct 17 12:49:59 <Herrie|Laptop> Tofe: No I'll take those from Rocko release and slightly adjust it
Oct 17 12:50:14 <Herrie|Laptop> And once Yocto gets to 1.35 JaMa will drop it again ;)
Oct 17 12:50:17 <Herrie|Laptop> That's how it works :)
Oct 17 12:50:26 <Herrie|Laptop> We have a .bbappend
Oct 17 12:51:01 <Herrie|Laptop> Currently version specific while it shouldn't be, so can address that by making it % instead of hardcoded version number
Oct 17 12:52:07 <Herrie|Laptop> I.e. we have connman_1.33.bbappend now, which should better be: connman_%.bbappend
Oct 17 12:52:15 <Herrie|Laptop> So we don't need to rename it every time connman is updated ;)
Oct 17 12:55:04 <Herrie|Laptop> The bbappend takes care of the patch for correct start order for systemd
Oct 17 12:55:16 <Herrie|Laptop> For the rest we use plain vanilla upstream connman
Oct 17 12:55:27 <Tofe> Herrie|Laptop: let's go to 1.35; but if we run into issues with pyro, then we rollback and do the bluez5 migration with our current working version
Oct 17 12:55:42 <Herrie|Laptop> With upstream I mean Yocto ;)
Oct 17 12:55:45 <Herrie|Laptop> Not ConnMan itself
Oct 17 13:09:26 <Tofe> https://github.com/libhybris/libhybris/pull/360 <-- nice !
Oct 17 13:11:43 <Herrie|Laptop> Tofe: Yeah!
Oct 17 13:19:54 <Herrie|Laptop> MartinHov: New image for you to play with :P
Oct 17 13:22:51 <MartinHov> Herrie: I've just seen this. downloading ..
Oct 17 13:25:33 <Herrie|Laptop> Tofe: I noticed we can drop our libconnman-qt5 as well since we have it in meta-qt5 now. I'll test this locally first and will drop it (rebuilding qtbase :P)
Oct 17 13:32:30 <Tofe> ok
Oct 17 13:43:24 <Herrie|Laptop> OK seems to build fine
Oct 17 13:48:29 <Herrie|Laptop> Tofe: https://github.com/webOS-ports/meta-webos-ports/commit/2a901a2b6c95e8e69eaea5747fb4484766d2fc18, https://github.com/webOS-ports/meta-webos-ports/commit/ea5a2903765b4c3814e4a80732089740c5485080 and https://github.com/webOS-ports/meta-webos-ports/commit/2c3f629bf442461efa3f1a3fc8a0f8bd1a0d63c7
Oct 17 13:49:52 <Herrie|Laptop> I kicked off a Hammerhead build locally
Oct 17 13:50:37 <Tofe> ok great, thanks
Oct 17 13:51:08 <Tofe> So next step is to be able to see bluetooth devices from a connmanctl shell
Oct 17 13:52:10 <Herrie|Laptop> Tofe: Yeah
Oct 17 13:52:26 <Herrie|Laptop> Well we might need to hook up our BT properly with the new Halium kernel
Oct 17 13:52:29 <Herrie|Laptop> Due to the Ubuntu bits
Oct 17 13:52:44 <Herrie|Laptop> They have backported BT stack from 4.2 kernel in 3.4 kernel for Mako & Hammerhead
Oct 17 13:54:19 <Herrie|Laptop> I mean start it properly
Oct 17 13:54:25 <Herrie|Laptop> But that shouldn't be rocket science really
Oct 17 13:54:33 <Herrie|Laptop> I.e. we have these patches in our kernel now: https://wiki.ubuntu.com/Touch/BluetoothEnablement
Oct 17 13:57:27 <Tofe> Herrie|Laptop: I'm not sure what they mean about the backports/driver part
Oct 17 13:57:45 <Herrie|Laptop> Tofe: Well they have basically backported the BlueZ BT stack from 4.2 kernel to 3.4 kernel
Oct 17 13:58:00 <Herrie|Laptop> Everything should work in general since it does for UBPorts/Halium
Oct 17 13:58:42 <Tofe> ok
Oct 17 13:59:25 <Herrie|Laptop> Tofe: I mean we might need to tweak something like: https://github.com/shr-distribution/meta-smartphone/blob/da5e96d9e49ce3a8803f1b85b9d79a410946f53e/meta-lg/recipes-core/systemd/systemd-machine-units/hammerhead/hcismd.service
Oct 17 13:59:34 <Herrie|Laptop> And https://github.com/shr-distribution/meta-smartphone/blob/da5e96d9e49ce3a8803f1b85b9d79a410946f53e/meta-lg/recipes-core/systemd/systemd-machine-units/hammerhead/hci-smd-enable.sh
Oct 17 13:59:44 <Herrie|Laptop> To get BT up, but that shouldn't be too hard really
Oct 17 14:00:47 <Tofe> yes it should be fine, I'll play with it tonight
Oct 17 17:05:42 <Herrie> Tofe: My local build is almost ready
Oct 17 17:05:54 <Herrie> Just another 22% of webengine
Oct 17 17:06:06 <Tofe> mine is still running, not even yet at qtwebengine...
Oct 17 17:27:35 <Herrie> Tofe: Well still need 15%, not very quick
Oct 17 17:35:09 <Tofe> Herrie: where is the documentation for the appinfo.json file?
Oct 17 17:44:10 <Tofe_> oops, the fuse went off...
Oct 17 18:19:04 <Herrie> Tofe: You got mail with specs
Oct 17 18:19:12 <Herrie> Or you're looking for something else?
Oct 17 18:19:16 <Tofe> yep, thanks!
Oct 17 18:19:47 <Tofe> no that was fine; I was looking at how to organize things for the settings app and the various sub-apps
Oct 17 18:28:47 <Herrie> OK build ready
Oct 17 18:28:54 <Herrie> When WiFi works things should be OK right?
Oct 17 18:29:19 <Tofe> right
Oct 17 18:29:55 <Herrie> I did a clean Google 5.1 install and our image works ;)
Oct 17 18:30:01 <Herrie> I mean in general with Halium bits
Oct 17 18:30:05 <Herrie> So no CM 12.1 ;)
Oct 17 18:30:20 <Herrie> DId that this morning
Oct 17 18:30:37 <Herrie> That was on a to-do list
Oct 17 18:30:38 <Tofe> ah, great idea!
Oct 17 18:30:49 <Herrie> Since my Hammerhead needed a fresh start anyway decided to do that
Oct 17 18:30:55 <Tofe> so we can now officially say it's fine :)
Oct 17 18:30:58 <Herrie> And back to CWM instead of TWRP
Oct 17 18:31:12 <Herrie> I like the adb sideload more compared to installing from SDCArd with TWRP
Oct 17 18:31:30 <Herrie> Also TWRP was flaky for me at times
Oct 17 19:01:33 <Herrie> Tofe: N% stuck @ Google logo :S
Oct 17 19:01:56 <Herrie> Building TP now
Oct 17 19:02:14 <Herrie> Doesn't seem to bootloop though :S
Oct 17 19:02:36 <Herrie> Could also just be my flaky N5
Oct 17 19:39:43 <DougReeder> Tofe, do you still need docs on appinfo.json?
Oct 17 19:45:06 <Herrie> DougReeder: I sent some by email
Oct 17 19:45:12 <Herrie> But if you have some more would be good
Oct 17 19:45:29 <Herrie> I found some link on Google Books about webOS and from WebOS Internals
Oct 17 19:45:32 <Herrie> + LG WebOS one
Oct 17 19:45:37 <Herrie> But I know there were more
Oct 17 20:02:40 <EricBlade1> docs? but we have the code! haha
Oct 17 20:05:06 <Herrie> EricBlade1: LOL
Oct 17 20:11:44 <DougReeder> The page on webostv.developer.lge.com is not very useful for us.
Oct 17 20:14:30 <DougReeder> My computer is in the shop for a week, so I can't send samples that show Just Type integration, etc.
Oct 17 20:15:04 <Tofe> Herrie: same here, my N5 doesn't boot completely. Android subsystem isn't even started.
Oct 17 20:15:28 <DougReeder> Tofe, which properties were you most interested in?
Oct 17 20:15:53 <Tofe> DougReeder: I wanted to know if we can pass parameters to a program through appinfo
Oct 17 20:16:40 <DougReeder> Hrm, I don't think so. What's the use case?
Oct 17 20:17:29 <Tofe> I'm looking at the alternatives to start the various "settings" sub-apps
Oct 17 20:18:17 <Tofe> so far what I have is several appinfo.json (of course), with appIds like "org.webosports.app.settings.wifi", which all start the same qml app; the latter will determine what page to show based on the appId.
Oct 17 20:18:17 <DougReeder> Just Type would read certain fields, do its search, then call the app with launxh parameters, but that's not a general mechanism.
Oct 17 20:19:30 <DougReeder> Well, that's why webOS had separate apps for settings.
Oct 17 20:20:33 <Tofe> DougReeder: I'm quite satisfied with the solution I have right now, so I'm not looking for appinfo fields anymore :)
Oct 17 20:20:43 <Tofe> Herrie: reflashing helped, now it boots
Oct 17 20:20:52 <DougReeder> It would be possible to have stub apps that just launch another app with parameters, but you'll all recall how slow luanching YouTube on the Touchpad was.
Oct 17 20:22:27 <Tofe> ah yes :)
Oct 17 20:22:50 <DougReeder> Ideally, launching an app would allow a path, as well as an app ID
Oct 17 20:23:28 <DougReeder> That's more aligned with the web platform.
Oct 17 20:24:19 <Herrie> Tofe: My Tenderloin image flashed, rebooting
Oct 17 20:25:43 <DougReeder> I do appreciate you're working on that.
Oct 17 20:27:13 <Tofe> DougReeder: :)
Oct 17 20:27:18 <DougReeder> s/you're/your/
Oct 17 20:28:30 <Herrie> DougReeder: I'd believe the code we have is a lot more straightforward and it should be less slow
Oct 17 20:28:52 <Herrie> We're also moving to QML based Settings app which will mean no more plugins to load for BT and WiFi so should load a lot quicker
Oct 17 20:32:17 <Herrie> TP made boot sound :P
Oct 17 20:32:20 <Herrie> Let me try wifi
Oct 17 20:34:04 <Herrie> Tofe: OK I'm missing topbar but that's something else
Oct 17 20:34:16 <Herrie> I bumped the dbus a bit
Oct 17 20:34:24 <Herrie> And now get module "org.nemomobile.dbus" is not installed
Oct 17 20:34:29 <Herrie> Which is due it being renamed
Oct 17 20:34:33 <Herrie> That should be an easy fix
Oct 17 20:34:43 <Herrie> the nemo-dbus I mean
Oct 17 20:36:40 <Tofe> ah, yes
Oct 17 20:38:11 <Herrie> That's something I did locally
Oct 17 20:38:15 <Herrie> You shouldn't have that
Oct 17 20:38:24 <Tofe> nope
Oct 17 20:39:07 <Herrie> I'll prepare some PR
Oct 17 20:39:11 <Herrie> For once I have it fixed
Oct 17 20:54:04 <Tofe> Herrie: I've managed to get a bluetooth device list on N5
Oct 17 20:55:10 <Herrie> Tofe :D
Oct 17 20:55:20 <Herrie> That seems like it's not too much work ?
Oct 17 20:55:29 <Tofe> it's ok :)
Oct 17 20:56:07 <Tofe> what I did was:
Oct 17 20:56:07 <Tofe> /usr/bin/hciattach ttyHS99 bcm43xx 4000000 flow sleep /persist/bluetooth/.bdaddr ; rfkill unblock bluetooth ;  hciconfig hci0 up
Oct 17 20:56:26 <Tofe> I also did " ln -s /system/vendor/firmware /etc/" previously, which I think helped a bit
Oct 17 20:57:24 <Tofe> So we'd need something a bit like https://github.com/mer-hybris/droid-config-hammerhead/blob/master/sparse/lib/systemd/system/hciattach.service
Oct 17 21:00:19 <Herrie> Tofe: OK I got the DBUS stuff working more or less. I have statusbar back
Oct 17 21:00:38 <Herrie> Just have this: Oct 17 16:58:31 tenderloin luna-next[1993]: INFO: 16:58:31.694: file:///usr/palm/luna-next/shells/card/qml/Connectors/BluetoothService.qml:45:5: QML DBusInterface: QDBusError("org.freedesktop.DBus.Error.UnknownMethod", "Method \"DefaultAdapter\" with signature \"\" on interface \"org.bluez.Manager\" doesn't exist\n")
Oct 17 21:00:47 <Herrie> Which I guess is BlueZ4->5
Oct 17 21:02:16 <Tofe> yep, exactly
Oct 17 21:04:29 <Tofe> one annoying thing is that connman doesn't look very receptive to the bluetooth devices
Oct 17 21:04:42 <Tofe> it can power it on&off, but that's mostly all about it
Oct 17 21:08:02 <Tofe> I begin to wonder if it's supposed to do more or not...
Oct 17 21:13:43 <Tofe> anyway, time for bed.
Oct 17 21:15:28 <Herrie> Tofe: Well connman doesn't do that much
Oct 17 21:15:42 <Herrie> Rest is mainly via dbus I think
Oct 17 21:15:45 <Herrie> Anyway good night
Oct 17 21:15:55 <Herrie> I'll prepare some PR's and will go to sleep too
Oct 17 21:26:23 <Herrie> OK PR's are in, 3 pieces
**** ENDING LOGGING AT Wed Oct 18 03:00:00 2017