The quick answer: Shizuku can give Battery Watch access to system operations used for automatic battery saver, Always-On Display controls and wake-lock tools. It is optional, and it does not make every root-only feature available.
Choose the access that fits your needs
| Feature | Access needed |
|---|---|
| Live current, voltage, power and temperature | No root |
| Charging and discharging session tracking | No root; persistent monitoring improves continuity |
| Historical screen and per-app usage insights | Usage Access |
| Automatic battery saver and AOD controls | Shizuku or root, with device support |
| Wake-lock inspection and app controls | Shizuku or root |
| Hardware charge limits | Root and a supported charging interface |
These are device-access requirements. Some app features also require Premium or a temporary rewarded-ad unlock. Permission and purchase status are separate.
Connect Shizuku to Battery Watch
- Install and start Shizuku using the official Shizuku setup guide for your device. Wireless debugging and root are different setup options.
- Open Battery Watch and go to Settings → Power & access.
- Choose Shizuku as the privileged access mode and approve Battery Watch’s access request when prompted.
- Return to Power & access and check that the app reports Shizuku as connected.
- Enable only the controls you want to use. Recheck connection status after restarting the device or Shizuku.
How automatic battery saver works
When enabled, Battery Watch evaluates screen-off conditions and can turn on Android’s battery saver according to its configured policy. It restores the previous saver state on wake. The app does not promise a particular number of extra hours.
For a useful comparison, record a normal discharge session before changing the setting and another under similar conditions afterward. Check both drain and whether background behavior still fits your needs.
Charge alerts and charge limits are different
A charge alert reminds you when your chosen threshold is reached. It does not stop electricity flowing into the battery.
Hardware charging control needs root and a compatible device interface. Battery Watch checks the resulting value when it writes a supported control. Shizuku access alone does not provide this feature, and root does not guarantee compatible hardware.
Wake-lock controls need context
Inspect an app before restricting it. Background work may be intentional, and force-stopping an app can interrupt playback, synchronization or notifications. Prefer the smallest change that addresses the behavior you observed.
If a control is unavailable
Check that Shizuku is running, Battery Watch is authorized, and Power & access reports the intended mode. If the device does not expose a supported control, basic monitoring still works. Root-only hardware behavior cannot be validated using a Shizuku-only emulator.