Forum Discussion

SLI_Carl's avatar
SLI_Carl
Explorer
10 days ago

Having to click the USB Detected notification before Link detects connection

My quest recently updated to v2.3.1027 which added the new Navigator UI.

Before, I could just plug in a USB cable from my PC and the headset would ask me if I want to start Link. If I chose not to, I could go to the Link option in settings and it showed my PC as available.

After updating, now when I connect the USB cable, it doesn't ask me to start Link. When I go to the Link settings, its showing that a USB cable isn't connected.

I found that when I first plug in the USB cable, I need to have the headset on and click on the USB Detected notification that pops up. Just clicking on it allows Link to see my PC as available. This popup disappears after a few seconds and the only way I've found to get it back is to disconnect/reconnect the USB cable.

Does anyone know of a way to restore the functionality so I don't have to click this notification every time? I do PCVR development and I prefer using USB connection. 

5 Replies

  • Hi SLI_Carl​ πŸ™‚

    SLI_Carl wrote:

    When I go to the Link settings, its showing that a USB cable isn't connected.

    try this:

    open you quick settings - link - toggle air link(it should find your pc), then disabable air link, it now should  show your pc as connected via USB.

    • SLI_Carl's avatar
      SLI_Carl
      Explorer

      Thanks for the tip. This didn't work for me though.

      I did find that I can click on the notifications icon in the in the bottom after clicking the Meta button on the right controller. I can click the USB Detected notification there which allows Link USB connection. It's still an extra step compared to how it worked before, but at least I don't have to rush to click the popup before it disappears.

      • Choleni's avatar
        Choleni
        MVP
        SLI_Carl wrote:

        This didn't work for me though.

        Hmm....maybe because you have never linked your headset via air link before?

        Anyway, I'm glad you found another workaround πŸ™‚πŸ‘