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
I have to report that I’ve missed several calls with Jolla C2 5.0.0.21 because it didn’t play the ringtone. I was able to restore sounds by restarting pulseaudio and ngfd systemd services as mentioned in this thread. I’m currently running device in “2g only” mode + wifi and usually no apps running. Don’t know howto to reproduce that.
This is an old bug that’s been around for some time. I’ve got it on my Sony Xperia 10 iii running 4.6. There is no fix available but Jolla recently introduced a new function in Settings/Utilities to restart the sound system when this bug occurs. For me this sometimes brings back sound until the bug occurs again. If not, then a reboot will restore sound.
Unfortunately I have experienced the same issue on my Xperia 10 IV (72 variant). SFOS 4.6.0.15 on top of Android 14.
I have missed a number of notifications, my alarm did not sound this morning, and though I noticed a call appear on screen today I was not able to hear the person on the other end after answering, nor were they able to hear me. Upon connecting bluetooth headphones, I was able to hear some keypresses in the phone dialer but sound was inconsistent at best and calls still did not work. A reboot has solved the issue.
Interestingly, though I had not connected the two events until reading this thread, I had extensively used PureMaps for navigation yesterday (approx. four hours of driving with PureMaps running), so this may be related. Perhaps to be safe, I should be rebooting the device every night.
Very unfortunate to hear that the VI is also affected but this bug.
I have it constantly on my Xperia 10 iii and I reboot after GPS use to ensure that I can be contacted.
So far my Xperia 10 V (with 4.6.15 beta on top of Android 14) does NOT have this bug.
It is worrisome to hear that the C2 is alsi affected, because in the end this means it is a Sailfish bug, not a Sony problem.
Missing calls and alarms render the devices with the OS useless for me. Unfortunately
3 Likes
Indeed, sadly on those C2’s that are working it seems that a lot of the ‘old favourites’ of bugs are emerging just as they have on previous Sony devices.
At this point, other than a larger form factor, I can’t see what advantage the C2 has over the Xperias - especially since it seems that it might take a couple of years or so to reach a reasonable level of maturity with all the additional new hardware adaptation issues that also exist at the moment.
Agreed; and large form factor isn’t an advantage per say.
I’m not one to watch content on their mobile devices, so if something like an N95 ever got revived with modern day security and mobile connectivity standards I’d switch back without a second thought.
But this particular audio issue is the biggest reason I’m looking to replace my Xperia 10 III, it makes it unreliable as others have said before.
On an average Xperia 10 III day I’d not wake up in time for work because the alarm didn’t sound; on the worst N95 day where the battery was drained and the phone had switched off it would power up just so it could wake me 
Nostalgia aside, I’m stuck on candybar form factors for the moment, but it looks like the Xperia 10 V is going to be the next contender and perhaps the only officially supported modern device that doesn’t suffer from this particular audio issue?
Hopefully the V has not this awful bug.
Until now, in my V device I could not provoke this bug, whereas the iii in parallel use is heavily affected and audio crashes silently after nearly each GPS use.
Based on this: for me personally the V is the route go into the future with SailfishOS.
I was not seduced by C2 because of inferior hardware, i.e. no OLED = no buy
1 Like
It is worrisome to hear that the C2 is alsi affected, because in the end this means it is a Sailfish bug, not a Sony problem.
Isn’t this a good thing? Now it can be fixed instead of thinking that the problem is somewhere in Sony’s firmware and therefore unrepairable.