How itsfitts/axmanager works
Project type and purpose
• This is a multi-module Android application (“Axeron Manager”) with three primary modules plus a static website:
• app – the Android UI and entry point
• engine – a core library providing IPC services, JNI/native execution, ADB and (optional) root logic
• shizuku-server – an embedded service to obtain elevated permissions via Shizuku APIs
• website – static documentation site for user guides and plugin docs
• Purpose: provide shell execution, plugin management and a WebUI for non-rooted and optionally rooted Android devices via ADB/Binder IPC.
File structure
• Top-level Gradle modules: app, engine, shizuku-server, website
• Android app module follows MVVM: data/ repository, ui/viewmodel, ui/screen, UI components, assets (js, shell scripts), JNI code under src/main/jni
• engine module: defines AIDL interfaces, client binder wrappers, core service implementations, managers, JNI/native helper for process startup, cgroup, SELinux, logging
• shizuku-server: Shizuku AIDL interfaces and service starter to bootstrap a system service for elevated permission
• website: VitePress documentation
README for architectural insights
• Highlights IPC-based permission handling via ADB/Binder (inspired by Shizuku)
• Describes plugin system, WebUI, optional root support
• Indicates use cases: shell executor, unrooted plugin modules, WebShell UI
a. Main components
• Android UI (app module): Activities, ViewModels, Compose/screens or XML layouts
• WebUI assets (axeron.js, kernelsu.js) hosted locally in the app and served by a mini-webserver or WebView
• engine service (engine module): bound via AIDL through AxeronService
• JNI/native layer: helper library loaded by engine to launch processes, manipulate cgroups, SELinux contexts, file I/O
• Shizuku server (shizuku-server module): system-level service for elevated Binder calls
• External: ADB daemon (USB/Wi-Fi debugging), optional su binary for root
b. Relationships and interactions
• UI ⇄ engine: the app binds to engine’s AIDL interfaces (IAxeronService, IFileService, IRuntimeService) via AxManagerProvider
• engine ⇄ Shizuku server: engine acts as a client invoking elevated calls through Shizuku’s IShizukuServiceConnection
• engine ⇄ JNI layer: engine calls native methods (starter.cpp, cgroup.cpp, selinux.cpp) to spawn processes, change permissions
• UI WebUI: WebView communicates with injected JS bridges (AxWebInterface, KsuWebInterface) which forward commands to the engine
• plugins: loaded dynamically by engine, registered via PluginService and PluginInfo data structures
c. Architectural patterns and design principles
• MVVM pattern in app (ViewModel → Repository → AIDL service)
• Service-oriented IPC: AIDL contracts separate interface from implementation
• Modularization: clear separation of UI, core engine logic and privilege escalation service
• Native boundary: JNI to handle low-level operations securely
d. Key technologies and frameworks
• Kotlin and Java for UI and engine code
• Android AIDL for IPC
• JNI/C++ for native process control
• Gradle/Kotlin DSL for build scripts
• Shizuku API for non-rooted elevated permissions
• Jetpack libraries (ViewModel, LiveData or Compose)
Details to capture
• All AIDL interfaces and their clients (IAxeronService, IFileService, IRuntimeService, plus plugin interfaces)
• JNI modules and native libraries loaded by engine
• Shizuku server’s service starter and its manager classes
• WebUI bridging components (AxPathHandler, AxWebInterface)
• Data flow for shell command execution:
UI → engine shell executor → native starter → process I/O → UI console or WebUI