Dozens of people who bought the iPhones 8/8 Plus are reporting a sound problem with their new devices, which have a loud popping noise during voice calls – both in calls via the operator network and through FaceTime, which rules out possible carrier-related issues. The problem has been reported by users in all countries where the device has already been launched.
The noise is similar to static and occurs intermittently, only on the speaker – not being displayed if used with headphones or the iPhone speakerphone. The problem also does not occur in audio messages, either via iMessage, WhatsApp or Telegram, corroborating the possibility that it is a software problem and not a hardware problem. ??
According to the ManuCHfrom the forum MacRumors, the problem occurs with or without the “Wi-Fi Connections” feature, with VoLTE on or off, with noise cancellation enabled or not (feature available in the device’s accessibility area) and even with VoIP applications (such as Groundwire) with several operators.
Some users have forced a hard reset to see if the problem would be solved (some say yes, others don’t). The Apple support team advised some users to restore their phones and set up again via iCloud backup, again with very mixed results.
I bought an iPhone 8 Plus and my device had the problem; the good news is that I then went to an Apple Store, where everything was duly noted and the phone was changed. The bad news is that the replaced device has started to present the very same problem, again indicating that it may be a software problem.
Hopefully we don’t have a #crackgate or #estalogate, which would be a huge problem for Apple – the company is already on top of everything and is investigating what can be done.
Update, for Rafael Fischmann Sep 26, 2017 at 23:16
Good news. Apple has not only acknowledged this problem, but has promised to fix it through a software update that will be released “soon” – which is obviously not in iOS 11.0.1, available today.
According to her, the bug affects “a small number” of users.
via The Verge
Update II, by Eduardo Marques Oct 03, 2017 at 19:57
The problem was fixed in iOS 11.0.2 – more about the update in this article.