USB-C 3.0 cable identified as 2.0 on a 3.0 port
USB-C 3.0 cable identified as 2.0 on a 3.0 port
For a while now, I've been attempting to connect my Quest 3 to my PC using the 3.0 USB-C cable. It appears as 2.0 in the Oculus app and USB Device Tree Viewer. At this stage, I'm not sure what to do. I've tried restarting the port and switching the cable, but nothing seems to work. Occasionally, I connect it as 3.0, but after about 20 minutes I see a black screen on my Q3 and have to reconnect. Once connected again, it switches to 2.0 instead of USB 3.0. Support is slow and only offers copied solutions that don't help. I'm getting frustrated and this is my last option.
Yes, it seems to be a regular cable rather than a charge-only one, as I've experienced stable 2Gb speeds for two months without any problems.
What type of cable are you employing? Do you have any extensions or adapters connected to it? Which device are you connecting it to? (For example, a USB hub that draws power externally, or the USB-C 20 Gbps port on the back of your Super Cool Motherboard Model by Motherboard Company)
USB controllers can adjust port speeds when bandwidth is limited. Running out of available bandwidth might cause performance issues, potentially leading to controller overload. If this happens, some devices may need to be disconnected. The cable itself is unlikely to be the cause unless it’s damaged.
It relies on the controller design and the number of connected devices. There are STT and MTT-based controllers. If many connections go to one controller, bandwidth per port gets divided. STT and MTT configurations depend on how the hub functions when different device speeds are involved. STT uses a single transaction translator that manages communication between low and full speed USB devices when their speeds don't match. With STT, this translator stays on the hub controller, so if a slower device needs to slow down, the whole controller temporarily slows too, affecting speed changes. This may lead to problems when switching between many high and low-speed devices at full capacity, causing delays in signal processing. MTT uses one translator per port, allowing each port to change speeds independently without affecting others. Overloading a USB controller usually results in devices dropping out and showing a warning about resource limits, especially if many ports are used or power draw increases. Rarely does a USB controller reach complete saturation since it must maintain full data rates constantly.