[Bug 1385113]
"unknown main tag item 0x0" comes from the HID layer, it has nothing to do with Bluetooth or connection stability. It's usually a stray NUL character at the end of the HID descriptor which the kernel safely ignores but still logs. In my own driver development (xpadneo), I just shorten the HID descriptor by one byte if it ends with NUL because the devices I work with are known to NUL-terminate their HID descriptors. Maybe the kernel should do the same: If the last HID descriptor byte is a NUL-byte, it should simply shorten the HID descriptor by one byte, essentially cutting the offending byte off, and the message would be gone. Other than a log message, it has no consequences in the kernel, it comes from a completely different layer that's not related to Bluetooth at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750146]
Yeah, it seems to get worse with every 5.4 LTS update. Worked almost flawless about some months ago (despite taking something from 30-60s to successfully connect). But I don't see a correlation to any commits. But now, it's almost impossible to connect successfully, it usually disconnects after a 1-2 minutes (coincidentally just when entering a game). I usually also see messages like this: During use of the controller (probably around disconnect time): [ 5304.480502] Bluetooth: Unexpected continuation frame (len 52) When plugging the BT dongle: [ 5241.926752] Bluetooth: hci0: unexpected event for opcode 0x While it's in a loop of constantly connecting and disconnecting: [ 1120.736530] Bluetooth: hci0: hardware error 0x58 [ 1120.923550] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 1120.923555] debugfs: File 'le_max_key_size' in directory 'hci0' already present! [ 1120.923557] debugfs: File 'force_bredr_smp' in directory 'hci0' already present! Other BT devices seem to just work fine tho I don't use a lot of them and only occasionally. It seems that the Xbox One S firmware does something strange in the BT protocol. It also needs either ERTM disabled to connect. Alternatively, one can apply this patch to be able to use ERTM: https://github.com/kakra/linux/commit/c8b24d83f227a7fecfa9420d6756074e8f9b542c I'm also feeling there's some internal state getting messed up within the controller on each BT pairing: Results are not really reproducible. I managed to get it to work flawlessly one time (stable connection despite 20-30s connect handshake time), then purged my Bluetooth config from /var/lib, re-paired the controller and now it's a mess - still with the same kernel version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750146 Title: Xbox (One) Wireless Controller won't connect To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
