astrosnail / apexctl Goto Github PK

The command apexctl bright 1 1 (had to run as sudo) worked for my Apex Raw keyboard -- I'd appreciate if this information was added to the readme to ease the setup for new users.

Hello, should I do a PR to README file just to say it works? Never had problems

Will the rewrite make apexctl compatible with new keyboards in the series like the Apex Pro? I'd be interested in getting one if I knew I could use it on Linux (specifically, Fedora 30).

The extra keys on my apex 350 must be enabled on wake, is this expected? To be persistent through sleeps should I add sudo apexctl keys on to my ~/.xinitrc?

Hi, wondering if apex 7 would work, its very similar to the apex 3.

Hello, i have an apexM800 and im interested into helpig you to make it work on this keyboard

Hello,

thank you for creating this thingy :)

Going to contribute here with my feedback on making this work for Steelseries Apex Raw and Ubuntu 18.04 LTS.

I ran this command to install dependencies:

sudo apt install libhidapi-dev pkgconf

It said that I already had libhidapi-dev installed and it only installed pkgconf (pkgconf_0.9.12-6_amd64.deb). After that I ran make and got this error:

cc -std=c99 -Werror=all -Wextra -Wpedantic -Os $(pkgconf --cflags hidapi-libusb) -DENABLE_CMD_PROBE=1 -DENABLE_DATA_PRINT=0 -s $(pkgconf --libs hidapi-libusb)  apexctl.c   -o apexctl
/tmp/cciXZ1b7.o: In function `usb_setup':
apexctl.c:(.text+0x1a2): undefined reference to `hid_init'
apexctl.c:(.text+0x1bf): undefined reference to `hid_open'
/tmp/cciXZ1b7.o: In function `usb_cleanup':
apexctl.c:(.text+0x202): undefined reference to `hid_close'
apexctl.c:(.text+0x208): undefined reference to `hid_exit'
/tmp/cciXZ1b7.o: In function `usb_put':
apexctl.c:(.text+0x210): undefined reference to `hid_send_feature_report'
collect2: error: ld returned 1 exit status
<builtin>: recipe for target 'apexctl' failed
make: *** [apexctl] Error 1

Any ideas?

I tried searching online and found something related to header files being included in wrong order or something like that. My C is very rusty, but I'm hoping to remember it.

I'm on Fedora 31 using a Steelseries APEX 3 keyboard.

Every command I try with apexctl gives me the error "Re-run as root!" while I am running the command as root. However, the commands apexctl, or apexctl -h give the help text.

Please help to fix this.

The title says it all:
https://youtu.be/W81LvtMsQ0w

Hello.
I'm working on daily driving linux and your tool seemed like the perfect (and kind of only, haha) option to get my keyboard running.

The board is a rebranded Apex 350 by HP and shows as
ID 1038:120a SteelSeries ApS
in lsusb and
SteelSeries SteelSeries Apex 350 HP Omen
in evtest

At first it wasn't recognized because the reported id doesn't match any of the ones in the program, but after adding it manually to steelseries.txt it seemed to work fine when testing with the lights.

The problem arises when trying to actually use the extra keys; they're all over the place (MX6, 7 and 8 are vol up, down and mute respectively, and M5 is sleep, for example).

Checking with evtest, the keyboard seems to be reporting the correct scans as listed in the hwdb files, but they're sending the wrong codes.
Some examples:
M9-12 and L1-4 all send keycode 240
M1-4 send 136, 177, 178 and 176 respectively instead of 148-151

I dug around the files a little looking for an offset of some kind or something, but I'm not really a programmer, so I don't really understand how the program works or what I'm even potentially looking for.

Any ideas on what I could try?
I can provide any further information I might've missed or is otherwise required.

At least Apex Raw requires running the Steelseries software on the background for the macro keys to work (on Windows), the changes aren't seemingly written to the device. I wanted to ask if the maintainer desires macro support and whether it can be realistically achieved.

Hi,
fist i would like to thank you for this great program, for me is a must have.
I'm running manjaro, and i have notice, specialy after suspend, that my usb device won't be recognized. I have analyze the system log and i found some udev continuos error about apexctl. I don't know if this error is the cause of the above problem. And i notice this behavior in the last weeks, maybe some major update have change something. But anyway if i install apexctl i have many error that you can see in the log that i have attached. If you can take a look i will apreciate.
thanks
apexctl.log