iPhone 6s Plus powers off when charging. Hard reset to turn on- keep getting message to sign into iTunes when I'm already signed in- when alarm goes off in the morning screen lights for a second then goes dark no way to swipe off. When switching from standard to zoomed screen it powers off. Only hard reset starts it!!! Apple Hope this helps
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPhone 6S (+other iOS devices) not waking up *confirmed*
- Thread starter wakinghour
- Start date
- Sort by reaction score
Happened to my 6s too now overnight. It seemed turned off before I went to sleep so I plugged it in to charge (the battery was low, which somehow seems to not hold that long considering I'm not using my phone at all since I bought it -- waiting to give away my old iPhone first -- 75h standby max, not the 10 days it says on Apple's spec page).
None of my other iOS9 devices are experiencing this.
None of my other iOS9 devices are experiencing this.
Honestly don't think so because there was anecdotal evidence that 2 display phones in an Apple Store were suffering from this.
OP thanks for changing the title however I still wouldn't word it as the devices are turning off, they just aren't waking up to button press or waking the screen and some services (such as alarms) are failing to trigger or can't trigger because of something else crashing. Either way I feel we are getting some good info for Apple and hopefully they are still following this thread.
More info from my case:
I found a com.apple.safariservices.contentblockerloaderin my diagnostics logs that showed a crash at 08:30 on 10/2/15
Identifier: com.apple.SafariServices.ContentBlockerLoader
Version: 1 (1.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2015-10-02 08:30:47.47 -0400
Launch Time: 2015-10-02 08:30:46.46 -0400
OS Version: iOS 9.0.1 (13A405)
Report Version: 105
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010
Triggered by Thread: 5
Then I found this resetcounter log which I'm guessing is when I discovered my phone was not waking up and I did the button reset/restart:
Date: 2015-10-02 10:11:54 -0400
Reset count: 0
Boot failure count: 1
Boot faults: btn_rst
Boot stage: 255
Boot app: 2681261667
I didn't find any springboard crashes but I also haven't mailed logs off the device to search for them. Idk if content blocking is part of this issue or not but I'll say again I never had the issue before I turned it on and I haven't had the issue after turning it back off.
I can't think of why it would cause some part of the os to crash though (could not be related at all), but I'm not an expert developer. Also since some people have reported this is also showing up on the display models in Apple stores, I doubt they would have content blocking turned on there....so idk :/
More info from my case:
I found a com.apple.safariservices.contentblockerloaderin my diagnostics logs that showed a crash at 08:30 on 10/2/15
Identifier: com.apple.SafariServices.ContentBlockerLoader
Version: 1 (1.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2015-10-02 08:30:47.47 -0400
Launch Time: 2015-10-02 08:30:46.46 -0400
OS Version: iOS 9.0.1 (13A405)
Report Version: 105
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010
Triggered by Thread: 5
Then I found this resetcounter log which I'm guessing is when I discovered my phone was not waking up and I did the button reset/restart:
Date: 2015-10-02 10:11:54 -0400
Reset count: 0
Boot failure count: 1
Boot faults: btn_rst
Boot stage: 255
Boot app: 2681261667
I didn't find any springboard crashes but I also haven't mailed logs off the device to search for them. Idk if content blocking is part of this issue or not but I'll say again I never had the issue before I turned it on and I haven't had the issue after turning it back off.
I can't think of why it would cause some part of the os to crash though (could not be related at all), but I'm not an expert developer. Also since some people have reported this is also showing up on the display models in Apple stores, I doubt they would have content blocking turned on there....so idk :/
Happened to me yesterday for the first time since getting my phone on launch day.
1. Model, OS, and actions before the problem occurred.
iPhone 6s Plus, 9.0.2, I was taking photos, stopped for a minute then went to take another and it wouldn't wake.
2. Was the device started as new, or restored from a backup?
Restored from iCloud Backup
3. Was it restored through iTunes or restored through iCloud?
iCloud
4. Has the device logged any kernel panics?
No
5. Has the device displayed a heat warning prior to shutting down?
No
1. Model, OS, and actions before the problem occurred.
iPhone 6s Plus, 9.0.2, I was taking photos, stopped for a minute then went to take another and it wouldn't wake.
2. Was the device started as new, or restored from a backup?
Restored from iCloud Backup
3. Was it restored through iTunes or restored through iCloud?
iCloud
4. Has the device logged any kernel panics?
No
5. Has the device displayed a heat warning prior to shutting down?
No
Last edited:
My occasions (5 so far) were about 50/50 charging and not, so, that's definitely not a primary cause.
I used Apple's cable, i.e. an older iPhone gen's lightning cable, and it happened. So not a 3rd party problem.
Thanks for the tip. I also changed the explanation of the issue to provide more clarity.
what?? what kind of phone have you? i have never had a phone that restarts itself or even needed to be restarted without installing some updates...
Unfortunately they are trained monkeys for that "oh, that is not normal. this is the first time...." call to that rep tomorrow and dont give your information, just ask about this issue. you will hear the same cool "never heard" - story. it is a part of the imago: deny and give a new device. unfortunately it has become a joke already...
Last edited:
Happening here too. Had it happen twice now since getting the phone on launch day. Once overnight and just a few minutes ago - both times whilst not using the phone. Of course thats not to say that apps weren't performing background refreshes.
1. iPhone 6S 64GB Space Grey, iOS 9.0.2
2. Device created from new. No restore.
3. N/A.
4. No heat warnings at all. Ever.
1. iPhone 6S 64GB Space Grey, iOS 9.0.2
2. Device created from new. No restore.
3. N/A.
4. No heat warnings at all. Ever.
Yeah man! This happened to me this morning on a 6s Plus! Had to hold the Power and Home Buttons for a long time before it loaded back up!
Well this has happened to me now four times in total
Black Screen, no response from power or home button. Home button warm/hot to touch. Plugging the phone into the mains has no effect. Holding home and power button to reset brings the device back to life. Spoke with apple support today regarding this including the sending of a short diagnostic report from the phone which they say shows nothing ..... Apple support suggested I perform a restore from iTunes and restore a backup. My concerns are that my return date for a full refund is 9th October, if its a hardware issue then I don't want to keep the phone, if it's software then I can survive providing we all get a fix. Surely we have a genius in the forum who can help with this so we can go to Apple and get some answers Well this has happened to me now four times in total
Well this has happened to me now four times in total
Here's some good news... Or, at least some news... Apple has acknowledge this issue as I reported the issue via the 9.1 Public Beta Feedback program. I received this reply today...
Hi Michael,
Can you reproduce this problem on Build 13B136? There are changes in this build that may have resolved this issue.
Hi Michael,
Can you reproduce this problem on Build 13B136? There are changes in this build that may have resolved this issue.