AndroidControl

AndroidControl is an Android toolbox for app operations, portrait display sessions, system rotation, privileged file access, and shell access. Its privileged backend is derived from Shizuku; the integrated operation controls bring AppOpsX functionality into the same app.

App name: AndroidControl · Package: org.androidcontrol.app · Minimum Android: 7.0 (API 24).

Download AndroidControl from this repository’s Releases or successful Actions builds. Upstream Shizuku downloads are a different application.

For the project brief, stable work-item cards, dated status and scoped evidence, see the project kanban.

• App operations: search installed apps, choose an Android user, group/filter by permission and find apps by operation, inspect access and rejection timestamps, and set package modes to Allow, Ignore, Deny, Default, or Foreground only (Android 10+). Each write is read back from Android.
• Backups: export a user’s package modes with stable operation names; import AndroidControl JSON or AppOpsX v1 .bak files with a target-user preview and per-operation failure reporting.
• New-app rules: optionally apply selected Ignore rules to newly installed apps for a chosen user. Rules exclude updates and AndroidControl itself and run while the privileged AppOps daemon is alive.
• Portrait sessions: edit the target package, open it on a portrait-shaped display, forward touches and web links, hide/restore the bottom controls using the arrow handle (the restore handle turns completely transparent after five seconds but remains tappable), and hand off to the normal phone display for external checkout screens.
• System rotation: control and restore system portrait behavior separately from target-specific sessions.
• Privileged tools: retain the manager, server, starter, shell, file provider, and Shizuku API for future extensions.

AppOps do not grant missing runtime permissions. Operations can share a switch and change together. AndroidControl changes package modes only and displays effective AppOps modes; UID-wide rules affecting several apps are preserved. See AppOps behavior and formats.

1. Install an AndroidControl APK from this repository.
2. Start its privileged server from the home screen. The always-available ADB settings shortcut opens Android Developer options for USB/wireless debugging. On Android 11+, wireless-debugging pairing can start it without a computer. Root and wired ADB startup options are also available.
3. Open Manage app operations, choose a user/app, and tap an operation’s mode or tick operations for a batch restriction. Default returns a package operation to Android’s default handling; the menu can reset all recorded package operations.
4. Use the separate portrait/session and system-rotation controls as needed. The saved portrait target does not limit AppOps app selection.

An ADB-started server needs restarting after reboot. Automatic new-app rules resume when AndroidControl reconnects its daemon; installs while it was stopped are not retroactively covered. Device/OS privileges can limit supported controls.

The previous fork used upstream Shizuku’s application ID. org.androidcontrol.app installs alongside that previous app and official Shizuku. Android keeps their settings and Keystore identities separate, so pair wireless debugging again in the new app. The old app’s data is retained; this is not an automatic settings or key migration.

AndroidControl has its own declared private permissions, native starter lookup, server process, and authorization file. Internal upstream Binder keys/namespaces remain where required by the backend. External clients must target AndroidControl’s identity/permissions to discover this fork; the rename does not redirect clients compiled for official Shizuku.

Use JDK 21, Android SDK platform/build tools 36, NDK 29.0.13113456, and CMake 3.31.x. The Gradle wrapper is included.

git clone --recurse-submodules https://github.com/c933103/AndroidControl.git
cd AndroidControl
./gradlew :manager:assembleDebug :manager:assembleDebugAndroidTest
bash tests/run-portrait-checks.sh

The APK is under manager/build/outputs/apk/debug/. Set ANDROID_HOME or sdk.dir in local.properties. Signing material stays outside Git; updates to the new package require the same signing certificate.

Android CI builds the app and exercises Android 13/15 package separation, pairing persistence within the new package, portrait lifecycle, AppOps read/write, backup validation, and user isolation.

The inherited Shizuku implementation is Apache-2.0. AppOpsX backup compatibility is adapted under MIT; see THIRD_PARTY_NOTICES.md. AndroidControl uses its own identity and launcher artwork and is an independently branded fork.