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

[tfosseli]

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

For video references on the issue here is a playlist in chronological order

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

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

[Mister_Y]

You're bringing up good points with this in general. The whole environment we're in here is very complex, a lot of moving parts, and I think most people, just like me, mostly judge from their go-to configuration and what they experience with that. For example, ideally everyone would be trying and comparing Air Link, VD and Steam Link (if it's about a SteamVR game) to really get some meaningful results - whether it's a third party software or not shouldn't count that much by itself (can be both advantage or disadvantage), the point that counts more is that all of them are separate pieces of software that might come with their own issues, distorting our test results. If you only test with Air Link, who can guarantee you that it's not just a bug in Air Link and has nothing to do with Wifi connectivity at all?

And then also run each test again on 5 vs. 6 GHz, wired and wireless, on 90 vs. 120 (or even 72) fps, with various bandwidth settings, on Quest 2 vs. Quest 3 (I actually would have both devices here to compare). And of course the game might also make a difference. The only other game I play regularly is NMS VR, and there I didn't see any difference with 90 vs. 120 fps, but that game rarely reaches such high frame rates anyway.

My post was kinda highlighting this by adding just another odd piece to the big puzzle that all of this is, just as the piece nixt had added before and hundred other people could do just the same.

It could mean that a setting you wouldn't expect to, can have an impact on the Wifi issues, or just the same it could mean that my lag issues (and those that others were experiencing) weren't because of the Wifi connection to begin with. Both things to consider when trying to analyze this issue.

Can't agree to your modding example though, while I have to admit I didn't compare with Air Link for this specific 90 vs. 120 Hz scenario, I kept on going back to Air Link from time to time to compare the stability during the past months, but that was never a long test, as I would run into stuttering issues within minutes, sometimes seconds, just to go back to the perfectly smooth experience with VD. I did this (and will still do) as I'd actually prefer to use Air Link for its ease of use and in general just better integration into the Meta software.

[Munkiemagik]

Has anyone got their hands on the Grandstream GWN7665 Access Point to test with the Quest 3?

I had a Unifi U7 Pro I tried out previously but didnt realise that Grandstream also had released a 6GHZ capable AP and at significantly less cost than the Unifi U7 Pro.

Tempted to give it a shot but cant get hold of it with easy return here in the UK. I cant find specifics regarding specs it but I believe it uses mediatek soc.

[11thomas22]

I have same problem with my tp-link router  the post is very informative, I will must try these options.

[Luchingador]

 recently updated to v69, can confirm i STARTED having this issue while using a hotspot with my Intel AX200 wifi card of my PC. On quest 2 the transfer speed its LOCKED 1200Mbps, on Quest 3 is LOCKED 286Mbps, UNLESS, i connect the quest 2 first and while is still connected, i connect the Quest 3, then i will get the 1200Mbps.
Before in v68 the transfer speed would be variable, between 866-1200. 

so... any ideas? other than using 2 headsets when i just want to play 1? 

[sacco.svd]

Is that over 5G or 6E?

I have zero problems with 5G and my TPLink AXE5400.

Only 6E gives me troubles so I decided to forget about it since I get the same speed (2400) the few times it worked.

5G with 160MHz channel width gives you 2400Mbps theoretic speed (actual usable in VD and Link is about 180Mbps). 

[dedmoin]

Sorry guys to revive this old thread but it seems Q3 is still one of/the best VR headset and I guess i will buy one after all. You did a great job managing the issues with WiFi and so I am coming back to the best guys to ask about the status of Q3 and compatibility with various Wifi routers.

Does Q3 still have issues with certain Wifi routers or does it work with all routers now? 

Are there any suggestions what Wifi router to use in case if it still matters?

thanks a lot

[Munkiemagik]

Ive tried so many Wifi 6E routers, currently on a Grandstream GWN7665 Access Point for my 6GHz fix. Though its not the HIGHEST constant throughput, I am seeing around 1300mbps down and 700mbps up, which is way more than enough bandwidth for ireless Quest3.

it has been rock solid and stable with my Quest 3. I am quitting while I am ahead and no more faffing around on this subject.

[what.278987]

edit - too many tabs open, wrong thread.

[dedmoin]

Sorry to bother you guys but I thought I add some experiences regarding Q3 and Wifi. (edit: ah sorry, i just found the other thread continuing the topic of Wifi issues)

Q3 still does not fully support Wifi6e as 6GHz networks are invisible most of the time. I was able to connect to my 6GHz network for 2 seconds until it switched back to 5GHz. Fortunately they have improved 5GHz network support and there it is quite stable. 

I have a new TP-Link BE550 and was following the guide by TP-Link on how to use 6GHz with Q3. BE550 is stated as being one of the routers able to connect to Q3 with 6GHz. The support tried to help me but in the end simply said 5GHz is not supported.

One week earlier I used a HMD from another vender but similar specs and same chipset. There was no problem at all to connect to Wifi 7 and 6GHz. As this HMD also used Android (but more recent version) it is obviously at Meta not being able to fix it. On the other hand it might also mean there might be Wifi 7 support when Meta eventually releases a new update.