Disabling physical volume and power buttons via Esper Agent JSON params: works on Lenovo CSDK and Samsung Knox, not supported on SUNMI devices

Android

Title: Physical button disable not working — check device SDK compatibility

When you configure a Blueprint to disable the volume and power buttons on managed devices, the Blueprint converges successfully but the buttons remain fully functional on certain devices.

Why this happens

Disabling physical buttons requires manufacturer-level SDK support on the device. Esper passes the disable parameters to the device, but only Lenovo devices (via Lenovo CSDK) and Samsung devices (via Samsung Knox) have the underlying SDK to act on them. On all other OEMs — including SUNMI, Zebra, and Honeywell — the parameters are silently accepted during convergence and then ignored. No error is surfaced in the Console.

Before you begin

Confirm your device OEM before proceeding:

Supported: Lenovo (Lenovo CSDK), Samsung (Samsung Knox with active Knox license)
Not supported: SUNMI, Zebra, Honeywell, and all other OEMs without explicit SDK integration

To identify your device OEM, go to Devices & Groups → [Device Name] → Device Info and check the Model field.

How to disable volume and power buttons

Open the Esper Console and navigate to Endpoint Management → Blueprints → [Blueprint Name].
Click Advanced Android Settings.
Locate the Esper Agent Params / Additional Settings JSON field and enter the following. Both keys can be included together; remove either key if you want to leave that button functional.
```
{
  "dpcParams": [
    {
      "key": "allowVolumeButtonAccess",
      "value": "false"
    },
    {
      "key": "allowPowerOff",
      "value": "false"
    }
  ]
}
```
Click Save and Publish to push the updated blueprint.
Navigate to Devices & Groups, select the target device or group, and trigger a Blueprint Converge. This pushes the updated configuration immediately rather than waiting for the next scheduled convergence window.
Once convergence completes, physically press the volume up, volume down, and power buttons on the device to confirm they produce no response.

Verify: On a supported device, pressing the volume or power buttons produces no visible or audible response within 1–2 minutes of convergence completing. On Samsung devices, also confirm that Knox is active — navigate to Devices & Groups → [Device Name] → Device Info and check that Knox enrollment status is shown as active. Without a valid Knox entitlement, Knox-specific parameters are silently ignored even on Samsung hardware.

If this doesn't resolve it

Work through the following checks before contacting support:

Lenovo devices: Confirm the device is running CSDK-capable firmware. Older Lenovo models may not support these parameters. Collect Esper Agent logs by running the following command and search the output for allowVolumeButtonAccess to confirm the parameter was received:
```
adb shell dpc_logs
```
Samsung devices: Confirm Knox is active and enrolled with a valid license. Collect Esper Agent logs using the command above and search for allowPowerOff to verify the parameter was processed.
SUNMI or other unsupported OEMs: Button disabling is not supported on these devices. The Blueprint will converge without error, but the buttons will not be disabled. This behavior is expected and cannot be resolved through configuration changes.

If buttons remain active on a confirmed Lenovo or Samsung device after following all steps above, contact Esper Support with the following information: device model and firmware version, Esper Agent version (found at Devices & Groups → [Device Name] → Device Info), Knox enrollment status (Samsung only), and the Esper Agent log output from adb shell dpc_logs.

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.