Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Req] Add HyperX Cloud Wireless 3 #7

Open
Jason-THL opened this issue Apr 6, 2024 · 17 comments
Open

[Req] Add HyperX Cloud Wireless 3 #7

Jason-THL opened this issue Apr 6, 2024 · 17 comments

Comments

@Jason-THL
Copy link

Would it be possible to add the cloud wireless 3 to the supported devices?

@auto94
Copy link
Owner

auto94 commented Apr 7, 2024

Probably yes, if you're prepared to help.

Does ngenuity show the exact battery percentage in the app?
If yes, please provide:

  • A recording of the USB traffic (using Wireshark and USBPcap) while you're opening ngenuity that ends after you see the current battery percentage.
  • Battery % as shown by ngenuity at the time of the recording?
  • A screenshot of the product ID. (Open device manager -> find the headset under "Sound, video and game controllers" -> Right click -> Properties -> Details tab -> Hardware IDs property

And post all that in here and I'll see if I can figure it out.

@Jason-THL
Copy link
Author

Hey, sorry for the late response.
Can you run me through what to do with Wireshark and USBPcap?

@auto94
Copy link
Owner

auto94 commented May 1, 2024

Sorry for the delay.

  1. Install Wireshark. If you scroll down a bit, you can see the download links.
  2. Install Wireshark. During install it should ask you if you want to also install USBPcap. You should agree (checkmark it first).
  3. Open Wireshark.
  4. In the top menu click Capture->Options
  5. In the Input tab, you should see 1 (or more) USBPcap options (USBPcap1, USBPcap2 etc.).
  6. Now you have to figure out which USBPcap can record your headset data. I suggest you double click one of the USBPcap options in the Input tab, which should start a recording. Then play some music and see if there is a bunch of data being recorded when the music is on and less (or none) when the music is off. The port that responds like that is probably the port your headset is using.
  7. Once you've figured it out, start a new recording for the correct USBPcap entry (with no music) and then open HyperX Ngenuity.
  8. Once you can see your headset in Ngenuity, click on it so that you can see your current battery level. Remember the battery level and write it here.
  9. Stop the Wireshark recording and upload it here.
  10. Upload the screenshot of the product ID. Instructions where to find are in the previous comment.

If you need more help let me know, I can probably make a guide with screenshots or something similar if needed.

Thanks for your help!

@Jason-THL
Copy link
Author

Hey, thanks for the instructions, I messed up earlier because I installed USBPcap and Wireshark seperately.

I managed to get the recording, hardware ID and battery level. Hope this helps. :D

id
battery_at_recording
recording.zip

@auto94
Copy link
Owner

auto94 commented May 23, 2024

Crap, I totally forgot about this. Sorry! I'll be more attentive from now on.

I took a look at the recording and it seems very different to what I've seen with other headsets.
Could you maybe try and create another recording? Basically just restart from step 6 from my previous post. I have a small suspicion that you might have also recorded some data that was actually you moving your mouse but I could totally be wrong on that and this headset is just that different.

I appreciate your time and help in this, and as I mentioned sorry for the wait.

@Jason-THL
Copy link
Author

image
recording2.zip

Yeah, no worries.
I rerecorded it on a different usb port if that helps. I'm not sure if its something on my PC that is affecting the Wireshark output, let me know if I need to do something else.

@Jason-THL
Copy link
Author

If this helps, this is what the USBPcap.exe shows, I don't know if the other stuff showing could be any of them.

image

@auto94
Copy link
Owner

auto94 commented May 27, 2024

Judging from the USBPcap screenshot this 2nd recording should be the correct USB port but honestly I can't find what data could be the battery level. Usually you'd get a URB_INTERRUPT in that would have the battery level in it's data (in hex) and I don't see anything like that here. I'll try to start over again sometime and hopefully I can figure it out with a clear head.

Just in case, did you make the screenshot and the recording at the same time (roughly).
Thanks.

@Jason-THL
Copy link
Author

Yeah the screenshot and recording were done at the same time.

I do not have the ngenuity headset drivers installed which might be the issue? (I saw that it makes the sound quality significantly worse for the Cloud 3 Wireless)
But after opening ngenuity, I can still see the battery level after clicking "Headset" option.

Let me know if I gotta do anything, more than happy to comply :D

@auto94
Copy link
Owner

auto94 commented Jun 3, 2024

Yeah honestly I can't figure it out from this recording. If you're up for it, I'd ask you to make one last USB recording, this time with a more specific order of actions.

Ok so:

  1. Completely exit/quit the ngenuity app.
  2. Start new USBPcap recording in Wireshark. Use USBPcap3.
  3. Open ngenuity.
  4. Wait for the headset to show up in the "Connected devices" in ngenuity.
  5. Click the headset.
  6. Take a screenshot of the battery level.
  7. End USBPcap recording.

If that doesn't create a helpful recording, then I'm out of ideas.

@Jason-THL
Copy link
Author

Alright, I tried again. You might be right, I didn't complete quit out of ngenuity last time, hopefully this time it shows the right data. Thanks again for trying to get this to work.

recording3.zip

@auto94
Copy link
Owner

auto94 commented Jun 30, 2024

Well I lied and didn't respond for way too long again.
I did try a couple of times to understand the data and find the battery info in the packets but I didn't succeed so I think this will have to wait either for someone else to figure it out or for my headset to die and then maybe I buy a Cloud 3 and try it.

I'll keep the issue open in case someone else makes a pull request or something so that you get a notification.

Sorry for wasting your time. Appreciate your help!

@Bonus83
Copy link

Bonus83 commented Jul 9, 2024

Hi, maybe you can provide a "device data reader" within your application (like a plugin) to identify all data coming from that one specific device (selected by the user), exportable in a file, which can be uploaded here to help you?

@VirgilSurin
Copy link

VirgilSurin commented Aug 14, 2024

Hello,

I have an HyperX Cloud III Wireless. I followed your last instructions from here : #7 (comment)

Here is the recording of the correct USBcap :
cloud3_capture_73bat.zip

Here is a screenshot from the app with the battery level :
battery_level

Here is the hardwares ID :
image

I hope these informations can help!

@BlankPixels
Copy link

Hey,
Just saw this post, was there any updates on it?

@VirgilSurin
Copy link

Not that I am aware of

@auto94
Copy link
Owner

auto94 commented Oct 29, 2024

I've checked Virgils recording when he posted it and it didn't help. It seems to me that the Cloud III is quite different from the rest in regards to the data being sent/received so unless someone who owns a headset puts in the time (or I happen to get my hands on one), I think it's unlikely it gets added.

Having said that, the more recordings the better so anyone who comes across this feel free to add yours, the instructions are in this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants