Exit Android kiosk mode locally using the Hexnode exit passcodeSolved

Yes @melora. Android kiosk mode can be exited locally from the device using the kiosk exit passcode.

For Hexnode Android kiosk, the default local exit gesture is to tap any vacant area of the device screen 10 times in quick succession. This opens a prompt where you can enter the kiosk exit passcode.

The exact behavior depends on the kiosk type:

• Single-App Kiosk: Reboot the device first. When the device reaches the home screen, tap the screen 10 times quickly before the kiosk app auto-launches. Then enter the exit passcode.
• Multi-App Kiosk: Tap any vacant area on the kiosk home screen 10 times quickly. Then enter the exit passcode.

You can find the kiosk exit passcode in either of these locations in the Hexnode portal:

• Global exit passcode: Admin > General Settings > Global Exit Settings.
• Policy-specific exit passcode: Policies > select the kiosk policy > Manage > Modify > Android Kiosk Lockdown > Kiosk Exit Settings.

If an exit passcode is configured inside the kiosk policy, it overrides the global exit passcode.

Best Regards,
Isabel Lora
Hexnode UEM

When you say “tap the specified number of times,” is that configurable or always 10 taps? I couldn’t find a setting for the number of taps.

By default, the gesture is 10 taps in quick succession. After the 10 taps, the device should display the exit passcode prompt.

The important part is where you perform the gesture:

• In multi-app kiosk, do it on the kiosk launcher/home screen.
• In single-app kiosk, reboot first and perform the taps on the home screen before the single kiosk app launches again.

This local exit method is useful when the device is offline or cannot receive remote actions due to a Wi-Fi change, because it does not require the device to be connected to the Hexnode portal at that moment. You only need physical access to the device and the correct kiosk exit passcode.

Best Regards,
Isabel Lora
Hexnode UEM

The policy-specific passcode override is good to know. I was checking the global passcode and wondering why it didn’t work on one of our tablets. Turns out that device had a different kiosk policy assigned.

That is expected behavior @sutton. When both passcodes exist, Hexnode gives priority to the passcode configured in the assigned kiosk policy. For consistency across multiple kiosk deployments, either use the global passcode everywhere or document the policy-specific passcodes for each kiosk policy.

Best Regards,
Isabel Lora
Hexnode UEM