Skip to content
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

Bluetooth peripherals not recognized #2205

Open
2 tasks done
Kaukov opened this issue Feb 8, 2024 · 8 comments
Open
2 tasks done

Bluetooth peripherals not recognized #2205

Kaukov opened this issue Feb 8, 2024 · 8 comments
Labels

Comments

@Kaukov
Copy link

Kaukov commented Feb 8, 2024

Distribution

Support

I have a Naga Pro and a BlackWidow V3 Mini. Both work flawlessly when connected via cable or via their respective dongles.

However, when I connect any of them via bluetooth, OpenRazer no longer sees them and can't control them at all. This means that I can't control their backlight, effects, or synchronize them with my other Razer devices.

lsusb doesn't display any of the bluetooth-connected devices. I think this is normal since they're not connected via USB at all.

I have a Windows partition on the same laptop and I can debug anything you need, I just need instructions on how to do it.

Running Gentoo with kernel 6.7.3 currently. Kernel modules and everything is working except for this issue.

@Kaukov Kaukov added the support label Feb 8, 2024
@z3ntu
Copy link
Member

z3ntu commented Feb 12, 2024

lsusb doesn't display any of the bluetooth-connected devices. I think this is normal since they're not connected via USB at all.

For most devices they show up there, according to #1544 (comment) also the BlackWidow V3 Mini Hyperspeed should show up there.

Perhaps you're missing some kernel config option (since you're running Gentoo)?

@z3ntu
Copy link
Member

z3ntu commented Feb 12, 2024

Check that you've enabled CONFIG_UHID and the module is loaded.

@Kaukov
Copy link
Author

Kaukov commented Feb 12, 2024

Check that you've enabled CONFIG_UHID and the module is loaded.

Here's what I got:

~ > zgrep -i uhid /proc/config.gz
CONFIG_UHID=m
~ > lsmod | grep -i uhid
uhid                   16384  1

And the devices are still not visible via OpenRazer or lsusb.

I also found the module btusb but it was loaded by default:

~ > lsmod | grep -i btusb
btusb                  73728  0
btrtl                  28672  1 btusb
btintel                49152  1 btusb
btbcm                  20480  1 btusb
btmtk                  12288  1 btusb
bluetooth             884736  48 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm

@z3ntu
Copy link
Member

z3ntu commented Mar 3, 2024

Might be worth checking on e.g. an Ubuntu livecd image, connect the Bluetooth mouse there and check if it shows up in lsusb. I don't own any Razer Bluetooth devices myself so it's difficult to judge how it really behaves in practice.

@Kaukov
Copy link
Author

Kaukov commented Mar 3, 2024

lsusb doesn't see the bluetooth-connected device. But bluetoothctl devices shows it.

@z3ntu
Copy link
Member

z3ntu commented Apr 4, 2024

As per example #1553 (comment) I'd expect your device should also show up a bit like this

[ 6818.110674] hid-generic 0005:1532:0095.001C: input,hidraw1: BLUETOOTH HID v0.01 Mouse [Orochi V2] on 18:56:80:29:62:64
[ 6818.140984] elogind-daemon[1378]: Watching system buttons on /dev/input/event9 (Orochi V2 Consumer Control)
[ 6818.147656] elogind-daemon[1378]: Watching system buttons on /dev/input/event11 (Orochi V2 System Control)
[ 6818.147732] elogind-daemon[1378]: Watching system buttons on /dev/input/event23 (Orochi V2 Keyboard)
[ 7463.581348] input: Orochi V2 Mouse as /devices/virtual/misc/uhid/0005:1532:0095.001D/input/input88
[ 7463.581437] input: Orochi V2 Consumer Control as /devices/virtual/misc/uhid/0005:1532:0095.001D/input/input89
[ 7463.581474] input: Orochi V2 System Control as /devices/virtual/misc/uhid/0005:1532:0095.001D/input/input90
[ 7463.581501] input: Orochi V2 as /devices/virtual/misc/uhid/0005:1532:0095.001D/input/input91
[ 7463.581571] input: Orochi V2 Keyboard as /devices/virtual/misc/uhid/0005:1532:0095.001D/input/input92

There the USB VID:PID is 1532:0095

Why it doesn't for you I'm really unsure.

@Kaukov
Copy link
Author

Kaukov commented Apr 5, 2024

I'm currently using another laptop with OpenSUSE Tumbleweed on it. Testing with the Razer Naga Pro mouse.

When connecting via bluetooth, the mouse appears in lsusb and is shown in Polychromatic as Razer Naga Pro (Wireless), but the battery is shown as 0% and I can't control any of the mouse's properties like brightness, polling, etc. This happened because the dongle was still connected to the system. After disconnecting the dongle, the mouse disappeared from everywhere. So the issue still persists.

Is this a Polychromatic issue or an OpenRazer one?

Here are my dmesg logs: (deleted the old log as it was falsy)

[302014.104613] input: Naga Pro Mouse as /devices/virtual/misc/uhid/0005:1532:0092.0022/input/input77
[302014.104880] input: Naga Pro Consumer Control as /devices/virtual/misc/uhid/0005:1532:0092.0022/input/input78
[302014.105026] input: Naga Pro System Control as /devices/virtual/misc/uhid/0005:1532:0092.0022/input/input79
[302014.105141] input: Naga Pro as /devices/virtual/misc/uhid/0005:1532:0092.0022/input/input80
[302014.105220] input: Naga Pro Keyboard as /devices/virtual/misc/uhid/0005:1532:0092.0022/input/input81
[302014.105297] hid-generic 0005:1532:0092.0022: input,hidraw14: BLUETOOTH HID v0.01 Mouse [Naga Pro] on 1c:1b:b5:22:84:99

The mouse appears in the logs, but is nowhere to be found in Polychromatic, can't be controlled, and doesn't appear via lsusb.

Edit 3: tried with razerCommander as well - it also doesn't see the bluetooth mouse, so it's an OpenRazer issue

@z3ntu
Copy link
Member

z3ntu commented Apr 6, 2024

I just saw there's HID_BLUETOOTH_DEVICE in the kernel sources, so maybe that's somehow useful for matching on 1532:0092 for example. Also pretty sure e.g. razer_get_usb_response in the driver wouldn't work on Bluetooth, not sure what other code we'd need to have there instead. Udev rules actually look like they could/should also be able to match on these Bluetooth devices.

In short, somebody with such a device in hand will need to try to hack on it and add some code for it. I can't do it without such device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants