Skip to main content
tfosseli
Inspiring
October 11, 2023
Solved

Resolved - Unstable wifi coverage with Quest 3 on some Router Brands.

  • Update January 2024 - full post history below
Hi. Let me try to give a quick TLDR summery.
 
Since the launch of the Quest 3, numerous users have encountered difficulties with their Wi-Fi connections related to wireless PCVR. A notable bug affects certain mid-range AX and AXE routers, such as TP-Link's AXE75, leading to significant packet losses and varying negotiation rates. Consequently, connection speeds fluctuate between 480 and 1921 Mbps, occasionally reaching 2161 Mbps but rarely achieving the full 2401 Mbps speed.
 
In contrast, the Quest 2 maintains a stable 1200 Mbps on 5GHz dedicated networks. However, on release, the Quest 3 struggled to reach 720 Mbps, with speed fluctuations occurring every other second.
 
Meta was promptly notified of this issue on launch day and has been working on resolving it through build updates. Versions v.57 to v.60 have seen a dramatic reduction in negotiation rates, making wireless VR "usable" under certain conditions, particularly when in close proximity to the router and within the line of sight. Nevertheless, users still report random speed reductions to unusable levels (below 740 Mbps), even at close range.
 
TP-Link has been diligently working on resolving the issue since the initial launch. Unfortunately, their latest update indicates that they couldn't make a breakthrough on their end, and they believe the problem persists on the client side. They've conducted thorough tests with various chipsets, including MTK, BCM, and QCA routers, and it seems these routers are experiencing similar issues. Their focus shifted to Meta software updates, and their most recent test with the Quest3 V60 suggests that while the negotiation rate still varies, the occasional streaming lag seems to have disappeared.
 
A glance at this threads posts reveals that TP-Link is not the only affected brand; users with Asus and other AX and AXE routers also face similar challenges. The root cause seems to be linked to either Meta or Qualcomm. Users have noted similar issues with the Google Pixel 7, leading to speculation about problems with the XR2 Gen2/Snapdragon 8 Gen2 drivers. So in other words it's in Meta and Qualcomm's hands at the moment.
 
Please reply to this thread and post your information as per Metas instructions:
 
"December 14th Update from MetaStoreHelp 
Hey everyone! I wanted to let you all know that I heard back from our engineering team. It looks like there might've been some changes with the recent v60 update. I recommend checking your headset to make sure that it is updated to the latest version, and then checking your Wi-Fi connection with your headset. If you're still having trouble after updating your headset, please let me know the below information and I'll pass it along to our engineering team so this can be looked into further.
 1. Router make and model.
 2. Router firmware.
 3. Full Headset version. (59.0.0.##) Go to Settings > System > Software Update"
 
You can also make a video grab of your issue and send it to Meta over the "report a problem" option in the headset.
 
 
NOTE: If you have a working setup with a different router and not experiencing any issues please post the details on this separate thread: https://communityforums.atmeta.com/t5/Get-Help/What-Wifi-6e-routers-currently-works-bug-free-with-the-Quest-3/td-p/1101778
 
 
 
 
Original post October 10th 2023
 

On my Quest 3 the WIFI signal is hopping from 720 - 864 - 960 

But my Quest 2 ti stable at 1200 Mbps

I am sitting 1 m from the Ruter

Is my Quest 3 broken or is this a bug?

 

Edit FYI: This is a firmware bug with communication between some brand of routers. Please post your info here as a reply. (Se MetaQuestSupports reply)

The team has been made aware and is currently looking into the unstable connection reports.

Meta needs to know:

  1. What version is your headset running? (Full number, i.e. 57.0.0.####)
    • Quick Settings > System > Software Update
  2. Which router do you currently have?
  3. Tag MetaStoreHelp 

Also.. Remember to send a bug report via Oculus apps or headset...

Here is how: https://www.youtube.com/watch?v=7i9Q_h_yeQQ

 

Edit 2, to be clear: 

The issue is not dependent on AirLink or VirtualDesktop. It's a clear communication issue between the Quest 3 and certain routers in Quest build vertion 57.  That effects both 5Ghz and 6Ghz. Quest 2 is unaffected.

Here is the issue we are facing demonstrated to TP-link:

https://youtu.be/JFrl9rTJH8E?si=2vBOI6E2PjGvPL_7

 

If you're r not experiencing any issues please post the details on this seperate thread: https://communityforums.atmeta.com/t5/Get-Help/What-Wifi-6e-routers-currently-works-bug-free-with-the-Quest-3/td-p/1101778

 

Edit 3 - Update:

Version 59 showed no improvement. TP-Link has received a unit and are experiencing the same negotiation rate problems. They are investigating the problem. 

 

MetaStoreHelp has stated that they are working on the issue and it will be fixed in a future firmware update. https://communityforums.atmeta.com/t5/Get-Help/Unstable-wifi-covarage-with-Quest-3-on-some-Router-Brands-Known/m-p/1099915#M241197

 

Edit 4 - Update...
TP-Watched  @VirtualOmnipresence 's video  and confirmed: 

Our Wireless RD found that it might be the case Quest3 are kind Quest3's wireless connection rate strategy is more aggressive in terms of speed reduction. Once it encounters wireless packet loss or interference, it will reduce the negotiation rate on a large scale, thus affecting the actual wireless performance.

In other words, it is actually unnecessarily overly sensitive... especially when interference is basically impossible at 6GHz.

We've tested the Quest3 v57(haven't got v59 yet) so far with almost all our routers from wifi6e to wifi7 with QCA/BCM chipest...

Also thanks a lot for your updates about that article, we will also notice to get the previous quest2 sample to check how it works with our router in old firmware, then upgrade it to newer one for checking.

We will also focus on this issue later quickly if there's new firmware released.

 

Edit 5 - November 20th 2023

Still no more contact with meta and the silence is deafening. 

Though with the new update to v.59 it is actually a lot better on AXE75 for both 5g and 6g. It's fluxing, but not below 1200 in 6g and not below 720 in 5g. Making it... "usable"... if you are relatively close to your router.

Here is my video in my test with v. 59.

We still want to take advantage of the 2401 Mbps so that we are not reliant on no interference and being 2 to 3 meters from the access point. 

Any working 6Ghz device connected to a 6 Ghz router, dedicated at close range should output a connection at 2401Mbps. If it doesn't it's simply not working correctly. 

So I'm not giving you a pass just yet Meta. 😉

 

Edit 6 December 8th

A lot of new posts here and in my community on still experiencing this issue making their wireless experience unbearable. The uptick has been noticeable since the release of SteamLink bringing more people over to PC wireless. 

I also go a new confirmation from MetaSupport over email:

Meta Store Support following up on your issue.

To clarify, the issue you are experiencing is most likely to be patched up with a new software update. I know how inconvenient this may be for you. We really appreciate your extended patience and utmost understanding regarding this matter. As much as I would like to give you an exact timeline, since this is still a known issue, I'm afraid we are still unable to provide an exact date for it.

This is also for our customers, as we don't want to set you an expectation that is vague. We value transparency here at Meta, and we can assure you that we will quickly contact you as soon as possible once the issue is resolved or workarounds are provided.

We're eager to have this one sorted out for you, so we'll keep an eye on this issue. Looking forward to solve this issue at your earliest convenience so you can proceed enjoying your VR experience.

----

later:

I can confirm that your issue regarding Wi-Fi connection has been coordinated with our engineering team; however, they didn't provide an exact time; maybe they are still figuring out the root cause of the issue. By the way, thank you for the clear explanation of your issue; that helps us a lot.

 

Edit December 14th Update from MetaStoreHelp 

Hey everyone! I wanted to let you all know that I heard back from our engineering team. It looks like there might've been some changes with the recent v60 update. I recommend checking your headset to make sure that it is updated to the latest version, and then checking your Wi-Fi connection with your headset. If you're still having trouble after updating your headset, please let me know the below information and I'll pass it along to our engineering team so this can be looked into further.

  1. Router make and model.
  2. Router firmware.
  3. Full Headset version. (59.0.0.##)
    1. Settings > System > Software Update

---

Here is my video on testing version 60

tfosseli
tfosseliAnswer
Inspiring
February 8, 2024

EDIT May 21th 2024: The bug returned with build v.65. Lets hope its a hiccup.  

...

 

Hey everyone! Build v62 has officially arrived, and I'm pleased to announce that my initial issues have been resolved. The speeds remain rock solid at 2401Mbps, even when I'm in a different room from the router. There was only one brief 5-second disconnect, which was swiftly resolved and did not reoccur during my session.

The issues concerning fluctuating speeds, packet losses, and random negotiation rates have all but disappeared.

However, I'm aware that some of you are still encountering difficulties connecting to the 6G network in general and are experiencing random disconnects. I'm unsure if these issues are related, especially as the problem doesn't seem to be consistent with router brands.

I recommend creating a separate forum thread on the matter so that those affected can voice their concerns and avoid being mixed up with the excitement in this thread.

Thank you to everyone who has engaged in civil discussions and shared their experiences and constructive feedback. And thank you to MetaStoreHelp and TheAntiSocializer for making sure our issues were heard by the Meta engineers. 

 

Edit: if your experiencing micro studders in AirLink follow this thread: https://communityforums.atmeta.com/t5/Get-Help/Quest-3-Airlink-micro-lags-and-stutter-esp-when-moving-head/m-p/1150175/ 

 

When a "problems finding 6G Wi-Fi" thread is created, share it here, and I'll add a link to it. 

(I can't stay as the OP of a post concerning problems connecting to a 6G network as I am not experiencing that particular problem and can't replicate it.)

 

1188 replies

Participant
January 18, 2024

I just contacted support. Here is my message

Since Virtual Desktop and wifi issues isnt a category in the support wizard I picked Display. But this issue is regarding the wifi virtual pc. Virtual PC wifi 6e is unstable, regardless of lightning fast setup and expensive dedicated accss point routers. Not sure if device is faulty and I should refund or wait until updates because of any known issue. All statisctics virtual desktop are fine, in the debug software numbers never drop to the  yellow numbers. All latency numbers are extremely low, but the mbps constantly fluctuate from 1700 to 2400 (wifi6), and every now and then weird aggresive stutters occur. Its an dedicated expensive router, only a few meters away from me. I am testing with 2 routers at the moment:
 
tp-link archer axe75 and asus Wireless Router RT-AXE7800
 
I am quite experienced with routers and internet, and I honestly dont think its caused by my expensive setup. I think I am dealing with the same issue as:
 
 
My concern is, lets say the quests 3 attenna is just faulty, that if I wait to long, I can't refund my quest anymore. Until how long can I refund in case it doesnt get fixed? I am considering switching to pico4. A friend of mine has this one, and after doing a test at my house, it simply seems to be way more stable. 
 
Are you on to something internally? Because apart from these issue, I genuilely would like to stick to the quest... 
Up and Coming
January 18, 2024

I just tried DHCP reservation. No help.

The main issue I experience is the 6E network not showing up in the Quest 3 no matter what. It shows briefly once but then is gone forever.

My TPLink AXE5400 is Hardware V1 and in its latest FW.

No problem connecting to the 5G network.

Participant
January 18, 2024

sacco.svd wrote:

I just tried DHCP reservation. No help.

The main issue I experience is the 6E network not showing up in the Quest 3 no matter what. It shows briefly once but then is gone forever.

My TPLink AXE5400 is Hardware V1 and in its latest FW.

No problem connecting to the 5G network.


Try to give it a number pfefix, so it would be at the top of the list and you can se it easily. Also, channel 85 seems to works best for me

Up and Coming
January 18, 2024

Where do I set the number prefix?

Up and Coming
January 18, 2024

Tried 1Q36E instead of Q36E.

Just doesn't show up.

The times it did, it was close to the top anyway but connecting to it for more than 5s was not possible. Once that happens the 6E network is gone forever.

I'll receive a Galaxy S23 in a couple days, With it I could see if I can connect to the 6E network reliably or not.

Participant
January 18, 2024

Are you sure you set it right? You see static MAC of you quest 3 in a router settings of reserved DHCP?

Up and Coming
January 18, 2024

Yep. I've set the 6E saved network to "device MAC"

Added the Reserved DHCP address. Although I have no idea what IP to choose. Currently on 192.168.1.160 taken from the 5G address.

6E simply doesn't show up in the wifi list in the Quest 3.

Up and Coming
January 18, 2024

Finally I could make it work somehow. Got to even test VD a bit. Will report if is still dropping connection. Seems like if I leave the Q3 in standby mode it disconnects but when I try connecting again it stays up.

The connection oscillates between 1921 and 2401 and at some point I got screen corruption coming from my PC to VD. (The 5G radio is solid 2401)

After some more time, I left the Quest 3 in its charging base and is still connected. I still see it in the Clients List.

Here's what I did.

- Network is called 1Q36E (1 as prefix). Not sure if this makes a difference. And its settings in Auto.

- Added the network manually in the Quest 3 list. Made sure is set to "device MAC"

- Added the DHCP reserve with the Quest device MAC and I've chosen IP 192.168.1.160

Participant
January 18, 2024

Glad you made it. So, it proofs a solution for this problem, i suppose. Also, i have same games expirience with 6e as you mentioned. Bit lagy from times .o times, not as stable as 5ghz.

Participant
January 18, 2024

Unfortunately, even in theory this cannot solve the wifi problem on oculus 3, because... has absolutely nothing to do with this problem. it solves some problems of your router. Try just playing around with the Wi-Fi channels.

 

Up and Coming
January 18, 2024

So I tried playing Alyx for 1h. It never disconnected although there were some obvious connection stalls once in a while. The performance was solid but not bullet proof as with the 5G network.

Up and Coming
January 18, 2024

Here is a peculiar detail related to the TPLink router:

For the 5G network, with the TPLink router I cannot choose any channel I tried, tried 60, 120 and 128. The quest 3 doesn't see it.

With my AX86U, I could choose pretty much any channel and it worked.

Participant
January 18, 2024

Just got an reply from support, which is not reassuring at all... Telling me to restart the device and check if there are no errors in the wifi password 😞 I hate it how support of the big problems just totally ignore an obvious issue on their end. Feels so unfair... I genuily don't want a refund (only got the device for 20 days).. but now Meta isnt leaving a choice, or so it seem. The reply:

----

Hi Charlie, 

Hope you are having a wonderful day!

Thank you for contacting Meta Store Support, my name is Irshaad and I'll be happy to assist you. 

I understand that you are experiencing Wi-Fi issue's while using Virtual Desktop to connect your headset to your computer, rest assured I will be happy to look into this for you. 

We could try a few troubleshooting steps to sort this issue out and if the issue is due to a defect, rest assured we would be able to look into a possible replacement.

I understand that you are quite familiar with routers and internet connectivity but due to the nature of your query I will have to go over Wi-Fi related troubleshooting with you, please be open minded to see if these steps resolve your issue.

Does the system have an antivirus suite that is active?

  •  
    • Antivirus software may interrupt or slow down the Oculus software’s ability to access information from Oculus’ servers.
    • Does the system run on a strict firewall/proxy network configuration? Some configurations may prevent the Oculus software from being able to communicate with the Oculus servers.

Some of the most common reason to have connectivity/performance issue with the Wi-Fi are listed below:  

- Captive Portals

The network will prompt any new devices via a browser to interact with a web page, the captive portal, before allowing Internet access. Quest setup will fail on these networks; however, they may be used successfully after the initial Quest setup has been completed.

- Incorrect Wi-Fi password

The user may experience connection or authentication errors if the password for their network was not typed correctly. Advise these customers to disconnect from the network, reconnect, and reenter their Wi-Fi password.

- Dual Band Routers (5 GHz and 2.4 GHz)

We advise the user's to disable the dual-band feature of the router so the headsets can be on the same channel. This may help the headset from joining another channel which can impact the Wi-Fi signal.

Troubleshooting

  •  
    1. Restart the device
    2. Try another application to check if the connection issue is related to the Oculus app only
    3. Try another connection type (ethernet or Wi-Fi)
    4. Try checking the settings of the Antivirus software for options to whitelist or add Oculus as a trusted program.
      1. Adding the Oculus application to the antivirus software’s whitelist or trusted list should help resolve slow down or issues accessing content without compromising the user’s system integrity.
      2. Please provide this public article for additional information on antivirus software.
    5. Try a different network; one with no restrictions.
      1. Trying another network without a proxy can help resolve any slowdown that occurs when routing internet traffic through another network.
    6. Try troubleshooting network Wi-Fi issues with RouteThis Help

Regarding your concern's about the refund your device will be refundable 30 days after receiving the device 

If we determine, in our sole discretion, that none of the listed means are reasonable to correct for a defect or malfunction, then we may refund to you the price you paid to purchase the Product.

If you have further questions or concerns, please don't hesitate to get in touch. 

I look forward to an update from you.

Best Wishes, 

** redacted **
Meta Store Support

Up and Coming
January 18, 2024

Until the problem is solved by actual engineers (on either side) the support team has no way to actually help.