amazon-chime-sdk-js
amazon-chime-sdk-js copied to clipboard
Samsung galaxy s22 ultra no sound
What happened and what did you expect to happen?
I use amazon chime to build a video-conference application. Attendees that join to the meeting with Samsung galaxy s22 ultra doesn't listen to other attendees. It's reproduced only for Chrome 102 on Samsung galaxy s22 ultra. FF on the same device works ok.
Have you reviewed our existing documentation?
Reproduction steps
- Start a chime meeting on Samsung galaxy s22 ultra.
- Attendee will not listen other attendees.
Amazon Chime SDK for JavaScript version
2.15-2.30
What browsers are you seeing the problem on?
Android Chrome
Browser version
102
Meeting and Attendee ID Information.
{ ExternalMeetingId: '1a17c4d5-ba72-4a19-8ddd-aa9baad53089', MeetingId: 'dfd7c48a-069e-48e6-8400-66c4a1070706' , attendeeId: 'a6f870d6-ea44-1e67-262b-000bdfb09848', browserMajorVersion: '102', browserName: 'Chrome', browserVersion: '102.0.0.0', deviceName: 'Samsung SM-S908B}
Browser console logs
- Could you try replicating the issue with our browser demo?
- You seem to be calling bindAudioElement twice with a HTML with no ID, what's the element being passed in these two cases?
Could you try replicating the issue with our browser demo?
- You seem to be calling bindAudioElement twice with a HTML with no ID, what's the element being passed in these two cases?
The same element is being passed in two bindAudioElement calls. Is this problem?
Ah no that's not an issue, I was just curious if this was intended behavior and if it might be binding to the incorrect element.
Hi. I deployed Serverless Demo to my AWS account (I checkout chime SDK to 2.27 tag because I use the 2.27 version) and I reproduced the audio issue on Samsung Galaxy S22 Ultra. Samsung-Galaxy-S22-Ultra-log.txt macos-chrom-log.txt
The first attendee joined from MacOs Chrome, the second from Samsung Galaxy S22 Ultra Chrom. The second doesn't hear the first. The first hear all.
The screenshot shows 2nd attendee settings before joining to the meeting. All logs are copied from the browsers console after joining to meeting of 2nd attendee (Samsung Galaxy s22 Ultra)
Hi @vitiaaap29 sorry for the delay, but looks like there is no error in the provided logs from S22 ultra device.
Could you please try once the below official WebRTC sample app and see whether it works fine?
- Check whether you get feedback testing this demo on the same device in same browser where you are facing issue (Chrome 102): https://webrtc.github.io/samples/src/content/getusermedia/audio/
- Check whether you get feedback here as well: https://webrtc.github.io/samples/src/content/devices/multi/
Few questions:
I do not see explicit chooseAudioOutputDevice
API call in logs hence may be the selection is not supported but since its Chrome 102 I am not sure whether that is 100% correct. FAQ.
Are you trying to choose a different audio output device if allowed or no?
Closing due to inactivity.