Skip to content

Architecture

krishna3163 edited this page Nov 11, 2026 · 2 revisions

🏛 Architecture & Internal Blueprint

OmniShizuku is architected as an advanced multi-process, multi-layer framework connecting user-space Android management tools to privileged native services without permanent root or boot image modifications.


🏗 Subproject Modules

Module Namespace / Target Purpose & Responsibility
:manager com.krishna.omnishizuku Modern Jetpack Compose UI, AGY Comput engine, ADB module loader, ShizuWall controller, and client authorization gateway.
:server Native executable / Binder daemon Privileged Shizuku service running under UID 2000 (shell) or UID 0 (root). Hosts the IPC endpoints.
:starter Native bootstrap executable Handles startup execution across wireless debugging (adb pair / connect), boot receivers, and local terminal.
:rish Native PTY client Remote interactive shell executable interfacing via pseudo-terminals for full command-line sessions.
:database Android Room Database Persistent tracking of authorized client applications, permission history, and diagnostic events.
:wallpaper-apis Kotlin library Dynamic wallpaper management bypass engine hooking into IWallpaperManager.
:nightdog Android Foreground Service Battery-optimized heartbeat daemon protecting Shizuku server binder from aggressive OEM process killers.
:dfroot Native C & Kernel Module Sandbox Local privilege escalation testing and kernel exploit security auditing framework.

🔒 Security Model & Isolation

  1. Binder Token Validation:
    • Each client application receives a unique cryptographic Binder token during initialization.
    • Unauthorized processes attempting to communicate with moe.shizuku.server are immediately dropped with SecurityException.
  2. SELinux Transits:
    • Executes under shell or su contexts while maintaining strict compartmentalization to prevent domain leaks.
  3. Automated Defect & Threat Remediation:
    • Real-time sanity filters prevent shell escapes and protect system properties from arbitrary corruption.

Clone this wiki locally