Smallest Width DP changes unexpectedly on devices

Android

If you notice that the Smallest Width value on your devices changes unexpectedly without any configuration changes from the Esper Console or ADB, a third-party Supervisor plugin may be forcing a display density override. This article explains how to diagnose and resolve this issue.

Before you begin

This issue typically affects devices from the same store or model at the same time. The Smallest Width value may change from the expected 752 dp to 485 dp or 640 dp without any intentional configuration update.

Important: Before making any manual corrections on newly affected devices, capture a bug report first. Manual changes will overwrite the diagnostic evidence you need to identify the root cause.

Step 1: Capture a bug report from the affected device

1. In the Esper Console, go to Devices & Groups → [Device Name] → Overview
2. Select Bug Report
3. Follow the full steps at How to generate and download device logs to capture the complete bug report

Step 2: Analyze the bug report for display density override

Open the bug report and look for a discrepancy between the base density and the active (override) density:

• Base density: 160 DPI (expected)
• Active/override density: 240 DPI (abnormal — indicates a forced override is active)

Also note the package name responsible for the override. Common examples include com.shoonyaos.oculus.plugin.supervisor.rk3566_r or similar Supervisor plugins.

Step 3: Manually restore the Smallest Width value

1. In the Esper Console, go to Devices & Groups → [Device Name] → Settings → Developer Options
2. Locate Smallest width
3. Set the value back to the expected 752 dp

Step 4: Address the Supervisor plugin behavior

Work with your device manufacturer (OEM) to determine:

• What triggers the Supervisor plugin to apply the density override
• Whether a plugin update, configuration change, or removal resolves the issue
• Whether you can use an Esper Device Configuration to enforce the correct display density as a preventive measure

Step 5: Monitor for recurrence

After manual correction, confirm that:

• The Smallest Width value shows 752 dp under Developer Options
• The display renders as expected
• The value does not revert on the affected devices

If the issue persists or recurs

If the Smallest Width value reverts after manual correction, the Supervisor plugin is likely re-triggering the density override on a schedule, reboot, or in response to an app or system event:

• Capture a bug report immediately at the point of recurrence without making any manual changes
• Check for scheduled actions: Confirm with your account team whether a Blueprint app update or other scheduled action correlates with the timing of each recurrence
• Consider enforcement: If the Supervisor plugin cannot be disabled or reconfigured, ask your account team about using an Esper Device Configuration to enforce the correct density value at the platform level — this may counteract the plugin override
• Contact Esper Support (see below) if multiple stores are affected on a recurring basis

Still need help?

If you've followed these steps and the issue persists, contact Esper Support. provide:

• Bug reports from affected devices
• The specific device model and firmware version
• The package name of the Supervisor plugin (from the bug report analysis)
• Details about when the issue started and whether it recurs