Monday, 2026-11-02

T42<damnbruh2004> i set boot image header version to 0 explicitly and it worked. it reports randisk size != 0, so we can assume it is packaged? full output https://pastebin.com/QTzHFigw00:03
T42<damnbruh2004> oh, apparently telnet is provided by device, i just needed to run lsusb -v as root. that being said i can't connect to it and steps from the halium docs don't apply. perhaps this is because i am using wsl + usbipd00:56
T42<damnbruh2004> halium docs are at https://docs.halium.org/en/latest/porting/debug-build/early-init.html00:56
*** n2klb_ is now known as n2klb02:37
T42<damnbruh2004> apparently you need to compile and enable a separate module for usb networking to work with wsl + usbipd-win. you can follow the steps as described in this post, except for the sed-based patch line, it's not needed05:04
T42<damnbruh2004> https://forum.sailfishos.org/t/jolla-phone-2026-windows-11-has-anyone-successfully-used-usb-developer-mode-rndis/30616/605:04
T42<damnbruh2004> managed to get telnet and examined the logs. it fails to mount userdata and the partition layout is different from what i have set in the fixup-mountpoints. i can mount the directory manually (though the device path is different from both fixup-mountpoints and what the init script is using)06:27
T42<damnbruh2004> error is as follows06:27
T42<damnbruh2004> mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: No such file or directory06:27
T42<damnbruh2004> full log https://pastebin.com/dvJUi2tq06:27
T42<damnbruh2004> any tips would be appreciated, thanks06:27
T42<damnbruh2004> fixup-mountpoints source https://github.com/fortuna-for-smoothie/hybris-boot/blob/hybris-18.1/fixup-mountpoints#L118306:28
T42<the_hiktor> Which device was that ? (re @damnbruh2004: fixup-mountpoints so...)07:32
T42<damnbruh2004> @the_hiktor fortuna3g is galaxy grand prime xxu07:34
T42<the_hiktor> You sure about the mount points ? (re @damnbruh2004: @the_hiktor fortuna3...)07:36
T42<the_hiktor> Besides does it use dynamic partitions ?07:36
T42<damnbruh2004> Not really. I will boot into android later today and confirm. It does not use dynamic paetitons (you mean a/b boot, right?)07:37
T42<damnbruh2004> For the mountpoints it had two categories with different names when i checked in android. Ao maube i should've used the other one07:38
T42<the_hiktor> Could be without a/b scheme too (re @damnbruh2004: Not really. I will b...)07:38
T42<the_hiktor> Check fstab (re @damnbruh2004: For the mountpoints ...)07:38
T42<damnbruh2004> Yeah, it had recovery fstab and basic fstab in android. I took info from the basic one07:39
T42<damnbruh2004> @the_hiktor google says dynamic partitons were introduced in android 10. The device is from 2015, so probably no. Even rhough I am building on top of custom lineage 18.1 android 1107:42
T42<the_hiktor> Ik but i remember some people crazy enough to bring such thing to old devices (re @damnbruh2004: @the_hiktor google s...)07:43
T42<the_hiktor> Show me your fstab08:01
T42<damnbruh2004> @the_hiktor the fstab looks like this https://pastebin.com/s5kzTBeK08:11
T42<elros34> so your fixup-mountpoints doesn't match it08:21
T42<damnbruh2004> as per hadk handbook i did `ls -l /dev/block/platform/*/by-name/` and used the output08:32
T42<elros34> that is wrong. read hadk-hot or just use by-name path from your fstab08:33
T42<elros34> block/bootdevice/by-name08:33
T42<damnbruh2004> srry for not referring to hot again. I was setting up the kernel part before i discovered it09:52
T42<damnbruh2004> I edited the fixup script but the log is identical09:53
T42<damnbruh2004> You can find it here https://github.com/fortuna-for-smoothie/hybris-boot/blob/d329c541912542285da7299c439053ae7038783b/fixup-mountpoints#L118309:53
T42<damnbruh2004> just in case i misunderstood the writing09:55
T42<damnbruh2004> fstab.qcom https://pastebin.com/s5kzTBeK09:55
T42<damnbruh2004> ls devices https://pastebin.com/NKYzZpLe09:55
T42<elros34> did you run make hybris-hal and fash hybris-boot.img after making changes?09:58
T42<damnbruh2004> also diagnosis.log file reports CONFIG_AUTOFS4_FS option missing in kernel, even though i've enabled it09:58
T42<damnbruh2004> https://github.com/fortuna-for-smoothie/android_kernel_samsung_msm8916/blob/d0367ab6d2b60ce937d5c513536a5d9e446d99f4/arch/arm/configs/msm8916_sec_defconfig#L9609:58
T42<damnbruh2004> @elros34 i built hybris-hal and droidmedia, then packaged the full zip and flashed on top of lineage, since i was testing the layout in it09:59
T42<elros34> just flash now hybris-boot.img09:59
T42<damnbruh2004> may this error be due to no files .rc in /root after building droid-hal? we circumvent this by creating a dummy rc10:00
T42<elros34> not related at all10:02
T42<damnbruh2004> okay. after flashing hybris-boot into the kernel it bootloops. let me see the kmsg10:03
T42<elros34> touch /data/.stowaways/sailfishos/init_enter_debug210:04
*** deathmist1 is now known as deathmist10:06
T42<damnbruh2004> nope, still bootloops without establishing connection with my pc10:06
T42<damnbruh2004> gotta go now. will return to ya'll later10:07
T42<elros34> you must have done something else also. First you had fastboot mode - that wasn't fixup issue10:08
T42<damnbruh2004> no no, the fastboot thingy is wsl misinterpretting the connection10:08
T42<elros34> ok10:09
T42<damnbruh2004> i fixed it by installing the usb netwroking module into wsl and getting telnet10:09
T42<damnbruh2004> and then i sent you the logs, with mounting data failing10:09
T42<elros34> now it should mount /data but if AUTOFS4_FS is not set then it will still fail to boot and telnet would work. It is useless kernel config btw10:13
T42<damnbruh2004> Useless as in it takes no effect  or as in it is nonsense in and of itself?10:14
T42<elros34> you don't really need it so can be removed from init-script10:37
T42<damnbruh2004> Aren't the kernel's features build based on its content? Hadk handbook says to edit it and then use the keenel checker utility10:42
T42<damnbruh2004> I mean it says to find the config used, and various commonconfig files point to this one, so i started editing it and checker errors resolved then10:43
T42<damnbruh2004> I'm really new to rom development and porting, hope you don't mind obvious questions10:45
sharks[m]"Obvious" questions are okay - you know how to search the channel logs though right? Always try that first10:51
*** xmn__ is now known as xmn12:06
T42<theflyingrahul> Hi @mal, tried the rounded-corner idea for the left camera cut-out. Does it pad the right-side also by default, despite setting the rounding only for the left corner? Is there a way around this?12:17
T42<Mister_Magister> @theflyingrahul one tiny protip on irc you tag people like this (though it often depends on their irc client settings but this one is most common) <nick>: <message>12:28
T42<theflyingrahul> Got it, Thanks!12:29
mal@theflyingrahul hmm, need to have a look, maybe there is bug in that13:05
T42<theflyingrahul> <mal>: It is picking up the max radius from all the 4 radii, not sure if it's affecting the lower corners too13:07
T42<Mister_Magister> without the <> :)13:07
T42<theflyingrahul> Aha got it!13:08
Mister_Magistermal: i'm not sure if its claudine hallucinating or if its just my device or is it just a15 based ports but my app segfaults when using libuuid and something something it's because libhybris/android library, anyway, easy test is LD_PRELOAD=/usr/lib64/libuuid.so.1 jolla-calculator, could you maybe take a sec and look at it?20:50
Mister_Magisterit segfaults at tlsdesc_resolver_dynamic () at tlsdesc_resolver.S:5820:50
malwhich libhybris do you use?20:55
Mister_Magisterpr-testing20:56
malseems to fail yes20:57
malthe pr-testing branch is a hack20:57
malI wonder which apps use libuuid?20:58
Mister_Magisterwell mine does xd20:59
T42<adampigg> zypper rm libuuid21:00
T42<adampigg> n21:00
T42<adampigg> will tell you :)21:00
Mister_Magistermal: aigh I leave that to you have fun :)))) :DDD21:04

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