Sunday, 2022-05-29

T42<Verevka86> And yamuisplash should show something when loading? I have a black backlit screen for some reason10:12
T42<edp_17> Yamuisplash don't work on any of my ports since sfos 4.3. :(10:25
T42<elros34> @Verevka86 did it work previously? I had to cut splash screen logo to get it working but I guess you have bigger screen resolution than my device. logo have 1080x2520px resolution10:32
T42<Verevka86> 2400*1080 (re @elros34: @Verevka86 did it wo...)10:38
T42<Verevka86> thanks for the hint 🤝 (re @elros34: @Verevka86 did it wo...)10:44
T42<elros34> so either try to use --text argument, it should print whether text you want on screen or cut logo slightly, it may help10:44
T42<Verevka86> logo has started working, and the system has stopped starting 😁11:32
Thaodanvoidanix[m]: On A10 it the same issue.11:45
Thaodantry rebuild the kernel with CONFIG_QCOM_RUN_QUEUE_STATS=y11:49
T42<Verevka86> Need help, droid-camres:12:18
T42<Verevka86> [defaultuser@PocoX3Pro ~]$ droid-camres -w12:18
T42<Verevka86> [I] unknown:0 - Camres version 1.2.312:18
T42<Verevka86> [I] unknown:0 - Searching cameras...12:18
T42<Verevka86> [C] unknown:0 - Camres error: Property camera-device is not an enum.12:18
T42<Verevka86> [F] unknown:0 - Camres error: No cameras found.12:18
voidanix[m]Thaodan: yep rq-stats is actually needed and irqbalance now works, although CPU usage on the big cores hasn't changed13:59
Thaodanvoidanix[m]: I'm not sure if the config in vendor is done properly14:00
Thaodan /vendor/etc/msm_irqbalance.conf  that is14:00
Thaodanthere's also E MSM-irqbalance: WARNING: Cannot find matching virq for hwirq(39).14:00
voidanix[m]the PRIOs look very much correct to me14:01
voidanix[m]could be a scheduler issue?14:01
Thaodanvoidanix[m]: I don't know.20:23
Thaodanis this in dmesg something that should be of concern? [    0.162137] persistent_ram: uncorrectable error in header20:25
T42<cryptodas> <continuing with attempts to run Sailfish on HTC U11>23:59
T42<cryptodas> After checking journalctl via recovery I have managed to get the device booted stably enough.23:59
T42<cryptodas> For new porters: I saw errors about droid-hal-init failed to start and lots of firmware libraries not found. So I had to deal with mounting the vendor partition (it is /system/vendor instead of /vendor in my case) and creating symlinks to (I used odm path in sparse as suggested somewhere in this chat). After all I got telnet working and the device running without reboots (thanks to this chat advice).23:59
T42<cryptodas> Now I have droid-hal-init started successfully but it seems that other services fail (it's reported they receive signal 6 SIGABRT after encountering some errors). And I have no graphics, the device just shows the boot logo.23:59
T42<cryptodas> I feel a bit exhausted searching for solutions. Can somebody please point me where to start with debugging no graphics case?23:59

Generated by 2.17.1 by Marius Gedminas - find it at!