Inspiring

Solved

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

1188 replies
383322 views

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.

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

What version is your headset running? (Full number, i.e. 57.0.0.####)
- Quick Settings > System > Software Update
Which router do you currently have?
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.

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

---

Here is my video on testing version 60

tfosseliAnswer

Inspiring

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

Show previous replies

M

MrRobotG

Participant

I’m not saying it’s not a hardware issue, but I would suggest that we wait for the user that stated their gf’s quest didn’t have the issue comes back with some detailed test results.. for example video showing the transmit and receive rate doesn’t drop when moving in the same room within a few metres

skylanet

Participant

A week ago I've posted that my Quest3 WIFI speeds with Asus RT-AXE7800 was really fluctuating too much. I've had my router near my TV approx. 3-4 meters away from my PC desk. Now I have moved it on my PC desk, so now it's approx. 1-2 meters away, depending on where I am with my Quest. Now it works really great and I have no problems with fluctuating WIFI speeds anymore. I have almost constant 2401 Mbps speed. Sometimes it drops to 2161 Mps, very rarely to 1921 Mbps and I didn't noticed any lower speed, even if I've moved further away. Maybe it was my old TV (not WIFI) that somehow interfering with my router electronics or maybe it was just wrong place in my living room (I'm in apartment building) where I've placed the router. Anyway, now it really works as it should. Yesterday I did a 3 hour flight in MSFS without any stuttering or audio distortions.

These are my router WIFI settings and I have set my Quest to a dedicated IP (not DHCP) with Use device MAC (not random):

O

Outrunne33

Up and Coming

my q3 according to wifi settings is locked at 2400mbps on receive, but transmit moves between 800 and 1900.

On my q2 ive never looked at this stuff, so unsure how it would have compared.

C

CaptainLuds

Participant

I can tell you: 1200Mbps (solid as a rock-ZERO fluctuations)

M

MrRobotG

Participant

From the testing I’ve done with the latest meta firmware and the TP-Link AXE5400 it ‘appears’ like it’s a hardware issue related to the antenna. I say this with no background in wireless hardware and based on my own limited testing.

but what I’m seeing is if I stay still in the same place the transmit and receive speed stays the same. The closer I am to the device the higher the speed, the further I move away the lower the speed. This is all expected behaviour except for the fact that it’s dropping so quickly at very small distances ( like 3 meters ) this indicates to me that the antenna in in the headset is just really a weak or positioned in the headset in a way that the other components of the headset are interfering with it.

like I said this is really just a guess

D

darekd1977

Participant

This means that the darkest suspicions are confirmed that Quest 3 has a manufacturing defect and that it cannot be eliminated by updating the software.

Well, someone simply assumed that since the 5GHz memory worked previously, if 6GHz was added it would also work properly, and no tests in this direction were carried out.

It's just like the Elite strap with an extra battery. It worked on quest 2, so the new one will also work on quest 3, but it turned out that it didn't work and that the sale had to be stopped and replaced (which I did with my belt after very difficult conversations with the completely unintelligent customer service in the meta) and only the new strap seems to work properly and does not disappear from the information about the additional battery.

I am horrified by the negligence of such a large company Meta in basic matters and how it tries to sweep this serious problem under the carpet by remaining silent about the defect in the operation of WiFi 6e, without making it public that such a problem exists and that they are working on it solution, finally removing the ability to select anything related to network connection from error reports! This looks like one big scam to people!

ps.

I also want to note that quest 3 has one centrally located antenna above the CPU, and perhaps for greater stability there should be 2 antennas on both sides of the device...? After all, it is a device in which every user moves rather than a computer that statistically stays in one place.

Update:

Please note, compared to quest 2, that the antenna is located at the bottom of the goggles and there is absolutely nothing on the front cover that could somehow interfere with the wifi signal, it can reach the antenna from various sides, including from the bottom - many people have routers located lower than head level.

In Quest 3, the antenna had to be moved up due to the sensors and cameras installed in the front cover. The signal may already have a difficult path to this antenna due to interference from these components, especially if it runs from the bottom. These pictures really make you think.

So in quest 2 the antenna is at the front and from the bottom, which in my opinion is a better location for it. In quest 3, the antenna is in the center above the CPU and in addition, there are other components in the front below it.

M

MrRobotG

Participant

My post doesn’t confirm anything, I tried to make that clear.

a scientific approach needs to be taken to testing. one person ( me ) making a guess based on my unique experience in my unique environment doesn’t confirm anything. It simply creates a hypothesis for testing

0

007x007

Up and Coming

Meta now is in "Depeche Mode" mode: Enjoy the silence...

t3chnod3lic

Up and Coming

"Words are very unnecessary.. They can only do harm" ... Just like the lack of real customer care.

Ive just ordered another headset from Amazon. Coming tomorrow. Sometimes you have to take matters into your own hands and deal with things only you know how. Brute force and ignorance.

If it's a better headset then I'll swap them and return the bad one. Then get refund... If it's another bad one, I'll try one more time. Cheeky I know, but better than the dog poo response we've had lately. Fingers crossed..

C

CaptainLuds

Participant

***Obsolete*** So now it turns out the Link Cable does not have proper audio return operational at present. With WiFi speeds being inconsistent and no audio over cable the headset is USELESS AS **bleep** for anyone interested in using it for racing simulators. Good God META, what kind of company are you? This issue, it turns out, is also months old. Just mentioning this for anyone on here having hope anything will get fixed quickly, IF at all. I am fuming. ***Obsolete***

A simple software uninstall in full and subsequent reinstall restored full audio functionality. Still annoying.

T

TomCgcmfc

Honored Contributor

Captain.Luds wrote:

So now it turns out the Link Cable does not have proper audio return operational at present. With WiFi speeds being inconsistent and no audio over cable the headset is USELESS AS **bleep** for anyone interested in using it for racing simulators. Good God META, what kind of company are you? This issue, it turns out, is also months old. Just mentioning this for anyone on here having hope anything will get fixed quickly, IF at all. I am fuming.

I'm not currently having any problems with audio using Link with my Q3 or QPro with v60. Maybe follow the meta support troubleshooting tips and/or do a bit of googling.

https://www.meta.com/en-gb/help/quest/articles/fix-a-problem/troubleshooting-oculus-link/sound-issues-with-oculus-link/

Otherwise, contact meta support I guess. Good luck mate and cheers.

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers

C

CaptainLuds

Participant

**deleted**

tfosseliAuthor

Inspiring

I'm baffeld... baffeld... Meta removed casting because it was not "reliable".

It's not chromecast it's your Wi-Fi...

This is some BS ditch effort to hide this fact, and on the fringe of elegal to remove functionality.

(Trying to keep calm) 😤

https://www.uploadvr.com/meta-removing-tv-casting-quest/

I just bought a chromecast to my nephew for casting

A

Alphy81

New Participant

"Olson Johnson is right! What kind of people are we anyhow? I say we stay and and fight it up!"

S

SteveJaye84

Participant

So I have been trying to figure out my wifi issues with my quest 3 since I opened it up on Christmas Day. Countless hours trying to figure out why some apps like big screen would stutter and freeze up every 30 seconds or so. Factory reset router… tried every option I could think of with the settings and it refused to work properly.

The router in question was a TP-Link AX20.

I removed it from my network and used my isp modem/wifi router and it was solved 100%. Zero issues now. It’s only wifi 5 but it’s fine to use as they solve this issue hopefully soon.

D

darekd1977

Participant

Interesting fact for users of the Asus GT-AXE16000 router.
After turning off the UM-MIMO and Universal beamforming options, there is a visible improvement in the stability and predictability of the 6GHz network.
After starting Quest 3, the 6GHz network is found faster or there is a connection immediately, and during use there are almost no discrepancies and there is no network floating, and therefore no disruptions in the smoothness of the image.
I encourage you to also try it on other routers equipped with the same options.

R

Ruined

Inspiring

Worth mentioning though, if you disable UM-MIMO and beamforming on a radio that has anything else but Quest 3 attached, everything else will likely suffer in performance with those options disabled

D

darekd1977

Participant

Well, no, because my Surface 9 pro also sees the 6GHz network almost constantly with this setting, and even after startup. Previously, on Surface, the network was invisible for up to several days and appeared occasionally.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO