The iOS option to charge battery to "80% Limit" shouldn't just be for iPhone 15
keydiscussions.com
keydiscussions.com
Conversely, I also have an Android Galaxy S22+ for my personal phone. The "Battery Protect" feature limits charging to 85%. Life is easy with this device and it causes me a lot less anxiety.
Really now, why can't Apple enable this for older phones? I don't believe there's any good reason to force batteries to excessively damage themselves. I had a previous iPhone 13 mini I was less careful with on the over-charging front, and the battery performance was markedly worse. Hence the OCD. I acknowledge my neuroticism, but try to curb it within the realm of evidence.
What grinds my gears though is the AirPods. I have AirPods Pro that I want to last a long time, but out of the case the earbuds are always 'on' and drain battery relatively quickly (much faster than a phone left idle); put them in their case and they're almost always* charged to 100%. I want to be able to leave them out, off, and disconnected. I almost never need 100% battery in my day-to-day use and there's no replacing the batteries in them once they're worn out.
An 80% max charge limit would be great.
*They do offer 80% overnight charge protection, but that's irrelevant as I don't keep them plugged in overnight
Ask me how I know *cries softly*.
Are you saying Apple doesn’t re-seal it properly?
Why?
My last phone spent like 8-10 hours a day on and off a wireless charger and had 88% battery health when I sold it over two years after I bought it
It's something that should be automated. And even then, I'm not sure I would use it, I usually need 100% of my battery to go through the day.
I really do not understand how that’s worth “a lot of manual toil”
You shouldn't worry too much about going below 40%. Regularly draining it to zero might shorten battery life, but going down to 10-20% won't.
> " I don't believe there's any good reason to force batteries to excessively damage themselves."
From Apple's perspective there is. Selling replacement batteries is very profitable.
Lithium batteries are happiest around 40% state of charge. The closer you can keep them to that magic number the longer they’ll last. But leave them fully charged, or even worse, fully dead and that’s the quickest way to kill them with “normal” use.
https://play.google.com/store/apps/details?id=com.digibites....
That’s not how the Optimized Battery feature works, according to the help text displayed right next to the feature in the Battery Health settings.
I question the whole premise of this article.
Author here, I think my Optimized Charging description is a fine description of how it works in practice. To borrow from another publication: "Optimized battery charging is a feature on iOS 13 or newer that limits overnight charging to protect your phone's battery in the long term." [0] With it, iOS learns your habits and will try to keep your phone charged under 80% until soon before it thinks you will take the phone off the charger, when it tops it off to 100%. "The algorithm aims to ensure that your iPhone is still fully charged when unplugged." [1] I have also used the feature personally since it came out, and this is how it works. What do you take issue with specifically?
[0] - https://www.pocket-lint.com/what-is-optimised-battery-chargi... [1] - https://support.apple.com/en-us/HT210512
What? You got tripped up on my wording, sorry. But the article's premise is valid, and it's not cool that the top comment on this submission for its first three hours on HN has totally lacked curiosity and come to a sensationalist conclusion. Do you have any actual problems with the article? Could you list them? (You responded to others but not my previous comment)
The claim from the article is that a fixed 'charge to 80% feature' is "likely possible on earlier models". I asked Apple to comment and am curious what they say. We do have evidence for the article's claim: iPhones dating back to at least the iPhone 8 support a feature that limits charging to 80% for multiple hours per day already. It just only occurs during hours Apple chooses via its learning algorithm. I never claim that the hardware is/is-not different; you simply have to look at what is already supported to understand what the devices are capable of.
Please say what the difference is, then?
So, again, what is the difference from what you quoted? Is it the implication that it might work at other times of day when the phone is "normally idle"? I don't even know if that implication is true or not, since it depends on exactly how the phone calculates your schedule. But if that's your complaint, it seems pretty small to me, not enough to throw the rest of the article into question.
Is there something else I'm missing?
I don't see the conflict.
Optimized charging is based on learning and thus unpredictable and hard to influence. It only works if you have rigid habits.
Like, if I say my car only starts when it has gas, I'm not promising it always starts as long as it has gas.
It's far from a comprehensive list of things that break the feature, but it gets the point across that the existing feature does a fraction of the job at best.
If your argument is that it "works" all the time even when it's not affecting charging, therefore the article is wrong, you are splitting hairs in the worst possible way. And if you're not arguing the article is wrong you might need to reread the comment thread.
Technology should be as transparent as possible in my opinion and not bring us back to thinking about said technology, just what we can do with it.
It's tiresome enough to worry about having a charged phone, i couldnt bring myself to look at battery percentage or even phone charger options just because i am calculating how long will my phone last in the long run.
Worn out batteries don't just have limited capacity, they charge slower and create more heat while charging due to internal resistance. I'd much rather charge to 80% for my typical day, but have the option to 100% charge on those rare occasions when I know I might need it (long day travelling, etc).
Personally, I have a Shortcut to put my phone into "low power mode" once it hits 90% (why not?).
Maybe a Shortcut could do the same and turn off power once it hits 80% on your overnight charging dock and then use a small amount of power while the screen is off.
Isn't low power mode for when your phone has very little battery left? I don't understand why one would put a phone in low power mode when it's charging and hits 90%.
Personally, my 15 pro can do >72 hours on a single charge WITHOUT doing stuff like this, even starting at 80% (note: mostly standby, no always on display, with ~3h screen on time total). The 80% limit is definitely something I'll be using virtually all the time.
For me, I find the performance/lost functionality fine: https://support.apple.com/en-ca/HT205234
Replacing an iPhone battery at an Apple Store costs about 1/3 the price of the phone by the time you need it replaced, so ideally one would want the battery to last as long as the lifetime of the phone. One way to delay liion battery ageing is to shallow charge.
Case in point I’ve a 6 year old dell laptop that is set to shallow charge to 75% in BIOS and the battery still holds 3 hours of charge (from 75% to forced standby)to this day. Most laptop battery stop holding a charge 2 to 3 years in.
Counterpoint. I have a lenovo thinkpad t480s that I bought second hand and is now 4+ years old. The battery lasts at least 6 hours. I haven't discharged it fully in a while to be more precise. Ubu 22.04 running in power save mode as selected from the default gnome menu.
Dell? Yeah, terrible company making terrible laptops for sure. Used to think differently before owning one.
An iPhone battery replacement is $49-99 at an Apple Store.
> about 1/3 the price of the phone by the time you need it replaced
So that sounds plausible if iPhones can be purchased for $150-300 at the age you'd replace the battery. (Though that does strike me as a little low, still? Depending on how long the battery lasts...)
Personally i hate the optimized battery charging ios does. It’s awful. I’d rather being able to keep my phone plugged in basically 24/7 and always have it ready to go, but not have to worry about expediting its death.
I've been using it successfully for around a year. It works pretty well sans a couple quirks due to hardware limitations e.g. if you plug in with the screen closed (sleep mode) it will charge fully to 100%.
For my main computer (M1 Macbook Pro) that spends roughly 80% of the time on its charger, I have it set to 65% which gives me plenty of margin at home, plus it allows you to top-up to 100% on the pro version with one click.
For my 2015 Macbook Pro with heavily degraded battery that spends 100% of the time on its charger and on, I set it to 50% to (hopefully) lengthen the life of the battery before it swells since removing the battery safely is a bit sketchy on even that era of Macbook.
1. OS’s battery driver does the charging. This is possible when the computer is on and the driver has control. 2. Firmware driven charging. Typically used in sleep mode 3. Analog Trickle charge - no intelligence, no code is executing. Charge slowly from a dead battery so as to not damage any components.
#1 is the only case where an app. Can control any aspect of charging.
I eventually tried this instead (for Intel Macs) :
https://github.com/DevNulPavel/osx_battery_charge_limit
I use it to keep my battery level indicator pegged at 70%. Often doesn't persist after a system update, but it's just a quick terminal command to reapply the setting.
I use my Macbook in clamshell mode, and I use sleep mode when I'm not using it - receiving power from a Thunderbolt dock. It's handy to pick up exactly where I left off on resume. Plus, I use two LG screens where one of the two doesn't switch on after a cold boot, and it's annoying to unplug and replug to activate it. Sleep mode gets around that.
It’s an M1 Pro MacBook that I’ve had since launch.
I keep it at ~80% limit normally with occasional charges to 100% for long trips, etc. I do spend a lot of time on battery though so it's charging and draining a lot, but rarely goes above 80% charge.
Thanks for posting your results, I'm curious just how much the charge limit helps battery longevity.
Basically, I find individual stories vary, but statistics may show overall trends
It’ll regen charge up to “really” 100%, but that would require something like a 5,000-10,000 ft continuous elevation drop, where you just ride the regeneration brake the whole way down.
Nissan took a different approach. The batteries on the old Leafs died really prematurely because they didn’t have decent battery management.
They fixed it on later models.
Anyway, this stuff is mostly a solved problem these days. It would be nice if device manufacturers were compelled to provide an 8 year, 80% capacity parts and labor warranty on all non-replaceable batteries (like the car manufacturers do in the US).
Like GoPro can only auto clear a video from your sd card that has been uploaded on the newest model. There is no way that is limited to those devices. But, it probably isn't profitable to even crack open the code for the older models so they don't even consider it. It makes it worse because I'm even paying a subscription for storage.
You still need the actual acc app: https://github.com/VR-25/acc/
Honestly, I’d suggest trying to use your phone less. A new 15 pro has a pretty ridiculous screen on time even at just 80%.
so i'd like to know more about the science behind this. how much does the battery life actually improve by doing this. is the trade off worth the inconvenience of a shorter runtime before i need to recharge?
And if you do ever need all 100%, just turn off the limit the day before.
For me it's a no-brainer: 85% on my current (brand-new) Android phone lasts around 50-55 hours.
The cutoff points are going to be picked to balance lifespan and capacity.
The Android API allows you do get the voltage and current of the battery (with negative current for discharging and positive for charging), so there are apps out there that tell you the real state of the battery when it's in that range. The phones will tell the user fully charged before it's actually completely charged, but it's not much. It's mainly so if you leave it plugged in, it can cycle a bit up and down while still displaying 100% instead of continually trickle-charging.
My guess is tablets would be similar, but I've never had one.
Those are not pleasant facts that users need always be made aware of. 98% understood by BMS rounded up to 100%, actual 12% displayed as 1%, etc., should be tolerated.
But... this happens at the bottom end too, your battery already still has some charge left at 0%, the BMS protects it from being fully discharged. I'm just wishing there was a bit more so I don't have to make decisions about wearing out the battery faster.
Then I could enable OVERCHARGE and get 120% charge for travelling or when I know it's going to be a long day, at the cost of battery life.
I already expect my phone to die fast when it gets under 5%.
https://batteryuniversity.com/article/bu-808-how-to-prolong-...
You would then consume almost 2x of those cycles just recharging to make up for the lost capacity.
Capacity or longevity?
- Below 10%, battery is charged in pre-charge mode through a 10-foot pole.
- Above 10%, battery is charged in constant current mode, as in:
`charger.current_max(battery.CAPACITY * battery.CHARGE_C_RATE)`
`charger.voltage(battery.voltage + 0.0001)`
- Above 80%, battery is charged in constant voltage mode, as in:
`charger.current_max(battery.TERMINATION_CURRENT)`
`charger.voltage(battery.VOLTAGE_MAX)`
- `charger.charge_complete` shall return `True` if `battery.voltage == battery.VOLTAGE_MAX and charger.current == battery.TERMINATION_CURRENT`.
- * `battery.CHARGE_C_RATE` is generally set within 0.2 to 4; 1.0 matches mAh rating of the battery, a mostly-safe default. 0.2 is 5 hours to full charge, and 4 is "fast charge to 80% in 15 minutes".
- * all above is usually implemented in charge controller chip firmware, often in actual ROM; the bare minimum often done in real products is to hardwire indicate `charger.current_max` to the chip in circuits. That suffices unless intricate charging really is one of your differentiation.
- * `battery.state_of_charge` is more or less `find_acidity_or_pH(battery.voltage, battery.formulae)`, by the way. Capacity-Voltage curve is titration chart turned sideways.
It is often vaguely told that this constant voltage variable current mode used in 80 - 100% range is harmful to batteries, so not doing it should improve longevity. As to why then implement CV modes at all, and why not offer an option to easily disable it, I don't know. Everyone does it this way. I wish I knew if altering `battery.VOLTAGE_MAX` would work or if `charger.allow_cv_charging` can be set to `False`, but those are often hardcoded `4.2` and `True` in ROM.In Li-ion however, I think it's something like, max voltage ramp is limited even within current limit, then afterwards current is limited even below cutoff voltage, or whatever to similar effects. It's definitely more complicated than just constant max voltage fed through a 330R.
Although my laptop does get a lot more use.
i tend to buy cheaper older models of phones though, that may not have the strongest battery to begin with.
The only time I get close to running out of battery is when I'm watching YouTube videos on a long bus/train/plane ride.
I try to take it off around 80% so I was interested in this feature and confused when the update didn't include it. I don't like that it's in my "pros" column for upgrading when it could be available to everyone, would rather not reward them for that.
- Charge cycles (including partial cycles, e.g. 100% -> 50% is half a charge cycle)
- Depth of discharge (deeper discharge cycles are worse)
- Extended periods in hot conditions (over 40 degrees Celsius)
- Extended periods of being held at 100% state of charge
In essence, your charging behavior dings the first two items: higher number of charge cycles, and deep discharge cycles. If your goal was battery longevity, keeping the phone plugged in as much of the time as possible would be the best strategy. Bonus points if your phone supports a "stop at 80%" mode, but still the winner even without this feature.
https://www.bonnenbatteries.com/lithium-battery-low-temperat...
Li-ion chemistries that are tolerant of charging at low temperatures are a subject of active research.
Charging faster is something that can be variable between chemistries, but typically batteries are fine with charging quite quickly in the first 80% regardless, and can be made to tolerate fast charging (though usually you sacrifice a little bit of lifespan or total capacity to increase that tolerance)
As the battery life degrades over time, it will try to keep the same useful range, and shrink those boundaries until you are using the full battery life each charge.
Perhaps this works less will for phones, but I'm not so sure. Personally I never have issues with battery on new phones. It's only as the battery life shrinks that you really need the full range.
By default have it stop charging at the recommended 100%, but let the user decide if they need that to go beyond that and are willing to damage their battery health to do so.
Most users don't know enough about battery chemistry.
WAY too many people don't even understand how USB charging work, their brains are still stuck in the barrel jack charging ages where the charger pushed power and the device just took it (or blew up).
If Huawei had a "limit charge" feature in this device, it would probably have avoided all that hassle!
Create an automation when the battery hits 80%, switch off the smart plug.
Of course unlike Nestle and Coca Cola, Apple is too hip to be known for its environmental impact…
I also set a geofence around the cell dead spot at my house to enable airplane mode.
The latter spams notifications due to an (anti-stalking?) “feature” of shortcuts that doesn’t let you disable geofence notifications.
That bug can then be fixed by exploiting another bug by enabling screen time, the creating a custom app shortcut that produces a notification. Run the custom app a bunch and screen time will decide it is spam, and force-enable the “disable notifications” toggle for the shortcuts app. (Apparently this doesn’t work on some of the newer/higher end iPhones. My guess is they copy pasted the policy logic for each model, and forgot to backport a bugfix).
The above greatly increased battery life and did so transparently.
Now, all I need to do is buy a smart plug and have it toggle the power on a low-speed charger when the iPhone battery is above 80% or below 60%.
After that, I’ll do the same for my watch and iPad.
Couldn’t be simpler.
/s
How?
Looking at my battery history, the automated version has my phone sit at 80% all night, and leaves it at 100% for only a couple hours in the morning. I suspect this will be a fairly negligible impact on battery longevity for me, and most users, without the severe inconvenience of a 20% reduction in battery life.
It would be nice to know how the longevity math works out.
This is one of my pet peeves - obvious and easy to implement features that are just not there. I literally only switched to iPhones because the blindingly obvious Emergency Bypass feature [1] wasn't available on Android.
Phones already perk up when connected to a power source. Why not display an optional dialog with a choice of either the desired max battery level and/or some user-friendly modes like "battery health" vs "battery charge"?! Easy to implement, zero downsides, massive upsides, nobody's doing it.
[1]: https://support.apple.com/en-gb/guide/iphone/iph21d43af5b/io....
Could Apple have enabled this feature for all phones? Maybe
Would it have provided any use to older phones? Maybe
How much lifespan does it actually add? No one knows
Did they do this as planned obsolescence? Maybe.
There we go, the whole discussion finished.
I replace it with a 15 because it was dropping off the OS bandwagon, needed more storage, battery life, lightning port getting fiddly.
The OS support was the stake in the heart. If not for that I would have looked into getting the phone serviced with a new battery and port, and cleaned up some storage.
Unlikely? Yes, however it's not impossible.... and not the only alternate explanation :-)