Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Have you encountered this issue yet?

  • Yes

    Votes: 695 56.6%
  • No

    Votes: 533 43.4%

  • Total voters
    1,228
9.1 should fix this problem. Dont worry guys. Beta runs smooth snappy and no lag or feeeze

beta 3 certainly still had issue.. so I'm not holding it as fixed quite yet. since settings reset and beta 4 I've not had an issue in over a week.. but considering the nature of the issue at hand, that's hardly writ home free yet.
 
A few people reported the same issues with Beta 4 so Beta 4 did not resolve the issue.

Try Beta 5. Maybe this one will fix it.
 
Beta 4 was supposed to fix the issues according to engineers. It certainly improved the situation for 99% of people. Hopefully beta 5 and the subsequent public release will make this 100% fixed.
 
Beta 4 was supposed to fix the issues according to engineers. It certainly improved the situation for 99% of people. Hopefully beta 5 and the subsequent public release will make this 100% fixed.
Exactly. I didn't have one occurance on PB5 (what, 6 days?). There may be very strange combinations that cause this, because, if not, everyone would have it happening. And they don't.

Hope B5 picks up the final cases!

Please note what rev you are on when posting, it appears to be about the only factor that really matters.
 
I can't remember if I gave an update at the end of last week but I had it happen on Thursday or Friday and again this morning. Both times made me late to work. Luckily my boss doesn't give much of a crap, but still it's unprofessional and I don't like to be late. I had my wife as a backup this morning but she forgot to check on me, lol. Time to go buy an alarm clock I guess? Or I might just bring up my iPad. My watch isn't strong enough to wake me up. I'm on 9.0.2 like most. Talked to Apple today and they recommended a fresh restore so that's what I'm trying right now. I'm not very hopeful though as I did a fresh restore just in August so it's not like I'm carrying around a lot of baggage like some people. I also hate how long it takes to setup everything without a backup. Massive PITA!!
 
If beta 5 wont fix it for you seriosly i would return the phone. My phone is no problem at all after beta 4. Even beta 5 is smoother
 
Update #1: iOS 9.0.2 is released.
Update #2: Issue confirmed in isolated cases at Apple forums
Update #3: New survey questions (thanks notgreg)
Update #4: A possible fix has arrived.
Update #5: iOS Public Beta 4 is released.

View the latest data here.

Issue:
Many users have found out that their iPhone 6S's and other iOS devices not waking up, even when left unattended. Although it appears that the device turned off due to the screen not displaying, it may actually be frozen.

How do I fix it?
It is fixed by forcing a restart of holding the home and power button for 10 seconds.

Is this problem a priority bug fix for Apple?
I was told by an Apple rep that this error isn't well documented. Based on our survey, this is probably because it is not identifiable in diagnostics. But we still need to look at them, because they provide substantial info about the device.

How can I help?
1. Send diagnostics to Apple
On your iOS device, go to Settings > Privacy > Diagnostics & Usage, and select Automatically Send
2. Call Apple Care and let them check.
3. Take the survey below. Be specific and show us your diagnostics logs.

*if you are a Beta user, submit your bug through the app.


What causes it?
I've been told by Apple support that at least one of (many?) possible causes is likely corrupted iCloud backups. If you've restored your device from any previous backup through iCloud, and that backup is corrupted, it could result in this problem. There has been some acknowledgment that iCloud still has bugs.

How should I fix the problem completely?
First, make sure you are running the latest iOS 9 point release. If you run beta, those are inherently unstable so your results may vary.

Method 1: (for those who setup a device as new OR restored from backup)

Reset all your settings and test for a couple days for stability before attempting anything else. (Settings > General > Reset > Reset All Settings>

Method 2: (for those who restored from backup)
If #1 fails, make sure all your iCloud data is saved then setup as a new iPhone (here). You'll need to re-download all your apps manually so create a list first. Your iCloud data can be synced from your account, so that part is covered.

The key is to get a clean install and then create a backup from there. Then, create a backup on iTunes (not iCloud) and save that one. Test for a few days and if it's okay, you can create an iCloud backup again.

Please report your results after trying these. Especially if the problem is still not fixed.

Setting up your device as new means you are responsible for keeping your data. Please ask Apple support if you aren't comfortable.

-------

Survey:
The survey is still open but the spreadsheet is paused for now.

1. Model, OS, and actions before the problem occurred.
2. Was the device started as
new, or restored from a backup?
3. Was it
restored through iTunes or restored through iCloud?
4. Has the device displayed a heat warning prior to shutting down?
5. Please post any crash logs from your device. (Settings>Privacy>Diagnostics & Usage>Diagnostics & Usage Data.)



Sample Diagnostics:
1. iPhone 6S 64 GB Gold, iOS 9.01, idle state
2. Restored from backup
3. Restored through iCloud
4. None
5. See below:

Sample Kernel Panic Log:
(There is no need to scroll through the list, as the only important logs will be at the top and they will start with a long string of numbers. (example here) )

Incident Identifier: 2DF88CD6-7F78-43F3-B3D4-0BF9F3960DDA
CrashReporter Key: 768d5d741ff408154afa54e0f1a8629589420d74
Hardware Model: iPhone5,1
Date/Time: 2013-07-21 16:14:15.097 -0600
OS Version: iOS 6.1.4 (10B350)

panic(cpu 0 caller 0x81d3176b): "AppleUSBEHCI[0x83aa0000]::WaitForAsyncSchedule: USBCMD (0x00010351) and USBSTS (0x0000c000) did not synchronize"
Debugger message: panic
OS version: 10B350
Kernel version: Darwin Kernel Version 13.0.0: Wed Feb 13 21:40:10 PST 2013; root:xnu-2107.7.55.2.2~1/RELEASE_ARM_S5L8950X
iBoot version: iBoot-1537.9.55
secure boot?: YES
Paniclog version: 1
Kernel slide: 0x0000000001800000
Kernel text base: 0x81801000
Epoch Time: sec usec
Boot : 0x51e457b6 0x00000000
Sleep : 0x51e5b99b 0x0007aac7
Wake : 0x51e5b9aa 0x00000009
Calendar: 0x51e5c0d0 0x000e78f5

Sample Error Log (from echothree):
(
Titles vary a lot here)

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

Sample Reset Counter Log (from echothree):
(Title is something like ResetCounter-2015-10-02-3039393.ips)

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


Update #1: iOS 9.0.2 is released.
Update #2: Issue confirmed in isolated cases at Apple forums
Update #3: New survey questions (thanks notgreg)
Update #4: A possible fix has arrived.
Update #5: iOS Public Beta 4 is released.

View the latest data here.

Issue:
Many users have found out that their iPhone 6S's and other iOS devices not waking up, even when left unattended. Although it appears that the device turned off due to the screen not displaying, it may actually be frozen.

How do I fix it?
It is fixed by forcing a restart of holding the home and power button for 10 seconds.

Is this problem a priority bug fix for Apple?
I was told by an Apple rep that this error isn't well documented. Based on our survey, this is probably because it is not identifiable in diagnostics. But we still need to look at them, because they provide substantial info about the device.

How can I help?
1. Send diagnostics to Apple
On your iOS device, go to Settings > Privacy > Diagnostics & Usage, and select Automatically Send
2. Call Apple Care and let them check.
3. Take the survey below. Be specific and show us your diagnostics logs.

*if you are a Beta user, submit your bug through the app.


What causes it?
I've been told by Apple support that at least one of (many?) possible causes is likely corrupted iCloud backups. If you've restored your device from any previous backup through iCloud, and that backup is corrupted, it could result in this problem. There has been some acknowledgment that iCloud still has bugs.

How should I fix the problem completely?
First, make sure you are running the latest iOS 9 point release. If you run beta, those are inherently unstable so your results may vary.

Method 1: (for those who setup a device as new OR restored from backup)

Reset all your settings and test for a couple days for stability before attempting anything else. (Settings > General > Reset > Reset All Settings>

Method 2: (for those who restored from backup)
If #1 fails, make sure all your iCloud data is saved then setup as a new iPhone (here). You'll need to re-download all your apps manually so create a list first. Your iCloud data can be synced from your account, so that part is covered.

The key is to get a clean install and then create a backup from there. Then, create a backup on iTunes (not iCloud) and save that one. Test for a few days and if it's okay, you can create an iCloud backup again.

Please report your results after trying these. Especially if the problem is still not fixed.

Setting up your device as new means you are responsible for keeping your data. Please ask Apple support if you aren't comfortable.

-------

Survey:
The survey is still open but the spreadsheet is paused for now.

1. Model, OS, and actions before the problem occurred.
2. Was the device started as
new, or restored from a backup?
3. Was it
restored through iTunes or restored through iCloud?
4. Has the device displayed a heat warning prior to shutting down?
5. Please post any crash logs from your device. (Settings>Privacy>Diagnostics & Usage>Diagnostics & Usage Data.)



Sample Diagnostics:
1. iPhone 6S 64 GB Gold, iOS 9.01, idle state
2. Restored from backup
3. Restored through iCloud
4. None
5. See below:

Sample Kernel Panic Log:
(There is no need to scroll through the list, as the only important logs will be at the top and they will start with a long string of numbers. (example here) )

Incident Identifier: 2DF88CD6-7F78-43F3-B3D4-0BF9F3960DDA
CrashReporter Key: 768d5d741ff408154afa54e0f1a8629589420d74
Hardware Model: iPhone5,1
Date/Time: 2013-07-21 16:14:15.097 -0600
OS Version: iOS 6.1.4 (10B350)

panic(cpu 0 caller 0x81d3176b): "AppleUSBEHCI[0x83aa0000]::WaitForAsyncSchedule: USBCMD (0x00010351) and USBSTS (0x0000c000) did not synchronize"
Debugger message: panic
OS version: 10B350
Kernel version: Darwin Kernel Version 13.0.0: Wed Feb 13 21:40:10 PST 2013; root:xnu-2107.7.55.2.2~1/RELEASE_ARM_S5L8950X
iBoot version: iBoot-1537.9.55
secure boot?: YES
Paniclog version: 1
Kernel slide: 0x0000000001800000
Kernel text base: 0x81801000
Epoch Time: sec usec
Boot : 0x51e457b6 0x00000000
Sleep : 0x51e5b99b 0x0007aac7
Wake : 0x51e5b9aa 0x00000009
Calendar: 0x51e5c0d0 0x000e78f5

Sample Error Log (from echothree):
(
Titles vary a lot here)

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

Sample Reset Counter Log (from echothree):
(Title is something like ResetCounter-2015-10-02-3039393.ips)

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 am having this issue as well. iPhone 6S 128GB Space Grey. Running iOS 9.0.2 This has happened to my twice while the phone was idle and not charging. Called Apple, they deny even knowing the problem exists. Directed them to this thread, the thread on their own support site, and the CNET and ZDNet articles.

I am taking a 3 hour roundtrip journey to the nearest Genius Bar to allow them to "evaluate the device" next Saturday, but I'm not expecting much. Please let me know if I can offer any additional information that might help resolve this issue.
 
If beta 5 wont fix it for you seriosly i would return the phone. My phone is no problem at all after beta 4. Even beta 5 is smoother
Unique to both the Developer's B5 and PB5 is that there are two versions... (Using the PB format)... 13B5137 for everyone except 6s and 6s+ and unique to 6s and 6s+ owners version 13B139. I find that to be interesting...
 
Unique to both the Developer's B5 and PB5 is that there are two versions... (Using the PB format)... 13B5137 for everyone except 6s and 6s+ and unique to 6s and 6s+ owners version 13B139. I find that to be interesting...

I believe 9.0.2 has a different build for 6s and 6s plus
 
I really hope this issue is sorted soon as it's driving me mad! Will update to 9.0.2 tonight but from posts i've read it doesn't resolved it!
 
The data really lead to the conclusion that 9.1 beta fixes this at least as far as it can be fixed so far. :) I've not had an occurance since loading 9.1PB4 (on PB5 now) and had it five times in three days before that on 9.0.2. There are one or two reports of it on B4 but that's way down from non-beta and could be another issue, no way to know for sure.
 
I just started experiencing this problem, first happened yesterday, pulled my phone out of my pocket and I thought my battery was dead, phone wouldn't come on until I did a reboot. Fast forward to this morning and it made me late to work, woke up an grabbed my phone to check the time and nothing, tried holding down home + power and it wouldn't come on. Only when I tried it while plugged in would the phone reboot and turn back on.

I consider this a major issue, I pretty much ignore the chip, the occasional freezing and lag, but this is bad.

I've got a 64g AT&T space gray 6s+ on 9.02, restored from an iCloud backup.
 
Mine hasn't done it yet this week. I uninstalled most of my apps and unpaired my watch. Maybe the watch or an app was a contributing factor.
 
It happens to me since i've installed iOS9 in my non-s 6. It was very scary to me cause days prior the update my phone fell hard on the ground and I thank that the Fall was the reason of the problem :S. I've just installed Beta 5 i will check if it solves the problem.
 
I'm sad to say it does not. I woke up to my phone in this state this morning.

6S+ on 9.1b5 (13B139).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.