Audrius

The way this works is this: 1. The apexctl utility itself only enables those extra keys, so they could be seen in evtest 2. **udev then translates those raw scancodes...

This might actually be worth looking into, because right now starting ApexCtl causes a driver detach in linux, which registers as a device unplug/plug, which doesn't feel 'clean'. After quickly...

It seems that you interpreted ApexCtl's behavior correctly and as far as I can tell there is nothing wrong with your script. Just make sure that you are invoking the...

Unfortunately right now this is expected behavior. This is because when changing keyboard colors, ApexCtl uses a command that has to specify colors for all zones. When you skip some...

I'm sure that USB request that reads existing color profile exists, but it isn't implemented in ApexCtl. I would need to fire up my VM with Steelseries software and capture...

Yeah, I totally forgot about those keys. It does make sense to rebind those keys to something more useful.

Please paste the command line you used to achieve this weird behavior.

If I had to guess I'd say that these binaries depend on different versions of libusb and that's why things get messed up.

That looks like GHC installation issue. Make sure that you have a working installation of GHC.

@gericom-hummer I'm not using an Apex keyboard anymore, so I can't test the utility well. However, in order to make different keys work, you need to properly install the 90-apex.hwdb...