Display brightness and volume settings revert after saving in Blueprint: investigation steps and data collection

Android

If display brightness and volume settings revert to lower values after you save them in a Blueprint, follow these investigation steps to identify and resolve the issue.

Before you begin

Gather the following information about the affected devices:

Device serial numbers or group names where the issue occurs
Whether the problem affects all managed devices or specific ones
The exact brightness and volume values you're trying to set
Whether you recently changed a Blueprint, updated firmware, or upgraded the Esper Agent

Step 1: Review your Blueprint configuration

In the Esper Console, go to Blueprints.
Open the Blueprint assigned to the affected device or group.
Navigate to Device Settings → Display and check the Brightness value.
Navigate to Device Settings → Sound and check all Volume sliders.
If either setting is below your target value, update it to 100% (or your desired value).
Click Save.

Step 2: Re-apply the Blueprint to your device

Go to Devices & Groups → [Device Name] → Blueprint.
Click Re-apply / Converge Blueprint and confirm.
Wait 2–5 minutes for the changes to apply to your device.

Step 3: Check for conflicting policies

If your device belongs to multiple groups, conflicting policies may override your settings:

Verify that a parent group's Blueprint does not override the child group's display or sound settings.
Confirm that no Compliance Policy or separate Device Settings profile is enforcing lower values.

Step 4: Disable adaptive brightness (if applicable)

Android's adaptive brightness feature can override MDM-enforced brightness values. To prevent this:

In your Blueprint, go to Device Settings → Display.
Disable adaptive brightness or auto-brightness.
Save and re-apply the Blueprint.

Step 5: Test the settings on your device

After Blueprint convergence completes, manually adjust brightness and volume on the device to your target values.
Observe whether the values revert within the next convergence interval (typically a few minutes).
Monitor through at least two full convergence cycles (10+ minutes) to confirm the settings persist.

Step 6: Collect diagnostic data if settings continue to revert

If brightness and volume settings still revert after following the steps above, collect a bug report for analysis:

In the Esper Console, go to Devices & Groups → [Device Name] → Actions → Bug Report.
Wait for the bug report to complete and download it.
Alternatively, you can use ADB to capture a bug report:
```
adb bugreport bugreport_[device_name].zip
```

When you contact Esper Support, include:

The bug report ZIP file
Your Blueprint JSON export (available in Blueprints → [Blueprint Name] → Export)
The Esper Agent version (found in Devices & Groups → [Device Name] → Device Info)
Your device model and Android OS version
Steps you've already taken to resolve the issue

Known limitations

Some OEM devices with custom Android ROMs restrict programmatic brightness control through mobile device management. This can cause the operating system to silently reject enforced values, producing the same revert behavior even when your Blueprint is correctly configured.

Volume enforcement behavior may also differ by stream type (media, ringtone, notification, alarm). Verify which audio stream you're targeting in your Blueprint settings.

Still need help?

If the issue persists after completing these steps, contact Esper Support. Provide the bug report, Blueprint configuration, and device details from Step 6 to help us diagnose the problem quickly.