**** BEGIN LOGGING AT Thu Oct 19 03:00:02 2017
Oct 19 05:20:51 <Tofe> EricBlade: it means it's likely we could; to be sure, it should be in the libhybris suppored list, and have a 3.4+ kernel. In the end it's Halium that's going to be built, so anyway the first thing to do is to check if they already had it working or not on that device
Oct 19 05:23:10 <Tofe> EricBlade: https://github.com/Halium/docs/blob/master/supplementary/device_overview.md https://wiki.merproject.org/wiki/Adaptations/libhybris
Oct 19 06:04:37 <Herrie|TP> EricBlade: Any device you have in mind?
Oct 19 06:04:46 <Herrie|TP> Morning BTW
Oct 19 10:22:26 <MartinHov> Morning!
Oct 19 10:22:59 <MartinHov> FYI - latest http://build.webos-ports.org/luneos-testing/images/qemux86/luneos-dev-emulator-qemux86.zip has 404 Not Found
Oct 19 10:23:30 <MartinHov> perhaps new builds have failed for this platform qemux86*
Oct 19 10:37:02 <Herrie|Laptop> MartinHov: We ran out of space again
Oct 19 10:37:48 <Herrie|Laptop> I'll have a look at that later today
Oct 19 10:49:06 <MartinHov> ok - fine
Oct 19 10:52:08 <Herrie|Laptop> I'm already running a workspace cleanup for testing, stable & unstable
Oct 19 10:52:12 <Herrie|Laptop> That might free some space already
Oct 19 13:50:37 <Herrie> MartinHov: Started new build
Oct 19 14:40:18 <Herrie> [15:50] <+Herrie> MartinHov: Started new build
Oct 19 16:14:04 <Herrie> nizovn: ping
Oct 19 16:16:11 <nizovn> Herrie: pong
Oct 19 16:20:32 <Herrie|Laptop> nizovn: Any thoughts on the BlueZ5 migration? We're looking into QtConnectivity specifically QtBluetooth currently to replace the C++ Settings plugin the QML rewrite of Settings
Oct 19 16:24:11 <nizovn> Herrie|Laptop: i have no objections; i don't know if it's easy to port, someone just needs to try
Oct 19 16:29:17 <Herrie|Laptop> nizovn: Well we need BlueZ5 anyway so the C++ one would need updating
Oct 19 16:29:35 <Herrie|Laptop> It might make more sense to drop the BT and WiFi C++ plugins and do it in QML directly
Oct 19 16:29:48 <nizovn> yes
Oct 19 16:30:22 <nizovn> but i'm not sure it can be done in qml completely
Oct 19 16:30:34 <Herrie|Laptop> I guess we might potentially replace the bits in LNC as well with QtBluetooth, but that's to be seen still
Oct 19 16:32:33 <nizovn> yes, dbus api (used in LNC) probably will change as well
Oct 19 16:39:22 <Herrie|Laptop> nizovn: Yeah slightly
Oct 19 16:39:28 <Herrie|Laptop> But it are direct dbus calls
Oct 19 16:39:36 <Herrie|Laptop> So we can always use those :)
Oct 19 16:39:43 <Herrie|Laptop> For pretty much anything where we need dbus
Oct 19 16:40:35 <Herrie|Laptop> Tofe will be trying QtBluetooth, should cover quite some of what we need, if not more even :) http://doc.qt.io/qt-5/qtbluetooth-overview.html
Oct 19 16:41:01 <nizovn> ok, good
Oct 19 16:43:03 <Tofe> my first tries were quite positive, but I'll definitely have to try on device :p
Oct 19 16:43:28 <Tofe> I was thinking about migrating LNC to QtBluetooth, and see it that works
Oct 19 16:44:11 <Tofe> I'm just not sure the QML API handles the eventual authentification handshake
Oct 19 16:49:17 <Herrie> Tofe: http://doc.qt.io/qt-5/qml-qtbluetooth-bluetoothsocket.html
Oct 19 16:49:33 <Herrie> That to me suggest it does offer that?
Oct 19 16:50:18 <Tofe> Not sure... If the other party wants a code ?
Oct 19 17:35:48 <EricBlade> Tofe: according to that page, Halium doesn't work on very much of anything?
Oct 19 17:37:20 <Tofe> EricBlade: I failed to parse your sentence :)
Oct 19 18:20:16 <EricBlade> Herrie: hmm.. threw out a bid on a couple of phones, i probably won't get them.. checking to see what they were
Oct 19 18:20:55 <EricBlade> Tofe: That page lists N7 2013 GSM, Moto G 2014, and Sony Xperia Z
Oct 19 18:22:14 <Tofe> EricBlade: which one ?
Oct 19 18:22:25 <Tofe> Halium's ?
Oct 19 18:22:29 <EricBlade> Tofe: the one you linked me to about what Halium supports
Oct 19 18:24:43 <Tofe> ah ok I see; this list is not very accurate though. N4 and N5 are not marked as working (but it is), for instance
Oct 19 18:25:04 <Tofe> also I know Nexus 5X begins to work reasonably well
Oct 19 18:26:37 <Tofe> Overall, if the libhybris page says it's fine, then we can be reasonably confident about Halium.
Oct 19 18:27:35 <Tofe> But it might be necessary to do the Halium port, if it hasn't been done yet.
Oct 19 18:28:19 <EricBlade> none of these list touchpad .. :)
Oct 19 18:28:40 <Tofe> ... for instance :)
Oct 19 18:29:31 <Tofe> but that one I guess we'll have to handle it ourselves anyway
Oct 19 18:29:58 <EricBlade> so, Lune TP is still using LineageOS/Cyanogen ?
Oct 19 18:30:40 <Tofe> No no, I migrated it to Halium too; but it doesn't mean the Halium guys will maintain the device-specific stuff
Oct 19 18:31:24 <Tofe> It just means we can build the Android (i.e. Halium) part in the same way as any other Halium port
Oct 19 18:32:50 <Tofe> So if Halium fixes a but in the generic Android infrastructure, we'll have it too for TP
Oct 19 18:32:56 <Tofe> a bug*
Oct 19 18:35:15 <EricBlade> everything got harder for me to understand. :-D maybe easier to work with, though, i don't know.  Say I have a random device from the hybris list (which also doesn't include TouchPad, so are there other non-documented devices?) .. what would generally be involved with porting?
Oct 19 18:40:03 <Tofe> porting would mean: 1. first ask in #halium if there's already something unofficially running 2. if not, then take the CM 12.1 kernel, device and vendor files and simply try to build Halium with it. 3. once the Halium build is fine, then add the device in our meta-smartphone and meta-webos-ports layers, adding the various little pieces for that device (luna-platform.conf, fstab...)
Oct 19 18:40:36 <Tofe> EricBlade: you can consider that Halium 5.1 == minimal build of CM 12.1, if that helps understanding
Oct 19 18:41:34 <Tofe> (and yes I should ask the hybris&halium guys to add Touchpad to the lists)
Oct 19 18:44:30 <Tofe> There are many devices that could be fairly easily ported today; but I don't want to do it myself, as I wouldn't have the time to maintain it afterwards. However, I can help anyone who wants to give it a try :)
Oct 19 18:48:01 <Herrie|Laptop> EricBlade: There's a bigger list at: https://docs.halium.org/en/latest/supplementary/device_overview.html
Oct 19 18:48:41 <Herrie|Laptop> Their table is funny though
Oct 19 18:49:33 <Herrie|Laptop> Once Halium is running, technically the port should be really straightforward
Oct 19 18:49:41 <Tofe> Herrie|Laptop: it's the same list, it just doesn't show up nicely on the website
Oct 19 18:49:50 <Herrie|Laptop> Tofe: Ah oK
Oct 19 18:50:34 <Herrie|Laptop> EricBlade: Halium is basically Ubuntu Touch, Plasma Mobile, Mer/Sailfish/Jolla and LuneOS joining forces on the commonly used bits
Oct 19 18:50:44 <Herrie|Laptop> So we don't keep reinventing the wheel
Oct 19 18:50:55 <Herrie|Laptop> We can use the Halium kernels directly in our build now
Oct 19 18:51:06 <Herrie|Laptop> They accepted our GCC 5/6/7 and other specific patches
Oct 19 18:51:13 <Tofe> yup. And also the guys that really know Android work on the Android stuff, so it's more efficient :)
Oct 19 18:51:15 <Herrie|Laptop> So we don't maintain it ourselves anymore
Oct 19 18:51:49 <Herrie|Laptop> Their GitHub repo has some more clues as to which devices are actively being worked on: https://github.com/halium
Oct 19 18:53:12 <EricBlade> so the devices that i might end up with are ZTE Maven 3.  i saw there *might* be Lineage for it.  In any case, it's a decent looking phone that has Android 7 stock, and they are cheap .. and my Nexus 5's are running dead
Oct 19 19:05:46 <Herrie|Laptop> Some Motorola or Xiaomi would be nice targets too
Oct 19 19:06:11 <Herrie|Laptop> Seeing they have 3.10 and/or 3.18 kernels mainly they could potentially run stuff like www.anbox.io ;)
Oct 19 19:07:56 <Tofe> EricBlade: ok - mmh, hard to tell then. It's not yet in the list of libhybris devices, and it uses a Snapdragon 210 which apparently was never tested before. You say there might be a LineageOS for that device ?
Oct 19 19:44:19 <EricBlade> there might be
Oct 19 19:44:57 <EricBlade> i more saw the current bid of $5 on an auction on them and decided to throw out a bid on them, just to see what they are, on the offchance i win.  i probably won't, though, but my $7 bid is still good for now :-D
Oct 19 20:28:15 <Herrie|Laptop> MartinHov: New image to play with ;)
Oct 19 20:28:27 <Herrie|Laptop> I cleaned up the disk a bit and started a new build earlier this afternoon
Oct 19 20:28:34 <Herrie|Laptop> They were now rsynced and are available
Oct 19 20:28:48 <Herrie|Laptop> No real changes for qemux86 are expected currently
Oct 19 20:30:38 <MartinHov> Herrie: thanks. I will try it a bit later .. // Is there anything specific to test for this build ?
Oct 19 20:38:02 <Herrie|Laptop> Not really ;) There will be some interesting things soon
Oct 19 20:38:16 <Herrie|Laptop> MartinHov: Are there any specific features that you would need for a daily driver :P ?
Oct 19 20:38:20 <Herrie|Laptop> Just wondering
Oct 19 20:38:28 <Herrie|Laptop> I would need VPN myself for example
Oct 19 20:42:44 <MartinHov> no - not really something I urgently would need.  Anyhow after playing around with emulator I would like start testing Nexus4 and RPI-3 in few weeks.
Oct 19 20:43:30 <Herrie|Laptop> N4 image is broken for now, but should be back working in a couple of days
Oct 19 20:43:30 <MartinHov> for emulator I wonder if there is an option to adjust screen size to my max laptop resolution ?
Oct 19 20:43:46 <Herrie|Laptop> You can play with virtualbox settings maybe?
Oct 19 20:43:56 <Herrie|Laptop> Or change a .conf file in the image maybe?
Oct 19 20:44:23 <MartinHov> ok - I never looked at that before .. I'll have a look
Oct 19 20:50:30 <Herrie|Laptop> There's some luna.conf I think
Oct 19 20:50:36 <Herrie|Laptop> That sets it to 1024*768
**** ENDING LOGGING AT Fri Oct 20 03:00:01 2017