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

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