Hello team, I have an issue with two Android devices that are stuck in kiosk mode. Both devices indicate that the Wi‑Fi is active and that there is internet connectivity, but they do not respond to the disenroll command that is pushed from the Hexnode console.
The odd part is that the last check‑in timestamp shows 23 days ago, which is in direct contradiction to the fact that the devices are obviously online and working.
Has anyone come across this inconsistency before?
50 Views
@laura123 Interesting. In case the devices are online but not checking in, would that be the reason for the kiosk exit prompt not showing up? Or is there a way to get the kiosk exit screen?
@amelia Yes, that was my thought as well. I’ve tried various times to send the command to disenroll the device, but the kiosk screen is still there, showing that its locked. If there is a possibility to really think of the exit prompt, it might be the way to solve this by unlocking the kiosk directly.
Hi @laura123 and @amelia , thanks for reaching out!
If the device is stuck in kiosk mode and not responding to disenroll commands, please try the following steps:
If the device doesn’t exit the kiosk mode even after the password has been entered, it might not be sending the signal to the server properly. So, please make sure:
Regards,
Simon Scott,
Hexnode UEM
Just tried tapping the screen 10 times; the exit prompt finally appeared. I typed in the password from Global Exit Settings, and the device was able to be released from kiosk mode. The agent then reconnected, and the disenroll command was finally executed.
Thanks, @simon_scott !
It’s better to be aware of the 10-tap gesture and exit password method. I didn’t know this at all.
Thank you @simon_scott for the hint!
Great to hear that the issue is resolved!
In case someone else encounters a kiosk lock or check‑in mismatch issues, you can try the above steps. And like always, if you need more support, contact us; we’re ready to assist.
Don't have an account? Sign up
