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
So just to throw a little twist.. .I have an iPhone 6s plus 128GB space grey.

- The lirium chip utility reports "n66map" which the discussion above indicates TSMC
- The jetsam logs indicate the kernel is n8000 which seems to indicate SAMSUNG

So not really any of the wiser....
 
planetf1 said:
So just to throw a little twist.. .I have an iPhone 6s plus 128GB space grey.

- The lirium chip utility reports "n66map" which the discussion above indicates TSMC
- The jetsam logs indicate the kernel is n8000 which seems to indicate SAMSUNG

So not really any of the wiser....
Click to expand...

Further to this, lirium states I have the TSMC nmap66a and jetsam logs say I have S8000.
 
john991 said:
Further to this, lirium states I have the TSMC nmap66a and jetsam logs say I have S8000.
Click to expand...

Yes please ignore the JetsamEvent log. It's just a naming convention for their kernel version which supports both CPUs. It has no bearing on the chip.

The Lirum app has been pulled from the app store so you'll have to use one of the two identifier programs.
 
Been running 9.0.2 on 128GB 6s Plus Rose Gold. Phone was shutting down 5-7 times per day. Closed all apps and ran only one app at a time for one day and no shutdowns.

Called Apple support and they said to bring it into the Genius Bar. Genius Bar looked at it today and started to do an iCloud backup. Luckily it shutdown in the middle of the backup. They immediately replaced the phone with a warranty phone. They also said that they think it's an iOS issue, but replaced the phone anyway.

I'll check the chipset and report back.
 
It's only ever happened to me once. The diagnostic data showed an issue with American Airlines and WatchKit. So I deleted the AA app and it hasn't happened since.

I don't think it's the AA app; I'm sure not everyone has it installed and I know not all of you have Apple Watches. I'm not sure what's causing it; I'm sure it's an iOS issue (perhaps how it interacts with some apps?)

I've also had a few random crashes. I had them on iOS 8.4.1 but they were resprings and not full restarts. These have been full crashes that require the re-entry of my passcode.
 
Running 9.1 beta4. Its been rock solid. 9.1 beta3 crashed twice the day and night before.

If you have a good phone dont exchange it. Its seems to be a os issue.
 
cnick6 said:
Yes please ignore the JetsamEvent log. It's just a naming convention for their kernel version which supports both CPUs. It has no bearing on the chip.

The Lirum app has been pulled from the app store so you'll have to use one of the two identifier programs.
Click to expand...

MCube74 said:
Why was the program pulled from the app store?
Click to expand...

Was pulled by the app dev so he can sell the $2.99 version. See the top charts for his app.
 
cnick6 said:
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.
Click to expand...

Ok, so and again this happened to me. Heres a log from the phone this morning, doesn't show much though :confused:

Incident Identifier: 6716825B-C860-4383-838A-F1D1C6F753A5
CrashReporter Key: dd87c624c5589e449e54afb4ee2084d9f26ab7bf
Date: 2015-10-09 06:29:39 +0100
Reset count: 0
Boot failure count: 1
Boot faults: btn_rst
Boot stage: 255
Boot app: 2681261667

I'm going to return it, I can't be bothered I'm too busy to fix Apple's problems - how about everybody else o_O
 
I was at the Apple Store today and they guys over there had no clue of the problem but their suggestions were similar to what I have read over at this forum. Surely they are aware of the problem and just being quiet about it.
 
markbrads said:
Ok, so and again this happened to me. Heres a log from the phone this morning, doesn't show much though :confused:

Incident Identifier: 6716825B-C860-4383-838A-F1D1C6F753A5
CrashReporter Key: dd87c624c5589e449e54afb4ee2084d9f26ab7bf
Date: 2015-10-09 06:29:39 +0100
Reset count: 0
Boot failure count: 1
Boot faults: btn_rst
Boot stage: 255
Boot app: 2681261667

I'm going to return it, I can't be bothered I'm too busy to fix Apple's problems - how about everybody else o_O
Click to expand...
What software (iOS) version? That seems to be the most important factor. Unless I'm mistaken, we've still not seen this on PB4.
 
I really want to know for sure if this is hardware or software. Don't care about the chip and the phone works flawlessly except this issue.

Apple have offered to replace but I really don't want a new phone with the same issue.

If it's software I will wait if its hardware I want to changed now! I have a developers account so I might install 9.1 B4 if we seem to think it's fixed but I'd rather not on my primary device.
 
MCube74 said:
I see. I downloaded the paid version and seems my iPhone 6s Plus is using the TMSC chip.
Click to expand...

You might not laugh yourself, but given what's happening elsewhere it would be absolutely hilarious if this turned out to be a problem with the TSMC chip..
 
I've updated to 9.0.2 and so far so good (prolly jinxed it, I know).

To the users thinking they need to replace their phone: don't. It's very likely a software issue, given that it is also affecting older iPhones and not just new 6s. Save yourself some time and energy and don't replace your phone over this bug.

To the users thinking this is a small problem because it isn't widely reported: remember it takes more effort to make a report about a problem than to just ignore it and stay silent. So we don't really know how many users have seen this. For example, I just made a forum account to try and help troubleshoot this problem. I would also say that since Apple Store display models are getting hit by this that Apple is surely aware of this issue and it should be a top priority to them regardless of how many or few users report on it.

The latest 9.1 public beta sounds promising but I really hope they would put this fix in 9.0.3 if they do have it fixed in the 9.1 PB. Unless of course 9.1 comes out in the next two weeks or so, prolly when the iPad pro drops. Even then, with users missing alarm clocks and just the scariness and bad experience of pressing the buttons that normally wake the phone up but suddenly don't... I would push the fix out asap.
 
Of course not everyone immediately joins a forum and makes these complaints if they're affected by an issue like this; but a proportion do and it's possible to draw comparisons between the reports of this and other known issues in the past, such as "antennagate" for example.

The fact is, the numbers reporting this are really very small, particularly when you factor in what was likely to be blockbuster sales. I'm not saying it's not an issue for some people and should be fixed, but the notion that this is a massive widespread issue is misplaced I think.
 
Dented said:
You might not laugh yourself, but given what's happening elsewhere it would be absolutely hilarious if this turned out to be a problem with the TSMC chip..
Click to expand...
That would be a disaster for Apple and for those who don't have Apple Care+.
 
nsxrox said:
Everyone is still covered under the 1 year warranty for this.
Click to expand...
Yes but Apple will not replace the phones just because of the chip set used. They will fix it somehow by software. Just like in the past.

It is sad that those iPhone with Samsung chipset are running hot and providing lower battery performance.

Like I said Apple should have used all Samsung chips for the regular 6s and TMSC for the plus model.
 
This happened last night when GF plugged 6s into power... blank screen, no response from any button, BUT the airplay (music on an Zeppelin Air) feature was still running. Had to hard reset to get the screen back up.
 
Not happened to me on my 64gb 6s running 9.0.2 with a Samsung chip. Must be one of the lucky ones.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Back
Top