Oculus Quest disconnecting

<p>Whenever I try to connect my Oculus Quest 2 VR (android) headset it just instantly disconnects itself before reconnecting again. It works fine with numerous other USB devices (steering wheel, gamepads). Running latest versions of client and server.
</p>
<p>Logs from server:
</p>
<p>May 25 11:51:20 vhusbdarm[1861]: Executed "" for onReset.2833.0186<br />
May 25 11:51:20 vhusbdarm[1861]: Device 211 [2833:0186] BOUND to connection 58<br />
May 25 11:51:20 vhusbdarm[1861]: Executed "" for onReset.2833.0186<br />
May 25 13:51:20 kernel: usb 2-1.1: USB disconnect, device number 64<br />
May 25 11:51:20 vhusbdarm[1861]: Device 211 [2833:0186] SURPRISE UNBOUND from connection 58<br />
May 25 11:51:20 vhusbdarm[1861]: Unmanaging device 211 [2833:0186]<br />
May 25 13:51:20 kernel: usbserial: USB Serial deregistering driver GSM modem (1-port)<br />
May 25 13:51:20 kernel: usbcore: deregistering interface driver option<br />
May 25 13:51:20 kernel: usbserial: USB Serial deregistering driver generic<br />
May 25 13:51:20 kernel: usbcore: deregistering interface driver usbserial_generic<br />
May 25 13:51:20 kernel: usbcore: deregistering interface driver usbserial<br />
May 25 13:51:22 kernel: usb 2-1.1: new SuperSpeed USB device number 65 using xhci-hcd<br />
May 25 11:51:22 vhusbdarm[1861]: Found Super speed device [2833:0186] "Oculus, Quest 2" at address 211<br />
May 25 13:51:22 kernel: usbcore: registered new interface driver usbserial<br />
May 25 13:51:22 kernel: usbcore: registered new interface driver usbserial_generic<br />
May 25 13:51:22 kernel: usbserial: USB Serial support registered for generic<br />
May 25 13:51:22 kernel: usbcore: registered new interface driver option<br />
May 25 13:51:22 kernel: usbserial: USB Serial support registered for GSM modem (1-port)
</p>
<p>Anything I can try or is this a known problem? I found another thread on the forum suggesting a custom handler which didn't help either.</p>

#2

I dont think it will work at the moment with virtualhere. I think it needs needs some firmware on power-on which virtualhere wont support without some tweaking and i dont have a quest to test with..

#3

I understand it was a long shot but worth a try.

I'd definitely advise picking up a Quest for entertainment purposes if not for Virtualhere :)