“Cheap” wasn’t necessarily the keyword. The fact that they are third party is the important part.
So the fact that they're Apple Certified is meaningless?
The myth you’re talking about is that newer devices can overcharge. They can’t. But that’s not what I’m talking about.
That was
exactly what you were talking about. "... don’t ever leave it plugged in all night" was what you wrote.
... both heat and a high charging voltage (above 80%) will still cause lithium-ion batteries to age faster.
What does "high charging voltage (above 80%)" mean? 80% of what?
You
do understand that for a charger to "push" energy back into a battery, the charging voltage has to exceed the battery's voltage, right?
This is precisely why the Samsung Galaxy Note 7 batteries were exploding. People were leaving them plugged in all night, keeping the lithium-ion chemical components in a high-tension state for hours overnight.
Waitaminute. First you said you
weren't talking about the overcharge problem, now you're saying you
are talking about the overcharge problem. Which is it?
So just do the math: leaving your battery in it’s highest tension state all night every night is most likely why
What exactly is a battery's "highest tension state?" That is a term that, in decades of electronics and rechargeable battery usage, I've never encountered before. Can you point me to a definition for it?
—or at least a major part of why—your batteries aren’t holding up very well.
I don't think you're reading entirely what I'm writing. The Apple "Battery Health" of the batteries was unchanged, yet runtime suddenly became
drastically reduced after the upgrade to 11.4.
It’s best to keep it between 30% and 80%, ...
I think you're talking about charge level. (And I
believe that low end should be 40%, not 30%.)
You do realize, I hope, that "charge level" is as much an
estimation on the part of the mobile device as anything else, right? These batteries are so "flat" in their charge/discharge voltage levels that the device has to estimate what charge levels are based on "experience."
I've seen this effect with both Android and Apple devices. Suddenly the device run-time takes a nosedive. Sometimes dramatically (as just happened with ours), sometimes not so much. Run it through a "re-learn cycle": Let it run all the way to the bottom, where the battery runs down past the voltage "knee" in its discharge profile, and the device re-learns what capacity the battery
really has.
You can see it in action: Device drops uncommonly fast until it hits somewhere in the 6% range or lower, then hangs on there forever in a day.
Leaving your device plugged in all night is certainly not the reason why it’s battery is degrading faster than it should, or else all my iDevices wouldn’t last very long without charging.
Same here.
I do the same thing with my iThings I did with my Android things: Charge when it gets to about 70% or lower, no lower than 40%, if I can avoid it. Otherwise don't get all anxious about it.
Anyway...
My phone was fixed by a battery capacity re-learn cycle. My wife's
appeared to be, at first, then it went back to it's bad new old ways. Did a capacity re-learn cycle again and it was fixed again. We'll have to see if it sticks. If not: Despite the fact the battery health thing claims 97%, we may have to replace her battery sooner, rather than later.
In the meantime: I've updated to 11.4.1 and my runtime is still normal. This time I'm going to run that a couple weeks before subjecting my wife's phone to it.
Throwing them is never a good idea!
