Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loudspeaker is always used #1685

Closed
532910 opened this issue Jul 13, 2020 · 22 comments · Fixed by #2014
Closed

Loudspeaker is always used #1685

532910 opened this issue Jul 13, 2020 · 22 comments · Fixed by #2014
Assignees
Labels

Comments

@532910
Copy link
Contributor

532910 commented Jul 13, 2020

Whether wired headset is connected or not, or which sound device is selected: Phone, Headset or Speaker the loudspeaker is always used.

@532910
Copy link
Contributor Author

532910 commented Jul 13, 2020

Moreover, trying to toggle between Phone and Speaker or between Headset and Speaker the Phone (Headset) is always shown on the bottom:
image

@blaggacao
Copy link

On Motorola Android One it worked.
On huawei BLA-L29 I can vonfirm your report.

@532910
Copy link
Contributor Author

532910 commented Jul 27, 2020

looks like it should be Switch Loudspeaker -> Earpiece/Wired Headset doesn't work

@rarepops
Copy link

For me I have to actually switch to Loudspeaker then back to Headset to work. It seems like the app thinks it's in Headset mode but selecting that without selecting Loudspeaker first will not make the switch correctly

@532910
Copy link
Contributor Author

532910 commented Aug 24, 2020

@bmarty is any update there? People say this is one of the most annoying issues.

@bmarty bmarty added this to the Sprint13 milestone Aug 25, 2020
@bmarty bmarty added the A-VoIP label Aug 25, 2020
@onurays onurays self-assigned this Aug 26, 2020
@532910
Copy link
Contributor Author

532910 commented Sep 10, 2020

Not fixed, please reopen.

@bmarty
Copy link
Member

bmarty commented Sep 10, 2020

Please test with version 1.0.6 or at least tell us what are the version you are using.
We are closing issue when fix is merged on develop, which can be sometimes automatically handle by GitHub, not when the application containing the fix is released. This is maybe something we could change (DOD), and on our side we should maybe mention in which version of the app the fix will be available.

@532910
Copy link
Contributor Author

532910 commented Sep 10, 2020

All the time the loudspeaker is used and proximity sensors works:
ScreenRecord-2020-09-10-16-40-38

@532910
Copy link
Contributor Author

532910 commented Sep 10, 2020

I'm on Element 1.0.6 surely!

@bmarty
Copy link
Member

bmarty commented Sep 10, 2020

Let's reopen it then!

@notramo
Copy link
Contributor

notramo commented Nov 16, 2020

Please make it more important.
This is not good for privacy. If everybody in the room (or public transport or anywhere) hears what the callee says, then it's better to use Messenger or WhatsApp.

@bmarty bmarty modified the milestones: Sprint 16, Sprint 17 Dec 2, 2020
@notramo
Copy link
Contributor

notramo commented Dec 2, 2020

While a call is active in Element, an incoming phone call switches the Matrix call back to ear speaker. An outgoing phone dialing sometimes (I'm not sure that in this case, the Matrix call has to be accepted, or dialing is enough).
I haven't tested that it is only the phone call, or any app playing audio on ear speaker would switch Element back to ear speaker.

Let's tell this to your chat partners who currently use Messenger instead of Element because this bug, that there is this workaround, so they can switch to Element, just have to place a phone call to somebody every time they start a Matrix call.

@532910
Copy link
Contributor Author

532910 commented Dec 2, 2020

@notramo I believe this is a separate issue.

@landergate
Copy link

UX looks like this:

  1. Receiving an incoming call.
  2. Accepting it.
  3. Loudspeaker is forced by default and cannot be disabled.

AFAIK this behavior started since spring updates.
It doesn't depends on headset as it happens without them too.

@Freepony
Copy link

I can confirm that. When I make a call I hear the ringing tone in my headset but when the call is answered the app switches to loudspeaker.
Asus Max Pro m2 (X01BD), LineageOS 16.0 (Android 9), Element Android 1.0.11 (from F-Droid).

@notramo
Copy link
Contributor

notramo commented Dec 15, 2020

Please don't fix this. Do features like emojis (#2514) and confetti chat effect (#2535) instead, because emojis and confetti are important privacy features, which are often used by security-minded people, but being able to talk without everyone hearing the conversation on the public transport isn't important.

@Ledarium
Copy link

+1 for making it more important

@root562
Copy link

root562 commented Feb 2, 2021

I can confirm this problem on Huawei Mate 20 and Mate 10 Pro.

@bmarty
Copy link
Member

bmarty commented Feb 22, 2021

To be tested again with Element Android 1.1.0 which contain VoIP stuff

@bmarty bmarty modified the milestones: Sprint 17, Sprint 20 Feb 22, 2021
@notramo
Copy link
Contributor

notramo commented May 4, 2021

With the new VOIP protocol, the loudspeaker issue is solved for most devices, but even if it's on earspeaker, the ringback tone plays on the loudspeaker (sometimes quite loudly) for a second when starting an outgoing call, but then switches correctly to earspeaker.

@ouchadam
Copy link
Contributor

With the new VOIP protocol, the loudspeaker issue is solved for most devices, but even if it's on earspeaker, the ringback tone plays on the loudspeaker (sometimes quite loudly) for a second when starting an outgoing call, but then switches correctly to earspeaker.

I'm able to reproduce and confirm this has been fixed with 26d2694

https://github.com/vector-im/element-android/releases/tag/v1.2.1

@ouchadam ouchadam self-assigned this Oct 12, 2021
@ouchadam
Copy link
Contributor

ouchadam commented Oct 12, 2021

I'm unable to reproduce the original loudspeaker issue, the correct audio device is always being selected for me, I suspect the multiple fixes across #3863 #2014 did the trick

this thread has also diverged a little from the original issue so I'm going to close this issue for now, if we get more reports of the loudspeaker being incorrectly selected lets open it again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment