As mentioned by Ingo I moved your post here in the existing thread. Please have a look around.
After update to Android 10 WiFi calling no longer worked. Had to disable. Haven’t checked with recent update.
Surprised that this issue is discussed here for over a year and still no solution…
As many of us experience the same issue it would be great if you could report it to the fairphone-support. I think the more reports they get, the more they realize that this is really a big problem and this could lead to a sonner solution by fairphone.
thanks for the advice, did it. Ticket is #386824.
That might be possible. Maybe I didn’t express myself understandable enough: the problem may have started with the update to Android 10 and on calls, when trying them after using Spotify some time before.
Still just an idea - and unfortunately there’s only a German topic up to now…
Same problem here. The call seems to go through (timer starts running) but I can’t hear nor be heard. Rebooting fixes the issue temporarily and for an undefined period of time. In my case:
- Fairphone 3 (bought directly from fairphone shop, on january 2020)
- I never use earphones, never plug anything on that port.
- Swapped the SIM to 2nd slot, same problem happens.
- Updated the OS last week as per the phone notification. The problem started showing months before this and now it happens more often.
I sent them a request and they answered with a template answer asking me to buy a new SIM, change provider or some other non-sense. And telling me they will not look into it unless I satisfy all these demands. So I have to spend more money before they even decide to give it a look!? They don’t seem to honor their brand name when it comes to customers and that is extremely disappointing.
It looks like they have the problem well identified but got no clue as to what causes it, so the customer care team just fools around with you to buy themselves time.
I don’t really have any hope left and I’m stuck with this, but I’m sure I’ll never buy anything off this company again and I will not recommend it to anyone. As soon as the phone breaks down I’ll buy another phone somewhere else, replacing components of a piece of crap does not make much sense.
I entirely agree with everything you say. So disappointing…
The last email I received said :
If not specified already, please provide the following information:
- Network provider(s)
- In which country are you experiencing this issue?
- Frequency of the issue after the last update. How often does it happen? Once a day, once a week, every phone call, etc.
I am checking with my colleagues how we can help you with this, I can only hope for your patience.
They’re totally trying to gain time. I just hope they do put resources in fixing the issue.
To me it sounds like they’re trying to find a typical pattern for those problems. And as there’s currently no fix they hope for your patience…
I’m convinced they do.
Same problem here. Often when calling apparently people hear me, but I can’t hear others. Rebooting fixes it. Really hope that this will be fixed, but it only seems to become worse actually…
I’m convinced they are doing nothing. If they’d be looking into it they’d have told me something in the lines of “yes, we know the problem and are trying to find a fix, please be patient”, instead they simply deny everything and make you go through a nightmare to find an excuse not to help you.
I haven’t seen such a bad customer support ever.
I have a newish FP3 and have the same problem which is resolved by restart.
I think it happens after using and then turning off Do Not Disturb
Unfortunately I have to admit, that I am suffering under the same problem.
Did someone already find out what is causing the issue? I read about spotify and “do not disturb”.
I also noticed, that it became worse with the Android 10 update.
as there is no real pattern in the reports of the users i assume that it simply is whether a software or a hardware bug. I suggest you too to write to the FP-support team to raise their awareness and put some more pressure on them for finding a solution!
I have the same Problem, i guess its since the Upgrade to Android 10. I have to reboot to receive calls wich is really annoying. Hope that there is a fix for this issue soon!
Hi Volker and all,
On my Fairphone 3 we discovered the problem of “no sound while calling” originates from two things. First, it only occured after the Fairphone software update ( roughly a month ago). Second it is related to the usage of another app from the playstore: Trivia Crack.
When the problem occurs, you can solve it by rebooting your phone. It will work fine…days after days…until we play Trivia Crack. After using this app one time I entered the “no sound while calling” problem again.
My solution for now…which is not elegant but practical: don’t use the app Trivia Crack any more and this works. To me, it seems likely this effect can occur with other apps (games) as well.
Note: When using spotify app the phone works fine.
The “no sound while config” was happening from september 2019, long time before android 10 update.
And I never used, nor I know what is, Trivia Crack.
Still, I have this issue, randomly appearing for days/weeks, until disappearing for days/weeks.
I thought at some point that it was correlated to the use of the jack plug, but I’m not sure, because I wasn’t able to reproduce at will the issue by plugging the jack
Please do contact Fairphone support, and do not hesitate to link to that thread
In another thread, Spotify has been identified as the possible culprit here. Could you please check if your issue occurs right after using the Spotify app?
I’ve got the same issue with my FP 3 for months. I don’t use my phone a lot for calls but my impression is that it got worse during the last weeks.
Interrestingly I’ve had this problem with my FP 2 as well. That makes me think the problem might bei caused by an app (not Spotify in my case). But I admit that I don’t want to test every single app.
I will try the earplugs in the next days and report my findings.
Ticket is sent too.
You could try starting in #dic:safemode, it would allow you to know whether this is caused by an app or not (not which one though).