-
Notifications
You must be signed in to change notification settings - Fork 50
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
DeathAdder Elite (2016) #92
Comments
This device is not supported and as far as I know nobody is working on it, yet. |
+1 for this feature request. Want this feature so that I don't have to play Razer's game and require Synapse installed / connected to cloud. It's a dirty and silly tactic |
Would love to see this mouse supported. Much better tracking with the new optical sensor. |
I started to develop this by assuming it operates the same as Deathadder Chroma, just with added enum values for DPI stages. Turns out this is not the case. The device is recognized but the GUI doesn't seem to issue the correct commands to the device. I captured USB traffic for certain LED-changing scenarios but it's not easy to reverse the protocol from this subset of captures. Needs more investigation. Were "breathing" and "reactive" lighting options available on previous devices? This is my first Razer mouse. Maybe Synapse 2.0 makes use of spare bits/fields in the protocol for the extended lighting options, etc. |
I want to contribute to add support for Elite. I also have the hardware |
Great. Please don't hesitate to do so. |
@lswest perhaps embed the USB ID in the issue subject? My Elite is $ lsusb | grep Razer
Bus 002 Device 007: ID 1532:005c Razer USA, Ltd
$ |
Is there anyone working on support for this device yet?
Based off the functionality, I'm not sure it's that much different from the chroma version - most of the changes were to the shape, the sensor, and the buttons themselves. The USB ID is:
1532:005c
.The text was updated successfully, but these errors were encountered: