Audio output changes in WebRTC app in Chrome for Android when incoming GSM voice call

[Antón Román]

Hello,

we have noticed that when we have a WebRTC session established (in our case is a audio/video p2p call) and we receive a regular voice call and we reject it, the audio output changes from the main speaker to the earpiece speaker. Is this the expected behavior? 

We can reproduce this with different WebRTC applications and with different terminals so I guess it's related to the way the phone manages the audio output. Has anyone experienced this? If yes, is there any available workaround to force the main speaker?

On the other side, the audio output device can not be chosen in Chrome for Android, there is only one available option (it appears as DEFAULT checking it with https://webrtc.github.io/samples/src/content/devices/input-output/).  

 

Thanks in advance,

[Dimitri Osler]

We are also interested in being able to switch the audio device in Chrome for Android. So far Chrome WebRTC seems to use the system audio device. By default handsfree mode - if a BT or corded headset is connected then headset. In your case during the phone call the device switches to the ear piece but this looks more like a consequence of Chrome not being able to select a specific audio device.