When i experienced that once audio through Bluetooth was still working
During the last few months I’ve only used GPS a couple of times. Other than that, it was disabled. Guess what, EACH time I’ve used GPS I had the “total lack of audio” problem within hours after that, and not a single time when not using the GPS. Which leads me to a conclusion that this issue is 100% GPS-related. So in the future I will probably restart the device after each GPS use to avoid the disappearance of audio soon after that, usually in the least desirable conditions, e.g. when one needs to make a call and only hears silence.
1 Like
I just had 25 days of uptime with GPS disabled the whole time to be sure, and audio still broke. I did have a long session of using Bluetooth headset before I noticed this, however. Using Bluetooth hasn’t caused audio loss before AFAICT, but I think it’s worth mentioning.
1 Like
I’m 100% sure that the issue will appear when having the GPS and Android support running at the same time.
Try using Android apps and GPS as usual (a lot), but reboot your device once a week. My hypothesis is that you will not hit the issue, or will hit it a lot less frequently.
Unfortunately things are not as clear, I’ve encountered the issues even with GPS/ location being disabled. Xperia 10 III audio and video problems trigger after a period of time in use - #29 by schmittlauch
I’d like to investigate one possible correlation:
On top of which pre-installed Android OS did you flash Sailfish OS? I have to admit that my device already had Android 13 when I bought it, I had no access to a Windows machine to downgrade back to Android 11 and thus directly flashed Sailfish on top of Android 13. If this is the same for all o you, maybe some updated firmware components or settings that came with the Android 13 OTA from Sony could be at fault?
I did not update my X 10 iii beyond Android 11 62.0.A.9.11 with Android security patch level: 1 February 2022 prior to installing SFOS.
So I installed SFOS on Android 11 and experience the audio/video issue from time to time …
1 Like
As mentioned here a manual restart action has been added to Sailfish utilities.
As this is a bug report tracked by Jolla, I strongly suggest fixing the actual issue rather than adding a manual workaround. How could manually restarting audio services prevent missed calls? People who are using Sailfish as a daily driver have probably implemented some automatic service restart, so who needs a manual restart? What we need is a fix!
2 Likes
I agree. I would say for a phone this is a serious bug. A phone should be designed for phone calls, so this is the most important part of a phone, so this is a highly critical bug, if it makes phone calls unreliable. On the other hand it might be very hard to debug
1 Like
Now i have this bug too.
since the last update to sauna 4.6.0.13
so there is no permanent fix availabe?
very annoying!
restarting the system, or restarting pulseaudio.service helps, but now and then audio and video freeze.
i am not using Bluetooth, but have used positioning in the last time.
haven’t switched positioning on for a long time before (didn’t realy worked before the last update)
I have similar bugs on both my home desktop and my work laptop. Pulseaudio seems to have serious issues.
I can’t imagine positioning being related.
I never had those issues on Arch or Mint. I didn’t compare the version numbers of SFOS and my Arch installation of my laptop. But for me it seems like a bug in the suspend part of the sailfish version.
Please; until you can back that up with any substance at all, refrain from throwing unfounded theories around. (Still a much better theory than it being positioning related).
What i mean with pulseaudio having issues is that A) it can break like this, and B) it is no good at recovering. Most likely the triggering factor here is somewhat SFOS specific.
Same here, can’t remember when I had any problems with sound on my laptops.
they switched to pipewire i guess, maybe that would help for sfos too? but i don’t know if it’s even possible or with how much effort.
It does work. (Meaning you can compile, install, and run it.)
But it’s not very useful as-is.
The SFOS version of PA includes lots of custom bits, some for the Android base support, some for AppSupport (bluetooth, audio), some for some other stuff like routing, profiles, etc. to
enable the MeeGo/Nemo/SailfishOS way of doing audio. (You can see packages like pulseaudio-modules-droid* and pulseaudio-modules-nemo* and some others installed in SFOS.)
While PW claims to be a drop-in replacement for PA, that does not apply to PA plugins/modules. So these would have to be rewritten for PW, or in some cases maybe replaced with something like WirePlumber scripts.
That’s certainly a bit of work, with little guarantee that things will get better in the end.
1 Like
It should be asterisk or hash ?
Thanks
Hash(#) for sure, not asterisk. Thank you!