app: make the Shizuku banner actionable (open Shizuku / request permission)
A third-party app cannot start Shizuku — the wireless-debugging pairing flow is privileged and lives in Shizuku's own app — so the banner deep-links there when it is installed but stopped, and fires the permission request directly when it is running but unauthorised. The hint line says which. Verified on-device together with the earlier UX work: progress bar showing "test 4 of 8 · icmp.ping6 · ~33s left", Cancel beside the disabled Run button, cutout-safe title, and the banner live-updating from not-running to needs-permission via the binder listener. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
d7dda40e4e
commit
1d9e2063bf
@@ -520,3 +520,14 @@ Detection is listener-based (`addBinderReceivedListenerSticky` + binder-dead), b
|
||||
`pingBinder()` is only truthful once ShizukuProvider has delivered the binder — a one-shot poll at
|
||||
launch would show a false "not running". Installed-vs-not needs the `<queries>` package-visibility
|
||||
entry on Android 11+. Verified on-device: with shizuku_server stopped the banner appears correctly.
|
||||
|
||||
### Shizuku banner is actionable; progress + cancel verified on-device (2026-08-01)
|
||||
Tapping the shell-tier banner now does the right thing per state: **installed-but-stopped** →
|
||||
deep-links into the Shizuku app (a third-party app *cannot* start Shizuku itself; the wireless-
|
||||
debugging pairing flow is privileged and lives in that app, so taking the user there in one tap is
|
||||
the best available), **running-but-unauthorised** → fires the Shizuku permission request directly.
|
||||
The hint line states which action the tap performs.
|
||||
Verified on-device in one screenshot: progress bar at "test 4 of 8 · icmp.ping6 · ~33s left",
|
||||
Cancel button beside the disabled Run button, title clear of the status bar/cutout, and the banner
|
||||
having live-switched from "installed but not running" to "running but not authorised" via the
|
||||
binder listener when Shizuku was started mid-session.
|
||||
|
||||
Reference in New Issue
Block a user