Inspiring

Solved

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

1188 replies
383319 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

tfosseliAuthor

Inspiring

This is true though irrelevant for this bug.

The reason 6Ghz is preferable to 5Ghz, even though the range is shorter, is that it should be practically unaffected by radio interference. Also wifi 6/6e on 5 Ghz is very unstable according to TP-link who are testing in very controlled environments.

0

0culusRift

Participant

OK that is true.

Only a short tough about it.

The Q3 works well with some routers that are using known, probably more expensive Wifi Chipset and probably better adapted Firmware. Than there is a bunch of other Routers, where at least to us the exact Hardware and underlying Firmware is not known.

So it is not sure, who is to blame in this case, and on which side the correction in the Firmware must or can be made.

One additional relevant question is, how motivated is meta to solve a problem, that in most cases only affect Airlink or similar PVCR. Because we all know, they abandoned it and punch only I the standalone direction where the described bug is probably less noteable.

So i hope, they (Meta? Tp-Link? the chinese Chipset OEM manufacturer? or others.?) can first find out what is the exact problem and than fix it.

tfosseliAuthor

Inspiring

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.

It appears that the issue might be related to either Meta or Qualcomm. If you glance through the posts here, you'll notice that TP-Link isn't the only one affected; users with Asus and other AX and AXE routers are facing similar challenges.

Let's hope for a resolution soon

N

nN117

Participant

I found something new today about wifi 6e and axe75 issue. Previously i was unable to see 6e network, but today i found out that if i reboot Quest 3, i can see it at the begining, before it gets hiden like known network without connection.

So, i restarted Q3 until i was able to connect to 6e network. Few times i been able to connect, but it always disconnect after time. Once i been able to connect for 30 minutes. Speed was good, around 1900.

Then i checked my TP-link app and this is how Quest 3 looks there. Just as some random android. Even my heater provides correct information about him self!

N

nN117

Participant

So, i just had a full session with 6e. If you cant find 6e wi-fi, you should try to reboot your Q3 and immediately try to connect to you 6e network and continue clicking "connect" until you get connection to it or it disappears. If it disappears - reboot and try again. Eventually, you will get stable connection. Channel 85PCS, if it may help you.

That a piece of tech...

tfosseliAuthor

Inspiring

Try turning on experimental mode and advanced Wi-Fi setting. Then you can deactivate "Randomised MAC" in the wifi settings. That way your headsett retains the same adress.

Migth help... might not.

N

nN117

Participant

Actualy, it kinda helps. Like not fully removes the problem, but makes it a easier to connect. Thank you ❤️

H

Hopheylalaley

New Participant

I tried to do as you did, but when I reboot I see a 6E network even if I had previously added it manually by SSID
But unfortunately, after 15+ attempts I still couldn’t connect
Router tp-link axe5400 (archer axe75) was purchased on amazon.de
quest 3 was also purchased there
Everywhere all the firmware is the latest, and it doesn’t want to see a 6E network, it works tolerably at 5ghz, but I want 6E

what am I doing wrong?)

tfosseliAuthor

Inspiring

Figuring out why the 6GHz network isn't showing up can be a bit tricky, especially since it seems to be affecting only a handful of TP-link AXE users. Here's a roundup of what people have shared to help troubleshoot:

Check for obstacles! Make sure your router isn't playing hide-and-seek behind furniture or walls. Cozy up as close as possible for testing purposes while troubleshooting.
Ensure your router is running the latest firmware through the Theder APP. (Yours is, but just a heads up for others).
Run a network diagnosis to rule out any channel conflicts: Theder APP - Tools > Network Diagnostics > Diagnose. (It's a bit odd that this option is exclusively in the Theder app, right?)
Confirm that the 6GHz network has a unique name and passkey. (preferably 8+ characters with only numbers, letters and underscore)
In the Theder app, access advanced settings for the 6GHz WiFi and activate PSC. Ensure "Hide SSID" is not toggled.
Be patient! Give it 3 to 5 minutes on the WiFi settings page on your quest and see if the 6GHz magickly appears.
If it's still playing hard to get, add the network manually. Jot down the Name, Security protocol, and passkey (e.g., TP-link-VR6G, WPA3-Personal, passw0rd23), then manually add the network on your quest without scanning.

Additional Experiments:

If 2.4GHz and 5GHz are disabled and taking a nap, try waking them up and see if the 6GHz network joins the party.
If Smart Connect is disabled, try enabling it to see if it resolves the issue.
If OneMesh is activated, consider deactivating it as an experiment.

Connecting to 6GHz Network but disconnects randomly:

If you manage to find the 6GHz network but experience disconnections:

Head to the Wi-Fi connection settings on your headset. Under privacy, choose "Use device MAC."
In the TP-link web client you can try giving it a fixed IP using Network > DHCP Server > Address Reservation.
Of course, you can attempt configuring it in the DMZ (Demilitarized Zone). This essentially bypasses the firewall of your router. It's a bit risky, but you can give it a shot for testing purposes. Navigate to TP-link's web client, then go to NAT Forwarding and select DMZ. (This should in theory only mater for accesses over the internet but some users has mentioned this helping for some odd reason.)

Except for the bug of fluctuating speed (1440-1931Mbps) my wireless experience is actually quite good as long as I'm in short range of my router and in line of sight.

Here are my Wi-Fi settings:

Video of the v60 test with these settings

Hope it helps...

H

Hopheylalaley

New Participant

Unfortunately, none of the above helped, I can see the 5 GHz network perfectly, the connection is somewhere around 1800-2200+-, delays are around 40-60, i.e. 160 MHz works great, but I want 6 GHz and use the router to its fullest... The only thing left is to return the quest3 and AX5400 to the factory settings and try everything from the beginning, I have no other ideas

By the way, mine and my wife’s iPhone 15 pro max also do not see the 6G network...

iKadash

Participant

I'm kinda confused. Out of frustration i fiddled around with my RT-AXE7800 some more today and it seems i have achieved a usable 6GHz configuration. The important thing is to leave the 5GHz band enabled otherwise i'm not seeing the 6GHz band. I just hid the 5GHz band so it won't pop up everywhere. The 2,4GHz band is completely disabled. Here's the wireless and the professional config i'm running currently:

Additionally i have a MAC filter applied to both bands so only the Quest 3 can connect to the router. The connection speed itself is still fluctuating from 1700-2400 BUT no stuttering or lag whatsoever in a 2h session. Wasn't able to do that with the 5GHz band. I'm still gonna try out the GT-AX6000 as soon as it arrives.

t3chnod3lic

Up and Coming

I have the GT-AX6000 and look forward to your findings.

O

owca6666

New Participant

Quest 3 not finding your Wifi 6e (6Ghz) router?
Once you get it to connect, try this:
Go into your connection settings in your headset.
Scroll down to Privacy.
Click the dropdown and choose Use device MAC.

We're not sure why this works but it does.

Also, enabling the 2.4Ghz band seems to help with discovery as well. You can set it on low power to minimize possible interference.

This is information from virtual desktop discord for those having problems with wifi 6e.

H

Hopheylalaley

New Participant

It doesn’t help me, I’ve already tried everything, left all networks turned on, or only 6e, in router mode, in repeater mode, I don’t know what the problem is, maybe there really are some regional restrictions, I’m in Serbia

S

SimeonV

New Participant

Hi, just working through WIFI issues myself and seeing mixed messages from Reddit and here. Is the problem just with WIFI 6/6e? or does it include WIFI 5?

I went and bought an RE650 AP/Extender (running in AP mode, direct connection to PC with bridging enabled for internet access, 5GHZ Wifi 5) and it disconnects constantly in VD when in desktop mode and disconnects/stutters when playing VR games (MSFS). This is despite being 1 meter away from router. It reconnects within a few 5 seconds of disconnecting.

Trying to ascertain if it is the issue discussed here, and therefore I am waiting for a firmware update, or if it's another issue.

tfosseliAuthor

Inspiring

As of now, WiFi 5 appears to be less impacted, although I cannot definitively state that none of them are affected. However, disconnection is not the primary concern related to this bug; you may be encountering a different issue.

The bug generally 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. (For 5Ghz Wifi5 it should have full speed at 1200 Mbps.)

TP-link conducted thorough tests with various chipsets, including MTK, BCM, and QCA routers, and it seems all these routers are experiencing similar issues.

In your case, I would recommend trying to activate "Use device mac" under privacy in the headset's Wi-Fi settings. Additionally, consider assigning a fixed IP address in the router's settings. See if that helps.

N

nN117

Participant

Hi again. So, after enother succesfull session with Wi-Fi 6e, i concluded for my self, that its better just use Wi-Fi 6 , not 6e network:

1. You still get 2400mbps and they be more stable

2. Image quality is the same. BUT! But with wi-fi 6e image may feels laggy. It may be due to packet loss and mbps spikes.

3. I didn't noticed any significant llatency difference between two.

4. Its just much more comfortable user experience.

My advice, at the time just use wi-fi 6 at you axe75. Dont try to catch that edge with 6e, it doesn't worth it. I may worth if all the 5ghz channels are under load, i suppose

O

owca6666

New Participant

We’re currently having discussion on virtual desktop discord regarding transmit power of WiFi 6e in the EU, some charts indicate that transmit power on normal channels is very low, however dfs channels should have higher transmit power might be worth testing.

tfosseliAuthor

Inspiring

This is true. When it comes to the 6GHz range, the EU and US have some differences in their laws regarding signal strength. Check out this link for more info: https://www.wi-fi.org/countries-enabling-wi-fi-in-6-ghz-wi-fi-6e. The US version allows the full 6GHz to be used, while the EU version only permits half of it for home wifi.

...but... these differences shouldn't have such a drastic impact on package losses and negotiation rates. It's worth noting that I've received feedback on this bug from several US residents on my channel, reporting the same issue.

0

007x007

Up and Coming

Not only 6E have differences between EU and US. In US 5Ghz uses more wide range: UNII-3 (channels 149-165). In EU is forbidden to normal users and for "some" companies are limited to 24mW power while in US is up to 1000mW. All EU routers are locked for this frequency except some "free to configure" like mikrotik. I just tested it today and I can use that freq. in EU and Quest 3 connect without problem. This give me almost 100% chance that I'll not be influenced by other networks.

T

thrillux

Up and Coming

Quest 3 5ghz Wifi lag spiking: Strange solution (for me, anyway)

(SEE UPDATE AT BOTTOM - Didn't stick after all)

I was having the issue where every 10 seconds or so, Air Link/Virtual Desktop/Steam Link would freeze up for about a second.

I naturally tried reducing the bitrate, and a billion other things, like making sure the Quest was the only device on 5ghz, that it was using an uncontested channel, etc.

I was in Air Link after rebooting one more time, and the lag spiking was still there. I turned the bitrate down to 10mbps, still laggy. What the hell, let's try 200mbps.

Buttery smooth. Zero lag spikes. What???

This is on WiFi AC 5ghz, not a WiFi 6 router.

If this works for you let me know. I can't logically imagine why this works for me.

UPDATE: Nevermind. It's back to spiking.

tfosseliAuthor

Inspiring

That fix was probably a freak accident. I had the 10 sec spike lag issue on my Quest2. The issue there was that i was not using a dedicated network. If other units are using the nettwork you will probably get spikes because of bottleneck issues.

I eradicated that issue by getting an extender and setting it up as a dedicated accsess point. Works like a charm. I still use it for my Q3 when playing in my spear room.

When this bug is fixed I'm hoping to use 6Ghz without it. My 6Ghz is also dedicated to Quest.

S

SimeonV

New Participant

I actually managed to fix my issue I was having with the Re305 (Ac1200).

I had bridged the connection between the Ethernet (Re305) and the Wifi (Internet) so the Quest could still get internet access when connected to the AP. Second I deactivated all stuttering stopped and so did the random disconnects.

So either a sensitivity with windows bridging or something on my other network flooding the AP.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO