audioRouteChanged is not called on getting a call

[shashikantdurge]

Describe the bug
Use-case:
User joins a Live broadcast channel with NO earphones connected, the audio route is SpeakerPhone
User gets a call in between, all audio streams are muted.
ISSUE => The audio route switches to earpiece, audioRouteChanged is not called.

To Reproduce
Steps to reproduce the behavior:

1. User A & B joins Live Broadcast channel as Broadcasters. No earphones connected.
2. Audio comes from SpeakerPhone for both users.
3. User A gets a phone call
4. User A disconnects the call
5. Now, The sound comes from earpiece rather than the SpeakerPhone for User A

Expected behavior
Either switch back to the audio route what it was before getting call. (Recommended)
OR
Call the audioRouteChanged callback on changing it to earpiece.

Smartphone (please complete the following information):

• Device: [ OnePlus 3 Model: A3003]
• OS: [ Android 9]
• Version [ 22]

[marcusvpais]

This problem occurs on 3 xiaomi phones models that we tested here too. Only way to get back audios is to leave room and join again.

[shashikantdurge]

Even the setEnableSpeakerphone(true) also not working

[LichKing-2234]

could you pls provide the SDK log?

[shashikantdurge]

agorasdk.log

[LichKing-2234]

Have you tried the latest version?

[LichKing-2234]

https://pub.dev/packages/agora_rtc_engine/versions/4.2.0-rc.1

[adikimadhumohan]

Even with latest version(4.2.0) same issue happening.

[littleGnAl]

If you still face this issue, please try upgrading to the latest version to see if it works or not.

[github-actions]

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. If you find this problem please file a new issue with the same description, what happens, logs and the output. All system setups can be slightly different so it's always better to open new issues and reference the related ones. Thanks for your contribution.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please raise a new issue.