Inspiring

Solved

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

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

t3chnod3lic

Up and Coming

Ive been saying this for ages. Brilliant Idea. Drop it right in Zucks's lap and see how he responds... though I can make a good guess.

C

CaptainLuds

Participant

Done.

Let’s wait for a response. I linked the thread and asked if we can expect something soon.

D

darekd1977

Participant

Some of you are probably wondering why I'm so upset with meta and its approach to its customers due to the 6GHz problem.

That's not the only thing that annoys me about this company.

Some time ago, I described the problem with the 6GHz network and asked for corrective actions to be taken or, if the device is defective, to be replaced with a defect-free one. It is known that the more such reports, the better.

The answer I received really raised my blood pressure, who do they employ there? I asked myself when I read it. How can I not say bad things about this form and that it is a bunch of idiots:

"If you receive an error when trying to connect to Wi-Fi, you may need to connect your headset to a different Wi-Fi network. Here are some possible causes of Wi-Fi problems on your headset:

Captive portals: A captive portal is a website that prompts you to interact with it before connecting to the Internet. They are commonly used by public Wi-Fi networks in businesses, airports, hotels, and other places that offer free Wi-Fi hotspots. This type of network will not work when setting up Meta Quest 2 or Meta Quest, but may work after initial setup.

Weak signal: If the Wi-Fi signal is weak, the headset may not detect it. Try moving closer to your router (internet connection device) or switching to another Wi-Fi network that has a stronger signal.

Incorrect password: Make sure you entered your Wi-Fi password correctly. Disconnect from the network, reconnect and enter the Wi-Fi password again.

Before you start troubleshooting Wi-Fi issues, restart your headset to see if this fixes the problem. To do this:

Hold down the power button on your Meta Quest headset.

Continue holding until you see a prompt in VR to restart the headset.

Select Restart and then try to connect to Wi-Fi again.

To change the Wi-Fi network your headset is connected to using the Meta Quest mobile app:

Turn on your headset and open the Meta Quest mobile app on your phone.

Tap Devices in the bottom menu, then select the headset you're currently using.

Click Wi-Fi.

Click the new Wi-Fi network you want to connect to and enter the password if asked.

Click Connect to Wi-Fi".

The real hit number 1 is the tip to check if your network password is correct!!! Because you know perfectly well that the more correct the password, the faster and better the WiFi network will work!!!:) If, for example, you make a mistake and enter 50% of the wrong characters when entering the password, your network will work 50% slower. :))) He's just an idiot...

Hit number 2 for 6GHz network stability issues is the following tip: If you get an error when trying to connect to Wi-Fi, you may need to connect your headset to a different Wi-Fi network. So if the 6GHz network doesn't work, you have to switch to 5GHz, if 5GHz doesn't work either, then switch to 2.4GHz, and if no network works, you have to connect the cable! Easy? Easy! :)))

And the failure was fixed, and we write and discuss so much here, and it was enough to write to the finish line, where some very smart (idiot) took care of the problem and solved it the first time..

I am used to and expect much higher standards of customer service in today's world, and certainly not reducing every person who writes to such a form to the level of an idiot.

tfosseliAuthor

Inspiring

They gave in and reinstated Chromecast casting.

https://communityforums.atmeta.com/t5/Ideas/Re-Enable-Direct-Casting-to-Chromecast/idc-p/1133462/highlight/true#M36083

The root cause of users are experiencing poor casting is entirely unrelated to the absence of "official support by Google." Since they are operating on the Android platform, inherent support for Chromecast is essentially integrated.

The issue is regrettably much more severe...

I'm betting my shirt that this is related to our issue. If users experiencing Chromecast problems check their Wi-Fi, it is likely to register below 400 Mbps and has fluctuations.

LunchAndJosh

Inspiring

D

dervilrus

Participant

Sorry for my bad english

- Mercusys MR90X with OpenWRT (ax6000, 2.5gbe port, Panama wifi region for disable Radar detection, 1 client Oculus3). Channel 116. Width 160 MHz.

- Oculus 3 60.0.0.214.366.553497759

I figured out a little about what might be the problem with AirLink lags. For some reason, the WiFi speed periodically drops catastrophically. My normal connection speed is 2400/2400 mbit. Because When everything is ok, the download/upload speed is 1650+/1650+ Mbit. But periodically, especially after hibernation mode, the speed drops to 300/30 Mbit(Although the connection speed continues to show 2400/2400). The download speed is severely limited and the data transfer speed from the oculus to the computer drops catastrophically. Therefore, severe lags may occur, especially when casting from the oculus 3 to the computer. I also noticed very strong variations in the behavior of the helmet depending on the channel. Let's say on channel 100 the speed drops very often, and on channel 116 quite rarely (although both channels are essentially included in the same 160 MHz range). So you should also experiment very carefully with the choice of channel. Changing the standard forcibly to AC or reducing the bandwidth to 80 MHz fundamentally does not change anything (except for reducing the original normal speed)

What did I do? I installed FTP server with autoloading on the oculus and before starting the game on the oculus 3 I check the download speed from the oculus. (Any client, I use far manager) If the speed is bad (3 MB per second), then I reboot the oculus. Sometimes the speed is not restored the first time. Another option is to install the iperf3 server on your computer and check the connection with oculus using the Magic iperf program.

It should also be noted that I observe this behavior only on Oculus 3, with other clients everything is ok. There are a lot of posts on reddit about the not very good wifi of oculus. But as practice has shown, it does not always work poorly, but only periodically. I really hope this will be fixed in future firmware.

I also found out that you don’t even need to restart oculus 3, just turn off and immediately turn on wifi. Sometimes not the first time, but the speed is restored.

But I have no problem with the displayed speed. It always shows 2400/2400 for me. The problem is with the actual transmission speed. And I repeat once again, oculus 3 sometimes works just perfectly, and sometimes the speed is catastrophically low, the problem is somehow related to an incorrect connection and can be solved by reconnecting wifi.

P

poodude289

Up and Coming

+1 to channels heavily influencing Quest 3 speeds which the Quest 2 did not

t3chnod3lic

Up and Coming

Things have improved for me greatly. I am embarrassed to say I didn't exactly have everything setup right, like a right royal idiot 😕

For starters I didn't exactly have the right codec selected within the virtual desktop pc app. I had it set to 'AV1-10bit (Quest 3). Didn't realise this is for Nvidia 4000 series only (I have a 3080, doh!). I tried them all but settled on 'HEVC-10bit' and able to run 200mbps within the Quest 3. Also I had some options set on the AX6000 that I didn't realise would make such a big impact. I had the 'Game Acceleration/Gameboost enabled. Turning this off and just relying on the wifi settings fixed everything. So easy to muck things up and not realise. Hope it helps someone or sparks some idea's up. Btw, 2.4ghz wifi is also enabled for other stuff and not effecting anything else.

F

Flobud

Up and Coming

Well good for you but VD has no connection with the issue since it happens without it.

I'm pretty sure you still have bitrate drops when shaking you're head left and right. It's just a bit better since the last update. Unless they definitely fixed it with a silent update of course. I'll try stress testing it again on my side.

M

MarkWentWalking

New Participant

Quest 3 - 5ghz Random WiFi disconnections.

Quest 3 - 2.4ghz Solid no dropouts.

For me a 5ghz connection will drop out at least once every 20mins if not more. Frustrating as it crashes any apps needing a network.

Please add me to your huge list of customers who are experiencing this issue.

O yeah fix it soon.

tfosseliAuthor

Inspiring

Hey guys?... Something has improved...

Where I before could not get a full signal even inches from the router, it now shows 2401/2401 at 1 foot from the router. Occasionally dropping to 2100 but generally stable.

Moving back 3 meters to my desk, it drops to 1900...

And at that point, I fear it's no longer faulty software, but as people have pointed out... pore design and antenna placement.

Please try to move your headset inches from the router while monitoring the connection speed and see if you experience similar signals.

Version 60.0.0214.366.553497759

Runtime Version 60.0.0214.366.553497793

OS Version

SQ3A.220605.009.A1

U

Urchin80

New Participant

I'm having the same problem using an ASUS RT-AX55 (AX1800). I've tested on Virtual Desktop, Air Link, and Steam Link. All of them do the same thing with the stuttering. It might work very well for 5-10 seconds, then a brief hitch. Some situations cause it to happen more often than others.

Windows 10
32GB RAM
Geforce 4070
ASUS RT-AX55 (AX1800) hard wired to computer, used ONLY for the purpose of VR. We have another router for the household. This is in the corner of my room about 6-8ft from where I play. There are no obstructions.

2.4GHz seems to work fine but it looks considerably worse, so I haven't messed with this beyond testing
Link cable. Seems to work perfectly, but it's a pain if I want to play something where I'll be turning and get tangled up.
5GHz Virtual Desktop - In desktop mode (not in a game) everything seems to work very well. It could just be that I haven't noticed the issue. I don't spend much time in this mode.
5GHz Any Method in games. Same issue as others. Constantly fluctuates between a good framerate and then hitches. This may happen every 5-10 seconds, or in some situations could be MUCH more frequent. This is unplayable due to causing motion sickness.

Sorry that I can't offer any solutions. I figured the best I can do it throw in a "me too" to help Meta realize that this is widespread. Also, thanks to the OP and everyone who is contributing to find a solution!

E

escruting

New Participant

Hi guys, just a quick message. I was having the same stutters like you are describing but I saw that for two weeks on Christmas it didn't stutter. Then when the stutters returned I started thinking that maybe on those two weeks some neighbor wasn't at home and that made my wifi more stable. Yesterday I changed the wifi channel and the connection became 99% flawless. I thought i already was on a free wifi channel and that my building was not very congested, but i checked with the software Netspot and it turned out that my other main router was in the same 80mhz channel and the neighbor next to me is also on the same channel.

I used this image:

You see, the 80mhz channels are 42, 58, 106 and 122. Those also have the 40 and 20 mhz channels inside. I had the 108 channel and my neighbor had the 100, and because those are all on the 106 80mhz channel, it was stuttering. I changed to the 116 channel that is inside the 122 80mhz channel and it solved the stutters almost perfectly because no one around me is using it (I also tried the 42 and 58 80mhz channels but those were stuttering too). You can also limit it to the 160mhz channels, but because it has even more lower channels inside, it didn't help to solve the stuttering (even though the bandwidth doubled from 1200mbps to 2400mbps).

Maybe I'm dumb describing this in this way and you all know this, but I hope this helps someone as it helped me. I'm now playing Half Life 2 VR mod without stuttering.

Router: Asus RT-AX57

V

vrarena22023

New Participant

Can somebody replicate this?

M

MrRobotG

Participant

This isn’t the issue. They had another device on the same band which caused interference and stuttering. The issue we are seeing is the transmit/receive speed is dropping off dramatically within metres of the device even on 6ghz where there is no one around us on the same band. Which ‘seems’ to indicate it’s a hardware issue

D

dervilrus

Participant

I also don’t agree that it’s just the antenna. For me, if Quest 3 connects to WiFi normally, then the speed remains excellent for a long time (1.5+gbps/1.5+gbps). For me, the problem is solved simply by restarting the helmet/re-initializing wifi, which indicates a software problem. If the connection is normal, then the connection is good throughout the room throughout the entire time. But I have a router with OpenWRT and it can output good Power.

S

saccosvd

Up and Coming

In my case is more severe. (Also Quest 3 and TPLink AXE5400)

I can see the 6E radio intermittently and connect for a short brief but never got enough connection time to even try VD.

With the 5G radio works just fine, as good as with my AX86U. Two 3h Alyx sessions, no hiccups.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO