Bug 230902 – REGRESSION(Safari 15 - iOS15): [WebRTC] MediaStreamTack audio volume too low

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: WebRTC

[Les]

The audio in our web application’s WebRTC sessions is barely audible for users using Safari 15.This is not the case for previous Safari/iOS versions. Adjusting the volume in the web application and on the physical device has no effect. 

While searching for a solution, we found that the same issue exists for iOS15 users that join FaceTime calls via facetime.apple.com with Safari. We encountered this issue with the following steps (Users A and B are both using iOS15 ): 

- User A chooses “Create Link” from the FaceTime app
- User A shares the link with User B via SMS
- User B copies the facetime.apple.com link into Safari and ignores any prompt to use the FaceTime app
- User B should be able to hear User A clearly but the audio is very low

We’ve tried a number of workarounds with no luck:
- Establish a new audio connection after the initial to reset the volume
- Enabling autoGainControl
- Manually setting the volume constraint
- Triggering the audio by playing a sound prior to the WebRTC session

[Matt]

Using the above test from Les in my case:


User B was NO sound, until they turned on the video, then User B had low sound. User A (on app) could hear User B fine.

I have same issue.

remote stream volume on iOS 15 Safari is obviously lower than iOS 14.

[Kevin Neal]

Thank you for filing. The appropriate engineers have been notified.

[Radar WebKit Bug Importer]

<rdar://problem/83673859>

[Phong Le]

Although, audio stream is played on bottom speaker, but the volume is very low

[Mike Olson]

Hi Kevin,

Thanks for the Radar issue.

I'm not sure whether this is possible, but Les and I (we both work for the same company) would love to see this issue imported into OpenRadar or some other community-visible tool if that's convenient. I'm happy to authorize disclose of any details of the original report, in case that's necessary.

[Eliel Cohen]

Hi Everyone,

Where I work we also suffer from this, therefore I have been investigating on my side this issue, by the way it's not that the audio volume is low, but that the audio output is the earpiece and not the speaker anymore to my opinion.

Now I have got some interesting finding that could guide Apple engineers in solving this, basically I've found out that if I open a new tab (with some audio tag inside, but it could be not mandatory), as long as the new tab is on a different domain, then it will put back the audio back to the speaker at normal volume, and going back to the tab where the Webrtc call happens will not reproduce the low volume/earpiece output issue.

Please note, that using an iframe, won't solve it, and using a same domain url for the new tab, won't also solve it.

Other finding, using Chrome application (which relies of course on WKWebView) will reproduce the issue, but there, simply going to the tab view will solve the audio issue, and we can then go back to the tab where the Webrtc call takes place.

At last, please note that sometime, these two solutions can deliver a mix solution, meaning that some rare time, it did create a state where the audio will go through the earpiece (low volume) for half a second, then through the speaker for half a sec, and so on continuously...

Hope my findings will help someone :)

Thanks,

Eliel

[Steve Mieskoski]

Hi everyone,

I am also seeing this issue with iOS15. Our QA people went through the various audio settings to see if any of them would have an effect, but none did.

[Sherwin Sim]

Just want to add that Bluejeans/Verizon is also seeing this issue

We've tried a couple different workarounds as suggested in other threads and we cannot seem to get it to work

[Anna Vasilko]

We @Twilio received multiple reports of this iOS15 issue as well and are able to reproduce internally. Most of the end users perceive this as a "low volume issue" , when in reality it seems that in iOS15 audio is routed into earpiece audio output by default instead of speaker.

[Mina]

We are having the same issue too, in iOS15 the audio seems to be routed to the earpiece audio instead of the speaker, on the other hand iOS14 works properly

[Krieger]

*** Bug 231421 has been marked as a duplicate of this bug. ***

[youenn fablet]

Have any of you tried the latest iOS 15 beta?

[Mike Olson]

We tried 15.1 beta 3 and 15.0.2, the problem wasn't fixed in either.

[neo]

do not use media element (audio or video)
for play remote audio stream use audio context destination. 
this work for me.

[Phong Le]

Could you guide about how to use AudioContext to play this remote stream? I researched and when using AudioContext to play, we must attach with an audio element. Thanks

[Phong Le]

(In reply to neo from comment #15)
> do not use media element (audio or video)
> for play remote audio stream use audio context destination. 
> this work for me.

Could you guide about how to use AudioContext to play this remote stream? I researched and when using AudioContext to play, we must attach with an audio element. Thanks

[neo]

(In reply to Phong Le from comment #16)
> Could you guide about how to use AudioContext to play this remote stream? I
> researched and when using AudioContext to play, we must attach with an audio
> element. Thanks

i tested iOS 15. (wkWebview)

// audio stream example
 function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
    const context: AudioContext = window.AudioContext || window.webkitAudioContext;
    const audioNode = context.createMediaStreamSource(remoteAudioStream);
    const gainNode: GainNode = context.createGain();
    // some device volume too low ex) iPad
    gainNode.gain.value = gain;
    audioNode.connect(gainNode);
    gainNode.connect(context.destination);
  } 

and i'm not append video(with audio) element to document body. 
i use canvas.

[Brendan Del Rosario]

(In reply to neo from comment #18)
> (In reply to Phong Le from comment #16)
> > Could you guide about how to use AudioContext to play this remote stream? I
> > researched and when using AudioContext to play, we must attach with an audio
> > element. Thanks
> 
> i tested iOS 15. (wkWebview)
> 
> // audio stream example
>  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
>     const context: AudioContext = window.AudioContext ||
> window.webkitAudioContext;
>     const audioNode = context.createMediaStreamSource(remoteAudioStream);
>     const gainNode: GainNode = context.createGain();
>     // some device volume too low ex) iPad
>     gainNode.gain.value = gain;
>     audioNode.connect(gainNode);
>     gainNode.connect(context.destination);
>   } 
> 
> and i'm not append video(with audio) element to document body. 
> i use canvas.

This workaround allowed us(OP/Les, Mike & Brendan) to be able to hear the remote audio at an appropriate level. We set our gain value to 10 for now and will tweak as needed (increasing too much can cause clipping). The quality of audio is slightly lower than that of iOS 14 but for the time being it is a workaround that gets us closer to previous functionality. Thank you very much for posting this!

[Phong Le]

(In reply to neo from comment #18)
> (In reply to Phong Le from comment #16)
> > Could you guide about how to use AudioContext to play this remote stream? I
> > researched and when using AudioContext to play, we must attach with an audio
> > element. Thanks
> 
> i tested iOS 15. (wkWebview)
> 
> // audio stream example
>  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
>     const context: AudioContext = window.AudioContext ||
> window.webkitAudioContext;
>     const audioNode = context.createMediaStreamSource(remoteAudioStream);
>     const gainNode: GainNode = context.createGain();
>     // some device volume too low ex) iPad
>     gainNode.gain.value = gain;
>     audioNode.connect(gainNode);
>     gainNode.connect(context.destination);
>   } 
> 
> and i'm not append video(with audio) element to document body. 
> i use canvas.

Wow, it works :) Thanks for sharing. Before, I tested this one on MacOS Safari but not work. Only work on iOS device :). I set gain 4 to iPhone and 2 to iPad.  The <audio> and <video> tag (play file by url not remote stream) is still very low volume

[neo]

(In reply to Phong Le from comment #20)
> (In reply to neo from comment #18)
> > (In reply to Phong Le from comment #16)
> > > Could you guide about how to use AudioContext to play this remote stream? I
> > > researched and when using AudioContext to play, we must attach with an audio
> > > element. Thanks
> > 
> > i tested iOS 15. (wkWebview)
> > 
> > // audio stream example
> >  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
> >     const context: AudioContext = window.AudioContext ||
> > window.webkitAudioContext;
> >     const audioNode = context.createMediaStreamSource(remoteAudioStream);
> >     const gainNode: GainNode = context.createGain();
> >     // some device volume too low ex) iPad
> >     gainNode.gain.value = gain;
> >     audioNode.connect(gainNode);
> >     gainNode.connect(context.destination);
> >   } 
> > 
> > and i'm not append video(with audio) element to document body. 
> > i use canvas.
> 
> Wow, it works :) Thanks for sharing. Before, I tested this one on MacOS
> Safari but not work. Only work on iOS device :). I set gain 4 to iPhone and
> 2 to iPad.  The <audio> and <video> tag (play file by url not remote stream)
> is still very low volume

still very low volume <== it'll be ok if use audio context for playing audio file.

[neo]

does anyone knsow about this issue.
https://bugs.webkit.org/show_bug.cgi?id=231733

[Phong Le]

(In reply to neo from comment #21)
> (In reply to Phong Le from comment #20)
> > (In reply to neo from comment #18)
> > > (In reply to Phong Le from comment #16)
> > > > Could you guide about how to use AudioContext to play this remote stream? I
> > > > researched and when using AudioContext to play, we must attach with an audio
> > > > element. Thanks
> > > 
> > > i tested iOS 15. (wkWebview)
> > > 
> > > // audio stream example
> > >  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
> > >     const context: AudioContext = window.AudioContext ||
> > > window.webkitAudioContext;
> > >     const audioNode = context.createMediaStreamSource(remoteAudioStream);
> > >     const gainNode: GainNode = context.createGain();
> > >     // some device volume too low ex) iPad
> > >     gainNode.gain.value = gain;
> > >     audioNode.connect(gainNode);
> > >     gainNode.connect(context.destination);
> > >   } 
> > > 
> > > and i'm not append video(with audio) element to document body. 
> > > i use canvas.
> > 
> > Wow, it works :) Thanks for sharing. Before, I tested this one on MacOS
> > Safari but not work. Only work on iOS device :). I set gain 4 to iPhone and
> > 2 to iPad.  The <audio> and <video> tag (play file by url not remote stream)
> > is still very low volume
> 
> still very low volume <== it'll be ok if use audio context for playing audio
> file.

No. (In reply to neo from comment #21)
> (In reply to Phong Le from comment #20)
> > (In reply to neo from comment #18)
> > > (In reply to Phong Le from comment #16)
> > > > Could you guide about how to use AudioContext to play this remote stream? I
> > > > researched and when using AudioContext to play, we must attach with an audio
> > > > element. Thanks
> > > 
> > > i tested iOS 15. (wkWebview)
> > > 
> > > // audio stream example
> > >  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
> > >     const context: AudioContext = window.AudioContext ||
> > > window.webkitAudioContext;
> > >     const audioNode = context.createMediaStreamSource(remoteAudioStream);
> > >     const gainNode: GainNode = context.createGain();
> > >     // some device volume too low ex) iPad
> > >     gainNode.gain.value = gain;
> > >     audioNode.connect(gainNode);
> > >     gainNode.connect(context.destination);
> > >   } 
> > > 
> > > and i'm not append video(with audio) element to document body. 
> > > i use canvas.
> > 
> > Wow, it works :) Thanks for sharing. Before, I tested this one on MacOS
> > Safari but not work. Only work on iOS device :). I set gain 4 to iPhone and
> > 2 to iPad.  The <audio> and <video> tag (play file by url not remote stream)
> > is still very low volume
> 
> still very low volume <== it'll be ok if use audio context for playing audio
> file.

Yup. But I need to use media element tag to play. However, createMediaElementSource on ios safari hadn't worked for long time

[neo]

> 
> Yup. But I need to use media element tag to play. However,
> createMediaElementSource on ios safari hadn't worked for long time

hi
we no need to use createMediaElementSource for playing audio file.
how about use decodeAudioData.


window.onload = function(){
    var context = new AudioContext() || new webkitAudioContext(),
        request = new XMLHttpRequest();
    
    request.open("GET", "audio_file.mp3", true);
    request.responseType = "arraybuffer";
    request.onload = function(){
        context.decodeAudioData(request.response, onDecoded);
    }
    
    function onDecoded(buffer){
        var bufferSource = context.createBufferSource();
        bufferSource.buffer = buffer;
        bufferSource.connect(context.destination);
        bufferSource.start();
    }
    
    request.send();
};

[Paul]

We are running into this same issue - our website has been working for 3 years on all major browsers except IE. We do need to play audio at the same time as recording. We are beginning to get complaints.

[Paul]

The hack of adding the gain node works for us - sort of. Safari 15 on MacOS doesn't have the problem so I look at the User Agent and only apply the hack if the client is Safari 15 and mobile. That keeps from breaking browsers that don't have this bug.

However, I can't figure out how to distinguish between iPad and MacbookPro, so iPad is still broken. That's better than nothing, though, since iphones outnumber ipads in our user base.

BTW, we only have a few test devices but adding a gain of 10 seems to be approximately right.

The other thing we're worried about is that if this gets fixed then all of the sudden we'll be blasting iphone users out.

[Phong Le]

(In reply to Paul from comment #26)
> The hack of adding the gain node works for us - sort of. Safari 15 on MacOS
> doesn't have the problem so I look at the User Agent and only apply the hack
> if the client is Safari 15 and mobile. That keeps from breaking browsers
> that don't have this bug.
> 
> However, I can't figure out how to distinguish between iPad and MacbookPro,
> so iPad is still broken. That's better than nothing, though, since iphones
> outnumber ipads in our user base.
> 
> BTW, we only have a few test devices but adding a gain of 10 seems to be
> approximately right.
> 
> The other thing we're worried about is that if this gets fixed then all of
> the sudden we'll be blasting iphone users out.

More, if the user plug a headset and we still keep gain 10. Then, it would be very very high volume :(. We cannot do anything here because we cannot detect when users plug their headset. We must wait for fixing this issue

[Varun D]

(In reply to Brendan Del Rosario from comment #19)
> (In reply to neo from comment #18)
> > (In reply to Phong Le from comment #16)
> > > Could you guide about how to use AudioContext to play this remote stream? I
> > > researched and when using AudioContext to play, we must attach with an audio
> > > element. Thanks
> > 
> > i tested iOS 15. (wkWebview)
> > 
> > // audio stream example
> >  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
> >     const context: AudioContext = window.AudioContext ||
> > window.webkitAudioContext;
> >     const audioNode = context.createMediaStreamSource(remoteAudioStream);
> >     const gainNode: GainNode = context.createGain();
> >     // some device volume too low ex) iPad
> >     gainNode.gain.value = gain;
> >     audioNode.connect(gainNode);
> >     gainNode.connect(context.destination);
> >   } 
> > 
> > and i'm not append video(with audio) element to document body. 
> > i use canvas.
> 
> This workaround allowed us(OP/Les, Mike & Brendan) to be able to hear the
> remote audio at an appropriate level. We set our gain value to 10 for now
> and will tweak as needed (increasing too much can cause clipping). The
> quality of audio is slightly lower than that of iOS 14 but for the time
> being it is a workaround that gets us closer to previous functionality.
> Thank you very much for posting this!

Can this work if we have many peer's audio stream coming in?
Also, should the first line of this function be
const context = new (window.AudioContext || window.webkitAudioContext)();
Otherwise, createMediaStreamsource fails.

[Pablo Fuente]

Hi,

We at @openvidu are also experiencing this problem. From iOS 15, when using Safari audio is coming out through both the earpiece and the main speaker, but the total output volume is reduced about 1/2 to 2/3, comparing it to Safari in iOS 14.
I can provide some more information: if the user stops the camera clicking on the navigation bar "Stop Using Camera" button, then the receiving audio gets automatically back to a normal level.

[Phong Le]

@@ A month from reported day and nobody is assigned to investigate to fix. Why? How an super big company as Apple has lack of developers to resolve this one

[Luca Simonetti]

we're experiencing the same issue with a cordova app. Exactly same behavior. I sure hope this is being taken care of.

[youenn fablet]

This is being worked on but it is not clear yet whether changes in WebKit will be needed.

[Phong Le]

Cool. I hope that it's fixed asap :(. Many people are influenced seriously. We don't have anyway to make it workound now(In reply to youenn fablet from comment #32)
> This is being worked on but it is not clear yet whether changes in WebKit
> will be needed.

Cool. I hope that it's fixed asap :(. Many people are influenced seriously. We don't have anyway to make it workound now. Using AudioContext is bad solution. If the user plug a headset and we still keep gain 10. Then, it would be very very high volume :(. We cannot do anything here because we cannot detect when users plug their headset. We must wait for fixing this issue

Any update here? This has a *very* noticeable user impact and, like Phong mentioned, there is no viable workaround as increasing gain causes the opposite problem for users with headsets. Given the impact, updates on this ticket, rather than just on the internal Radar issue, would be very much appreciated.

[Mina]

I completely agree with you, the issue is causing a noticeable bad impact on our end users too.
I really appreciate any updates here.

[bdesai]

We are facing the same problem as well. we are highly relied on webRTC for our workflow. Would be great to have some progress on this one.

[Luca Simonetti]

Same here, we are currently suggesting users to use our app with headphones. 
And obviously it's not a solution nor a workaround but a real limitation.

[seanoshea]

Pinging on this here too to see if this can get prioritized. We're running into this on a daily basis.

[ivalencia]

We are being hit by this bug as well, a quick turnaround will be highly appreciated. Thanks.

[Natch]

Completely agree with Luca - switching to headphones is not a plausible solution.
Would really appreciate to see this one get resolved soon.

[Octavio Pinto]

Any updates, yet? Really impacting user experience.

[JoshSauder]

We're also frequently experiencing this same issue. Would also appreciate an update on this issue.

[melvin bos]

This is greatly impacting end user experience and please patch this soon. thanks in advance.

[Freet30]

This need to be patch.  Anyone tried new beta?

[Dana Chandler]

I agree with previous comments.  The is seriously affecting user experience and would be nice if this was prioritized.  Any updates you could provide would be greatly appreciated.

[Andrei Rebegea]

Please fix this regression. It impacts our users.

[neo]

iOS 15.1 low sound issue.

this works for me 
1. create new audio context (before getUserMedia. important!)
2. getUserMedia
3. use audio context to play remote audio and sound
hope this helps

[Mina]

I think the issue is related to webkit not safari, I've tested the same on Firefox on iOS which is webkit based and the issue occurred too.

[Freet30]

Sometimes plug in headphones and unplug them the audio goes to normal.

[Phong Le]

This is a critical issue. Please fix asap

[Phong Le]

At https://bugs.webkit.org/show_bug.cgi?id=232873, youenn fablet updated WebRTC lib. Does anyone know how to check this issue work on this patch?

[Yazz]

Wondering if there is any progress in this issue, we are recommending users to not use IPAD/IPHONE currently, which is not so good :(

[Phong Le]

(In reply to Yazz from comment #52)
> Wondering if there is any progress in this issue, we are recommending users
> to not use IPAD/IPHONE currently, which is not so good :(

Yeap, they move to use Android and Chrome on Windows becauase this one

[Matthew Windwer]

Waiting to hear as well. Hoping this will be fixed for iOS 15.2. Does anybody know?

[Zach Rattner]

If anyone on this thread is able to reliably reproduce this bug on iOS 15.1, you could try out the iOS 15.2 beta and see if the issue resolved: 

https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-15_2-release-notes

I know I, for one, would appreciate it if anyone could do this and report back here. Probably others would too.

My team's attempts at reproducing on iOS 15.1 were intermittent and I haven't had a chance to chase down exactly why yet. Will share if we figure anything out.

[Zach Rattner]

If anyone on this thread is able to reliably reproduce this bug on iOS 15.1, you could try out the iOS 15.2 beta and see if the issue resolved: 

https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-15_2-release-notes

I know I, for one, would appreciate it if anyone could do this and report back here. Probably others would too.

My team's attempts at reproducing on iOS 15.1 were intermittent and I haven't had a chance to chase down exactly why yet. Will share if we figure anything out.

[Marcus G]

(In reply to Zach Rattner from comment #56)
> If anyone on this thread is able to reliably reproduce this bug on iOS 15.1,
> you could try out the iOS 15.2 beta and see if the issue resolved: 
> 
> https://developer.apple.com/documentation/ios-ipados-release-notes/ios-
> ipados-15_2-release-notes
> 
> I know I, for one, would appreciate it if anyone could do this and report
> back here. Probably others would too.
> 
> My team's attempts at reproducing on iOS 15.1 were intermittent and I
> haven't had a chance to chase down exactly why yet. Will share if we figure
> anything out.

I have tried it on an iPhone 10XS with 5.2 beta 2 and it has not been fixed.
The audio is still low with our web app.

[Marcus G]

(In reply to Marcus G from comment #57)
> (In reply to Zach Rattner from comment #56)
> > If anyone on this thread is able to reliably reproduce this bug on iOS 15.1,
> > you could try out the iOS 15.2 beta and see if the issue resolved: 
> > 
> > https://developer.apple.com/documentation/ios-ipados-release-notes/ios-
> > ipados-15_2-release-notes
> > 
> > I know I, for one, would appreciate it if anyone could do this and report
> > back here. Probably others would too.
> > 
> > My team's attempts at reproducing on iOS 15.1 were intermittent and I
> > haven't had a chance to chase down exactly why yet. Will share if we figure
> > anything out.
> 
> I have tried it on an iPhone 10XS with 5.2 beta 2 and it has not been fixed.
> The audio is still low with our web app.

Sorry 15.2 beta 2.

[[e-mail]]

the issue is not fixed on 15.2 beta and 15.2beta2 on devices below,
iphone 12 pro
iphone 12 
iphone 7
ipad gen 8

[Phong Le]

(In reply to [e-mail] from comment #59)
> the issue is not fixed on 15.2 beta and 15.2beta2 on devices below,
> iphone 12 pro
> iphone 12 
> iphone 7
> ipad gen 8

Thank for this announcement. This is actually critical issue for web based call applications. Hope that Apple will fix it asap :(

[Marcus G]

Bug still in iOS 15.2 public beta 3

Just checked the new released 15.2 public beta 3 on an iPhone XS and the issue has not been fixed.  Audio is still low on connection to our audio web app. Opening an additional browser window while the audio is running in the original window brings the audio back to a normal level. User can then go back to the original browser window, but most users are not going to figure this out.

[Paul]

(In reply to Zach Rattner from comment #56)
> My team's attempts at reproducing on iOS 15.1 were intermittent and I
> haven't had a chance to chase down exactly why yet. Will share if we figure
> anything out.

Zach, it happens every time in our website. If you'd like to see it contact me and we can give you an account.

[Johnny V]

To reproduce the issue all you have to do is go here on an iPhone/Pad https://webrtc.github.io/samples/src/content/devices/input-output/

When speaking into the microphone of an iPhone it is clear the sound is coming out of the headset instead of the speaker.

[Mina]

Hi Guys,

My colleges did something like 

mediaStream.getAudioTracks()[0].enabled = false;
setTimeout(() => {						        mediaStream.getAudioTracks()[0].enabled = true;
}, 1500);

they reported hearing echo sound which was never happening before, can anybody help verifying it on your end too?

We tested iOS 15.1 and 15.0

[Teodor]

We tried overriding audio route (kAudioSessionOverrideAudioRoute_Speaker) while WebRTC audio was being played through earpiece – we are seeing this issue in WKWebView as well as Safari – and the result is that the entire WebRTC call crashes.

If anybody has any stable (reproducible) workarounds, even if they rely on executing native code, please share. It seems we won't see a fix in 15.3, and we are looking at one more month and a half with this bug, and that's if we are lucky.

[Marcus G]

(In reply to Johnny V from comment #63)
> To reproduce the issue all you have to do is go here on an iPhone/Pad
> https://webrtc.github.io/samples/src/content/devices/input-output/
> 
> When speaking into the microphone of an iPhone it is clear the sound is
> coming out of the headset instead of the speaker.

We have the same low audio issue using airPods and other bluetooth devices (car audio) as well. So it seems to go beyond a headset/speaker routing issue.

[Phong Le]

(In reply to Marcus G from comment #66)
> (In reply to Johnny V from comment #63)
> > To reproduce the issue all you have to do is go here on an iPhone/Pad
> > https://webrtc.github.io/samples/src/content/devices/input-output/
> > 
> > When speaking into the microphone of an iPhone it is clear the sound is
> > coming out of the headset instead of the speaker.
> 
> We have the same low audio issue using airPods and other bluetooth devices
> (car audio) as well. So it seems to go beyond a headset/speaker routing
> issue.

@@ Super critical issue. :(. Apple should be aware of fixing this one asap

[Teodor]

Can anybody confirm that this issue is NOT reproducible on iPhone 8 (model number MQ6W2LL/A) with iOS 15.1?

I could join a call with it 10+ times in a row and sound was coming out of the speaker every time. Comment 59 mentions iPhone 7, so iPhone 8 may be the only exception.

If this is the case, then gain workaround must not be applied on iPhone 8. Media query to detect it is "only screen and (device-width: 375px) and (device-height: 667px) and (-webkit-device-pixel-ratio: 2)".

[Varun D]

I tried a solution mentioned the last comment by David on this thread 
https://bugs.webkit.org/show_bug.cgi?id=218012
It partially improved the volume.

However, as soon as Mic permission was granted - peer volume dropped to very poor.

[Varun D]

I tried a solution mentioned the last comment by David on this thread 
https://bugs.webkit.org/show_bug.cgi?id=218012
It partially improved the volume.

However, as soon as Mic permission was granted - peer volume dropped to very poor.

[Jacob]

We are experiencing this on our video chat app on ios 15.1.1 but not ios 15.0.1

[Johnny V]

I wanted to let everyone know that new evidence suggests that WebRTC sessions in iOS15.1 with Stereo Opus Audio come in at full volume whereas Mono Opus Audio does not.

https://meeting.anycompany.xyz/ can be used to test the Mono Audio
https://demo.millicast.com/ can be used to test the Stereo Audio

It is possible that some other factor is in play here.  Just wanted to update everyone so get more eyes on this.

[Varun D]

(In reply to Johnny V from comment #72)
> I wanted to let everyone know that new evidence suggests that WebRTC
> sessions in iOS15.1 with Stereo Opus Audio come in at full volume whereas
> Mono Opus Audio does not.
> 
> https://meeting.anycompany.xyz/ can be used to test the Mono Audio
> https://demo.millicast.com/ can be used to test the Stereo Audio
> 
> It is possible that some other factor is in play here.  Just wanted to
> update everyone so get more eyes on this.

When viewing millicast video, was mic permission asked & granted? 
when mic permission is granted - that is when volume drops on iphone.

[Johnny V]

(In reply to Varun D from comment #73)
> (In reply to Johnny V from comment #72)
> > I wanted to let everyone know that new evidence suggests that WebRTC
> > sessions in iOS15.1 with Stereo Opus Audio come in at full volume whereas
> > Mono Opus Audio does not.
> > 
> > https://meeting.anycompany.xyz/ can be used to test the Mono Audio
> > https://demo.millicast.com/ can be used to test the Stereo Audio
> > 
> > It is possible that some other factor is in play here.  Just wanted to
> > update everyone so get more eyes on this.
> 
> When viewing millicast video, was mic permission asked & granted? 
> when mic permission is granted - that is when volume drops on iphone.

Do you have a test URL where I can try this?  The https://meeting.anycompany.xyz/ will not let me in the room without enabling Camera and Microphone on iOS 15.1

[Varun D]

(In reply to Varun D from comment #73)
> (In reply to Johnny V from comment #72)
> > I wanted to let everyone know that new evidence suggests that WebRTC
> > sessions in iOS15.1 with Stereo Opus Audio come in at full volume whereas
> > Mono Opus Audio does not.
> > 
> > https://meeting.anycompany.xyz/ can be used to test the Mono Audio
> > https://demo.millicast.com/ can be used to test the Stereo Audio
> > 
> > It is possible that some other factor is in play here.  Just wanted to
> > update everyone so get more eyes on this.
> 
> When viewing millicast video, was mic permission asked & granted? 
> when mic permission is granted - that is when volume drops on iphone.

I have tried this working on a WebRTC solution for client - cant share the URL.
More details here https://bugs.webkit.org/show_bug.cgi?id=218012'

As I understand, for viewing milicast video - mic permission is not needed - and that is making the difference.

[Matthew Windwer]

Twilio has indicated that this bug is resolved in iOS 15.2 beta 4:
https://github.com/twilio/twilio-video.js/issues/1586#issuecomment-985094190

Has anybody else confirmed?

[Marcus G]

(In reply to mattwindwer from comment #76)
> Twilio has indicated that this bug is resolved in iOS 15.2 beta 4:
> https://github.com/twilio/twilio-video.js/issues/1586#issuecomment-985094190
> 
> Has anybody else confirmed?

On an iPhone XS this is NOT resolved for the speakers with iOS 15.2 beta 4. There is some progress though.

My initial testing with an iPhone XS and iOS 15.2 beta 4 is that volume is still very LOW (unusable) with the SPEAKERS, but... with bluetooth airPods or bluetooth car audio or wired apple earphones the audio is at a normal level again and sounds good.

To get normal level with the speakers, if you open another browser window to some other web site after you have opened the audio site, then the speaker level reverts to normal volume for the duration of the session.

So, definitely progress with the 1 phone I have tested with but not resolved. I have an iPhone 7 that I will update and test with as well.

All testing was done with Safari.

[Lee]

We are seeing this, although our use case is slightly different, we have (intermittently) very low audio on non-WebRTC video playback while microphone access is granted.

[Johnny V]

(In reply to Lee from comment #78)
> We are seeing this, although our use case is slightly different, we have
> (intermittently) very low audio on non-WebRTC video playback while
> microphone access is granted.

Check https://bugs.webkit.org/show_bug.cgi?id=218012

[Marcus G]

(In reply to Marcus G from comment #77)
> (In reply to mattwindwer from comment #76)
> > Twilio has indicated that this bug is resolved in iOS 15.2 beta 4:
> > https://github.com/twilio/twilio-video.js/issues/1586#issuecomment-985094190
> > 
> > Has anybody else confirmed?
> 
> On an iPhone XS this is NOT resolved for the speakers with iOS 15.2 beta 4.
> There is some progress though.
> 
> My initial testing with an iPhone XS and iOS 15.2 beta 4 is that volume is
> still very LOW (unusable) with the SPEAKERS, but... with bluetooth airPods
> or bluetooth car audio or wired apple earphones the audio is at a normal
> level again and sounds good.
> 
> To get normal level with the speakers, if you open another browser window to
> some other web site after you have opened the audio site, then the speaker
> level reverts to normal volume for the duration of the session.
> 
> So, definitely progress with the 1 phone I have tested with but not
> resolved. I have an iPhone 7 that I will update and test with as well.
> 
> All testing was done with Safari.

FOLLOW UP - 15.2 RC (19C56) released Dec 7, 2021:

As far as I can tell the progress that was made in 15.2 public beta 4 did not make it into 15.2 RC (19C56). The 15.2 RC has all audio levels low again regardless of it being the speakers, bluetooth, or wired headphones on a iPhone XS. This is with a WebRTC audio streaming web app.

[Peter]

Is there an ETA on fixing this? This is a major bug and I'm really shocked that has gone on this long.

[Mahmoud]

Can someone take a look on this bug ?
We are running a peer to peer streaming service based on WebRTC and this bug decrease the value of our product drastically. At least tell us an ETA on what we can expect so we can act upon it towards our clients. 

How could Apple afford this kind of major flow to be in the system for so long ? This makes iPhone useless.

[Mahmoud]

Is there any reference ticket created about the issue on Apple side which can be accessed publicly?

[youenn fablet]

A first fix should have landed in iOS 15.2 beta.
If the issue still reproduces in the latest iOS 15.2 beta, please provide repro steps.
Thanks.

[Marcus G]

(In reply to youenn fablet from comment #84)
> A first fix should have landed in iOS 15.2 beta.
> If the issue still reproduces in the latest iOS 15.2 beta, please provide
> repro steps.
> Thanks.

Hello,

It seems 15.2 RC (19C56) has lost some of the progress made with 15.2 beta 4.

It seems there was a partial fix with 15.2 beta 4. The volume level was normal again with bluetooth devices and directly plugged apple headphones, but NOT with speakers. Speakers were at about 50% volume which makes it difficult to use the app.

But with 15.2 RC (19C56) we are experiencing the same issue as before.  Low audio in all devices unchanged from the original problem.

On an iPhone XS, if you first connect to the site that has audio and then open another browser window to some other web site, the audio jumps up to a normal level. This work around may not work, though, on an iPhone 13.

I will PM you a link you can use to reproduce the issue.

Thanks

[youenn fablet]

That is not expected, I'll look at that.
Btw, the fix I am talking about is only for MediaStreamTrack audio rendering at the moment.

(In reply to Marcus G from comment #85)
> (In reply to youenn fablet from comment #84)
> > A first fix should have landed in iOS 15.2 beta.
> > If the issue still reproduces in the latest iOS 15.2 beta, please provide
> > repro steps.
> > Thanks.
> 
> Hello,
> 
> It seems 15.2 RC (19C56) has lost some of the progress made with 15.2 beta 4.
> 
> It seems there was a partial fix with 15.2 beta 4. The volume level was
> normal again with bluetooth devices and directly plugged apple headphones,
> but NOT with speakers. Speakers were at about 50% volume which makes it
> difficult to use the app.
> 
> But with 15.2 RC (19C56) we are experiencing the same issue as before.  Low
> audio in all devices unchanged from the original problem.
> 
> On an iPhone XS, if you first connect to the site that has audio and then
> open another browser window to some other web site, the audio jumps up to a
> normal level. This work around may not work, though, on an iPhone 13.
> 
> I will PM you a link you can use to reproduce the issue.
> 
> Thanks

[seanoshea]

I see 15.2 is out now. Is this fix considered closed for all iPhone models now (I did see some chatter in this bug report about iPhone XS still having this issue)

[Marcus G]

(In reply to seanoshea from comment #87)
> I see 15.2 is out now. Is this fix considered closed for all iPhone models
> now (I did see some chatter in this bug report about iPhone XS still having
> this issue)

15.2 RC (19C56) on an iPhone XS does not resolve the low audio issue as far as I can tell. We still have the original issue with no change.

[Mahmoud]

Hey everyone.
I tried it on our WEBRtc based site with the new 15.2 on an iPhone 11 pro max device and it seems to be resolved.

You can test it here: https://airtalk.live

[Peter]

I have tested with 15.2 RC in my own WebRTC app and I would say it’s improved but is definitely not “fixed”. On an iPhone 13 Pro which has perhaps the loudest and clearest speakers of any iPhone, turning the volume up to 100% makes it just barely loud enough to be usable. This can’t possibly be considered acceptable, as any other audio played at this volume would be blaring and heard from a long distance. By comparison, the WebRTC audio is just barely loud enough to be used when held 10 inches away from your face.

[Kat]

Tested with IOS 15.2 and it definitely is not fixed.

[Ed Umansky]

I tested this with the newly released 15.2, and the issue is slightly improved but not fixed. It looks like now the audio comes out of both the earpiece speaker at the top of the phone and the main speaker at the bottom, whereas before it only came out of the earpiece. However, the audio volume is still very low, so it's a bit louder than before and semi-usable at maximum volume, but far from fixed.

[Peter]

^ My results are exactly the same as Ed. I have no idea how this can be marked as fixed.

[Mahmoud]

+1 

My obervation was too fast yesterday. It seems volume level is increased but not to a satisfying level unfortunately.

[Jacob]

We are also seeing that it is improved but not fixed, still low unless at full volume.

[Michael Korkaris]

Any workarounds on this? Still waiting for a fix

[Varun D]

(In reply to Michael Korkaris from comment #96)
> Any workarounds on this? Still waiting for a fix

I have one working - please check my previous comments.

[Yuwei Zhang]

15.3(19D5026g) still has not fixed this problem, I hope Apple engineers can tell the cause of this problem and ways to avoid it.

[Phong Le]

(In reply to Yuwei Zhang from comment #98)
> 15.3(19D5026g) still has not fixed this problem, I hope Apple engineers can
> tell the cause of this problem and ways to avoid it.

Sad. My customers now are very disappointed with the issue. Hope Apple can spend time to investigate and resolve it in 15.4 version :(

[GARY]

(In reply to neo from comment #18)
> (In reply to Phong Le from comment #16)
> > Could you guide about how to use AudioContext to play this remote stream? I
> > researched and when using AudioContext to play, we must attach with an audio
> > element. Thanks
> 
> i tested iOS 15. (wkWebview)
> 
> // audio stream example
>  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
>     const context: AudioContext = window.AudioContext ||
> window.webkitAudioContext;
>     const audioNode = context.createMediaStreamSource(remoteAudioStream);
>     const gainNode: GainNode = context.createGain();
>     // some device volume too low ex) iPad
>     gainNode.gain.value = gain;
>     audioNode.connect(gainNode);
>     gainNode.connect(context.destination);
>   } 
> 
> and i'm not append video(with audio) element to document body. 
> i use canvas.

I have embedded a YouTube live stream into my iOS app, and I am getting very low volume, even with the device volume and YouTube volume at MAX, so I assume I am experiencing the bug reported here.  I would like to try your solution; however, my app is coded entirely in Objective C, and I have no Swift coding knowledge.

Normally, I can convert simple Swift code to Objective C, but I tried for several hours with your code, and got nowhere.  I even tried adding a Swift module to my app, but the compiler complained about not finding the MediaStream, AudioContext, and GainNode types.  Importing every framework I could think of had no effect.

Any chance you could provide an Objective C version of your solution?

[GARY]

(In reply to neo from comment #18)
> (In reply to Phong Le from comment #16)
> > Could you guide about how to use AudioContext to play this remote stream? I
> > researched and when using AudioContext to play, we must attach with an audio
> > element. Thanks
> 
> i tested iOS 15. (wkWebview)
> 
> // audio stream example
>  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
>     const context: AudioContext = window.AudioContext ||
> window.webkitAudioContext;
>     const audioNode = context.createMediaStreamSource(remoteAudioStream);
>     const gainNode: GainNode = context.createGain();
>     // some device volume too low ex) iPad
>     gainNode.gain.value = gain;
>     audioNode.connect(gainNode);
>     gainNode.connect(context.destination);
>   } 
> 
> and i'm not append video(with audio) element to document body. 
> i use canvas.

Upon further investigation, I see now that WebRTC is a framework in and of itself, and I realize that your code may not actually be Swift.  I was wondering why I had to change the ‘const’ keywords to ‘let’ and the ‘function’ keyword to ‘func’.  :-)

Now I am not even sure that my request for an Objective C version of your code makes any sense?

(In reply to GARY from comment #101)
> (In reply to neo from comment #18)
> > (In reply to Phong Le from comment #16)
> > > Could you guide about how to use AudioContext to play this remote stream? I
> > > researched and when using AudioContext to play, we must attach with an audio
> > > element. Thanks
> > 
> > i tested iOS 15. (wkWebview)
> > 
> > // audio stream example
> >  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
> >     const context: AudioContext = window.AudioContext ||
> > window.webkitAudioContext;
> >     const audioNode = context.createMediaStreamSource(remoteAudioStream);
> >     const gainNode: GainNode = context.createGain();
> >     // some device volume too low ex) iPad
> >     gainNode.gain.value = gain;
> >     audioNode.connect(gainNode);
> >     gainNode.connect(context.destination);
> >   } 
> > 
> > and i'm not append video(with audio) element to document body. 
> > i use canvas.
> 
> Upon further investigation, I see now that WebRTC is a framework in and of
> itself, and I realize that your code may not actually be Swift.  I was
> wondering why I had to change the ‘const’ keywords to ‘let’ and the
> ‘function’ keyword to ‘func’.  :-)
> 
> Now I am not even sure that my request for an Objective C version of your
> code makes any sense?

The code on comment #18 is Javascript code. not Objective c or Swift

[GARY]

(In reply to rychouwei from comment #102)
> (In reply to GARY from comment #101)
> > (In reply to neo from comment #18)
> > > (In reply to Phong Le from comment #16)
> > > > Could you guide about how to use AudioContext to play this remote stream? I
> > > > researched and when using AudioContext to play, we must attach with an audio
> > > > element. Thanks
> > > 
> > > i tested iOS 15. (wkWebview)
> > > 
> > > // audio stream example
> > >  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
> > >     const context: AudioContext = window.AudioContext ||
> > > window.webkitAudioContext;
> > >     const audioNode = context.createMediaStreamSource(remoteAudioStream);
> > >     const gainNode: GainNode = context.createGain();
> > >     // some device volume too low ex) iPad
> > >     gainNode.gain.value = gain;
> > >     audioNode.connect(gainNode);
> > >     gainNode.connect(context.destination);
> > >   } 
> > > 
> > > and i'm not append video(with audio) element to document body. 
> > > i use canvas.
> > 
> > Upon further investigation, I see now that WebRTC is a framework in and of
> > itself, and I realize that your code may not actually be Swift.  I was
> > wondering why I had to change the ‘const’ keywords to ‘let’ and the
> > ‘function’ keyword to ‘func’.  :-)
> > 
> > Now I am not even sure that my request for an Objective C version of your
> > code makes any sense?
> 
> The code on comment #18 is Javascript code. not Objective c or Swift

Thanks for the info.  I guess I should have figured that, since the WebKit engine is JavaScript; however, my only exposure to WebKit has been via the use of its WKWebView, which I access from Objective C.  (In reply to rychouwei from comment #102)
> (In reply to GARY from comment #101)
> > (In reply to neo from comment #18)
> > > (In reply to Phong Le from comment #16)
> > > > Could you guide about how to use AudioContext to play this remote stream? I
> > > > researched and when using AudioContext to play, we must attach with an audio
> > > > element. Thanks
> > > 
> > > i tested iOS 15. (wkWebview)
> > > 
> > > // audio stream example
> > >  function connectToSpeaker(remoteAudioStream: MediaStream, gain: number) {
> > >     const context: AudioContext = window.AudioContext ||
> > > window.webkitAudioContext;
> > >     const audioNode = context.createMediaStreamSource(remoteAudioStream);
> > >     const gainNode: GainNode = context.createGain();
> > >     // some device volume too low ex) iPad
> > >     gainNode.gain.value = gain;
> > >     audioNode.connect(gainNode);
> > >     gainNode.connect(context.destination);
> > >   } 
> > > 
> > > and i'm not append video(with audio) element to document body. 
> > > i use canvas.
> > 
> > Upon further investigation, I see now that WebRTC is a framework in and of
> > itself, and I realize that your code may not actually be Swift.  I was
> > wondering why I had to change the ‘const’ keywords to ‘let’ and the
> > ‘function’ keyword to ‘func’.  :-)
> > 
> > Now I am not even sure that my request for an Objective C version of your
> > code makes any sense?
> 
> The code on comment #18 is Javascript code. not Objective c or Swift

Thanks for the info.  Since WebKit’s engine is JavaScript, I probably should have figured that.  My total exposure to WebKit has been limited to the WKWebView object, which I have been able to access in Xcode via Objective C, but I guess I will need to start looking into Xcode’s JavaScriptCore framework ... if I want to solve this low volume problem.

[Silvia Pfeiffer]

Hi all,

Is there any indication that this will be worked on?

We have extensive problems with our video telehealth platform.
All patients that use iOS (iPhone or iPad) and don't use headphones are exposed to this bug.
We have over 70,000 clinicians using our platform and thousands of patients each day that cannot hold a consultation.

We've had to implement a volume slider in our web app for patients to increase the volume and even then they cannot properly hear the clinician, ending up moving the call to phones instead of webrtc.

It's starting to become a reputational issue for us with people not trusting our platform any longer.

Can I please please get an indication that this is going to get fixed. Thousands of patients and clinicians will be grateful.

[Silvia Pfeiffer]

I'm told the actual problem is under WebRTC, so @othermaciej and @youenn

[Simon Fraser (smfr)]

The "See also" bugs above relate to additional fixes in this area.

[Silvia Pfeiffer]

(In reply to Simon Fraser (smfr) from comment #106)
> The "See also" bugs above relate to additional fixes in this area.

Those fixes were applied in November and released with 15.2 and neither 15.2 nor 15.3 has this issue fixed.

We now have to use the AudioContext approach to by default increase iOS volume for our video calls by 800% to allow hearing the audio as the majority of our customers don't use headsets and wouldn't know how to turn up the volume via a slider in the app as compared to the volume button on the device. We just hope that for those that do use a headset, they are fast at turning down the volume before destroying their hearing.

This is not a tenable solution. Please prioritise working on this issue - 4 months has been a long time!

[Peter]

It’s incomprehensible that this bug has gone on so long. It’s akin to abandoning WebRTC on iOS.

[youenn fablet]

(In reply to Silvia Pfeiffer from comment #107)
> (In reply to Simon Fraser (smfr) from comment #106)
> > The "See also" bugs above relate to additional fixes in this area.
> 
> Those fixes were applied in November and released with 15.2 and neither 15.2
> nor 15.3 has this issue fixed.

One fix has shipped, not the others.

> We now have to use the AudioContext approach to by default increase iOS
> volume for our video calls by 800% to allow hearing the audio as the
> majority of our customers don't use headsets and wouldn't know how to turn
> up the volume via a slider in the app as compared to the volume button on
> the device. We just hope that for those that do use a headset, they are fast
> at turning down the volume before destroying their hearing.

I am surprised x8 is needed on latest iOS, https://bugs.webkit.org/show_bug.cgi?id=232941 is doing x5.

> This is not a tenable solution. Please prioritise working on this issue - 4
> months has been a long time!

https://bugs.webkit.org/show_bug.cgi?id=233316 should fully fix the audio level issue.
I'll let know this thread when this gets testable.

[Sun]

Here at a french agency, we first noticed the issue in September 2021 (https://discussions.apple.com/thread/253190228?answerId=255976213022&cid=em-com-apple_watches_email_thread_owner-view_the_full_discussion-en-us-11192020#255976213022). We are in contact with Apple since October 2021 for this issue that severely affects one of our projet. Despite many exchanges, a very nice lady on the phone, and the fact that I had to share my iPhone logs, nothing useful from "the tech team" behind. Looks like "they don't reproduce"...

Just uploaded to OS 15.3 ---> STILL NOT FIXED

Seriously, Apple, are you working on it, what is going on? Has someone has any news?

[Bernardo Gontijo]

It is so sad that a company like Apple left this open for so long.
We have lost a lot of clients because of this issue.
We are thinking of creating an app to stop using safari.

[youenn fablet]

Could anybody try out iOS 15.4 latest beta?

[Marcus G]

(In reply to youenn fablet from comment #112)
> Could anybody try out iOS 15.4 latest beta?

Has this been released for public beta or is it developer? My iPhone XS (public beta) is not finding it (currently at 15.3-19D49). I will test it if I can get it installed.

[Dag-Inge Aas]

Reports on Twitter that the issue has been resolved in 15.4 on iPhone XS. https://twitter.com/christer_a_j/status/1486828979168464897?s=21 I’ll get around to testing my devices tomorrow.

[Yuwei Zhang]

I just updated the latest 15.4 beta on my iphone 12 and it seems to have fixed the issue, I will continue to test more.

[youenn fablet]

Thanks for the testing, please ping me or file any bug you may encounter during that testing.

To summarise:
- In iOS 15 and 15.1, web apps might need a workaround with a big volume gain
- In iOS 15.2 and iOS 15.3, web apps may or may not need the gain workaround. If needed, it should be smaller than previous iOS 14 versions.
- In iOS 15.4 beta, no workaround should be needed.

[Misha]

(In reply to youenn fablet from comment #116)
> Thanks for the testing, please ping me or file any bug you may encounter
> during that testing.
> 
> To summarise:
> - In iOS 15 and 15.1, web apps might need a workaround with a big volume gain
> - In iOS 15.2 and iOS 15.3, web apps may or may not need the gain
> workaround. If needed, it should be smaller than previous iOS 14 versions.
> - In iOS 15.4 beta, no workaround should be needed.

Hello, thanks for pointing to this summary.
Do you know what could cause this issue? webkit bug/safari bug/ios bug?

[Daniel ORorke - Vonage]

Hi Youenn,
The problem with with the proposed workaround is that the issue is not present on all devices - iPhone 8 for example will not exhibit this behavior. Using the big audio volume gain will damage someone's device or hearing. We need more information to be able to use this workaround effectively.

Which devices do and which versions do not need this? How can we detect when the workaround is needed or may result in a very unpleasant (deafening) experience for the user? "sometimes" for iOS 15 - 15.3.x is not specific enough to safely implement.

Glad this appears to be resolved in iOS 15.4.



(In reply to youenn fablet from comment #116)
> Thanks for the testing, please ping me or file any bug you may encounter
> during that testing.
> 
> To summarise:
> - In iOS 15 and 15.1, web apps might need a workaround with a big volume gain
> - In iOS 15.2 and iOS 15.3, web apps may or may not need the gain
> workaround. If needed, it should be smaller than previous iOS 14 versions.
> - In iOS 15.4 beta, no workaround should be needed.

[Krieger]

(In reply to youenn fablet from comment #116)
> Thanks for the testing, please ping me or file any bug you may encounter
> during that testing.
> 
> To summarise:
> - In iOS 15 and 15.1, web apps might need a workaround with a big volume gain
> - In iOS 15.2 and iOS 15.3, web apps may or may not need the gain
> workaround. If needed, it should be smaller than previous iOS 14 versions.
> - In iOS 15.4 beta, no workaround should be needed.

Hi youenn,

I tested the fix with iPhone xs Max, 15.4 beta, and found the following:

- with iOS 15.4 (19E5209h) everything works fine, no low audio issue present

and today I upgraded to the latest 15.4 beta:

- with iOS 15.4 (19E5225g) it works fine, until I turn off the microphone. While the microphone is enabled, the audio is at the correct volume level,  but the audio is low again when the mic is turned off.

Seems like the new beta added a similar issue what was present before. Can you check it please?

[Austin]

I have tested on a iPhone 7 Plus running 15.4 Beta (19E5241a) and the issue is still happening. 

Steps to reproduce:
1. Open 2 tabs in Safari and navigate to an application that uses WebRTC in both tabs.
2. Start and complete 1 call in first tab.
3. Switch to Tab 2 and repeat step 2. 
4. Repeat steps 2 & 3 at least 2-3 times to see issue occur.

It appears that after certain amount of back to back calls Safari starts routing the audio to the headpiece instead of the external speakers.

[Austin]

I have tested on a iPhone 7 Plus running 15.4 Beta (19E5241a) and the issue is still happening. 

Steps to reproduce:
1. Open 2 tabs in Safari and navigate to an application that uses WebRTC in both tabs.
2. Start and complete 1 call in first tab.
3. Switch to Tab 2 and repeat step 2. 
4. Repeat steps 2 & 3 at least 2-3 times to see issue occur.

It appears that after certain amount of back to back calls Safari starts routing the audio to the headpiece instead of the external speakers.

[Simon Fraser (smfr)]

(In reply to Austin from comment #121)
> I have tested on a iPhone 7 Plus running 15.4 Beta (19E5241a) and the issue
> is still happening. 
> 
> Steps to reproduce:
> 1. Open 2 tabs in Safari and navigate to an application that uses WebRTC in
> both tabs.
> 2. Start and complete 1 call in first tab.
> 3. Switch to Tab 2 and repeat step 2. 
> 4. Repeat steps 2 & 3 at least 2-3 times to see issue occur.
> 
> It appears that after certain amount of back to back calls Safari starts
> routing the audio to the headpiece instead of the external speakers.

This seems to be a routing issue, rather than a volume issue. I filed it as bug 237375.

[mh]

(In reply to youenn fablet from comment #116)
> Thanks for the testing, please ping me or file any bug you may encounter
> during that testing.
> 
> To summarise:
> - In iOS 15 and 15.1, web apps might need a workaround with a big volume gain
> - In iOS 15.2 and iOS 15.3, web apps may or may not need the gain
> workaround. If needed, it should be smaller than previous iOS 14 versions.
> - In iOS 15.4 beta, no workaround should be needed.

We added this workaround & it has been working until recently it was reported that the audio no longer plays when the browser or tab is backgrounded. It seems like this could be due to another webkit bug that is still present on 15.4 https://bugs.webkit.org/show_bug.cgi?id=231105 but I'm curious if anyone has encountered this issue & has a solution.

[youenn fablet]

> We added this workaround & it has been working until recently it was
> reported that the audio no longer plays when the browser or tab is
> backgrounded. It seems like this could be due to another webkit bug that is
> still present on 15.4 https://bugs.webkit.org/show_bug.cgi?id=231105 but I'm
> curious if anyone has encountered this issue & has a solution.

This is probably the right bug.
I wonder whether you can call audioContext.resume() once the page is backgrounded to restart the audio context.

[Lee]

I'm still seeing this issue on 15.4 (19E241) - Media is still imperceptibly quiet while a microphone stream is active.

[Matthew Windwer]

Created attachment 458458 [details]
feedback noises

[Matthew Windwer]

We identified a new issue that is causing echo and feedback noises during WebRTC calls on older iPad models as soon as they are updated to 15.4

We have identified (based on dozens of customer reports over the last few weeks as the iOS 15.4 update propagates) that this issue occurs when a participant in the group is on an iPad 6th generation, and have also gotten reports that the 10.5" iPad Pro causes this issue as well. We are not able to reproduce the issue on newer iPads.

We finally got our hands on an iPad 6th generation last night, updated it to 15.4.1, and were able to reproduce this issue on our own site as well as https://talky.io/.  I am not affiliated with Talky but they use WebRTC and the issue is reproducible there.

About 60+ seconds into the call (this varies), the other participants will start to hear feedback coming from the iPad 6th generation microphone.  As soon as the iPad 6 leaves the call, the feedback stops. Counterintuitively, the player on the iPad 6 doesn't hear the echo. A successful workaround that we have verified with many of our customers is to have the player on the offending device use a headset, such as AirPods.

Attached is an example of feedback noises reported by one of our customers.

I'm looking forward to hearing any responses from Apple and the WebRTC community about this new issue.

[Gavin Lefebvre]

Hi Matt- can confirm that iPad 7th Generation is impacted also. I have submitted FB9975516 via feedbackassistant.apple.com so Apple is aware. However, it might be worth creating a separate issue on bugzilla here?

[Matthew Windwer]

(In reply to Gavin Lefebvre from comment #128)
> Hi Matt- can confirm that iPad 7th Generation is impacted also. I have
> submitted FB9975516 via feedbackassistant.apple.com so Apple is aware.
> However, it might be worth creating a separate issue on bugzilla here?

We have also gotten some reports from iPad 7th generation. All 3 devices affected (iPad 6th generation, iPad 7th generation, and iPad Pro 10.5") have the A10 chip.

I will file a new bug if that is the best path forward. I haven't heard this issue acknowledged publicly (yet) so I wanted to announce here first to see what the best path forward is.

[Matthew Windwer]

(In reply to Gavin Lefebvre from comment #128)
> Hi Matt- can confirm that iPad 7th Generation is impacted also. I have
> submitted FB9975516 via feedbackassistant.apple.com so Apple is aware.
> However, it might be worth creating a separate issue on bugzilla here?

Hi Gavin,

I filed a new bug for the Echo/Feedback issue on iOS 15.4: https://bugs.webkit.org/show_bug.cgi?id=239860


Thanks for any additional information that you can provide.

[Shikher]

The issue is still there in 15.5

[HALA CHAT]

Hi everyone,

I am also seeing this issue with iOS15 <a href="https://hala.chat/en">Voice Chat With Random</a>