Intents

Intents

Reference of the public (and internal) intents declared by Shevery Manager. Package name: com.hamondev.shevery.

Server control (internal)

Receiver: moe.shizuku.manager.receiver.SheveryControlReceiver (exported=false).

Action	Effect
moe.shizuku.manager.action.START_SERVER	Clears the user-stop request; if last launch mode was ADB, enqueues AdbStartWorker and refreshes the notification; calls WatchdogManager.attemptRestart()
moe.shizuku.manager.action.STOP_SERVER	goAsync() + WatchdogManager.stopServerAndWait(userInitiated=true), then refreshes the notification

Because the receiver is not exported, only Shevery itself (notification buttons, AdbStartWorker, and the bundled Tasker Plugin) can send these. Third-party apps: use the public automation actions below instead of crafting these broadcasts.

// inside Shevery (same UID) — explicit + package-scoped
val intent = Intent("moe.shizuku.manager.action.START_SERVER").apply {
    setPackage("com.hamondev.shevery")
    component = ComponentName(
        "com.hamondev.shevery",
        "moe.shizuku.manager.receiver.SheveryControlReceiver"
    )
}
context.sendBroadcast(intent)

adb shell am broadcast with these internal actions will not work from the shell because SheveryControlReceiver is not exported. For shell/ADB or third-party automation, use the public broadcast actions below.

Public automation control (Tasker, MacroDroid, ADB)

Receiver: com.hamondev.shevery.tasker.PluginReceiver (exported=true).

Action	Effect
com.hamondev.shevery.action.START_SERVER	Starts Shevery server (clears stop flag, wakes watchdog)
com.hamondev.shevery.action.STOP_SERVER	Gracefully stops the server
com.hamondev.shevery.action.RESTART_SERVER	Restarts server with graceful binder death monitor
com.hamondev.shevery.action.TOGGLE_SERVER	Toggles server (stops if alive, starts if stopped)

Example shell usage:

adb shell am broadcast -a com.hamondev.shevery.action.START_SERVER -p com.hamondev.shevery -e auth <token>

Requirement: third-party automation broadcasts and the Tasker plugin require Shevery Connectors to be enabled in Settings → Automation (shizuku_connector_enabled). With connectors off, every incoming action is rejected before it reaches the server.

Authentication token: direct broadcasts must carry the secret auth token as the auth extra (-e auth <token>). The token lives in Settings → Automation → Extras (Auth Token) and in the Home screen View intents sheet. A missing or wrong token is rejected with RESULT_CANCELED.

Detailed guide: Tasker & MacroDroid Automation Guide.

App update status (internal)

• Action: moe.shizuku.manager.action.APP_UPDATE_INSTALL_STATUS
• Sent by PackageInstaller to AppUpdateInstaller (setPackage(context.packageName)), consumed with an explicit IntentFilter. Not for external use.

Public API for third-party apps

Request permission (runtime dialog)

Launches RequestPermissionActivity (exported=true, requires android.permission.INTERACT_ACROSS_USERS_FULL):

• com.hamondev.shevery.intent.action.REQUEST_PERMISSION
• moe.shizuku.privileged.api.intent.action.REQUEST_PERMISSION (legacy alias)

Always add category android.intent.category.DEFAULT. This is the ShizukuService#requestPermission() flow — user taps Allow/Deny, decision is stored as FLAG_ALLOWED / FLAG_DENIED.

Legacy authorization

• com.hamondev.shevery.intent.action.REQUEST_AUTHORIZATION
• moe.shizuku.privileged.api.intent.action.REQUEST_AUTHORIZATION

→ LegacyIsNotSupportedActivity (guarded by moe.shizuku.manager.permission.API). Old Shizuku API clients only.

Binder request (shell / legacy)

• rikka.shizuku.intent.action.REQUEST_BINDER → ShellRequestHandlerActivity and ShizukuReceiver (exported=true, directBootAware=true)
• Aliases also handled by ShizukuReceiver: com.hamondev.shevery.intent.action.REQUEST_BINDER, moe.shizuku.privileged.api.intent.action.REQUEST_BINDER

Used by the rish / shell path (ShellBinderRequestHandler, ShizukuReceiverStarter). See How it works and Shizuku Connectors.

Binder delivery

• moe.shizuku.api.action.BINDER_RECEIVED (broadcast by ShizukuProvider, extra moe.shizuku.privileged.api.intent.extra.BINDER) — how API clients receive the binder. Permission moe.shizuku.manager.permission.API_V23.

Accessibility manager shortcut

• com.hamondev.shevery.action.ACCESSIBILITY_MANAGER (+ DEFAULT category) → AccessibilityManagerActivity (exported=true). Lists system accessibility services, enable/disable/pin via WRITE_SECURE_SETTINGS.

Quick examples

# open the accessibility manager
adb shell am start -a com.hamondev.shevery.action.ACCESSIBILITY_MANAGER

# legacy permission request (reproduces the API dialog path)
adb shell am start -a com.hamondev.shevery.intent.action.REQUEST_PERMISSION

# start the server from Termux / a PC shell (needs connectors + auth token)
adb shell am broadcast -a com.hamondev.shevery.action.START_SERVER -p com.hamondev.shevery -e auth <token>

Source of truth: manager/src/main/AndroidManifest.xml, manager/.../receiver/SheveryControlReceiver.kt, tasker/.../PluginContract.kt, tasker/.../PluginReceiver.kt. Repo mirrors of this page: docs/intents.md.