Sunday, 2026-07-05

*** n2klb_ is now known as n2klb01:53
T42<Mattia990> Do you mean using the kernel of lineage 22 on my actual build of lineage 18.1? (re @elros34: it's in lineage 22 s...)08:47
T42<elros34> for test sure. Trigger kernel crash to see if you can get any log. If it's not enough then switch whole base08:52
sharksI extracted the rootfs for two identical builds but one with `%define android_version_major 14` and one `15`. I am 100% certain on the device the version 14 one has working VoLTE and version 15 one has broken VoLTE. The base is Lineage 22.2 so it stands to reason I should have A15 set, but comparing the diffs between the rootfs of each I can't see what has changed that should affect VoLTE? Can anyone offer any insight? https://paste.opensu09:19
T42<elros34> you could just compare sparse-14 vs sparse-1509:46
sharksSure, I could have. I was just trying to be thorough. At any rate, it doesn't change the fact that the only differences are the ApiLevel in gbinder.conf, keymaster vs keymint, /etc/sysconfig/dummy_netd, and a comment in /etc/ofono/ril_subscription.conf. All of these changes I have copied to the phone running the A15 rootfs and I still can't re-enable VoLTE, but if I flash the A14 image it registeres straight away10:04
T42<elros34> so maybe it's random issue unrelated to change10:10
T42<Mattia990> I switched to the kernel of the android base i was using, made there the modifications and now i have working wifi, bluetooth, usb, rotation14:55
T42<Mattia990> I'm trying to understand where should i put /sys/class/backlight/panel0-backlight/brightness as the slider in lipstick is not changing the screen brightness14:55
T42<elros34> nice. Only kernel v22 without android base? mce handles backlight so check it. Maybe add few -v arguments to  mce.service.15:39
T42<Mattia990> I'm not using that. As a base right now i'm using a rom called evolution based on android 11. So i took the kernel from that, added initramfs and loop.c patches and it worked (it is this: https://github.com/sailfishos-cepheus/android_kernel_xiaomi_sm8150)15:50
T42<Mattia990> I see in some sony it is handled like this: https://github.com/mer-hybris/droid-hal-img-boot-sony-murray/blob/master/rpm/droid-hal-pdx225-img-boot.spec#L9C1-L10C3215:50
T42<Mattia990> But i'm not using that droid-hal-img-boot-*15:50
T42<Mattia990> What if i add the define in droid-hal-version-*? (re @elros34: nice. Only kernel v2...)15:50
T42<Mattia990> I'm seeing this in journalctl15:51
T42<Mattia990> 15:51
T42<Mattia990> [root@MI9 defaultuser]# journalctl -u mce -b --no-pager | grep -i backlightlug 05 17:10:04 MI9 mce[1752]: modules/display.c: mdy_display_type_get_from_sysfs_probe(): several backlight devices present, choosing the first usable one[root@MI9 defaultuser]#15:51
T42<elros34> that spec is for initramfs not useful for you.15:51
T42<elros34> use: systemctl stop mce; mce -Tqqq  -l modules/display.c:*brightness*15:54
T42<elros34> or just modules/display.c:*15:55
T42<Mattia990> I see this: https://paste.opensuse.org/pastes/19ec34538d7d15:56
T42<Mattia990> And this: https://paste.opensuse.org/pastes/14b473a88de715:57
malhave you tried with adaptive brightness disabled, from settings->display15:58
maljust to be sure that the als sensor is not causing the issue15:58
T42<elros34> I think it uses /sys/class/backlight/backlight/brightness. Is it correct?15:58
T42<Mattia990> No, the correct one is /sys/class/backlight/panel0-backlight/brightness15:59
T42<Mattia990> I tried with both, disabled and enabled (re @SailfishFreenodeIRCBridgeBot: <mal>have you tried ...)15:59
T42<Mattia990> And yes, in the log i see that it tries to use the wrong one, without panel016:00
malhttps://github.com/sailfishos/mce/blob/master/inifiles/backlight.ini16:00
maladd something like /etc/mce/70-backlight.ini with the [Display] section with suitable BrightnessDirectory16:01
T42<Mattia990> It is working, thank you!16:04
T42<elros34> just curious, isolate_lru_page is still there in this kernel?16:06
T42<Mattia990> I don't see it in dmesg and i didn't apply the patch16:12
T42<b100dian> rinigus: gps stopped working, pretty sure we need piggz' AIDL disablement workaround from 0.3.1 https://github.com/mer-hybris/geoclue-providers-hybris/pull/5316:23
T42<b100dian> I'm adding that to our devel16:23
rinigusb100dian: fingers crossed16:26
T42<b100dian> I've also changed the meta https://build.sailfishos.org/project/meta/nemo:devel:hw:sony:nagara to point again to 5.1 instead of latest, not sure if this was the cause the the gbinder unresolvable.. 🤷‍♀️16:38
malwhat is it with some devices creating broken aidl gps interface16:39
rinigusmal: we don't know that yet on nagara - b100dian will have to test if the fix worked.16:50
T42<b100dian> mal: rinigus: it started to work after disabling AIDL..17:20
T42<b100dian> I did not debug it, just wanted to look at what changed in the update and noticed the 0.3.1 workaround17:21
T42<nightishaman> @rinigus, does nagara support esim?18:21
T42<nightishaman> i mean the sailfishos build18:21
T42<nightishaman> mal: You got an idea what I can do, last time I checked hwc is getting no messages from the minimer18:35
T42<nightishaman> https://pastebin.com/HF5Kmt8E18:39
T42<nightishaman> hmm this sounds bad18:39
T42<elros34> permissive=1  so it doesn't matter18:52
T42<b100dian> @nightishaman yes, nagara has esim support. There are some wrinkles, like adding some of the providers doesn't work. There is a thread about what works and doesnt: https://forum.sailfishos.org/t/esim-provider-and-hardware-support/2952019:08
T42<nightishaman> cool, so i can use that phone as my secondary already19:08
T42<nightishaman> will try flashing ur stuff later19:08
T42<nightishaman> question is why is hwc not receiving anything, only two ioctl to BINDER_READ (re @elros34: permissive=1  so it ...)19:44
T42<elros34> do you even have correct env when running minimer? Do you see hwc initialization in logcat. maybe test_hwcomposer shows something19:46
T42<nightishaman> I did have correct env, i remember that and hwc initializes yes, test_hwcomposer segfaults19:51
T42<nightishaman> @b100dian Installed it, how do I install waydroid?19:59
T42<b100dian> err I thought your question was about esim :))?20:00
T42<b100dian> I don't think waydroid is available fro Android 14 base20:00
T42<b100dian> Which reminds me I have a touchscreen problem on waydroid 12 to debug on sake :-S20:01
T42<b100dian> Or maybe Jolla will make App support available for porters20:02
T42<b100dian> When they're out of the woods with flashing J2s, of course!20:03
T42<nightishaman> oof, i wanted waydroid lol20:05
T42<nightishaman> can i somehow install waydroid manually anyway and try it or is it locked? (re @b100dian: When they're out of ...)20:22
T42<b100dian> I don't think locked is a good description. You can install waydroid from chum, and when you init that it will probably download Android 12, but then when that version starts to boot and connect outside of the lxc container to the real vendor services, it will not work. You need a Waydroid 14 which is not yet published (tested, done, anything).  I think 13 is the latest20:26
T42<nightishaman> hmm20:28
T42<nightishaman> sad story20:28
T42<nightishaman> without waydroid it cant become my secondary20:28
T42<nightishaman> back to my port, where can I find the env variables for minimer again?20:28
T42<b100dian> 4th bullet here https://github.com/mer-hybris/hadk-faq#41lipstick-segfaultsno-display20:30
T42<nightishaman> https://pastebin.com/yZEk4D1420:33
T42<nightishaman> strace of hwc with test_hwcomposer20:34
T42<nightishaman> coming soon with minimer20:34
T42<nightishaman> with minimer: https://pastebin.com/S597CCpN20:35
T42<nightishaman> we got strace output this time20:35
T42<nightishaman> im excited20:36
T42<nightishaman> thanks b100dian for the link20:37

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