Android OS not updating automatically despite Blueprint set to "Update Automatically": verify and re-publish System Update Policy

Android

If your devices aren't updating to a new Android OS version even though you've set your Blueprint to "Update Automatically," the issue is likely that your Blueprint changes haven't been published and converged to your devices yet. This article walks you through verifying and republishing your System Update Policy.

Before you begin

Make sure your devices meet these prerequisites for automatic OS updates to work:

• Device is idle (not in active use) for at least 2 hours
• Device is connected to a charger
• Device is connected to a stable Wi-Fi network

Also confirm that the target Android OS version is actually available for your device model and region through your carrier's OTA update channel — Esper's System Update Policy controls when an update installs, not whether your device manufacturer distributes it.

How to verify your Blueprint's System Update Policy

1. In the Esper Console, go to Blueprints.
2. Open the Blueprint assigned to the device group that isn't updating.
3. Locate the System Update Policy setting.
4. Check whether it's set to "Update automatically" or "Postpone installation".

If it's set to "Postpone installation," proceed to the next section.

How to change your System Update Policy to "Update automatically"

1. In the Blueprint configuration, change System Update Policy from "Postpone installation" to "Update automatically".
2. Click Save to save your changes.
3. Click Publish to create a new Blueprint version.

How to converge the updated Blueprint to your devices

Blueprint changes only take effect on devices after they've been saved, published, and converged. Convergence pushes the new Blueprint version to your devices.

1. In the Esper Console, go to Devices & Groups.
2. Select your device or device group.
3. Open the Blueprint tab.
4. Apply or trigger convergence of the latest Blueprint version to the device(s).
5. Wait for convergence to complete. You'll see the status change to "Converged" on the latest version.

How to verify the OS update has been applied

1. In the Esper Console, go to Devices & Groups.
2. Select your device.
3. Open the Device Info tab and check the OS version — it should now show your target Android version.

Alternatively, check the Blueprint tab on the device details page and confirm that the latest Blueprint version shows as "Converged". After convergence completes and your device meets the prerequisites (idle, charging, connected to Wi-Fi), the OS update should trigger within a few hours.

Troubleshooting: Update still isn't triggering

If your Blueprint shows as converged with "Update automatically" but the OS update still hasn't started:

• Check for conflicting policies: Verify that no other Blueprint or parent group policy is also enforcing "Postpone installation," which could override your device-level setting.
• Verify OEM support: Some device manufacturers restrict or override OS update management even when Android Enterprise policies are set. Contact your device manufacturer to confirm they support managed System Update Policy through Android Enterprise's DevicePolicyManager.
• Review convergence status: Go to Devices & Groups → [Device Name] → Blueprint and confirm convergence succeeded. If convergence is failing or stuck, the policy won't take effect.

Still need help?

If you've followed these steps and your devices still aren't updating, contact Esper Support. Include your device ID, Blueprint version history, and a screenshot of your device's convergence status from the Blueprint tab.