Shizuku Watchdog (reupload)

1. Automate Community
2. Tools

Automatically starts the Shizuku service on boot and checks it every 60 seconds thereafter restarting it if stopped. Monitoring is suspended during doze and the refresh interval is customizable. It also checks Shizuku when the device enters an interactive state (becomes ready for user activity) to avoid making you wait for the next refresh.

UPDATES v23:
1. Restored 2 connections that were inadvertently removed from a prior version.
2. Increased ADB command failure retry limit from 3 (default) to 9.
3. Skip atomic load after subroutine and get ADB connection parameters directly.

ABOUT:
Targets unrooted Android devices version 12 (API 32) or lower that are unable to start Shizuku 13.6 on boot using a trusted WLAN, but is compatible with most Android devices running Shizuku version 13.5 only (see below). Also works with most forks of Shizuku 13.5, including that by Pixincreate.

This flow is intended for users who require maximum uptime and availability of Shizuku. Those wanting to start it on boot and in response to common events, but who don't necessarily need it running all the time, are better off with "Better Shizuku Starter." Both flows can run together, are 30 blocks or less, and have no measurable effect on battery life.

SETUP:
1. Install Shizuku 13.5 and pair it with wireless ADB.
2. Install Automate and enable "Run on system startup" in settings.
3. Download or import flow and grant required permissions.
4. Pair ADB shell command block [167] with wireless ADB.
5. Optionally update Delay block [155] with a custom refresh interval.
6. Start flow.

*Refer to Shizuku documentation for detailed instructions on Step 1:
https://shizuku.rikka.app/guide/setup

*Refer to Automate documentation for detailed instructions on Steps 2-6:
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. (TL;DR: Discussions following its release indicate breaking the startup script was likely unintentional suggesting this flow may work without any further modification in the next minor update of Shizuku.)

CREDITS:
Based in part on flow, "Start Shizuku" by jack5mikemotown.