shizukudownload

Shizuku on Xiaomi (MIUI & HyperOS): Keep It Running

MFWritten by Marcus Feld, Android Systems WriterIndependent editorialUpdated July 2026Tested on real devices

Xiaomi, Redmi and POCO phones need three settings to keep Shizuku alive: allow autostart, set no battery restrictions, and lock it in recent apps. MIUI and its successor HyperOS are among the most aggressive at killing background services, which is why Shizuku “keeps stopping” on Xiaomi more than any other brand. Apply all three and it stays running.

Grab v13.6.0 from the download page and see the activation guide for the basics; this page is the Xiaomi-specific layer.

Activate Shizuku on Xiaomi

  1. Enable Developer options — Settings → About phone → tap OS version (or MIUI version) seven times.
  2. Use wireless debugging (Android 11+) to skip the Mi-account requirement that USB debugging imposes. Turn it on in Developer options and pair with Shizuku.
  3. Tap Start in Shizuku. For USB activation, sign into a Mi account, enable USB debugging and Install via USB, then run the ADB command from a PC.

The three settings that keep Shizuku alive

  1. Allow autostart: Security app → Permissions → Autostart → enable Shizuku.
  2. No battery restrictions: Settings → Apps → Manage apps → Shizuku → Battery saver → No restrictions.
  3. Lock in recents: open recent apps, swipe down on the Shizuku card (or long-press it) and tap the lock icon so MIUI will not clear it.
Do all three

On MIUI/HyperOS these settings work together. Autostart alone is not enough if battery saver is still throttling the app, and battery settings alone will not stop the recent-apps cleaner. Set all three and reboot once.

If Shizuku still dies on Xiaomi

  • Confirm you are on the GitHub build (v13.6.0), not the frozen Play version — see the troubleshooting guide.
  • Disable any third-party or built-in “memory cleaner” / “boost” feature that force-closes background apps.
  • As a last resort, test with MIUI optimization toggled off in Developer options — but expect other side effects and turn it back on if it does not help.

MIUI vs HyperOS: what changed

HyperOS is Xiaomi’s newer operating system (2024 onward) that replaces MIUI on Xiaomi, Redmi and POCO phones. For Shizuku the behaviour is identical: both kill background services aggressively, and both expose the same Autostart and battery-saver controls. A few menu labels moved, but the three settings above apply to both.

USB debugging and the Mi account requirement

Xiaomi gates USB debugging behind a signed-in Mi account and an extra “Install via USB” permission, which can take a few minutes to enable. Wireless debugging has no such requirement, so it is the fastest path to Shizuku on any Xiaomi, Redmi or POCO device.

If you must use USB: sign into a Mi account, enable USB debugging and Install via USB (both under Developer options / Security settings), connect, and run the ADB start command. Expect a one-time Mi-cloud verification the first time.

Turn off the memory cleaner

MIUI and HyperOS ship a built-in cleaner and one-tap “boost” that force-close background apps. Disable aggressive cleaning under Settings → Apps, and avoid third-party “booster” apps entirely — they are the second most common reason Shizuku dies on Xiaomi, after autostart being switched off.

Xiaomi FAQ

MIUI and HyperOS kill background services aggressively to save power. You must allow Shizuku to autostart, set it to no battery restrictions, and lock it in recent apps. Miss any one of these and the service will be stopped when the screen sleeps.
Open the Security app → Permissions → Autostart (on some builds Settings → Apps → Permissions → Autostart), then enable Shizuku. Autostart lets MIUI keep the service alive after the screen turns off.
For USB debugging Xiaomi often requires a signed-in Mi account and “Install via USB” enabled. You can avoid that entirely by activating Shizuku over wireless debugging (Android 11+), which needs no Mi account.
Usually no. Toggling “Turn on MIUI optimization” in Developer options can change how permissions are granted and sometimes causes more problems than it solves. Try the autostart and battery settings first; only experiment with the optimisation toggle if activation still fails.