Wednesday, 2022-06-01

T42<edp_17> Hi all! Have you ever experienced that shorly after lipstick started, the / partition (including /home) suddenly became read only?06:41
*** spiiroin_ is now known as spiiroin09:29
Thaodanvoidanix[m]: Are you there?10:23
voidanix[m]pong Thaodan10:23
ThaodanCan you try something for me? I've been tinkering around why kumano needs miniaudio policy10:24
ThaodanDoes the camera lock up for you if you record a video, take a picture and then try to record one again?10:25
voidanix[m]lemme see10:25
voidanix[m]doing videos -> photos does lock up the camera, yes10:26
Thaodanvoidanix[m]: Ok I hoped this was gone in A11 with the new pa module.10:28
ThaodanThe issue is that jolla-camera (or any camera app I guess) spawns a new player instance this instance than asks for media.audio_policy.10:30
ThaodanIf I remove the maxOpen and Active count on this line in the audio policy:10:32
Thaodan <mixPort name="record_24" role="sink" maxOpenCount="2" maxActiveCount="2">10:32
ThaodanThe lockup is gone but the nuplayers still asks for the service10:33
voidanix[m]So the crash is not supposed to happen with miniaudiopolicy?10:57
ThaodanNo but miniaudiopolicy just starts normal audiopolicy service which shouldn't happen as it can change the audio policy in Sailfish.10:58
voidanix[m]Also does lena's camera also break this way?10:58
T42<edp_17> Hi all. I am a bit confused now about whether I need to use "ofono-ril-binder-plugin" or "ofono-ril-binder-plugin".11:26
T42<edp_17> When "ofono-ril-binder-plugin" is instaled, rild and ofono are happy (not crashing) but there is no telephony at all.11:27
T42<edp_17> However, when I installed "ofono-ril-binder-plugin", ofono did start to complain about and : "Can't load /usr/lib/ofono/plugins/*.so".11:29
T42<edp_17> Which one should I use then?11:29
T42<edp_17> I don't have /dev/socket/rild11:29
T42<elros34> yes:) ofono-ril-binder-plugin or ofono-ril-binder-plugin?11:33
T42<edp_17> Ah, stupid copy/paste. :)11:36
T42<edp_17> So, with "ofono-ril-binder-plugin" it was okay, then with "ofono-binder-plugin" it started to complain.11:36
T42<edp_17> According to the chat history, based on the error I am getting "Unknown RIL transport: binder", I should use "ofono-ril-binder-plugin".11:37
ThaodanWhich Android version?11:37
T42<edp_17> A10 (Los 17.1)11:37
ThaodanI mean which stock Android version, from which version did it start?11:39
ThaodanOlder devices use the legacy ril plugin, newer can use binder plugin11:40
T42<edp_17> The last officially android the device got was android 5.11:41
Thaodanthen the ril plugin11:42
Thaodanthe blobs are probably from that release still.11:42
ThaodanSailfish OS also needs proper cgroup support which will be hard with such an old kernel.11:43
T42<edp_17> Thaodan : So, the official android version, and not the base that we use for the port, dictates which plugin should be used.11:45
T42<edp_17> So, the real question is why I don't have /dev/socket/rild ?11:49
T42<edp_17> If I use ril plugin, I should have that, right?11:49
Thaodanedp_17: Not really the Android version but the blob version the thing is that the blobs can't really be updated unless its the vendor so if you use aosp or los your blob version stays as old as it was.11:50
T42<elros34> probably adaptation was updated and you need one of binder plugin. DIdn't you already confirm it with lshal?11:51
T42<edp_17> I see. Thanks. (re @SailfishFreenodeIRCBridgeBot: <Thaodan>edp_17: Not...)11:53
T42<edp_17> @elros34 : No, I didn't yet confirm that. lshal? what's that and how to use?11:54
T42<edp_17> Okay, I was wrong.11:55
T42<edp_17> I did /system/bin/lshal | grep radio.11:55
T42<edp_17> It gave me this:
T42<elros34> did you try to install ril-binder-plugin from adaptation-common repo or you build some latest from github?11:56
T42<edp_17> Have installed from adaptation-common. I didn't build that.11:57
T42<edp_17> You know what's "funny" now? I've installed "ofono-ril-binder-plugin" back and ofono still complains about "Unknown RIL transport: binder".11:58
T42<elros34> didn't you messup something in /etc/ofono?11:59
T42<edp_17> No, I just installed "ofono-binder-plugin" then restarted ofono, then installed "ofono-ril-binder-plugin" and restarted ofono again.12:00
T42<elros34> I wonder why did you install ofono-binder-plugin?12:01
T42<edp_17> Because I though that's the one I needed.12:02
T42<edp_17> This is the ril_subscription.conf :
T42<elros34> not sure which one you should use but  here its still ofono-ril-binder-plugin: Only later ports pulls ofono-binder-plugin.12:05
T42<elros34> about config, why don't you use default one, that should be first thing to try:
T42<edp_17> I've replaced my ril_subscription with this one but (after ofono restarted) I still have the same error.12:09
T42<edp_17> ofonos -n -ddd :
T42<edp_17> *ofonod12:11
T42<edp_17> ops, there was more in log just didn't wait for long enough. Here :
T42<elros34> have you checked logcat?12:20
T42<elros34> what plugins do you have now installed: zypper se -s ofono?12:23
T42<elros34> you seems to have old ofono and ril plugin instead binder. Which sfos version is that?12:37
T42<edp_17> @elros34 : zypper se -s ofono:
T42<edp_17> sfos
T42<edp_17> But custom ofono version is used (the one I build for treltexx). Should I try the other one (1.28+git3.1-1.12.1.jolla)12:41
T42<elros34> why not latest sfos version and why custom ofono?12:41
T42<elros34> you don't even have ofono-ril-binder-plugin  installed which we were talking about12:42
T42<edp_17> Because I used the latest one but didn't work, and I though would try the other one that worked for the treltexx.12:42
T42<elros34> if you buld custom version than you need to take care of matching plugins so it's not worth12:42
T42<edp_17> Oh, sorry, wrong list was uploaded. Here is the recent one :
T42<edp_17> I didn't know that, but that custom ofono still works on treltexx (sfos (re @elros34: if you buld custom v...)12:44
T42<elros34> looks like that ofono is fake 1.2912:44
T42<edp_17> Yes, that how I managed to install my version over the other one.12:44
T42<elros34> so this lead to all confusions, you should mention that. Remove it and install ofono packages only from jolla's repos12:45
T42<edp_17> Okay.12:46
T42<elros34> @lbt: hi, could you tell me how to remove leftover from deleted project?
T42<edp_17> @elros34 : I've installed ofono from official repo and after restart the service the icon appeared. I put a SIM into it to see whether it works. :)12:50
T42<edp_17> @elros34 : Yeah, telephony is working now (calls/text in/out, haven't tried data yet.) Thanks for your help!12:57
T42<cryptodas> Back to my logcat output, I steel see errors like this one:12:58
T42<cryptodas> ```12:58
T42<cryptodas> SELinux : avc:  denied  { add } for interface= ... permissive=1```12:58
T42<cryptodas> 12:58
T42<cryptodas> I found elros34 message that it should be treated just as spam. May be there is a way/instruction to get rid of them? (re @cryptodas: @elros34, thank you,...)12:58
T42<elros34> @edp_17 nice, just to confirm you have now ofono-ril-binder-plugin not ofono-binder-plugin?13:16
T42<elros34> @cryptodas audit=0 in kernel cmdline13:17
T42<elros34> but not sure it will remove all these warnings but at least it should get rid of audit spam13:18
T42<edp_17> @elros34 : Yes, I have ofono-ril-binder-plugin. However, something is still not right. I've tried to send a text message and the device hang. I rebooted and now ofono is crashing:
T42<cryptodas> @elros34 , that's already set. Ok, there are not too many errors, I can ignore them15:01
T42<edp_17> @elros34 : Dispite of those errors (two of them gone after flight mode on/off), telephony do works (calls/texts in/out and data). Many thanks for your help again. :)15:11
T42<edp_17> Now, it seems only BT and Camera need fixing. (Oh, and for some reason audio is not routed to headphone. I've tried both jack-match/device and state file in accessories.ini but none of them worked.) I do a fresh build including all fixes so far and will try these three again.15:14
T42<cryptodas> Hmm, I'm facing strange usb errors. When I connect my HTC U11 to the host, dmesg gets filled with lots of such messages:19:11
T42<cryptodas> *usb 1-9: device descriptor read/64, error -7119:11
T42<cryptodas> * usb 1-9: device not accepting address 110, error -7119:11
T42<cryptodas> * usb 1-9: Device not responding to setup address.19:11
T42<cryptodas> * usb usb1-port9: attempt power cycle19:11
T42<cryptodas> Looks like it means EPROTO — Protocol error. It's same for the recovery, Sailfish and Android. Of course, no telnet, adb of any other connection. Only after staying booted to Android for some time (along with changing usb settings in developer section and reconnecting the device several time) I got some sort of stable connection in Android on each plug-in.19:11
T42<cryptodas> Could it be Sailfish porting related or it looks like hardware issue?19:12
T42<cryptodas> Of course, I have tried another cable, port and even host19:25
T42<elros34> @cryptodas so you do not have telnet/usb ssh now? Is this also issue whhen you boot hybris-recovery for example?19:53
T42<cryptodas> @elros34, exactly. I tried rebooting android system several times. After each reboot there are about 5 attempts and the device gets connected finally. Last time I checked that it's possible to get adb in recovery/download mode but I haven't dared to flash sailfish kernel again. Feel worried that overwriting the serial number with "Mer boat loader..." could have broken something.21:03
T42<elros34> AFAIK hybris-boot/usb-moded doesn't overwrite anything permanently, it handles usb similar way to android.21:16
T42<cryptodas> By the way after "Mer..." I usually see real device info (HTC U11 and serial number). Is it the same for others?21:21
T42<elros34> Sometimesinit*usb*rc are loaded and can mess up with you usb, that is why I asked whether telnet works in hybris-recovery (before droid-hal-init loads init*rc)21:27
T42<cryptodas> Okay, gonna try21:33
T42<elros34> about /media/sdcard/ mountpoint: what was the reason for label -> UUID change? Is it safe to revert thsi change

Generated by 2.17.1 by Marius Gedminas - find it at!