Saturday, 2026-07-11

sharks@mister_magister did you have any ofono/connman problems with Miami / Lineage22 base? Seems if I set `%define android_version_major` to `14`, I can get VoLTE and MMS, but if I set it to `15` I can't. Either way I can't get cellular internet.00:34
Mister_Magisterno00:34
Mister_Magisterwhat kind of problems?00:34
sharksI dunno. The output of dbus commands is showing that the SIM card is working fine, it can see all the APNs it needs and everything, but connman is not picking them up. `connmanctl technologies` is completely missing any mention of cellular, `ip a` isn't listing routes. Hardly any mention of ofono at all in journal. But SMS works.00:37
Mister_Magisteridk works for me00:37
sharksYeah, bugger. It must be a device specific problem I guess00:38
sharksI think I'm going to go back to setting the android version major to 14 again just to make it work, and try to work around any other problems that causes. Might be easier00:40
*** n2klb_ is now known as n2klb01:11
*** n2klb_ is now known as n2klb02:05
malthe only relevant difference in droid-hal-config submodule is gbinder api level configuration which is on device at /etc/gbinder.conf02:06
malyou can override that in by adding a working file to sparse/etc/gbinder.conf in your config repo02:07
sharksChanging the gbinder apilevel value from 35 to 30 on device doesn't fix VoLTE. Do I need to do that before the first boot?04:44
sharksNope, that doesn't work either04:54
T42<Mattia990> I think the libaries errors i was having was due the missing ENV. By the way i still have the SIGBUS error when running pulseaudio (https://paste.opensuse.org/pastes/88a4fedd0bfa)07:31
T42<Mattia990> Sometimes it starts but with NULL sink (re @elros34: or was it only becau...)07:31
T42<Mattia990> And with NULL sink i can't hear any sound coming from the speaker08:53
T42<Mister_Magister> well obviously08:53
Mister_Magisterit's a null sink08:53
sharksOkay - trying to debug sensors now. I learnt that for AIDL sensors I need the latest 0.15.2 version of sensorfw so I compiled that and threw it on the device, which helped progress things along a bit but it's getting stuck with `hw_get_module() probe failed`. Output of running it manually -> https://paste.opensuse.org/pastes/e4e333547bbd09:25
sharksAlso strace of what it's looking for --> https://paste.opensuse.org/pastes/644f4a80c5a9, I note that `/vendor/lib64/sensors.ssc.so`, the only sensor.*.so file on my filesystem, is missing from this output. I think that's the problem but I don't know how to fix it.09:26
T42<elros34> @Mattia990 add more -v otherwise you will have to gdb it which might be tricky09:27
T42<elros34> @sharks what spec file dd you use for building sensorfw plugin?09:30
sharks@elros34 sensorfw-qt5-hybris.spec09:31
T42<elros34> that is for old android versions only09:31
sharks...Really? I was going off what @mal said here: https://piggz.co.uk/sailfishos-porters-archive/index.php?log=2026-04-10.txt#line57609:32
T42<elros34> ok didn't follow this but hw_get_module doesn't seams right09:34
sharksSo you suggest trying to build the sensorfw-qt5.spec instead? I can try that I suppose09:35
T42<elros34> no, binder one. If your right that link you will see hybris was mistake09:37
T42<elros34> read*09:37
sharksOh balls, you're right. Sorry, I was struggling to follow the conversation too. And now I've already started building the wrong spec file again!! I will wait for it to finish and then build the binder version. Thanks09:39
sharksWow the binder version builds way quicker09:44
T42<Mattia990> I'm checking with gdb regarding the SIGBUS, i don't know if it can be this the problem, but there is a function that seems to point to selinux stuff. I didn't do this alone because i don't know about gdb, but maybe it can be useful09:52
T42<Mattia990> 09:52
T42<Mattia990> open_output_stream     = valid address09:52
T42<Mattia990> close_output_stream    = valid address09:52
T42<Mattia990> open_input_stream      = valid address09:52
T42<Mattia990> ...09:52
T42<Mattia990> create_audio_patch     = "selinux."09:52
T42<Mattia990> release_audio_patch    = "so:libsy..." (re @elros34: @Mattia990 add more ...)09:52
T42<Mattia990> https://paste.opensuse.org/pastes/eb93f855894509:53
T42<elros34> so -vvvvvvvv didn't reaveal anything?09:59
T42<Mattia990> I'm not seeing something strange: https://paste.opensuse.org/pastes/fff8a4b0f01b10:02
T42<Mattia990> Maybe this: Opened hw audio device version 2.0 (This module compiled for API 3.1, Android 11.0.0) ? (re @elros34: so -vvvvvvvv didn't ...)10:02
T42<elros34> maybe worth to look for some of quirks in pulseaudio-modules-droid readme10:10
T42<Mattia990> In my case, as i'm on android 11, is it correct https://github.com/Halium/android_vendor_halium_hardware the halium-10.0 branch? Or should be halium-12.0?10:11
T42<elros34> I am not sure but if it builds then I guess 10 is fine10:12
sharks@elros34 didn't seem to go much better with the binder version over the hybris version, I still see the same hw_get_module() probe failed --> https://paste.opensuse.org/pastes/b71ba7f5797610:17
sharksand ot10:17
sharksand it's still not looking for `/vendor/lib64/sensors.ssc.so` --> https://paste.opensuse.org/pastes/fa6010ff325610:18
T42<elros34> are you sure you have installed the right one?10:18
sharks`rpm -qa` outputs "hybris-libsensorfw-qt5-binder-0.15.2-0.aarch64"10:19
sharksSo I have to assume it is the right one10:20
T42<elros34> did you git clean -xdf sources when switching from hybris to binder?10:20
sharksNooooo I just ran `build_packages.sh --mw=https://github.com/sailfishos/sensorfw --spec=rpm/sensorfw-qt5-binder.spec`10:21
sharksIf I deleted $ANDROID_ROOT/hybris/mw/sensorfw and started again would that work?10:22
T42<elros34> hope so because I have impression you are still using hybris one10:23
sharksSo I re-ran the build_packages.sh, changed patterns to have "Requires: hybris-libsensorfw-qt5-binder" instead and built a new image10:24
T42<elros34> but how did you choose that specific branch you were talking about?10:24
sharksAnd confirmed on the new image with `rpm -qa` that the binder version was installed10:24
sharksI didn't choose that specific branch because those changes have since been merged into the master branch10:24
T42<elros34> ok10:25
T42<elros34> wouldn't be faster to copy rpm and install on device?10:26
sharksProbably but I'm not a smart person and figured the best way of being truly sure some remnant of the old one wasn't still there would be to make a new image10:26
T42<elros34> btw I guess binder one is default in patterns. Did you have something else there?10:27
sharksBefore in patterns it just had `hybris-libsensorfw-qt5` not `hybris-libsensorfw-qt5-binder`10:28
T42<elros34> IIRC same thing10:28
sharksoh10:28
sharkstold you I wasn't smart10:29
sharksOkay so delete hybris/mw/sensorfw and build it again to be completely sure it's not still the hybris version?10:29
T42<elros34> cmon don't be so hard on you, no way you could know this10:30
T42<elros34> yeap delete or clean sources I think there was such a issue long time ago when switchin backend10:31
sharksYeah okay thanks, I'm trying my best!! Have rebuilt it, copied the new rpm to device, installed with `pkcon install-local hybris-libsensorfw-qt5-binder-0.15.2-0.aarch64.rpm`, and got new output! No longer have "hw_get_module() probe failed" --> https://paste.opensuse.org/pastes/2a6041de740410:37
sharksBut it still dies: https://paste.opensuse.org/pastes/7e637db5aa6210:38
sharksOh logcat is being spammed with "Unable to set property "ctl.interface_start" to "android.hardware.sensors@X.X::ISensors/default..." again, I thought that went away after I installed sensorfw-qt5-hybris but its back now with the binder one. It shouldn't be looking for these at all because they're HIDL not AIDL is my understanding10:52
T42<elros34> play with binder-list on /dev/(hw)binder10:58
T42<elros34> increasing logs verbosity in sensorfw should also help10:59
T42<elros34> you should mask service if you are stating it manually11:00
sharksAlright forgive me but I just went back to check for myself and I definitely don't see those errors if I use the hybris version, but anyway I'll put the binder version back on and "play with binder-list"11:03
sharksOkay `binder-list -d /dev/hwbinder` returns a ton of stuff and `binder-list -d /dev/binder` returns nothing11:12
sharksIf it matters the exact output is here --> https://paste.opensuse.org/pastes/254d849e1dfd11:13
sharksBut to your point given that I believe the sensors to be AIDL I think you're trying to prove they should show up in the output of the /dev/binder result?11:14
sharksI have also masked sensorfw as requested and run it manually at higher verbosity --> https://paste.opensuse.org/pastes/3698fb982dfa11:17
malsharks: do you have suitable volte plugin installed?11:36
sharks@mal I reverted android_version_major to 14 and volte registers now, but I have no sound in calls I'm yet to debug that. No matter what I did I could not get volte to register with android_version_major set to 15, even though the only differences I can find should be /etc/gbinder.conf and keymaster vs keymint11:39
malsharks: another possible reason is that aidl dummy_netd setting in /etc/sysconfig/dummy_netd11:42
sharksYou know that's probably totally it, considering its file contents are "DUMMY_NETD_ARGS=--device=/dev/binder" and @elros34 has just helped me prove that /dev/binder is completely empty11:46
malif binder is empty that mean you have wrong gbinder api level in use11:49
sharksYep, adding that file to my current working install on device has broken volte registration11:49
malyou should fix gbinder api level11:49
sharksOh? How do I learn the right gbinder api level?11:49
maltry different value, possible values are https://github.com/mer-hybris/libgbinder/blob/master/src/gbinder_config.c#L189 35 or below, try checking binder-list -d /dev/binder after changing the config value11:52
sharksDo I need to reboot or restart anything first, or just change the value and run `binder-list`?11:53
malno need to reboot11:53
sharksDang, I had so much hope11:54
sharksI have tried all of those values, saved the file and run binder-list in between each attempt, but never got any output11:54
sharksOoh scratch that11:55
malis servicemanager process running?11:55
sharksMaybe I made a typo, I tried again and with apilevel 35 it works!11:55
sharksI have sensors!!!11:56
sharksmal you are a legend among men11:56
malso using android_version_major should be fine after you remove that dummy_netd config file11:56
mal*android_version_major 1511:57
sharksYes, I will do that, thankyou.11:57
malremoving files can be done with delete_file.list way11:57
sharksNow I just need to fix mobile data because connman does not see a cellular technology for some reason, and fix audio in calls11:57
malhttps://github.com/mlehtima/droid-config-fp511:57
malyou can see two delete_file*.list files there11:58
sharksI have seen you and magister discuss delete_file.list, I'll do it that way sure thanks11:58
malto remove that dummy_netd config file you need to use delete_file_$DEVICE.list11:58
maldelete_file.list won't work in that case, has to have the device codename11:59
sharksSure, thanks I'll do it that way11:59
sharksNot to be greedy but while I've got you, you don't know any leads I could chase to find out why `connmanctl technologies` doesn't list "cellular"?11:59
sharksIf you can't help I'm just glad I've got sensors, been fighting that for a week now so thanks again12:00
sharkscan confirm delete_file_$device.list worked, VoLTE fixed with android_version_major 1512:10
sharksAnd now I've got the latest sensorfw the aidl sensors are working great out of the box12:11
sharksthis thing is so close to actually usable now12:11
malso mobile data is not working?12:12
sharksNo, not at all12:13
maldo you see anything from ofono in journal?12:15
sharksofono related things from journal --> https://paste.opensuse.org/pastes/0f14971b2d3112:19
sharksI'm no expert but I don't think any of that is to do with mobile data12:24
sharksWhat I do know is that `dbus-send --system --print-reply --dest=org.ofono /ril_0 org.ofono.ConnectionManager.GetContexts` spits out the right APN for mobile data in "/ril_0/context1"12:25
malwhich interface are you using?12:30
malcheck binder-list -d /dev/hwbinder for anything related to radio12:30
sharksradioInterface = 1.512:30
malok12:31
sharksFair bit of radio stuff in hwbinder --> https://paste.opensuse.org/pastes/08155fbe24b412:31
maltry adding defaultDataProfileId = 65535 to /etc/ofono/binder.d/*.conf12:34
sharksHmm I added it to /etc/ofono/binder.d/qti.conf under [Settings], not sure if that was the right thing to do but after a reboot it has not worked12:36
malwhere do you set radioInterface = 1.5?12:38
malit seems you are not doing that correctly12:39
mal[gbinder-radio] Connected to android.hardware.radio@1.2::IRadio/slot112:39
T42<welhone> where can you find list of all the latest SFOS ports and community editions?12:39
sharksin /etc/binder.d/$device.conf12:39
malshow the file?12:40
maland that is wrong12:41
sharksrepo not up to date with latest changes but https://github.com/sharks-dev/droid-config-pdx225/blob/master/sparse/etc/binder.d/pdx225.conf12:41
malhttps://github.com/mer-hybris/droid-config-sony-murray/blob/master/sparse/etc/ofono/binder.d/murray.conf12:41
sharksDang, I have the location wrong?12:41
malthose should be in /etc/ofono/binder.d/ not /etc/binder.d12:41
malno wonder you have problems12:42
sharksI believe that's what they call a "rookie mistake"12:42
sharksThanks for helping mal, I've just fixed that on device and rebooting now12:42
malI sometimes do such mistakes also12:44
sharksHmm I may have made a mistake but that hasn't actually fixed it12:44
sharksI moved it to /etc/ofono/binder.d/pdx225.conf but still no mobile data with or without defaultDataProfileId = 6553512:45
sharks`connmanctl technologies` should list "cellular" shouldn't it, or am I barking up the wrong tree? It still only has ethernet, wifi, bluetooth and gps12:46
sharksAnd mobile data option in sailfish settings is greyed out and disabled12:46
malany difference in ofono output12:48
sharksDoesn't seem like much difference --> https://paste.opensuse.org/pastes/8ac498bd979912:49
malhmm, do you have both sim slots enabled?12:57
sharksYes, is that a bad thing? It's a dual sim phone after all but to be fair I personally only use one sim12:57
malso what is xperia 10 iv?12:58
maldoesn't it only have one physical sim slot?12:58
sharksNo mine is XQ-CC7212:58
malah12:58
sharksI think XQ-CC52 only has one physical sim, but I have two12:58
malok, then that is not the problem12:58
sharksCool, okay12:59
sharksBut it could be a problem if someone with a XQ-CC52 tried to use this port?12:59
malyes13:00
malat the moment eSIM slots are a problem if there is no valid profile there13:01
T42<Mattia990> I fixed my pulseaudio problem, now i have audio output from main speaker and headphones working, also mic13:01
T42<Mattia990> I didn't test calls13:01
T42<Mattia990> I opened an issue here with what I did13:01
T42<Mattia990> https://github.com/Halium/android_vendor_halium_hardware/issues/213:01
sharksSo just get rid of /etc/ofono/binder.d/dual-sim.conf and an XQ-CC52 would be happy? Notwithstanding whatever the issue actually is with mobile data?13:02
malalso /etc/ofono/ril_subscription.d/dual-sim.conf13:02
sharksAh of course13:02
sharksShould there be something in the ofono output that indicates mobile data is working, or are you just looking for some error message?13:04
mallooking for error messages13:06
sharksAnd it is most likely ofono at fault you think?13:08
malnot sure13:15
maldo you see anything interesting in output of /system/bin/logcat or /system/bin/logcat -b radio13:16
sharksSeems just as devoid as everything else in regards to mobile data --> https://paste.opensuse.org/pastes/13a2cba9d4f813:18
maldo you see anything about waiting something in /system/bin/logcat ?13:20
maldid you try removing the dual-sim things already?13:22
malon device first13:22
maland don't add the defaultDataProfileId13:22
sharksNot sure this is helping you with anything, but re: waiting... https://paste.opensuse.org/pastes/b9f7c2359a2713:23
sharksGive me a moment I'll remove dual sim13:23
malalways grep with -i13:25
sharksOh dual sim did it13:25
sharksSorry, did not know about `grep -i`13:26
sharksWell I can live with no dual sim, but I wonder why that broke it13:26
malyes, very odd13:27
malwould need some ofono debug logs probably for that13:27
malor maybe it didn't like that you had dual sim ofono but not installed jolla-settings-networking-multisim13:28
malif your patterns are correct13:28
sharksAh, yes the patterns are correct. That might do it13:29
malwhile at it maybe enable some other things, you have nfc disabled, also uncomment that  mapplauncherd-booster-silica-qt5-media13:29
malin patterns-sailfish-device-configuration-pdx225.inc13:30
sharksI also need to put fingerprint in there too at some stage13:30
malfor nfc to work you need https://github.com/mer-hybris/droid-config-sony-murray/blob/master/sparse/etc/libncicore.conf13:31
sharksOkay sure, thanks mal!13:32
sharksI am glad to have some progress again, it's been a while. You're a lifesaver13:33
sharksIf I can fix audio in calls now I will have a device functional enough to put back in my pocket, but it is getting close to midnight again so perhaps I should leave that challenge for another day13:34
Mister_Magistermal: i just ran my 3.4 device's kernel through latest mer_kernel_check, do you think any of those are critical for 5.1? https://paste.opensuse.org/pastes/f4a7490a7c6f13:58
Mister_Magisterit doesn't seem so to me but thought i'd ask13:59
Mister_Magisternone of those sound like issuse I've encountered14:00
Mister_MagisterWARNING: CONFIG_RFKILL is invalid hoho14:01
Mister_Magisterbut comment says its for bluebinder14:01
malI think those might be for vpn use or something14:05
Mister_Magisteryeah14:05
Mister_Magisteror if you're connecting your ISP provided ETTH directly to your phone14:06
Mister_Magisterthere's gotta be madman who tired that14:06
Mister_Magistermy isp gives me PPPoE so i could do that xd14:07
T42<Mattia990> Is this still working for fingerprint support or is there another way to make it work? (re @Mister_Magister: @b100dian ping about...)14:35
Mister_Magisterthis was discussion about in-screen fingerprint, fingeprint alone is done in slightly different way14:36
T42<Mattia990> Yes, in my case is in-screen fiingerprint, xiaomi one14:36
Mister_Magisterwell good luck with that14:37
Mister_Magisterfor the record, nobody made in-screen one to work14:37
Mister_Magisteronly in like test environment14:37
T42<Mattia990> Ahhh, that's good, so i think my phone will live without it14:37
Mister_Magisterjolla would have to add API to draw circle at lock screen, which obviously, will only happen if they get device with in-screen fingerprint14:39
T42<Mattia990> Mister_Magister i read you were helping a guy with the bzip2 to gzip for flashing resulting zip in recovery.15:13
T42<Mattia990> I'm trying to read hadk hot to understand how to implement it. As far as i understand i need to modify the installer script and just the rpm/dhd/helpers/build_packages.sh to change the file extension, right?15:13
Mister_Magisternah i didn't do gzip conversion instead i create image file and flash that15:13
Mister_Magisterbut yes15:14
Mister_MagisterI think15:14
Mister_MagisterI never did it15:14
Mister_Magisteryou probably need to modify droid-configs too15:14
T42<Mattia990> Yeah, i saw that script you made, is it compatible with all the phones?15:14
Mister_Magistershould be, i haven't tested all phones15:14
Mister_Magisterits nicer in my opinion becaues it ensures that filesystem is not encrypted and it's filesystem type we expect15:15
Mister_Magisterif you want to implement my thingie i can help15:19

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