Hello
I have a question
is it normal when I call or people call me on phone (without earings or bluetooh justvwith ears in nomal way) the loudspeaker is automatically activated…..and I can’t desactivated
so it s annoying that people around me in the street can hear conversation…..I tried another telephone app then the initial, it changes nothing
I use fairphone 6 with murena OS
somebody have this problem resolved ?
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).