Skip to main content
New Participant
November 3, 2023
Solved

Quest 2, 3 & Pro - Connectivity Issues

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

TheLegend271265668
Honored Contributor
June 26, 2024

Hey everyone! I'm a bit late to the party for announcing this, but the PTC for V67 just started rolling out not too long ago. It sounds really promising that some of you are already reporting improvements after updating! For anyone else participating in the latest V67 PTC build, please feel free to continue providing your feedback and experiences—along with your full build numbers, so that I can continue funneling these reports to the team. I don't have confirmation on whether or not a fix was supposed to roll out for this PTC build, but I'm working on finding out anything more I can share from the team. Thanks for continuing to keep me updated with your feedback!

Update:

Hey everyone, its looking like some people are seeing their issue resolved by updating to the latest PTC. If you're interested in testing out the new PTC release, you can find more information for how to opt in here. Please keep in mind that the PTC is a test build for unreleased Quest software builds, so while your Wi-Fi connectivity may have improvements, it's possible that other features of the software could be unstable. If you prefer to stay on stable public builds, I recommend holding out for the live V67 release, which should hopefully be coming out sometime soon!

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably

448 replies

Participant
November 11, 2024

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.

New Participant
November 11, 2024

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
Inspiring
November 11, 2024

I'm banking 99% on WiFi, worst is 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.

I could dream forever, and never stop. I could think of life and beauty, the stars that fade in the sky. The hearts of lovers, the dreams of dreamers.
New Participant
December 9, 2024

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. 

Participant
December 9, 2024

Hey there, thanks for your suggestions.

All you guys say points towards DNS IPv6 issue and here is a snippet from my Quest's ADB log (I removed the MAC adresses and similar unique data) further confirming it.
Maybe someone how has more knowledge about Android nework stack/services can make something from the SSL issue occuring in resolv.


12-01 22:54:06.191 1252 1270 W WifiService: Permission violation - getConfiguredNetworks not allowed for uid=10035, packageName=com.oculus.systemux, reason=java.lang.SecurityException: Location mode is disabled for the device
12-01 22:54:06.192 5901 5901 I [SPA] NetworkProviderManager: onWifiEntriesChanged called
12-01 22:54:06.193 1252 1418 D ConnectivityService: NetReassign [82 : null → 121, 73 : null → 121, 116 : null → 121, 75 : null → 121, 19 : null → 121, 62 : null → 121, 135 : null → 121, 142 : null → 121, 84 : null → 121, 64 : null → 121, 38 : null → 121, 94 : null → 121, 34 : null → 121, 40 : null → 121, 23 : null → 121, 46 : null → 121, 92 : null → 121, 54 : null → 121, 7 : null → 121, 58 : null → 121, 31 : null → 121, 44 : null → 121, 70 : null → 121, 148 : null → 121, 182 : null → 121, 66 : null → 121, 21 : null → 121, 27 : null → 121, 25 : null → 121, 1 : null → 121, 184 : null → 121, 17 : null → 121, 119 : null → 121, 68 : null → 121, 137 : null → 121, 15 : null → 121, 33 : null → 121]
12-01 22:54:06.193 1252 1418 D ConnectivityService: Switching to new default network for: uid/pid:1000/1252 activeRequest: 1 callbackRequest: 1 [NetworkRequest [ REQUEST id=1, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_VCN_MANAGED RequestorUid: 1000 RequestorPkg: android] ]] callback flags: 1 priority: 2147483647 using NetworkAgentInfo{network{121} handle{523096739853} ni{WIFI CONNECTED extra: } Score(60 ; KeepConnected : 0 ; Policies : TRANSPORT_PRIMARY&IS_UNMETERED) lp{{InterfaceName: wlan0 LinkAddresses: [ IPV6_4_REPLACED/64,192.168.0.117/24 ] DnsAddresses: [ /192.168.0.1 ] Domains: null MTU: 0 ServerAddress: /192.168.0.1 TcpBufferSizes: 524288,1048576,2097152,262144,524288,1048576 Routes: [ fe80::/64 -> :: wlan0 mtu 0,192.168.0.0/24 -> 0.0.0.0 wlan0 mtu 0,0.0.0.0/0 -> 192.168.0.1 wlan0 mtu 0 ]}} nc{[ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED LinkUpBandwidth>=866000Kbps LinkDnBandwidth>=866000Kbps Specifier: <WifiNetworkAgentSpecifier [WifiConfiguration=, SSID="SSID_REPLACED", BSSID=BSSID_REPLACED, band=2, mMatchLocalOnlySpecifiers=false]> TransportInfo: <SSID: "SSID_REPLACED", BSSID: BSSID_REPLACED, MAC: MAC_REPLACED, Security type: 2, Supplicant state: COMPLETED, Wi-Fi standard: 5, RSSI: -127, Link speed: -1Mbps, Tx Link speed: -1Mbps, Max Supported Tx Link speed: 866Mbps, Rx Link speed: -1Mbps, Max Supported Rx Link speed: 866Mbps, Frequency: 5180MHz, Net ID: 3, Metered hint: false, score: 0, CarrierMerged: false, SubscriptionId: -1, IsPrimary: 1> OwnerUid: 10081 AdminUids: [10081] SSID: "SSID_REPLACED"]}}
12-01 22:54:06.195 1252 2261 D WifiMemoryStoreImpl: Set cluster G9bb25bc0448aaeef for W9bb25bc0448aaeef: SUCCESS
12-01 22:54:06.196 736 842 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
12-01 22:54:06.196 736 842 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'STATE' not found
12-01 22:54:06.196 736 842 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'TIME_NS' not found
12-01 22:54:06.196 736 842 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UID' not found
12-01 22:54:06.196 1252 1396 D WifiClientModeImpl[wlan0]: Received signal strength thresholds: []
12-01 22:54:06.197 1252 1396 E WifiVendorHal: stopRssiMonitoring(l.2617) failed {.code = ERROR_NOT_AVAILABLE, .description = }
12-01 22:54:06.202 1252 1809 D NetworkTimeUpdateService: New default network 121; checking time.
12-01 22:54:06.202 5901 5901 I [SPA] NetworkProviderManager: onNumSavedNetworksChanged called
12-01 22:54:06.202 5901 5901 I [SPA] NetworkProviderManager: onNumSavedSubscriptionsChanged called
12-01 22:54:06.202 5901 5901 I [SPA] NetworkProviderManager: onWifiEntriesChanged called
12-01 22:54:06.202 1252 2178 D UpstreamNetworkMonitor: New default Internet network: 121
12-01 22:54:06.203 1252 1418 D ConnectivityService: Sending CONNECTED broadcast for type 1 [121 WIFI] isDefaultNetwork=true
12-01 22:54:06.204 1252 1418 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendStickyBroadcast:1568 com.android.server.ConnectivityService.sendStickyBroadcast:2812 com.android.server.ConnectivityService.sendGeneralBroadcast:2787 com.android.server.ConnectivityService.sendConnectedBroadcast:2760 com.android.server.ConnectivityService.sendLegacyNetworkBroadcast:8713
12-01 22:54:06.204 18340 18707 D xrstreamingclient: WiFi Speed Changed: network=121 (523096739853), mWifiInfo={SSID: <unknown ssid>, BSSID: 02:00:00:00:00:00, MAC: 02:00:00:00:00:00, Security type: 2, Supplicant state: COMPLETED, Wi-Fi standard: 5, RSSI: -127, Link speed: -1Mbps, Tx Link speed: -1Mbps, Max Supported Tx Link speed: 866Mbps, Rx Link speed: -1Mbps, Max Supported Rx Link speed: 866Mbps, Frequency: 5180MHz, Net ID: -1, Metered hint: false, score: 0, CarrierMerged: false, SubscriptionId: -1, IsPrimary: -1}, Tx=-1, Rx=-1
12-01 22:54:06.208 1252 1418 D ConnectivityService: NetReassign [no changes]
12-01 22:54:06.209 18340 18707 D xrstreamingclient: WiFi Speed Changed: network=121 (523096739853), mWifiInfo={SSID: <unknown ssid>, BSSID: 02:00:00:00:00:00, MAC: 02:00:00:00:00:00, Security type: 2, Supplicant state: COMPLETED, Wi-Fi standard: 5, RSSI: -36, Link speed: 866Mbps, Tx Link speed: 866Mbps, Max Supported Tx Link speed: 866Mbps, Rx Link speed: 866Mbps, Max Supported Rx Link speed: 866Mbps, Frequency: 5180MHz, Net ID: -1, Metered hint: false, score: 0, CarrierMerged: false, SubscriptionId: -1, IsPrimary: -1}, Tx=866, Rx=866
12-01 22:54:06.210 2439 2439 W InitStatus: Not blocking Service (74733887)
12-01 22:54:06.211 1252 11492 W ActivityManager: Unable to start service Intent { act=OC_BATTERY_PERSIST_BATTERY_CYCLE_COUNT cmp=com.oculus.companion.server/com.oculus.companion.inbound.workers.util.BatteryCycleService } U=0: not found
12-01 22:54:06.213 1869 2078 D TelemetryEventLogger: Reporting event: oculus_mobile_cms_wireless_events, event data: type: WIFI_HEADSET_STA_CONNECT, status: SUCCESS, duration: -1 ms, payload: { sessionP2p: NO_SESSION, sessionCms: 4520d072, timestamp: 548.076148402, frequency: 5180, }
12-01 22:54:06.214 5901 5901 I [SPA] NetworkProviderManager: onSavedWifiEntriesChanged called
12-01 22:54:06.214 5901 5901 I [SPA] NetworkProviderManager: onSubscriptionWifiEntriesChanged called
12-01 22:54:06.215 1869 2078 D ControllerManagement: P2p group not formed. No need to switch band.
12-01 22:54:06.215 1869 2078 D ControllerManagement: P2p group not formed. No need to switch band.
12-01 22:54:06.215 1252 2053 D WifiCountryCode: Reading country code from telephony
12-01 22:54:06.217 1252 2053 D WifiCountryCode: Set telephony country code to:
12-01 22:54:06.219 1869 1869 I ControllerManagement: onApConnected(): mWlanConnected=true, countryCode=DE

Participant
December 9, 2024

Hey there, thanks for your suggestions.

All you guys say points towards DNS IPv6 issue and here is a snippet from my Quest's ADB log (I removed the MAC adresses and similar unique data) further confirming it.
Maybe someone how has more knowledge about Android nework stack/services can make something from the SSL issue occuring in resolv.

https://pastebin.com/JWjeBHaH

Today I've written at laest 5 mails to Meta support - all I want is to make bug report with all data I provided.. But these freaking Meta AI keep on telling me to do factory-resets or to RMA my device.
I tried to escalate to a human that actually reads and understands what I want and actually answers a single question - then in two of the Meta support answers the sender acutally claims to be human ("Please know that I am a human, and I am following the necessary procedures to help you to the best of my ability. Your cooperation is greatly appreciated. If you have any other questions or need further assistance, please feel free to let us know.") but still did not answer my question nor did create a bug report... still kept repeating the same phrases the AI did so I'm not really sure.


I've never experience anything like this - I can get a brand new device via RMA at once (offered me this multiple times and wanted serial numbers, receip etc) and literally burning Metas money without fixing the issue but Metas Support is not capable or willing to create a bug report created by an developer.

New Participant
December 10, 2024

I had issues with the controller tracking on V71 and decided to opt into the V72 PTC to see if it would fix it. Now Wifi drops and won't connect to anything at all. No networks show up and it won't let me switch the toggle to "ON", it'll stay on "OFF". I can't even connect to my phone via HotSpot or bluetooth to use wifi that way. It'll connect via bluetooth to the Meta Horizon App on my phone perfectly fine but not anything else.

I've factory reset 3 times already. The wifi will work for like 2 minutes before it disconnects and i can't do anything. Iv'e had no issues with this headset for about a year and now with these updates it feels like it gets worse.

Up and Coming
December 13, 2024

This is now happening to both of my  Quest 3 headsets. The app on my phone will also not work on WIFI but will on mobile data. How can two Quest 3's and the phone app suddenly stop working on wifi even though I didn't touch my network settings at all and they were all working a week ago? I've updated everything and reset my modem and router.

This makes absolutely no sense.

New Participant
December 14, 2024

Yes I've got the same issue. I've had the quest 3 for 3 months no problems. Now having issues with viewing the store/horizon feed/library. Occurs both on the headset and app. If I hotspot the mobile (same wifi) the issue resolves on the headset. If I switch the mobile phone to 5g then the issue resolves on the app. 

New Participant
December 14, 2024

I got mine to work but I don't know if it'll work for others. This is on V72. I factory reset the headset but before continuing with resetting up the headset after the factory reset I reset my router/modem.

When I was done resetting my router I continued setting up my headset again. Chose my wifi and got everything running up. Since than I've had no issues with wifi connectivity. 

Participant
December 23, 2024

Hey guys,
I reported the same issue ~20 days ago to Meta support and had lots of absolutely non productive responses and questions from Meta Support... was absolutely infuriating!

The last response was helpful - it is possible to create a bug report on the not working network so that all information about the issue is logged and then connect to another working network so that the report can actually be sent.
Here the steps form the Support's mail:
1. Reboot the headset.
2. Remove any unsupported third-party accessories that may affect communication (such as headset covers, etc.)
3. Connect to the problematic network and submit a bug report.
4. Try connecting to a different network.
If you were not able to successfully submit a bug report in the previous step, do so now.


I finally received two Firmware updates it seems the issue is resolved. I’m now on v72 Build 5047332.12760.510 and since 4 days the issue is gone.

Thanks to the dev team to look at the issue and fix it and thanks to the last two Meta Support representatives who gave usefull answers and actually adressed my questions (and probably where not AI generated responses)

Happy Christmas

New Participant
December 26, 2024

Since v72 i have similar problems with my Quest 3. Meta Apps aren't loading, i can't download and install games and I already did a factory reset, reset my router and tried multiple router configuration options. There is nothing wrong with my connection, all other devices run as expected. I also filled a bug report. Please reach out to resolve this problem so that i can finally use my device again.