OS updates not applying automatically on enrolled devices: understand OEM-controlled update behavior and verify Blueprint OS policy

Android

When an Esper Blueprint is configured for automatic OS updates, enrolled devices may still remain on their current OS version with no update activity, even after the policy has been applied.

Why this happens

Esper's OS Update policy controls how a device behaves when an update is available — it does not source, host, or deliver OS packages. The actual update file comes entirely from your device manufacturer's (OEM's) update servers. If the OEM has not released a new OS version for your specific device model, or if the device does not meet the OEM's preconditions (battery level, network type, idle state), no update will occur regardless of your Blueprint configuration.

Steps

1. Confirm the OS Update policy in your Blueprint.
   In the Esper Console, navigate to Blueprints → [Blueprint Name] → Device Settings → System Updates and verify the policy is set to Update Automatically (or your intended update mode). Then confirm that this blueprint is the one actively applied to the affected devices or group — a device inherits only the Blueprint currently assigned to it.
2. Record the current OS version on the affected devices.
   Navigate to Devices & Groups → [Device Name] → Device Info and note the OS Version and Security Patch Level for each affected device. This gives you a baseline to compare against the OEM's latest published firmware.
3. Check whether the OEM has released an update for your device model.
   Visit your device manufacturer's firmware release portal or contact their support team (for example, Zebra, Honeywell, or Datalogic each publish release notes by device model). Confirm that a newer OS version exists for your exact model and that it is distributed through standard Android update channels. Some OEMs use proprietary firmware delivery mechanisms that operate independently of standard Android update infrastructure — if this applies to your devices, your OEM can advise on the required configuration.
4. Manually trigger an update check directly on the device.
   On the device, go to Settings → About Device → System Update (the exact path varies by OEM) and tap Check for Updates. This forces the device to contact the OEM's update server directly and confirms whether the device can reach it and whether an update is available. If this check fails or returns no update, the issue lies with the OEM's server availability or your network, not the Esper policy.
5. Verify the device meets all OEM preconditions for updating.
   Most OEMs enforce the following before allowing an update to proceed:
   • Battery level is above the OEM minimum threshold (typically 30–50%, or 100% when not plugged in for some models)
   • Device is connected to a stable network — preferably Wi-Fi rather than mobile data
   • Device is in an idle or low-usage state
   • Sufficient free storage is available for the update package
   If any precondition is not met, the update will silently defer until conditions are satisfied.
6. Review the Activity Feed for any update-related events.
   Navigate to Devices & Groups → [Device Name] → Activity Feed and filter for OS update events. Any policy push confirmations, update attempts, or errors will appear here and help you determine whether Esper has successfully delivered the policy to the device.

Verify: After conditions are met and an OEM update is available, the device should automatically download and install the update without user interaction. The new OS version and Security Patch Level will be reflected under Devices & Groups → [Device Name] → Device Info within a few hours of the update completing. If the update mode is set to Update Automatically, no manual action on the device is required.

If this doesn't resolve it

If the OEM confirms an update is available, the device meets all preconditions, and the Blueprint policy is correctly applied but the device still does not update, contact Esper Support with the following information:

• Device name and serial number (from Devices & Groups → [Device Name] → Device Info)
• Current OS version and Security Patch Level
• Name of the Blueprint applied to the device and its OS Update policy setting
• Screenshot or export of the Activity Feed filtered to OS update events
• Confirmation from your OEM that the update is available for this model via standard Android update channels

Still need help?

If you've verified your Blueprint OS policy settings and OS updates are still not applying automatically on your enrolled devices, please submit a support ticket and include your device model, OEM, current OS version, and a screenshot of your Blueprint OS policy configuration.