I have a set of 5 Quest 2s. Today I updated them to software v68.
Since this update, I am unable to interact with any buttons in any Meta OS menu - e.g. the boundary setting buttons, the dashboard buttons to select or launch apps, the settings button, etc, after the headset has been restarted. My hands or controllers appear just fine, but I cannot interact in either mode. Sometimes interactivity is restored after leaving the headset to sit for a long period, sometimes it does not appear to return at all. Even if interactivity is restored, after the next restart the problem arises again.
If for any reason the headset is in the boundary setup space, e.g. if an object has been detected in the boundary space, it is impossible to leave this space from inside the headset. A workaround is to disable the boundary via ADB, but this just brings you to the unresponsive home menu.
While in this state the headsets also run very hot.
If I hold the power button to open the power menu, I get a notification saying that hand tracking and controller tracking is disabled, and to select an option using the volume buttons instead. My hands or controllers are still visible, but will not interact with the menu buttons. The volume buttons also do not interact with the menu buttons, and just open the volume bar like normal.
I am able to interact with content inside whatever window happens to be open in the headset - e.g. the Horizon window which opens by default - but I cannot close or minimise the window, or interact with any button which is a part of the OS. I can grab the border around the windows and move them around, or recenter the view with the Meta button.
The headsets are in developer mode, and if I try to launch an app through MQDH, I get stuck on the three dots screen, with no interactivity options whatsoever (including the Meta button). The only option is to hold power and turn off the device.
I tried factory resetting one of the headsets, but this did not change anything - as soon as I was past the setup and into the home screen, the OS buttons were unresponsive.
This behaviour is consistent across all five headsets, and is obviously practically bricking the headsets.
Hi @ARU_StoryLab, we are disappointed to hear that you're having similar issues across all your headsets therefore in order to allow us to look further into this, we would request you to PM us as it may require some personal information. To PM us:
Please select our name to get to our profile page, or click here.
Next, click "Send a Message" to privately message us!
Please remember, you must be signed into the community first to send us a private message.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Still need help?
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
