Android kiosk mode: setting minimum volume, blocking vibrate, and avoiding “Swipe to open” lock screenSolved

Android does not provide an MDM-level option to allow volume adjustment while enforcing a minimum volume threshold, such as 20%.

If the device must not go below a specific volume level, the recommended approach is to prevent users from changing the volume locally:

• Go to Policies > Kiosk Lockdown > Android Kiosk Lockdown > Peripheral Settings and enable Disable volume button.

After volume controls are disabled, set the required volume level from the Hexnode console so the device maintains a fixed volume.

For vibrate-only mode, Android’s native volume panel combines volume sliders, ringtone controls, and sound profile controls. If users can access the volume mixer, they can usually either reduce the volume to the lowest level or tap the ringtone/sound icon to switch to vibrate. Hexnode cannot selectively disable only that vibrate icon while still allowing the rest of the volume UI.

On Android 7 and later, Hexnode can restrict muting through the physical volume keys so the ring volume does not go all the way to zero. However, switching to vibrate from the software volume mixer can still bypass that behavior. Disabling volume buttons is the safer workaround when consistent sound output is required.

For the lock screen behavior, check the kiosk policy settings for Lock Task Mode: Policies > Kiosk Lockdown > Android Kiosk Lockdown > Peripheral Settings > Advanced Lock.

Make sure Lock task mode is enabled. Also check whether Activate Lock task mode on reboot while the device is locked is enabled. On some Samsung devices, if this is not enabled, the native Android lock screen may appear before the kiosk app takes over.

It is also worth checking whether the affected devices had any native lock screen configuration applied before kiosk mode was enforced. A stock swipe lock screen or previously configured secure lock can cause some devices to show the “Swipe to open” screen while others launch directly into kiosk.

That explains the volume part. So there’s no way to allow users to adjust volume but stop them from hitting vibrate through the icon in the Android volume popup?

Correct. If the Android volume mixer is available, the vibrate toggle in that native UI cannot be separated from the rest of the volume controls. The practical options are either:

• Allow volume changes and accept that users may be able to switch to vibrate from the mixer, or
• Disable volume controls in kiosk policy and manage the required volume level from Hexnode.

For environments where audible alerts are important, the second option is usually the more reliable setup.

For the lock screen issue, the Lock Task Mode settings were already enabled in the policy. We haven’t had new reports from the site since the initial deployment, so it may have stabilized after enrollment/policy application. Keeping an eye on it for now.

If the settings are already enabled and the issue is no longer reproducible, no further change may be needed. During or shortly after enrollment, behavior can differ if the kiosk policy, Lock Task Mode, or native lock screen state has not fully settled on every device yet.

If it happens again, compare one affected device with one working device for the following:

• Lock task mode is enabled in the assigned kiosk policy.
• Activate Lock task mode on reboot while the device is locked is enabled.
• No native Android secure lock or swipe-only lock screen was manually configured before kiosk mode.
• The same kiosk policy version is applied to both devices.

Once Lock Task Mode is consistently active, kiosk devices should normally wake directly into the kiosk environment instead of stopping at the Android “Swipe to open” screen.