iPhone 13 has no phone noise canceling problem, Apple has no prospect of finding a solution – innovative Japanese version

The phone noise canceling feature available on iPhone 12 and earlier models (reducing ambient noise during calls) is not yet available on the iPhone 13 series, and users have been waiting for an Apple fix for months.

A few days ago, there was a post on the main Reddit bulletin board that “iPhone 13 does not have a ‘front microphone that can be used for noise canceling’.” The reason the poster believed was the lack of a ‘phone noise canceling’ toggle on the previous model in the ‘Accessibility’ → “Audio/Visual” to apply the setting.

It is true that the iPhone 13 lacks this feature, but that does not mean that it has fewer microphones than the iPhone 12 and earlier. Exactly other Reddit users pointed out that this wasn’t a hardware issue, while relaying the last discussion on the official Apple forums back in October. Through a series of exchanges, it appears that it has been confirmed that the “iPhone 13 series does not have a phone noise canceling switch” has been left unattended.

Also on the official forum above, another user wrote that Apple is aware of this issue.

It means, “iPhone 13 never had this option in iOS 15 due to a bug. I’m talking to Apple Support about this. This is a known issue and at the moment. There is no possibility of a solution. This error also causes echo symptoms that occur in CarPlay when talking between iPhone 13s.”

The post that started this was on Oct 29, about 2 months ago. iOS 15.2 was recently released, but this issue has not been resolved and it seems that it is still persisting in iOS 15.3 beta. US writer 9to5Mac released an image with the iPhone XS on the left and the iPhone 13 Pro on the right (title image), imagining that the latest iPhone models don’t have the features available in previous models three years ago.

Accessibility features make it easy for everyone to access information and services. It seems strange that Apple, focusing on this area, has not been able to solve the problem for a long time, but I would like to wait for future support.

Source: 9to5Mac