• General
  • How Can I Limit Battery Charge to 80%

i am using the accubattery app, not because of the 80%, the app beeps when the battery is charged to 80.
it cannot stop charging however, it has to be unplugged manually

bookreader Is that why? I thought maybe it was because of the substantial body of peer-reviewed research showing that battery degradation accelerates with increased voltage. But I guess if we can achieve results that are based on science we can't complain, even if the results were achieved due to the complaints of stupid people.

Kudos to all the stupid people demanding research-supported science-based improvements to our phones!

Hi!
Have you tried install magisk?
There's a module called acc(advanced charging controller) that can be modified to limit charge percentage.

yes, I know and I am quite clear that purists will come to say that installing root goes against the whole philosophy of the project, but it is my cell phone, so be more open minded.
Excuse my toxicity.

dgzeij bookreader

These comments aren't helpful.

For many people, phone batteries last longer than other parts of the phone do. This topic isn't worth such heated exchanges. My suggestion is to share your thoughts or any articles or research you have found helpful in a respectful manner, let others draw their own conclusions, and let them use their own devices the way they'd like.

To answer the original question, it's not possible to automatically limit charging to 80% on GrapheneOS, even with a third party app.

Stock Pixel OS does offer adaptive charging, but that is also not possible on GrapheneOS.

On the point of whether it makes sense to limit charging to 80%, I don't see any value in continuing that discussion, since everybody has had a chance to make their point heard, and it has since descended into bickering.

If any one is looking for sources about battery degradation, there is a decent paper from a few years ago that gives a nice run-down with lots of references. https://www.sciencedirect.com/science/article/pii/S2352152X19314227

A few highlights:

"Zhang et al. show that a typical laptop battery stored at 25 °C and 100% SoC will irreversibly lose 20% of its capacity each year."

"Hoke et al. argue that if battery temperature and charge-discharge cycling are kept constant, minimizing time spent at high SoC minimizes degradation. If the next day's energy requirement is known, the battery can be charged to the minimum required level, rather than to the conventional full charge."

"Lunz et al. show that battery lifetime can be increased by reducing the target SoC to lower values, or by minimizing rest periods at high SoC."

"Because standby times dominate battery operation, there is a large opportunity to increase battery lifetime by adjusting the time and frequency of charging (smart charging)."

I'm locking this thread, because of the points raised already, and the continued bickering.

I would also recommend caution when citing academic references which refer to SoC of a Li-ion battery. There are a number of different definitions of SoC, so it's important to understand which one is being referred to in which article.

treequell locked the discussion .
6 months later

We plan to implement customization for charging. It requires doing research/design work to come up with a sensible approach rather than simply what other operating systems are doing. There's a lot of evidence that providing control over the minimum capacity to begin charging and the maximum charge capacity would be useful for people who want to sacrifice a bit of short term battery life to preserve it better in the long term. Charge rate is already throttled based on capacity where it greatly slows down as it approaches 100%. it's also already throttled based on heat. We have most of the standard battery health features used on Pixels, just not the adaptive charging feature which guesses your schedule and slows down or limits charging in some cases.

A lot of people are passionate about this topic and there's conflicting information. GrapheneOS developers didn't participate in this discussion and none of it before this post is official info from the project. Current lack of non-standard features in this area doesn't mean we don't want to it, but we generally agree with the standard approach other than adaptive charging often not doing what people want/expect. Providing a bit more control over the standard approach rather than layering another on top may be exactly what's needed. Controlling how much it slows down based on heat, charge capacity, etc. along with controlling how high it goes is probably all we really need. Expecting people to manually set a scheduled time for charging over and over is unrealistic and conflicts with charging whenever you can.

A new thread should be made if people want to have constructive discussion about it without getting so heated.