Luke Horwell

This might be an easy fix. Looks like the driver just didn't implement the logic for this device. * #2613 Since you're using Arch Linux, please could you test this...

Thank you for testing! When #2613 is reviewed/merged, this'll be fixed in the next release. 1. Snap tap isn't implemented. OpenRazer doesn't know what USB commands to use. See [#2606.](https://github.com/openrazer/openrazer/issues/2606)...

We recently had a report of a mouse wheel button doing nothing for a Basilisk V3 X HyperSpeed (#2428). Changing the mouse to "driver mode" fixed the problem. Might be...

Thanks for confirming! I've created #2509 so a future OpenRazer update can always set this device in driver mode, assuming that is the way forward. For now, you'll need to...

Thank you for the update. I've added a section to downgrade in our [troubleshooting guide](https://github.com/openrazer/openrazer/wiki/Troubleshooting#try-a-hardware-reset) - it does sound like Synapse 4 does something to the device that causes this...

Not 100% certain on how Razer Synapse works, but it's possible that when it's "running", the buttons are under software control (via the Windows driver). When it's closed it might...

Thanks! The best way to test would be to build a package from your branch: * https://github.com/openrazer/openrazer/wiki/Building-a-package To satisfy the checks, run this and commit the result: ./scripts/format_source.sh

OpenRazer only supports devices that work with USB protocols. I imagine this one would use HTTP or similar. I think it might be outside the scope of OpenRazer, sadly. This...

It seems to be feature handled by the firmware, so adding support is possible. We don't know what USB commands it uses. Please use Wireshark and a VM to capture...

Hello. The maintainers don't have this hardware, so it will rely entirely on community contributions to add support. If it has RGB to configure, then within scope of OpenRazer. However,...