Sidebar Sidebar
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*

Have you encountered this issue yet?

  • Yes

    Votes: 695 56.6%

  • No

    Votes: 533 43.4%
  • Total voters
    1,228
My guess is that the way the fingerprint sensor is so damn fast is that it's active 100% of the time. So when you touch it and press it, it's already registering your fingerprint before the display even turns on.

Maybe some kind of bug is causing the fingerprint sensor to malfunction and temporarily make the phone unusable until a hard reboot.
 
Just for balance, I have a launch day 128Gb 6S which was restored from my iPhone 5's backup that day, I've noted from the Lirum app that it has the Samsung chip although I have no complaints re battery life, and it has been absolutely rock solid reliable since day one. I never turn it off, it just charges and backs up every night. I remember it being a little warm the first day or so as it restored etc, but the home button was never hot and I've not noticed it get at all warm since.
 
My 6s plus on 9.0.1 did it for the second time a few minutes ago. No heat issue and my battery still shows 100% even after unplugging the phone at 6:30 this morning.

None of the buttons on the phone nor the silent / screen lock switch worked aside from doing the reset combo.

I have an Apple Watch and did some tests on it while the phone was in its coma state. The watch was still connected to the phone and some watch apps that need data from the phone appeared to still work. I was able to pull weather, email, and view messages (these items may be cached on the watch though?). I tried to open the camera app on the watch and it look like it attempted to turn on the camera but it kept flipping between two different messages really quickly and then eventually gave up and told me to manually open the camera on the phone, which of course I couldn't do. I should have tried to use Siri from the watch or even 'hey Siri' on the phone but I didn't think to try that until just now.

Anyway I think my guess of it maybe being content blocking is not correct because it is still turned off. I've used lots of different apps and games and I've only seen this happen twice and both times my phone was not on charge and was just sitting on my desk in standby/sleep mode and wouldn't wake up when asked by the normal button presses.

Hopefully Apple has this figured out by now and we get it fixed before 9.1.0

I will be updating to 9.0.2 for now.
 
leesweet said:
It's definitely some weird case that causes it, since even this thread is running about 50/50 for who has been affected. But it's too many to be random hardware. And Apple has explicitly said they think it's fixed. For what that's worth. :)
Click to expand...
Curious as to where you saw that Apple has explicitly said they think it's fixed? I've only gotten a response from Apple via the PB4 feedback program as I reported the issue in an earlier PB release that they believe it has been fixed in PB4. They are awaiting feedback from testers to confirm. Day 2 on PB4 and the issue has not reared it's ugly head. I still want to give it more time though before I report back to Apple.
 
It happened to me the second time. I had my phone in my Kavaj Sleeve pouch and when I took the phone out the display was off and no response from pressing the home button. After pressing the home and power button the phone restarted and all is good again.

This is so annoying.
 
mikeyg54 said:
Curious as to where you saw that Apple has explicitly said they think it's fixed? I've only gotten a response from Apple via the PB4 feedback program as I reported the issue in an earlier PB release that they believe it has been fixed in PB4. They are awaiting feedback from testers to confirm. Day 2 on PB4 and the issue has not reared it's ugly head. I still want to give it more time though before I report back to Apple.
Click to expand...
Its early to know if PB4 has cured this issue but I can say in the mornings, as with previous releases, my display is still off while my alarm is sounding. The phone is not locked/crashed but the display is off. The phone will let me slide across the dark display to stop the alarm and does turn on with a touch of the home button. My iPad is dark too when I open the smart cover in the mornings. I touch the TouchID to unlock and still its dark. When you press the home button its unlocked and ready as if it has been showing something the whole time.

I know this is not the specific issue, which I have had twice as well, just saying that while the need to reboot may be fixed we/I still have an issue with the display not reacting the way it has in the past.
 
gsmornot said:
Its early to know if PB4 has cured this issue but I can say in the mornings, as with previous releases, my display is still off while my alarm is sounding. The phone is not locked/crashed but the display is off. The phone will let me slide across the dark display to stop the alarm and does turn on with a touch of the home button. My iPad is dark too when I open the smart cover in the mornings. I touch the TouchID to unlock and still its dark. When you press the home button its unlocked and ready as if it has been showing something the whole time.

I know this is not the specific issue, which I have had twice as well, just saying that while the need to reboot may be fixed we/I still have an issue with the display not reacting the way it has in the past.
Click to expand...
Sorry, I may have missed a post. Are you on PB4? Thanks.
 
Dented said:
Which should tell you what a relatively minor and uncommon issue this is.
Click to expand...
Millions of units are sold and probably not yet used because majority of people in Hong Kong have bought and resold their phones for a small profit.

It could also be the same case in many other parts of the world.
 
Last edited:
MCube74 said:
Millions of units are sold and probably not yet used because majority not people in Hong Kong have bought and resold their phones for a small profit.

It could also be the same case in many other parts of the world.
Click to expand...


No, it's not. There are millions of phones being used right now, and maybe a few hundred or thousand experiencing an issue like this, that's the reality. Sucks if it affects you, but probably within the normal failure rate.
 
Dented said:
No, it's not. There are millions of phones being used right now, and maybe a few hundred or thousand experiencing an issue like this, that's the reality. Sucks if it affects you, but probably within the normal failure rate.
Click to expand...
Are you saying that only the members of this forum are facing this problem?

How do you know that it is not happening also with people from overseas?

I am in Hong Kong and there are some people I know locally who have this problem.

I had this people once last week and it happened again today.

I do have Apple Care+ support with my phone but currently right now this problem is only taking away some of the excitement from the phone.
 
Just happened to me for the first time this morning. Used my phone. 5 minutes later I went to use it again and could not get it to wake up. Had to home/power force a reboot. 128GB iPhone 6S.

Hopefully Apple finds the issue and corrects it in an upcoming point release.
 
This just happened to me. I noticed that my YouTube app updated by itself even though I have auto updates turned off. Last night I deleted the app from my phone and then used iTunes to restore back the old version and all was fine. Took a screenshot of my battery usage because I was amazed at the good battery life. Charged it to 100%, closed all my running apps and went to sleep.

When I woke up this morning my phone wouldn't turn on. Did the power home combo and it came back on. I checked the YouTube app and it updated again by itself to the new version. My battery had gone down to 96% when I turned it back on. As I was using it, my battery percentage kept dropping before my eyes. Is now at 75%. No overheating. I am on 9.0.1 and have a 6S Plus 64gb bought on launch day. Week 38. Do you think YouTube updating itself had anything to do with this crash? Has YouTube updated by itself on your devices?
 

Attachments

  • IMG_2272.png
    IMG_2272.png
    269.2 KB · Views: 154
Last edited:
How can we approach Apple with this and get a sensible answer - there must be somebody on here? or how about we all return/exchange our devices, a few thousand would get somebody's attention :rolleyes:
 
markbrads said:
How can we approach Apple with this and get a sensible answer - there must be somebody on here? or how about we all return/exchange our devices, a few thousand would get somebody's attention :rolleyes:
Click to expand...

There's nothing that you can really do except provide as much information as possible to Apple. They need to reproduce this issue in-house so they can analyze the code in real-time. This is the only way it'll get fixed. They may add more debug code (diagnostic logging) so that this issue can be caught by phones in the wild -- but this is only if they know where to look.

This issue sounds quite bad but it's recoverable. At least your phone isn't bursting into flames!

I agree with another comment that Apple's QA unit has been lacking in recent years. The public betas really help but it's hard to convince people to switch to that version when there's the possibility of losing their data and/or something failing where they can't use their phone. Most of us rely on our phones too much to take that risk.

Apple could use a similar program to Microsoft's Insider program -- where users (that are willing to risk their data) could opt-in to test updates ahead of the "stable" builds. That could really help to catch some of these weird issues before they hit everyone.
 
MCube74 said:
Are you saying that only the members of this forum are facing this problem?

How do you know that it is not happening also with people from overseas?

I am in Hong Kong and there are some people I know locally who have this problem.

I had this people once last week and it happened again today.

I do have Apple Care+ support with my phone but currently right now this problem is only taking away some of the excitement from the phone.
Click to expand...
Sweet, I just left Hong Kong. I noticed this issue on a demo model. Employee said it keeps happening. Btw Its extremely hot in HK compared to Beijing huh?
 
MCube74 said:
Are you saying that only the members of this forum are facing this problem?

How do you know that it is not happening also with people from overseas?

I am in Hong Kong and there are some people I know locally who have this problem.

I had this people once last week and it happened again today.

I do have Apple Care+ support with my phone but currently right now this problem is only taking away some of the excitement from the phone.
Click to expand...
I'm saying that wherever you look, on this forum and elsewhere, the numbers of people reporting this are relatively low in comparison to the sheer numbers sold. This is very clearly not an endemic issue, it is also not restricted to the new phones you're talking about but other iOS 9 devices too, so it's a software bug affecting a minority that should absolutely be fixed, yes, but is not worth some kind of panic over.
 
I was just thinking about this issue as I was writing in another thread about how my 6s is essentially perfect, even with the Samsung chip. I've only had this happen that one day. Same with my wife's iPhone 5. Are many people still having trouble on 9.0.2? Pretty sure I'm fixed but there's not really any way to know.
 
I've had my phone for about 5 days, I set it up with an icloud backup from my old 5. This issue happened this morning. I use my phone as my daily alarm and it went off and I believe I hit snooze/ Alarm never went off again and about 30 minutes later when I woke up the phone was unresponsive.

This has been a reoccurring issue on new iPhone models for years. Eventually they get it sorted so not too concerned.


iPhone 6S, 128GB. Running 9.0.2
 
mikeyg54 said:
Curious as to where you saw that Apple has explicitly said they think it's fixed? I've only gotten a response from Apple via the PB4 feedback program as I reported the issue in an earlier PB release that they believe it has been fixed in PB4. They are awaiting feedback from testers to confirm. Day 2 on PB4 and the issue has not reared it's ugly head. I still want to give it more time though before I report back to Apple.
Click to expand...
I got the same response you got from Apple, where they stated in response to my bug report in the PB feedback app that changes were made in PB4 that could have an effect on this. The important part is that they explicitly addressed the issue. It may or may not be fixed.

All I *know*'is that it's been 48 hours and I've not had the problem recur. That's a good sign. It's not conclusive. That's the problem with this sort of issue, we can't 'reproduce' it since there are no steps I'm aware of. I wish we had them.

So, once again, has anyone on Beta 4 had the issue? I don't recall seeing a post, but I could have missed one.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back