Android kiosk day mode did not resume because tablet was offlineSolved

Participant
Discussion
3 weeks ago Aug 26, 2026

I’m testing Android tablets in Single Website Kiosk mode for a sealed wall-mounted setup. The kiosk is locked to a web app and we configured an automation to switch into a low-brightness night mode in the evening, then return to day mode in the morning.

The tablet entered night mode at the scheduled time, but the next morning it was still in night mode even after the day schedule should have started. It also looked like the brightness was still stuck at the night value.

After checking the device, I noticed Wi-Fi had been turned off. Once Wi-Fi was enabled again, the tablet moved into day mode. Is network connectivity required for the scheduled day/night change to apply in Android kiosk? Also, is there anything specific to watch out for when controlling brightness on Android kiosk tablets?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Aug 26, 2026
Marked SolutionPending Review

Hi @sybylla,

Scheduled kiosk changes and automation-based actions require the device to receive the command from the Hexnode server. If the Android tablet is offline when the scheduled day-mode action is triggered, it may remain in the previous state until the device reconnects and checks in.

For sealed or unattended kiosk deployments, make sure that:

  1. Wi-Fi remains enabled and the network is available during the scheduled transition window.
  2. The kiosk policy does not allow users or the web app flow to disable Wi-Fi.
  3. The device can reach the Hexnode server after reboot, battery drain, or network interruption.
  4. The day and night automations are configured with enough time between actions so the device has time to check in and apply the change.

In your case, since the tablet switched to day mode after Wi-Fi was restored, the schedule itself appears to be working. The missed transition was caused by the tablet being offline at the time the action was expected to apply.

Brightness behavior can vary by Android version and OEM implementation. Hexnode can push brightness-related configurations, but some device firmware builds may override or ignore MDM brightness payloads, especially when battery saver, adaptive brightness, or vendor-specific power management is active.

For Android kiosk tablets, check the following first:

  1. Disable Battery Saver or any OEM power-saving mode on the device.
  2. Disable adaptive brightness or automatic brightness if available through policy or device settings.
  3. Test whether the brightness value changes when the device is online and outside the night schedule.
  4. Confirm whether the issue occurs only on a specific model or firmware version.

If the device remains at the old brightness value even after the automation changes mode and the tablet is online, it is likely a device/OEM compatibility issue rather than a kiosk configuration issue. In that case, validate the brightness behavior on the exact tablet model and Android build before installing the devices in sealed locations.

Regards,
Sienna Carter
Hexnode UEM

Save