How to Inspect Display Refresh Rates, HDR, and Color Modes on Android Using ADB dumpsys display

Modern Android smartphones, foldable devices, and tablets feature sophisticated OLED and AMOLED panels capable of dynamic variable refresh rates (from 1 Hz up to 120 Hz or 144 Hz via LTPO technology), wide color gamuts (Display-P3), and high-dynamic-range video decoding (HDR10+, Dolby Vision). When developing high-framerate mobile games, streaming video applications, or camera preview viewports, verifying whether the Android operating system actually switches into the expected refresh mode or enables HDR tone-mapping requires looking deeper than consumer settings sliders. The Android Debug Bridge (ADB) dumpsys display command extracts raw hardware and framework state from the DisplayManagerService, providing complete visibility into display modes, HDR capability bitmasks, and thermal display limits.

Understanding the Android DisplayManager Architecture

The Android display architecture coordinates with the hardware SurfaceFlinger compositor through the DisplayManagerService. Rather than treating screen panels as fixed pixel matrices, modern Android represents each physical screen as a LogicalDisplay backed by one or more hardware DisplayDevice endpoints.

Key display properties managed by the service include:

• Supported Modes: A list of indexed hardware configurations combining resolution (e.g., 1080×2400 or 1440×3200) and vertical refresh frequencies (e.g., 60.0 Hz, 90.0 Hz, 120.0 Hz).
• HDR Capabilities: Reports supported high-dynamic-range formats, including HDR10, HDR_HLG, HDR10_PLUS, and DOLBY_VISION, alongside luminance peak thresholds.
• Color Modes: Supported color management gamuts (such as COLOR_MODE_DEFAULT, COLOR_MODE_WIDE_COLOR_GAMUT, and COLOR_MODE_HDR).
• Display State Limits: Dynamic frame rate limits imposed by the operating system due to battery saver modes, thermal throttling, or display brightness levels.

The dumpsys display command dumps the real-time operational state of all these parameters directly to the shell.

Extracting Display Telemetry via ADB

Connect your Android device or virtual device via USB or Wi-Fi debugging. Verify authorization:

adb devices

To inspect the entire display subsystem, execute:

adb shell dumpsys display

Because the full report catalogues all active logical displays, presentation displays, and historical brightness transaction curves, piping output into targeted search commands allows rapid analysis.

Auditing Active and Supported Display Modes

To verify the current operational resolution and refresh rate, search the dump for the active display mode:

adb shell dumpsys display | grep -E "mActiveModeId|supportedModes" -A 10

The terminal outputs the mode list:

mActiveModeId=1
supportedModes:
  Mode 1: 1080x2400, 120.0fps
  Mode 2: 1080x2400, 90.0fps
  Mode 3: 1080x2400, 60.0fps
  Mode 4: 720x1600, 60.0fps

This confirms that the device hardware supports 60 Hz, 90 Hz, and 120 Hz, and that Mode 1 (120 Hz) is currently active. If your game or app requests 120 fps but the active mode reports 60.0fps, check whether battery saver mode or system thermal policies are restricting maximum refresh rates.

Inspecting HDR Formats and Luminance Thresholds

Streaming video services require explicit hardware confirmation that the display can process HDR metadata before delivering high-bandwidth 4K HDR streams.

Filter the dump for HDR capabilities:

adb shell dumpsys display | grep -A 8 "mHdrCapabilities:"

A high-performance display panel returns detailed luminance data:

mHdrCapabilities:
  supportedHdrTypes: [2, 3, 4]
  maxLuminance: 1450.00 cd/m2
  maxAverageLuminance: 1000.00 cd/m2
  minLuminance: 0.0001 cd/m2

The integer identifiers correspond to Android standard HDR types:

• 1: HDR_TYPE_DOLBY_VISION
• 2: HDR_TYPE_HDR10
• 3: HDR_TYPE_HLG
• 4: HDR_TYPE_HDR10_PLUS

The peak luminance value (e.g., 1450 cd/m2) confirms that the hardware supports high-contrast HDR rendering without tone-mapping clipping.

Auditing Color Modes and Wide Color Gamut (WCG)

Modern photography, creative, and video editing apps utilize the wideColorGamut manifest flag to render Display-P3 imagery.

To verify whether wide-color rendering is currently enabled by the hardware, run:

adb shell dumpsys display | grep -E "(mColorMode|isWideColorGamut)"

If isWideColorGamut=true, the operating system is actively driving the display panel in DCI-P3 or AdobeRGB color spaces. If it reports false, the framework restricts color coordinates to the narrower sRGB gamut.

Forcing Specific Refresh Rates for Development Testing

Testing application responsiveness at specific frame rates—such as verifying animation smoothing at 90 Hz or auditing battery drain at 120 Hz—can be forced directly through ADB system settings overrides.

To lock the display to a minimum and maximum refresh rate of 120 Hz, execute:

adb shell settings put system min_refresh_rate 120.0
adb shell settings put system peak_refresh_rate 120.0

To reset the device back to dynamic LTPO variable refresh behavior, clear the overrides:

adb shell settings delete system min_refresh_rate
adb shell settings delete system peak_refresh_rate

Leveraging dumpsys display gives mobile developers and QA engineers hardware-level insight into panel mechanics, ensuring graphics pipelines perform optimally across all modern Android hardware.