Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Not sure if this is related, I drained my phone down to 2 percent yesterday before charging. Overnight it only charged to 79 percent (8h) which was odd but later after plugging it back in the phone will not charge. So it seemed to have stopped charging overnight.

I got it to start charging again after a reboot.

I’m using the official cable from Apple to charge.
 
We REALLY need Apple to address this. It’s bordering on ridiculous that they’ve been silent.

Some people need calls and texts immediately for work or emergencies. It makes me very anxious to know that our phones can go out of commission at any point in time, all at the same time. While they were down, would we have been able to call 911 if we woke up to a house fire? We don’t know.

We don’t know if we would have been able to start our phones up during the time they were mysteriously down. Before my father passed a year ago I needed the ability to receive calls 24/7. This is unreal.
 
My iPhone 13 on 17.0.3 just did this last night. And it has a SystemMemoryReset log for the time when it happened. So my guess is there's a memory leak (this has happened in previous iOS versions too) and overnight the phone decides it has had ENOUGH of the leak and it resets. Yeah, they need to friggin fix this.
 
  • Like
Reactions: Lizzard899
Can't say I've had this happen with my 15 Pro Max that I've had since launch day. Hopefully Apple fixes it (if it is indeed a software issue) with a patch for those that are affected. This has been happening since at least iOS 15 so I'm not holding my breath for them to fix it any time soon lol.
 
Yes. 15 Pro on 17.0.3. I’m not sure exactly what day, but this week at night. I woke up earlier and I saw this, so I was able to enter passcode before my alarm should ring. But it was only once.
 
Has anyone seen this happen, and how long the phone was actually off for? any on-screen messages? I haven’t experienced it (and haven’t been charging at night) but the thought of missing an alarm… alarms me.

Not, however, to the point of staying up all night watching my phone charge :)
 
15 Plus here, on 17.0.3. This phone also experienced the reboot during the early morning hours of October 10, with a long gap in activity depicted in the battery history graph. Last night, curiously, the phone charged for a short while after being plugged in, then stopped charging for the remainder of the night. Battery level when plugged in was around 50 percent; it charged for perhaps 30 minutes on an Apple 5W charger (the tiny cube), then the battery level dropped, steadily, from around 60 percent to 51 percent percent by 6:00 a.m. this morning. The phone is set to charge to 80%. Just mentioning as another instance of odd charging behavior overnight.
 
My 13 Pro did it on 17.0.2 on the 9th whilst on charge overnight on a flight, so it's definitely not something serverside as it was well away from any network ( and on airplane mode). I did look at the logs and there was no crash logs, but as mentioned some memoryReset logs at the right time so the memory leak theory in iOS 17 holds water for me
 
  • Like
Reactions: WarmWinterHat
Happened again last night to me, second day in a row and this has only happened for the past two days even though I’ve used iOS 17 on both my 13 Pro and now on my 15 Pro since I got it. As soon as I went to bed with the phone on the charger, it looks like it shut down but remained charged all night, only to wake up for my alarm.
 

Attachments

  • IMG_0460.jpeg
    IMG_0460.jpeg
    273.4 KB · Views: 71
I’ve been turning on airplane mode while I sleep.

Still no information of the cause yet?
 
it looks like it shut down but remained charged all night, only to wake up for my alarm.
If the alarm went off at the proper time, that suggests that the phone actually was on when the battery graph is blank. Someone above suggested that the phones might be restarting straight way, but no activity registers until the passcode is entered. That seems a reasonable hypothesis. I might try turning my phone off later and see what the battery graph shows if I don't log in right away.

If phones are restarting straight away, that is a much smaller and less mysterious problem than if they're shutting down and staying off for a number of hours.
 
If the alarm went off at the proper time, that suggests that the phone actually was on when the battery graph is blank. Someone above suggested that the phones might be restarting straight way, but no activity registers until the passcode is entered. That seems a reasonable hypothesis. I might try turning my phone off later and see what the battery graph shows if I don't log in right away.

If phones are restarting straight away, that is a much smaller and less mysterious problem than if they're shutting down and staying off for a number of hours.
Quite possible it wasn’t off but just rebooted at some point. After the alarm went off and silenced, I had to put in my passcode to get into the phone and it said I was required to input it after a reboot.
 
Quite possible it wasn’t off but just rebooted at some point.
Interesting. I'm experimenting with what happens to the battery graph with my phone restarted but not logged in (15 Pro on 17.0.3). I haven't experienced the spontaneous shutdown (yet...), and I figure a watched iPhone never mysteriously shuts down, so this is the best I can come up with...
 
it's not shutting down for hours. The gap in the battery graph is explainable because the graph doesn't get updated until the user enters their passcode after a reboot. The phone will reboot immediately, but the graph will have a gap because of this.
Did not know this. Thanks.
 
Repeated again for me last night. New iPhone 15 Plus, 17.0.3, cable-charging. Phone was running first thing in the morning but needed passcode.
 

Attachments

  • IMG_054540C64CD6-1.jpeg
    IMG_054540C64CD6-1.jpeg
    100.9 KB · Views: 68
Did not know this. Thanks.
I just did a little experiment to check. Indeed, after restarting, the green battery graph shows as blank until the passcode is entered. So, at least we only need to worry about restarts and not hours-long shutdowns as some people seemed to be reporting.
 
  • Like
Reactions: 2Xtreme21
it's not shutting down for hours. The gap in the battery graph is explainable because the graph doesn't get updated until the user enters their passcode after a reboot. The phone will reboot immediately, but the graph will have a gap because of this.

Both my wife's and my phones show gaps that ended in the middle of the night; mine was around 3 AM and my wife's around midnight. We both didn't enter the passcodes until the morning after, around 6 AM. So, if I understand your assertion, I believe it's incorrect.
 
  • Like
Reactions: LacrosseChic
Both my wife's and my phones show gaps that ended in the middle of the night; mine was around 3 AM and my wife's around midnight. We both didn't enter the passcodes until the morning after, around 6 AM. So, if I understand your assertion, I believe it's incorrect.
But did you look at the phone between 3am/midnight and 6am? The battery graph will be blank until you enter the passcode, even if the phone is on. I just tried it with mine to check (by turning the phone off and on again then not entering my passcode). Having said that, I didn’t receive any notifications etc. in that time, so I don’t know if that would have affected things.

Really we need a stake-out!
 
IMG_2800.png

The battery graph will be blank until you enter the passcode, even if the phone is on. I just tried it with mine to check (by turning the phone off and on again then not entering my passcode). Having said that, I didn’t receive any notifications etc. in that time, so I don’t know if that would have affected things.
P.S. here is the graph. I turned the phone off and on again within a minute, then didn’t enter the passcode for 90mins or so. The phone wasn’t charging at the time.
 
But did you look at the phone between 3am/midnight and 6am? The battery graph will be blank until you enter the passcode, even if the phone is on. I just tried it with mine to check (by turning the phone off and on again then not entering my passcode). Having said that, I didn’t receive any notifications etc. in that time, so I don’t know if that would have affected things.

Really we need a stake-out!

I'm kind of skeptical of myself :). I wish I could look back to the graph on that earlier day. I'm rather confident that neither my wife nor I unlocked our phones in the middle of the night. I can't rule out that we accidentally looked at our phones, but we wouldn't have made the effort to enter the passcodes. My passcode is a long one. I was definitely prompted in the morning to enter it.
 
Mine went off at 3:30am. Everyone’s phones are shutting down in the night while people are sleeping, in all time zones. Too much of a coincidence, it may seem conspiratorial but I think it’s a vulnerability exploit, Chinese or other hackers? Is it even possible?
 
Mine went off at 3:30am. Everyone’s phones are shutting down in the night while people are sleeping, in all time zones. Too much of a coincidence, it may seem conspiratorial but I think it’s a vulnerability exploit, Chinese or other hackers? Is it even possible?

Like the person above, mine rebooted while on a cross-country flight. Airplane mode was on and WiFi off.

13 pro, 17.0.3.
 
  • Like
Reactions: ChoiMinji
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.