12-07-2022 07:30 AM - edited 12-07-2022 07:31 AM
Solved! Go to Solution.
12-09-2022 10:14 AM - edited 12-09-2022 10:19 AM
I purchased a new cable, the Kuject MT005, a USB-C to USB-A where you can plug the headset charger directly into the cable for extra power. I plugged this into my USB A PCI-e card, and now I’m getting 896 mA and USB 3.2 reported. Of course I am getting more current than that, as the headset is getting a charge from 2 sources now, only one of which the computer can measure.
This does not mean this is a hardware problem! My USB-C to USB-C cable charges other devices just fine. I guess my problem is solved for now, but I really hope Meta solves this problem. There’s many reports on this site that go back years reporting it, even using the official $80 cable.
I’ve sent Meta my logs after chatting to Support.
12-08-2022 02:50 PM
Thanks for sharing your experience! I gotta be honest and say this is past my range of expertise. However, if anyone here with experience in using Macs with Quest 2 has some advice or suggestions, I'd love to hear 'em chime in!
12-09-2022 05:06 AM
I did a factory reset on the headset and connected it again to the computer and the USBDeview reported USB 3.2…for about 5 minutes, and then it went back to USB 2.0 again. Still no power.
I am running Windows natively on the machine, and it’s all PC components except for the motherboard, so it’s a stretch to call this a Mac issue. It’s got an Apple on the box, but it’s a Windows machine in the ways that count. It's not an emulation or virtual machine.
12-09-2022 10:14 AM - edited 12-09-2022 10:19 AM
I purchased a new cable, the Kuject MT005, a USB-C to USB-A where you can plug the headset charger directly into the cable for extra power. I plugged this into my USB A PCI-e card, and now I’m getting 896 mA and USB 3.2 reported. Of course I am getting more current than that, as the headset is getting a charge from 2 sources now, only one of which the computer can measure.
This does not mean this is a hardware problem! My USB-C to USB-C cable charges other devices just fine. I guess my problem is solved for now, but I really hope Meta solves this problem. There’s many reports on this site that go back years reporting it, even using the official $80 cable.
I’ve sent Meta my logs after chatting to Support.