explaingit

rikkaapps/shizuku

★ 25,238KotlinAudience · developerComplexity · 3/5QuietLicenseSetup · moderate

TLDR

Android library that lets apps access system-level APIs by routing requests through a privileged background server, avoiding the need for root or slow shell commands.

Mindmap

mindmap
  root((Shizuku))
    What it does
      Routes system API calls
      Bypasses app limitations
      Uses Binder IPC
    How it works
      Elevated server process
      ADB or root setup
      Standard Android APIs
    Use cases
      App management tools
      System automation
      Device control apps
    Tech stack
      Kotlin
      Android Binder
      ADB protocol

Things people build with this

USE CASE 1

Build app managers that can enable/disable components or uninstall apps without user prompts.

USE CASE 2

Create automation tools that modify system settings or device state programmatically.

USE CASE 3

Develop device control apps that access detailed system information normally hidden from regular apps.

Tech stack

KotlinAndroidBinder IPCADB

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Android development environment setup and understanding of Binder IPC architecture to integrate the library into an app.

Use freely for any purpose including commercial. Keep the notice and disclose changes to the patent grant.

In plain English

Shizuku solves a specific Android developer problem: some system actions (like enabling or disabling app components, or querying detailed device state) require either root access or elevated ADB privileges, ADB being Android's built-in debugging bridge that lets a computer send commands to a phone. Normally, apps that need these capabilities resort to running shell commands, which is slow and unreliable. Shizuku takes a smarter approach. It works by having the user start a small background server process with elevated privileges (either via ADB from a computer, or via root). Once that server is running, any app that integrates Shizuku's API can talk to it through Android's standard inter-process communication system called Binder. The Shizuku server then relays system API calls on behalf of the app, using its elevated permissions to do things the normal app cannot do directly. To the app's code, it looks almost identical to calling Android system APIs normally. This is useful for developers building Android apps that need deeper system access, for example, apps that manage other installed apps, automate system settings, or bypass limitations that Android places on regular applications. It requires either a computer connected via ADB (no permanent root needed) or a rooted Android device, and the library itself is written in Kotlin.

Copy-paste prompts

Prompt 1
How do I integrate Shizuku into my Android app to access system APIs that normally require root?
Prompt 2
Show me example code for using Shizuku to enable or disable an app component from my app.
Prompt 3
What's the difference between using Shizuku vs. running shell commands for system-level Android tasks?
Prompt 4
How do I set up the Shizuku server on an Android device via ADB so my app can use it?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.