v13.6.0.r2240
v13.6.0.r2240
Changes since v13.6.0.r2239
🐛 Bug Fixes
1 distinct GitHub issue(s) referenced in this release.
📦 Recent Releases
🚀 Most recent major release — v13.6.0.r2202
Third-party apps that Shizuku+ grants permissions to (WifiList, App Ops, Hail, Tasker, and others) now reliably detect and connect to the service. Closed the last gap in the Cached Apps Freezer guard: a UserService's very first connect callback could be silently dropped if the client app was frozen in the background while its process was still starting.
⚠️ Most recent critical fix — v13.6.0.r2153
Releases r2141–r2152 all shipped the Drop-In build under the Plus APK's filename — anyone who installed "Shizuku+" in that window actually got moe.shizuku.privileged.api, which fails to install or update alongside stock Shizuku. Fixed by selecting release assets by verified applicationId instead of directory order.
| Release | Highlight |
|---|---|
| v13.6.0.r2240 (this release) | fix(#387): retry binder delivery and show actionable feedback on frozen-app failure |
| v13.6.0.r2239 | fix(#400, #402): fix live activity notification respecting toggle, fix SU bridge redeploy on read-only dex |
| v13.6.0.r2238 | chore: add settings XML string reference check to pre-push guard |
| v13.6.0.r2237 | fix: correct string references in settings_shizuku_plus.xml |
| v13.6.0.r2231 | feat: auto-run snippets on Shizuku service start (#399) |