Imma keep this as short as possible.
I got a new 5GHz / 2.4GHz router so I could use Oculus Air Link without it stuttering every five seconds (my previous router only had 2.4GHz). When I try connect to my PC it just says "searching for device" but cannot find the PC. I have been troubleshooting and looking at forums and reddit posts for the past few days but none of the advices I have found so far have helped me. I found out that if both devices [the PC(in this case an old laptop I found) and the Quest 2] are connected to Wi-Fi, instead of the PC being connected to Ethernet, Air Link can find the Device and it works without problem. But my PC doesn't have a Wi-Fi adapter, and even if it did I do not want to use Wi-Fi on my PC for Air Link.
Here's a list of everything I have done to try and fix this issue:
I'm really desperate for help. My Oculus Link cable also started to act up yesterday and replacing it would cost too much for me right now so I *really* need to fix Air Link. Thanks in advance!
Opposite problem as me then. I can always detect the PC, and pair with it. But so far... Air Link has only actually launched twice, out of over 30 attempts. The two times it did work, I had to start with Air Link disabled both on the Quest and my PC. I then had to turn it on in the PC first, using either Oculus Link (which also isn't working often right now) or Virtual Desktop. Then I'd turned it on in the Quest, and it decided to work. Strangely, that "turn on via PC then Quest 2" tactic so far has only worked if streaming my PC to the Quest already. If I try doing so by lifting the headset (so I can see what I'm doing) and using the PC directly, it hasn't actually worked.
One thing I had to do was to have my desktop plugged into the router and have it connected to the 5g wifi network my quest is on, at the same time. Also, don't forget to open up the Oculus app on your computer and turn on Air Link. While that stays enabled in the quest once set to on, the desktop app will turn it off after 24 hours. And defaults to it being off when the app is first started up too.
MY DUDE! Dev mode, the answer to all life's problems XD
Turn dev mode on using your app on your phone.
Open the Oculus app on your phone and go to
settings / device / development mode ~ There's a toggle there. I had to turn it on and off again and then reset the headset a couple of times to get it to work but as soon as I saw it registered in the headset (there's a new settings menu towards the bottom for dev mode) it worked fine 🙂
Good luck dude.
Having the same exact problem.
Quest 2 is already set for developer mode.
I have a Ubiquiti UniFi WiFi6 AP wired into a Ubiquiti US-8 network switch, and my PC is wired directly into the same network switch. The only SSID broadcast by that WiFi6 AP is a unique name I set up exclusively for Quest 2 to connect to, and there is no 2.4GHz network broadcasting on that same SSID. Virtual Desktop VR game streaming works absolutely fine, and all other network connectivity between the PC and headset works fine, but not Air Link. My Oculus client software shows the Quest 2 as a known device because I've previously connected it to the PC using the wired Oculus Link cable. I've checked my Windows firewall settings and verified that the Oculus client software has a correctly-configured-and-enabled set of inbound rules applicable to all network profiles (Private, Public, Domain, etc). I have the Air Link "experimental" setting enabled in the Oculus software. My router (a Ubiquiti ER-12) shows that both the Quest 2 and the PC are assigned IPs on the same subnet, with no firewalling of any kind between them. As far as I can tell, EVERYTHING is configured correctly EVERYWHERE, yet the Quest 2 still refuses to find my PC. It just searches forever and never finds anything.
You seemed to have gone through the same steps as I have. Were you able to find a solution in the end? I tried with ALVR and it works once I set the IP static in the software, but Virtual Desktop Streamer nor Airlink works. I also tried Virtual Desktop Streamer with my laptop and it works, so I suppose it's the LAN connection that's bothersome