Kai Krakow

> The last row is the only other one that is not all-zeroes. After the discussion on [atar-axis/xpadneo#428](https://github.com/atar-axis/xpadneo/issues/428), I had expected that it would be the same as #7814's data...

@smcv BTW, maybe of interest: In profile 0, the back paddles are hard-coded to buttons A,B,X,Y - so if profile 0 bit is set, you may want to ignore presses...

This is a known behavior and is explained by the fact how browsers implement input: they use evdev to detect the button mappings, then use jsdev to actually read the...

This is a new behavior of bluez that it no longer destroys input devices of disconnected endpoints, and reuses the same input device node if the endpoint reconnects. You can...

You could try `UserspaceHID=false`. It seems this was changed to default to true to actually support the "virtual cable unplug" flag.

There's also this in the changelog: ``` ver 5.55: ... Fix issue with handling HID virtual cable unplug. Fix issue with handling HID channel disconnect order. ... ver 2.8: ......

Can you guys verify that the controller is gone in `evtest` after you disconnected it? Also, after reconnected, check if another controller appears in `evtest` and if any of them...

If it shows `hidraw`, the system settings do not unconditionally use evdev devices. Using hidraw is usually done through SDL. Do your system settings use SDL for controller input? Our...

Yeah, qmk should really fix adjusting permissions only for supported devices. Usually, the desktop has no business in accessing the hidraw devices (you can confirm that by seeing that even...

I'm not sure what the question is. Do you intent to use xpadneo for the built-in deck controls? That doesn't make a lot of sense... Do you ask if -...