Yes, some people claim this is the case. It is possible but not properly verified.
My Xperia 10 III (that does not suffer from the audio issue) has Android 11.
2 Likes
I could relatively good reproduce the audio issues by installing OsmAnd from F-Droid, having some offline maps downloaded and then navigate a little with that. I do that when cycling and i can be more than sure, that audio is more or less completely dead after some time using it.
Now with sailfish flashed on Android 13 with 12_4.19.v2a blobs according to this setup cited here:
The no sound after GPS use is at least less persistent, so that it is not reproducible anymore.
I will test if it is completely gone and if it will be at least absent for the next 30 days.
Currently, audio works flawlessly after GPS use with the Sailfish on top of ‘Android 13 + 12_4.19v2a blobs’ route, but it needs more testing for robust evaluation.
For my non technical expert mind this is somewhat strange: that the Android fundament on which Sailfish is flashed, has such an impact.
Does this imply that Sailfish 5 on the upcoming Jolla C2 device will not suffer these strange Xperia specific and annoying bugs?
Anyway, deep respect to wetab73 and others who paved the way for this unexpected findings.
I hope that too, that jolla c2 will be bugless, because of jollas direct access to drivers
I’m also curious about that, the Jolla C2 is a lot worse spec wise than an Xperia III or V, but that alone might make it worth getting one after all.
Still curious to see if the V will get it’s share of SFOS issues as well, hopefully not so I can upgrade to that one instead!
The ‘Audio not working after GPS use’ bug is still there on my Xperia 10 iii with Sailfish flashed on top of Android 13 with 12_4.18v2a blobs.
Stopping pulseaudio and ngfd and restarting them as described by @jovirkku does indeed restore audio.
I also have something like up to 7 apps open, none of them appear to be particularly memory hungry.
Audio loss does not happen after every use of GPS, but frequently.
I also used the script ‘Collect Persistent Logs’ as suggested by @jovirkku. Shall I provide the generated log tarball?
I have provoked this audio loss error 3 times and collected all three logs with the gather-logs.sh tool. I just do not know where to send the logs to. Can someone please point to a potential recipient of these logs?
Cool, just sent the logs to Zendesk.
Thanks again for your support
1 Like
In my honest opinion, I think this should be added to the Utilities menu in the Settings.
It is already there in the utilities
Yes, even in the documents: 
1 Like
Hi
I have the same problem (on xperia 10.III, with OS 4.6), and in my case it is not (only) related to GPS usage.
Unfortunately neither Restart audio in the Utility menu or the systemctl method solves the problem. The only solution, till now, is to reboot.
1 Like
This problem still exists in 4.6.0.15 and, for me, whether I’ve used GPS or not seems to make no difference. It happens several times per week. Restarting audio from the utilities menu mostly doesn’t fix the problem. The only thing that brings sound back reliably is a reboot.
1 Like
Yes agree, still there this annoying bug on 10 iii with 4.6.0 15.
I also experience the heterogeneity the previous users described.
This bug seems to br absent on Xperia 10 V, so it is device specific
Unfortunately the 10 V, from what has been announced and reported by others, is nowhere near usable yet as a daily driver and may not be for some time.
Agreed; I’m in the same boat, would like to have a fully functional device, hopefully the IV or the V will be it; I don’t like the C2 size and specs wise; don’t want to go back to LCD; SFOS really shines on OLED.
Wonder if there are any other devices that are specs wise better or similar to a IV or V without all the issues of the III 
The oneplus 6 is smilar, it has oled and 8Gb ram
2 Likes
I experienced it twice recently on my XA2 plus. No sound and could not make a call. Rebooting helps.
Re-installing Windows also helped. Is anyone working to fix this?
2 Likes