search

mbuesch / razer

Razer device library and tools
http://bues.ch/h/razercfg
GNU General Public License v2.0
250 stars 50 forks source link

DeathAdder Elite (2016) #92

Open lswest opened 7 years ago

lswest commented 7 years ago

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.

mbuesch commented 7 years ago

This device is not supported and as far as I know nobody is working on it, yet.

lowlyocean commented 7 years ago

+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

Pillgar commented 7 years ago

Would love to see this mouse supported. Much better tracking with the new optical sensor.

lowlyocean commented 7 years ago

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.

fuzunspm commented 4 years ago

I want to contribute to add support for Elite. I also have the hardware

mbuesch commented 4 years ago

Great. Please don't hesitate to do so.

skewty commented 4 years ago

@lswest perhaps embed the USB ID in the issue subject? My Elite is 1532:005c I don't know what (2016) means or if that will help others.

$ lsusb | grep Razer
Bus 002 Device 007: ID 1532:005c Razer USA, Ltd 
$