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

[TheLegend27]

Hey @petecod! I'm currently working on collecting more information to bring to our engineering team to look into. With the ISP, model, and other information (with their default configuration), we may be able to work with the ISP to resolve the issue. If everyone here could provide the information from my previous reply (the marked solution), I'll be able to share these reports with the team. Thank you for your patience!

[petecod]

@TheLegend27 thanks for the reply, good to know you're gathering information. Here's mine:

• Can you share your current Internet Service Provider (ISP)?
  • VIRGIN UK
• Which router are you using (Brand & Model)?
  • TP-LINK DECO XE75
• Which Modem are you using? (Brand & Model)?
  • VIRGIN HUB 4 (IN MODEM MODE) 
• Are you using a Gateway? (Router + Modem combo) YES, VIRGIN HUB 4 WITH TP LINK DECO
• Did your ISP provide your network devices, or did you buy your own?
  • ISP PROVIDED MODEM, SEPARATELY PURCHASED TP-LINK DECO XE75
• Is your network a set of mesh routers?
  • YES
• Does your router have a separate guest network name? GUEST NETWORK IS DISABLED
• Does your router have a separate network name for different bands?
  • 2.4GHZ AND 5GHZ NETWORKS SHARE THE SAME SSID, 6GHZ HAS A DIFFERENT SSID
• Are you attempting to connect to the device using the headset's virtual keyboard or the QR code? VIRTUAL KEYBOARD TO ENTER THE NETWORK PASSWORD
• Have you configured the router yourself using the router's web page or companion app? YES INITIALLY AND ALSO AFTER A TOTAL NETWORK RESET YESTERDAY. REBUILT THE NETWORK FROM SCRATCH.
• Are you attempting to connect your headset to a separate, dedicated router for your play space? YES, THE TP-LINK ID AX75 6GHZ BAND IS DEDICATED TO THE QUEST AND IS THE ONLY DEVICE CONNECTED (UNTIL IT DISCONNECTS ITSELF!). THE 6GHZ CONNECTION WAS EXTREMELY ROBUST BEFORE THE V64 UPDATE, NOW IT IS UNUSEABLE.

Apologies for the CAPS!

[SimpleCJ]

Ok, I was able to test a bit more today after work and I tried 5ghz band and it's working fine on that, but if I switch back to 6ghz the problem returns.  This isn't an ISP issue, this is just a wifi connection issue.  For now I'll just use 5ghz I guess. I played on VRChat thru Virtual Desktop for a full hour and it had zero problems on 5ghz.

[Alex.RG]

Hi everyone;

I have a Quest 3 and cannot connect the the wifi (Infinitum, Mexican internet provider).

Steps i took to troubleshoot : 

1 - I did manage to connect the quest to my cellphone via hotspot.

2 - I factory reseted the quest and retried to connect to the ASUS router ET12 aimesh 6e latest patch. via passwords and QR code.

3 - I got connected eventually to the “Guests’ network “ and that’s how I was using the WiFi. Same router but guests’ network .

4 - Reset the router many times and same  shared pc WiFi and it connected but lagged a lot  

5 - We have all other devices connecting without problem to this router  and you can see is latest 6e ASUS Zenwifi pro ET12 latest version firmware  

Thanks for your help

Alex

[Talgoro]

• Internet Service Provider (ISP)
  • NetCrawler (Canada)
• Router
  • Asus RT-AC86U (also tried RT-AX86U Pro)
• Modem 

  • Hitron CODA-45

• Router & Modem are separated devices.
• The ISP provided the modem, I bought the router.
• No mesh
• No guest network
• Separate network names for different bands
• Connecting using the headset's virtual keyboard
• Configured the router myself using the router's web page (a long time ago)
• No  dedicated router

After upgrading to the PTC v64 I immediately noticed a choppy performance in the Racket Ball game. When it started with the Wi-Fi disconnects I figured that what I thought was a performance issue was in fact a connectivity issue since from what I understand it requires a constant data transmission in order to properly trace the ball.  

It just so happened that I switched the ISPs and also replaced the router (temporarily) after the problems started and it didn't make any difference.

[killerquest.2023]

ditto rock solid wifi until 64 update now looses wifi a lot usually at a crucial point in a game ;-@

[The.Black.Cat]

The same for me. I have v64 and the controller has also received updates. I have a FRITZ!Box 7530. 5 GHz reserved only for Quest 3. I've never seen the "WiFi has been disconnected, check settings" message before.
It happens randomly every few minutes. If i look into the settings WLAN is already connected again. So it just disconnectes for a brief moment.
Meta: Whatever you changed in the WLAN settings. Undo it! The quest is no longer usable.

[petecod]

@TheLegend27 

May we get an update on this issue please. Has it been identified as a Meta issue considering that the network hardware information given by users shows different brands of wifi routers/access points?

I currently have a 6ghz network which is not being used due to constant disconnections meaning that my wifi 6e device is currently redundant and I am unable to use the dedicated access point with the quest 3.

[azvampyre]

Ditto. V64 PC software/driver is junk.

Desktop/games are now all pixelated, look like trash when it does work. Takes several minutes for the headset to be detected by the new driver. The new background processes by Meta use 40% GPU and 14% CPU constantly, even when not in use, so expect it to increase your electric bill.

[TheLegend27]

@petecod I'm not too certain on what's been confirmed by engineering just yet, as I have yet to hear back about any specifics or details. I do know that the team is requesting this information to improve wi-fi connectivity for Quest devices overall.

---

@TheLegend27 wrote:

With the ISP, model, and other information (with their default configuration), we may be able to work with the ISP to resolve the issue.

---

As I mentioned previously, It looks like the team is planning to use this data to make informed improvements, so hopefully I'll have some information to bring back to you all soon. I'll be sure to check back in as soon as I have an update from the team. Thank you for your patience!