Features

Start on boot

This option will automatically start Shizuku after a reboot. Additionally, the Watchdog service will start if the option is enabled. This option works on all devices (including non-rooted). On unrooted Android 11+ devices, Shizuku will wait for a Wi-Fi connection before proceeding (this is required to enable wireless debugging and start Shizuku).

Note

It may take a few minutes before the startup process begins, even if a Wi-Fi connection is established immediately after a reboot.

TCP mode

This option switches your device to the TCP/IP debugging mode when starting Shizuku. This is the equivalent of the adb tcpip command.

Tip

With this option enabled, Shizuku only requires Wi-Fi on the first start after a reboot. Any later restarts can be done without Wi-Fi! This is useful when certain apps (e.g., some banking apps) require you to disable USB debugging or developer options before being able to use the app, as you can immediately restart Shizuku afterwards without Wi-Fi.

Warning

TCP mode is more insecure than the normal Wireless Debugging mode that is used to start Shizuku. Anyone can send a prompt to your device asking you to "Allow USB debugging" for the device that's trying to connect. Shizuku will only prompt you to "Allow USB debugging" when you start Shizuku in TCP mode. NEVER accept the prompt if you aren't sure where it came from.

Watchdog

This option automatically restarts Shizuku if it stops unexpectedly. It can also send a notification when it crashes and suggest potential fixes.

Tip

The crash notification can be disabled from the app's notification categories.

Intents

Automation apps (e.g. Tasker, MacroDroid, Automate) can start/stop Shizuku on-demand using intents. The parameters for the start/stop intents are listed in the app.

Important

If you are using the Watchdog feature, you MUST stop Shizuku with an intent. DO NOT use the kill pid command or disable USB debugging to stop Shizuku. Otherwise, the watchdog will think that Shizuku crashed and restart the service.

Note

Please check the documentation for your automation app to learn how to send intents.

[BETA] Stealth mode

Shizuku can hide itself from other apps by changing its package name. When enabled for the first time, it will ask you to choose a folder where the clone APK will be saved. Shizuku will then uninstall itself, and you can install the clone.

The feature also provides a way to temporarily unhide Shizuku by installing a "stub application" with the original package name, so that it appears like Shizuku is installed. This is useful for some Shizuku-enabled apps that check if Shizuku is installed by package name before performing certain actions. When you're done, you can re-hide Shizuku, which uninstalls the stub application.

If you'd like to permanently unhide Shizuku, you'll need to uninstall the clone and re-install the normal version of the fork from GitHub.

Important

You'll need to re-configure Shizuku when enabling stealth mode for the first time. If you control Shizuku with an automation app, make sure to update the intents.

Also, you MUST update Shizuku through the in-app update feature. This applies even if you have Shizuku temporarily unhidden. Updating manually or with apps like Obtanium WILL NOT WORK because the clone signature is different from the original signature.

Note

Some apps may still be able to detect Shizuku even when hidden. Unfortunately, nothing can be done about this. However, this feature should work on most apps.