Samsung S21FE no Bluetooth calls (sound)

Samsung S21FE no Bluetooth calls (sound)

Author
Discussion

Gecko1978

Original Poster:

10,303 posts

163 months

Wednesday 10th January
quotequote all
So last summer updated my s21fe as per the annoying reminder. An soon as I did that my phone would no longer open the mic when making Bluetooth calls.

I can play music via Bluetooth it connects to the call. But no sound. Tried it in multiple cars and with ear buds no joy. Vodafone claimed it was a Samsung software issue so phone Warrenty does not apply. Samsung say nothing to do with update.

Now I have lived with it for a year but wondered has anyone else experienced thus issue?

My solution is new phone in April which is a shame as bar that it does all I need

indigochim

1,627 posts

136 months

Wednesday 10th January
quotequote all
Does it work if you restart your phone. There used to be a setting in android to restart when needed which got dropped after an update mind did the same although I've not noticed it recently.

Gecko1978

Original Poster:

10,303 posts

163 months

Wednesday 10th January
quotequote all
No restarting does not help online it says clear the cache but I can't find that function

indigochim

1,627 posts

136 months

Thursday 11th January
quotequote all
Settings, Apps, select the filter and sort menu (to the right of where it says "Your Apps (??)...... looks like an down arrow to the left of three bars). change the switch to "Show system apps" OK, You'll now find Bluetooth listed open it, Select Storage and clear cache will be under there.

The Auto restart is worth having on anyhow. I noticed a drop in performance and battery life while it wasn't enabled. It can be found under settings in Device are, Auto Optimisation, Auto Restart.

Like I say mine had the same/similar issue on my samsung wireless buds but was fine in the car but it appears to have fixed itself or the regular auto restart has. Restart used to fix it temporarily for me. I'm on an S21 Ultra so not quite the same I've recently had the update to Android 14 so maybe that had something to do with the fix..