Android single app kiosk opens webpage through wrong browserSolved

Hello @ethan_ ,

This usually happens when the Android kiosk policy has both Single App Kiosk settings and Launcher settings configured.

In Hexnode UEM, the Launcher setting is intended for Multi-App Kiosk mode. It creates a custom kiosk home screen with app icons and can optionally auto-launch an app after a delay. If an app is added under Launcher with an app auto-launch delay, the device may briefly show the Hexnode kiosk home screen or return to it when the app restarts, crashes, or when the home action is triggered.

For a true single-app kiosk experience:

1. Open the Android kiosk policy applied to the device.
2. Go to Kiosk Lockdown > Android Kiosk Lockdown > Launcher.
3. Remove the app configured there, especially if an App auto-launch delay is set.
4. Keep the required app or website configured only under the Single App Kiosk or Website Kiosk Settings, depending on your setup.
5. Save the policy.
6. Run the Scan device action from Manage > Devices > [select the Android device] > Actions > Scanning & Monitoring.

After the updated policy is applied, the device should stay in the single-app kiosk flow without showing the app selector or custom home screen.

Regards,
Simon Scott
Hexnode UEM

Okayy got it. I have one more thing to ask, these devices were enrolled using the Hexnode UEM Legacy app. Is that expected, or should Android kiosk devices use Hexnode For Work instead?

Hexnode supports two Android management approaches:

• Hexnode UEM – Legacy: Uses the older Android Device Administrator framework. This is commonly seen when a device is set up manually and the Hexnode app is installed like a regular app.
• Hexnode For Work: Uses Android Enterprise, which is the recommended framework for corporate-owned Android deployments.

For new corporate kiosk deployments, Android Enterprise enrollment is generally preferred because it provides stronger management capabilities and aligns with Google’s modern Android management model.

Migrating to Android Enterprise is not dependent on Hexnode licensing. The organization must be linked to Google Android Enterprise first. After that, devices can be enrolled using the Android Enterprise workflow instead of the legacy Device Administrator method.