Thursday, 2022-10-06

budrzlineage kernel sources:
T42<elros34> AFAIK this should be no problem in android 11 but you can check cat /proc/cmdline in lineage (not recovery) to make sure there is no skip_initramfs but more likely it's something else00:23
budrzhere is my kernel sources:
budrzok, I'll check00:33
budrzthere is no skip_initramfs00:37
budrzthe boot.img didn't work. same messages as before00:43
budrzso are you suggesting reverting to the originial defconfig, except maybe some of the config "ERROR"s fixed from the hybris kernel config check?00:48
budrzI'll pick this up tomorrow00:55
T42<elros34> yes revert to original, if that will lead to the same results then maybe you are making abootimg incorrectly. You have working lineage kernel to compare06:21
T42<elros34> again check what is in host dmesg, because I still do not know06:24
voidanix[m]broken vibration, camera and video playback all at once means gstreamer is broken right?15:26
voidanix[m]here's a jolla-gallery with GST_DEBUG and ngfd+gdb just in case15:27
voidanix[m]urgh, figured out my issue:
voidanix[m]ping @Thaodan: does using the commit above require another commit somewhere else?19:55
T42<elros34> according to description yes: some commit in droidmedia19:57
voidanix[m]that one is already merged, it seems there is something for dhd though20:01
Thaodanvoidanix[m]: there's one pr in dhd for packaging that you need to use if you build this locally21:04
budrzelros34: I tried creating the image with the original defconfig and modified to remove the errors from the mer-kernel-config check script but still no progress21:36
budrzdmesg has the same messages as before21:37
budrzso I guess maybe I'm making abootimg incorrectly21:37
T42<elros34> again: I still do not know what are messages in your host dmesg at first boot21:38
T42<elros34> you showed flood of logs, I have no idea when you flashed kernel, when it try to boot and when it switch slot and starts android21:38
T42<elros34> anyway in android sources you should have unpack_bootimg or something like that, if I remember correctly this tool prints a lot of info about abootimg which you can use to compare with lineage's boot.img21:40
budrzthere's in system/tools/mkbootimg/21:44
budrzis that it?21:44
T42<elros34> probably, try and you will see21:44
budrzelros34: here is the output of the image created using the original defconfig:
budrzand one with the errors removed from the kernel check script:
budrzthere's not much of a difference:
T42<elros34> they will be the same, compare with working one so:lineage's boot.img21:57
budrzok, hang on21:58
budrzhere is the lineage output:
budrzand the diff between lineage and the image with out errors from the config script:
budrzthere's much more of a difference here...22:03
T42<elros34> not really I was hoping for dtb differences but no.22:04
budrzseems like I'm missing the androidboot.super_partition command line argument though (among other things). not sure if adding that would help22:05
T42<elros34> Have you tried flashing some empty vbmeta image? no idea whether this is needed for your device. Try adding 'sleep 40': here then mka hybris-boot and flash hybris-boot.img (can be without any defconfig changes). Provide dmesg from first boot after flashing and reboot also timing.22:23
T42<elros34> or maybe even in line 34322:27
budrzthere is a vbmeta.img for lineage and the stock rom23:04
budrzI will try adding the sleep command to the init script. can the vbmeta image be from lineage?23:08
T42<elros34> I am not sure about it but AFAIK it should be empty vbmeta flashed so this kind of verification is disabled23:10

Generated by 2.17.1 by Marius Gedminas - find it at!