Screen Flickering on Managed Devices: Troubleshooting Steps to Isolate Cause

Android

Title: Screen flickering on managed devices — isolate and resolve the cause

When a managed Android device experiences screen flickering across all applications, the cause is typically a launcher configuration issue, a pinned application conflict, or a hardware fault — not a problem with any single app.

Why this happens

Screen flickering that affects every application at once originates at the device or launcher level, not the app level. The Esper launcher, an incompatible pinned application, or a Blueprint display setting can all trigger persistent flickering. If the issue survives a launcher change and a reboot, the fault is likely in device hardware or firmware.

Before you begin

Confirm you have physical or remote visibility of the device screen to observe behavior changes in real time.
If you need to capture a bug report (Step 5), arrange for a technician or user to be physically present at the device — they must tap Share on the device screen to complete the report. This step cannot be performed remotely.
Note the device's current mode before making any changes so you can restore it afterward.

Steps

Check the device's current mode. Go to Devices & Groups → [Device Name] → Details and note whether the device is in Single App Mode, Multi App Mode, or Kiosk Mode. Record this so you can restore the original configuration after troubleshooting.
Switch the device to Multi App Mode. Go to Devices & Groups → [Device Name] → Blueprint, open the active blueprint, and set Device Mode to Multi App Mode. Apply the updated blueprint to the device. Switching modes replaces the current launcher environment, which isolates whether the Esper launcher or a kiosk-level display setting is responsible for the flickering. Wait 2–3 minutes for the change to take effect.
Observe the device screen for 5–10 minutes.
- Flickering stops: The issue is linked to the Esper launcher, a pinned application, or a Blueprint display setting. Review the pinned applications and display configuration in your blueprint before re-applying it.
- Flickering continues: The launcher is not the cause. Proceed to the next step.
Reboot the device. Go to Devices & Groups → [Device Name] → Actions and select Reboot. Wait 3–5 minutes for the device to restart and stabilize, then observe the screen for another 5–10 minutes. A reboot clears transient memory or rendering faults that can persist across launcher changes.
- Flickering stops after reboot: The issue was a transient software or rendering fault. Monitor the device; if flickering recurs, review recent Blueprint or application changes applied before the issue started.
- Flickering continues after reboot: Proceed to capture a bug report.
Capture a bug report. Go to Devices & Groups → [Device Name] → Actions → Bug Report and select Initiate. A prompt will appear on the physical device — the on-site user or technician must tap Share to upload the report to the Esper Console. Return to Devices & Groups → [Device Name] and confirm the bug report appears in the device's report history before contacting support.

Verify: After switching to Multi App Mode and rebooting, the device screen should display without flickering within 5–10 minutes of each change. If flickering stopped after the mode switch, the active blueprint is the confirmed source. If flickering stopped after the reboot, confirm stability over the following 24 hours before restoring the original configuration.

If this doesn't resolve it

If flickering persists after completing all steps, the issue may indicate a hardware or firmware fault that requires device-level inspection. Contact Esper Support and provide the following:

The uploaded bug report from Devices & Groups → [Device Name]
The device make, model, and Android version (visible in Devices & Groups → [Device Name] → Details)
A description of when flickering first appeared and whether any Blueprint or application changes preceded it
A screen recording or video of the flickering behavior, if possible

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.