Quest 2, 3 & Pro - Connectivity Issues

[Gunstar_Tony]

Hi everyone,
I have a Quest 3 and cannot connect the the wifi (it's a freebox, french internet provider).

Steps i took to troubleshoot : 

• I did manage to connect the quest to my cellphone via hotspot.
• I factory reseted the quest and retried to connect to the freebox via passwords and QR code.
• I trued to connect the quest via the phone app.
• Rooter was rebooted, i was in the same room etc.
• We have all other devices connecting without problem to this rooter.

Thanks for your help

[MetaQuestSupport]

Hi @ireallylikerobots,
 

Thank you for sending this with us and we understand that you have done the factory, however you cannot still connect the Quest to the WIFI. This is not the experience we want you to have.

Please could you send us a private message so we can assist you further. To do this, please click "Send a Message" to privately message us! Please select our name to get to our profile page, or click here.

Please remember, you must be signed into the community first to send us a private message. We look forward to your reply. 
 

[george_atburro]

Have a wifi issue with headset! Drops out constantly with Deco M4 mesh network. Tried connecting direct to my Zyxel EX3301-T0 router same issue constant disconnects sitting right next to the router. Only mobile hotpsot is working for me at the moment!  It worked initially when I purchased the item. Update broken something?

[paul.frampton.754]

@george_atburro 
All I can suggest is if you're still under warranty, get a refund and buy another headset.

This has been going on for many months now. It's never going to be fixed, IMO. They've broken something and either don't know how to fix it, or don't care enough to fix it, as it's a minority of users affected. Like you, mine used to work fine, but now it drops out of Wi-Fi every twenty minutes or so.
Remember Meta, we are future lost sales.

Good luck.

[moijjo]

not all doom and gloom, I have managed to fix my situation, for me, this was a network connectivity error with Meta servers thanks to PiHole being overly aggressive. For whatever reason, when pinging meta home servers fails, the whole device wifi is out of whack. It seems that it calls home as a check to verify if WiFi is solid and disconnects if it fails. It seems that it periodically checks calling home and that causes the disconnect when it fails calling home.

For me, it's still a bit of a problem, since I do have packet loss sometimes on my ISP and that results exact same outcome as blocking Meta home servers with PiHole. 

So probably, whatever fix they did way back when this thread started, is not actually related to WiFi drivers but more related to how Meta Horizon OS verifies and measures and decides wifi quality that is the problem.

Hopefully it helps, might be fixed in latest versions, as I have not experienced this problem on V70 and V71 but you never know right?

[MrScottBull]

I'm banking 99% on WiFi, worst us the are people with Pro headsets that it's affected.

"Hopefully it helps, might be fixed in latest versions, as I have not experienced this problem on V70 and V71 but you never know right?"

Yup, never underestimate their ability to faff things up, lol.

[LinusWP]

A couple of weeks ago, my Quest 3 started to drop any Wi-Fi connection after a couple of seconds. Resetting the Quest or the router didn't fix it. (Prior to that, I was already dealing with randomly losing connection for a couple seconds every once in a while). What eventually fixed all my problems was asking my ISP to enable dual stack for my Internet connection, which meant I could now put the ISP-provided router in bridge mode and instead use the tp-link WiFi 6e router (which was previously in Access Point Mode), which allowed me to disable IPv6 in the router settings. Disabling IPv6 in my home network seems to have fixed all my problems. I've read online that some Android versions struggle with IPv6, so maybe Horizon OS inherited some of these problems.

[RedOne87]

Thanks for your post - this was very helpful!
I'm experiencing the exact same issue with my Quest 3 since a couple of weeks and everything points to the same root cause.. will check if disableing IPv6 will work for me as well (if my ISP still gives me a IPV4).

At this point I have to say that I'm getting very frustrated with Meta Support.
I created a ticket and provided an ADB log showing the issue and all the internal error-codes etc. of the network/wifi stack and also a description of my network topology and asked them to please analyse the log and tell me what to do.

And all I'm getting from Meta support are very general suggestions (like factory-reset..) and lots of unproductive questions that point in different direction every time I get an response from another customer service representative.
It seems that nobody even tried to analyse the adb log (or forwarded it to the development department that have the necessary skills to do so) to actually reproduce and fix Quest 3 firmware issue.

[jas0n_]

My solution here:

1) Look at IP and remember what it was then Forget connection

2) Find it again, put in password but don't hit connect

3) click advanced

4)Change DHCP to Static and put in the IP you had before

5) set Gateway as your router IE:192.168.x.x

6)prefix to 24

7) first DNS to 8.8.8.8 and 2nd to 1.1.1.1

This worked for me when the last update broke both my quests connection. Hope it helps.