Quest 2, 3 & Pro - Connectivity Issues

I doubt it, or the people who subscribe to the test channel firmware would have said the issue is already fixed there. 

There's a reason I don't subscribe to test, because I want my hardware's core features to work without fail, yet here we are weeks later and not a fix in sight. 

It's gone rather quiet from the Meta support side, it feels like us as users are just left to troubleshoot ourselves and are otherwise abandoned. TheLegend27 would you care to comment?

I can confirm that I don't have now any wifi deconnection following the previously explained solution. All is good under FW64

Here is a more detailled explanation for this solution that has been validated during several hours but only for PCVR using Virtual Desktop and use of DCS and MSFS2020:

1- Environment: 

a) An internet server is connected by LAN ethernet to a wireless router (in my case a TP-LINK Archer 5400 6E)

b) This router is connected through a 1Gb ethernet cable to a PC hosting win11 and the simulator games as well as the Virtual Desktop streamer application

c) the Quest 3 is connected wirelessly to the router  first using its internal software and then VD app

d) The internet server connected to the external internet world is providing local network IP adresses to all my local network through its DHCP service (192.168.x.xx) and so to the PC, the TP-LINK wifi router and the Quest 3

e) The local adresses that are usually variable through various timely power on/off phases of various local connected equipments are made fixed by internal programming the internet server (a dedicated application must be provided by your provider for that and to manage server parameters) I can't help more on that

2- Aim: 

Obtain a stable and wireless PCVR link between the Quest3 and the wifi router connected to the PC by creating an exclusive and stable wireless link between them through a mutual exclusive recognition

3- Solution

1. make sure of the point e) above is reached, take note of all relatives fixed local IP adresses for PC, wifi router and Quest 3 as well as internet server gateway IP address
2. on the PC, open a browser and reach the URL 192.168.x.xx relative to the wifi router in order to reach its parameters, then I can't help much as it is very much linked to the type of wifi router but:
3. select only one type of network (in my case 6Ghz)
4. activate the auto best channel search
5. switch wifi router DHCP function off and create a dedicated link with the Quest 3 using the mac adress and the IP local address delivered by the internet server to the Quest 3 (you can find Mac adress in the inside parameters of the HMD under the form xx:xx:xx:xx:xx
6. be sure the Quest 3 has only one network account to connect on in its network list (forget all possible direct wifi account with the internet server keep only the one with the wifi router)
7. be sure the PC has no wifi link (wifi off). It must have only a LAN link with the wifi router and be connected to internet through it by cable
8. in the Quest3 click on wifi, select the network related to the wifi router, click modify and deselect the DHCP mode to create a direct link using:

IP local adress of the wifi router(192.168.x.xx)

Gateway IP adress of the internet server (generally 192.168.0.1 or 1. 1

Using 24

DNS= gateway adress

Then the wifi must show "connected" to the wifi router in the Quest 3 basic parameters with the dedicated small wifi icon activated in the summary bar, then you can access to the Virtual Desktop app inside the Quest 3

Well it looks like I was way too optimistic, after 2 days without problems, it seems that a new update broke the statu quo. This evening I encountered at least 5 wifi lost connection and sometimes but not always fast reconnection, in 1 hour with my wireless router while flying an Apache in DCS on my 6DOF motion platform leading to brutal crashes….That began by lot of difficulties to connect as usual (I changed nothing to my network configuration) and curiously, the network account used asked me to register while usually it asks for connection…..at the end I suppressed the account and recreated it without more success and never obtaining the request for connection but only register and always suffered the déconnection, sometimes it was written registered or connected but without internet link……..I tried also the new boot next step will be the factory reset but the HMD just informed me that a new FW was loading so I will investigate tomorrow. Whatever this is really a serious problem….

The changes you made were partly like mine. I didn't write them down here anymore because I wanted to see if they worked for more than a few days first.

For almost 2 days, everything was fine. Then, the problems started again.
What I found out is the following:
It has nothing to do with resetting the headset, DHCP, DNS, Gateways settings, or other devices on the network... or whatever you change in the settings in the router, in the headset... what channel you use...!

Suddenly, some changes seem to fix the issue, but then the errors come back without any further changes in the next headset startup/reboot..

So, I changed everything back to normal. The only thing I did during those days was turning the Quest3 on and off.

Result: Sometimes it works perfectly after a restart, but then the next few Quest reboots: connection errors are back every 10 minutes.

It seems like nothing I do makes a difference. The only thing that helps a bit is turning off notifications/do not disturb so I don't see the "WiFi connection lost" message, even though I still see the connection problem in "bell".

I wish I could return the headset, but I've bought a lot of software through the Meta Store.

The errors have been present since v64, still persist in v65, and were non-existent in v63 and prior versions.

And Meta: It's not funny that this topic is now labeled "solved" when nothing is solved! 

Totally agree too, this issue must be so unimportant to Meta that their course of action is to make no further communication to the users affected by the issue. Even directly tagging in the mods/admin of the forum has not generated a single response. This entire discussion should be sent to VR news websites for publication to gain traction and embarrass Meta into action. I have to be honest i did expect a response from Meta by now. Disappointing to say the least.

I agree with you, I noticed exactly the same behaviour, few days ok then problems but I never had such amount of déconnections as yesterday evening…however, I don’t agree about your conclusions, even if putting off then on the HMD has probably indirect effect by reinitializing the wifi card, loss of wifi is not a hardware issue as it was working fine with 63, so it is a SW issue linked to the management of the wifi card or of the environment or of the protocol of excganges. It seems internal software is based on Linux and I remember some identical behaviour with my raspberry at a time. What is curious is when I connect directly to my main wifi 6 network, in 5Ghz, the one that feed all my IOT, connection is immediate and stable. So could be a problem of management of the 802.11 ax or 6Ghz. Next step will be configuring my dedicated TP link router in wifi 6 in 5 GHz to see what happen and also to check a different protection protocol of the wifi 6E in place of the wp3 personal going back to wp2 because this is a difference between my main and dedicated router and can also lead to loose of link.

But yes META unsolve this problem in the thread because it is yes present and please help users to solve it by identifying what differences in the FW64/65 vs 63 relatively to the wifi network….

This is not a WiFi 6 problem, it also affects WiFi 5 . A lot of users of my VR Community are reporting this mainly with different AVM Fritzbox Models here in Germany. A lot of them are using their smartphones as a hotspot between to circumvent a direct connection to the affected router. One of them reported this Wednesday that the v65 has sorted it out for him. I can't crosscheck it since I am still on v64.

For me it is definitely a problem Meta introduced by v64 somewhere within the WiFi protocol. On my ASUS router everything is okay, my AVM 6490 produces droppings every 10 Minutes.

Yes, that's what I mean.
The reboot happens to have an effect. sometimes. My conclusion is also that it is a SW problem since the v64 update. In an area we can not access without rooting the device.

The Quest 3 is an normal Android 12. You can get to the Android settings of the quest if you activate the developer mode of the q3. But the additional settings there like wipe the wifi had no effect there either.

I also already changed standards and encryption protocols of the wireless networks. Nothing. You can also find various messages about people trying all these things on reddit. with the same results.

One thing that had the best effect was using the guest wifi for the quest. But in guest mode you cant access the wired connections like the pc.