Skip to main content
New Participant
April 21, 2026
Question

Black screen after removing and reattaching headset, display on but no image rendered (2.1 & 2.3)

Overview

After taking the headset off and putting it back on, the display stays completely black. Audio continues playing and controllers can still interact with UI elements, confirming the session is active and the display is on. This is not intermittent, it occurs frequently and has been reproduced across multiple Quest 3 units on both Horizon OS 2.1 and 2.3.

Affected apps

  • First Encounters (system app)
  • Horizon Store apps
  • Custom / developer apps

Confirmed on

  • Multiple Meta Quest 3 units
  • Horizon OS 2.3 (all units affected)
  • Horizon OS 2.1 (some units affected)
  • Not present on v85

Steps to reproduce

  1. Put on Meta Quest 3 running Horizon OS 2.1 or 2.3
  2. Open any app (system, store, or developer build)
  3. Remove the headset
  4. Put the headset back on
  5. Screen remains black, while audio and controller input still active.

Workarounds found

Hand tracking

Moving a hand in front of the headset cameras triggers hand detection, which resolves the black screen.

Controllers

Pressing the Meta home button restores the display. Holding controllers in view of cameras is not sufficient.

Developer impact

This issue directly breaks automated onboarding flows. Our app is designed so onboarding requires no manual intervention, but users are now forced to interact with the home button or manually wave their hands to recover from the black screen. Which defeats the purpose of a seamless first-run experience.

Version & unit breakdown

OS versionUnits testedResult
v85 (pre-2.x)2No issue
Horizon OS 2.13Intermittent, not all units
Horizon OS 2.33All units affected

If more info is needed, let me know.

Sincerely,
Raymond

1 reply

Degly
Inspiring
May 10, 2026

Just to add a bit more info for mi this sounds like a Horizon OS compositor/resume regression rather than an app-specific rendering bug.

The fact that v85 does not show the issue is also a very strong signal that something changed in the suspend/resume pipeline in 2.x.

It almost sounds like the display/compositor is failing to resume properly until another system-level tracking/UI event forces a refresh.