First of all, I would like to thank you for developing an amazing WebRTC.
I am facing a new issue after updating my iPhone from iOS 14 to iOS 15.
When I join a video session the publisher’s sound comes out from earpiece (like during a phone call). How can I set output source to a speaker?
I tried enabling speaker layout from media player icons, but nothing seems to be working.
This issue occurs on all Apple iPhones with iOS 15 (Latest version)
Please, provide to us as much information as possible about your client device.
Device model, platform used (is it Safari? Which exact version?). The exact iOS 15 number.
Also please describe in detail the scenario in which you see the wrong behavior. Is it a simple 1:1 audio+video OpenVidu Session? Does it happen in any of the official OpenVidu demos?: https://demos.openvidu.io/
I’ve just test in https://demos.openvidu.io/ OpenviduCall with iPhone XS - iOS 15.0.2 Safari. Audio level is low.
Audio level will be normal if I click stop/start using camera button in address bar.
Audio level is max but volume’s low. mute/unmute is working fine but not make the audio be louder.
To be louder, I have to click on camera icon in safari address bar → stop using camera.
You can find in this video test: https://photos.app.goo.gl/qhY9BdxzRCGvTtDX9
OK, I got it.
Could you please check if you have the same behaviour with Chrome Browser? Maybe it is only happening with Safari and Apple has a bug with the new release
Ok, I have been performing further tests and I can confirm the problem. Audio is in fact coming out OK through both outputs: the earpiece and the main speaker. But the total audio level is reduced, I’d say about 1/2 to 2/3. And clicking on the “Stop camera” option on the Safari’s navigation bar does in fact increase the audio output level.
And the unfortunate news is that this is an Apple bug. It does not affect OpenVidu in particular, it is problem with iOS WebkitView. Here at the Apple’s developer forum there are some entries talking about it: iOS 15 Safari WebRTC Issue | Apple Developer Forums
Other WebRTC services are also reporting the problem. You can even see an engineer from Twilio complaining about it: