-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apex Pro Tkl Wireless #49
Comments
Hi, this is "normal", as we do not have every steelseries' keyboard, there are some that are not recognized by the the software, the list of recognized keyboard is stored in apex-hardware/src/usb.rs, currently, only 5 should work, I will do a pull request adding the apex pro tkl wireless (but won't be added now, I don't know when not-jan will be available) |
resolve [this issue](not-jan#49)
If you want to try it out, you can download my pull request here and compile it again, it should "just work", but since I'm not seeing any other wireless keyboard in the code, I can't promise anything |
okay btw , when i connect cable i see 2 device one is cable connected other one is wireless. |
|
kadir@kadir-GE76-Raider-11UH:~/repo/apex-tux$ sudo target/release/apex-tux |
not i got this error |
can you try running it as root? it seems like a udev issue |
yeah i am running it as root. i have tried this: kadir@kadir-GE76-Raider-11UH:~/repo/apex-tux$ sudo cat /etc/udev/rules.d/97-steelseries.rules SUBSYSTEM=="usb", ATTRS{idVendor}=="1038", ATTRS{idProduct}=="1632", MODE="0666", GROUP="plugdev" |
if you're already running as root, udev rules don't matter, I'm perplexed |
by chance, are you running openrgb? |
i have sim7600 module connected to my laptop also |
thank you for your clarification, i'm running an AMD system, but I don't think there should be any difference in how usb is handled by linux, the main difference that i can think of is the wireless part. can you try to edit the line in apex-hardware/src/usb.rs#21 from ApexProTKLWireless = 0x1630, to ApexProTKLWireless = 0x1632, then recompile, and try it in root when your keyboard is plugged in (to see if, when wired, apex-tux can recognize it) |
kadir@kadir-GE76-Raider-11UH:~/repo/apex-tux$ sudo target/release/apex-tux |
The thing i want is , i also want to watch battery status what i do on windows also. |
Depending on how the wireless is implemented this project may or may not work. I wouldn't hold my breath. Battery status for example is not implemented at all (and likely won't be unless one of the devs gets their hands on one of those keyboards). |
do you know how to sniff pcie data on windows ? |
Hi, I'm hitting the Anything I can do to help out? I'm up for a live debugging session over zoom (or any other conferencing option) if that would help... |
I tried to troubleshoot this myself and i've found out that the problem is at
tldr: the libusb_open(...) call returns this error:
I've tried chmod 666 /dev/hidraw*, and i've tried disabling selinux (i'm using Fedora 39), but none of that helped and neither did running apex-tux as root. |
Hi, sorry for responding late, I haven't touched apex-tux for quite some time. It seems weird, are sure no other software is using the keyboard? (openrgb, for example) I'm wondering if the wireless keyboard uses an alternate interface? could you try
|
|
Well this is weird, the second interface is a keyboard while the first is a mouse, I guess they share the same dongle for both keyboard and mouse? |
One thing you can try (but I wouldn't even place a bet on it), is change the line 44~ in usb.rs
and change the 1 to values between 2 and 5 |
if you want I can try to come on zoom or another site but I'm french so english is not my main language |
So we had a quick zoom meeting with jehendeoff but we couldn't make any progress. |
Quick recap :
(EDIT: darkprokoba also had the idea to make a recap, thank you) |
Hi, everyone. Thanks for the effort :) I think the easiest way would be for @darkprokoba to use the official SteelSeries software on Windows or Mac and use something like Wireshark to capture the USB traffic. Please include a step-by-step of what you did in the SteelSeries app so we can make sense of the data more easily. Please also include any images of GIFs so we can find them in the data stream. |
Hi, @not-jan
I have a color profile for all-white static backlight. I will attach the image i'm testing with. And here's the capture: https://prokoba.com/apex_pro_tkl_wireless.pcapng One thing bothers me though, apex-tux fails to open the hid raw device. I.e. it never gets to speaking to the device. Perhaps this is the first thing we need to address before looking for any protocol changes... |
BTW if you can recommend a set of steps to perform in the official windows software, I can provide another capture. |
i tried to use your software on
TK Pro Wireless
with
Zorin ( Ubuntu fork )
kadir@kadir-GE76-Raider-11UH:~/repo/apex-tux$ sudo target/release/apex-tux
Error: No supported SteelSeries device found!
kadir@kadir-GE76-Raider-11UH:~/repo/apex-tux$ cat /etc/udev/rules.d/97-steelseries.rules
SUBSYSTEM=="input", GROUP="input", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1038", ATTRS{idProduct}=="1630", MODE="0666", GROUP="plugdev"
KERNEL=="hidraw*", ATTRS{idVendor}=="1038", ATTRS{idProduct}=="1630", MODE="0666", GROUP="plugdev"
kadir@kadir-GE76-Raider-11UH:~/repo/apex-tux$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 1038:1122 SteelSeries ApS SteelSeries KLC
Bus 003 Device 004: ID 1038:1630 SteelSeries ApS Apex Pro TKL Wireless
Bus 003 Device 011: ID 1e0e:9001 Qualcomm / Option
Bus 003 Device 013: ID 1038:172b SteelSeries ApS SteelSeries Rival 650 Wireless
Bus 003 Device 008: ID 8087:0032 Intel Corp.
Bus 003 Device 007: ID 5986:1160 Acer, Inc Integrated Camera
Bus 003 Device 006: ID 1038:1134 SteelSeries ApS SteelSeries ALC
Bus 003 Device 002: ID 1038:1726 SteelSeries ApS SteelSeries Rival 650 Wireless
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Whats wrong ?
The text was updated successfully, but these errors were encountered: