Remote Control unavailable on existing Blueprint — enable via Supervisor Plugin

Android

When a device is enrolled under an existing Blueprint and Remote Control is not working, enabling the feature normally requires modifying that Blueprint to expose Android Accessibility settings — a change that can affect every device sharing that Blueprint. The Supervisor Plugin method grants the required Accessibility permission at the system level, enabling Remote Control on individual devices without touching the shared Blueprint.

Why this happens

Esper Remote Control requires that the Esper Management Service holds Android Accessibility permission on the device. In a standard setup, this permission is granted through Blueprint settings. When those settings cannot be safely changed — because the Blueprint is shared across production devices, or because you are running Esper Agent 7.4 or earlier — the Supervisor Plugin provides an alternative path that operates entirely at the system level.

Before you begin

Confirm the device model identifier before contacting Esper Support. The request cannot be fulfilled without it.
Esper Agent 9.4 or later is required to display Supervisor Plugin status in the Esper Console. On earlier versions, the plugin may install successfully but will not appear as active until the agent is updated.
A pre-signed Supervisor Plugin must exist for your specific device model. If none exists, your OEM must sign the plugin before it can be installed. Esper Support will confirm availability when you request the plugin.

Steps

Find the exact device model identifier. In the Esper Console, navigate to Devices & Groups → [Device Name] → Device Details → Hardware and record the model identifier exactly as shown (for example, rk3566_r). An incorrect or partial model string will delay the request.
Request the Supervisor Plugin from Esper Support. Contact Esper Support and provide the model identifier from Step 1. Esper Support will check whether a pre-signed build exists for your model:
- Signed build exists: Esper Support uploads the plugin directly to your tenant. No further action is required from you — proceed to Step 3.
- No signed build exists: Esper Support provides an unsigned APK. Submit this APK to your OEM for signing with their platform keys, then return the signed APK to Esper Support for upload to your tenant.
Bring the target devices online. Once Esper Support confirms the plugin has been uploaded to your tenant, ensure the affected devices are powered on and connected. The plugin installs automatically — no manual installation is needed. Allow up to 40 minutes after the device comes online, or reboot the device to trigger immediate installation.
Update Esper Agent to version 9.4 or later. Navigate to Esper Software Updates in the Esper Console and deploy the latest agent version to the affected devices. This step is required to display plugin status in the Console; it does not affect whether the plugin installs.
Confirm the plugin is active. In the Esper Console, navigate to Devices & Groups → [Device Name] → Overview → Software → Active Plugins and verify that Supervisor Plugin appears in the list. The plugin does not appear as a user-visible app on the device — it installs silently as a system-level component and will not be visible to the end user.

Verify: After the Supervisor Plugin appears under Active Plugins, initiate a Remote Control session from Devices & Groups → [Device Name] → Remote Control. The session should connect without prompting the user to grant Accessibility permission manually. Plugin status should reflect as active immediately once Esper Agent 9.4 or later is running.

If this doesn't resolve it

If the plugin does not appear after 40 minutes and a reboot, or Remote Control still fails after the plugin shows as active, collect the following before contacting Esper Support:

The exact device model identifier from Device Details → Hardware
The current Esper Agent version from Device Details → Software → Esper Agent Version
A screenshot of Overview → Software → Active Plugins showing the current state
The device Activity Feed from the time of the last reboot, exported from Devices & Groups → [Device Name] → Activity Feed

Contact Esper Support with the above information. If your device model required OEM signing, confirm with your OEM that the APK was signed with platform keys and not application keys, as the plugin will silently fail to install if signed incorrectly.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.