Bug 239860

Summary: REGRESSION (iOS 15.4): Echo & Feedback from Microphone of devices with A10 Processor
Product: WebKit Reporter: Matthew Windwer <mattwindwer>
Component: WebRTCAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Major CC: alex.wayfer, chrisguttandin, teodor.atroshenko, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: Safari 15   
Hardware: iPhone / iPad   
OS: iOS 15   
Attachments:
Description Flags
feedback noise none

Description Matthew Windwer 2022-04-28 11:20:32 PDT 
Created attachment 458537 [details]
feedback noise

We identified a new issue that is causing echo and feedback noises during WebRTC calls from certain iPad models as soon as they are updated to iOS 15.4. Based on dozens of customer reports and our own testing, we have found that the following iPad models are affected, all with the A10 processor:

1. iPad 6th generation (2018)
2. iPad 7th generation (2019)
3. iPad Pro 10.5-inch (2017)

We are not able to reproduce the issue on newer iPads.

We tested on an iPad 6th generation that was updated to iOS 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 participant 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 participant 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.
Comment 1 Radar WebKit Bug Importer 2022-04-28 15:33:04 PDT 
<rdar://problem/92491455>
Comment 2 Sam Sneddon [:gsnedders] 2022-04-29 06:16:52 PDT 
Pretty sure this is just a duplicate of this?

*** This bug has been marked as a duplicate of bug 239285 ***