- Some iPhone 16E users experience Bluetooth -Bugs
- Audio can sometimes strain or cut out according to the reports
- It is unclear what exactly causing this problem Apple has not yet responded
Apple’s iPhone 16E is a complete renewal of iPhone SE that improves Apple’s budgetary kit in almost any way. But there is an area where the new device seems to fight for some, causing widespread complaints from users.
The problem seems to be centered on the iPhone 16E’s Bluetooth capacities. Specifically, many users have noticed that audio from the phone will occasionally set or cut out completely when 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 a number of people on Reddit, X and Apple’s official support forums. These complaints seem to go back for a few weeks, suggesting that they may have been present when the iPhone 16E was launched in mid -February. We have asked Apple for comment and will update this story if we hear back.
Similar problems do not appear to occur on other devices in the iPhone 16 series in any large number, suggesting that the problem could be limited to Apple’s latest phone.
Causing unknown
When Apple launched the iPhone 16E, it was the first iPhone to come with Apple’s C1 chip, a cellular modem that handles 5G connection. But if you are thinking that new chip may have something to do with the problem, it is probably wide of the brand.
This is because earlier rumors have claimed that Apple is working on its own internal Bluetooth chip, but that this is still not ready for production. This means that Bluetooth is still handled by other components, just as on other iPhones that are apparently not affected by this error.
This means that the cause is still something of a mystery. It is unclear whether the problem concerns iOS (and if so, how), though some users have claimed that update to the latest iOS 18.3.2 patch does not solve the problem.
Some users have contacted Apple’s support team, so hopefully the company is aware of and is working on a solution. With iOS 18.4 on the horizon we have got our fingers crossed this widely reported bug is quickly squeezed.
