Android remote view/control taking too long or not connectingSolved

Hello,

Thanks for reaching out to Hexnode Connect.

For Android Remote View/Control and other remote actions to execute reliably, the device must be actively communicating and syncing with the Hexnode portal. Even if the device has a stable internet connection and plenty of battery, a stale check-in or a throttled background process can severely delay commands such as remote view, kiosk exits, or device resets.

Since unattended remote access is already configured and working on one of your tablets, your policy setup is likely correct. For the devices experiencing delays, the critical factor is whether they are successfully checking in with the server.

Please try the following steps:

1. Open the device details page in your Hexnode portal and verify the device’s last check-in time.
2. If the last check-in is not current, initiate a Scan Device action.
3. Wait to see if the check-in time properly updates to the current time.
4. If it updates, stop any pending remote session attempts and start a fresh Remote View/Control session.

If the check-in time still does not update after the scan, or if the commands continue to hang, the device’s management agent or Android’s OS task scheduling might be stuck. In this scenario, restarting the affected Android device is the best possible solution.

A physical reboot forces the background processes to reinitialize and re-establishes a fresh communication channel with the Hexnode server. Once the device boots back up, run the Scan Device action again, and your remote sessions and queued commands should begin responding normally.

I hope this helps. If you find any more issues or need further assistance feel free to reach out.

Best regards,
George,
Hexnode UEM