On Wed, 2022-12-07 at 12:07 +0100, Rafael J. Wysocki wrote: > # hidpp-list-features /dev/hidraw1 > Bluetooth Mouse M336/M337/M535 (046d:b016) is a HID++ 4.5 device > Feature 0x01: [0x0001] Feature set > Feature 0x02: [0x0003] Device FW version > Feature 0x03: [0x0005] Device name > Feature 0x04: [0x0020] Reset > Feature 0x05: [0x1e00] Enable hidden features (hidden) > Feature 0x06: [0x1800] Generic Test (hidden, internal) > Feature 0x07: [0x1000] Battery status > Feature 0x08: [0x1b04] Reprog controls v4 > Feature 0x09: [0x2100] Vertical scrolling > Feature 0x0a: [0x2200] Mouse pointer > Feature 0x0b: [0x2205] Pointer speed > Feature 0x0c: [0x18b1] ? (hidden, internal) > Feature 0x0d: [0x2121] Hi-res wheel > Feature 0x0e: [0x1f03] ? (hidden, internal) Would you be able to enable debugging for the hid subsystem to get some debug data when getting the version from the device fails? I can't see any problems in there that wouldn't also have impacted all the other Logitech Bluetooth devices listed in the support devices list. If the problem is a timeout, maybe we should lower the timeouts we currently have (5*HZ = 5 seconds, right?), so we can retry 5 times one second instead. Still, as I mentioned earlier, I can't reproduce the problem on another Bluetooth Classic device...
