On this page
Android 10 and older
- No wireless pairing on the phone. Start from a computer, or from another phone over OTG, after every restart.
- Android 8 stops everything adb started when adb is turned off. The USB menu there is Select USB configuration. On Android 9 and 10 it is Default USB configuration.
Sources: Shizuku setup guide, Discussion 431, Issue 16
Android 11
- Wireless debugging with a pairing code appears, so no computer is needed. Wireless steps.
- Disable adb authorization timeout appears. Turn it on.
Sources: Shizuku setup guide, Android adb docs
Android 12
- Many reports of Shizuku stopping when the screen locks. The no data transfer or charge only USB default fixes them. Fix 25.
Android 13
- With Shizuku 13.6.0, Shizuku can start by itself without root on a trusted Wi-Fi network. How.
- Wireless debugging reaches TVs and Wear OS.
Sources: Release 13.6.0, Android adb docs
Android 14
- rish files must not be writable, so copy them into the terminal app's own data folder. Fix 46.
- ColorOS 14 needs Shizuku 13.5.2 or newer. The QPR2 and QPR3 updates needed 13.5.3 and 13.5.4.
Sources: Release 13.5.2, Issue 353, Issue 382
Android 15
- Screen share protection hides the code field while an app records or shares the screen. Fix 4.
- The search can hang until you tap Stop searching. Fix 10.
- Private Space isn't supported.
- Since about the February 2025 security update, Shizuku stops if both USB debugging and Wireless debugging are off. Keep USB debugging on.
Sources: Issue 868, Issue 955, Issue 837, Discussion 1000
Android 16
- QPR1 needs Shizuku 13.6.0 from GitHub; the older Play build breaks.
- Samsung One UI 8 needs the Charging phone only or Debugging only USB default. Samsung.
- Pairing is remembered, but some phones close Shizuku soon after it starts.
- Some 13.6.0 problems: fix 47 and fix 48.
Sources: Issue 1125, Issue 1427, Issue 1454, Issue 1149, Issue 2443
Android 17
- Official Shizuku 13.6.0 shows an empty app list and 0 apps authorized. Apps you allowed earlier keep working. New apps may still get the permission prompt, or can be allowed from the app's own settings, but you can't manage grants in Shizuku.
- The cause, as analysed by users: a change in what an Android function for listing apps returns, which Shizuku calls.
- Android 17 adds a newer wireless adb that connects by itself on trusted networks.
Sources: Issue 1965, Issue 1988, Issue 2016, Issue 2095, Issue 2180, Android adb docs