I am leaning more toward the crash scenario vs the auto shutdown. It has been posted that some folks had to plug their phone into power to get them to come back on. That isn't just a shutdown, that's a crash.
No, it's not just a "crash". The system has a built-in shutdown to prevent damage when the CPU requires more voltage than the battery can provide.
A shutdown needs time as it waits for all the applications to close. A shutdown is when you power off your iPhone and you see the spinning wheel for a few seconds. That does not happen in the critical situation of a power failure. Of course, this can be easlity proven with logs.
A shutdown needs time as it waits for all the applications to close. A shutdown is when you power off your iPhone and you see the spinning wheel for a few seconds. That does not happen in the critical situation of a power failure. Of course, this can be easlity proven with logs.
You know how a CPU has a max temp, if that is reached, the system crahses .... there is no time for a system imitated shutdown , it has to be instant to save the CPU !! What the user sees is a system crash.
Ever seen a computer crash?
And .... still deflecting.... answer my question, did Apple introduce throttling ?
[doublepost=1514822355][/doublepost]
Spot on. It's just deflecting , and moving the topic away from the fact throttling has been added .
You are confusing a software controlled shutdown with a hardware shutdown. The power control circuits can immediately shut down the device by setting the voltage to the cpu to zero to prevent damage. They don’t wait for software to save things because the time that would take is an eternity when you are worried about damage caused by unreliable current supply.
[doublepost=1514822472][/doublepost]
Thermal shutdown isn’t a “crash.” But I don’t disagree with your sentiment.
A crash is a crash no matter what caused it. I am not into the details enough to sort out whether or not it was hardware or software in the long run.No. A crash is a software fault. This is a hardware fault. The fact that plugging in may be required to get them to power back on shows that it is not a crash. Instead, the power control hardware needs to be reset (by plugging in).
You are confusing a software controlled shutdown with a hardware shutdown. The power control circuits can immediately shut down the device by setting the voltage to the cpu to zero to prevent damage. They don’t wait for software to save things because the time that would take is an eternity when you are worried about damage caused by unreliable current supply.
You’re entitled to your opinion but not to your facts. A crash is a software fault. Not only is the CAUSE different than the shutdown, but the RESULT is different. A crash does not power off the device.A crash is a crash no matter what caused it. I am not into the details enough to sort out whether or not it was hardware or software in the long run.
I stand by my gut, it hasn't failed me yet.
And .... still deflecting.... answer my question, did Apple introduce throttling ?
Maybe but not necessarily. The OS could have been executing the correct instructions perfectly right up to the CPU clock tick where the power to the device is shut off. No engineer would say the OS crashed in that situation. It would be like saying you died of a heart attack when you were decapitated. It’s cute wordplay but it isn’t very helpful in describing what happened.I agree. But still behind the hardware shutdown due to power failure you have a crashed OS.
News break, Throttling is a new concept never before seen in other consumer devices. More at 11.
[doublepost=1514822726][/doublepost]Lets focus on the issues instead of semantics.
I agree. But still behind the hardware shutdown due to power failure you have a crashed OS.
It does in this case.A crash does not power off the device.
Incorrect. The OS doesn't crash. The system shuts down because the battery can't provide enough voltage to the CPU. If I hold the power button on my iMac while it's running normally, that doesn't crash the OS...it cuts the power.
It does in this case.
A crash is an unwanted or unexpected ceasing of the function of the equipment. You can define it and debate the semantics all you want. But to me, and probably many others, that is a crash.No it doesn’t, because it’s a hardware fault, not a crash.
What dirty move? Here's the chain of events...
iPhone 6S launches
Apple starts seeing a higher than normal amount of complaints about auto shutdowns
Apple determines that the majority of complaints are the result of defective batteries in a specific serial number range
Apple starts a free battery replacement program for those serial numbers
Apple also adds a software feature to iOS that helps to limit auto shutdowns
Seems like a fairly normal process for addressing customer complaints. Could you point out which part of that is "dirty"?
Zero shares in Apple (or any company for that matter). Not the investing sort.
Like it or not, it’s a package deal. You can’t have one without the other.
That to me is the Apple premium. You know how people like to say “why buy an iPhone when it’s twice the price of an android phone?” Well, I am essentially paying for Apple’s expertise in crafting a unique user experience in a way that that no one else can. That’s what justifies the Apple tax for me.
And that unique experience is derived from the integration of their hardware, software and services, including continued software updates which change the device based on what they believed is in the best interests of their users if need be.
Call it meddling if you will. But since I choose to embrace the Apple ecosystem, that means also trusting Apple to do the right thing for their users. Sometimes, they make the wrong call and screw things up, but I believe their hearts are in the right place and more often than not, they do by right and the end user is better off for it.
As I said earlier, it’s all one package deal.
If you don’t want software updates or want to be able to customise the device any way you wish, Android devices are that way. Though you will likely find that you are simply trading one set of issues for another.
A crash is an unwanted or unexpected ceasing of the function of the equipment. You can define it and debate the semantics all you want. But to me, and probably many others, that is a crash.
I NEVER claimed I was an expert. All this is purely personal experience. Save your time, you haven't convinced me yet and I don't expect you will be able to.The electrical and computer engineering profession disagrees with you, as your definition conflates two very different types of faults with two very different sets of causes and consequences, but I’ve learned on the internet that everyone is an expert, so have it your way.
Though I guess I should point out that your definition excludes most actual crashes - when I run software and it crashes, the equipment does not “cease to function.” Heck, the OS doesn’t even cease to function nowadays.A crash is an unwanted or unexpected ceasing of the function of the equipment. You can define it and debate the semantics all you want. But to me, and probably many others, that is a crash.
I NEVER claimed I was an expert. All this is purely personal experience. Save your time, you haven't convinced me yet and I don't expect you will be able to.
So is this still dependant on Apple's minimum level for battery replacements?
My iphone 6 had the battery cut off issue and when I went to get a replacement last summer at the Apple Store in Brent Cross the guy told me that it was just above the level to qualify for the battery replacement and instead I'd have to go for the full out of warranty replacement (which I didn't).
Does anybody know what the price will be in the UK?
Wrong again, it's the way I work based on experience and research.Though I guess I should point out that your definition excludes most actual crashes - when I run software and it crashes, the equipment does not “cease to function.” Heck, the OS doesn’t even cease to function nowadays.
But whatever.
[doublepost=1514824356][/doublepost]
That’s my point. I’m an expert. I pointed out that the definition used in the field. I pointed out that your definition does not even work for the most common situation that everyone agrees is a crash(when software exits prematurely and unexpectedly). But you’ll stick to your definition because that’s the way the internet works.