Remote View has stopped working on multiple Android phones. It stays stuck on “Connecting” and never opens the screen. This used to work without anyone touching the phone, but now I’m not sure if someone has to accept a prompt on the device. We need unattended remote view because the phones are not always near a user.
- Home
- Remote Actions
- Android Remote View stuck on Connecting for unattended access
Android Remote View stuck on Connecting for unattended accessSolved
Replies (4)
Hi @hugo_l , For unattended Remote View on Android, make sure the devices have a Remote Access Management policy associated.
This policy is required when you want remote access actions to proceed without a user accepting permission prompts on the device. If remote access worked earlier, it may have been because the permission prompt was accepted manually at some point. That permission can remain active for a while, but it may reset after an OS update, app update, or a long interval.
After configuring the policy, check whether the policy association is successful from the device action history. Then try Remote View again on an active Android device with a stable internet connection.
Also, the option “Silently download files from the device” applies to File Explorer access. If enabled, admins can browse and download files from the device without a permission prompt from the end user.
Regards,
isabel Lora
Hexnode UEM
I associated the Remote Access Management policy and the action history shows it was applied successfully. Remote View is still stuck at “Connecting” on more than one Android phone though.
If the policy is associated but Remote View still stays on “Connecting,” the next thing to isolate is the network. Try connecting one affected Android device to a different network, such as a mobile hotspot, and start Remote View again.
If it works over the hotspot, the issue is not with the policy. It usually points to a network restriction, firewall rule, proxy filtering, or connectivity problem on the original Wi-Fi or site network that is preventing the remote session from being established.
Regards,
Isabel Lora
Hexnode UEM
Testing with a mobile hotspot worked. Looks like the original network at the device location was blocking or delaying the Remote View connection.