Impending iOS update to help diagnose additional iPhone battery shutdowns
An imminent iOS update will help collect information about sudden iPhone shutdowns, specifically problems aren't limited to the iPhone 6s units Apple is currently offering battery replacements for, according to an updated support document posted on Tuesday.
On the webpage, at the moment only in Chinese, Apple explains that some phones "outside the affected batch" are suffering from shutdowns as well, and that it will "will add an additional diagnostic feature to the iOS software update that is [to be] released next week."
That tool will gather data that could contribute to algorithms for managing battery performance and shutdowns, Apple said, noting that if it can make improvements, they'll be delivered in subsequent software releases.
The iOS update coming next week is presumably iOS 10.2, which is already in its sixth beta and likely close to completion. Its main features will actually be a dedicated "TV" app and single sign-on support for TV providers.
Free battery swaps are only available to people with an iPhone 6s built between September and October 2015, and even then owners must check their serial number to see if they qualify. Apple didn't identify which iPhones outside that range might be having problems.
On the webpage, at the moment only in Chinese, Apple explains that some phones "outside the affected batch" are suffering from shutdowns as well, and that it will "will add an additional diagnostic feature to the iOS software update that is [to be] released next week."
That tool will gather data that could contribute to algorithms for managing battery performance and shutdowns, Apple said, noting that if it can make improvements, they'll be delivered in subsequent software releases.
The iOS update coming next week is presumably iOS 10.2, which is already in its sixth beta and likely close to completion. Its main features will actually be a dedicated "TV" app and single sign-on support for TV providers.
Free battery swaps are only available to people with an iPhone 6s built between September and October 2015, and even then owners must check their serial number to see if they qualify. Apple didn't identify which iPhones outside that range might be having problems.
Comments
Things seem to have changed in the past couple of years and it may be hard to pinpoint exactly why things appear to be going south. I'm not talking about a new revoltuoinalry device unleashed every two years but about inconsistent hardware, software bloat and Apple looking like the old guy in the room.
IOS in particular has gotten over cluttered and Apple's mantra of simplicity and minimalism has given way to a baroque overlay of options which I doubt most people ever use yet these "improvements" get touted as breakthrough and that they have had an army of people working on this feature just to ease your daily use of you iOS gadget. Take a look into the Settings of iOS 10, just the General section seems endless with options. If you need to select a seldom used option such as (turn off find my iPhone) you will find it eventually but it will be buried pretty deep somewhere in that mess.
Maybe I am spoiled by how well Apple's product have worked for me and having to replace a defective battery on my iPhone 6s recently was bound to happen when a company produces a billion of them per year but it may be the iOS that has me most concerned. I don't know if anyone else feel the way I do about this or if my love of things simple and intuitive make me more critical.
After that, reports emerged of iPhones in China having problems. The next time the "Hello" etc. screen happened, I checked Apple's website and found my iPhone's serial number was subject to the battery exchange program. So I took it to the Apple Store and the Genii told me again that it was probably the result of my corrupt data so even though my iPhone was subject to the battery exchange program, it probably wouldn't help. I went through various explanations trying to understand how corrupt personal data could not only shut down but also totally wipe a Unix device, but eventually agreed to accept this was possible and that it could be a corrupt data rather than a hardware issue, so I agreed with the Genius that I should wipe my phone to test it. After that, he consulted with his colleagues, scrolled frantically through his iPad, and suddenly suggested I should get an exchange iPhone.
I said I had already agreed that the problem was probably my corrupt data, so exchanging the phone would not help, but he insisted that exchanging the phone would address one of the three possible variables, the hardware issue, and besides, my phone was eligible whether it actually had problems or not. I pointed out that I had already been convinced that wiping the phone was likely to prove it was not a hardware issue, so there was no need for this, but he then became very insistent that I exchanged my phone. He assured me that the replacement was not subject to the battery exchange program.
Eventually I agreed and walked away with a replacement. Remember that this was not (directly) the battery performance and shutdown issue that has been reported. I formed the impression that the Genius had originally been operating under "deny any problems" mode, but during the course of my visit had received or read instructions saying "get hold of this device". Presumably so that Apple could test it.
"Outside the affected batch, a small number of customers reported an unexpected shutdown. Some of these shutdowns may be normal, because the iPhone will shut down to protect its electronic components. To gather more information, we will add an additional diagnostic feature to the iOS software update that is released next week. This feature collects a variety of information in the coming weeks that may help us improve algorithms for managing battery performance and shutdown operations. If such improvements can be achieved, we will deliver them through further software updates."
In any case, I had the phone checked in September and it checked out fine on their diagnostics. Yesterday they told me the sudden shut down was because the battery was
"marginal" (meaning it didn't register as needing replaced but it was close) and suggested I buy a new battery. When I asked why a new battery would fix the problem of the phone shutting down with 30% charge she told me that: "The % is not correct because the battery is weaker than a new one. The percent is closer to zero than what the phone displays".
Is she correct? I have no way of knowing. But, I have never seen this happen before on any other device.
But, I am glad to hear that Apple is at least looking into the problem. And it is a problem. If the phone says it has 30% charge, it should not be shutting down.
I wonder how many will take that route -- and flood the market with defective used IPhones?
The phone passes diagnostics (except there is an error trying to get the unexpected shutdown report): the battery has lot of cycles but the capacity is still around 90%. We tried a DFU/Firmware restore with no improvement. Apple has recommended some settings changes as a last resort. We're hoping it gets replaced by Applecare soon.
I wished the same, as it was 2nd trip to the apple store (a week before the 'recall' I was there, and they told me to reinstall iOS... because, "...you know, digitally signed binaries go bad sometimes" [no, I didn't know that, and it goes against all truths about Apple app/kernel security controls]. ), and it's a serious distance out of my way from work/home.
I agree with previous poster... I crave for iOS9 at this point no matter how cool iOS10 is.
Paid about $800 for my iPhone just over a year ago, why don't you buy me a new one?
As I mentioned in a previous post. On a trip to the Apple Store they told me the battery was almost into the replace zone and, because of that, the % charge it showed was not accurate. They recommended I replace the battery even though it is not in the replace category (yet).
Personally, I am not sure that I buy that story. But, I suspect a new battery might alleviate the problem only because the phone will keep a higher charge longer and be less likely to get down into the 20 - 30% range where it typically happens (especially when I start a video).
I plan to hold off because, all I have to do is stick it on the charger till it reboots and then I'm back to 20-30% charge and the phone works fine.
Funny how all these bugs Apple is experiencing in it's OS have materialised since Swift came on the scene... Many Apps are a Frankenstein of Swift & Objective C as Apple transition over, and frankly it's not too pretty.
Swift still isn't ready for prime time IMO, and bridging with Objective C classes is a messy revolting experience.
To be completely honest I'm not a big fan of Swift. There's a few features I like, but it forces you to write code in a way that fixes problems I never experienced in the first place. Rapid prototyping is not so rapid, everything takes 3 times longer to code.
Plus there's too many ways to skin a cat. It's a language the consensus of developers love, but consensuses almost always lack vision. A consensus in this instance is creating the swiss army knife of languages with a thousand ways to solve a problem when one would suffice.
Lets be honest, the main reason many (mostly non iOS) developers sing praise for Swift is that they simply couldn't get their brains round square brackets.
I know, it's got some good features, but just as many bad ones IMO.
I think there's just an issue with making batteries that thin, dendrites growing, causing temporary shorts, or something like that.
Still have an iPhone 4 that runs without a hitch, but the 6 series is much thinner, and all of mine have trouble.