Up and Coming

Question

V81 Bug? Menu won't appear when turning on Quest 3

64 replies
5454 views

Recently got access to the PTC for V81, and all seemed fine. But I turned on my Quest 3 and the menu won't appear at all, even after holding down the right controller button and even testing it with hand tracking...

HOWEVER...

This issue seems to be hit and miss. When I was ready to give up and do a factory reset, turned my headset on and randomly the menu appeared again. It sometimes disappears if I leave my headset on standby for a while, and sometimes disappears if I turn it off and on, and sometimes just randomly appears.

Is this a common bug or does anyone have any potential fixes? I have tried launching games from the app and it did work one time, despite it showing the launch and install on headset, even when the app is already installed. I understand it's a beta and could be a bug but wondering if it's just me.

Also, when the menu doesn't appear, if I were to hold the power button, it just shuts down, it doesn't give me the option to reset or anything.

Any help greatly appreciated 😁

Show previous replies

T

talastar

Up and Coming

Hey Chris, I’ve had the same issue on my Quest 3 after the V81 PTC update. The menu randomly disappears and only comes back after a restart or waiting a bit. It seems to happen more after standby, so I’ve been doing full shutdowns instead. Looks like a V81 bug, hopefully fixed soon.

S

Satconcook

Participant

I had been avoiding v81, knowing there have been issues and apparently I rolled the dice and got this one. It has boot up 1 time and as soon as I clicked on something, it all vanished and reboots have done nothing to bring it back. I am apparently able to take screenshots and it is making the sound of the menu opening. I can see it with the phone app and PC developer tool, but no menu in the headset or anything.

S

Satconcook

Participant

So, in search of finding a solution after rebooting multiple times, this is what I came across.
https://www.reddit.com/r/OculusQuest/comments/1oin4fi/psa_no_menus_ui_at_startup_bug_reproduction_and/

I just logged into my router, went to the client list and blocked the "Android Device" as I knew it was my Quest. Only device that uses the 6Ghz. Anyways, rebooted, waited a bit, then I was able to get a menu telling me that WiFi connection failed. I restored it on my router, selected the same WiFi it was already on and then it worked. It acted like it was trying to connect a new device, but I went back and now all the menus work as intended.

M

michaelgrosch2023

New Participant

Just to be sure, I'd like to double-check that I've understood correctly:

If you completely disable Wi-Fi – including all repeaters in the mesh network – so that there is no Wi-Fi connection whatsoever, and then restart the MetaQuest 3, will an error message appear stating that no Wi-Fi connection can be established?

If you then re-enable the original Wi-Fi network and reconnect to the MetaQuest 3: Do all the menus function correctly again, and are they displayed as usual every time the MetaQuest 3 is started?

(I have no 6 GHz WLAN Router. Is a Wifi 7 Router with only 2.4 GHz and 5 GHz.)

X

xMasterCGx

Up and Coming

Okay ive fixed mine.

Solution - Turned off my Router and my separate Wifi (15 - 20 seconds), plugged back in. Problem solved. I didnt have to do anything with SSIDs and passwords.

When we get updates, the headset should show a notification advising we reset our routers and wifi.

M

michaelgrosch2023

New Participant

Just to be sure, I'd like to double-check that I've understood correctly:

If you completely disable Wi-Fi – including all repeaters in the mesh network – so that there is no Wi-Fi connection whatsoever, and then restart the MetaQuest 3, will an error message appear stating that no Wi-Fi connection can be established?

If you then re-enable the original Wi-Fi network and reconnect to the MetaQuest 3: Do all the menus function correctly again, and are they displayed as usual every time the MetaQuest 3 is started?

(I have no 6 GHz WLAN Router. Is a Wifi 7 Router with only 2.4 GHz and 5 GHz.)

X

xMasterCGx

Up and Coming

Hi, it wasnt me who gave that instruction, you will have to ask them about the "No wifi can be established" stuff.

All i did is what i typed above, i turned off my router/wifi/meshes etc gave it 15-20 seconds, turned back on, then turned on my Quest.

Thats all i did.

Btw, the issue came back, after a few days but its always resolved with 1 restart.

M

Mackb0115

New Participant

The thing that meta will force us to use later the new menu if you will. It's called navigator just so you know

X

xMasterCGx

Up and Coming

Never heard of it and never seen it before.

M

Mackb0115

New Participant

Well if you want to try it, go into your advanced settings and it should be there. If not going to the meta horizons app like opt-in whenever you find the opt-in to any new experimental features once you restart your headset. Bam you got it!

X

xMasterCGx

Up and Coming

Thank you, i had no idea about this so i will check it out. Much appreciated.

islandpferd

New Participant

I keep getting this in v83 even. Getting the UI back is always a hit or miss, but something that worked almost consistently for me is switching positions for the hard reboots. Basically get out of your playspace to force the thing into using a Stationary (which BTW still completely sucks for small room usage since v40 where the boundary was removed without making the no-boundary mode optional, however without boundaries it's better for seated use) or back into your roomscale from outside. That and just leaving the thing be in OFF state (not standby) for like 5-10 minutes. Still can fail as it just did now again for me, which brought me here. We need to have this fixed.

BTW it ONLY happens for me after reboots, with or without updates. And since v83 introduced even more issues, the UI keeps slowing down more and more the longer you don't reboot until you're literally forced to do so when it only runs at like 1-5fps and then completely freezes up eventually.

PS: Switched back to the VASTLY superior old UI and thought that would fix the issue, but it didn't, so I guess the UI type doesn't really matter.

I'd actually even try the nuclear option, but I currently have no free space left anywhere to do proper backups with Sidequest beforehoof. Would want to try that, because Meta broke my standby timer settings with v64 and those never got fixed. I can set them to whatever I want, the thing IMMEDIATELY turns off as soon as I take the headset off or even just forehad-rest it, which is really annoying since that always causes it to recenter when putting it back on and there's no way to prevent this from happening anymore and I have to recenter myself a gajillion of times a day because of that unthoughtful design decision. Meta, please give us a "remember current centering position and keep it until I and only I myself change it" mode, it will be very much praised and appreciated by anyone using the thing for anything seated!

PPS: I can't even use the sideloaded Sidequest app anymore for disabling the prox sensor, its adb self-connect thing is completely broken since Meta went Android 14 and SQ haven't fixed it yet...

K

KeithVT6

New Participant

Same issue. Hard reboot is not an acceptable solution. Please fix this and all the other bugs in v81. For example, PIN code screen at same time as Boundary Off dialog and cannot click either so hard reboot is again needed. Very disappointing.

B

Billythefish76

New Participant

I'm having exactly same issue, absolute pain! It only worked once by putting headset into sleep rather than shutting it down seemed to keep menu up? Hoping Meta sort this issue soon as continuously 'hoping' restart will work is no way acceptable.

MetaStoreHelp

Community Manager

Hi Billythefish76, we came across your post and wanted to offer some assistance.

We completely understand that this is not an ideal situation, but not to worry, let's look into this for you!

You've mentioned that the menu is not appearing for you. There is a new software update which is available via the Public Test Channel. You may wish to enroll in this as it has an updated version of the Navigator menu. More information on this can be found here.

To enroll in the Public Test Channel, please follow these steps:

Open the Meta Quest Link app on your PC.
Select Settings, then select the Beta tab.
Select the toggle next to Public Channel to enroll.

If, after this, you are still experiencing issues, please don't hesitate to reach out to our Customer Support team where one of our colleagues can investigate this further for you.

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

W

WetBlister

Participant

Nope. My first problem was enrolling in that PTC to begin with. When I heard about V81, I was so excited and got impatient...because I typically NEVER install experimental operating systems for anything. But I decided to take my chances...enroll in PTC, so I could use V81. That was a disasterous choice. So I unenrolled from PTC and installed the official V81 when it went live...but the same problem with the menu stuck around.
The menu issue has gotten better since, with another update.
But it's still a bit dicey and hasn't been resolved.

I think I'll just wait until whatever is currently being tested to get an official release...because I don't trust the Beta versions anymore. I got a Quest to have fun...and not experience the bugs. ...and I'd be much more likely to experience more bugs by enabling PTC. So that ain't happening.
What's even the point of PTC when you're still releasing the non-Beta official updates with VERY significant bugs anyway? Those bugs are supposed to be resolved in Beta.

I miss those days with my Quest when I didn't have to FEAR each "big update".
Now that "fear" has become quite the norm among us users.
Not a good business model.

L

LilTimmyyy21

New Participant

I have this same issue. They need to fix this immediately.

G

Gwanatu

Participant

I have the same issue and I'm on V83 now. Have had this issue since V81 rolled out. I don't have Navigator enabled but will try that if my headset ever gives me a UI again ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

G

Gwanatu

Participant

Looks like turning my router off and booting up the headset with no Wi-Fi worked. I'll try it again next time it happens and see if it's consistent.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO