Bluetooth devices nowadays have UserspaceHID enabled by default - since 2024-03~ apparently:
/etc/bluetooth/input.conf
# Enable HID protocol handling in userspace input profile
# Defaults to true (Use UHID instead of kernel HIDP)
#UserspaceHID=true
As a result, SC-controller does not recognize my BT connection on a v2 DS4 on my system as per #21 (comment) due to grabbing the HCI path which is not used, instead of the UHID one. Same issue is also in #13.
No clue how to fix this as I cannot figure out where syspath is taken from.
|
rv: ctypes.c_char_p | None = self._eudev._lib.udev_list_entry_get_name(self._next) |
Here's the bastard.
Looks like we could do something like this?
https://github.com/libusb/hidapi/blob/master/linux/hid.c#L714-L728C9
Bluetooth devices nowadays have UserspaceHID enabled by default - since 2024-03~ apparently:
As a result, SC-controller does not recognize my BT connection on a v2 DS4 on my system as per #21 (comment) due to grabbing the HCI path which is not used, instead of the UHID one. Same issue is also in #13.
No clue how to fix this as I cannot figure out where syspath is taken from.sc-controller/scc/lib/eudevmonitor.py
Line 216 in 9e3f65e
Here's the bastard.
Looks like we could do something like this?
https://github.com/libusb/hidapi/blob/master/linux/hid.c#L714-L728C9