Quest 2, 3 & Pro - Connectivity Issues

[Gunstar_Tony]

Hi everyone,
I have a Quest 3 and cannot connect the the wifi (it's a freebox, french internet provider).

Steps i took to troubleshoot : 

• I did manage to connect the quest to my cellphone via hotspot.
• I factory reseted the quest and retried to connect to the freebox via passwords and QR code.
• I trued to connect the quest via the phone app.
• Rooter was rebooted, i was in the same room etc.
• We have all other devices connecting without problem to this rooter.

Thanks for your help

[Unprogress]

It really is getting ridicoulous. I have written to support the exact steps , including but not limited to, Test Firmware, current stock firmware, Factory resett, 2,4Ghz wifi, disabling Ipv6. Nothing works. I am beyond furious right now. I am right now striving for sending it in as waranty case.

[Baron-von-Doom]

ive updated my quest 3 to the official v67 and nothing is solved

my quest 3 cannot see 6ghz band and when it rarely finds 6ghz it doesnt connect saying cannot connect try again later!!!!

is this problem gonna be solved ever? or should i return my headset or send it back to get it fixed?

[lucacesa]

I finally received the V67, which forced me to factory reset my device because after the update, it blocked My Quest (thanks Meta, I need to reconfigure everything from scratch...) and, as imagined, NOTHING was fixed. Wifi still drops, same as before (if not worse, will check later tonight)

@TheLegend27 what about all your messages regarding this being fixed? To be very honest, looks like all false information to me. Can we escalate this thread to a higher-level mod or directly to a Meta Engineer? This needs to be directly reported to Meta.

Also in the changelog, nothing is mentioned about WiFi Fixes.

I have the feeling you have no idea what is going on here, and you are running in circles. I really hope to be wrong, though.

[SimpleCJ]

I'm also unable to use 6ghz. I can connect to it, but it is unstable.  Have you tried 5ghz band? That's what I've been using and it's been stable on my TP Link XE75, connected at 1200mpbs. 

This bug seems to be dependent on what router you are using and how that router is configured.  Some report it works in Router mode, but not Access Point mode, but that creates an internet connection problem for a dedicated setup, which I guess can be solved with further configuration, but for most people that might be over their heads or not even solve their issue.

I've not seen anyone with a PrismXR Puppis air bridge say they're having issues. That could be a cheap solution for many of us. Only $80 on Amazon and works independent of your home network. It is only 5ghz, but has a special pulse mode made for VR and connects to your usb ports. I've had many people on reddit confirm it works well for them.

I have hopes this will be resolved, but there are work-arounds in the meantime. I did a poll on reddit  and about 40% said they have had issues. 60% said no issues.  So this clearly isn't effecting everyone.

[paul.frampton.754]

It's annoying that we've gone from no issues with earlier versions of the software, to constant dropouts. Mine was fine when I bought it a few months ago, then the constant dropouts.

My Quest 2 is fine, so to my mind, it's clearly something Meta have done.
What happens when the Q4 comes out and they stop supporting the Q3? If this still hasn't been fixed, we'd have spent £500 on a device that was largely useless for our needs.

Surely some sort of compensation is in order for the time we've already spent not able to use the device?

[Baron-von-Doom]

i can connect to 5ghz at 2401mbps but i get frame drops and stuttering on airlink.

i got a wifi6e router to have the smoothest connection and my neighborhood is crowded with 5ghz .

i dont understand whats going on with 6ghz it was working fine on v64 and its working fine on my quest pro on v64. i guess the update messed up something with the headset wifi!!!! not all people have this problem.

i asked this youtuber (Mac In VR) who has the same router and similar setup to mine he has no problems with 6ghz and his quest 3.

even on a different thread someone had the same problem with 6ghz suddenly his quest 3 started seeing 6ghz normally and its working fine with no update or anything which was really weird,  

hope meta is working on a fix for this problem cause i wanna use my quest 3 with the router(TP Link XE75) i bought specifically to use 6ghz

[petecod]

@SimpleCJ We both have TP-Link XE75. I have just spent the last 60 minutes connected to the 6ghz network at 2401mbps. i have not had a single disconnection. i have tried youtube videos natively on the headset, videos from a local network server and pcvr on two separate gaming pcs. i tested beat saber which is installed on both pcs and suffered no disconnections, interruptions or glitches. I am hoping that this continues but if you like to test your environment then the following is what I did:

I noticed that I was on v67 (not PTC) so i enabled the 6ghz network and connected to it. In the meta headset I changed network usage from auto to unmetered and changed privacy from random to use device mac. Then i went into the TP-Link software and made an address reservation for the quest 3 headset.

It will be interesting to hear your findings if you are on v67. 

[SimpleCJ]

Your stuttering and frame drop are not related to this wifi issue. More likely it is your settings or your computer struggling to keep up. Use the performance HUD to see what is going on when it's stuttering.  My 5ghz is plenty solid at 1200mpbs with max graphics settings, 1.5x res, 120fps, on a 4090 with Virtual Desktop.  I would rather use 6ghz. I guess I'll have to see if v67 does anything for me. Last I checked I'm still on v66.

[SimpleCJ]

Thanks for the tip petecod, I wasn't planning on even getting on until I read your post. I went and checked and I am on non-PTC v67 now.  I'd already set a static IP for it a while ago and changed to unmetered and non-random device mac from a previous post, maybe yours.  I switched over to 6ghz and was able to play Beat Saber (on Steam with Virtual Desktop) for a little over a half hour with no disconnects. Connection seemed pretty solid, but I'll need to test it on some longer playtimes. I was able to get about a half hour on v66 before disconnects happened a couple weeks ago, which was the last time I'd tried it. Unfortunately I'm headed out of town tomorrow, so the testing will have to wait. It is promising though! I swear the controller response just seems more snappy on 6ghz, but maybe it's in my head? IDK...

[TheLegend27]

Hey everyone! Checking back in after my last reply. After discussing with the team a bit more, we wanted to confirm if a few network changes make any difference in your 5/6Ghz discovery and stability.

For those testing on 5GHz: Try manually changing your router to channels 36, 40, 44, or 48, if available. These are non-DFS (Dynamic Frequency Selection) channels, which might help with avoiding interference and mandatory channel routing. For those who are not in the US, you can find more information on what non-DFS channels are available to you here.

For those testing on 6GHz: Ensure your router is set to a channel that supports Wi-Fi 6. Verify that your router's firmware supports those channels, and update the router's firmware if needed.

It may help to try a 20MHz channel width initially for the sake of stability. If you find that you're able to connect stably, gradually increase the channel width while monitoring the stability of the connection. Since higher frequency bands have shorter ranges and are more easily obstructed, try placing your router or AP in the same room as your headset—away from potential interferences.

It looks like some of you had good results from switching your AP to Router mode, rather than AP mode, so that may be worth testing out as well. It also seems that configuring subnets has proved positive for some users. It may also be worth giving a shot.

Using wireless network diagnostic tools are also a great way to get a good estimate on the conditions of your network. I'd recommend trying RouteThis. This is one tool I've personally seen successfully configure user networks in the past:

1. Download RouteThis Helps app on your mobile phone or tablet.
2. Open the app and tap Begin.
3. Enter the code FBRL.
4. Stand within 6 feet of your headset and tap Next, then tap Network scan.
   1. This scan can take about 2 minutes, so ensure the application is open while running the scan.
5. When the scan finishes, you'll see a screen displaying your results. Tap Improve Device Performance and follow the instructions from there.