Another iPhone issue has surfaced recently. Following reports of overheating and camera problems primarily affecting the iPhone 15, there is now a wave of social media posts from iPhone users, expressing their frustration about their iPhones suddenly shutting down. Notably, this issue is not confined to the latest model; it is causing shutdowns across all iPhone models
Several iPhone users have reported a mysterious shutdown issue affecting their devices. The issue causes iPhones to randomly shut down, even when they have sufficient battery life. In some cases, the phones will not turn back on for several hours.
A 9to5mac writer wrote that his iPhone suddenly shut down and the FaceID didn’t work without entering the pass code first due to restart. Upon checking the battery level data in the Settings app, he noticed that it showed phone showed his phone had shut down for hours. This happened on his iPhone 15 Pro Max running iOS 17.0.3.
Another iPhone user on Reddit also reported similar issue. The user wrote that his iPhone turned itself off for four hours. User had to feed in the SIM pin to disable the sleep focus in the phone.
“What it also did which I have never seen before: it only charged to 80% and then stopped for about two hours prior to switching itself off. I never observed this behavior on the 13 yet. Also, while it was off it apparently charged further until 100%” user reported.
“It happened to my iPad and iPhone X night before last, but not my new 15 Pro. It’s not new to iOS 17. I strongly suspect the devices are not shut down for hours, then magically rebooting. They shutdown and reboot immediately, but the OS can’t get the battery readings until you unlock the phone (and FileVault specifically) with your passcode. This is why you start getting battery readings only after unlocking the phone,” wrote another user in reply to the above Reddit post.
The issue seems to be affecting a wide range of iPhone models. It is not clear what is causing the issue, but it may be related to a software bug.
Apple has not yet commented on the issue, but it is likely that the company is aware of it and is working on a fix.
Follow FE Tech Bytes on Twitter, Instagram, LinkedIn, Facebook.
