@schmittlauch I guess your observation is helpfull because for me the issue closely correlates with the use of PureMaps for navigation. But, off course, I don’t no whether this is a mere coincidence of using GPS and Android or something else.
I am switching on/off gps, to use in waze few times per week. Always after using gps in some app sound is lost after some time (could be after several hours). Therefore always after using gps after disabling it I restart my phone. When gps was not enabled, issue does happen to me even if phone is working without restartng for a weeks.
What could be tested is to restart the phone without android support. Enable the gps and see if the no sound will occur. REMEMBER NOT TO START ANY ANDROID APPS.
If an android apps must be started close the gps support first.
I had this problem every other day so I left the phone without Simcard. Read about a user experiensing different variations in time, travelling in different countries. So i charged the phone (10III), After two months everyday testing the sound, it did not fail once. Might this be a fault conversation with the Simcard and how does that effect the sound ???
The phone uses your location via the simcard mayby the bug is there
Is this related??
Yes, I do not know how to solve it, but do not have the GPS open then I will not have the issue.
In my case it was definitely independent from GPS and /or Android support. It occurred today with location off and no GPS use, also Android support was off
1 Like
Hey, so this is a Pulse Audio issue.
The quick fix is to run something like this in the terminal pulseaudio -k, which kills the existing pulseaudio process and starts a new one. If your terminal is irresponsible, reboot.
In android apps, sometimes mic won’t work but audio still works. While pulseaudio -k could work, sometimes closing the app altogether and restarting it, can fix the issue.
They always tell us to get logs, particularly journalctl -b --no-pager as devel-su or sudo. However, this logs everything, and pin-pointing when the issue arises can be challenging.
2 Likes
Today was again the audio locked in speakers.
After devel-su:
pulseaudio -k
gave an error message that translates to “background process not interrupted found, no suitabke process”
PA runs as normal user, not super user. So, no devel-su before killing it…
2 Likes
Oh thanks for letting me know, I will test next time as regular user
A “friendlier” way to do it is systemctl --user restart pulseaudio (as defaultuser).
3 Likes
I do stop and start pulseaudio, i had better results with that
1 Like
I’ve encountered this bug 3 times over the last two years of using XIII and ‘pulseaudio -k’ worked both times I was aware of it as an option, I think the more elaborate systemd calls should be used by the system itself if it’s possible to diagnose the situation happening without user actively not hearing anything
Unfortunately I experience it nearly daily, but killing pulseaudio as default user did the trick, thanks again to all of you. That’s a simple and doable workaround for me.
2 Likes
wow, that’s pretty much as reproducible as can be, pls contact jolla support, they will want your logs, with most of us experiencing it once per year you just cannot catch it in logs, almost daily is as good as it gets
1 Like
but annoying during important phone calls
Yaeh, just like 112 failing when you really need it, but there is no good way to test, unless you want to end up on the fake 112 callers list
