oorbE
Decoupled Android Systems Architecture & Shizuku IPC Daemon
“Architecting an un-rooted enterprise Android runtime with kernel-level privilege access and hardware keystore encryption.”
Executive Overview
oorbE is a high-performance Android systems and personalization platform engineered to bridge consumer mobile ergonomics with low-level device control. It eliminates the need for bootloader unlocking or root privileges by implementing a privileged IPC architecture via the Shizuku Binder daemon across 20+ decoupled Gradle modules.
The Problem: The Android Permission Dilemma
Accessing low-level OS operations (deep process inspection, frozen package management, battery cycle telemetry) traditionally required rooting the device.
- Rooting unlocks bootloaders and immediately invalidates Google Play Integrity / SafetyNet guarantees.
- Banking apps, biometric keys, and enterprise profiles refuse to execute on rooted devices.
- Monolithic Android applications suffer from quadratic compile times and fragile architectural boundaries.
The Constraints: System Privileges on Pristine Stock Hardware
The system needed to execute privileged operations without compromising Android’s verified boot chain.
Privileged IPC via Shizuku
oorbE binds to Shizuku’s privileged AIDL service over Android’s native Binder IPC driver (/dev/binder), obtaining adb shell credentials (UID 2000) on 100% un-rooted consumer hardware.
20+ Module Gradle DAG
Decoupled into :core-security, :core-platform, :core-ui, :feature-shizuku, :feature-vault, and :feature-applock. Feature modules never depend directly on each other.
Multi-Module DAG & IPC Topology
┌────────────────────────────────────────────────────────┐
│ :app │
│ (Dependency Injection & Application Root) │
└───────────────────────────┬────────────────────────────┘
│
┌────────────────────────┼────────────────────────┐
▼ ▼ ▼
┌──────────────┐ ┌────────────────┐ ┌─────────────────┐
│ :core-ui │ │ :core-security │ │ :core-platform │
│ Design Tokens│ │ AES-256 Keystore│ │ Android Syscalls│
└──────────────┘ └────────────────┘ └─────────────────┘
▲ ▲ ▲
├────────────────────────┴────────────────────────┤
│ FEATURE MODULES LAYER │
│ :feature-shizuku :feature-vault :feature-lock │
└─────────────────────────────────────────────────┘Zero Circular Dependencies
Strict Gradle api vs implementation visibility boundaries ensure changes to UI or themes never trigger recompilation of core security or data modules.
Zero-Copy Memory Pipelines
Telemetry and system stats stream across Binder IPC boundaries using shared memory ParcelFileDescriptors, avoiding JSON serialization overhead.
Hardware-Backed Keystore Cryptography
Security in oorbE follows zero-trust client principles. Cryptographic keys are generated inside the device’s physical Secure Element (SE) / Trusted Execution Environment (TEE) and never enter user-space RAM.
Vault records and application lock configurations are encrypted using AES-256-GCM authenticated encryption, guaranteeing both data secrecy and tamper-proof verification.
Authentication is gated through BiometricPrompt APIs cryptographically bound to hardware key invalidation if biometric enrollment is altered.
“By decomposing the codebase into a 20-module Gradle DAG and leveraging the Shizuku Binder IPC bridge, oorbE achieved elevated Android shell execution and hardware-backed AES-256-GCM cryptographic isolation without requiring root privileges or violating operating system boot integrity.”