What Shizuku Actually Unlocks (And the Apps Worth Granting)

Last updated: September 18, 2026 · 7-minute read

29,805 stars, and not a single push to the upstream repository since June 18, 2025. That is the strange state of Shizuku — the Android middleware that lets normal apps borrow system-level powers through ADB, no root required — fifteen months after its last upstream commit. The project is not abandoned in the legal sense, the docs site still stands, and the permission model still works on current Android. What is actually happening is more interesting: development energy has migrated to forks and, above all, to the app ecosystem built on top — which is now large enough, and good enough, to deserve its own map.

This is the follow-up to the ShizukuPlus piece — less about the middleware, more about what you do after the pairing screen.

The 60-second version of how Shizuku works

Shizuku runs a privileged process on your phone, started either from a PC over ADB or via wireless debugging, directly on the device. Apps that hold the Shizuku permission can call system APIs through that process — the powers of a rooted shell, scoped and revocable, without unlocking the bootloader. Rebooting kills it until re-paired, unless you enable the wireless-debugging auto-restart on Android 11 and newer. The mechanism is documented at shizuku.rikka.app, and it remains one of the cleanest privilege designs in the Android ecosystem.

Which apps deserve that trust is the real question, and the best-curated answer is timschneeb's awesome-shizuku list — 10,064 stars, community-maintained, split into open-source and closed-source sections with licenses on every row. Everything below is drawn from that list, cross-checked on September 6, 2026.

Audio: the category that justifies the whole setup

RootlessJamesDSP is the flagship example, from the same developer as the awesome list itself. It implements the system-wide JamesDSP audio processing engine on non-rooted devices — equalization, effects, per-device tuning — using Shizuku to attach to the audio service in a way the Play Store's equalizer apps cannot. GPL-3.0, mature, and consistently the first app people name when asked why they set up Shizuku at all. If you have ever bounced off Android's anemic built-in audio settings, this is the payoff.

Automation: the quiet workhorses

Three entries cover most automation needs without Tasker's subscription and without root:

• AutoJs6 — a JavaScript-based automation engine (MPL-2.0) for scripting UI interactions directly on the device.
• Geto — automatically applies device settings when a specific app launches (GPL-3.0); the "when I open the camera, kill background sync" class of rule, finally simple.
• PhoneProfilesPlus — Apache-2.0, schedules whole device configurations around situations like work hours or charging.

All three use Shizuku to reach settings and system services that Android normally walls off from background apps, and all three are installable from F-Droid or their repos.

The new wave: AI agents on the phone

The awesome list's newest category is the most consequential. A cluster of projects now uses Shizuku as the privilege layer for on-device AI agents:

• Mythara (MIT) — an open-source, local-first agentic layer running 65-plus on-device tools: calls, SMS, calendar, Termux, face recognition — using Shizuku only for cosmetic system tweaks like font scale and dark mode, a deliberately scoped privilege request.
• Operit AI (LGPL-3.0) — an agent that runs commands on the device through Shizuku.
• Open-AutoGLM-Android (GPL-3.0) — drives the phone via the AutoGLM vision-language model.
• rish-mcp (MIT) — the bridge that connects the two halves of this site: it exposes the Android Shizuku shell to AI assistants as an MCP runshell tool over an outbound relay, meaning Claude or any MCP client can run commands on your phone. No VPN, no ADB over USB, no sshd.

That last one deserves a beat of silence. The ADB-without-root trick that made Shizuku famous is now a tool surface for coding agents — your desktop AI pair-programmer gains hands on the actual device. Powerful, and exactly the kind of capability that makes the trust model below non-negotiable.

Where it falls short

The honest part. Upstream's fifteen-month commit gap means bug fixes for new Android releases land in forks — ShizukuPlus being the maintained example this site covered, unifying Root/ADB/Dhizuku startup with its own API additions — rather than in the original app. Chasing the fork with the freshest commit is a reasonable strategy; so is staying on upstream until something breaks, since the permission model has not changed underneath.

The deeper caveat is structural: granting an app Shizuku access hands it real power — the ability to grant itself permissions, modify system settings, read protected state. Every recommendation above is open source with a license on record, and the awesome list deliberately quarantines closed-source apps into a separate file; read that split as the editorial statement it is. Method note, as always: I have not run this full stack on a device — the map above comes from the awesome-shizuku list, the upstream repos, and GitHub API data pulled September 6, 2026.

Try it in five minutes

The minimal useful path takes one pairing and one install:

1. Install Shizuku (or ShizukuPlus) and start it via wireless debugging — Android 11 and newer needs no PC. 2. Install RootlessJamesDSP, grant it Shizuku access, and attach the effect engine to your current audio output. One app, immediate payoff. 3. Only after that works, browse the awesome-shizuku list for the categories you actually need — and read the license line on every app before granting.

TL;DR

• Upstream Shizuku (29,805 stars, Apache-2.0) has not been pushed since June 18, 2025 — the ecosystem, not the middleware, is where the action lives.
• RootlessJamesDSP remains the killer app: system-wide audio processing on non-rooted devices, GPL-3.0.
• Automation picks — AutoJs6, Geto, PhoneProfilesPlus — reach system settings that background apps normally cannot touch.
• The new wave is on-device AI agents: Mythara, Operit, and rish-mcp, which hands an MCP client like Claude a scoped shell on your phone.
• Trust is the currency: every pick above is open source with a verified license; forks like ShizukuPlus carry the maintenance torch upstream dropped.

---

Not affiliated with RikkaApps, timschneeb, or any listed app's developer. Sources: the awesome-shizuku list, the Shizuku repository, shizuku.rikka.app, and GitHub API data pulled September 6, 2026.