Android kiosk: Mobile data in Peripheral Settings closes after a few secondsSolved

Hi @lila_ace,

Regarding Mobile data under Peripheral Settings, this behavior is expected on some Android device models. The Mobile data option may launch the native Android system Settings app in the background. Since the main system Settings app is blocked by the kiosk policy, the kiosk layer automatically closes it after a few seconds to maintain lockdown security.

Other options such as Wi-Fi, Bluetooth, or Location/GPS may remain open because they can run through quick-access controls within the secure kiosk layer without opening the full system Settings app.

For third-party app settings, Hexnode can restrict access to global device settings and control what is available in kiosk mode. However, blocking or hiding settings inside a specific third-party app depends on the app itself.

If the app supports AppConfig or managed app configuration, and exposes a configuration key to disable or restrict its internal settings page, that configuration can be pushed through Hexnode. If the app does not provide such AppConfig parameters, Hexnode cannot directly control individual screens or settings inside that app.

Best Regards,
Isabel Lora
Hexnode UEM

That explains why only Mobile data closes. I was confused because nothing showed up as blocked after scanning the device, so I thought it was a crash in Peripheral Settings.

I have seen the same behavior on a few Android models. Cellular settings often jump into the full Android Settings screen, while Wi-Fi and Bluetooth can be handled separately. If Settings is blocked in kiosk, the cellular page closes almost immediately.

Correct @gareyy. The absence of a blocked package entry does not necessarily mean the Peripheral Settings feature is failing. In this case, the Mobile data section is invoking the device’s native Settings interface, and the kiosk policy blocks that master Settings app.

The timeout cannot be extended or modified from Hexnode. It is part of how the kiosk lockdown is enforced on that device architecture.

The available options are:

1. Keep Mobile data inaccessible while the device is in strict kiosk mode.
2. Allow broader access to the native Settings app, if that is acceptable for the deployment.
3. Use device-side or carrier-side controls for mobile data management, if available.

Best Regards,
Isabel Lora
Hexnode UEM