Android kiosk screen stays on despite Screen Timeout in Hexnode

Executive Summary

Android devices in kiosk mode may ignore the configured Screen Timeout when the Kiosk Lockdown policy still contains an active Keep screen On command. This behavior is expected. Keep screen On acts as a master override for kiosk deployments where the display must remain awake continuously. Removing the command row clears the override and allows the timeout value configured under Android > Restrictions > Allow Device Functionality to take effect after the device checks in with Hexnode.

Issue

An Android kiosk device remains on indefinitely even though a screen timeout value, such as 3 minutes or 5 minutes, is configured in the policy.

This can occur when:

• The device is associated with a Kiosk policy.
• Keep screen On was enabled earlier in the Kiosk Lockdown policy.
• The Screen Timeout value is configured under Android > Restrictions > Allow Device Functionality.
• The Keep screen On checkbox appears unchecked, but the restriction is still present in the active policy configuration.

Cause

The Keep screen On setting in the Kiosk Lockdown policy is designed to keep the display awake indefinitely. When this command remains active in the policy configuration, it overrides standard Android screen timeout rules.

Note: This is expected behavior and not a bug. The Keep screen On setting functions as a master override in kiosk mode.

Resolution

Remove the Keep screen On command row from the Kiosk policy, verify the required Screen Timeout value, then save and sync the policy.

Step 1: Remove the Keep screen On command row

1. Open the Policies tab in the Hexnode UEM console.
2. Edit the Kiosk policy applied to the affected Android kiosk devices.
3. Go to Kiosk Lockdown > Android Kiosk Lockdown > Peripheral Settings > Display.
4. Locate the Keep screen On row under the display-related settings.
5. Uncheck the square next to the Keep screen On row to remove the command from the active policy configuration.

Step 2: Confirm the Screen Timeout value

1. In the same policy, go to Android > Restrictions > Basic.
2. Go to the Allow Device Functionality section.
3. Set Screen Timeout to the required duration, such as 3 minutes or 5 minutes.
4. Save the policy.

Step 3: Sync the device

1. Ensure the Android kiosk device is powered on and connected to the internet.
2. Allow the device to check in with Hexnode UEM.
3. If needed, open the Hexnode UEM/Hexnode for Work app on the device and use the sync icon to force a check-in.
4. Wait for the policy update to apply on the device.

Expected Result

After the Keep screen On option is disabled and the device syncs successfully, the Android kiosk device follows the configured Screen Timeout value and turns off the display after the specified duration.

If the screen still does not turn off

• Verify that the Keep screen On option is no longer enabled in the active Kiosk Lockdown policy configuration.
• Confirm that the policy containing the required Screen Timeout value is saved and assigned to the device.
• Check that the device has recently checked in with Hexnode.
• Keep the device powered on and connected to the internet while pending policy actions are applied.

Additional behavior to note

Note: If a passcode policy with an Auto-lock timer is also configured, the device uses the shorter duration between the Screen Timeout restriction and the Auto-lock timeframe.

Related Topics

1. Peripheral settings for Android devices locked in Kiosk mode
2. Set up Android device Restrictions