Shizuku Keeper ♾️

1. Automate Community
2. Tools

✅️ Free
✅️ Non-root
✅️ Customizable
✅️ Error control
✅️ Stable release

UPDATES:
1. Updated appearance for consistency with my new flow, Shizuku Keeper Unlimited.
2. Minor refactoring and optimization.

ABOUT:
Automatically starts Shizuku on boot and whenever Wi-Fi connects using wireless ADB debugging. It then checks the service every 90 seconds, restarting it when necessary. Monitoring is suspended during doze and the refresh interval can be adjusted. It also checks Shizuku each time the device enters an interactive state (becomes ready for user activity).

Targets unrooted Android devices version 11-12 (API 30-32) that cannot start Shizuku 13.6 on boot using wireless debugging with a trusted WLAN, but is compatible with any Android 11+ device running Shizuku version 13.5.

Shizuku's current status, including any relevant error message and active TCP port, are displayed in a persistent notification along with options to immediately start/refresh the service, open the Shizuku app, or stop the flow entirely. You can dismiss the notification while disconnected from Wi-Fi, and it will reappear the next time you connect. It can also be managed individually or even disabled via a custom category in Automate's notification settings.

This high-performance flow is intended for users who require maximum uptime and availability of Shizuku. Those just wanting to start it on boot and/or in response to key events may prefer "Better Shizuku Starter" instead with fewer permissions and slightly lower power usage. Each flow runs on the free version of Automate with minimal impact on battery life.

SETUP (Required):
1. Install Shizuku 13.5 and pair it with wireless debugging.
2. Install Automate and enable "Run on system startup" in settings.
3. Download or import this flow and grant Automate the requested permissions plus WRITE_SECURE_SETTINGS.
4. Pair ADB shell command block [167] with wireless debugging.
5. Start flow.

SETUP (Optional):
1. Adjust the refresh interval by editing the "Timeout" field of Notification action block [214].
2. Restrict notification customizations to this flow by creating and/or assigning a unique "Channel" in Notification show blocks [200] and/or [239].
3. Disable toast messages by disconnecting Toast show block [267].

*Refer to Shizuku documentation for help with Step 1:
https://shizuku.rikka.app/guide/setup

*Refer to Automate documentation for help with remaining steps:
https://llamalab.com/automate/doc

*Download Shizuku 13.5 (Official):
https://github.com/RikkaApps/Shizuku/releases

TO-DO:
1. Include compatibility with Shizuku 13.6 (Discussions following its release suggest this flow may work with the next update of Shizuku 13.6 without needing any further modification).

CREDITS:
Originally based on "Start Shizuku" by jack5mikemotown.