Settings

Settings

The settings hub lists eleven sections, each opening its own screen: Application, Appearance, Security, Device Owner, Modules, Updates, AI, Backups, Automation, Extras, About. When Require authentication is enabled, opening Security and Device Owner first asks for biometric/device-credential confirmation.

Application — startup and service

Startup

• Start on boot via Root — starts Shevery with root privileges on boot (only offered when the device is rooted; re-checked on every resume).
• Start on boot via Wireless debugging — briefly enables wireless debugging on boot and starts Shevery over ADB (TCP port 5555). No root, Wi-Fi is needed only for a moment.
• TCP Mode — restart ADB startup onto TCP port 5555 so Shevery can reconnect without depending on the changing Wireless Debugging port. Changing it restarts the service.
• Re-assert wireless debugging — off by default. Restores the wireless-debugging flag if the ROM cleared it (at ADB start and Wi-Fi reconnect); never turns it off.
• Auto-disable USB debugging — turns USB debugging off after reboot when Shevery is not configured to start on boot.

Service maintenance

• ErrorProtect (Watchdog) — on by default. Checks process health and transactional errors every 10 seconds and automatically stops/restarts Shevery when problems are found. Disable only if you manage the lifecycle yourself.
• Notify on Service Stop — notification when the service stops unexpectedly (always shown while ErrorProtect is on).

Other

• Dhizuku Mode — allow Shevery to operate by binding to Dhizuku (warning dialog on enable). See Dhizuku.
• Compatibility Stubs — manage Shizuku and Dhizuku bridge stubs for legacy applications.

Appearance

Language, night/dark theme (including a pure black night theme), use system theme color, and the classic navigation bar (fixed bottom bar instead of the floating pill).

Security

• Require authentication — protect Shevery with fingerprint, face unlock or device credential (BiometricPrompt, strong biometric or device credential).
• Session timeout — Immediately / 1 min / 5 min / 15 min / 30 min / 1 hour. Applied when the app returns from the background; an expired session re-locks the app and drops grants made in the previous session.
• Protected Actions — each action can require its own confirmation: Unlock on app launch, Device Owner settings & transfer, Managing app permissions, Starting and stopping server, Installing or removing stubs.
• With authentication on, the app shows a Shevery is locked screen until unlocked.

Device Owner

Device ownership, app delegation and system privileges. Opens the Device Owner management screen with Transfer and Delegation subpages (guarded by the Device Owner settings protected action). See Dhizuku for the bridge that supplies Device Owner on devices where Dhizuku holds it.

Modules

• Module access mode — SAFE / CUSTOM / FULL, see Security policy.
• Custom permissions — configure every module permission separately.
• Allow background actions — permit installed modules to request background ADB work in full access mode.
• ReCommand for WebUI / ReCommand for Action — confirmation dialog before WebUI shell exec / before action.sh.

Updates

• Module Updates → subpage with the catalog toggle (modules discovered from GitHub Topics), check frequency (Daily / Weekly / Manual), install mode (build from sources vs release ZIP) and an optional GitHub PAT (raises the API rate limit from 60 requests/hour).
• App update group — channel (Stable = releases, Beta = pre-releases), auto-check, frequency (Daily ≈ every 20 h / Weekly / Manual) and manual Check / Download / Install. Details: Updates.

AI

• AI provider → opens the provider manager (list / set active / add / delete, keys encrypted in the AndroidKeyStore). See Commandium.
• ReCommand for Comput — confirmation dialog before running AI-generated or risky commands in Comput terminal.

Backups

Exports a ZIP of preferences, app authorizations and modules, and restores one on a new install — the easiest way to migrate to another device.

Automation

The hub for Tasker Plugin and Intents control:

• Shevery Connectors toggle (with a warning dialog when enabling) — gates both the connector provider and all incoming plugin/broadcast actions.
• Authentication & Security — the secret auth token (tap to copy) and Regenerate token; regenerating invalidates every configured Tasker/MacroDroid intent.
• Tasker & MacroDroid — the four broadcast actions, target package, receiver component and the ready-made am broadcast … -e auth <token> shell command, all tap-to-copy.

Extras

Experimental and diagnostic rows: AI explanations for failed commands, verbose logging, notify on recovery, auto-refresh on resume, Restart Service Now, Dismiss Update Banner, Revoke Trusted Modules (drops all per-module trust grants) and the Accessibility manager (list, enable/disable/pin system accessibility services via WRITE_SECURE_SETTINGS).

About

Version info, changelog shortcut, licenses, links and contributors → About screen.