Android 13 remote connection delay after manual reboot with Fully Kiosk BrowserSolved

Hello @elena ,

This behavior can occur when Android background service initialization is delayed after a manual reboot, especially when a third-party kiosk app such as Fully Kiosk Browser takes foreground priority immediately after startup.

For unattended remote access to work reliably, both the Hexnode For Work app and Hexnode Assist must be able to start their background services, maintain network sockets, and display the remote streaming layer. Check the following settings on the device:

1. Battery usage: Set both Hexnode For Work and Hexnode Assist to Unrestricted under Android battery settings. This helps prevent Android from delaying background socket connections after reboot.
2. Display over other apps: Allow overlay permission for Hexnode Assist. This is required so the remote session interface is not suppressed by the kiosk app’s foreground layer.
3. Background data: Ensure background data usage is enabled for the Hexnode apps.
4. Autostart or auto-launch: If the device firmware includes an autostart or auto-launch permission manager, allow it for Hexnode For Work and Hexnode Assist.

A remote session cannot be established while the device is still powered off or not fully initialized. After a manual reboot, Android and Fully Kiosk Browser may take additional time before Hexnode services can reconnect and re-authenticate. Once the network connection and background services are fully restored, Remote View should work normally.

Regards,
Simon Scott
Hexnode UEM