Inspiring

Solved

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

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

S

saccosvd

Up and Coming

That was an interesting read. So that means a "Wifi Scanner" app in your phone is not giving you the full picture?

Are those apps only measuring transmisión power?

D

darekd1977

Participant

Unfortunately, I don't have the 6GHz band on my phone, so I can't see it in the application. However, viewing and analyzing them in the application did not help me much in the remaining 5 and 2.4GHz bands.

M

mouse212001

New Participant

We shouldn't have to change any settings in our routers. Things should just work with basic settings out of the box. Its really unfortunate they haven't fixed this issues.

D

darekd1977

Participant

"We shouldn't have to change any settings in our routers. Things should just work with basic settings out of the box. Its really unfortunate they haven't fixed this issues."

I fully agree with you - but the reality is different, and what's more, the meta doesn't do anything about it, it's just a mess for now, so in the light of such facts, we can do nothing ourselves and throw Quest 3 into the basement or try to find the cause of the instability networks and have an argument in case the meta continues to ignore it.

S

saccosvd

Up and Coming

Does this happen with other non TPLink 6E routers?

M

MarcDwonn

Participant

Yes. Otherwise we wouldn't have 92 pages of complaints from users.

C

CaptainLuds

Participant

There are a few people here that think I am touting some sort of speculation around the power output of the Snapdragon. I have had enough of this nonsense. I am a professional network engineer with a focus on wireless solutions. I have a total work experience working for various integrators globally since around 1990.

That as a backdrop for those that think I make **bleep** up. The Quest 3 ALWAYS has a larger drop in Transmit than Receive Mbps when it renegotiates the speed levels/bandwidth. THIS IS A POWER OUTPUT ISSUE. Period.

Meta fix this **bleep** now! I can live with an external battery.

D

darekd1977

Participant

"There are a few people here that think I am touting some sort of speculation around the power output of the Snapdragon. I have had enough of this nonsense. I am a professional network engineer with a focus on wireless solutions. I have a total work experience working for various integrators globally since around 1990.

That as a backdrop for those that think I make **bleep** up. The Quest 3 ALWAYS has a larger drop in Transmit than Receive Mbps when it renegotiates the speed levels/bandwidth. THIS IS A POWER OUTPUT ISSUE. Period."

Thank you for being here and writing, because your comments and knowledge are very valuable. What you write about is very likely and fits into the general circle of suspicions regarding the signal stability in Quest 3.
This theory is also likely that by limiting power to extend battery life, these things are happening to the network connection.

My concern, however, is that Meta doesn't give a **bleep** about improving the stability of the network connection so that streaming works perfectly, because after all, it works somehow, and all they care about is that people sit in their Metastore and buy their games, and not some on Steam or somewhere else.

M

Mahlski

New Participant

Just sharing my experience, maybe for someone else this is helpful too.

Been trying to get Wifi6(e) stable for 7 weeks with a bunch of different routers: TP-Link AXE 75, Linksys Hydra 6e, Acer Predator Connect w6(worst performer), asus rt-88u pro. All to no avail.

Decided to try some cheap, isp provided wifi6 (non-e) access-point i had laying around

(brand: arcadyan, provided by KPN Netherlands as “SuperWifi 2.0”) mounted on the ceiling of the playroom/office.

@ 80/160mhz channels 100 tru 124 (less used channels in my area) semi decent results with hiccups when moving a lot. Although overall better than the other more exotic units mentioned above)

Due to a reboot of some kind it reverted to 80 mhz / ch 36 last night: since then zero bandwidth drops and super smooth gameplay in HLA on 120hz/godlike/av1-150 mbps with a total 36-38ms latency in Virtual Desktop

I play the game without controller turning so i’m constantly rotating physically; it remains to have a stable connection.

H264+ above 300 mbps is still somewhat wobbly at some times but that’s perhaps more of a throughput limitation of the AP.

N.b. Besides IPv4 checksum offload all other NDIS advanced settings are turned off on a dedicated NIC.

P

poodude289

Up and Coming

I did reply to someone the other day on this thread that was mentioning channels seem to have a large effect on the Quest 3 performance in comparison to the Quest 2, so maybe there is some sort of issue here.

M

Mahlski

New Participant

sounds like a proper deduction imho; higher channel no. equals higher frequency equals sh*tshow on q3 above ch 100 (pardon my french)

even when operating in clear line of sight to the router/ap, only 6e network in the area, q3 only client and phone/laptop/etc in airplane mode.

Overnight the AP switched to ch 116-> instantly stutters again.

back to ch 36-> smooth sailing

S

saccosvd

Up and Coming

So I gave "Openspeedtest" a try. It tests your private network by making a server you can access via a website with 192.168.1.131:3000

Here are my results for 5GHz and 6E. Which are pretty similar but 5G wins. I ran them multiple times and there were no hard dropouts on either network. (TPLink AXE75 router)

5GHz network.

6E Network.

W

Warja

New Participant

1. Router: Asus RT-AC68U

2. Router firmware: 3.0.0.4.386_51668

3. Headset version: 60.0.0.216.366.554098976

Specifically steamlink works perfectly on my kids' Quest 2s, and is unusable on my new quest 3

@MetaQuestSupport

C

CvdZwan

Participant

Update. I think I made my quest 3 + virtual pc work, at least, I had 2 nights of near flawless vr sessions so far.

When I bought the quest 3, I also bought the TP-Link Archer AXE75 wifi 6e router. And with this combination I had many stutters and the mbps range dipped to from 2400 to 1200 occasionally.

Since I thought it was a qualcomm chipset and quest 3 issue, I refunded the tp-link and bought the more expensive ASUS AXE7800 WiFi 6E. I did find a good online deal, so it didnt cost me the full 250-300 USD price. I found a 200 USD deal).

I am running the router in access point mode (dedicated, just for the quest), using channel 37 and have PSC enabled (to make sure it gets detected, while i am not 100% sure it helps).

The router is around 1,5 meter / 5 feet away from me.

While the signal still fluctuates from 2100 to 2400, is does seem to give me a stable experience. At least, the last couple of play sessions.

I think this expensive router is overkill, and I could have done it way cheaper by experimenting more with cheaper routers and settings.

I'm not sure what the connection is between the fluctuating signal strength and the stuttering. Maybe I'm overcompensating for an oversensitive attenna or firmware issues from the quest.

Or perhaps WiFi gaming remains a difficult task, regardless of the device. At the moment I am very unsure about the causes. I was thinking of borrowing a pico and testing the differences.

0

0culusRift

Participant

In relation to the invest for an proper VR PC, 200-300€ is not that pricey for an stable Wifi solution, that can also improve other Wifi Devices in your household. It is very comfortable, when all the IOT devices are available 100% of the time and Alexa don't tell you again and again that your light is not available at the moment. Your personal situation may differ.

C

CvdZwan

Participant

Makes sense. The one think that confuses me is why the Quest fluctuates so much compared to the quest 2. It really seems that the fluctuating thing is Quest 3 (hardware/firmware) related. Im standing so close to the router.

H

hardhotsweet

Up and Coming

So my wifi router supports wifi 'smart connect'. Basically, as an example, you have the same AP name and password for 2.4ghz, 5ghz, 6ghz. The router chooses at any given time which band will provide the fastest speed to the client. But the Quest headset has some issue with this. The headset often complains it lost the wifi connection but a split second later it's back online. I'm guessing the Quest headset wants each AP to be a certain band. Is there any planned support in the future to play nicer with this router setup?

https://www.asus.com/us/support/FAQ/1012132

0

0culusRift

Participant

It it absolutely not recommend to use this smart connect, because first, you never know with witch Network you are connected, and second, you can get into trouble because your smart router or client can decide randomly to switch the Band and this leads in every case to lags or disconnections.

S

saccosvd

Up and Coming

So my Galaxy S23 arrived.

I turned 6E on in my TPLink AXE75 and the phone had no problem whatsoever to see the 6E network. No problem connecting, turned Wifi several times in the phone, quickly jumped between 5GHz and 6E multiple times. Connects super quick and didn't fail even once.

Tried also OpenSpeedTest and it shows 985 DL / 913 UL and 0.4 Jitter.

I think this test kind of clearly shows that the problem is on the Quest 3.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO