Martin

You need to hack your mouse in like so https://github.com/maxmati/a4tech-bloody-linux-driver/pull/21/commits/8ac3427281e42ae98212bcf3229f2c4753108d8c you can get the IDs from `lsusb`

@lotarbo Would you please give me information about your mouse so I can add it to my fork? How-to is here: https://gitlab.com/C0rn3j/a4tech_bloody_p85_driver/issues/2

Turns out the PID is based on HWID, so it's completely useless for the project, I will have to write a different detection. You could still help out with the...

It's described in the issue I linked above. The description and process could possibly be better, so if you have any improvements to it I am listening ^^ https://gitlab.com/C0rn3j/a4tech_bloody_p85_driver/issues/2

Both are wrong, PID does not reflect mouse version.

To clarify, you can compile it by executing following in the project folder ``` cmake ./ && make``` and then just running ```sudo ./bloody``` to run it.

Observing same behavior on P85, changing core seems to mess with the PID.

I think this may have to do with newer firmware being pushed into the mouse, and the FW has a different ID than the old one for some reason.

You have to set up wireshark to listen on USB and reverse engineer the protocol. https://github.com/pez2001/razer_chroma_drivers/wiki/Reverse-Engineering-USB-Protocol Here's how Razer chroma guys are doing it.

The PID is useless, it's based off of the mouse ID, so different for every mouse (unless cloned). Also this project is pretty much dead, check my fork out. (though...