Shizuku Keeper ♾️ Lite

1. Automate Community
2. Tools

✅️ Free
✅️ Non-root
✅️ Customizable
✅️ Error control
✅️ Shizuku 13.5+

UPDATES:
(v111)
• Fixed invalid log entry following ADB shell command block error.
▪︎ Restored compatibility with Shizuku versions < 13.6 (Google Play Store).
▪︎ Improved version checking to accept future releases of Shizuku.
▪︎ Revised output text to avoid line wrapping in notification header and toast.
▪︎ Improved path retrieval function of ADB shell command.
▪︎ Added compatibility with Shizuku 13.6+

ABOUT:
Automatically starts Shizuku on boot using wireless ADB debugging and periodically checks that it's running every 90 seconds thereafter, restarting it only when necessary. Monitoring is suspended during doze and the refresh interval can be adjusted.

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

Current status, error messages, and wireless debugging port are displayed in a persistent notification along with options to manually start/refresh Shizuku, open the 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 separately from other flows or even disabled via a custom category in Automate's notification settings.

This flow is intended for users who require continuous availability of Shizuku. Those just wanting to start it on boot and/or in response to key events may prefer "Better Shizuku Starter" (also less than 30 blocks). Maximum uptime may be achieved with original Shizuku Keeper which combines the two for unprecedented performance of Shiziku and/or ADB using Automate Premium (well worth a nominal one-time fee).

SETUP (Required):
1. Install Shizuku 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.
4a. Pair ADB shell command block 167 with wireless debugging.
4b. Ensure the "Keychain alias" field matches the name of your chosen certificate. *Repeat after every update.
5. Start flow.

SETUP (Optional):
*Most changes reset after update.
1. Adjust the refresh interval by editing the "Timeout" field of block 214. Enter 0 or leave blank to disable periodic refresh
2. Restrict notification customizations to this flow by creating and/or assigning a unique "Channel" in Notification show blocks 200 and 239.

▪︎ Shizuku downloads
https://github.com/RikkaApps/Shizuku/releases

RECOMMENDED:
▪︎ Flow update notification by Ethan Grant
https://llamalab.com/automate/community/flows/19103

CREDITS:
▪︎ Originally based on "Start Shizuku" by jack5mikemotown.
https://llamalab.com/automate/community/flows/44848