I’ve had this happen once. I used GPS during the day for a few hours, then some in the evening, and some time after that I noticed the issue. My gut feeling is “it can’t be GPS” but now I’m starting to doubt that…
For me this is totally random. It can happen directly after a reboot, over night without using the phone,after a phone call…i never figured out a reproducable situation to trigger this bug.
But i will reboot now and check if the bug occurs without using GPS at all.
I don’t have this issue since 3 days by deactivating the GPS.
Do you have the same errors in journalctl?
2days and 18 hours without using GPS, audio is still working.
I can confirm that the same happened to me yesterday, while attempting to setup my Xperia 10 III.
After installing all my apps and copying all my data to the device, I tested audio and video, which worked fine.
Next step was to download maps and check GPS with OSM Scout. After enabling the GPS, audio was gone. A restart solved it for the time being.
There are two other similar cases, one you can find here:
Instead of restart you can in the terminal type the following:
pulseaudio --check && pulseaudio -k && pulseaudio --start
It is also possible to type the middle part:
pulseaudio -k
I had the same bug after using GPS/Pure Maps. However, I did not notice that it might be related to GPS/Pure Maps but I lost sound the day I was travelling with Pure maps’ assistance
It seems to me that I have already tried without solving the problem. I will try again this weekend.
The answers in this thread seem to confirm that the GPS is related to this issue.
Do you know if it is possible to use the location from a watch with a GPS function and compatible with Amazfish?
I don’t have one, but I can consider it if it can be a temporary solution to use OSM Scout when I go with my bike
I am 99,7% sure that the watch cannot feed GPS signal to the phone…
Somehow, I managed to get rid of this weird bug (?conflict?) where the audio is suddenly gone after enabling and using the GPS.
After getting no data connection from my SIM (placed in SIM slot 1), I decided to copy my mSD content to the internal storage, remove it, place the SIM card to slot 2 and check if mobile data is usable this way (found this solution in the forum).
So, after placing my SIM card to SIM card 2 slot, mobile data is working perfectly fine (up to now, 3-4 days in a row). I then tried to reproduce the aforementioned problem, enabling the GPS and checking with the sound. THIS BUG IS GONE TOO! (at least up to now)
It’s a bit inconsistent, too… I have used GPS every now and then for 10-15 minutes for testing this, and so far I haven’t been able to reproduce it with short sessions…
It may also have something to do with OOM killer, because I have only been able to reproduce it with Here WeGo navigator, which eats up quite a lot of RAM. It’s not a trivial task to hunt this down…
I’m having this issue again. I could collect some logs, what would be useful? I can survive this for a few days at least
PS. I did use GPS for 1.5h two days ago, this could be because of that, not sure, but certainly possible.
Perhaps collect all log since device has booted and then filter.
I have seen this a couple of times now too. Seems to happen even during inactivity, or maybe at the end of usage.
After using the GPS, which i barely do, i always restart the phone. The bug didn’t occur for weeks now, so i think it is definetly GPS related.
Did any of you check miau’s solution? [Xperia 10 III] Audio suddenly completly gone - #7 by miau
It did fix this issue for me, unless I have been extremely lucky so far.
Not yet, but I have GPSinfo running, and pulseaudio and ngfd restart scripts ready
When I hit the bug, I’ll test them one after other to what fixes it for me. I think the pulseaudio conf change comes last for me, I’ll try to find the general direction first.
I just hit the bug this morning, after 6d of uptime and no GPS use. I believe it was an OOM kill, necause I was at 5.0/5.38GB according to htop. Running the pulseaudio commands above solved it without reboot (at least for playing audio).
I haven’t tried the pulseaudio config change, but I doubt it would have affected the OOM kill in this case.
Just another little data point: Bluetooth headset plays music just fine with native and Android apps.
I can confirm this behaviour. My alarm stopped working yet again, so I’ve taken a moment to test this. With a music player trying to play a song (but frozen because of this bug), as soon as the bluetooth speaker connects playback starts working. Disconnect playback, it’s frozen again. This can be repeated over and over.
I also want to take this moment to reiterate how critical this bug is. Not being able to hear your alarm in the morning or incoming phone calls is unacceptable, working audio is a critical functionality on a mobile phone. Can we please get a confirmation by Jolla that this bug will finally be fixed in the next update?