All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221449] New: Wireless gamepad stopped working through Bluetooth
Date: Fri, 01 May 2026 22:37:17 +0000	[thread overview]
Message-ID: <bug-221449-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221449

            Bug ID: 221449
           Summary: Wireless gamepad stopped working through Bluetooth
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: arvin.ignaci@gmail.com
        Regression: No

I'm running Fedora Silverblue 44 (Universal Blue image) with kernel version
6.19.14. Some time in the last month or so, a Bluetooth gamepad I had stopped
working. It started with inputs being mapped incorrectly and certain inputs not
being recognized. Now, I don't get any input at all. The same gamepad used to
work just fine over Bluetooth and still works over USB.

The gamepad is a GuliKit KK3 set to the "Android" pairing mode; It shows up as
an "Xbox Wireless Controller" in Linux. My Bluetooth controller appears to be
an Intel AX200 modem (according to lsusb). When I connect the gamepad via
Bluetooth and try pressing some buttons or moving the sticks around, the dmesg
output is filled with these messages:

> [ 2041.273972] hid_report_raw_event: 14 callbacks suppressed
> [ 2041.273976] microsoft 0005:045E:02FD.000C: Event data for report 1 was too
> short (16 vs 15)
> [ 2041.277912] microsoft 0005:045E:02FD.000C: Event data for report 1 was too
> short (16 vs 15)
> [ 2041.280044] microsoft 0005:045E:02FD.000C: Event data for report 1 was too
> short (16 vs 15)
> [ 2041.288927] microsoft 0005:045E:02FD.000C: Event data for report 1 was too
> short (16 vs 15)
> [ 2041.300915] microsoft 0005:045E:02FD.000C: Event data for report 1 was too
> short (16 vs 15)
> [ 2041.309919] microsoft 0005:045E:02FD.000C: Event data for report 1 was too
> short (16 vs 15)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2026-05-01 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 22:37 bugzilla-daemon [this message]
2026-05-01 23:36 ` [Bug 221449] Wireless gamepad stopped working through Bluetooth bugzilla-daemon
2026-05-05  5:09 ` bugzilla-daemon
2026-05-06  2:12 ` bugzilla-daemon
2026-05-06  4:27 ` bugzilla-daemon
2026-05-06  6:39 ` bugzilla-daemon
2026-05-06  6:40 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-221449-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.