Right Display Intermittently Turns Black on Quest 3

I have the same issue. Did you managad to solve it?

Hi makatash​ 🙂

If you haven't already done so, you should contact support:

You can do that via email, chat or whatsapp here:

Get support | Meta Store

or send a PM MetaStoreHelp​ here on the forum.

Click on their name, then click the "message" button.

sysvinit​   same advice to you 🙂

I'm having this same issue with mine. Sometimes, quickly locking and unlocking it helps. Does anyone know of a permanent solution?

I had this happen in Il-2 BOS, last night,, had to go to desktop and click the controller... I was not using the controllers while flying. I use joystick. All my room lights were on. Does not happen in DCS. Also, Guardian is annoying as I don't use it. I think I found a way to stop it from asking me to set it up a long times ago, but It always comes up when I start the VR after not using it. Guardian needs a switch to just turn it off!

Update:

The issue somehow fixed itself for a while, but then appeared again.

At first I had the grey screen only in one eye. After that I installed the latest firmware update, v2.4, and now both displays inside the headset are grey/black.

Important detail: I do not see the Meta logo during boot, and I also do not see the boot/debug/recovery menu inside the headset. The internal displays only show grey/black. After the factory reset I had to go through the first setup blindly just to get the headset connected to the PC again.

The headset itself still works: I can connect it to the PC, ADB works, casting/streaming to the monitor works, and on the PC screen I can see the normal Quest interface. Sound, vibration and tracking also seem to be working.

Things I already tried:

• Many normal reboots and hard reboots
• Full factory reset
• Updating again through the browser / Meta Software Update Tool
• Fully discharging the headset and charging it again
• Charging with the original charger and original cable
• Charging with the BOBOVR strap/power bank
• Removing all accessories, facial interface/cover, strap accessories, etc.
• Trying with and without USB connected
• Checking the proximity sensor / sleep state

Some debug info that may be useful:

dumpsys power shows that the headset is awake and not sleeping:

mWakefulness=Awake

mProximityPositive=false

mHoldingWakeLockSuspendBlocker=true

mHoldingDisplaySuspendBlocker=true

mScreenBrightnessDefault=0.7992126

So it does not look like the headset thinks it is off my face or asleep.

dumpsys display also shows that the internal display is detected and enabled:

DisplayViewport{type=INTERNAL, valid=true, isActive=true, displayId=0, 4128 x 2208}

DisplayDeviceInfo{"Built-in display" ... type INTERNAL ... state ON, committedState ON}

mState=ON

mCommittedState=ON

mBrightnessState=0.8

DeviceProductInfo{name=Sharp novatek}

So Android/Quest OS seems to think that the internal display is present, active, and turned on. But physically inside the headset I only see grey/black screens.

I also saw repeated logcat messages like:

SurfaceRenderThread: Have Frame, but rendering is disabled

However, after checking more logs, this may be related to casting/virtual display services, because casting to the PC works and the compositor/passthrough seem to be active.

At this point it does not look like a proximity sensor, sleep, Guardian, or normal software issue. The system is alive, the internal display is detected as ON, but the actual headset panels do not show the image — not even the boot logo or recovery/debug menu. It looks more like a low-level display path / panel / display controller / ribbon cable issue, unless someone knows a specific firmware/debug fix for this.

Small update:

My Quest 3 was left unused for about two weeks. Today I checked it again, and one eye/display was working.

With only one working eye, I updated the firmware to v2.6. After the update, I used the “Restart” button in the power settings, and after that both eyes/displays turned on. For now, everything seems to be working normally.

Before all of this, I had also disabled the proximity sensor through SideQuest, and I disabled automatic dimming in Experimental Features. I’m not sure if any of this helped, or if the headset somehow fixed itself, but I wanted to share this in case it helps someone.

Important note: disabling the proximity sensor did not immediately fix the second eye. I tried turning the headset on and off after that, and nothing changed at the time. The second display only came back later, after the headset had been sitting unused for a while and after the v2.6 update/restart.

Right now I don’t know whether the proximity sensor is still disabled in SideQuest settings or not. It’s also possible that the sensor itself is faulty or not working properly for some other reason. Honestly, I don’t want to check or change that setting again while everything is working. I can live with turning the headset on manually with the power button.