**** BEGIN LOGGING AT Wed Jul 03 03:00:28 2019 Jul 03 04:40:22 Christian àb was added by: Christian àb Jul 03 04:40:23 Fwd from DEX: 🚀 Binance DEX … 🚀 Fast and secure decentralized digital asset exchange … 🚀 The new cryptocurrency trading standard is here. … ✅ Details: https://dextestnet.info Jul 03 06:11:59 @Jack ma [My ramoops log is a binary file called dmesg-ramoops-0.enc.z and I can't read it …], Humm which kernel do you have ? … Halium has a great documentation about that http://docs.halium.org/en/latest/porting/debug-build/dmesg.html Jul 03 06:23:53 @Jack ma [My ramoops log is a binary file called dmesg-ramoops-0.enc.z and I can't read it …], Enc sounds like encrypted Jul 03 06:24:21 But normally its called console-ramops Jul 03 06:32:43 dpes anyone know about "vald"? Is it something I can safely remove from the systemimage? (it cases some build errors) Jul 03 06:32:52 *causes Jul 03 06:33:37 vold is android volume daemon Jul 03 06:34:18 yes, AFAIU it's responsible for mounting devices, among other stuff. But is it used in Halium? Jul 03 06:37:59 it exists in system/vold, so probably yes Jul 03 06:38:20 also vold doesn't fail to compile on me Jul 03 06:39:37 Danct12: please see the error I reported above (10 hours ago), there it looks like vold is not failing itself, but it's a problem with a dependency Jul 03 06:46:13 what's your device manifest? Jul 03 06:46:24 also, make sure the repo is updated Jul 03 08:38:08 You can try to disable vold I think. Halium should do all mounts forthe container Jul 03 09:08:49 What about this? ninja: error: 'vendor/samsung/j3xlte/proprietary/bin/at_distributor', needed by '/mnt/Lavoro/halium/out/target/product/j3xlte/system/bin/at_distributor', missing and no known rule to make it Jul 03 09:09:28 I commented out `bin/at_distributor` from my `device/samsung/j3xlte/proprietary-files.txt` file, but that didn't make any difference Jul 03 09:11:03 the ninja files seem to still refer to `at_distributor`, even after a `mka clean` Jul 03 09:13:25 ah, it's mentioned in vendor/samsung/j3xlte/j3xlte-vendor-blobs.mk too. I'll remove it from there Jul 03 13:58:07 Danct12: thanks for your help; I ended up removing vold, since the last comment from here claims it's not used in Halium: https://github.com/Halium/halium-devices/pull/116 Jul 03 13:59:15 as for the other issue (about at_distributor), I was missing the proprietory blobs Jul 03 14:32:31 mardy, yeah, that was an interesting implication but UBports still does seem to require. I know because vold crashes when reading the ext4 partitions from SD cards still. Jul 03 14:35:30 @fredldotme mmm... you might be right: I indeed I have a /system/bin/vold in my Meizu PRO5 (still with the Canonical image). Well, I'll worry about it later :-) Jul 03 14:36:02 now I'm stuck on this: ninja: error: '/mnt/Lavoro/halium/out/host/linux-x86/bin/imgdiff', needed by '/mnt/Lavoro/halium/out/target/product/j3xlte/obj/PACKAGING/recovery_patch_intermediates/recovery_from_boot.p', missing and no known rule to make it Jul 03 14:38:00 yet I do have the source for imgdiff: bootable/recovery/applypatch/imgdiff.cpp Jul 03 14:40:40 maybe you have to add it to the `PRODUCT_PACKAGES` or however it's called. Jul 03 19:47:02 @fredldotme Didn't work :-( It may be that I need to add it to some other variable, given that this is a host tool Jul 03 20:06:36 make sure to add me to the reviewers in case you need a change in halium reps Jul 03 20:06:48 *repos merged Jul 03 20:13:04 so, I found that imgdiff is listed along with a few other host tools in `build/core/Makefile`. There's also a make target to build them ("otatools"), but if I run `mka otatools` it cannot build any of them: Jul 03 20:13:06 ninja: error: '/mnt/Lavoro/halium/out/host/linux-x86/bin/mkyaffs2image', needed by 'otatools', missing and no known rule to make it Jul 03 20:24:39 after some debugging of makefiles, it looks like make is entering into bootable/recovery/Android.mk but then does not parse it because the `ifeq ($(call my-dir),$(call project-path-for,recovery))` returns false. Is this expected? Jul 03 20:26:39 $(call my-dir) is "bootable/recovery", while $(call project-path-for,recovery) is "bootable/recovery-twrp" (the latter is a project listed in my lineageos.dependencies file) Jul 03 20:35:51 adding `bootable/recovery-twrp` to the `subdirs` variable in `build/core/main.mk` seems to get the build started, but I wonder if it's correct Jul 03 20:49:26 got this nice failure: https://pastebin.com/PBwKbDFX **** ENDING LOGGING AT Thu Jul 04 02:59:57 2019