Oculus Quest detects USB3.2 as USB2

NeilF

NeilF

NeilF

Soldato
Joined
15 Nov 2003
Posts
14,473
Location
Marlow
Suppose no real surprise, but I noticed on my new build that if I plug my old Oculus Quest into the front USB slots, the Oculus software reports it's connected via USB2. Whereas if I connect it to the rear USB3 slots, it happily reports it's connected via USB3.

The front USB3 slots are 3.2 slots and I guess the Oculus is simply confused, so reports USB2.
 
Quest 1? Isn't it no longer supported now? As long as some of your USB ports are recognised by it I guess you're ok.
 
Last edited:
depends on the header the usb ports are conencted to as well dont forget. its not alway obvious what speeds they are. your sure the front is 3.2?
 
Last edited:
LostCorpse said:
depends on the header the usb ports are conencted to as well dont forget. its not alway obvious what speeds they are. your sure the front is 3.2?
Click to expand...
Yes.

I even downloaded/used USB TreeViewer to actively watch the Quest connecting to different USB headers on my system. I think it just doesn't recognise a 3.2 socket so reports it's USB2.
 
Tykey said:
Quest 1? Isn't it no longer supported now? As long as some of your USB ports are recognised by it I guess you're ok.
Click to expand...
Well, the Meta PC app is working. The Quest is working. All my downloaded games on the Quest are working. Steam VR is working. ;)
 
Are your rears only USB3 (Mobo I/O panel?)

Presumably if rears are all USB3 it probably doesn't have the header to support 3.2? What motherboard are you using?
 
Assuming there's no actual damage to the Front USB ports i.e. other USB3 devices show up correctly

Could be the added length of the case's USB cable that causes connections to be marginal - I've had USB3 sticks not recognised at USB3 speeds with older/cheaper cases, but work fine in rear motherboard ports.

Can sometimes be resolved with PCI-E USB cards that have the appropriate header, and connect the front panel ports to that (as different chipset / dedicated power can make a difference)
 
Armageus said:
Assuming there's no actual damage to the Front USB ports i.e. other USB3 devices show up correctly

Could be the added length of the case's USB cable that causes connections to be marginal - I've had USB3 sticks not recognised at USB3 speeds with older/cheaper cases, but work fine in rear motherboard ports.

Can sometimes be resolved with PCI-E USB cards that have the appropriate header, and connect the front panel ports to that (as different chipset / dedicated power can make a difference)
Click to expand...
Oculus using the same cable into three different USB slots. Front mounted wired into a special dedicate USB 3.2 Gen header on the MB . Rear IO panel one. And even a USB hub plugged into the rear IO panel.

Oculus software reports USB 3 for the rear one, USB hub, but USB 2 for the front panel.

USB Tree Viewer reports the front USB stop as USB3.2 when Oculus plugged into it. All the others are lower USB versions.
 
But do the front USB ports actually operate at USB 3.2 with anything else e.g. A flash drive?

Regardless of what USB Tree Viewer reports, if they never work with any other devices then it's either a physical port issue or the front panel cable isn't sufficiently high quality / isn't receiving enough power that devices fall back to lower speeds
 
Looking at the specs of your case, the front USB only supports USB 3.0.
So it's the case rather than your MB.

Why the quest detects it as USB 2 I have no idea

lian-li.com

LANCOOL 216 - LIAN LI is a Leading Provider of PC Cases | Computer Cases

LANCOOL 216 AIRFLOW FOCUS The LANCOOL 216 is a mainstream case that features all-around mesh panels for optimal airflow. Thanks to its modular rear panel, it can be optimized for air cooling or water cooling. It includes 2 x 160mm and 1 x 140mm pre-installed PWM fans and an innovative rear PCIe...
lian-li.com lian-li.com
 
Last edited:
Here's the Quest plugged into my front USB3 sockets, a rear MB USB3 socket, and even a USB3 hub off a rear MB USB socket.

Note: The socket the Quest reports USB2 on is a USB 3.2 header/socket.

ps: Wonder why green and yellow?


Front USB socket
Note: There is also a USB 3 hard drive enclosure plugged into that front USB socket too for testing ("Mass storage device H").

The Quest reports USB 2.
NdOp9dm.png


Rear USB socket
The Quest reports USB3.

QOfs7uc.png


Hub in Rear USB Socket
The Quest reports USB3.

rplblTj.png
 
Last edited:
@NeilF It's possible it's yet another meta borkdate. Multiple users are reporting USB-3.2/2 issues after the V76 update.

communityforums.atmeta.com

Temporary solution for Quest Link wired V76 issues!

Après des jours de recherche, j'ai trouvé une solution temporaire aux problèmes de PCVR avec Quest Link. Vous aurez besoin d'un adaptateur USB-C femelle vers USB-A 3.0 mâle ; cela vous permettra de tester les ports USB-A 3.0 de votre PC. Une fois branché, accédez au test USB dans le logiciel...
communityforums.atmeta.com communityforums.atmeta.com
 
Aha! Thought it seemed to be the Quest having a spaz. Thanks!

I read that thread and seems to imply using a USBC header on the PC might fix it, and I have a USBC on the pc's front USB mount, but I can't be faffed with that.
 
NeilF said:
Aha! Thought it seemed to be the Quest having a spaz. Thanks!

I read that thread and seems to imply using a USBC header on the PC might fix it, and I have a USBC on the pc's front USB mount, but I can't be faffed with that.
Click to expand...

The latest V76/77 borkdates are also rendering link/airlink inoperable.

 
My wired link is working.

Airlink? Is that a wifi link rather than a cable? Assume that's not supported by Quest?

Note: I had used the VR Desktop Stream app to wirelessly connect the Quest to my PC, BUT, when I implemented a mesh network it stopped it from working unfortunately. If I revereted back to just my standard router all was OK. Mesh, fail.
 
Last edited:
NeilF said:
My wired link is working.

Airlink? Is that a wifi link rather than a cable? Assume that's not supported by Quest?

Note: I had used the VR Desktop Stream app to wirelessly connect the Quest to my PC, BUT, when I implemented a mesh network it stopped it from working unfortunately. If I revereted back to just my standard router all was OK. Mesh, fail.
Click to expand...

Yeah, I don't think meta implemented airlink for the Quest, which is probably why VD streamer was created.
 
Airlink is supported on all Quest devices, including Quest 1, though no doubt there will be issues on Quest 1 as it's no longer officially supported.
 
Last edited:
Ravenger said:
Airlink is supported on all Quest devices, including Quest 1, though no doubt there will be issues on Quest 1 as it's no longer officially supported.
Click to expand...

Just the fact that the last firmware for Quest was V51 and the PC app is at V76/V77 there's probably little hope of them talking to each other.
 
You must log in or register to reply here.
Back
Top Bottom