Inspiring

Solved

Quest 3/ Air Link stopped working/ No connection to PC/ PC found but Start Button is greyed out...

Forum|Forum|2 years ago
May 28, 2024
242 replies
106852 views

I've been using the Quest 3 for almost 8 months now, and before i used the Quest 2 without any problems via Air link/same router/same PC...

This Saturday I'm playing Borderland 2 VR and on Monday the Quest 3 can no longer connect to the PC without any reason.

If I want to activate Air Link via the Q3, my PC is displayed in the Air Link Menü as before, but the Start Button for Air Link remains gray and it says "not connected".

I've already tried everything:Hard reseting the Headset, factory reset, router reset, PC & Quest 3 reset, Meta Quest Link restart via the beta menu in the PC Oculus APP, repair function of the Meta Quest APP, firewall completely switched off but nothing...

Then I read that you should completely delete the Oculus software with all folders and reinstall it.
I did that and lo and behold it worked, for exactly ONE day....

When I booted up my PC today and started Quest 3, the same problem...
The PC is displayed but the start button to start Air Link remains gray and it is not connected.
WHY?
Do I have to completely uninstall the software every time, including all folders, then reinstall it in order to be able to play via Air link for exactly ONE day, which has worked for over 3 years before (Quest 1, Quest 2, Quest 3) without any problems?

The connection works immediately using the original Meta Quest Link cable.
Virtual Desktop APP works also...

PLEASE Help!

Best answer by LaserDisk

Hello everyone I just got word from engineering that they have rolled out a fix for this issue!

If you are experiencing a grayed out button when attempting to launch Air Link or Link, please follow these troubleshooting steps: Put on the Meta Quest headset. Go to "Settings" then select "System". Scroll down to find "Quest Link" and toggle it off, then back on again. Try launching Air Link or Link again.

If the issue persists after following these steps, please try restarting your computer and headset before trying again.

Please do not hesitate to come back to the thread and let us know if you're still experiencing this issue going forward!

Update 6/13/24

Hey everyone, just wanted to give you all a quick update. I've informed the engineers that even after a few hours, we still have several users experiencing the same issue. If you haven't already, please make sure to submit your bug reports

Update 6/26/24

With the launch of V66, a fix was issued that will roll out to everyone soon. Please check your headset system settings to ensure you are on the latest update. As always, please come back and let us know if you are still experiencing this issue after the update.

R

Raidolo

Up and Coming

I am in the exact same situation, now I'm starting to think that there is a bug in the recent update v65.

I've posted the same issue here: https://communityforums.atmeta.com/t5/Get-Help/Oculus-Quest-3-AirLink-needs-to-be-paired-again-when-the-headset/td-p/1198340

I've solved partially disabling Link and enabling it back from the Settings. Then I can Pair the device with the pc again.

R

RocketCookieAuthor

Inspiring

What settings you mean?

I'm almost reassured that it doesn't just affect me....

R

Raidolo

Up and Coming

In Settings--> System --> Quest Link... Disable it and enable it back, then launch it and pair the PC again...

S

SrG81

Up and Coming

Problems with AirLink can sometimes be solved by disabling the Quest functions completely. If your PC is peeling with a helmet and works via usb then
In the Quest headset:
Go to the Settings menu.Find the settings tab "Air Link", use it there "Air Link" is disabled/enabled and a window should open with the PC pairing code with the headset. The "Air Link" will not work from the main menu.

R

RocketCookieAuthor

Inspiring

This helps, until you reboot yout Headset, than you have to pair fhe Quest 3 again and again.

S

SrG81

Up and Coming

Yes, I agree, it's probably a v65 glitch.

A

azvampyre

Up and Coming

Same issue. Have to pair the headset after every reboot. I sent the headset for replacement and it worked fine until using the link cable, now the kernel has been recompiled to accept the link cable but omitted the airlink protocols and reinstalling the firmware is impossible since they use a communist boot loader.

I spent a good three hours trying to tell support there was a bug for the past two weeks, with them typing like a lethargic turtle, 120 seconds for one sentence, geezus.

L

LaserDisk

Honored Contributor

Not a solution - Marking for visibility

Known Issue

Hello everyone!

I have noticed that a considerable amount of users are currently facing a problem where the Air link button appears grayed out, necessitating the users to re-pair their headsets after each use. I have taken the initiative to inform our internal teams regarding this matter. I would like to express my gratitude to all those who have already shared bug reports and shared their experiences in this discussion.

We would greatly appreciate if everyone could please provide the following information:

What's the full version number of your headset? (65.0.0.####### or likewise)
- Quick Settings > System > Software Update
What's the full version number of your PC app? (65.0.0.####### or likewise)
- General > Scroll down to the bottom of the page.
Is your PC app on PTC?
Are you enrolled in Quest PTC?
Any potential workarounds?
Which headset is everyone using? Is this only happening with the Quest 3 currently, or is anyone experiencing the same thing on their Quest 2 and Pro

I'll do my best to keep you all updated as soon as I find out anymore information!

The future of home entertainment!

R

Raidolo

Up and Coming

Hi All,

I'm having a bit of difficulty with AirLink.

The problem is: every time I PowerOff the headset and power it back on, the AirLink stops functioning. I see my PC as "not connected" and if I click on it, the "Launch" button is greyed out. To make it works, I need to disable Quest Link in the settings inside the headset, turn it back on, then enable the AirLink and in that moment my PC change to "Pair", I pair it and then it starts functioning again. If I reboot the PC, it can connect back, the issue is only when rebooting the headset it seems.

I've checked everything from previous posts, Reinstalled tha app cleaning the AppData Oculus folders, the Windows Firewall settings, but nothing works.

Could please anyone help?

If you need the logs, I'm sending them through the "report a problem" button...

Thanks in advance.

MetaStoreHelp

Community Manager

Hey there, Raidolo! We know how important it is to be able to quickly connect your device after powering it back up. We want to ensure that you have the most smooth VR experience possible, so let's look into this together!

Looking into the matter, we see that you shouldn't have to re-pair it every time, so let's try some steps:

If you have any third-party accessories on your device, please remove them and see if that makes a difference.
Air Link issues can sometimes be resolved by completely disabling the functionality on the Quest.
- In the Quest headset:
  1. Navigate to the Settings menu.
  2. Ensure "Air Link" is disabled/toggled off.
Hard-reboot the device, then restart the PC, and finally restart the router in that specific order.
- To hard reboot the device:
  1. Hold down the power button and volume-down button for 30 seconds until you hear the boot-up sound.
  2. If the boot-up sound is not heard:
    1. Hold the power and volume (-) buttons down simultaneously until the boot screen loads on your headset.
    2. Use the volume buttons on your headset to highlight "Boot Device" and press the power button.
    3. Use the volume buttons on your headset to highlight Yes and press the power button.

Please let us know if this does the trick or not. We are more than happy to continue looking into things together.

If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!

B

bfsieg

New Participant

I've tried factory resetting my quest 2 and reinstalling the oculus app on my PC before trying to reconnect. Nothing has been working. Even the link cable has been extremely buggy. It was working fine until around 5 or 6 days ago. No basic troubleshooting has helped it any.

D

DurandDupuis

New Participant

Hello,
Same problem with my Quest2 for 2 days.

I have installed No man's sky 2 days ago.

Meta Quest Link 65.0.0.499.343

Headset Version : 65.0.0.547.341.596252018

S

STEMALO

Participant

Same for me, everything was working great and now not working. I did notice that the QUEST app is at 66.0.0.288.370 and that my QUEST 3 version is at 65.0.0.546.341.596219384 and my QUEST 3 runtime version is at 65.0.0.548.344.596219384.

I am seriously annoyed as i want to play a game and can't.

L

LamBob14

New Participant

Having the same problem. It started maybe 4 days ago. I can get connected by turning off and on in the quest link in the settings menu but I have to pair every time. Also Steam VR home and games appear to launch on my PC but even if they're running they don't appear to launch on the headset anymore.

Headset version: 65.0.0.548.344.596219384

Desktop app version: 65.0.0.499.343

E

Eliminater74

Up and Coming

I have the same problem.. and it started after that latest update on Quest 2, I dont have a 3, and it does the same thing on Quest 2 as some have reported on 3, I have done everything even reinstalled windows 11 pro, still didnt fix the issue. the only thing I havent done yet is factory reset my headset. which I really dont want to do. this is an issue with Quest. they need to fix this.. it always worked till last update and now it doesnt work. I have to re-Pair my pc with my headset everytime I want to use PCVR, good news is the Steam Link works without issue.. maybe Quest can learn a thing or two from Steam Developers.. I am beyond PO, with this issue..

M

MeatHo0k

New Participant

Same thing for the last coupe of days via airlink on my Q2.

can get it to work again temporarily (until restarting the quest 2) by disabling and re enabling airlink in settings and re-pairing.

Debug log looks fine, then as soon as my Quest 2 starts up again it repeats the below over and over:

11/06 22:16:38.891 {INFO} [xrstreaming_v2] Waiting for 0 connection instances to terminate
11/06 22:16:38.891 {DEBUG} [xrstreaming_v2] Checking running connection - 0 remaining references
11/06 22:16:38.891 {INFO} [xrstreaming_v2] All connection references released in 0.000 seconds.
11/06 22:16:38.891 {INFO} [xrstreaming_v2] oculus_xrs_apk_connection_release_duration release_duration: 0.000004s
11/06 22:16:38.891 {INFO} [xrstreaming_v2] All connection instances terminated
11/06 22:16:38.891 {INFO} [xrstreaming_v2] Creating channel to tlsserver,any-port
11/06 22:16:39.856 {INFO} [DML:HMDNormal] HMD Reporting state change: {'State':'NotDetected','IsDetected':0,'IsReady':0,'Mode':'Unknown','IsWirelessReady':0,'IsRebooting':1,'IsFirmwareOutOfDate':0}
11/06 22:16:40.885 {INFO} [xrstreaming_v2] XrspSocketTransport accepted TCP connection for TCP retransmit storm workaround via socket 6100 from DELETED
11/06 22:16:40.885 {DEBUG} [xrstreaming_v2] Setting TCP Keepalive
11/06 22:16:40.885 {DEBUG} [xrstreaming_v2] Set receive buffer for TCP retransmit storm workaround to 32768 kB
11/06 22:16:40.885 {DEBUG} [xrstreaming_v2] Set send buffer for TCP retransmit storm workaround to 32768 kB
11/06 22:16:40.887 {INFO} [xrstreaming_v2] XrspSocketTransport accepted TCP connection for regular connection via socket 6064 from DELETED
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Setting TCP Keepalive
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Set receive buffer for regular connection to 32768 kB
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Set send buffer for regular connection to 32768 kB
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Constructing socket flow for socket 6064 to DELETED
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Setup QoS for socket 6064 with traffic 4
11/06 22:16:40.887 {DEBUG} [xrstreaming_v2] Constructing socket flow for socket 6100 to DELETED
11/06 22:16:40.888 {DEBUG} [xrstreaming_v2] Setup QoS for socket 6100 with traffic 4
11/06 22:16:40.888 {!ERROR!} [xrstreaming_v2] socket_wr_fd was closed, aborting
11/06 22:16:40.888 {!ERROR!} [Kernel:Error] OVR Error:
Code: -6102 -- ovrError_XRStreamingUSBIssue
Description: socket_wr_fd was closed, aborting
OVRTime: 8212.238191
Time: 2024-06-11 22:16:40 [888:650:0]

11/06 22:16:40.888 {!ERROR!} [xrstreaming_v2] QOSRemoveSocketFromFlow(handle=0x00000000000015e0, socket=6064, flow=1235): An operation was attempted on something that is not a socket. (10038)
11/06 22:16:40.888 {!ERROR!} [Kernel:Error] OVR Error:
Code: -6102 -- ovrError_XRStreamingUSBIssue
Description: QOSRemoveSocketFromFlow(handle=0x00000000000015e0, socket=6064, flow=1235): An operation was attempted on something that is not a socket. (10038)
OVRTime: 8212.238263
Time: 2024-06-11 22:16:40 [888:721:400]

11/06 22:16:40.888 {!ERROR!} [xrstreaming_v2] QOSRemoveSocketFromFlow(handle=0x00000000000015e0, socket=6100, flow=1236): An operation was attempted on something that is not a socket. (10038)
11/06 22:16:40.888 {!ERROR!} [Kernel:Error] OVR Error:
Code: -6102 -- ovrError_XRStreamingUSBIssue
Description: QOSRemoveSocketFromFlow(handle=0x00000000000015e0, socket=6100, flow=1236): An operation was attempted on something that is not a socket. (10038)
OVRTime: 8212.238281
Time: 2024-06-11 22:16:40 [888:739:100]

11/06 22:16:40.888 {WARNING} [xrstreaming_v2] Failed to construct channel for tlsserver,any-port

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO