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 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.
Activity
github-actions commentedon May 8, 2024
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.
AdamGardelov commentedon May 8, 2024
This is my finding from Wireshark.
Sapd commentedon May 8, 2024
The headers are missing. What does WireShark tell you on the "Setup Data" section?
AdamGardelov commentedon May 8, 2024
This is off:
This is on, witch makes 2 requests:
Forgot to add that the function i need is to turn of the sidetone. It is a on/off-switch in their software.
Sapd commentedon May 8, 2024
I think this should work, you can try:
and
AdamGardelov commentedon May 8, 2024
Sadly this gives "Couldn't open device."
Sapd commentedon May 8, 2024
You might have to run it as root if you do not have the udev rules installed
AdamGardelov commentedon May 8, 2024
Thanks, running as root worked. But none of the commands turned sideton off unfortunately
Sapd commentedon May 8, 2024
I didnt see that you had 3 payloads there.
What about
AdamGardelov commentedon May 9, 2024
It worked!! if you want to add this device to the repo:
This is On:
And this is off:
Thanks for your help man, really appreciate it! Support 10/10!
Sapd commentedon May 10, 2024
I included it in the hyperx branch: #348. Can you try it?
First delete the build folder:
rm -r buildThen:
AdamGardelov commentedon May 13, 2024
Works perfect! Thanks!