@lohvht Hi there, could you dump without cable, just the dongle plugged in?

Hi! Thanks for responding, certainly!

Additional Details

Add any additional details here.

The output from the commands below are dumped with mouse connected via the slipstream dongle.

❯ sudo ./getUsbString 0x1b1c 0x1bdc 4
Read 52 bytes
Raw (hex): 34 03 42 00 6f 00 6f 00 74 00 6c 00 6f 00 61 00 64 00 65 00 72 00 20 00 76 00 65 00 72 00 73 00 69 00 6f 00 6e 00 3a 00 20 00 30 00 2e 00 30 00 2e 00 36 00 
String: Bootloader version: 0.0.6

❯ sudo ./getUsbString 0x1b1c 0x1bdc 5
Read 10 bytes
Raw (hex): 0a 03 42 00 50 00 30 00 30 00 
String: BP00

sudo usbhid-dump -d 1b1c:1bdc
003:008:003:DESCRIPTOR         1695303164.191031
 05 01 09 06 A1 01 85 01 05 08 95 03 75 01 19 01
 29 03 15 00 25 01 91 02 95 05 91 03 05 07 75 01
 19 E0 29 E7 15 00 25 01 95 08 81 02 19 00 29 67
 15 00 25 01 95 68 81 02 19 87 29 8E 95 08 81 02
 C0 05 0C 09 01 A1 01 85 02 95 01 75 10 15 00 26
 FF 03 19 00 2A FF 03 81 00 C0

003:008:004:DESCRIPTOR         1695303164.194015
 05 01 09 02 A1 01 09 01 A1 00 75 10 95 02 05 01
 09 30 09 31 16 01 80 26 FF 7F 81 06 C0 C0

003:008:005:DESCRIPTOR         1695303164.197015
 05 01 09 06 A1 01 85 01 05 07 75 01 19 E0 29 E7
 15 00 25 01 95 08 81 02 19 00 29 8B 15 00 26 FF
 00 75 08 95 0D 81 00 C0 05 0C 09 01 A1 01 85 02
 95 01 75 10 15 00 26 FF 03 19 00 2A FF 03 81 00
 C0

003:008:002:DESCRIPTOR         1695303164.200004
 06 42 FF 09 02 A1 01 15 00 26 FF 00 75 08 95 40
 09 02 81 02 C0

003:008:001:DESCRIPTOR         1695303164.203008
 06 42 FF 09 01 A1 01 15 00 26 FF 00 75 08 95 40
 09 01 81 02 95 40 09 01 91 02 C0

003:008:000:DESCRIPTOR         1695303164.206006
 05 01 09 02 A1 01 09 01 A1 00 05 09 19 01 29 20
 15 00 25 01 95 20 75 01 81 02 75 10 95 02 05 01
 09 30 09 31 16 01 80 26 FF 7F 81 06 75 08 95 01
 05 01 09 38 15 81 25 7F 81 06 05 0C 0A 38 02 95
 01 81 06 75 08 95 05 06 00 FF 09 F1 15 00 26 FF
 00 81 00 C0 C0

Generated Report

Drag your generated report here.

The report below is dumped with mouse connected via the dongle
ckb-next-dev-detect-report.gz

Please do let me know if there's anything more that i can provide to help!

@lohvht hi there. You can use my branch #997 to test your mouse. Use these instructions: #855 (comment)

@lohvht hi there. You can use my branch #997 to test your mouse. Use these instructions: #855 (comment)

I really want to get this working for my Scimitar Elite Wireless, and I thank you very much for putting the work in to address the issue, but I cannot figure out how to use your branch. I am admittedly a big idiot when it comes to things like this.

I am currently using the ckb-next AUR package on arch. I tried adding that experimental option in the #855 link, but it didn't seem to change anything for me. Am I able to just switch something around to add the fixes you made, or do I have to like compile it from github? I've never done anything like that before and I see the wiki page on how to do compile from source, but I'm confused as to how to compile your specific pull request.

Sorry if this is all basic and I'm over complicating things. Tried to figure this out on my own before asking this, but just couldn't figure it out.

@lohvht hi there. You can use my branch #997 to test your mouse. Use these instructions: #855 (comment)

I really want to get this working for my Scimitar Elite Wireless, and I thank you very much for putting the work in to address the issue, but I cannot figure out how to use your branch. I am admittedly a big idiot when it comes to things like this.

I am currently using the ckb-next AUR package on you. I tried adding that experimental option in the #855 link, but it didn't seem to change anything for me. Am I able to just switch something around to add the fixes you made, or do I have to like compile it from github? I've never done anything like that before and I see the wiki page on how to do compile from source, but I'm confused as to how to compile your specific pull request.

Sorry if this is all basic and I'm over complicating things. Tried to figure this out on my own before asking this, but just couldn't figure it out.

You're welcome! Yes, first you have to checkout my branch, delete AUR package, then run installation steps (https://github.com/ckb-next/ckb-next/wiki/Linux-Installation), and after installation it's completed, you can add experimental parameters on you daemon.service, as you already look at old @Clofriwen post).

You don't have to apologize, I'm here to help.

You can send me an email if you get stuck on that.

Did a short test with my device:
So far seems to work really good. Keybinding and LED Animations work.

Only things I noticed so far is the DPI Indicator only doing Green an Yellow tones as if the green channel is stuck on 255 and Blue channel on 0. The other thing is the device DPI config itself I can not notice a difference between 800 and 6000 dpi, which seems wrong.

Did a short test with my device: So far seems to work really good. Keybinding and LED Animations work.

Only things I noticed so far is the DPI Indicator only doing Green an Yellow tones as if the green channel is stuck on 255 and Blue channel on 0. The other thing is the device DPI config itself I can not notice a difference between 800 and 6000 dpi, which seems wrong.

Hi cirk2, thanks for testing! I will check the led dpi configuration. Yes, changing DPI with the button only works when the CKB program GUI is not running, only on the daemon (the button is mapped correctly on GUI). My assumption is that the wireless version uses different DPI actions compared to the wired one. That's one thing that I'm working on right now to fix.

Did a short test with my device: So far seems to work really good. Keybinding and LED Animations work.

Only things I noticed so far is the DPI Indicator only doing Green an Yellow tones as if the green channel is stuck on 255 and Blue channel on 0. The other thing is the device DPI config itself I can not notice a difference between 800 and 6000 dpi, which seems wrong.

Hi there, I fixed the 12 button and the dpi action values, @INTOODEEP-dev, check my code again.

So far from my tests:
DPI xhange works fine now.
Button 12 Binding also works well.

The DPI indicator LED colors are still wrong (white and red both make the led yellow).

So far from my tests:
DPI xhange works fine now.
Button 12 Binding also works well.

The DPI indicator LED colors are still wrong (white and red both make the led yellow).

Yes, but there are fewer problems, one bug that's still remains are the side mouse buttons macros doesn't work, work only on keyboard. I'll see that issue with the ex-manteiner on irc channel.

Here's my report in case it helps
ckb-next-report-1715529666.gz