Shizuku Android Compatibility (Android 7 to 17)
Shizuku v13.6.0 runs on Android 7.0 through Android 16. Below Android 11 you activate it from a PC; on Android 11 and newer you can activate wirelessly with no computer. Android 14 and 15 add one extra step for the rish shell, and Android 17 currently has an unresolved compatibility bug on Pixels.
Whatever your Android version, use the latest GitHub release from the download page — a single APK covers every supported version, and older builds are the main reason Shizuku “stops working” after an OS update.
Version compatibility table
| Android version | API | Shizuku status | Activation | Notes |
|---|---|---|---|---|
| Android 7.0 – 7.1 Nougat | 24–25 | Supported (minimum) | PC / ADB | Lowest version v13.6.0 runs on. |
| Android 8.0 – 8.1 Oreo | 26–27 | Supported | PC / ADB | — |
| Android 9 Pie | 28 | Supported | PC / ADB | — |
| Android 10 | 29 | Supported | PC / ADB | Last version without wireless debugging. |
| Android 11 | 30 | Supported | Wireless or PC | Wireless debugging added — no PC needed. |
| Android 12 / 12L | 31–32 | Supported | Wireless or PC | — |
| Android 13 | 33 | Supported | Wireless or PC | Trusted-Wi-Fi auto-start added. |
| Android 14 | 34 | Supported* | Wireless or PC | rish needs the private-dir dex step. |
| Android 15 | 35 | Supported* | Wireless or PC | Same rish dex note as 14. |
| Android 16 | 36 | GitHub build only | Wireless or PC | Play Store build fails — use the GitHub APK. |
| Android 17 | 37 | Broken (Pixel) | — | Known upstream bug, no fix yet. |
* Supported, with the Android 14+ rish private-directory step. Android 17 API level is provisional.
Which versions need a PC
Android 10 and older need a one-time PC connection to activate Shizuku; Android 11 and newer can do it wirelessly. Wireless debugging is a feature Google added in Android 11, and Shizuku uses it to start its service with no computer. On older phones you run a single ADB command from a PC instead.
Either way the permissions an app receives are identical — the method only changes how the service is started. Full steps for both are in the activation guide.
Android 14 and 15: the rish exception
Shizuku itself works normally on Android 14 and 15, but the rish shell needs one extra step. Android 14 (API 34) refuses to load a writable dex, so rish’s files must live in your terminal app’s private directory rather than shared storage. This affects only rish, not the core Shizuku permissions.
If rish prints “app_process cannot load writable dex,” move the files into Termux’s home directory as shown in the rish setup guide.
Android 16: use the GitHub build
Android 16 works with Shizuku, but only the GitHub release — the Google Play build lacks Android 16 support and is the single most common cause of failure after updating. The Play version has been frozen since March 2024, while the GitHub release (v13.6.0) tracks the source.
Install the GitHub APK and the “Shizuku not working on Android 16” problem disappears.
Android 17: currently broken on Pixel
As of mid-2026, Shizuku does not work correctly on Pixels running Android 17 — it starts but cannot detect or manage other apps. This is a known upstream bug (GitHub issues #2180 and #1967) with no patched release yet, not a configuration problem you can fix.
If you depend on Shizuku, stay on Android 16 for now. The Pixel guide tracks this status and will be updated when a fix ships.