
Amply
Amply is experimental and pre-launch. Direct control is verified on a limited set of devices — device reports and feedback are welcome!
Amply is an Android controller for OEM battery charge-protection modes. Its primary action temporarily allows one full charge, then restores your protective charge limit automatically — at 100%, on unplug, or at a safety timeout.
Features include:
- One-tap “charge to 100% once”, then automatic restore of your protective limit
- A dashboard that reports charge state honestly — verified, last-requested, or unknown
- Optional “reconnect to charge to 100%” gesture at the active hardware limit
- Quick Settings tile and a home-screen widget for protect / full-charge actions
- A persisted temporary-session monitor that survives reboots
- Diagnostics workflow (Shizuku) for before/after setting discovery, with redacted reports
- Works without ADB/Shizuku too — a charge alarm to remind you to unplug at a chosen level, a live battery-info card, and an OEM battery-protection guide on unsupported devices
- Branded light/dark themes, optional Material You, and contrast choices
- Works via
WRITE_SECURE_SETTINGSor Shizuku - No ads, no tracking, open-source (
fossandgplayflavors)
Currently supported for direct control:
- Pixel 6a and newer, Android 15+ (Google charging optimization)
- Samsung One UI 8 (multi-mode battery protection)
- Samsung One UI 4 / 5 (legacy battery-protection toggle)
- Xiaomi / Redmi / POCO on HyperOS 2 (charging protection)
- OnePlus / Oppo / Realme on ColorOS 15 (charging protection; requires Shizuku)
Other devices — other Pixels, Samsung One UI 6/7 and 9+, non-HyperOS-2 Xiaomi, and non-ColorOS-15 OnePlus/Oppo/Realme — are diagnostics-only for now.
Download
| Source | Status |
|---|---|
| GitHub (Pre-Release) |
Support the project
Amply has no ads and doesn’t sell your data. It’s free and open-source.
- Sponsor development on GitHub
- Buy me a coffee ☕
Get help
Screenshots






Setup & access
Install Amply, then enable control through one access path:
adb shell pm grant eu.darken.amply android.permission.WRITE_SECURE_SETTINGS
Alternatively, start Shizuku, grant Amply access, and optionally use Amply’s setup card to grant durable WSS. WSS-only control can write Pixel’s hidden values but Android blocks direct third-party reads, so Amply also watches Android’s public charging-hardware state; Shizuku provides exact configured-setting readback while it is running. On tested Pixels, Google’s policy worker takes roughly 10–15 seconds to propagate a setting change to the charging HAL.
License
Amply’s code is available under a GPL v3 license, this excludes:
- Amply icons, logos, mascots and marketing materials/assets.
- Amply animations and videos.
- Amply documentation.
- Google Play screenshots.
- Google Play texts & descriptions.
- Translations.