Saturday, 2026-05-16

« Friday, 2026-05-15 Index
nightishamanmal: https://paste.centos.org/view/9c38941c00:06
malcomment out "Requires: gstreamer1.0-droid" from patterns in droid-config repo00:10
malwhich should be in hybris/droid-configs/patterns/patterns-sailfish-device-adaptation-$DEVICE.inc00:11
malthen build_packages.sh -c again00:11
malnightishaman: while at it check that you have correct version in droid-config spec00:12
mallike this but the version you have in use which I understood is 16 https://github.com/mlehtima/droid-config-fp5/blob/master/rpm/droid-config-fp5.spec#L700:12
nightishamanalso gmp-droid00:12
nightishaman?00:12
malyes, gmp-droid can go also00:13
nightishamanI wonder whether my esim will work00:21
nightishamanits still saved in the phone, it survived across reflashes00:21
nightishamanits finished00:24
nightishamannow I just need to boot into recovery mode and apply the zip file from add?00:24
nightishamanadb?00:24
malsomething like that00:31
nightishamanhmm00:32
nightishamanit couldn't flash because it couldn't mount userdata00:32
nightishamani have to recheck the paths00:32
nightishamanthe paths exist00:39
malis userdata in correct format?00:40
malwe want it to be ext400:41
nightishamanprobably not00:41
nightishamanI can use adb shell for that00:41
malI need to get some sleep now00:44
nightishamanokay00:44
nightishamanmal: once you wake up, the install process fails because the recovery environment has no bzip2 support01:26
T42<elros34> common issue, use gzip instead https://sailfishos.wiki/link/20#bkmrk-%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0-%2A-twrp-is-kn01:47
rinigusMister_Magister: look for system apk's that can be of interest. At some point I decompiled a large bunch of them and just grepped for info05:20
malMister_Magister: I had a bit of a look at the refresh rate things in hwc, there are two things, setting a specific refresh rate and then the variable refresh rate in which it can change all the time based on content or something13:12
Mister_Magistermal: yeah the latter would be the best i think13:19
Mister_Magisterand the hardest xd13:19
Mister_Magisterso far i have one port that's locked to 120Hz and i locked my new port to 120Hz as well13:20
Mister_Magisterbut obviously if we could drop that when there's nothing happening on the screen it'd save power13:20
Mister_Magisterjust i think we'd need to implement hwc3 no?13:21
malyeah, we could consider forcing lower also in case someone wants to save power13:21
malwe basically have hwc3 already, in the compat code13:21
Mister_Magisteror like if low power mode is enabled (sfos has one idk how much it does)13:21
malwe just haven't named it hwc313:22
Mister_Magisterit'd be smart to limit it to 60Hz in low poer mode13:22
Mister_Magistergotcha13:22
Mister_Magisterwell it's something that I think should be implemented going forwards cause literally nobody makes 60Hz only phones anymore13:22
malafaik we just need to extend the hwc3_compatibility_layer13:22
Mister_Magisterand like the new oleds can go as low as 5Hz or something13:23
malforcing lower refresh rate should be quite simple in hwc level, just need to think how to get the info from UI level13:24
Mister_Magisterhow about higher refresh rate? :P cause default is often 60Hz and losing 120Hz would be a shame13:24
malwell same thing is used for both13:25
Mister_Magisterye13:25
Mister_Magistermine has 48, 60, 90, 120Hz13:25
Mister_Magisterhttps://github.com/VerdandiTeam/android_kernel_motorola_sm6375/commit/77fbb7f9861b17582d8d21edcacf2eb31cfc4958#diff-e75ed31b62dcf37090b02f434beaf1a7c9eb1703d6bd0659fc4b5a7804464631L372-L38713:26
malPSA: any porters testing 5.1, you need at least qt5-qpa-hwcomposer-plugin 5.6.2.26 for suspend to work, also a note that 5.6.2.27 requires update of the libhybris hwc2 compat module in hybris-hal build (i.e. in droid-hal packages)14:03
T42<CRK_11755> Are any of you boys and girls running this on fairphone 415:19
Mister_Magisterin fact the guy who ported sfos on fp4 is right above you15:20
mal@CRK_11755 I haven't yet tested fairphone devices with 5.1, I know some things that need to be fixed already though16:10
T42<CRK_11755> Okay great thank you16:28
nightishamanmal: I flashed all the img files yesterday to the device and extracted the rootfs to /data/.stowaways/sailfishos, but when booting now, it stays at the Google logo for 30 seconds and then reboots. How can I debug this?17:30
malnightishaman: do you see anything host dmesg?17:33
nightishamannope17:33
nightishamanthe last entry was from fastboot17:33
malyou flashed 4 images?17:33
malboot, init_boot, dtbo and vendor_boot17:34
malassuming you have all of those17:34
nightishamanI flashed from out/target/product/panther: boot, init_boot, dtbo, vendor_boot and vendor. I flashed from device/google/pantah-kernels/6.1/: vendor_dlkm and vendor_kernel_boot17:35
malhmm, what are those last ones17:36
nightishamanvendor_dlkm is kernel modules17:36
nightishamanvendor_kernel_boot no idea17:36
malbut aren't those in super partition usually17:36
malI mean vendor_dlkm17:36
malthat is too high levelfor current debugging anyway, current target is to get telnet into init17:37
nightishamanthey are, I flashed in fastbootd in LineageOS recovery17:38
maldo you have rndis functionfs stuff enabled in defconfig?17:38
malbut 30 seconds is too short for usb related issues which would trigger at 60 seconds17:38
malI suspect it somehow doesn't like the boot images17:39
malI wonder if it wants signed boot images or not17:39
nightishamanbefore I didn't flash vendor_boot, only boot. then it would restart immediately, so I guess not17:40
nightishamanwhich config is rends?17:41
nightishamanrndis?17:41
malsomething like these https://github.com/mlehtima/android_kernel_fairphone_qcm6490/blob/hybris-23.2/arch/arm64/configs/vendor/fp5-qgki_defconfig#L103117:42
malare the sizes of the boot images reasonable looking+17:43
malhmm, so you extracted the rootfs, I just wonder how far it actually boots17:49
malwithout rootfs in userdata it would always stop in init telnet17:50
nightishamanI can delete the userdata17:54
nightishamanalso Rndis is not set17:55
malenable rndis and see if anything changes17:59
nightishamanI just have to flash boot img then, the kernel is on that, correct?18:23
malvendor_boot also probably since it might affect module layout or something18:24
nightishamanvendor_kernel_boot too I think18:24
nightishamanhttps://source.android.com/docs/setup/build/building-pixel-kernels?hl=de#update-the-vendor-ramdisk18:24
nightishamanvendor_kernel_boot might contain kernel artifacts18:24
malhmm, wait18:24
malwas that pixel 7 you have?18:25
nightishamanyes18:25
malso that section doesn't apply to it18:25
nightishamanjust the warning it says there18:25
malI need to check a bit what kind of partition setup your device has18:25
nightishamanthat pixel 7 and up split vendor_boot into vendor_boot and vendor_kernel_boot18:26
malI need to read that to know what changes we might need18:26
nightishamanImportant: Skip this section for Pixel 7 and later devices. Only Pixel 6, Pixel 6 Pro, and Pixel 6a devices need to update the vendor ramdisk. Pixel 7 and later devices split the vendor_boot partition into two partitions -- vendor_boot and vendor_kernel_boot -- where the kernel artifacts are fully contained by the vendor_kernel_boot image.18:26
nightishamanI have to find out how to mount the images on my host system, to check out what's in there18:27
malyou don't have to mount them, I can tell how to get the content18:27
nightishamanill be back in half an hour18:27
malhttps://android.googlesource.com/platform/system/tools/mkbootimg/+/refs/heads/main this has unpack_bootimg.py which can be used to extract the content of boot images, clone that and use the tool18:28
malthe extracted ramdisks are there but usually don't have file extension correctly so copy the ramdisks and rename to something.cpio.lz4 after which those can be decompressed more easily18:29
nightishamanmal: jannikmueller@fedora:~/hadk/image$ ls19:07
nightishamanbootconfig  dtb  vendor_ramdisk00  vendor-ramdisk-by-name19:07
nightishamanit contains the vendor ramdisk19:07
malwhat does your vendor_boot contain?19:13
nightishamanokay the ramdisk contains modules19:14
nightishamanonly modules, the dtb and bootconfig19:14
malok19:14
malso the init side of the ramdisk is probably in vendor_boot then19:14
malthat just means both need to be flashed19:15
malthe modules are the more important part19:15
nightishamanvendor_boot seems to be the init ramdisk19:18
nightishamanhttps://paste.centos.org/view/c871855619:18
malwhat is in init_boot?19:21
maldoes the device even use init_boot19:22
malif init is in vendor_boot19:22
malI mean that file init19:23
nightishamaninit_boot contains kernel and Ramdisk, which contains init19:24
nightishamankernel is an empty file19:25
malyes, empty kernel there is normal19:26
malthat vendor_boot is a bit of question19:26
malif the init there a file or a symlink?19:26
malalso in init_boot19:26
nightishamaninit_boot is a normal file19:27
nightishamanvendor_boot was a symlink19:27
maldo you happen to have init_boot from a normal android build available?19:27
malI think you could get it from lineage builds19:28
nightishamani have lineage local yes19:28
maljust to see what it contains19:28
nightishamanjannikmueller@fedora:~/lineage/out/vrd_extracted$ ls19:29
nightishamandebug_ramdisk  dev  first_stage_ramdisk  init  metadata  mnt  proc  second_stage_resources  sys  system19:29
malis that init a normal file19:30
nightishamaninit is a file, the rest are folders19:30
malok19:30
nightishamanjannikmueller@fedora:~/lineage/out/vrd_extracted$ file init19:30
nightishamaninit: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, for Android 36, BuildID[md5/uuid]=d7c8c6c70ea911cf6c4daed50d405649, stripped19:30
nightishamani flashed the kernel with rndis enabled, im gonna try to boot it19:30
malI just had a look that bootloader should copy init_boot over vendor_boot ramdisk during boot so we should be getting the correct init into use19:30
maljust to be sure, you flashed hybris-init_boot.img?19:31
nightishamanfuck19:31
nightishamanI knew I forgot something19:31
malto init_boot19:31
nightishamannot booting19:34
nightishamanim back into fastboot19:34
malhmm19:35
maland you flashed also boot image19:35
nightishamanvendor_kernel_boot, vendor_boot, init_boot and boot19:35
maldoes it behave differently with init_boot.img and hybris-init_boot.img? assuming you have both19:36
nightishamanI only have hybrid-init_boot19:37
nightishamanI could flash lineage init_boot19:37
nightishamanhttps://pastebin.com/zpLGfbhW19:38
nightishamani have those images19:38
malok19:38
malhow did it behave in that last boot? same 30 second delay to reboot or directly to fastboot?19:40
nightishaman30 second delay then black screen and then I pressed fast boot key combination19:41
T42<elros34> did you ever check for init.log existence?19:42
nightishamannvm19:42
nightishamanit was 60 seconds19:42
nightishamanI just measured19:42
malok, that could be then usb issue19:43
malhttps://github.com/mer-hybris/hybris-boot/blob/a16/init-script#L307 just for our information19:43
mal*your19:43
malbut nothing in host dmesg still?19:43
T42<b100dian> did you flash boot or hybris-boot to boot partition?19:44
nightishamanonly the bootloader19:44
malthere are some cases where the usb related udc handling is done in a way that is not supported in our init script19:45
nightishamanboot.img, hybris-boot.img is never created, that was just boot.img that I copied earlier as mal told me I can use the boot.img from the kernel build19:45
nightishamanit only contains the kernel anyway19:45
mal@b100dian would not matter in this case since boot img only contains kernel anyway19:45
nightishamanwould the init.log be on user data @elros4319:46
T42<b100dian> ah, so the rest is in hybris-init_boot. Ok ;)19:46
nightishamanyes, the init ramdisk is in init_boot and vendor_boot19:46
nightishamankernel modules in vendor kernel boot19:46
T42<elros34> yes https://sailfishos.wiki/link/20#bkmrk-%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0-%2A-if-your-de-119:48
nightishamanok ill boot into recovery19:48
T42<hraj9258> !notes19:48
nightishamanno init.log19:55
nightishamanWhich ramdisk should contain the init-script?20:01
nightishamanthe vendor_boot init symlinks points to system/bin/init20:02
nightishamanhttps://pastebin.com/y1fZPB9v20:03
T42<hraj9258> which android base i can use to get started with porting sailfish os to my device ?20:10
T42<hraj9258> 20:10
T42<hraj9258> my device alredy support lineage os 23.220:10
T42<hraj9258> 20:10
T42<hraj9258> i also got halium based kernel running on my phoenix (POCO X2/ redmi k30),20:11
malnightishaman: as I mentioned earlier based on what I found is that init_boot overrides anything in vendor_boot so the init in init_boot should be the one used20:12
malnightishaman: that link earlier about init.log is only relevant if you have rootfs in place20:13
nightishamanhmm20:18
nightishamanok the init is the hybris oe20:18
nightishamanone20:18
malcan you check in android recovery a couple of things20:19
T42<elros34> @hraj9258 you can use it: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/2026/%23sailfishos-porters.2026-05-13.log.html#t2026-05-13T23:59:2820:20
nightishamanyes20:23
nightishamanwhat should I check20:23
T42<hraj9258> @elros34 thanyou20:25
malnightishaman: what do you have under /sys/class/udc/20:28
nightishaman1|panther:/ # ls /sys/class/udc20:28
nightishaman11210000.dwc320:28
malok, then what does this show: cat /sys/class/udc/11210000.dwc3/device/../mode20:29
nightishamanhttps://pastebin.com/NqaSQhrq20:33
malI wonder if that is the reason20:36
malcan you check /sys/devices/platform/soc/ if there are any paths with that 1121000020:36
nightishaman1|panther:/ # ls /sys/devices/platform/soc20:40
nightishamanls: /sys/devices/platform/soc: No such file or directory20:40
malhmm, or elsewhere there under /sys/devices/20:42
malmaybe do this: find /sys/devices -name '*11210000*'20:42
malor this: find /sys/devices -name mode20:43
nightishamanhttps://pastebin.com/ux0vu0cw20:44
malcheck under /sys/devices/platform/11210000.usb/20:46
nightishamanpanther:/ # ls /sys/devices/platform/11210000.usb/20:46
nightishaman11210000.dwc3             dwc3_exynos_otg_state  supplier:i2c:13-002520:46
nightishamandriver                    force_speed            supplier:phy:phy-11200000.phy.920:46
nightishamandriver_override           modalias               supplier:platform:11200000.phy20:46
nightishamandwc3_exynos_extra_delay   new_data_role          supplier:platform:18062080.pd-hsi020:46
nightishamandwc3_exynos_gadget_state  of_node                supplier:platform:1e080000.clock-controller20:46
nightishamandwc3_exynos_otg_b_sess    power                  uevent20:46
nightishamandwc3_exynos_otg_id        subsystem              usb_data_enabled20:46
malwhat does that usb_data_enabled contain?20:48
nightishaman130|panther:/ # cat /sys/devices/platform/11210000.usb/usb_data_enabled20:49
nightishamanenabled20:49
nightishamani have a feeling we have to enable that20:50
malnightishaman: does this work cat /sys/class/udc/11210000.dwc3/device/../usb_data_enabled20:51
T42<elros34> disable and see what will happen:P20:51
malI suspect we need to add write to that next to this https://github.com/mer-hybris/hybris-boot/blob/a16/init-script#L251C11-L251C4320:52
malbut we'll if can use the same method20:52
nightishamanpanther:/ # cat /sys/class/udc/11210000.dwc3/device/../usb_data_enabled20:53
nightishamanenabled20:53
malok, so edit hybris/hybris-boot/init-script in the place where I just linked, add new line with this: write /sys/class/udc/"$udc"/device/../usb_data_enabled 120:54
« Friday, 2026-05-15 Index

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