I hadn't got back on till after work today. Played a full hour for my regular cardio, Beat Saber and Punch Fit, workout and did not have any disconnects.
Headset was being weird when I tried to switch to 6ghz it wouldn't show me the network. I checked and I don't have it set to hidden. I turned off auto-connect on the 5ghz network and then turn wifi off and on again. It still wouldn't show me the 6ghz channel, so I just went into saved networks and clicked on it and then connected from there and it actually stayed connected.
Kinda odd behavior, but so far looking good. We'll see if it auto-connects when I get back on later. I will also try to do a longer session this weekend, like 3+ hours and see how it goes. I've just been busy with summer vacations. Heading out of town again next week. Not had as much time to play for now. I am happy to see some improvements though.
Update: Played another hour session today on 6ghz and no disconnects! I'm feeling like v67 has fixed it for us. Still not sure what's up with the headset not seeing the 6ghz SSID, but at least it's working!
Hello, unfortunately I have the same issue. Howerver this solution doesn't works for me. When I'm trying to connect it connects just for a second, and keeps reconnecting to the same network. I can't use quest 2 because of this.
I just installed v68 PTC today and played for about 90 minutes without experiencing any WiFi breakups! Normally, I would get one around the 60-minute mark, so I was pleasantly surprised. I will continue testing, but it seems promising!
Can confirm as well. With v67 I initially thought that the problem was resolved but my testing was limited and eventually I realized that I was wrong. With v68 I had enough testing to be sure that the issue is no longer present.
I'm currently on the v67 release update, and still encountering WiFi issues. I have attempted:
- Factory Reset Headset
- Factory Reset Router
- Assign Static IP to Headset
- Attempted to separate 2.4 and 5ghz bands (impossible on my COVR-X1870 mesh network)
- Connect to mobile hotspot (success)
- Connect to PC hotspot (unsuccessful - headset cannot connect to router, no matter how)
- Drain headset batteries to 0% and recharge from there
This has been going on for almost 3 months now and I have been unable to use my headset. Please submit a proper solution HERE WITHIN THE THREAD and not a "private message". I cannot sign up for the PTC to access a beta build of v68 which appears to be working for some, as the test environment is full. It's crazy to me this can even happen in the first place for a wireless VR headset.
Thank you? For what? META introduced this error itself and fixed it after 4 versions (!) and 6 months later. No thank you from me. In half the time I've owned the Q3 I haven't been able to use it properly. What do I get in return?
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
