**** BEGIN LOGGING AT Fri Jul 07 03:00:04 2017 Jul 07 16:26:43 Hello Jul 07 16:27:21 Very interested in potentially porting LuneOS to Moto G4 (athene), can LuneOS build from Lineage 14.1? Jul 07 16:34:30 thejsa: Hello! Jul 07 16:36:29 We never tried porting with a Lineage 14.1 base, so far we only got as far as CM 12.1. This really depends on the support of libhybris, which is still not complete for that Android version. CM13 would be ok though, I don't know if there's a build for that... Jul 07 16:36:44 I don't believe so Jul 07 16:36:52 There is AOSP 6.0, though Jul 07 16:37:09 In fact, the phone came stock with Marshmallow Jul 07 16:37:25 thejsa: ok, so that could be a possibility Jul 07 16:37:28 Tofe: random note: current libhybris works pretty well with androud 7.. ;) *hint**hint* Jul 07 16:37:39 bshah: oh, I'm so out-of-date :) Jul 07 16:38:31 thejsa: ok, so, considering that we'll move to Halium in the coming months, it could be a smart move to have Halium support working for Moto G4 as a first step Jul 07 16:38:39 we needed just this : https://github.com/Halium/libhybris/commit/58960ab7c1b0f80a9fa8af1b0b6258853cc163d2 Jul 07 16:39:03 bshah: haha (: Jul 07 16:39:16 bshah: looks like an easy PR Jul 07 16:39:31 I'll go look into Halium Jul 07 16:39:33 but .. well.. android parts is bit differnt story :p Jul 07 16:40:24 bshah: what is the most advanced version of Halium, apart Android 5.1 ? Jul 07 16:40:33 7.1 Jul 07 16:40:51 we have it working on Nexus 5X for instance .. and some more "exciting" devices Jul 07 16:41:06 bshah: it's == Lineage 14.1 ? Jul 07 16:41:20 Looks like a straight port according to https://halium.org/docs/Porting/ since there's an actively developed Lineage 14.1 tree (which I run right now) Jul 07 16:41:37 Tofe: yeah Jul 07 16:41:47 thejsa: ok, that good news there Jul 07 16:42:32 how much disk would you recommend I set aside for this (: Jul 07 16:43:06 need to get a ubuntu partition setup Jul 07 16:43:27 thejsa: quite a lot... And you need to build the Android bits too, let me count a bit Jul 07 16:44:42 would a 250GB disk be sufficient? Jul 07 16:46:22 that's quite too much Jul 07 16:46:24 :) Jul 07 16:46:43 That's good news, it's the biggest I have haha Jul 07 16:47:00 thejsa: For LuneOS build + Ubuntu install + Android build, you're about 100GB too much, but well that's fine ;) Jul 07 16:47:20 time to go clear out Windows 7 then Jul 07 16:47:21 For LuneOS we usually recommand 60GB Jul 07 16:47:54 wow.. 60 GB :O Jul 07 16:48:00 does it build skynet in it? Jul 07 16:48:13 bshah: qtwebengine, almost the same ;) Jul 07 16:49:01 Herrie: am I mistaken about the recommended size ? Jul 07 16:49:27 well........ IMO packages should not be built on porter's machiine Jul 07 16:49:54 bshah: ah, well yes, but it has also its pros Jul 07 16:50:05 hm? Jul 07 16:50:42 bshah: very easy debug and hacking, maybe Jul 07 16:51:26 bshah: trying out that patch for libhybris, yesterday, took me, what, 8 minutes Jul 07 16:51:46 sure.. it also takes me same time Jul 07 16:52:03 for plasma mobile.. I've CI building binary packages... and rootfs distributed Jul 07 16:53:05 We also have the possibility to have pre-built bits from our official distant build, but I disabled it, my intenet connection is slower than my CPU Jul 07 16:53:26 xD Jul 07 16:53:54 ah, for me it's definitely the other way around Jul 07 16:54:52 bshah: you have CI for all the branches of the devs ? Doesn't that take a lot of CPU ? Jul 07 16:55:49 On our side, we start a build on-demand, but we only have unstable,testing and stable builds, not a per-dev build Jul 07 16:56:46 thejsa: you'll be able to get the prebuilt bits with the default configuration, a-piori Jul 07 16:56:49 right.. well we also don't have per-dev build but I can do commit -> revert to temparary branch Jul 07 16:56:57 (I can't say I've tested that a log xD) Jul 07 16:57:37 Tofe: btw... any update on halium compatible rootfs for nexus 5? :P Jul 07 16:58:38 bshah: ah, I've been working too much on HP TP :p however that work can be at least partially reused for integrating Halium in the Nexus 5 build Jul 07 17:00:11 I'm beginning to think we maybe should delay too much our main release because of that device; but well, it's a device of great meanning for our core users :p Jul 07 17:03:16 well.. its "official" device as far as I understand right? Jul 07 17:03:22 yup Jul 07 17:03:50 But quite old now, and it becomes pretty hard to have a working system on it using up-to-date components Jul 07 17:04:15 maybe then keep old android stack on it? Jul 07 17:04:37 Not possible, we need a kernel >= 3.4 Jul 07 17:04:46 uhg Jul 07 17:04:50 Which only comes with a newer Android, afaik Jul 07 17:05:25 bshah: yes, that's a consequence of our last glibc upgrade Jul 07 17:06:02 well... you can build glibc with old kernel version header Jul 07 17:06:24 (maybe) Jul 07 17:06:35 what kernel version you got? Jul 07 17:06:44 I didn't try, but Herrie told me it didn't work Jul 07 17:06:47 We had 3 Jul 07 17:06:50 3.0 Jul 07 17:06:57 oh rip Jul 07 17:07:49 And for systemd I think we're far away from a supported kernel version, even with 3.4 :) Jul 07 17:24:38 bshah: do you think this strace extract is a good lead ? https://paste2.org/fhhapKtz Jul 07 17:25:08 I think... Jul 07 17:25:18 you can maybe look into hwcomposer source Jul 07 17:28:18 interesting, I think morphis got similar problems back in 2014 with CM11 Jul 07 17:28:20 http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2014-07-04.log.html Jul 07 17:29:13 let's try to patch the caf display... Jul 07 17:31:46 umm... if I understand your problem is at EGL side Jul 07 17:31:47 ? Jul 07 17:32:00 and display gets initialized correctly for you Jul 07 17:32:05 so you are well past that error Jul 07 17:33:12 http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2014-07-01.log.html it really looks like he stumbles upon the same behavior Jul 07 17:33:49 --> I get "Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted" ; also --> "however I only get one frame on the screen" Jul 07 17:34:06 ah right hm Jul 07 17:34:21 well, doesn't hurt to apply the patches we had on cm-11 Jul 07 17:39:42 Tofe: well.. sorry I can't really be of much help here... never had to deal with such errors or issues.. :/ Jul 07 17:40:16 bshah: no worries :) Jul 07 17:51:33 Tofe: 100GB isn't a luxury really Jul 07 17:51:51 60GB is on the tight side especially when you need to pull in 20GB of Android stuff + WebEngine ;) Jul 07 17:52:09 If you do multiple targets I would add 20-30 GB per target device Jul 07 17:52:26 right Jul 07 18:09:10 victory ! Jul 07 18:11:48 Tofe: So it's working now? Jul 07 18:11:53 I got our compositor to start, using the libEGL_android Jul 07 18:11:57 :D Jul 07 18:12:09 HP/Palm devices were specific with their frame buffers Jul 07 18:12:17 it's not using the native drivers, I'll have to try with them too Jul 07 18:12:18 They were different from Android from what I recall Jul 07 18:12:50 I think they were using dual while Android wasn't.. At least that's what I vaguely recall Jul 07 18:12:56 I think it's also buggy as hell Jul 07 18:13:12 Which you sometimes could see when a frame was stuck somewhere :P Jul 07 18:13:22 Tofe: It worked fine on webOS, just on Android it's weird Jul 07 18:15:12 we have now display + wifi, I think pulseaudio still has some little issues Jul 07 18:17:28 bluetooth works, that's a surprise Jul 07 18:17:52 orientation sensor ok Jul 07 18:18:07 basically just sound, I'd say Jul 07 18:22:08 oh wait, but it works too with hardware drivers Jul 07 18:22:11 that's great Jul 07 18:24:27 yup, great news! Jul 07 18:24:39 It's quite a releaf Jul 07 18:24:56 bshah: and by the way, it's using Halium, for most of it ;) Jul 07 18:26:30 Herrie: for pulseaudio that's most probably a kernel defconfig issue somewhere Jul 07 18:26:48 I'll just compare with mako or hammerhead Jul 07 18:28:36 Tofe: do you know if screencaptures are still black on TP? Jul 07 18:28:52 nizovn: didn't try Jul 07 18:29:06 ok Jul 07 18:29:29 I just remarked that TP doesn't get out of screen blanking Jul 07 18:29:44 nizovn: what's the shortcut for screenshots ? Jul 07 18:29:57 swipe to right on gesture area Jul 07 18:30:24 ah yes ofc Jul 07 18:35:17 working well Jul 07 18:35:37 good :) Jul 07 18:37:37 Tofe: we had issue on TP that unblanking screen could cause kernel panic sometimes (usually after volume switches or plug in/out usb cable) Jul 07 18:38:07 I think hardware keys are just not working, maybe I missed something in the defconfig Jul 07 18:39:04 ^ that issues should be solved with latest changes: https://github.com/shr-distribution/linux/commits/tenderloin/3.0/master Jul 07 18:49:55 Tofe: So in the end you needed to patch something in caf-display? Jul 07 18:50:56 Herrie: exactly Jul 07 18:52:39 Tofe: Ah OK :D **** ENDING LOGGING AT Sat Jul 08 03:00:00 2017