Android Hexnode Assist Accessibility seems to turn off after reboot and remote view does not start immediatelySolved

That matches what I have seen on a few of our Android devices too. Right after boot, some background services are still starting, so the remote view can look like it is stuck or unavailable for a short while. Waiting a bit before launching the first unattended session usually avoids it.

Hi @arthur,

@casper is exactly right! After a reboot, the remote access service simply takes a short time to initialize before that first unattended remote view session can connect.

The important distinction here is whether the Accessibility permission is actually being disabled by the OS, or if the first session is just delayed. If you run into this, here is a quick checklist to verify:

1. Confirm that Hexnode Assist is installed on the affected devices.
2. Check that the policy assigned to the device has remote access management configured for unattended access.
3. Ensure the Accessibility permission for Hexnode Assist is enabled on the device.
4. After rebooting, wait a brief moment for the background services to start before launching the first remote view session.

As long as subsequent remote view sessions work without manually re-enabling Accessibility, the permission is intact and working as expected. Keeping the unattended remote access settings properly configured in your assigned Hexnode policy should prevent any recurring permission issues.

Please let me know if you ever find that the permission is actually being wiped after a reboot, as that would require some deeper troubleshooting!

Best regards,
Eden Pierce
Hexnode UEM