This is ShizukuTendCF — frdminc/ShizukuTendCF, a fork of thejaustin/ShizukuPlus maintained for the stayturgid Android fleet. It tracks ShizukuPlus and adds unattended-fleet features on top: permission-gated headless start/stop/status broadcasts (HEADLESS_START / HEADLESS_STOP / HEADLESS_STATUS) with an on-disk diagnostics log of the start path that HEADLESS_LOG returns (--ei lines N, default 200), readable on a release build, JSON fleet profiles (APPLY_FLEET_PROFILE) and auth-token provisioning (PROVISION_AUTH), indefinite start-on-boot retry, a trusted-signer allowlist that keeps the fleet agent's grant from being lost (see docs/trusted-signer-allowlist.md), a status card that shows protocol version and app build separately, and CI that refuses to cut an unsigned release. Releases are named ShizukuTendCF-<version>-<abi>.apk. Download them from this fork's Releases page.

Disclosure: this build ships a built-in trusted-signer allowlist — any app signed with the stayturgid-agent release certificate (SHA-256 35bbc3d1…ff9b6a) is always allowed Shizuku access. The manager shows it locked on; revoke and deny are ignored (a deny is honoured only when the server cannot verify the signer at that moment, until its next successful check). To cut such an app off, remove its digest from TrustedSigners, rebuild and restart, then revoke it in the manager (an Allow once tapped in the dialog is stored like any other grant); or uninstall the app, or stop Shizuku. (This reverses commit ca52b44d's "revoke sticks" rule, by owner decision on 2026-10-03.) That is intended for stayturgid fleet devices; if you are not running that fleet, this fork is probably not the one you want. Headless broadcasts must name the package since Android 8 — standard build: adb shell am broadcast -p af.shizuku.plus.api -a af.shizuku.plus.api.HEADLESS_STATUS; Drop-In build: replace both with moe.shizuku.privileged.api. The fork history, feature overlap matrix and remaining work are in docs/SHIZUKUPLUS-REBASE-PLAN.md; the pre-ShizukuPlus history is preserved on the legacy/pre-shizukuplus branch. Everything below is ShizukuPlus's own README.

Shizuku+

The advanced privileged-process manager for Android.

An enhanced version of Shizuku built on top of thedjchi/Shizuku, with quality-of-life improvements, backported optimizations, and exclusive Plus APIs.

Shizuku lets normal apps use system-level APIs directly via a privileged process started with adb or root. Shizuku+ keeps full compatibility while adding features for power users and developers.

🌐 Languages: English · Simplified Chinese

Contributors welcome! If you've found a bug or want to improve the codebase, please open an issue or pull request — the project is actively looking for contributors and collaborators.

⬇️ Download

Get the latest release from GitHub Releases — see the release notes there for what's changed recently.

✨ Shizuku+ Core Features

• Universal Privilege Provider: One interface for Root, ADB Shell, and Dhizuku (Device Owner).
• OneUI 8+ Theming Fix: Lets theming engines like Hex Installer or Substratum keep working on Android 16/17 and OneUI 8+.
• Dhizuku Mode: Share the system Device Owner binder with any app that has Shizuku permissions — set up via ADB, no root needed.
• Customizable Gestures: Swipe left, swipe right, and long-press actions, configurable per app.
• In-App Changelogs: See what's new after an update without leaving the app.
• Bulk Management: Multi-select apps to grant/revoke permissions or hide them in one tap.
• Activity Log: Audit trail of API calls and su bridge commands, with app icons and real-time updates.
• Root Compatibility Hub: Dashboard for legacy root apps, with granular module control (Magisk mocking, auto-grant, file interceptor, and more).
• Universal SU Automation: One-tap 'Magic Setup' to point all installed root apps at the Shizuku+ SU Bridge.
• Service Doctor: Diagnoses and fixes service startup issues (Samsung Auto Blocker included).
• Integrated Feature Guides: Every Plus feature has an info icon with a plain-language explanation of what it does.
• Quick Settings Tile: Check and toggle the service status from your notification panel.

🚀 Plus API Features

Shizuku+ provides exclusive system interfaces for advanced automation and tools — none of these exist in stock Shizuku:

• AICore+ Automation Bridge: Privileged UI automation (hierarchy dumps, tap/swipe) for AI-driven tools — no root needed. (added)
• AVF (Virtual Machine) Manager: Run isolated Linux/Microdroid VMs with GPU acceleration. (added)
• Privileged Storage Proxy: Authenticated access to restricted paths for backups and file management. /data/app/ and external /Android/data/ work in ADB mode; /data/data/ requires root (the server must run as UID 0 to cross app-private directory boundaries). (added)
• Device Spoofing (Spoof Device Identity in Settings): Present a different device identity to bypass device-specific restrictions. (added)
• Intelligence Bridge (AI Core Plus): Privileged NPU scheduling and screen context intelligence. (added)
• Window Manager Plus: Force free-form resizing, manage the Bubble Bar, and resilient overlays. (added)
• System Theming Bridge (Overlay Manager Plus): Privileged overlay management for rootless theming (e.g. Hex Installer). (added)
• Network & DNS Governor: Manage Private DNS and firewall routing for rootless ad-blockers. (added)
• Deep Process Control (Activity Manager Plus): Lets process managers kill apps and set standby buckets more aggressively. (added)
• Continuity Bridge: Secure state and task handoff between Shizuku+ devices. (added)

🛠️ Backporting & Optimizations

Shizuku+ makes regular Shizuku apps faster and more compatible without any code changes:

• Transparent Shell Interceptor: Routes common pm, am, and settings commands through faster native APIs.
• Local ADB Proxy: Emulates an ADB server on port 15555, so legacy apps can use Shizuku without Wireless ADB staying on.
• SU Bridge: A Shizuku-backed su drop-in for non-rooted apps that support a custom root path. Common root commands are translated into real framework operations where shell UID allows it — iptables --uid-owner per-app blocks become live NetworkPolicy restrictions, resetprop reads/writes real system properties, and chmod/chown apply for real — falling back to mocked success only when an operation genuinely requires root (e.g. flashing partitions or loading kernel modules).
• plus CLI Helper: A privileged command-line utility, available inside rish.
• Dynamic App Database: Keeps app descriptions and suggestions in the UI up-to-date from GitHub.

⚙️ Modular Control

Everything in Shizuku+ is optional. Use the Plus Features category in Settings to toggle:

• Transparent Shell Interception
• Individual Plus APIs (AVF, Storage, Intelligence, etc.)
• Home screen card visibility
• Activity Logging

🔌 Third-Party App Compatibility

Shizuku+ installs under its own package (af.shizuku.plus.api) so it can coexist with stock Shizuku. Because most Shizuku-aware apps look specifically for the moe.shizuku.privileged.api package, Shizuku+ ships a lightweight Compat Hub — a tiny companion app that registers that package name and forwards binder/permission requests to Shizuku+.

If third-party apps don't detect Shizuku+:

1. Start the Shizuku+ service (ADB or root).
2. On the home screen, use the Compat Hub card to install the companion (it's bundled in the app; installation goes through the running service, so start the service first).
3. Re-open the third-party app — it should now detect Shizuku and receive the service binder.

Alternatively, install the drop-in build, which registers as moe.shizuku.privileged.api directly (do not install it alongside stock Shizuku).

☑️ Requirements

Minimum: Android 7+ · Fully supported through Android 17 (SDK 37)

• Root mode: Requires a rooted device
• Wireless Debugging mode: Android 11+ and all Android TVs
• PC mode: All devices
• Start on boot: Available only with Wireless Debugging or Root mode

On Android 16+, Shizuku+ requests the new Local Network Protection permissions so wireless-debugging discovery and pairing keep working; on Android 17, it transparently handles the hidden-API deviceId change so authorized apps still appear and permission grants still apply.

📱 Developer Guide

See the Shizuku+-API repository for documentation on the exclusive Plus APIs.

🙏 Acknowledgements & Licenses

Shizuku+ is a community-driven enhancement and fork of thedjchi/Shizuku, which is itself a fork of the original RikkaApps/Shizuku. This project is not affiliated with the original RikkaApps team.

Thanks to the following upstream contributors and projects whose work makes Shizuku+ possible:

• RikkaApps / Rikka — For the foundational Shizuku project and its elegant API design.
• thedjchi — For the intermediate fork and quality-of-life improvements, and for carrying the Android 17 (SDK 37) compatibility work that Shizuku+'s A17 support is adapted from.
• kerneldroid / Nightzuku — Origin of the Android 17 hidden-API deviceId compatibility approach (the Android17Compat / InstalledPackagesCompat reflection layer) and Local Network Protection handling that this fork's A17 support descends from.
• LandonMoran — For porting Nightzuku's Android 17 support into the thedjchi fork and verifying it end-to-end on a physical Android 17 device (pairing, service start, and the authorized-apps list), which is the field validation Shizuku+'s port builds on.
• Muntashir Akon — For the aShell You codebase, which inspired the terminal and shell automation features.
• iamr0s — For Dhizuku, enabling the unified Device Owner privilege mode, and AndroidAppProcess for standalone Java process execution.
• pascua28 — For native Samsung System UID 1000 escalation integration.
• kerneldroid — For the Nightzuku fork, which inspired our Android 16/17 (SDK 37) hidden API resilience (handling deviceId) and UI modernizations.
• ShizukuExt-SystemUID — For conceptualizing systemic UID 1000 privilege escalation beyond standard limits.

Upstream Projects

Project	Author	License	Role
Shizuku	RikkaApps / Rikka	Apache 2.0	Foundational privileged-process architecture
Shizuku (fork)	thedjchi	Apache 2.0	Intermediate fork with QoL improvements; carried the Android 17 compat work Shizuku+ adapted
Nightzuku	kerneldroid	Apache 2.0	Origin of the Android 17 hidden-API deviceId + Local Network Protection compatibility approach
Shizuku (fork)	pascua28	Apache 2.0	Samsung UID 1000 system execution exploit
Nightzuku	kerneldroid	Apache 2.0	Android 16/17 API resilience & UI modernizations
ShizukuExt-SystemUID	ShizukuExt Team	Apache 2.0	System UID privilege escalation concepts
Dhizuku	iamr0s	Apache 2.0	Device Owner binder sharing (Dhizuku Mode)
AndroidAppProcess	iamr0s	LGPL-3.0	Standalone high-privileged Java process wrapper

Open Source Libraries

Library	Author	License
AndroidX Jetpack	Google / AOSP	Apache 2.0
Material Components	Google	Apache 2.0
Material Symbols	Google	Apache 2.0
Kotlin / Coroutines / Serialization	JetBrains	Apache 2.0
RikkaX Libraries (appcompat, material, insets, html, recyclerview, preference, lifecycle, parcelablelist)	Rikka	Apache 2.0
Hidden API / Refine	Rikka	Apache 2.0
Mavericks (MvRx)	Airbnb	Apache 2.0
Lottie	Airbnb	Apache 2.0
Coil	Coil Contributors	Apache 2.0
Koin	Koin Contributors	Apache 2.0
Timber	Jake Wharton	Apache 2.0
libsu	topjohnwu	Apache 2.0
AndroidHiddenApiBypass	LSPosed	Apache 2.0
libcxx	LSPosed / LLVM	Apache 2.0 + LLVM Exception
AppIconLoader	Zhang Hai	Apache 2.0
BoringSSL (NDK)	vvb2060 / Google	Apache 2.0 / ISC
Gson	Google	Apache 2.0
LeakCanary	Square	Apache 2.0
AboutLibraries	Mike Penz	Apache 2.0
Bouncy Castle	Legion of Bouncy Castle	MIT
Sentry Android SDK	Sentry	MIT
SQLite (C Recovery API / CLI)	D. Richard Hipp / SQLite Consortium	Public Domain

Full license texts and per-library details: OPEN_SOURCE_LICENSES.md | NOTICE

📃 License

Apache 2.0

Contributors

Thank you to everyone who has contributed code, translations, and testing to Shizuku+:

Code Contributors

Contributor	Contribution
thejaustin	Project founder & primary maintainer — all core Plus features, UI/UX, and infrastructure
thedjchi	Intermediate fork base; Android 17 (SDK 37) compatibility groundwork
Kevin Doremy	Dead code removal, unused import cleanup, layout & class refactoring
Ryfter	mDNS timeout improvements, FGS subtype refactoring, notification UX
vvb2060	AGP build system updates, LTO optimization, license clarifications
Haruue Icymoon	Documentation & README improvements

Translation Contributors

Language	Contributor
Brazilian Portuguese	odorizzioficial
French	Ryfter, T. Clement
Vietnamese	ThePrimalPea
Filipino	IverCoder
Italian	Dany-coder778
Japanese	MES-mitutti

Plus many more via community translation through Weblate — thank you to all translators!

Acknowledgments

• Special thanks to AkayamiShurui42 for the proactive security research and stability patches (Reference: #239).
• Thank you to AlexeiCrystal for identifying MIUI crash bugs and suggesting the Compat Hub workaround for legacy apps (#241, #242).
• Thank you to ddnexus and kai-bash for highlighting the Device Owner factory reset trap and Google Backup conflicts (#237).
• Thank you to Kevinco1 for feedback on root compat app detection issues (#243).
• Thank you to aragortsantiago6-beep and Scoop2389 (Pixel 9a) and ConversionRituals (Xiaomi) for on-device Android 16/17 testing, crash reports, and logs that drove the SDK 37 hidden-API and Local Network Protection compatibility fixes (#317, #323).
• Thank you to gmm96 for extensive multi-round logcat debugging across several builds that pinned down the Cached Apps Freezer binder-delivery bug (#371).
• Thank you to odorizzioficial for the complete Brazilian Portuguese translation (#409), and for the detailed report on the Samsung "Sleeping apps" Watchdog freeze (#415).