You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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.
Added 0x12c4 in 75de3b0. It is one PID off the 0x12c2 Arctis 9 we already drive, so the legacy SteelSeries protocol should fit — but I have no such headset here, so this is unverified.
Please try a continuous build once it finishes and post the output of:
headsetcontrol -b
headsetcontrol --capabilities
If it is detected but battery or sidetone misbehaves, the interface number is the first suspect: we open interface 0 for the Arctis 9, and the path you posted is MI_03. Say so and I will make it interface 3 for this PID.
Leaving this open until someone confirms it on hardware.
Activity
github-actions commentedon Aug 5, 2026
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?
See ADDING_A_DEVICE.md for detailed instructions.
feat(device): add Arctis 9 product ID 0x12c4
Sapd commentedon Oct 23, 2026
Added
0x12c4in 75de3b0. It is one PID off the0x12c2Arctis 9 we already drive, so the legacy SteelSeries protocol should fit — but I have no such headset here, so this is unverified.Please try a continuous build once it finishes and post the output of:
If it is detected but battery or sidetone misbehaves, the interface number is the first suspect: we open interface 0 for the Arctis 9, and the path you posted is
MI_03. Say so and I will make it interface 3 for this PID.Leaving this open until someone confirms it on hardware.