- Some 16E iPhone users are experiencing Bluetooth errors
- Audio can sometimes stutter or cut, according to reports
- It is not clear what this problem is causing, Apple has not yet answered
Apple’s iPhone 16E is a complete renovation of the iPhone SE, which improves Apple’s budget telephone in almost every senses. But there is an area where the new device is apparently fighting for some, which causes generalized complaints from users.
The problem seems to be focused on the Bluetooth audio capabilities of the iPhone 16E. Specifically, many users have noticed that the audio of the phone will occasionally stutter or cut completely when they are connected to a Bluetooth speaker or headphones. According to some reports, the error appears when you connect the phone to multiple Bluetooth devices at the same time.
The problem has been documented by several people in the official support forums of Reddit, X and Apple. These complaints seem to return a few weeks, which suggests that they could have been present when the iPhone 16E was launched in mid -February. We have asked Apple comments and we will update this story if we receive news.
Similar problems do not seem to be occurring on other devices in the iPhone 16 range in any excellent issue, which suggests that the problem could be limited to Apple’s last phone.
Cause unknown
When Apple launched the 16E iPhone, it became the first iPhone to come with Apple’s C1 chip, a cellular modem that manages 5G connectivity. But if he is thinking that the new chip could have something to do with the problem, it is probably a brand.
This is because past rumors have affirmed that Apple is working on its own internal Bluetooth chip, but that this is not yet ready for production. That means that Bluetooth is still managed by other components, as in other iPhones that are apparently not affected by this error.
That means that the cause remains a kind of mystery. It is not clear if the problem is related to iOS (and if so, how), although some users have affirmed that the update of the last patch 18.3.2 does not solve the problem.
Some users have contacted Apple’s support team, so I hope the company is aware and works in a solution. With iOS 18.4 on the horizon, we have our crossed fingers, this widely informed error is quickly crushed.
