**** BEGIN LOGGING AT Fri Feb 02 03:00:05 2018 Feb 02 05:38:43 pottisumus: Thanks for the feedback. We'll have a look into this. We keep updating the back-end rendering engine (now at fairly recent Chromiim 56 based) while the original app code was for very old webkit Feb 02 05:39:05 So we needed to make some changes over time to the app code to keep things working. Could be this is one of those Feb 02 06:41:57 Morning! Feb 02 06:44:58 elvispre: morning! Feb 02 06:49:09 Herrie: So why was the first image broken yesterday? I mean what was the problem? Feb 02 06:49:14 elvispre: I guess you could pull a log a bit later Feb 02 06:50:24 Herrie: Yeah. Off to work in a minute. Feb 02 06:51:33 elvispre: Not sure... I just removed the # from fstab file for /firmware and put back the systemd system units Feb 02 06:51:38 I commented those out locally Feb 02 06:52:18 elvispre: I mean it seems the log you pasted yesterday was quite early on boot Feb 02 06:52:27 It still needs to start some other bits normally Feb 02 06:52:43 Herrie: I was too quick :) Feb 02 06:52:54 Yeah probably Feb 02 06:54:18 Herrie: I think blobs were in a folder called /system (rather than /firmware) under OxygenOS, so the systemd changes seem more likely to be the problem to me. Feb 02 06:55:11 I don't remember seeing a /firmware folder in the LineageOS fs either. Feb 02 07:06:02 elvispre: I guess there might not be one Feb 02 07:06:13 If it's /system we should be good too Feb 02 07:06:22 Since that one is anyway mounted I guess Feb 02 14:50:42 Here's a longer boot log from my onyx with Herrie's latest LuneOS image: https://paste2.org/tVj6akAf Feb 02 15:13:05 elvispre: It seems ti cannot mount your persist partition which should be on mmcblk0p14 :S Feb 02 15:31:59 elvispre: Seems that somehow system/lib still isnt there... Feb 02 15:32:03 So looking into that Feb 02 16:28:36 elvispre: Another try:P http://vve-goudenleeuw.nl/luneos-dev-package-onyx-20180202153807-0-0.zip Feb 02 18:48:09 Herrie: No adb access to the new image. Feb 02 19:03:24 elvispre: Seems I might have broken android-tools somehow. My mido is also quite random with adb Feb 02 19:03:59 You could try to reboot to twrp/cwm and pull the console-ramoops from there Feb 02 19:05:12 I'll try to cleanup my build again Feb 02 19:09:01 Herrie|Pre3: Still no /sys/fs/pstore folder, so no console-ramoops available Feb 02 19:09:13 weird Feb 02 19:09:34 You have twrp or cwm? Feb 02 19:09:42 twrp Feb 02 19:09:56 Could be you need to mount it in twrp Feb 02 19:10:07 I have twrp too Feb 02 19:20:27 Herrie: Rummaging in twrp with adb shell, I see I can mount /firmware (mmcblk0p1) and /persist (mmcblk0p14). Content of /firmware looks convincing. Feb 02 19:29:13 hmmz interesting Feb 02 19:34:37 Which twrp version? Feb 02 20:10:55 Herrie: twrp version 3.1.1-1 Feb 02 20:13:25 I can only find Android 5.1 fstab: https://github.com/TeamWin/android_device_oneplus_onyx/blob/android-5.1/recovery.fstab Feb 02 20:16:13 Herrie: /etc/fstab in twrp: https://paste2.org/3EhkChDP Feb 02 20:17:18 I can mount /firmware and mount /persist at that command line Feb 02 20:24:13 The LineageOS layout calls that /firmware partition "modem": https://pastebin.com/KVyw4sAY Feb 02 20:24:32 (Talking about onyx still) Feb 02 20:35:43 ok Feb 02 20:36:29 Well we have those in our fstab too: https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-oneplus/recipes-core/base-files/base-files/onyx/fstab **** ENDING LOGGING AT Sat Feb 03 03:00:01 2018