Samsung Android tablet won’t enter Hexnode kiosk mode after Generic Android enrollmentSolved

Participant
Discussion
3 weeks ago Jun 30, 2026

I’m setting up Samsung tablets as internet-connected kiosk devices with a custom app. Two tablets enrolled successfully in Hexnode, but kiosk mode would not activate properly. The devices showed a prompt in the Hexnode app saying the admin wanted to activate kiosk mode, but tapping Activate just returned to the launcher/home screen and the prompt stayed there.

Removing and reapplying the kiosk policy and restarting the tablets did not fix it. A similar Samsung tablet worked without any issue, so I initially suspected a model or Android build difference.

Is there anything specific about Android enrollment methods that affects kiosk mode activation in Hexnode?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Jun 30, 2026
Marked SolutionPending Review

Hi @douglas,

For Android devices, the enrollment method has a direct impact on how kiosk mode is enforced.

If the device is enrolled using the Generic Android method, Hexnode cannot silently enforce kiosk mode. The device user will be prompted inside the Hexnode app to manually activate kiosk mode.

If the device is enrolled using Android Enterprise – Device Owner mode, kiosk mode can be enforced silently without user intervention. This method also provides stronger device-level management and supports silent app installation and updates.

For dedicated kiosk tablets, the recommended approach is to factory reset the device and provision it using Android Enterprise enrollment, such as QR code enrollment from the initial device setup screen. This enrolls the device as Device Owner and allows Hexnode to apply kiosk restrictions reliably.

Regards,
Sienna Carter
Hexnode UEM

Save