Software Update Policy "Disable" Not Enforced on Google Pixel 9a (Android 16): Switch to "Postpone Updates" as Workaround

Android

Title: Pixel 9a (Android 16) ignores "Disable" update policy — switch to Postpone Updates

When a Blueprint with the Software Update policy set to Disable is applied to a Google Pixel 9a running Android 16, devices continue to download and install OTA updates as if no policy were set.

Why this happens

The Android Device Policy Client on Pixel 9a devices running Android 16 does not support the Disable value for the Software Update policy. The restriction is accepted by the Esper Console but silently fails to apply at the device level, so OTA updates proceed normally. This is a device and OS compatibility limitation, not a misconfiguration in your Blueprint.

How to fix it

1. Open the Esper Console and navigate to Blueprints.
2. Select the blueprint currently assigned to your affected Pixel 9a devices.
3. Locate the Software Update section within the blueprint.
4. Change the policy value from Disable to Postpone Updates. Postpone Updates is enforced correctly on Pixel 9a and Android 16, and delays OTA installation for a configurable period rather than silently failing.
5. Set the postponement window to match your organization's update management requirements.
6. Click Save, then Publish to push the updated blueprint to your device group.

Note: Postpone Updates delays OTA installation for a configurable period but does not permanently block updates. If your organization requires a permanent block, see If this doesn't resolve it below.

Verify: Within 5–10 minutes of publishing, affected devices should reflect the updated policy in Devices & Groups → [Device Name] → Compliance. No new OTA installation should be initiated, and the device should show a compliant status in the Activity Feed.

If this doesn't resolve it

If Postpone Updates also fails to suppress OTA updates on your Pixel 9a devices, or if you observe the same behavior on other device models or Android versions, collect the following before contacting support:

• Device IDs of all affected devices
• An Android bug report from at least one affected device
• Esper Agent version (visible under Devices & Groups → [Device Name] → Device Info)
• A screenshot of the current Blueprint Software Update configuration

If your organization requires a permanent Disable setting rather than postponement, contact Esper Support to discuss whether Esper Agent support for this policy value can be added for Pixel 9a and Android 16.

Still need help?

If the "Disable" software update policy continues to not work on your Google Pixel 9a running Android 16, submit a support ticket and include your device model, Android version, and the specific policy configuration you're using.