DethByte64

Xtreme Battery Saver

v2.1.4guide

An extreme battery saver Magisk Module for users who want to really stretch their battery life

★83 stars
•Performance & Kernel•by DethByte64•GPL-3.0•Updated Aug 13, 2025
Platforms:
✓ Magisk✓ KernelSU
Download v2.1.4Starting download...GitHub Source
XtremeBS.zip

Overview

Xtreme Battery Saver (XtremeBS) is a root module for configurable power-management behavior. Its documented controls include CPU cores, app handling, process priority, Doze, Wi-Fi, low-RAM mode, and Google Mobile Services. It supports both Magisk and KernelSU according to the upstream README.

This is an aggressive tuning tool, not a universal battery fix. The upstream project warns that poor settings can cause lag, missed notifications or alarms, SystemUI crashes, and device instability. Compatibility varies by device and ROM; the project says it was tested primarily on a Pixel 5 running ProtonAOSP.

Installation

  1. Download the current XtremeBS.zip release.
  2. Flash it through Magisk or KernelSU.
  3. Reboot.
  4. Review the generated configuration before enabling non-default behavior.

The module starts its daemon in late-start service mode after Android boot completes. The release includes the XBSctl command-line utility and an optional WebUI launcher script.

Configuration

The configuration file is:

/data/local/tmp/XtremeBS/XtremeBS.conf

The upstream project documents two formats:

  • v1: legacy key=value settings controlled by a single trigger.
  • v2: recommended event blocks such as boot, charging, screen_off, low_power, manual, or a custom event.

A minimal v2 example from the upstream documentation is:

version=2
delay=3
log_file=/sdcard/XtremeBS.log
log_level=3

screen_off={
  handle_apps=nice
}

Reload after editing:

su -c XBSctl reload

Custom events can be started manually:

su -c "XBSctl start my_event"

The upstream documentation says multiple event blocks can stack, so overlapping changes should be planned carefully.

Controls and safety

The most consequential controls include:

  • disable_cores: disables selected or automatically selected CPU cores.
  • handle_apps: can kill, lower priority, or suspend apps.
  • handle_proc: changes process priority and can delay background work.
  • doze: forces light or deep Doze and may affect alarms.
  • kill_wifi: disables Wi-Fi.
  • low_ram: enables Android low-RAM behavior.
  • handle_gms: can affect Google services; killing GMS can break Google apps and Play Integrity.

Use an allowlist when suspending apps. Include essential apps such as the keyboard and terminal before testing. Start with one change, observe the device, and keep a recovery route available.

WebUI and logs

The upstream README documents a WebUI for v1.0.6+ launched through the module action script at:

http://127.0.0.1:8081

The documented status and log locations are:

/data/local/tmp/XtremeBS/XtremeBS.status
/sdcard/XtremeBS.log

Increase log_level when diagnosing behavior, then restore a quieter level after troubleshooting.

Recovery and troubleshooting

If the device is still responsive through ADB:

adb shell XBSctl safe

This is documented as stopping XtremeBS and unsuspending apps. If ADB is unavailable, the upstream README documents booting recovery and setting safemode=1 in /data/local/tmp/XtremeBS/XtremeBS.conf, then rebooting.

Device-specific cautions from upstream:

  • Avoid disable_cores and handle_cores on Samsung devices.
  • Avoid low_ram on OnePlus devices.
  • Disable or coordinate overlapping features in other battery/performance modules.

Sources

Frequently Asked Questions

Is XtremeBS plug-and-play?

No. The upstream README describes it as an advanced configurable module. Start with the default configuration, enable one change at a time, and test before enabling aggressive options.

What should I do if the device becomes unstable?

Use the upstream safe-mode path, such as adb shell XBSctl safe, when ADB remains available. The README also documents setting safemode=1 in the configuration from recovery. Disable risky options and restore the previous configuration.

Which settings are especially risky?

The upstream documentation warns about disable_cores, low_ram, Doze, app suspension, process reprioritization, and Wi-Fi disabling. It specifically advises avoiding disable_cores and handle_cores on Samsung devices and low_ram on OnePlus devices.

How do configuration changes take effect?

After editing the configuration, run XBSctl reload or reboot. In v2, verify the event name and block syntax; in v1, use the legacy key/value format.

Does XtremeBS guarantee a specific battery-life increase?

No. The upstream page mentions a possible increase but also says results depend on the device and configuration. Magisk Hub makes no battery-life guarantee.