Wednesday, 2021-02-24

riniguswhile looking into pulseaudio config, I stumbled on https://github.com/sailfishos-sony-tama/droid-hal-configs/blob/master/sparse/etc/pulse/xpolicy.conf#L519 installed on aarch64 device. should probably point to lib64 version, as that's the one we have on the device10:43
riniguspulseaudio tries to load few 32-bit libs in vendor, fails and then doesn't try to get the available 64 bit version. this is according to journal message (below) and strace showing no try to load 64 bit one10:48
riniguspulseaudio[4502]: "/vendor/lib/hw/sound_trigger.primary.sdm845.so" is 32-bit instead of 64-bit10:48
rinigusmal || jusa: any pointers? ^10:48
T42<eugenio_g7> rinigus: try setting HYBRIS_LD_LIBRARY_PATH like this: https://github.com/hybris-mobian/adaptation-fxtec-pro1/blob/bullseye/etc/profile.d/zz-fxtec-pro1.sh10:59
T42<eugenio_g7> In your case both on /vendor I guess10:59
T42<eugenio_g7> But lib64 before lib11:00
rinigus@eugenio_g7: thanks, will try11:04
T42<eugenio_g7> if it works I guess a systemd drop-in on the pulseaudio service should be enough11:05
rinigusYou mean adding that far into systemd unit file?11:11
malrinigus: should not matter probably11:15
T42<eugenio_g7> rinigus: yup, as a drop-in (/etc/systemd/user/pulseaudio.service.d/filename.conf)11:16
malit seems to be quite common that android doesn't have all audio libs for 64-bit version11:25
rinigusmal: in my case, all the libs that failed to load this way are available in 64 bit as well. judging by names.11:26
malhmm, that's odd11:30
malrinigus: did you check strace?11:30
rinigusmal: yes, I did check strace. after writing message "... 32-bit instead of 64-bit" no attempt was made to load from 64 bit location. no idea where it also gets the list of libs and tries to load them. (haven't tested with hybris var, as suggested by eugenio_g7, will try soon).11:32
rinigus@eugenio_g7: running HYBRIS_LD_LIBRARY_PATH=/vendor/lib64:/vendor/lib strace -f pulseaudio -n --file=/etc/pulse/arm_droid_d11:37
rinigusefault.pa > logs/pa.strace 2>&1 did not help. still loading /vendor/lib/hw/sound_trigger.primary.sdm845.so . which I guess is expected assuming that PA is loading by itself..11:37
T42<eugenio_g7> 😐 try also putting /vendor/lib64/hw in the search path11:41
rinigus@eugenio_g7: did already - no difference.11:46
T42<eugenio_g7> oh ok, well it was worth a try11:47
rinigussure it was! thanks!11:48
malrinigus: that needs some checking12:17
rinigusmal: thanks! I am trying to upload strace somewhere, but it is rather large. any idea where the search path for PA libs is set?12:18
malrinigus: can you show the whole strace12:18
malrinigus: you can email it to me if you want12:18
rinigusmal: just a sec. will see where to add it12:18
rinigusmal: it is attached at https://github.com/sailfishos-sony-tama/main/issues/107#issuecomment-78503750312:20
rinigusmal: just to be sure that you see it. in PA config, we have /usr/lib/telepathy/telepathy-stream-engine and not lib64 version.12:32
malrinigus: hmm12:34
malrinigus: which config?12:34
rinigusmal: https://github.com/sailfishos-sony-tama/droid-hal-configs/blob/master/sparse/etc/pulse/xpolicy.conf#L51912:35
riniguslooks to be merged with sparse-10.12:35
rinigusat least I found that on device12:35
rinigusmal: ^12:36
Mister_Magistermal: found this while running test_gps https://paste.opensuse.org/23d482ea as root12:37
T42<edp_17> Hi all. Can somebody help me with sensorfwd, please? When the screen is on, sensorfwd uses more than 60% cpu and the log is flodded with messages "failed to write payload to the socket": https://paste.ubuntu.com/p/j9y4mvpfwf/13:49
T42<edp_17> Galaxy Note (n7000) CM14.1 base, sfos 4.0.1.4813:49
rinigusmal: looks like few PA modules also fail to load: https://dpaste.org/jKUO14:14
riniguslooks like the missing libs are in /usr/lib64/pulse-12.2/modules which are not used during resolution14:24
malrinigus: I'll have a look14:26
rinigusmal: thanks!14:29
T42<adampigg> mal: remember the UCM lib issue too14:37
mal@adampigg that will be fixed14:39
malrinigus: those don't seem to be critical, happens on other devices also, the sound volume issue is known and could be some sony issue14:52
malthere is some idea how to fix it14:52
rinigusmal: I presume that is related to aarch64 / aosp10. as on aosp9 32 bit I had no such issues14:53
riniguslooking forward to fix14:53
rinigusbtw, it is not detecting headphones either14:54
malhmm14:54
rinigusmal: those non-critical errors - this is regarding pulseaudio --dump-modules, right?14:55
malyes14:57
malI get those also for example on xa214:57
rinigusmal: that's right, dump-modules are making the same errors on aosp9/32bit xz2 as well15:00
rinigusshould have checked, sorry.15:00
rinigusmal: but missing libs as only 32-bit versions are tried, that's strange. I guess something in PA sets the path and it is wrong for 64 bit version15:01
malrinigus: more like android side does it15:02
malrinigus: as I mentioned before android often has 32-bit audio server15:02
rinigusmal: maybe. is it also 32 bit server on seine? don't know what it is in AOSP for tama, I must say15:04
malrinigus: looks like there might be another 64-bit bug related to audio routing, also speaker phone mode is probably not working15:05
rinigusmal: haven't got that far, no sim in that phone15:06
rinigusmal: do you have that volume bug in seine as well?15:07
malrinigus: yes15:11
T42<adampigg> whats the volume bug?15:13
rinigus@adampigg: https://github.com/sailfishos-sony-tama/main/issues/10715:14
T42<adampigg> ok, much different to the pinephone volume bug15:15
malrinigus: try restarting ohmd and see if headphone detection works15:16
riniguswill do15:17
malthat helped for me15:17
rinigusmal: restarting ohmd while having headphones in helped.15:25
malrinigus: should work fine after that15:28
rinigusmal: yes, inserting and removing reroutes sound accordingly.15:31
rinigusso, sounds like ohmd needs to be primed with headphones15:31
malrinigus: no need to have headphone in when restarting ohm15:32
malthere is some timing issue at boot which causes initial detection to fail15:32
rinigusmal: ahh, that's better and should be easier to fix :)15:33
T42<Verevka86> https://paste.ubuntu.com/p/3gYjxwTxJN/17:56
T42<Verevka86> Please help17:56
T42<Verevka86> Not build aarch64😔17:57
malremove the repo from .ks file manually18:01
T42<Verevka86> Boot up Xiaomi MI6 hybris17. 1 aarch64 😍19:28
rinigus:)19:40
riniguslooks like I am missing miniafservice (miniaf not starting on boot). how do you package that?20:22
*** daniel is now known as Guest1828220:37
malrinigus: if you mean 17.1 base, do not use miniaf20:43
rinigusmal: yes, I mean aosp10. find it rather confusing with these mini services. right now I have minimediaservice and minisfservice20:44
malrinigus: miniaf is not used anymore, it was replaced by https://github.com/mer-hybris/audiosystem-passthrough20:44
rinigusmal: that seems to be running (audiosystem-passthrough)20:45
malyeah20:46
rinigusmal: I have also camera freezing if I switch from video to photo mode. https://github.com/sailfishos-sony-tama/main/issues/11520:47
rinigusany tips for that?20:47
riniguslogs are in the issue20:48
malrinigus: the reason is right there in the logs :)20:51
rinigusmal: media.audio_policy?20:52
malyes20:52
rinigusmal: any clues on why wouldn't it start? or what should provide it?20:53
malrinigus: try adding MINIMEDIA_AUDIOPOLICYSERVICE_ENABLE := 1 to env.mk in droidmedia sources20:53
rinigusmal: will do, thanks!20:54
rinigusmal: getting error on droidmedia compilation20:58
rinigusframeworks/av/services/audiopolicy/service/AudioPolicyService.h:34:10: fatal error: 'mediautils/ServiceUtilities.h' file not found20:58
rinigusI have made the change in env.mk and just fired make hybris-hal droidmedia20:59
rinigussuch file does exist, but for some reason it is not included in the search path.21:02
rinigusbtw, minisfservice and minimediaservice are 32 bit on tama aarch64 build21:06
malrinigus: yes, that's how it's supposed to be afaik21:32
malrinigus: I think I never built audio policy for android 1021:32
malrinigus: found the issue21:34
T42Braillynn was added by: Braillynn22:18
T42<Braillynn> Hello, idk if this is the place to reach out but I'm having some difficulty installing Sailfish OS, I'm at the final step.22:19
malwhich device?22:21
T42<Braillynn> @mal [which device?], Xperia 10 Plus22:21
T42<Braillynn> (Photo, 1280x720) https://irc.thaodan.de/.imgstore/t8PpprzYFx.png It never stops searching device to flash.22:22
maldoes the device led show blue color?22:22
T42<Braillynn> @SailfishFreenodeIRCBridgeBot Yes22:23
malwhat do you see if you run "fastboot devices" in the terminal?22:24
T42<Braillynn> @SailfishFreenodeIRCBridgeBot Well I typed it in, nothing happened. The terminal didn't respond to it.22:26
maldo you have other usb ports on the computer, if yes try another port22:26
T42<Braillynn> Okay, let me try another one.22:27
malusb2 port if you have one22:27
T42<Braillynn> I'm on an Intel Nuc 8th gen, I think all 4 ports are USB 322:27
T42<Braillynn> @SailfishFreenodeIRCBridgeBot I moved to another usb port and it's telling me found I3223, baseband: FAILED, bootloader: waiting22:30
T42<Braillynn> Found 1 devices: CQ3001SQ6Q22:30
T42<Braillynn> Fastboot command: fastboot -s CQ3001SQ6Q22:30
malhmm, interesting, does it still stop after that?22:32
T42<Braillynn> @SailfishFreenodeIRCBridgeBot Not sure what you mean by stop, but phone still has blue led, and terminal looks like I can type more into it.22:32
malbut the flashing doesn't progress if you use the flash.sh script?22:33
T42<Braillynn> @SailfishFreenodeIRCBridgeBot right, it doesn't appear anything is happening.22:34
maltry again22:35
malusb3 and fastboot sometimes has issue22:35
T42<Braillynn> @SailfishFreenodeIRCBridgeBot okay, just want to make sure I do this correct, I'm going into the Sailfish OS folder, opening the location in terminal, plugging in the Xperia 10+ while holding down the up volume button and waiting for the blue led, doing sudo bash ./flash.sh and it should take care of the rest?22:37
malyes, it's known that usb3 sometimes misbehaves, we don't really know why22:39
maldo you happen to have any usb2 hub?22:39
T42<Braillynn> @SailfishFreenodeIRCBridgeBot I do but on another PC.22:40
T42<edp_17> Hi guys. Can I get help with my sensorfwd and/or rild issues, please?22:40
mal@edp_17 what is the issue?22:41
T42<edp_17> When the screen is on, sensorfwd uses more than 60% cpu and the log is flodded with messages "failed to write payload to the socket": https://paste.ubuntu.com/p/j9y4mvpfwf/22:41
mal@edp_17 do you have /run/sensord.sock ?22:43
T42<edp_17> mal: yes.22:44
T42<Braillynn> @SailfishFreenodeIRCBridgeBot I'm going to try on a Raspberry Pi 4, would that work?22:45
malworth a try22:45
mal@edp_17 when did those messages start?22:45
T42<Braillynn> @SailfishFreenodeIRCBridgeBot Wish me luck lol22:45
T42<edp_17> mal: When I wake up the screen.22:45
mal@edp_17 I mean has that issue always been on that port or did it start after update or something?22:46
T42<edp_17> mal: This is a fresh port, my first image for this device.22:47
T42<edp_17> mal: What is also weird, right after I installed sfos, none of the sensors worked. After that I put hw-settings.ini into /usr/share/csd/settings.d/ and some of them started to work but got this behaviour.22:49
T42<edp_17> mal: The usb charging icon and message was incorrect, so I added the /etc/mce/60-battery-udev-devices.ini file.22:50
T42<edp_17> mal: vibra didn't work, so I changed /init.rc to set up the correct user and group for /sys/class/timed_output/vibrator/enable22:52
T42<edp_17> This is all, I changed on the device.22:53
malcan you enable sensors one by one and see if it's some specific sensor causing the issue?22:55
T42<edp_17> mal: How can I do that? (Enable one by one.)22:55
T42<edp_17> How can I disable all of them?22:55
malthat csd config file for example22:59
T42<edp_17> mal: Okay, I'll try. Should I restart something when I changed something in the file?23:00
T42<edp_17> I set everything 0 in hw-settings.ini and restarted sensorfwd service. The device is a LOT snappier, like before I created thar hw-settings.ini.23:05
T42<edp_17> mal: I think got it. When I enabled the LightSensor, I got that error in sensorfwd service and the device became sluggish again.23:11
T42<edp_17> Does it mean that light sensor hardware faulty?23:14
mal@edp_17 not sure23:43
T42<edp_17> I'll install an android and will test there to ensure it works.23:45
T42<edp_17> I have another question. Leds do not work at all and I do not have /sys/class/leds. Do you knwo where else I can look for it?23:46

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