Forcing Android OS version upgrades on managed devices: OEM dependency and Blueprint OS update scheduling

Android

When you configure OS update settings in a Blueprint and publish it to your devices, the update may not install — or may not be available to schedule at all — if your device manufacturer has not yet released that Android version for your specific device model.

Why this happens

Esper controls when an OS update installs, but not whether one exists. Android OS updates are packaged and released by each device manufacturer (OEM) independently, and only updates already published to your OEM's update servers can be scheduled through Esper. Until your manufacturer releases the target Android version for your exact device model, no Blueprint setting can apply it.

Before you begin

Confirm that your OEM has released the target Android version for your specific device model. This is separate from a general Android version announcement — manufacturers release updates per model, often on a staggered schedule. Enterprise-focused OEMs such as Zebra and Honeywell frequently release major Android versions later than consumer device manufacturers. Contact your device manufacturer directly to verify release availability before proceeding.

Schedule an OS update using Blueprints

In the Esper Console, navigate to Blueprints and select the blueprint assigned to the device group that requires the update, or create a new one. Using an existing blueprint ensures all other device settings remain unchanged.
Within the blueprint editor, locate the Esper Foundation Updates section. This is the dedicated OS scheduling feature and is separate from app updates and Esper Agent updates.
Choose the update behavior that fits your rollout:
- Apply immediately — the update installs as soon as the device detects it on the OEM's update server.
- Scheduled — the update installs during a maintenance window you define, minimizing disruption to device users.
- Postpone — delays installation by a number of days you specify, giving you time to validate the update on a pilot group first.
Save and publish the blueprint. Unpublished changes are not applied to devices.
Apply the blueprint to the target devices or groups. Go to Devices & Groups, select the device or group, and confirm the correct blueprint is assigned.

Verify the update was applied

Verify: In the Esper Console, go to Devices & Groups → [Device Name] → Device Info and check the OS Version field. The field should reflect the new Android version within the timeframe defined by your update schedule. If you selected Apply immediately, the version should update within the device's next check-in cycle.

If the update is not applying

If the OEM has confirmed the update is available for your device model but it is still not installing, work through the following checks:

Confirm the blueprint is published and assigned to the correct device or group in Devices & Groups. A blueprint that is saved but not published has no effect on devices.
Check that the device is online by reviewing the Last Seen timestamp in Devices & Groups → [Device Name]. Offline devices cannot receive or apply update instructions.
Attempt a manual update directly on the device by navigating to Settings → About Device → Software Update (exact path varies by manufacturer). This confirms whether the update is available on the OEM's server independently of Esper.
Review the Activity Feed for the device in the Esper Console to check for any update-related errors or status events that indicate where the process is failing.

If this doesn't resolve it

If the update remains unavailable or fails to apply after completing all steps above, contact Esper Support with the following information:

Device manufacturer and model number
Current OS version (visible in Devices & Groups → [Device Name] → Device Info)
Target Android version you are trying to install
Screenshot or export of the Esper Foundation Updates configuration in your blueprint
Any error events from the device's Activity Feed

Still need help?

If you need further assistance with OS version upgrades or Blueprint scheduling, submit a support ticket and include your device's OEM, current OS version, target OS version, and any error messages encountered during the upgrade process.