Screen flickering on managed devices: switch to Multi App Mode and capture bug report to isolate cause

Android

Title: Screen flickering on managed devices — isolate cause and capture diagnostics

When a managed Android device experiences screen flickering across all applications, the cause is typically either the Esper launcher configuration or a hardware-level issue rather than a problem with any single app.

Why this happens

Screen flickering that affects every application simultaneously usually originates at the launcher or device level. A pinned application, a display setting in the active Blueprint, or a conflicting Single App Mode or Kiosk Mode configuration can force the screen into a persistent refresh loop. If the flickering survives a mode change, the issue is more likely hardware-related and requires diagnostic data to confirm.

Before you begin

Confirm you have physical or remote visibility of the device screen so you can observe behavior changes in real time.
If you reach the bug report step, a technician or user must be physically present at the device to tap Share when prompted. This step cannot be completed remotely.
Note the device's current mode before making any changes — you will need this if you want to restore the original configuration later.

Steps

Check the device's current mode. In the Esper Console, 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 it after testing.
Switch the device to Multi App Mode. Go to Devices & Groups → [Device Name] → Blueprint, edit the active blueprint, and set Device Mode to Multi App Mode. Apply the updated blueprint to the device. Switching modes removes launcher constraints and pinned-app rules that could be forcing a continuous screen redraw. Wait 2–3 minutes for the change to take effect.
Observe the device screen for 5–10 minutes.
- Flickering stops: The issue is launcher or Blueprint-related. Review the pinned applications and display settings in the blueprint you were running, then restore your original mode. No further steps are required.
- Flickering continues: Proceed to the next step.
Reboot the device. Go to Devices & Groups → [Device Name] → Actions and select Reboot. A reboot clears transient memory and rendering states that can survive a mode change but are unrelated to hardware failure. Wait 3–5 minutes for the device to restart fully, then observe the screen for another 5–10 minutes.
- Flickering stops after reboot: The issue was a transient software or rendering state. Monitor the device over the next 24 hours and reboot again if it recurs.
- Flickering continues: Proceed to the next step.
Capture a bug report. Go to Devices & Groups → [Device Name] → Actions → Bug Report and select Initiate. A notification appears on the physical device. A technician or user on-site must tap Share on the device to complete the upload to the Esper Console. Return to Devices & Groups → [Device Name] and confirm the report appears in the device's report history before contacting support.

Verify: After switching to Multi App Mode, the device screen should stabilize within 5–10 minutes. If you captured a bug report, it should appear in the device's report history in the Esper Console within a few minutes of the on-site user tapping Share.

If this doesn't resolve it

If flickering persists after switching to Multi App Mode, rebooting, and capturing a bug report, contact Esper Support. Before reaching out, collect the following:

The uploaded bug report from Devices & Groups → [Device Name]
The device's serial number and model
The name of the Blueprint that was active when flickering began
A short video recording of the flickering behavior if possible
Whether the issue affects one device or multiple devices on the same Blueprint

Still need help?

If screen flickering persists after switching to Multi App Mode, submit a support ticket and include the bug report you captured along with details about when the flickering occurs and which apps trigger it.