REPRODUCIBILITY: Occurs after the phone has been on sometime. Rebooting the device seems to solve the issue, for a time.
OS VERSION: 5.1.0.11 (Pispala)
HARDWARE: Sony Xperia 10 III (Device adaptation: 1.0.1.12)
UI LANGUAGE: English (UK)
REGRESSION: If my memory serves me correct, I didn’t have the issue in the previous OS version. Issue occurred first a few weeks or around a month ago.
DESCRIPTION:
The call function (4G) in the phone does not work properly. After the phone has been powered on for a while (eg. a few days at least), the incoming and outgoing calls are completely mute. The issue seems to be removed after rebooting the phone.
I remember seeing a error notification “com.jolla.nativeapp.phone is not responding” a couple of weeks ago. I don’t know if it was related to the issue at hand, as it didn’t seem to occur at the same time when attempting a call, but it did raise suspicions it might be related to mute calls. Please see the screenshot below.
PRECONDITIONS:
It seems the phone has had to be on for a some time (eg. a couple or a few days at least). Freshly booted phone seems to be able to make and receive calls normally.
STEPS TO REPRODUCE:
Use your phone as normal for a few days, keeping it powered at all times.
Receive or make a call. You can’t hear the phone ringing if receiving or the phone dialing when making a call.
Answering the call results in no sound in the call on both ends. Neither of the parties can hear each other in the call.
EXPECTED RESULT:
After answering a call, both parties can hear each other.
ACTUAL RESULT:
No audio can be heard during calls and neither of the parties in the call can't hear each other.
MODIFICATIONS:
The OS installation wasn’t followed by the book as Android version wasn’t reverted back to 11 as instructed. Instead, the phone had the freshest Android version available prior to the installation of SFOS. Installation was done in 5/2026.
ADDITIONAL INFORMATION:
Screenshot of an error message. I’m not sure if it’s related to issue at hand. It occurred randomly around three weeks ago (16.7.2026), not related to a call as far as I recall.
Is any audio working? Have you had GPS enabled? You might try to restart the Audio Subsystem from Settings → Utilities - but in general audio in calls on a 10iii works fine.
I have the exact same problem, Xperia 10 III. It has been since i installed 2,5 years ago, on all versions/updates. Followed all installation instructions, the phone was unused so never updated to android 12.
Yes, audio in general works. For example audio from notifications, alarms and such work fine. I think the call audio after rebooting the system work fine too, but the problem arises after phone has been powered on for a few days at least. Could it be a RAM issue if the error pictured in the screenshot is related at any rate? I don’t know.
I’ve had location enabled from the top menu. I’ll try to restart the audio subsystem and see if I still get the mute calls.
There is a known issue that Location enabled will sooner or later screw up the audio subsystem on the 10iii. I’ve never seen the phone app crash on mine but that might certainly play into the issue you’re seeing.
Ahh thanks for letting me know. I’ll disable location and see if the audio issue persists during calls. I’ll try to remember to report back by the end of August.
I don’t know if there’s been /one/ post/topic that discusses that issue, but sound loss has been an issue with the 10iii for a long time and has eventually been pinpointed to GPS as the culprit.
Here is one post: No audio after some time, have to reboot - #67 by Dickus51
It’s happening on mine consistently (5.1.0.11, no idea about the Android base) but since I don’t need GPS on a regular basis and know how to easily restart the audio system, I didn’t bother too much and just started to turn Location off. Problem solved (for me).
OK I just spent 10 min reading that topic and a few other links.
Nowhere is there any evidence (except users guessing) of GPS being the culprit, quite the opposite: many report that is has nothing to do with it, i.e. that they experience audio problems even though they never use GPS and similar.
Also, audio cutting out - as annoying and unacceptable as it is - is not a single bug, there can be many reasons for it, many scenarios.
The issue supposedly was more widespread - but when your audio repeatedly and consistently goes out after having GPS enabled and doesn’t when GPS is disabled, then GPS at least plays a part in it. But maybe own experience is not as trustworthy as speculation based on random posts
