Arctis GameBuds

[ikogan]

Description

Arctis GameBuds are earbuds that have both Bluetooth and a 2.4ghz dongle. This request is specifically to support them being used in dongle mode, though bluetooth mode would be a fun bonus although since headsetcontrol doesn't even see them as devices (probably no /dev/hidraw device?), I doubt it's worth the troubler. The vendor app provides the following controls:

• Audio Mode (Bluetooth or 2.4ghz)
• Equlizer (looks like typical Arctis equalizer settings)
• Noise Control (On/Off and ANC/Transparency as separate toggles, however, pressing the left earbud switches from ANC -> Transparency -> Noise Control Off)
• Microphone Volume
• Sidetone (Off, Low, Medium, High)
• Volume Limiter (On/Off)
• Auto-Power Off (Dropdown including Never, 1 Min, 5 Min, 10, 15, 30, 45, 60, 75, 90)
• "Wear Sense" (mute when they're taken out of your ears)
• Button Mapping

This request isn't asking for all of these to be implemented, just the standard Arctis settings would be nice, Side Tone in particular.

Headset Name

Arctis GameBuds

Device information

Detailed Device Information

❯ headsetcontrol --dev -- --list --device 0x1038:0x230a
Device Found
  VendorID: 0x1038
 ProductID: 0x230a
  path: /dev/hidraw10
  serial_number: 
  Manufacturer: SteelSeries
  Product:      Arctis GameBuds
  Interface:    3
  Usage-Page: 0xffc0 Usageid: 0x1

Device Found
  VendorID: 0x1038
 ProductID: 0x230a
  path: /dev/hidraw11
  serial_number: 
  Manufacturer: SteelSeries
  Product:      Arctis GameBuds
  Interface:    4
  Usage-Page: 0xc Usageid: 0x1

Device Found
  VendorID: 0x1038
 ProductID: 0x230a
  path: /dev/hidraw12
  serial_number: 
  Manufacturer: SteelSeries
  Product:      Arctis GameBuds
  Interface:    5
  Usage-Page: 0xff00 Usageid: 0x1

USB Capture: Gamebuds.zip. They should be device 1.3.0 and 1.3.1 just in case. I'm not sure if this is the exact data that's needed, I can capture it again as necessary.

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.