**** BEGIN LOGGING AT Sun Feb 25 03:00:05 2018 Feb 25 05:54:17 elvispre: Weird that the firmware mount doesn't work. That seems to be the biggest problem for now. Feb 25 05:55:03 When looking at the CM/LineageOS ones seems they have the persist before the firmware in fstab as per https://github.com/LineageOS/android_device_oneplus_onyx/blob/cm-14.1/rootdir/etc/fstab.qcom#L16 Feb 25 05:57:56 You might want to try to push this fstab file instead: https://raw.githubusercontent.com/shr-distribution/meta-smartphone/48caf979eeee924808368c503cb618ae048afe17/meta-oneplus/recipes-core/base-files/base-files/onyx/fstab Feb 25 07:49:23 Morning! Feb 25 07:51:39 Morning! Feb 25 08:19:54 Herrie|Laptop: That does not change anything. systemd p1 and p14 ".device /start" even still time out in the same order as before. Feb 25 09:07:43 elvispre: Morning & hmmz Feb 25 09:07:44 Weird Feb 25 09:53:19 Tofe: I came across this one: https://github.com/mer-hybris/droid-config-mako-12.1/blob/0330a101f24a64b04d34b8989816f3a4f4525b37/sparse/var/lib/environment/compositor/droid-hal-device.conf#L13 Feb 25 09:53:29 We don't seem to set it, not sure we need it but guess we might? Feb 25 09:53:55 https://github.com/mer-hybris/qt5-qpa-hwcomposer-plugin/blob/bb95d09b893761c25409363e15f7048739c436ba/hwcomposer/hwcomposer_backend_v11.cpp#L122 Feb 25 12:02:36 Herrie|2: but do we know if that is the problematic point ? It's easy to try, so let's try for mido, but for the others, as long as it works, let's keep it as is Feb 25 16:39:56 Tofe: No clue, why it's there for Mer... Can ask the guys if and when it should be there.... Feb 25 16:40:02 This one is also interesting: https://github.com/mer-hybris/droid-config-mako-12.1/commit/015077108b5cb08b7d89a525c1997bba66ff548a Feb 25 16:40:27 I think this might help on mido? I recall I saw that it wouldn't detect the size? Feb 25 16:48:41 I guess I could try to force a size to see if that does something Feb 25 16:52:50 Tofe: I haven't seen this one recently: http://issues.webos-ports.org/issues/1213 You? Feb 25 16:56:58 Herrie: no didn't see it latetly, but I wouldn't be surprised if it's still there Feb 25 16:57:13 If it's fixed though, it's for the best Feb 25 16:59:05 For the physical size patch, well, it's easy to try too. Though I doubt it would lead to a crash. Feb 25 17:00:27 I'm currently looking at a possible migration path to halium-boot; at least partially, i.e. reusing their initrd script Feb 25 17:05:02 Tofe: Yeah I saw your messages in #halium Feb 25 17:05:11 Tofe: It might solve some issues here and there Feb 25 17:05:22 Though most of our Yocto stuff is pretty stable as well Feb 25 17:05:31 elvispre: Might have found a cause for your issues Feb 25 17:05:41 https://lists.freedesktop.org/archives/systemd-devel/2015-September/034204.html Feb 25 17:06:08 Yes, that's why I would like to keep our toolchain for generating the image to sideload Feb 25 17:06:55 Seeing we build everything with new GCC gives some performance improvements too Feb 25 17:07:01 GCC 4.x is really outdated Feb 25 17:07:52 Some things are nice on their side, like reusing android's system.img directly with a loop-mount Feb 25 17:08:18 And all the Android setup looks quite mature Feb 25 17:08:24 Tofe: Yeah some of their bits might enable multirom etc well Feb 25 17:09:33 Any less fiddling for new targets is welcome ;) Feb 25 17:10:15 We'll see what compromise is the best in our case. Less fiddling with Android means more time for LuneOS itself Feb 25 17:12:29 Tofe: Well the Android bits in general don't seem too bad Feb 25 17:13:33 But yeah less time spend on that always helps ;) Feb 25 18:55:32 Herrie|Laptop: Interesting! Feb 25 19:16:52 elvispre: Checking the whole defconfig with the mer_verify_kernel_config script and updating the defconfig Feb 25 19:16:59 Just as usual some build errors appear Feb 25 19:17:03 So working through those now Feb 25 19:17:09 Once OK I'll have a new image for you Feb 25 19:17:24 Well actually flashing the fastboot should suffice Feb 25 20:08:26 elvispre: http://www.vve-goudenleeuw.nl/zImage-dtb-onyx.fastboot Feb 25 20:08:34 fastboot flash boot zImage-dtb-onyx.fastboot Feb 25 20:08:40 And you should be set to go Feb 25 20:08:44 Hopefully this works better Feb 25 20:08:50 And we get a bit further Feb 25 20:08:55 And can do some debugging Feb 25 20:09:03 Because it looked pretty OK otherwise in logs Feb 25 20:09:46 Herrie: Yes it did. I'll give it a go as soon as I can download it to file and not just as a weird-looking web page! Feb 25 20:10:58 http://www.vve-goudenleeuw.nl/zImage-dtb-onyx.zip Feb 25 20:11:05 That might work better, you just need to unzip it Feb 25 20:11:13 :-) Thanks Feb 25 20:25:30 Hmmm. fastboot failed. Rapid-fire boot loop. Feb 25 20:30:18 elvispre: You could try to see if you can pull the console-ramoops from twrp/cwm Feb 25 20:30:36 I updated quite some defconfig so could be I broke something Feb 25 20:30:53 Though shouldn't be critical. Feb 25 20:31:09 Herrie|Pre3: The only thing I can try at the moment is any kind of recovery at all. I can only just get the thing into fastboot mode atm. Feb 25 20:31:15 Could be we'd need to manually disable selinux via cmdline param Feb 25 20:31:58 elvispre: That's weird Feb 25 20:33:57 You should be able to disable the selinux with fastboot as well Feb 25 20:36:08 fastboot boot image.fastboot -c "cmdline params" Feb 25 20:43:31 YOur cmdline params should be "androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 androidboot.selinux=permissive" Feb 25 20:44:00 So fastboot boot zImage-dtb-onyx.fastboot -c "androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 androidboot.selinux=permissive" Feb 25 20:53:30 So fastboot boot zImage-dtb-onyx.fastboot -c "androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x3b7 ehci-hcd.park=3 androidboot.bootdevice=msm_sdcc.1 androidboot.selinux=permissive" Feb 25 20:54:12 Herrie: Thanks. Currently running "fastboot flashing unlock" Feb 25 21:07:33 Hmmz really weird by just flashing boot this shouldn't happen Feb 25 21:08:27 Herrie: It won't do anything at the moment except tell me it is not unlocked. Feb 25 21:20:52 elvispre: Hmmz weird but OK Feb 25 23:14:44 Looks like my OnePlus X is a brick. I think the battery ran down and now it won't charge or turn on at all. Oh well. Feb 25 23:37:35 ...no. Not it's not completely dead yet. **** ENDING LOGGING AT Mon Feb 26 03:00:02 2018