There seems to be a curious phenomenon that is causing some iPhone models temporarily restart at night, which can interrupt the alarms and other functionalities of the new iPhones. It is curious yes, but the affected users are more angry than surprised, since it is another failure, or error that adds to those that have already appeared in recent days since the iPhone 15 was released on the market.
Some people say that their iPhone restarts for no apparent reason during the night or even turned off at night without turning back on, a serious problem if you count on your device waking you up in the morning to go to work on time.
In a thread on Reddit, a user complains that two alarms on his iPhone, separated in time, never sounded. Several other users also chimed in with similar issues, and it turns out that some of the issues could be related to the iPhone turning off at night.
It is true that the phone continues to charge and after a few hours, the iPhone turns on by itself now function normally. You will be able to tell, because the next morning, you will have to unlock your iPhone with a passcode and not with facial recognition.
iPhones 15 turn off in the middle of the night
One user, h1roll3r says that:
“I was actually awake when I saw my iPhone turn on to 100% and then turn off. There have been a couple of cases where the phone would turn off and restart, but the screen would be completely black. The phone would still work but I couldn’t see anything on the screen. “I had to connect the phone to my computer to get the screen to turn on again.”
Another user, DoomSleighor says that:
“I checked and initially I had a gap in my battery history around the time mentioned. I went back a second time to check it again and the gap was gone, which makes me wonder if it’s just a simple graphics/rendering bug in the settings, and not some creepy mystery like everyone thinks it is.
If you want to know if it has happened to you too, simply check the battery configuration and see if there is a charging gap overnight. Many iPhones are turning off for a few hours at night. If you’re lucky, it hasn’t happened to your iPhone, and if it has, at least it turned on again before the alarm had to go off.
But as I said above, waking up to the passcode screen is the best indication that your iPhone has restarted while you were sleeping. The security policy of Apple requires entering passcode after restarting device before using Face ID or Touch ID again.
For security, turning an iPhone off and on again disables other features until the passcode is entered.
What to do if your iPhone restarts or shuts down during the night?
This problem is well documented in online forums such as Reddit, media such as 9to5Mac and MacRumors confirming that some of their own staff and readers of the aforementioned media are suffering from the same problem. But as expected, Apple has not yet issued a statement on the matter, at least as of this moment.
And this problem does not only affect the new iPhone 15, but it affects several iPhone models, including the iPhone 13, iPhone 14 lines. For some people, their device restarts if it is left plugged into a charger overnight . Others say it only happens sporadically, and not always at night.. And finally, some others say that their phone restarts if left on a MagSafe charger overnight, or even does so if it is not put on charge.
Although it is a bug that the guys from Cupertino will probably fix soon, it is true that it adds to the numerous list of bugs that have been appearing on the iPhone, especially on the iPhone 15 and those iPhones that have updated to the iOS 17 operating system. Yesterday without going any further, we talked about the screen problems suffered by some of the users of Apple’s new flagship, the iPhone 15 Pro Max.
Conclusion
And to make users who suffer from this type of annoying failure even a little more, it must be said that it is still not clear what is happening, and Apple has not commented anything about it.
It is unclear how widespread this problem is. It’s easy to attribute it to iOS 17but it seems that the problem came from before, because even in the aforementioned forums iPhone X users complain about suffering the same error, and there are some threads that go back several years that mention this same error.
