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.
Resolved charging past 80% limit
- Thread starter 6787872
- Start date
- Sort by reaction score
He tries.
Oh, he tries.
Updates that got by him were because he had to have service on a device or something and they updated it.
Close! I only willingly updated one older iPad I no longer have. The update destroyed it, and I vowed never to update anything ever again. This happened in 2014.He tries.
Oh, he tries.
Updates that got by him were because he had to have service on a device or something and they updated it.
After that, only one iOS device has ever been updated: there is an iOS 9 activation bug for A9 devices, in which all A9 iPhones and iPads on iOS 9 are deactivated by Apple’s servers and forced to update (1st-gen iPad Pros, iPhone 6s and 6s Plus, 1st-gen SE).
My 9.7-inch iPad Pro was happily on iOS 9 from purchase in 2016 until September 2019, when this issue finally got to me and I was forced to update it if I wanted to use it. Just to be clear: I was reading a newspaper on Safari. The iPad randomly rebooted into the hello screen, and when I tried to go through the setup... something happened.
Here’s a screenshot of that moment:
I tried everything I could, to no avail. I tried to hack the iPad with software from the jailbreak community, I tried it all. I had to update, because nothing worked. The iPad was forced into iOS 12, and I’m still running that, of course.
Apart from this issue... everything else runs the original version. iPod Touch 5G on iOS 6, iPad Air 5 on iPadOS 15, iPhone Xʀ on iOS 12, etc. I will never update anything. The 9.7-inch iPad Pro would still be running iOS 9 if Apple hadn’t forced it out.
At one point I'd heard of some sort of issue with iOS 9, but I am not sure that the one I heard of is the same as what you encountered. At the time, I was using my 6s Plus on 9.0.1 because it was jailbroken.
The issue I heard of was that Apple was forcing upgrades because you'd restart and then be presented with the Hello screen and there was no way to get out of it without upgrading the phone.
The problem in that particular thing was that somehow the setup app was being triggered on reboot. It's actually an app and your iPhone remained jailbroken and in its normal state. But there was no way to kill the app and get back to the springboard. Thus, a forced update. The solution was to use iFile or some other file manager to locate the setup app and either rename it or delete it. iOS was hardcoded to look specifically for the filename of that app, so renaming it or deleting it caused the issue (bug?) to fail and you went on your normal, merry way. There was even a JB tweak developed to do this for you.
I'm just not sure if that had any relation to the issue you describe.
It’s that issue, but you don’t have to restart. Some people may have triggered the issue by rebooting, but some devices (like mine) would reboot by themselves. Funnily enough, there was an issue on iOS 9 in which A9 devices would respring by themselves. My iPad would occasionally respring, but it did that ever since I got it. This issue was fixed on iOS 10, so when it happened, I initially thought “this again? Alright”. I panicked when it booted into setup. I have an iPhone 6s on iOS 10.0 and it has never resprung like that. It was definitely fixed.
Yes, that is exactly the way to fix it: you have to be jailbroken before it triggers, and the solution is to rename “setup.app” to anything else, because iOS looks for the setup.app whose name is hardcoded, so if the app is renamed, the issue is never triggered. Of course, to rename the app to need to be jailbroken and you need to rename it before it triggers. Once it does, you’re doomed. I wasn’t jailbroken, so once it triggered, I had no options. I tried to forcibly exit the setup.app with a tool from the jailbreak community (I thought, worst case scenario, I break it and I have to DFU restore), but when the tool tried, the iPad would reboot a few times as if it were on a boot loop and then boot right into the hello screen again.
Realizing I had nothing else to try and this was my only iPad, I updated. This happened five days before the release of iPadOS 13, which I was (in hindsight, rightfully) scared of, as it was a large update. I thought “iPadOS 13 will destroy performance and battery life even more”, so I took the loss and updated to iOS 12 before iPadOS 13 was released.
1st-gen iPad Pro users reported iPadOS 13 was the beginning of the end in terms of both performance and battery life, with extensive slowdowns and keyboard lag and battery life irreversibly plummeting to a little over half the battery life I had on iOS 9. iOS 12 is much better than that, so glass half-full, I’m happy I did that.
I considered waiting until someone came up with a way to bypass it, but I thought: “I wait, nothing comes up, and I have to update to a worse version, and I’ll definitely regret that”.
If you asked me today, I would’ve updated it to iOS 10.3.3 when I had the chance and call it a day, but I don’t have a crystal ball. The iPad worked flawlessly for three years. I’d first read of the issue in early 2018. Why in the world did it take over a year and a half to trigger on my iPad? Who knows. Random luck. I thought I was safe when it’d been months since it showed up and I hadn’t been affected back then.
I saw a comment once on a thread like this, someone asked if doing x was bad for a battery, and someone said “being a battery is bad for the battery”
I keep my phone at around 100% all day. Only time it’s off a charger is evenings and weekends. My old Xs Max after 4.5 years was at 91% health. They last quite a while without getting too complicated about percentages.
I keep my phone at around 100% all day. Only time it’s off a charger is evenings and weekends. My old Xs Max after 4.5 years was at 91% health. They last quite a while without getting too complicated about percentages.
I have to charge my phone a few hours into my work day every day without fail, so why not keep it in the 40-80% range. i could get a full day if i charged to 100% and let it fall below 20%, but i always have my macbook to give the phone a quick top up. basically I do it because there's no negatives for me. i'm sure i'll trade in my phone next year and pay in full again so the battery health won't really matter..but what if i decide to keep it? lolol