Problems with Bluetooth (Murena Fairphone 6)

I don’t have Fairphone, but that is not normal for me.

On a normal call (the call has to be commenced in my test) do you see the Speaker icon and are you able to toggle it on and off? For me the icon fully works but is somewhat non intuitive if toggled on or off. Black speaker for on, dark grey speaker for off, no strikethough (Use of colour is seen on regular Android a16 as it happens – I cannot seem to screenshot this view.)

I also tested that the last used “Speaker off” persists to the next call.

(However it is possible the use of Bluetooth might leave a residual inappropriate “last used”, idk.)

Do you have different?

The toggle loudspeaker is already activated, I can see clearly with the font white color, and doens t matter I put my finger, it s not desactivate

so if it s not murena os, it s about fairphone unfortunalty ?

OK but you are saying that you want it deactivated ?? You want LOUDspeaker off, earspeaker on.

If the toggle does not work it is a case for Report an issue

Perhaps also double check with the app Fairphone Checkup.

yes desactivated

just the phone put on my ear to speak and hear.

without people hearing conversation with interlocutor.

Hello everyone Hi a problem with Fairphone 6. Currently I have as a system 3.2-a15-20251022539003-official-FP6 When I connect it to my car (Fiat uconnect) if I make a phone call I hear from the speakers, if I receive a call I don’t hear the ringtone from the speakers. I can only answer and speak from the phone. I will try everything but it doesn’t change the problem. Thank you

Indeed, as you can read here, this is a well known issue on FP6.

Normally it should be fixed in the next 3.3 release (very soon) - (and hope so very much as well).

1 Like

I empathise. Likewise, I am a hearing aid user (NHS Phonak Nathos Nova) and I have just bought a Fairphone 6 with /e/OS on it straight out of the box. I can’t take calls through the Bluetooth connection and it makes the phone unusable for me, full stop. As suggested, I’ll attempt to put a comment on GitLab to try to add some weight to getting the bug fixed. I’m a novice on these forums, but from what I can see it hasn’t been addressed in v3.3…

Ok… Well I don’t know, since version 3.3 stable has not been released so far (20.12.25 - 13:17 UTC).

Let’s hope Bluetooth issues will be fixed on 3.3…. I will give a feedback here and on the e-Gitlab page.

Thanks. And yes, fingers crossed for Bluetooth fixes. Reliable Wi-Fi and Bluetooth connectivity is pretty fundamental these days…

So…..the very good new is: Bluetooth incoming calls in car seems to be fixed with /e/OS 3.3! I just tested right now in my Ford Fiesta (2017) and sound was correctly handled on my high-speakers and microphone unit! :folded_hands: :flexed_biceps:

Now I will have to make further tests, including in my Seat Alhambra (2014), but there are high chances that it will work as well.
As soon as I could test this in the Seat Alhambra, I will close the Gitlab ticket. But now the vehicle is in repair ‘till begin of next year….

So pretty happy with this fix! Thank you very much all the team!

1 Like

Thanks for alerting me to this. It sounds very much as though I’ll soon be able to get up and running with my FP6 + hearing aid.

However, I’m not being “offered” 3.3 yet… Am I right in assuming that with a FP6 direct from Fairphone with /e/OS pre-installed, I should wait until I see it via Settings → System Updates?

It should appear in “Settings” => “System updates” (1rst menu in settings). If not, refresh with the circular arrow at the top right.

Refreshing continues to inform me “No new updates found” and that "You are running the latest /e/OS version”.

Maybe just a rollout sequencing thing then. I’ll try leaving the phone on (which I haven’t been doing, because I’ve not moved my number to it yet).

Hmmm. Maybe try to press the small arrow repeatedly until the update appears.

1 Like

Bingo! Thanks! 5 presses and it’s there.

2 Likes

Good new! Issue is fixed along V3.3. Tested on my both Ford Fiesta (2017) and Seat Alhambra (2014). Incoming calls were correctly redirected to the car units. Therefore I close the following issue.

Thank you very much!

The update to version 3.3 did not fix the problem for me :worried: (Dacia Sandero 2020).

/e/OS : 3.3-a15-20251210556408-official-FP6

Build : BP1A.250505.005

As regards making and receiving calls, I had/have a similar bluetooth hearing aid connectivity problem on a Fairphone FP6 with /e/OS version 3.3-a15-20251210556408-official-FP6 (that also existed with v3.2). When moving from /e/OS v3.2 to v3.3 didn’t change anything for me, I began playing with other settings. I don’t pretend to understand why, but turning off both Wi-Fi calling and VoLTE is a workaround that solves making and receiving calls for me.

I only had problems with phone calls, which always worked through the phone speaker(s), just not through my bluetooth hearing aids. I haven’t done much of it, but I’ve had no problems with listening to music.

1 Like

Where do you turn VoLTE & Wi-Fi calling off? Realy would like to try! I have the same issue with my hearing aids.
Alarms work again with v3.3 :slight_smile:

I found switches for both VoLTE and Wi-Fi Calling here:

Settings → Network and Internet → SIMs → eSIM (or whatever yours is, I don’t know what it would say for a physical SIM!)