Tuesday, 2026-06-30

*** n2klb_ is now known as n2klb02:02
sharksWoo! I'm getting somewhere!! https://imgur.com/a/j0cMbem09:08
sharksNothing works, but at least I have a screen09:09
sharksProbably a bit early to celebrate tbh09:10
sharksHoly shite the camera works lol --> https://imgur.com/a/CaU3is109:41
sharksHow about that? An Xperia 10 IV running sailfishOS with a working camera, never thought I'd see the day09:41
sharksIf I can get sound and wifi and phone calls out of this thing now I'll be a happy man09:42
T42<elros34> so what was the issue with not working gui?09:52
sharksI came across `test_hwcomposer` in the porters logs, when I ran that I got a display which proved to me that we could talk to the hardware.09:56
sharksI still don't know why I get `Control message: Could not find 'android.hardware.graphics.composer@2.1::IComposer/default'` in journal, but that goes away once you actually manage to put something on the screen09:57
sharksAnyway then I tracked down how lipstick starts and started it manually / strace / etc, trying to debug it. Worked out it's looking for a touchscreen at /dev/input/event4, which did not exist. After running modprobe sec_ts_drv the touchscreen appeared at /dev/input/event3, and once I pointed lipstick to that it fired right up.09:57
sharksSo I wrote some very bodgy fixes into droid-hal-early-init.sh and now can reboot the device and bring up the display reliably\09:58
sharksnow I just have to clean that up and do it properly09:58
T42<elros34> didn't you have just evdevtouch in https://github.com/mer-hybris/droid-hal-configs/blob/master/sparse/var/lib/environment/compositor/droid-hal-device.conf?10:00
T42<elros34> it should autodetect touchscreen node by default10:00
sharksYes I think the problem is that there was no touchscreen in /dev/input/event3 until I ran `modprobe sec_ts_drv`10:01
sharkssorry, in /dev/input/* anywhere. All I had was buttons and a switch for when the USB disconnects.10:02
sharksSo I need to work out why that is missing10:02
T42<elros34> not so important but just it doesn't matter whether there is /dev/input/event3 or not if you don't hardcode any node in droid-hal-device.conf10:05
sharksSo /dev/input/. can be an empty directory and the hardware still works?10:07
T42<elros34> no I am only talking about autodetection of touchscreen node in lipstick/qt10:10
sharksAh sorry I understand now, yes /dev/input/event4 was hardcoded in the file, I changed that to /dev/input/event3 and put `modprobe sec_ts_drv` in early-init.sh and that fixed things. But I think the modprobe command should not be in that script? So I need to figure a cleaner way to do that.10:13
sharksI have now changed the file to autodetect per your suggestion and can confirm that works too. I like that solution better, thanks10:13
T42<elros34> https://github.com/mlehtima/droid-config-fp5/blob/master/sparse/etc/modules-load.d/fp5.conf10:19
T42<elros34> but you seams to have10:20
T42<elros34> ```10:20
T42<elros34> sec_ts_drv: disagrees about version of symbol module_layout in logs```10:20
T42<elros34> so could be reason why it's not autoloaded10:21
sharksThanks - I just came across modules-load.d, was about to go down that route but good spot, I wonder why we get that warning. You could be right, maybe it is trying to autoload but is failing. I wonder why it works when I load it manually?10:23
T42<elros34> I guess first try is in initramfs10:26
sharksYes could be there. I think to be honest I will just put it in modules-load.d for now and come back to it later if it's a problem.10:31
T42<elros34> also check for  other maybe useful modules you want to add there which now fail with: "disagrees about version of symbol module_layout"10:37
sharkshmm there are a few, I'll work on that. Thanks. Chances are some of them are related to other bits of the hardware I'm yet to make work10:40
T42<nikita_kraev> how do we tackle the "disagrees about version of symbol xxx" in general?10:42
Mister_Magisteryou just ignore it and it works anyway10:44
T42<nikita_kraev> lol okay, that's what i was planning to do anyway :D10:47
sharksHaha too easy10:49
Mister_Magisterwait a minute10:55
Mister_Magister@edp_17 yo did you try my moto gestures stuff?10:56
mal@nikita_kraev what gives that error?11:02
T42<Mister_Magister> mal android's modprobe11:04
Mister_Magistermal: from what I gathered, and I might be wrong, because I have same issue on my device, it's from android wanting to modprobe from vendor11:40
Mister_MagisterI could be wrong tho11:48
T42<nikita_kraev> yeah, it's Android modprobe, only happens in droid-hal-init i think, i am currently masking ins_modprobe, so don't have it in the latest logs unfortunately11:53
malwell you should make sure the modules get loaded, a bit like how I did on fp5 https://github.com/mlehtima/droid-config-fp5/blob/master/sparse/etc/modules-load.d/fp5.conf11:54
T42<nikita_kraev> oh yeah, that is a big source of inspiration for me, thanks mal!11:55
T42<nikita_kraev> modules-load.d is the one i am touching next, that one is only after systemd starts though, right? or can we check it in init-debug?11:55
malthat happens in systemd11:56
malwhat issue are you trying to solve?11:56
T42<nikita_kraev> Just boot system past droid-hal-init, initially i tried just masking anything i could, but i am reassessing since i have an early kernel panic re: some of the modules, so i am taking a step back and probably will spend a little more time in init-debug until it progresses naturally. Not in front of the laptop for now so no logs, but I'll send them later12:14
T42<nikita_kraev> i think that was my best run; logcat -  https://gist.github.com/nikita-kraev/92d87cb212a6672256b092d20df4bc9a14:13
T42<nikita_kraev> since then i am only regressing lol, something is rebooting the device earlier and i am not even able to get to logcat anymore14:13
T42<elros34> did you check /sys/fs/pstore/console-ramoops*?14:31
T42<nikita_kraev> yeah, it's empty, looks like the kernel is not panicking or my device doesn't preserve it14:33
T42<elros34> did you check all files there, right after rebooting?14:36
T42<elros34> maybe you should try echo -n “/vendor/firmware” > /sys/module/firmware_class/parameters/path as in https://forum.sailfishos.org/t/livecasting-porting-notes-for-zenfone-8/14727/3814:48
T42<elros34> btw do you have CONFIG_FW_LOADER_USER_HELPER_FALLBACK enabled?14:52
T42<nikita_kraev> i'll check it out, thanks! No, i don't have the CONFIG_FW_LOADER_USER_HELPER_FALLBACK, will also google that, ty!15:01
T42<elros34> so try fw loader fallback first15:02
T42<elros34> enable together with dependencies, build hybris-hal and flash kernel15:03
T42<edp_17> @Mister_Magister , Nah. I am still busy with waydroid on hammerhead. Then, I'll start building 5.1 for my ports an fixes bugs. Sorry.15:26

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