**** BEGIN LOGGING AT Mon Feb 08 03:01:12 2021 Feb 08 06:10:18 Morning Feb 08 06:10:38 Tofe: New images prepared and sent for Volla & Sagit. Let's see what they get back with Feb 08 06:10:44 Always good to test on more devices Feb 08 07:26:28 morning Feb 08 07:30:10 Herrie: I didn't test much on the usual 3.18, I hope I didn't break adb there Feb 08 07:30:36 (Morning! Feb 08 07:30:37 ) Feb 08 09:51:01 Tofe: ADB works on Sagit I got confirmation Feb 08 09:51:09 So now we'll debug why it doesn't boot LuneOS further Feb 08 09:51:16 Can at least pull journal and logcat easily now Feb 08 09:51:25 So that will probably give some clues Feb 08 09:51:36 On Volla it also seems to work better Feb 08 09:51:43 Though no final confirmation yet Feb 08 10:17:27 Tofe: I'll try on my 3.18 Tissot ;) Feb 08 10:34:02 ok, that's great :) Feb 08 13:21:41 Tofe: Sagit works, however LXC Android container fails to start Feb 08 13:21:51 Probably because Sagit used cust as vendor Feb 08 13:22:04 I've asked for output of mount and df -h Feb 08 13:22:07 Anything else that could help? Feb 08 13:31:28 This is the fstab: https://github.com/SailfishOS-sagit/android_device_xiaomi_msm8998-common/blob/hybris-16.0/rootdir/etc/fstab.qcom#L8 Feb 08 13:34:31 dmesg could help; one easy fix for the moment is to remove this cust entry from fstab and retry; or we could try to filter it out in halium's init script Feb 08 13:36:48 I have dmesg Feb 08 13:37:01 Well journal Feb 08 13:37:15 https://paste.ubuntu.com/p/F69prRdKN9/ Feb 08 13:37:57 lsblk: https://paste.ubuntu.com/p/nt9Hr6vYBv/ Feb 08 13:38:09 I see "mounting android system image (/tmpmnt/system.img) ro, in /android-system (system mode)" ==> it's not system-as-root Feb 08 13:38:24 It should be really Feb 08 13:38:26 Let me check Feb 08 13:38:26 which is fine, but then we have : cat: can't open '/android-system/boot/android-ramdisk.img': No such file or directory Feb 08 13:38:40 maybe it's just the naming ? Feb 08 13:39:55 https://github.com/UbuntuTouch-sagit/android_device_xiaomi_msm8998-common/blob/halium-9.0/BoardConfigCommon.mk#L41 Feb 08 13:40:10 what about the .bb recipe Feb 08 13:40:13 So should be system-as-root Feb 08 13:40:17 Let me check Feb 08 13:40:55 I should add? ANDROID_SYSTEM_IMAGE_DESTNAME = "android-rootfs.img" Feb 08 13:41:00 yes Feb 08 13:41:01 That's what we have for Tissot Feb 08 13:41:03 Ah OK :) Feb 08 13:41:31 Let's try that Feb 08 13:41:34 we're not yet able to determine this automatically; that would require mouting the image, and it's probably not worth it Feb 08 13:42:06 Tofe: OK Feb 08 13:42:10 We'll I'll rebuild simply Feb 08 13:42:12 Quick enough Feb 08 13:42:22 P.s. I'm in the Telegram group you forwarded Feb 08 13:42:22 yes, it's really just a name convention Feb 08 15:03:38 Sagit boots Feb 08 15:16:16 UI is there, you mean ? Feb 08 16:01:08 Yes Feb 08 16:01:15 Power button doesn't work though Feb 08 16:01:21 Is that this one? https://github.com/webOS-ports/meta-webos-ports/blob/gatesgarth/meta-luneos/recipes-webos/nyx-conf/nyx-conf/rosy/nyx.conf Feb 08 17:17:47 Herrie: yes, there's this one, and if touchscreen doesn't work it's in luna-next/environment.conf Feb 08 17:25:31 Ok Feb 08 17:25:41 And how to monitor again for the keys? Feb 08 17:53:48 just "cat /dev/input/eventX" Feb 08 18:15:02 Tofe: seems power button long press activates power menu but short press doesn't turn off screen Feb 08 18:17:20 that's weird Feb 08 18:17:42 could be the backlight path is incorrect in the cmake nyx conf file ? Feb 08 18:23:47 mmm maybe not, I don't see any specific path there Feb 08 18:53:19 Tofe: nothing really weird there but volume down works, up not Feb 08 18:53:25 Weird stuff a bit Feb 08 18:53:40 Could be newer kernel somehow or some ubports patches they did to device tree Feb 08 18:53:50 I took ubports one, not los for this Feb 08 18:54:00 That might be part of the cause Feb 08 19:36:01 Damn, I can't get lineage-16 to install correctly Feb 08 19:36:08 I'm always getting a black screen Feb 08 20:07:16 Tofe: Hmmz weird Feb 08 20:07:19 With me it boots Feb 08 20:14:32 I can have a look tomorrow in my backup folder which one I used Feb 08 20:40:06 In the meantime, I just wanted to have a look at dmesg from lineageos 16, to compare a bit Feb 08 20:40:30 so if it boots for you, and you can retrieve that, that's all I need :p Feb 08 20:40:58 but it's still strange yes. And I'd like to figure out if we're really using a matching kernel/device couple **** ENDING LOGGING AT Tue Feb 09 03:00:29 2021