-
Notifications
You must be signed in to change notification settings - Fork 2
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
Support for Model O2 Wireless #1
Comments
Hey, I did some tests, and unfortunately I don't think it's as straight forward in the implementation as initially thought. You've correctly mapped the vendor ID based on the logs, it is "0x93A" as you've mentioned in your post The wireless dongle has the ID "0x822D" For testing purposes I added the devices to the enum and changed the vendor ID. So I printed the I then went a step further and instead of dynamically searching for the correct entry in the iterator, I converted it to a map and manually tested every occurence that matched against the o2 wireless mouse, and they all resulted in the Just to be sure I also retried this with a different USB port and different cables for the wired connection, but all tries resulted in the same error, I also tried running with root and my own user, but the results were always equal. Finally I tried pinpointing the exact line of error and for I've never worked with HID before, but to me this looks like the O2 Wireless mouse does not communicate like the other devices offered by glorious. Since I've got no idea how to find out how to properly communicate here, I can't do much more. |
It is true that the communication method is different. Now that Glorious have released CORE 2.0, the site states
To add support for these newer models, the same "brute force" way of reverse engineering it is required, unpacking the |
cc @Karagra
The text was updated successfully, but these errors were encountered: