Saturday, 2022-10-01

budrzHi I'm trying to build Sailfish OS for Google Pixel 3a XL and I'm stuck on section 7.2.1 of the porting guide01:30
budrzHere is the log file when running rpm/dhd/helpers/ --droid-hal:
budrzI did run make hybris-boot and make hybris-recovery01:32
budrzso I'm not sure why the file is missing01:33
budrzshould I run make bonito as described here?01:34
malusually make hybris-hal should be enough, are you sure it built successfully all the way to the end01:55
malmake hybris-boot only builds the kernel not everything needed for droid-hal packaging, make hybris-hal builds everything needed01:56
budrzlet me check01:58
budrzhere is the kernel build log file:
budrzthere are a couple depmod: WARNING's02:13
mal"Skipping build of hybris-updater-scr"02:15
malipt since HYBRIS_BOOT_PART is not specified02:15
budrzI see02:18
malso migth be it can't find a suitable fstab file in device repos, can you check your device repo if it has some fstab file02:20
budrzlet me check02:21
mal but that doesn't have any boot partition02:22
budrzhmm, that's odd02:23
malmaybe add one there02:23
mala bit like the userdata there02:24
malbut it seems you have also super partition in use which will require some extra things later but not now02:24
budrzI see that there's a boot_a and a boot_b on my device instead of a single boot. is that what you mean by super partition?02:32
malsuper partition mean how those system, vendor and some other partitions are listed in fstab02:37
malif you add the boot partition it should be something like this: /dev/block/bootdevice/by-name/boot         /boot           emmc    defaults                                                        defaults02:40
malif you add that and run make hybris-hal it should fix things02:41
malyou can see if it worked by searching for the error message I mentioned earlier from the build log02:42
malI need to get some sleep now02:43
budrzok I will try it. thanks for your help02:44
budrzI also need some sleep02:44
T42<hasajacy> any fix? (re @Marcel: It’s bootlooping and...)15:20
voidanix[m] anybody seen this before?17:49
voidanix[m]not sure if mic is failing at e2fsck or at dumpe2fs in the ks file17:50
malare you really building image like that and not the community style image?17:52
malmeaning that are you building image with flashable images17:52
voidanix[m]yep i am building the sfos X way as this is a sony anyways17:53
T42<elros34> how about adding set -x at beginning of script18:22
voidanix[m]will try18:32
voidanix[m]no luck with the `set -x`18:49
voidanix[m]i wonder if `Warning[10/01 18:46:56] : Can't get url from repo for droid-flashing-tools` has something to do with this all18:49
T42<elros34> no luck: no output or no useful output?18:50
voidanix[m]same error as before18:52
T42<elros34> set -x should print additional information, are you sure set -x i in your ks file?18:53
T42<elros34> is in*18:53
T42<elros34> btw do you build Do you have all these repos available?18:54
voidanix[m]hmm, strange that it didn't do anything18:55
voidanix[m]yes this is, targets, toolchain and sdk are updated18:55
T42<elros34> but is set -x really there in ks file? How did you add that? Also I am asking about repos defined in ks file not sdk/toolchain as these are quite irrelevant18:56
voidanix[m]i added it at the top of `hybris/droid-configs/kickstart/pack/j8210/hybris` which contains the actual "script"19:01
voidanix[m]there is also a `Jolla-@RELEASE@-j8210-@ARCH@.ks` in $ANDROID_ROOT, so i added it in the %pack part19:02
T42<elros34> did you build droid-config after that change?19:02
Thaodanvoidanix[m]: that's because the package isn't hw-common right now.19:08
ThaodanIt's not an issue unless you want to flash on windows.19:08
voidanix[m]oh i see19:11
voidanix[m]btw @elros34, this is the 4th time i run mic and it only now picks up the `set -x` wtf19:12
voidanix[m]or at least i think it does: `losetup: /dev/loop12: failed to set up loop device: No such file or directory`19:12
ThaodanThat sounds like an issue on your host.19:13
voidanix[m]interesting that there's only loop0 up until loop719:15
T42<elros34> doesn't looks like it do. Maybe there are some leftovers  from your previous attempts, that is why you have new error:  failed to set up loop device19:17
voidanix[m]guess i'll reboot then19:19
Thaodanvoidanix[m]:  check if some logical volumes are stuck19:23
Thaodanif so do vgchange -a n sailfish19:23
Thaodanthen the loop devices should be released19:24
voidanix[m]will try that next time, retrying to run mic rn19:26

Generated by 2.17.1 by Marius Gedminas - find it at!