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.
Some iPhone 6s Owners Seeing Their Phones Randomly Shut Off
- Thread starter MacRumors
- Start date
- Sort by reaction score
Glad we're not the only ones, I wrote about this issue a few days ago http://techaeris.com/2015/09/30/iphone-6s-plus-random-crashes-ios-9-0-1/
No! No! Please people, do not do this ^^^^. It's over once a warranty exchange takes place. It is best to return the phone and buy another one or return it and wait a few months for Apple to fix the problem. Tip! Never ever do a warranty exchange if it can be avoided (If the return option is available). Once the exchange takes place, it's over. The person doing the exchange will be limit and stuck in the manufacture's endless loop of exchanges, unless that person actually receives a good working phone / device...
Last edited:
This is a great point. I have noticed in the past that running games (which often use alot of memory tricks that can get messy outside of the game) occasionally resulted in unexpected behavior in iOS afterwards. I still run games, but clear them from memory after use and clear all apps from memory and then restart if anything unusual occurs.
It'll be interesting to see what the cause of this apparent display crashing in iOS 9.x is.
My iPhone 6S Silver 128G had a bad screen, horrible audio, touch response issues and it got pretty hot at times. It went right back. I was waiting for the 2G update...
I'm back using my iPhone 5 and really prefer the iPhone 5 size over the iPhone 6 size.
Here it is! Here it comes! Crappy-Phone-Gate
I'm back using my iPhone 5 and really prefer the iPhone 5 size over the iPhone 6 size.
Here it is! Here it comes! Crappy-Phone-Gate
I am not hostile, but I expect you will be disappointed by the massive influx of bugs you are about to encounter with little or no hope of ever getting them fixed. Even if you are motivated enough to get the latest version of the OS that could possibly run on your hardware, many 1.0 bugs still persist.
Grass is sometimes browner on the other side.
Ever tried an iPad 3 or iPhone 4s with iOS 8? Are you telling me it's a smooth experience ?
It's very true.
Fair enough, could be that than
Last edited by a moderator:
One interesting thing to note is that most iOS crashes (and most other modern operating systems) automatically reboot when they hit an unhanded exception or fatal error of some kind. When I've experienced this in previous iOS releases, the screen goes black, flashes white for a split second, then reboots.
According to most of the data collected so far, this crash requires user intervention to get the system back up.
Did the speaker cut out at the same time as the display?
According to most of the data collected so far, this crash requires user intervention to get the system back up.
Did the speaker cut out at the same time as the display?
The next time this happens to someone, can you try plugging it to a computer and seeing if it is seen by itunes? I think the phone is actually ON and running but not displaying the screen.
Or maybe try calling the phone, or texting it with another device.
Also, if people have the issue, can you post whether or not you put the phone FACE DOWN and if it happened after doing that.
My current theory is that something is going on with the FACE DOWN recognition feature and possibly the motion chip or touchid sensor.
Or maybe try calling the phone, or texting it with another device.
Also, if people have the issue, can you post whether or not you put the phone FACE DOWN and if it happened after doing that.
My current theory is that something is going on with the FACE DOWN recognition feature and possibly the motion chip or touchid sensor.
Exact same situation with an iPad 3 last night. Not the first time it's happened in the past couple of weeks, either. I'm running the iOS 9.1b on it and have been running public betas since they appeared. Methinks it's tied to iOS. Mehopes it's tied it iOS.
I had a similar thought. It would usually reboot on an error; making it seem like iOS isn't seeing the error and is still running normally.
I can confirm when it happened to me, I had been walking down the street holding the phone upright... The crash occurred after 5 minutes of the device being in this orientation so the proximity/gyro sensor doesn't seem like the culprit.
What seems odd though is that people who have iphone 6, the older one, are having the problem now that they use ios 9, so other than "everything" some ios 9 software to hardware thing seems to be causing this. maybe it's an option to move to powersave battery saving, maybe it's the implementations of the proximity sensors.
With the relative prevalence of the issue I think Apple would've caught battery issues affecting so many units during QC checks. Could be the power management subsystem in iOS, and given it's position in the kernel might explain why it circumvents the usual automatic reboot.
This is false, unless you are using the latest hardware...
Windows 8.1 and Windows 10 > OSX
Windows 8.1 and Windows 10 are so much better than OSX. Speed and hardware optimization. Both Windows versions have some nice features. Window 8.1 and 10 can both run smoothly on systems with as little as 2Gs Ram. OSX needs almost 8Gs Ram to run smoothly with applications running. Windows is now aware and can optimize its self to function better based on hardware and usage.
The only Apple device I like now, is the iPad. I think the iPad Pro is going to ruining the iPad line
If you're a developer, then you should not have a problem with Windows reliability.
Last edited:
My iPhone 4S is running perfectly with the update. SO maybe everyone should downgrade to a 4S and be happy!
to my theory, 4s doesn't have the motion sensor to take advantage of FACE DOWN not to light the screen. If the theory is somehow correct and related to motion sensor and some interpretation of sensor readings it wouldn't occur on an iphone prior to 5s
I understand that the FingerID sensor is new, and much faster. The over-heating Home Button makes me suspicious as to whether this button is experiencing an internal latch-up (ie. over-heating) and sucking the voltage down; thus causing the Low Voltage Interrupt to kick in (which protects NVRAM from getting corrupted). A hard reset is about the only way to recover.