cancel
Showing results for 
Search instead for 
Did you mean: 

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

tfosseli
Adventurer
  • 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 @MetaQuestSupport 
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-th...
 
 
pagerip.jpg
 
 
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 @MetaQuestSupport 

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-th...

 

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. 

 

@MetaQuestSupport 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-Br...

 

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 @MetaQuestSupport 

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

1,135 REPLIES 1,135

itsjase
Explorer

Has anyone managed to test with v60 yet? I haven't gotten the update on my headset yet

Packet loss seems to be the primary issue here which can cause stutters and frame drops. See the video in OP's post comparing Q2 vs Q3 in various firmwares. 

V60 Have the same problem.

 

banchan.sprint
Honored Guest

Before v60 came out, I had the same issue. The networking latency is very unstable and fluctuates between 10 to 150ms. After a factory reset, it worked perfectly. So I put it down and went to sleep. On the next morning, it returned to what it used to be.

A day later, v60 was out. This was what I got without a factory reset after the first launch. I had never seen a 25ms total latency. The networking latency is solid 4-5ms very stable.banchansprint_0-1701954441944.png

However, history happened again. I went to sleep and redo the test the next morning. The latency becomes unstable again. About 95% of time, it can hold up around 10ms.

AX1800AX1800
But somehow it will shoot up to 150ms, just like v59.
banchansprint_3-1701954994643.png
I have 2 routers: one is ASUS AC86U(Home use), another one is a tp-link AX1800(dedicated for VR)

007x007
Protege

Just got Asus GT-AXE16000 (Europe). Quest 3 can't find WiFi6e. 5Ghz is not stable. Jumps between 2100-2400Mhz. Don't bother and try to find BEST router. I had same problems with MikroTik router too. It's Quest 3 problem. Wait for Meta update or return Quest 3 as non functional device. Hope is software problem, not hardware (WiFi module).

Its not only a Quest 3 problem. It has to do with the region also. Many routers (including yours) do not have such problems in USA. 

People who live in EU countries do appear to be having the most trouble, I know the broadcast regulations there are more strict than USA

Sure, but when I buy device which have wifi 6e support I expect to work with wifi 6e router 🙂 I buy Quest 3 on EU market directly from Meta.

 

Edit. Just connected 2 times to wifi 6e. But got disconnected after 1 hour. Quest see wifi 6e randomly. I'm 1,5m away from router. I have tried different freq. It's just random, but chance to see 6e is like 1 to 100. So it's not broadcast requlations problem in EU for sure.

ymo1965
Expert Protege

I'm in the UK and I had this issue. The Asus GT-AX6000 router certainly helped, but one other thing I had to do was disable the VPN. It really does mess things up. That was the main wndows app I had to shut down first. So if you have a VPN running, try diabling it. Kudos to Ruined for originally mentioning this weeks ago.

HFMudd
Honored Guest

Hello, i have an AVM Fritzbox 7590 router (2.4 and 5 GHz, no wi-fi 6!) and i also had connection problems with my Meta Quest 3 (firmware version 59.0.0.172.706.535429038). The Quest 3 lost it’s wi-fi connection every 2 seconds so that no download was possible.

I tried a lot without success but when i connected the Quest with my guest WLAN i suddenly had no connection problems anymore! I have a stable connection with 900-1300 MBit/s on 5 GHz! Maybe the reason is that the Quest is currently the only device connected to that WLAN? Maybe it has problems when there are more devices in the same WLAN because of the collisions?