• Persistent reminder notifications
• Auto-restores dismissed reminders
• Rich Markdown note editor
• Nested checklists & subtasks
• One-time & recurring reminders
• Attach files and images
• Search, labels & organization
• Material Design 3 interface
• Dynamic Material You colors
• Completely Free & Open Source
• Auto-restores dismissed reminders
• Rich Markdown note editor
• Nested checklists & subtasks
• One-time & recurring reminders
• Attach files and images
• Search, labels & organization
• Material Design 3 interface
• Dynamic Material You colors
• Completely Free & Open Source
❤2
Features of shevery:
• Jetpack Compose manager UI with Material 3 Expressive components, motion, switches, and rounded icon treatment.
• Dhizuku Experimental Support: Dedicated Device-Owner bridging system available inside Laboratory features.
• Better shell/adb based "Comput" feature with Gemini Explaination.
• Android 16/17 target work with current preview SDK/build tooling in this fork.
• ADB Modules screen for installing and managing ZIP modules.
• Module features: module.prop, banner, enable/disable switch, action.sh, policy-gated service.sh, local WebUI, delete, path checks, size limits, output limits, and last-run logs.
• Module policy settings: Safe mode, Full access, and background action control.
• Debug test module under test-modules/adb-test-module.zip.
• [ADB Modules guide](docs/adb-modules-guide.md)
• [ADB Modules API reference](docs/adb-modules-api.md)
• [Shizuku Connectors API](docs/shizuku-connectors.md)
• [Android 17 Compatibility](docs/android-17-compatibility.md)
• Extremely slow (Multiple process creation)
• Needs to process texts (Super unreliable)
• The possibility is limited to available commands
• Even if ADB has sufficient permissions, the app requires root privileges to run
📸 Click to open Screenshot Gallery
• ADB permissions are limited
• Hidden API limitation from Android 9
• Android 8.0 & ADB
• Direct use of transactRemote requires attention
• The API may be different under different Android versions, please be sure to check it carefully. Also, the android.app.IActivityManager has the aidl form in API 26 and later, and android.app.IActivityManager$Stub exists only on API 26.
• SystemServiceHelper.getTransactionCode may not get the correct transaction code, such as android.content.pm.IPackageManager$Stub.TRANSACTION_getInstalledPackages does not exist on API 25 and there is android.content.pm.IPackageManager$Stub.TRANSACTION_getInstalledPackages_47 (this situation has been dealt with, but it is not excluded that there may be other circumstances). This problem is not encountered with the ShizukuBinderWrapper method.
• Clone with git clone --recurse-submodules
• Run gradle task :manager:assembleDebug or :manager:assembleRelease
• You are FORBIDDEN to use manager/src/main/res/mipmap*/ic_launcher*.png image files, unless for displaying Shizuku itself.
• You are FORBIDDEN to use Shizuku as app name or use moe.shizuku.privileged.api as application id or declare moe.shizuku.manager.permission.* permission.
• [Nightzuku](https://github.com/kerneldroid/Nightzuku) - for parts of App UI and Android 17 support.
• [Shizuku](https://github.com/rikkaapps/Shizuku) - for Shizuku API and main sources.
• Jetpack Compose manager UI with Material 3 Expressive components, motion, switches, and rounded icon treatment.
• Dhizuku Experimental Support: Dedicated Device-Owner bridging system available inside Laboratory features.
• Better shell/adb based "Comput" feature with Gemini Explaination.
• Android 16/17 target work with current preview SDK/build tooling in this fork.
• ADB Modules screen for installing and managing ZIP modules.
• Module features: module.prop, banner, enable/disable switch, action.sh, policy-gated service.sh, local WebUI, delete, path checks, size limits, output limits, and last-run logs.
• Module policy settings: Safe mode, Full access, and background action control.
• Debug test module under test-modules/adb-test-module.zip.
• [ADB Modules guide](docs/adb-modules-guide.md)
• [ADB Modules API reference](docs/adb-modules-api.md)
• [Shizuku Connectors API](docs/shizuku-connectors.md)
• [Android 17 Compatibility](docs/android-17-compatibility.md)
• Extremely slow (Multiple process creation)
• Needs to process texts (Super unreliable)
• The possibility is limited to available commands
• Even if ADB has sufficient permissions, the app requires root privileges to run
📸 Click to open Screenshot Gallery
• ADB permissions are limited
• Hidden API limitation from Android 9
• Android 8.0 & ADB
• Direct use of transactRemote requires attention
• The API may be different under different Android versions, please be sure to check it carefully. Also, the android.app.IActivityManager has the aidl form in API 26 and later, and android.app.IActivityManager$Stub exists only on API 26.
• SystemServiceHelper.getTransactionCode may not get the correct transaction code, such as android.content.pm.IPackageManager$Stub.TRANSACTION_getInstalledPackages does not exist on API 25 and there is android.content.pm.IPackageManager$Stub.TRANSACTION_getInstalledPackages_47 (this situation has been dealt with, but it is not excluded that there may be other circumstances). This problem is not encountered with the ShizukuBinderWrapper method.
• Clone with git clone --recurse-submodules
• Run gradle task :manager:assembleDebug or :manager:assembleRelease
• You are FORBIDDEN to use manager/src/main/res/mipmap*/ic_launcher*.png image files, unless for displaying Shizuku itself.
• You are FORBIDDEN to use Shizuku as app name or use moe.shizuku.privileged.api as application id or declare moe.shizuku.manager.permission.* permission.
• [Nightzuku](https://github.com/kerneldroid/Nightzuku) - for parts of App UI and Android 17 support.
• [Shizuku](https://github.com/rikkaapps/Shizuku) - for Shizuku API and main sources.