HyperX Cloud Core Wireless Support

[CeV35]

Description

HyperX Cloud Core Wireless

Headset Name

HyperX Cloud Core Wireless

Device information

Detailed Device Information

Device Found
 VendorID: 0x0951
ProductID: 0x173f
 path: \\?\HID#VID_0951&PID_173F&MI_03&Col01#8&279d860d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
 serial_number:
 Manufacturer: Kingston
 Product:      HyperX Cloud Core Wireless HID
 Interface:    3
 Usage-Page: 0xc Usageid: 0x1

Device Found
 VendorID: 0x0951
ProductID: 0x173f
 path: \\?\HID#VID_0951&PID_173F&MI_03&Col02#8&279d860d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
 serial_number:
 Manufacturer: Kingston
 Product:      HyperX Cloud Core Wireless HID
 Interface:    3
 Usage-Page: 0xffc0 Usageid: 0x1

Device Found
 VendorID: 0x0951
ProductID: 0x173f
 path: \\?\HID#VID_0951&PID_173F&MI_03&Col03#8&279d860d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
 serial_number:
 Manufacturer: Kingston
 Product:      HyperX Cloud Core Wireless HID
 Interface:    3
 Usage-Page: 0xff00 Usageid: 0x1


C:\Users\cemeg\Downloads\headsetcontrol-windows>headsetcontrol --dev -- --list --device 0x0951:0x173f
Device Found
 VendorID: 0x0951
ProductID: 0x173f
 path: \\?\HID#VID_0951&PID_173F&MI_03&Col01#8&279d860d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
 serial_number:
 Manufacturer: Kingston
 Product:      HyperX Cloud Core Wireless HID
 Interface:    3
 Usage-Page: 0xc Usageid: 0x1

Device Found
 VendorID: 0x0951
ProductID: 0x173f
 path: \\?\HID#VID_0951&PID_173F&MI_03&Col02#8&279d860d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
 serial_number:
 Manufacturer: Kingston
 Product:      HyperX Cloud Core Wireless HID
 Interface:    3
 Usage-Page: 0xffc0 Usageid: 0x1

Device Found
 VendorID: 0x0951
ProductID: 0x173f
 path: \\?\HID#VID_0951&PID_173F&MI_03&Col03#8&279d860d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}
 serial_number:
 Manufacturer: Kingston
 Product:      HyperX Cloud Core Wireless HID
 Interface:    3
 Usage-Page: 0xff00 Usageid: 0x1

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]

Hello 👋

Thank you for reaching out and expressing interest in having support for a new headset.
We appreciate your willingness to contribute to the project!

In order to create a implementation for a specific headset, we need to be able to reverse-engineer and test the implementation on that particular device.
Explicitly speaking, only people who actually own the headset, can implement that request.

👉 If you're interested in adding support for a specific headset, we recommend taking a look at our wiki to get started.

📝 If you encounter any problems while using WireShark, we would be more than happy to help. Simply post screenshots and data on your progress.

[Sapd]

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.

Please post your findings

[CeV35]

hi how can i use wireshark do you have any tutorial ofor that

[Sapd]

Here you can find one: https://github.com/Sapd/HeadsetControl/wiki/Development-1-%E2%80%90-Adding-a-device

[pituluk]

HyperX communications can be reversed in NGenuity2Helper.exe in their NGenuity app, its a .NET bin so easy to read decompiled stuff
I would propose adding HyperX Cloud Alpha S too and this helper would help implementing full options with hyperx devices without having them physically and without wireshark