Mic Monitoring - HyperX Cloud III S Wireless

[lautit]

Description

Hey! I've been able to sniff the USB packets of my new Cloud III S Wireless using a Wireshark on a win-vm in Mac, but I'm not entirely sure what I'm supposed to be reading. Following the instructions on the Wiki and ADDING_A_DEVICE.md, I saved the Wireshark logs for toggling ON-OFF Mic monitoring from NGENUITY.

Is there any way I can share more info on the capture to get this bad boy up and running?

Thanks!

Headset Name

HyperX Cloud III S Wireless

Device information

Detailed Device Information

Device Found
 VendorID:  0x03f0
 ProductID: 0x06be
 Path: DevSrvsID:4295321564
 Serial: C1V5370018
 Manufacturer: HP, Inc
 Product: HyperX Cloud III S Wireless
 Interface: 3
 Usage-Page: 0x000c  Usage-ID: 0x0001

Device Found
 VendorID:  0x03f0
 ProductID: 0x06be
 Path: DevSrvsID:4295321564
 Serial: C1V5370018
 Manufacturer: HP, Inc
 Product: HyperX Cloud III S Wireless
 Interface: 3
 Usage-Page: 0xff13  Usage-ID: 0x0001

Device Found
 VendorID:  0x03f0
 ProductID: 0x06be
 Path: DevSrvsID:4295321564
 Serial: C1V5370018
 Manufacturer: HP, Inc
 Product: HyperX Cloud III S Wireless
 Interface: 3
 Usage-Page: 0x000b  Usage-ID: 0x0005

Device Found
 VendorID:  0x03f0
 ProductID: 0x06be
 Path: DevSrvsID:4295321564
 Serial: C1V5370018
 Manufacturer: HP, Inc
 Product: HyperX Cloud III S Wireless
 Interface: 3
 Usage-Page: 0xffc0  Usage-ID: 0x0202

Device Found
 VendorID:  0x03f0
 ProductID: 0x06be
 Path: DevSrvsID:4295321564
 Serial: C1V5370018
 Manufacturer: HP, Inc
 Product: HyperX Cloud III S Wireless
 Interface: 3
 Usage-Page: 0x01c0  Usage-ID: 0x0001

Device Found
 VendorID:  0x03f0
 ProductID: 0x06be
 Path: DevSrvsID:4295321564
 Serial: C1V5370018
 Manufacturer: HP, Inc
 Product: HyperX Cloud III S Wireless
 Interface: 3
 Usage-Page: 0x170f  Usage-ID: 0x0202

New Device Implementation Checklist

• I acknowledge that implementing a new device requires direct access to the device and familiarity with capturing and analyzing its communications. I have access to the device and am willing to contribute by capturing necessary data and/or attempting implementation.
• I have already attempted to capture device communications using WireShark or similar tools and am including my findings (successful or not) with this issue to assist in implementation efforts.
• I am seeking guidance on how to begin this process and am willing to collaborate with the community to add support for this device. I understand where to find resources (refer to the WIKI).

[github-actions]

Thank you for requesting support for a new headset!

To implement support for a specific headset, we need to reverse-engineer and test on that device. Only people who own the headset can implement support for it.

Want to help?

1. Check our Development Wiki to get started
2. Use Wireshark to capture USB traffic from the official software
3. Post your findings (screenshots, data) here - we're happy to help!

See ADDING_A_DEVICE.md for detailed instructions.