HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
VR-25
acc
Shell2021–2026
VR-25 / acc

acc

Advanced Charging Controller

11Distinct people
15Mentions
0Explicit recommenders
2.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Advanced Charging Controller

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year15 dated mentions

Observed mentions: 2021-01-30 15:56:06 UTC to 2026-01-26 03:15:12 UTC.

02462021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC606
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

15 sources
Unless your Pixel 4a is from Verizon (locked), keep it. Unlock the bootloader, then install LineageOS, MindTheGapps, and Magisk. Once you have Magisk stabilized, install the Advanced Charging Controller, and configure it to halt charging at 80%. That should solve your problems, and turn the updates back on. I don't think there is a way to make Google Pay work in this configuration, which is a drawback. I can put all the URLs here if you ask. Edit: https://lineageos.org/ [I did not remember that Lineage hosts gapps images] https://wiki.lineageos.org/gapps/ [IIRC, the APK is renamed to a ZIP and flashed with recovery, then name it back and install the app] https://github.com/topjohnwu/Magisk/releases/tag/v28.1 https://magiskmanager.com/ https://github.com/VR-25/acc/releases/tag/v2023.10.16
In Google Pixel 4a's old firmware is gone, trapping users on buggy battery update
You can run these commands to turn that kill behavior off: setprop persist.sys.fflag.override.settings_enable_monitor_phantom_procs false /system/bin/settings put global settings_enable_monitor_phantom_procs false Termux as an example supports several services that run forever. Works great, sshd and crond don't get killed for example. https://wiki.termux.com/wiki/Termux-services Battery wise you can use this app to keep it in a healthy range and temperature indefinitely: https://github.com/VR-25/acc
In Install postmarketOS on Android phone and use Docker as a home server
GOS's limited device support is disappointing, but I understand their reasoning. I still wish they'd release "GrapheneOS Minus" (in the vein of uBlock Origin Minus[0]) so a much larger audience could have 95% of the security benefits they'd have on Pixel hardware. As an alternative to replaceable batteries you could consider installing something like acc[1] to mitigate stress on your battery. My phone is 7 years old and the original battery still holds a charge like the day I bought it. [0]: https://github.com/uBlockOrigin/uBlock-issues/discussions/22... [1]: https://github.com/VR-25/acc
In GrapheneOS finds Bluetooth memory corruption via ARM MTE
On Android, I use a terminal script called Advanced Charging Controller (ACC) to automate keeping the battery under 80% and some other battery saving tweaks. It allows you to charge to any value (like 80%), then stop charging until it discharges to another set value, which triggers it to start charging again. That was you can keep it between something like 70% and 80% while you leave it charging over night. It also has settings to keep the batter under a specified temperature and trigger cool-down intervals if it gets to a particular temperature. It can use a job scheduler to switch between different profiles for different days, or events. There are also some frontend apps, which let the user control the script with a more friendly GUI ("AccA" or "ACC Settings"). Link to the script: https://github.com/VR-25/acc This does require root per
Read the rest
missions, though.
In Charging a lithium battery to 80% only?
This seems to be partly a Lineage problem - with probably some Android culpability mixed in. Lineage had their own very simple to install superuser addon, but that was dropped a few versions ago. Some Android changes prompted this, but probably also their attitude against rocking the boat (no rooting, no signature spoofing, etc). The remaining solution was Magisk. Magisk was equally easy to install, but recently deprecated that easy install method so that only patching the ROM file remains (you get that file from the ROM you run, unpack the archive, if you are unlucky you need to unpack a second payload.bin file, https://wiki.lineageos.org/extracting_blobs_from_zips#extrac...). But not only is that more complicated, it also does not persist after a Lineage upgrade, which happens every week, see https://github.com/topjohnwu/Magisk/issues/3
Read the rest
820#issuecomment.... Totally crazy for a project not in early alpha. I want root to properly manage my battery via https://github.com/VR-25/acc ( with ideally https://github.com/MatteCarra/AccA as Magisk module). How ridiculously complicated that is now and that the install procedure is broken without them documenting it soured me quite a bit on Magisk, but I also start to develop some bad feelings about Lineage - because it is them that would be in the best position to provide a simple root solution. But they just refuse it, and even forbid discussing such topics on their subreddit - that alone shows me that the project is very user hostile currently. I doubt with that attitude they can make a turnaround, but I'd be happy to be wrong... Sadly the other bigger ROMs are to my knowledge not better in this category, neither /e/ with their service suite, nor DivestOS with the passionate developer nor CalyxOS or GrapheneOS with their "security" focus are interested in giving the user full access to their device. Android seems to be a dead end here, real Linux is needed.
In New F-Droid repository format for faster and smaller updates
There's also the possibility of using Advanced Charging Controller - though it requires root. Essentially you can set it up so when the battery reaches eg. 100% it stops charging, and resumes only once it reaches eg. 15%. Surprisingly the Android devices that I have still don't ever stop charging on their own, constantly keeping 100%. [Advanced Charging Controller (ACC)](https://github.com/VR-25/acc) [BU-808: How to Prolong Lithium-based Batteries](https://batteryuniversity.com/article/bu-808-how-to-prolong-...)
In How to control your smart home without yelling at a dumb voice assistant
Keeping them within a certain range is useful but not as much as preventing them from overheating, heat and fast charging is more dangerous, basically if you limit them to 80% it will prevent trickle charging, you can do this in hardware by monitoring the speed it charges at and shutting off when it lowers with wattage monitoring equipment. Apple has this as well, and every lithium charger has trickle charging at 80%, but not all of them are able to end charging at this percentage. https://linrunner.de/tlp/settings/battery.html https://support.apple.com/en-us/HT210512 The best implimentation from my understanding is this one under android. https://github.com/VR-25/acc By hack I mean a bypass versus your meaning of attacking the security and removing DRM, is there a reason you can't just use another chip or anything special its doing? Do y
Read the rest
ou need the CPU and is the cryptography documented enough to make it easy or woth the effort? It may also be a passion project so I understand if you just want to do it to do it, and even share the information. If it is battery charging features if they're important are not special. The last 20% makes extra cycles and is the most stressful. https://batteryuniversity.com/article/bu-409-charging-lithiu... >Turn off the device or disconnect the load on charge to allow the current to drop unhindered during saturation. A parasitic load confuses the charger. >Charge at a moderate temperature. Do not charge at freezing temperature. (See BU-410: Charging at High and Low Temperatures) >Lithium-ion does not need to be fully charged; a partial charge is better. Not all chargers apply a full topping charge and the battery may not be fully charged when the “ready” signal appears; a 100 percent charge on a fuel gauge may be a lie. >Discontinue using charger and/or battery if the battery gets excessively warm. >Apply some charge to an empty battery before storing (40–50 percent SoC is ideal). (See BU-702: How to Store Batteries.)
In Show HN: Long Range E-Bike
If you're a tinkerer, I'd seriously recommend using something like ACC (Advanced Charging Controller). It'll automatically cut your charge off at ~80% and slow the charging if it's heating up too much. Should greatly extend the service life of your battery. You can pretty much just install with Magisk and forget it. Perhaps it's too late for your current phone/battery but maybe on the next one. https://github.com/VR-25/acc Pair with something like AccuBattery for visibility into battery capacity over time.
In OnePlus 6 and OnePlus 6T seeing work for mainline Linux kernel support

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.