What's new 
Some of our Android tablets are locked in kiosk mode and run a tracking app. After a few weeks or months, the app’s battery setting gets changed back automatically, so the app stops working in the background. The only way we have been fixing it is by exiting kiosk mode on each tablet and enabling the battery permission again manually. This is happening across a large fleet, so doing it one tablet at a time is causing delays. We also noticed that remote view sometimes works, but remote control does not always respond when trying to interact with the tablet from the portal. Is there a way to keep the app’s battery permission allowed permanently from Hexnode, or stop Android from changing it later?
22 Views
Replies (1)
Marked SolutionPending Review
Hexnode Expert
22 hours ago
Aug 17, 2026
Marked SolutionPending Review
Android battery optimization behavior is controlled by the Android operating system and, in many cases, by the device manufacturer’s battery management layer.
If an app does not natively request persistent background execution or exemption from battery optimization, Android may move it back into an optimized/restricted state over time. Hexnode can help manage kiosk mode and app deployment, but it cannot force a third-party app to permanently retain background battery access if the app or OS does not support that behavior.
For this scenario, check the following:
- Confirm whether the app itself requests unrestricted background activity or battery optimization exemption during setup.
- If the app does not expose this permission request, the long-term fix usually needs to come from the app vendor, such as adding support for persistent background execution.
- If the device has OEM-specific battery controls, verify whether the app is allowed to run in the background under those Android battery settings.
- For affected devices already in kiosk mode, the practical workaround is to temporarily exit kiosk mode, re-enable the app’s battery/background setting, and return the device to kiosk mode.
For the remote control issue, if remote view works but input control does not respond intermittently, it is often related to browser session cache, network quality, or device connectivity. Try opening the Hexnode portal in an incognito/private browser window or clearing the browser cache before starting a new remote control session.
Save