Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Sometimes I also have to enter my code in the morning. However, I think that in my case, it's not because of a reboot because of two reasons:

1. The message says something like "You have to enter your code to enable FaceID". When I reboot my phone manually, I get a message saying something like "Your code is required after a restart".
2. I have no gap in my battery graph.

The reason for number 1 is (I think) that I sometimes check the clock during the night when I wake up. So I tap the screen and lean over the phone (next to my bed). This probably leads to a few failed unlocks which in turn makes it necessary to enter the code to unlock it (that was also the mishap when the iPhone X with FaceID was introduced on stage all the way back then). My point is: Just because you have to enter your code, doesn't mean the phone rebooted, maybe there are other people as well who also just have to enter the code because of the same reason as me after some nights.
That's an interesting take. I will need to watch out for that and see whether that is the case as well.
 
  • Like
Reactions: chris4565
Interesting. I had a WatchOS 10 watch.

The day after the outage on my phone I noticed something strange. Mid morning I noticed my watch wasn't fully charged. That's never occurred before.
I think its the 80% limit option thats been enabled perhaps with WatchOS 10?

Same thing happened to me and i was confused as i knew i had left my Series 8 Watch on the charger for over 8 hours but in the morning when i put it on and then after a few hours i was already down to 65% when normally it would be 94% at that same amount of use time.

Do you have a Series 9 Watch or Series 8 or older?
If you have a Series 9 Watch you can individually turn off the 80% max limit charge but if you have a Series 8 or older you can only turn it off all together with battery optimization off.
 
IMG_5802.jpeg
Seeing this reboot issue while charging on iPhone 14 Pro Max running 17.1 beta 3
 
I think its the 80% limit option thats been enabled perhaps with WatchOS 10?

Same thing happened to me and i was confused as i knew i had left my Series 8 Watch on the charger for over 8 hours but in the morning when i put it on and then after a few hours i was already down to 65% when normally it would be 94% at that same amount of use time.

Do you have a Series 9 Watch or Series 8 or older?
If you have a Series 9 Watch you can individually turn off the 80% max limit charge but if you have a Series 8 or older you can only turn it off all together with battery optimization off.

I have a series 5. It only happened the day after the outage. I hadn't happened before and hasn't happened since.
 
I have a series 5. It only happened the day after the outage. I hadn't happened before and hasn't happened since.
Hmm ok then.
Yeah something for sure is a little off overall with these latest i/Watch OS updates thats for sure.
We might need to wait for some further patch releases to help iron out the bugs.
 
Same thing happened to me and i was confused as i knew i had left my Series 8 Watch on the charger for over 8 hours but in the morning when i put it on and then after a few hours i was already down to 65% when normally it would be 94% at that same amount of use time.
This is some new feature in watchOS 10 to extend battery lifetime. I saw a notification on my watch explaining this. IIRC, if you tap the charge ring, it will charge to 100%.
 
Let's try the following steps to see if we can eliminate this issue:

1. Reboot your phone once per week, maybe on a Saturday or Sunday morning.
2. Limit the USB-C initial charging rate on your charger to 27 watts or lower by using a lower-power USB-C charger.
3. Turn off the battery saving modes (e.g., limit the charging to 80%, and so on).
4. Use a quality charging cable from the likes of Anker or Apple's own charging cable.

My own iPhone 12 runs iOS 17.0.23, but charges overnight from a USB-A charger limited to 12 watts/2.4 amperes charging spec. I've never seen the sudden shutdown of phone even after overnight charging so far (knock on wood 🤞). Hopefully, the next beta drop of iOS 17.1 contains a fix for this unusual charging issue.
 
This is some new feature in watchOS 10 to extend battery lifetime. I saw a notification on my watch explaining this. IIRC, if you tap the charge ring, it will charge to 100%.
Yep indeed.
I however never received any notification on my Watch and also from my fault i never read the notes in the WatchOS 10 update either.
So when it first started to happen on mine i was totally confused lol.

Ive noticed mine is doing the limit charge ever 2nd day and im happy with that to be honest.
 
Had this happen for the first time last night. Woke up to “passcode is required when your phone restarts” and a big gap in my overnight charging. iPhone 14 Pro, iOS 17.1b3.

IMG_2944.jpeg
 
Last edited:
Well don’t know if it’s related but today my 15PM did it again, with a blank battery log, but this time with a kernel panic log :

(panic(cpu 2 caller 0xfffffff058712fb4): DCP PANIC - IOMFB: power on in incorrect vmaod state 0 -> 1\n - iomfb_ap_callee_1(22)\nIOMFB: power on in incorrect vmaod state 0 -> 1\n\nRTKit: RTKit-2413.2.1.release -)

I’m a bit worried, I reported it to Apple they ran a diagnostic but nothing. I have to keep them updated in case it would do it again
 
Last edited:
  • Like
Reactions: CodeRaven
I charge my phone on a Belkin "Boost" 3 in 1 charger. Since getting the 15 Pro Max - and upgrading to 17.0.3 - the phone has been making the "duh dunk" noise it makes when you put it on to a MagSafe device several times a night (at least once but often two or three times) - which is not great as it keeps waking me up.

Yesterday I changed the charging setting to "charge to 80%" - and last night it did NOT do it even once. I will try it again for another night - and then maybe switch it back to Optimised Charging - and see if it starts doing it again. I hope Apple sort this with 17.1 ??
 
Not me Mook.
I charge when I sleep. If Its "clean" so be it.
If it's not clean, I have a charges iPhone.
 
It really looks like that even though there is a gap, it did charge to 100%? and it looks like the pause started at 2230/2300?
Yeah I think as a few others have speculated it’s as if the phone is crashing and rebooting, but then continuing to charge and not registering it in the battery level graph until the phone is unlocked with the passcode.
 
  • Like
Reactions: chriswhv6
Yeah I think as a few others have speculated it’s as if the phone is crashing and rebooting, but then continuing to charge and not registering it in the battery level graph until the phone is unlocked with the passcode.
You know, I just noticed that it did this to my last night. Created a new Feedback FB13281011 on this issue.
 
No restart the last night iOS 17.1 RC. It was restarting two nights before the last one on 17.1 DB3 . Now I have a hope :)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.