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

taking a video call does not always default to loudspeaker #5368

Closed
HarHarLinks opened this issue Jan 11, 2022 · 6 comments · Fixed by matrix-org/matrix-ios-sdk#1512
Closed
Assignees
Labels
A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems X-Needs-Community-Testing Z-Ready This issue is ready for development Z-WTF WTF issues: High impact, Low Effort

Comments

@HarHarLinks
Copy link
Contributor

HarHarLinks commented Jan 11, 2022

Steps to reproduce

video call somebody that uses element-ios.

they're not so technologically inclined as to open this report themselves.

Outcome

What did you expect?

default to loudspeaker

What happened instead?

earphone speaker is selected by default

Your phone model

7

Operating system version

15.2

Application version

1.6.11

Homeserver

No response

Will you send logs?

No

@HarHarLinks HarHarLinks added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Jan 11, 2022
@kittykat
Copy link
Contributor

I would say priority for video call should be

  1. Bluetooth headset if available
  2. Speaker
  3. Phone-mode

@HarHarLinks
Copy link
Contributor Author

HarHarLinks commented Jan 11, 2022

to be precise,

  1. any additional device (headphones, headset, hands-free like a car, wired, wireless) if available

@pixlwave pixlwave added O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Jan 26, 2022
@pixlwave pixlwave added the Z-WTF WTF issues: High impact, Low Effort label Jan 26, 2022
@daniellekirkwood
Copy link
Contributor

I'm comfortable with this suggestion, let's go ahead and implement it as a WTF. I will mark this issue as Ready so it can be picked up by the WTF team :D

@daniellekirkwood daniellekirkwood added the Z-Ready This issue is ready for development label Feb 2, 2022
@aringenbach
Copy link
Contributor

Here's some informations about this issue's status.

  • The priority order mentioned here is already implemented at the moment.
  • Regarding the issue, my best guess would be that on this device, AVAudioSession returns that loudspeakers are not available at the moment we are interrogating it (maybe some weird race condition here).
  • I tested with a few devices, with different levels of build optimization in order to trigger the issue but actually never had it. I'll try again for this if I get my hands on other iOS devices.

FTR, I tested the issue with these devices:

  • iPhone 7 - iOS 13.3
  • iPhone 6S - iOS 13.4
  • iPhone SE (2nd gen) - iOS 15.0

@HarHarLinks
Copy link
Contributor Author

This is still happening on above mentioned iphone with updates applied in the meantime

@pztrn
Copy link

pztrn commented Apr 5, 2022

Confirming on latest Element on iPhone 12 Pro.

Also might be related - bluetooth headset not working at all when answering on incoming call despite on manual switching back and forth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems X-Needs-Community-Testing Z-Ready This issue is ready for development Z-WTF WTF issues: High impact, Low Effort
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants