Thursday, 2026-06-18

*** n2klb_ is now known as n2klb01:12
T42<elros34> @Mattia990 ah so you didn't flash sfos image then obviously searching for init.log is pointless. Your ramdisk contins only busybox and small script. I do not remember exact size but it won't be huge. Next time please use github or at least git diff to show your changes03:54
T42<elros34> you seams to change completly BOARD_KERNEL_CMDLINE. Revert it back to normal state04:04
T42<Mattia990> Is that I'm just trying, so for now I'm not committing to git the changes04:49
T42<Mattia990> I will try with stock cmdline04:49
T42<Mattia990> So I need to flash sfos image? Because I tried but the recovery said that bzip isn't available so I can't extract the tar file with the normal script (re @elros34: you seams to change ...)04:49
T42<elros34> you don't have flash whole sfos now, just it would be nice to know about it:P04:51
T42<Mattia990> I'm wondering if I need to manually run fixup-mountpoints.sh or if it is run during make hybris-boot.04:51
T42<Mattia990> I didn't run manually, so if it is needed probably it can be the main problem04:52
T42<elros34> nah, don't worry about it. It's automatic. for sure it's needs to be correct to switch from initramfs to sfos but that is not a problem now04:55
T42<elros34> you cna compare lineage's boot with hybris-boot.img with mkbootimg or some other tool04:56
T42<elros34> can*04:56
T42<Mattia990> Good to know, so later I will04:59
T42<Mattia990> - Revert the cmdline04:59
T42<Mattia990> - Build again with TEMPORARY_DISABLE_PATH_RESTRICTIONS04:59
T42<Mattia990> - Let you know the problem i have with the sfos tar extraction in recovery (I tried orange fox and twrp)05:00
T42<Mattia990> - Compare the boot images with lineage's one05:00
T42<Mattia990> Thank you for the support05:00
T42<elros34> tar.bz extraction is know issue and there are few possible workarounds05:02
T42<Mattia990> Good to know, what are those workaround? So later I can prepare the sailfishos's data folder (re @elros34: tar.bz extraction is...)05:09
T42<elros34> for axample: you got telnet working then you can unpack tarball straight from initramfs or switch to tar.gz (link to instruction is in hadk-hot) or.. few more05:11
T42<Mattia990> I understand, so the main point is to get telnet working05:46
T42<Mattia990> A doubt i have, probably my device has dynamic partitions, in order to fill up fixup-mountpoints.sh I checked the partitions name+number directly in the recovery instead of during the boot of the rom, am I doing the right or wrong thing? (re @elros34: for axample: you got...)05:46
T42<elros34> part number from recovery should be fine but by-name path you always take from fstab.05:48
T42<Mattia990> So the first part from here: https://github.com/xiaomi-sm8150-devs/android_device_xiaomi_sm8150-common/blob/lineage-18.1/rootdir/etc/fstab_dynamic.qcom05:52
T42<Mattia990> And the other part from recovery, right? (re @elros34: part number from rec...)05:52
T42<Mattia990> So the first part from here: https://github.com/xiaomi-sm8150-devs/android_device_xiaomi_sm8150-common/blob/lineage-18.1/rootdir/etc/fstab_dynamic.qcom05:52
T42<Mattia990> And the other part from recovery, right? (edited) (re @elros34: part number from rec...)05:52
T42<elros34> yeah but without kernel working this is little pointless05:53
T42<Mattia990> I thought it was important to make the kernel working. By the way thank you for all the information, later I will try what I wrote before05:59
T42<Teleg3_7> I’ve successfully compiled SFOS version 5.1.0.11 for my device. Usually, I have no issues using the self-built pulseaudio-modules-droid* packages, but with this new version, I had to use the pulseaudio bso rpm from  fp5 repo (https://repo.sailfishos.org/obs/nemo:/devel:/hw:/fairphone:/fp5/sailfish_latest_aarch64/aarch64/) . I once tried using the bso rpm package from  tucana device repo (https://repo.sailfishos.org/obs/nemo:/devel:/hw:/xia07:33
T42<Teleg3_7> 07:33
T42<Teleg3_7> Here’s a comparison of one of these files:07:33
T42<Teleg3_7> PlatformSDK home:~/sfos/src/hybris-20.0$ rpm -qpl droid-local-repo/fog/pulseaudio-modules-droid-14.2.106-1.6.1.bso.aarch64.rpm07:33
T42<Teleg3_7> /usr/lib64/pulse-17.0/modules/libdroid-sink.so07:33
T42<Teleg3_7> /usr/lib64/pulse-17.0/modules/libdroid-source.so07:33
T42<Teleg3_7> /usr/lib64/pulse-17.0/modules/module-droid-card.so07:33
T42<Teleg3_7> /usr/lib64/pulse-17.0/modules/module-droid-sink.so07:33
T42<Teleg3_7> /usr/lib64/pulse-17.0/modules/module-droid-source.so07:34
T42<Teleg3_7> /usr/share/licenses/pulseaudio-modules-droid-14.2.10607:34
T42<Teleg3_7> /usr/share/licenses/pulseaudio-modules-droid-14.2.106/COPYING07:34
T42<Teleg3_7> 07:34
T42<Teleg3_7> PlatformSDK home:~/sfos/src/hybris-20.0$ rpm -qpl ~/bckp/new/pulseaudio-modules-droid-14.2.106+master.20260512072452.e9ad39c-1.aarch64.rpm07:34
T42<Teleg3_7> /usr/lib64/pulse-14.2/modedge://linux-proxy-config/ules/libdroid-sink.so07:34
T42<Teleg3_7> /usr/lib64/pulse-14.2/modules/libdroid-source.so07:34
T42<Teleg3_7> /usr/lib64/pulse-14.2/modules/module-droid-card.so07:34
T42<Teleg3_7> /usr/lib64/pulse-14.2/modules/module-droid-sink.so07:34
T42<Teleg3_7> /usr/lib64/pulse-14.2/modules/module-droid-source.so07:34
T42<Teleg3_7> /usr/share/licenses/pulseaudio-modules-droid-14.2.106+master.20260512072452.e9ad39c07:34
T42<Teleg3_7> /usr/share/licenses/pulseaudio-modules-droid-14.2.106+master.20260512072452.e9ad39c/COPYING07:34
T42<Teleg3_7> 07:34
T42<Teleg3_7> Can anyone explain how to create a bso rpm package for pulseaudio-modules-droid* intended for pulse-17.0? That way, I won’t have to copy the package from another device anymore.07:34
T42<the_hiktor> Is anyone having problems with USB tethering on arch ?10:35
T42<Umeaman> What problem do you have and is libimobiledevice installed to begin with? (re @the_hiktor: Is anyone having pro...)11:18
T42<Umeaman> And usb_modeswitch11:19
T42<Umeaman> Check this page:11:19
T42<Umeaman> 11:19
T42<Umeaman> https://wiki.archlinux.org/title/Android_tethering11:19
T42<adampigg> Is arch allowing rndis? (re @the_hiktor: Is anyone having pro...)11:32
T42<moworola> Why would libimobiledevice be relevant? That's for apple devices (re @Umeaman: What problem do you ...)15:11
T42<elros34> did you update droid-config submodule? pulseaudio was updated in sfos 5.116:17
T42<elros34> @Teleg3_7 ^16:17
malPSA: it's recommended to use commit 41cd1d9dbe6f644c98478705a4d96e9eb3fe0a90 for droid-hal-configs submodule in Sailfish OS 5.116:37
mallatest version has some new changes which might cause issues (USB call audio related changes)16:38
T42<Mattia990> Here there is the comparison between boot.img (lineage os 18.1), hybris-boot.img and stock.img (android 11 stock)17:02
T42<Mattia990> Also I put all fastboot informations17:02
T42<Mattia990> What I'm doing now is building hybris boot with stock cmdline17:02
T42<Mattia990> Meanwhile I will try to flash also dtbo.img17:02
T42<Mattia990> Something different is that lineage header version is 0, hybris is 2 and stock is 117:02
T42<Mattia990> www.pastebin.com/fxuhhRmr (re @elros34: you cna compare line...)17:02
maldid you check inside the ramdisk you extracted from hybris-boot.img?17:20
malbut interesting why boot image version is different17:20
T42<Mattia990> Should I try to build with version 1?17:22
T42<Mattia990> Soon I will extract the ramdisk (re @SailfishFreenodeIRCBridgeBot: <mal>but interesting...)17:22
T42<elros34> https://github.com/xiaomi-sm8150-devs/android_device_xiaomi_sm8150-common/blob/lineage-18.1/BoardConfigCommon.mk#L9217:22
malso that boot.img was from some different build?17:24
T42<elros34> lineage sources also have same v2 header https://github.com/LineageOS/android_device_xiaomi_sm8150-common/blob/lineage-18.1/BoardConfigCommon.mk#L9217:31
T42<Mattia990> boot.img is from the stock miui based on android 11 that i flashed on the phone (re @SailfishFreenodeIRCBridgeBot: <mal>so that boot.im...)17:35
T42<elros34> but you should flash lineage-18 instead17:36
T42<Umeaman> It wasn't obvious as to WHAT brand the problem applied to. (re @moworola: Why would libimobile...)17:47
T42<the_hiktor> @Umeaman, I already checked wiki and have those libs17:49
T42<the_hiktor> @adampigg idk 🫤17:50
T42<the_hiktor> Do u mean it's kernel problem17:50
T42<the_hiktor> Or firewall17:51
T42<the_hiktor> Or something else17:51
T42<Mattia990> Here's ramdisk content extracted from hybris boot: www.pastebin.com/1b0RWGSi (re @SailfishFreenodeIRCBridgeBot: <mal>did you check i...)17:53
malseems reasonable18:04
malcheck the init file in there and if the partition is set correctly, near the top18:05
T42<Mattia990> It is wrong. init script sets it to /dev/sda31 but in twrp is /dev/block/sda31 how can I fix it?18:21
T42<Mattia990> Here there is the full information: www.pastebin.com/ny8zCgaM (re @SailfishFreenodeIRCBridgeBot: <mal>check the init ...)18:21
T42<elros34> it's fine18:23
malit's supposed to be without block/ so don't change it18:28
T42<Mattia990> Perfect, the thing I'm trying to do now is to build with BOARD_BOOT_HEADER_VERSION := 018:31
T42<Mattia990> I hope something changes18:31
T42<Mattia990> Nothing, it doesn't work. I built the image with that value to 0 but it instantly goes to fastboot18:58
T42<elros34> do you fastboot flash it or boot?19:02
T42<Mattia990> I do fastboot flash boot and then fastboot reboot19:06
T42<Mattia990> I also tried with fastboot boot, the screen goes black, the phone seems to disconnect and then fastboot is available again (re @elros34: do you fastboot flas...)19:06
T42<elros34> add 'sleep 30' here: https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L36819:07
T42<Mattia990> After or before date? (re @elros34: add 'sleep 30' here:...)19:11
T42<elros34> doesn't matter19:12
T42<elros34> if device still reboots to fastboot mode then it's either boot image or your kernel changes19:13
maldoes it reboot to fastboot without any delay?19:27
T42<Mattia990> No, it is instantly, I don't see any delay19:33
T42<Mattia990> Now I'm building the image like elros said (re @SailfishFreenodeIRCBridgeBot: <mal>does it reboot ...)19:33
T42<Mattia990> It didn't work, also with the sleep it reboots to fastboot instantly.19:43
T42<Mattia990> Now I'm trying to revert my kernel change and build again (re @elros34: if device still rebo...)19:44
mal@Mattia990 something I noticed, in the boot.img ramdisk size is 0, the ramdisk might be somewhere else then, are you really sure there no other partitions like vendor_boot20:59
maljust wondering how the stock does things and if you have now some conflicting content from partitions21:02
T42<Mattia990> So stock android boot image also should have the ramdisk? I thought no because both stock and lineage boot images haven't (re @SailfishFreenodeIRCBridgeBot: <mal>@Mattia990 some...)21:04
malthere has to be ramdisk somewhere imo21:04
T42<Mattia990> I will check for partitions21:04
malfastboot should tell the partition layout21:05
T42<Mattia990> I can't see it, here's all the partition my phone has: www.pastebin.com/UHwDtWqg21:18
malyeah, seems ok21:37

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!