Disabling hardware buttons (power + volume) on Samsung tablets via Esper Agent params — force-reboot and power-on edge cases remain

Android

When you disable hardware buttons on Samsung tablets using device policies, most button interactions are blocked. However, two hardware-level behaviors persist: a forced reboot triggered by holding Volume Down + Power for 10–15 seconds, and power-on when pressing the Power button on a device that is off and unplugged. This article explains what you can control and what limitations exist.

How to disable standard power and volume button interactions

You can successfully block standard power and volume button presses on Samsung tablets by applying device policy parameters through the Esper Console.

1. In the Esper Console, go to Blueprints → [Your Target Blueprint] → Esper Settings → Advanced Android Settings.
2. Add the following JSON to the Advanced Android Settings field:

   {
    "dpcParams": [
    {
    "key": "allowVolumeButtonAccess",
    "value": "false"
    },
    {
    "key": "allowPowerOff",
    "value": "false"
    }
    ]
   }

3. Click Save and Publish.
4. Apply the changes to your devices by going to Devices & Groups → [Device] → Actions → Reconverge.
5. Verify that short power button presses and volume button presses no longer trigger the power menu or volume UI.

Understanding hardware-level button limitations

Device policies control button behavior at the Android operating system level. However, two hardware functions operate at the bootloader or firmware level and cannot be blocked by device policies:

• Forced hardware reboot: Holding Volume Down + Power for 10–15 seconds triggers a forced reboot. This is a hardware-enforced function built into Samsung devices for crash recovery and operates below the Android OS.
• Cold power-on: Pressing the Power button on a device that is powered off and not connected to a charger boots the device. This is a fundamental hardware function that exists before the Android OS loads.

These limitations are not specific to Esper — they apply to any Android device management solution that uses standard Android Device Policy Manager (DPM) APIs.

Before you begin

• Ensure your target devices are online in the Esper Console.
• Verify that your Blueprint has successfully converged by checking Devices & Groups → [Device] → Blueprint Status.

If standard button presses are still not blocked

After applying the policy and triggering reconvergence, confirm that your device is online and the Blueprint has successfully applied. Check the Blueprint Status in the Esper Console to verify convergence.

If you need to block the forced reboot or cold power-on behaviors, these may require Samsung Knox APIs or OEM-level customization, which is outside the scope of standard device policies. In this case, contact Esper Support to discuss potential solutions.

Still need help?

If you have questions about disabling hardware buttons or need assistance with device policies, submit a support ticket.