**** BEGIN LOGGING AT Thu Sep 05 03:00:58 2019 Sep 05 07:17:17 Morning! Sep 05 09:01:00 o/ Sep 05 12:29:51 Tofe: I saw this in mer-hybris: I'm not really sure how this is better v.s. patching the repos themselves and they seem to do it on an individual target basis :S https://github.com/mer-hybris/hybris-patches/commit/95b26af3fd625400094509f93c09202a9be4db38 Sep 05 12:55:47 Herrie: a bit more context for that repo. Some of the android devices don't come with open source BSP. *cough*mediatek*cough* Sep 05 12:56:39 so they try to apply these patches to that BSP tree Sep 05 13:07:32 Ah OK, we already had a solution for that in Halium as well, or at least in our LuneOS fork ;) Sep 05 13:07:46 Where we could apply device specific patches Sep 05 13:10:58 Yeah these are supposed to be those device specific patches.. Sep 05 13:11:23 when the BSP that the device vendor gives you is a 21 GB tarball of the whole android tree with no git history whatsoever :P Sep 05 13:21:52 "But, see, Android is OpenSource !" ... yeppee :) Sep 05 13:34:55 saidinesh5: It's almost like LG's webOS OSE release ;) Big code dump, no history LOL ;) Sep 05 13:37:01 Herrie: ohh .. didn't know that about their OSE. how's your integration work coming along with the OSE stuff they released btw? Sep 05 13:37:25 Tofe: lol. those vendors don't even release kernel sources.. crazy i tell you. Sep 05 13:54:13 saidinesh5: Yeah they just dropped their initial release without any history, so we had to do a lot of trial and error ;) We're about 1/2 way I'd say ;) https://webos-ports.org/wiki/LuneOS-webOS-OSE_Migration_Status Sep 05 14:00:31 Ha! " 159431973 chromium68 OSE version of webos webengine based on chromium v68 New Very Hard Not started " Sep 05 14:02:32 how come they used chromium instead of relying on the chromium from Qt WebEngine though? Sep 05 14:02:41 isn't it more work? Sep 05 14:04:18 bah IRC/quassel/freenode/ihavenocluewhatitis Sep 05 14:05:05 saidinesh5: Well there's a whole story behind it, since they were stuck @ Qt 5.6 but needed newer Chromium they didn't use QtWebEngine Sep 05 14:05:13 Also in terms of optimizations etc Sep 05 14:05:32 Now they signed partnership with Qt and seems they'll be going Qt 5.9/5.12 Sep 05 14:05:55 But their approach is interesting, also for us. We might migrate at some point to their webapp stack Sep 05 14:06:10 But it's not an easy swap probably Sep 05 14:06:20 Seeing how deeply it's integrated into the OS Sep 05 14:06:27 webapp what? O_O Sep 05 14:07:03 also yeah i heard about that partnership.. but does that mean they will goback to QtWebEngine again? Sep 05 14:07:04 Well the webapp manager basically. That takes care about the lifecycle of the webapps such as the ones written in Enyo 1.0/2.0 and Enact 1.0/2.0/3.0 Sep 05 14:07:22 Ahh right. You guys expose something with QtWebChannel right? Sep 05 14:07:27 saidinesh5: I'm not sure... I THINK they are happy with their own Chromium ;) Sep 05 14:07:48 Yeah we have some patches on top of QtWebEngine to make things work, but it's not that heavy anymore nowadays Sep 05 14:08:16 I.e. https://github.com/webOS-ports/meta-webos-ports/tree/warrior/meta-luneui/recipes-qt/qt5/qtwebengine and https://github.com/webOS-ports/meta-webos-ports/tree/warrior/meta-luneui/recipes-qt/qt5/qtwebengine/chromium Sep 05 14:12:52 Yep I remember reading these ones a while ago while trying to port luneos to my tablet Sep 05 14:13:09 (Which still is a WIP.. as real life has been chaotic last few months) Sep 05 14:20:16 saidinesh5: I know the feeling ;) Sep 05 14:23:53 Herrie: which device are you trying to port to? Sep 05 14:24:44 Nothing specific at the moment ;) Just trying to get oFono to work on Android 7.1 and trying to get some Halium 8.1 off the ground (without much luck so far) Sep 05 14:24:54 Ahh Sep 05 14:24:56 oFono works on Hammerhead with 7.1 Sep 05 14:25:10 Just real life always gets in between me and projects :S Sep 05 14:25:12 Nice! didnt know hammerhead devices still work in the wild Sep 05 14:25:22 Yup they do ;) Sep 05 14:25:35 my cancro (similar guts as hammerhead) .. died after the battery expanded inside the case Sep 05 14:25:37 I did a quick Halium 7.1 port, just to be able to test oFono ;) Sep 05 14:26:13 Because on Tissot (Xiaomi A1) the calls just don't work (probably due to Qualcom QMI RIL) Sep 05 14:28:21 Ahh. there's also a mainline kernel for that device now right? Sep 05 14:43:36 Well this was still with 3.4 kernel Sep 05 15:04:53 saidinesh5: yes, a mainline kernel for hammerhead is also in the pipe; it still needs some more work though, as it's not as stable as I would like Sep 05 15:17:47 Ahh Sep 05 15:29:38 along that line - i wanted to ask - what are the 'system requirements' to be able to run luneos, etc. on a particular phone, e.g. gpu, etc. Sep 05 15:33:29 for example, if someone has a Motorola Droid 4, Nokia N9, etc. Sep 05 15:34:03 i didn't find any info regading this on the wiki, but I'd give it a second look in case i missed something Sep 05 15:37:25 sicelo: basically, either A) a mainline-compatible device with a decently recent kernel, or B) if there is a lineageos 14.1 build, and a 3.18 kernel, we're fairly sure a port will be possible Sep 05 15:38:11 A is pretty rare of course... Sep 05 15:38:48 sicelo: 3.4 could work as well, but will require a bunch of patches ;) Sep 05 15:38:58 droid 4 qualifies to some extent for (A) Sep 05 15:39:04 But we do have it working on a number of devices Sep 05 15:39:07 what are the gpu requirements? :) Sep 05 15:39:22 Herrie: yes, but I didn't want to raise false hopes :) Sep 05 15:40:39 Spec wise it's actually pretty similar to our HP Touchpad: https://www.gsmarena.com/motorola_droid_4_xt894-4418.php and https://www.gsmarena.com/hp_touchpad-3839.php Sep 05 15:41:01 Things will run, but not very quickly with 1GB of ram. Though things can be improved with some tweaks such as ZRAM and overclocking the CPU I guess Sep 05 15:41:19 Older Palm devices used TI OMAP CPU's as well and they were pretty OK to overclock Sep 05 15:41:39 sicelo: for A, any GLES 2 gpu will do, as long as it's supported by Mesa Sep 05 15:42:56 i think the GPU is where droid 4 completely fails .. powervr and mainline don' play well with each other. hanks for the info Sep 05 15:46:07 What's the codename for the Droid 4? Sep 05 15:47:33 maserati Sep 05 15:47:52 here is LOS14.1 for it Sep 05 15:47:56 *there Sep 05 15:48:15 Well you could try with that to port... Shouldn't be rocket science using Halium hopefully ;) Sep 05 15:48:57 kernel is 3.0.8 Sep 05 15:49:39 Ah wait, yeah that's problematic :( Sep 05 16:15:26 i htink this kind of info should have a place somewhere in the wiki Sep 05 19:00:04 sicelo: Yes it should. Well mostly we're based off Halium nowadays for Android bits, but it would be good to add some requirements yes. **** ENDING LOGGING AT Fri Sep 06 03:00:56 2019