You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just recently we have noticed that the newest IOS update for iPhone has made the audio come out softer than it usually does. We tested using iPhones with older IOS versions like 14.7 and 14.0 and the sound comes through the speaker and is louder than when using IOS 15.
we believe it might be that it is using handset speakers instead of loud speaker.
We expected the sound to be the same volume or around the same volume for when on loudspeaker in a normal phone call.
ldai1
added
the
audio
Issues related to impaired audio experience - quality related or not being able to get audio
label
Oct 12, 2021
ltrung
added
Browser Bug
and removed
audio
Issues related to impaired audio experience - quality related or not being able to get audio
labels
Oct 14, 2021
Thanks @benjing for reporting the issue. As @ElielCohen has pointed out this is a regression in iOS 15. I have put this in our known issue #1059 to track it there so I will close this one.
What happened and what did you expect to happen?
We have been using chime sdk js since August
Just recently we have noticed that the newest IOS update for iPhone has made the audio come out softer than it usually does. We tested using iPhones with older IOS versions like 14.7 and 14.0 and the sound comes through the speaker and is louder than when using IOS 15.
we believe it might be that it is using handset speakers instead of loud speaker.
We expected the sound to be the same volume or around the same volume for when on loudspeaker in a normal phone call.
Have you reviewed our existing documentation?
Reproduction steps
Using chime sdk js 2.18 start a call on an iPhone with IOS 15.0
Amazon Chime SDK for JavaScript version
2.18
What browsers are you seeing the problem on?
IOS Iphone Safari
Browser version
15.0
Meeting and Attendee ID Information.
No response
Browser console logs
NA
The text was updated successfully, but these errors were encountered: