- Top Pick: Xbox Wireless Controller — Carbon Black
- Runner-up: Xbox Wireless Controller — Robot White
- Also consider: Xbox Elite Series 2 Core — White
Pair an Xbox controller to a Linux PC over Bluetooth and it mostly works — until it doesn’t. The battery level never shows up, rumble arrives mangled or not at all, and the Series pad’s Share button is dead weight. None of that is the controller’s fault. It is the gap between what the in-kernel xpad driver covers and what these pads actually send over a Bluetooth link.
xpadneo exists to close that gap. It is an out-of-tree HID driver, maintained as the hid_xpadneo kernel module, that takes over Xbox One generation controllers the moment they connect over Bluetooth. This guide covers what it changes, which controllers the project documents as supported, how installation works — Secure Boot catch included — and when the stock driver or a cable is honestly the better answer.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
xpadneo is a community-maintained, out-of-tree Linux driver for Xbox One S, Series X|S and Elite Series 2 controllers over Bluetooth. Versus the stock setup it delivers a consistent mapping including the Share button, working rumble with trigger force feedback, correct signed axes, and battery level reporting. It installs through DKMS, needs kernel 4.18 or newer, and must be signed on Secure Boot systems.
What xpadneo actually changes
The project’s own list of advantages is specific, and each item maps to a real annoyance in the stock setup. The mapping is consistent even if the pad was previously paired to Windows or an Xbox, and it stays the same across software layers — SDL games, Steam Input and browsers all see the same layout. Axis ranges are correct and signed, which matters to emulators that read raw values. The Share button on Series X|S pads is supported and currently mapped to a keyboard F12 event, which Steam uses for screenshots.
Rumble gets the deepest work. Instead of routing effects through the kernel’s generic ff-memless layer, the driver streams rumble directly, avoiding the aliasing the generic layer introduces. It also adds trigger force feedback in every game by making the trigger motors follow the main rumble effect with pressure-dependent intensity — something the project notes is not offered on Windows at all. Rumble strength can be adjusted, or switched off, through the driver’s configuration.
Battery reporting is the third pillar. The driver exposes the pad’s charge level to the desktop, including when the official Play and Charge style rechargeable pack is fitted. Smaller documented extras sit on top: working back paddles on the Elite Series 2, exposure of the selected profile to user space, an optional high-precision mode for Wine and Proton players that disables the driver’s dead zones so games do not stack a second one, and a couch mouse mode on Guide plus Select.
Three drivers, three different jobs
Confusion starts because Linux has three Xbox drivers, divided by connection type. The in-kernel xpad driver is the default: it handles these controllers over USB, which is why a wired pad simply works on any modern distribution with nothing installed. xpadneo covers exactly one route — Bluetooth — and replaces the generic handling for that link only. The third driver, xone, exists for Microsoft’s official wireless dongle and the native Xbox Wireless protocol; it is a separate project and install.
That split has a practical consequence. Installing xpadneo changes nothing about how your pad behaves on a cable, and it does nothing for the dongle. It also cannot add controller audio over Bluetooth: the project states plainly that audio is unavailable in Bluetooth mode because the controller firmware does not support it there. If headset audio through the pad is your goal, the dongle or a cable is the answer.
Which controllers the project supports
Support is documented per model, and the three Microsoft pads sit at different levels. The Xbox One S controller, model 1708, is the original target and is listed as fully supported in every feature. The Xbox Series X|S controller, model 1914, is also fully supported, Share button included. Two documented caveats apply to it: it speaks Bluetooth Low Energy, so your adapter must support BLE, and the project documents a known problem where the pad may fail to set its connection parameters properly, showing up as laggy, choppy input — its troubleshooting pages cover the workarounds.
The Xbox Elite Series 2 is listed with basic support covering the driver’s features, including its paddles and native profile switching. The documented gap is that uploading profile mappings and sensitivity curves is not supported; profiles built in the Xbox Accessories app on Windows carry over and operate, but cannot be created or edited from Linux. Beyond Microsoft hardware, the project also documents quirk-based support for some third-party pads that imitate the Xbox Bluetooth protocol — certain 8BitDo, GuliKit KingKong and GameSir T4 models — enabled through per-device quirk flags.
Installing it, and the Secure Boot catch
The prerequisites are the same trio for every route: DKMS, the kernel headers matching your running kernel, and a Bluetooth stack such as BlueZ. Many distributions package the driver directly, the lowest-maintenance path; Arch users will also find it in the AUR. Installing from source is a short sequence — clone the repository and run the install script, which registers the module with DKMS so it rebuilds automatically after kernel updates.
Secure Boot is where newcomers get stuck. An out-of-tree module is not signed with your distribution’s key, so a Secure Boot system will refuse to load it until it is signed. The project’s packaging notes point to the standard remedy: sign the module and enrol your own machine owner key using openssl and mokutil, the same machinery DKMS uses for module signing. The alternative is disabling Secure Boot, which trades away a platform security feature to save ten minutes — signing is the better habit. Either way, expect this step; it is the most common reason a fresh install appears to do nothing.
Configuration worth knowing
Most people never touch the options, but they are there: the configure script and module parameters let you disable force feedback entirely, adjust how strongly the trigger rumble follows the main motors, set quirks for specific devices by Bluetooth address — the mechanism the third-party pad support hangs off — and disable emulated profile switching or the mouse mode.
One fix lives outside the driver: if a paired pad connects and drops in a loop, the project’s documentation describes disabling Enhanced Retransmission Mode for the Bluetooth stack as the stabilising fix for chipsets that mishandle it.
When the stock driver or a cable is the better answer
xpadneo is not compulsory. If you play wired, xpad already gives you a complete, zero-maintenance experience and this driver will never even load. If your Bluetooth use is casual and you do not miss the battery readout or trigger rumble, the stock handling may be all you need. Steam Deck and SteamOS users are in a similar position: the built-in handling there is already curated for these pads. And anyone unwilling to maintain a DKMS module should weigh that upkeep honestly against the feature list above.
The hardware that pairs with it
Xbox Wireless Controller — Carbon Black
The benchmark Series X|S pad: model 1914 hardware with full documented xpadneo support, Share button included.
Specs:
– Controller model 1914 (retail code QAT-00001)
– Bluetooth, Xbox Wireless and USB-C wired connections
– Share button and hybrid D-pad
– Power: two AA batteries, included; rechargeable pack sold separately
– Maker battery figure: up to 40 hours on AA batteries
Xbox Wireless Controller — Robot White
The same model 1914 platform in the white finish, for a second pad or a lighter colourway.
Specs:
– Controller model 1914 (retail code QAS-00007)
– Bluetooth, Xbox Wireless and USB-C wired connections
– Share button and hybrid D-pad
– Power: two AA batteries, included
– Maker battery figure: up to 40 hours on AA batteries
Xbox Elite Series 2 Core — White
The Elite hardware tier, in the Core package without the accessory kit — the pad family xpadneo’s paddle and native profile support is written for.
Specs:
– Elite Series 2 family (retail code 4IK-00001)
– Adjustable-tension thumbsticks and shorter hair trigger locks
– Internal rechargeable battery, maker-rated up to 40 hours
– In the box: controller, USB-C cable, faceted D-pad, standard thumbsticks, adjustment tool
– xpadneo support: basic, with native profile switching; profile uploads not supported
TP-Link UB500 Bluetooth USB Adapter
The Series X|S pads speak Bluetooth Low Energy, so the adapter has to speak it too. This nano adapter’s listing confirms EDR and BLE support — the requirement that matters.
Specs:
– Nano USB adapter, model UB500
– Bluetooth with EDR and BLE support (required for Series X|S pads)
– Listings span several hardware revisions
Xbox Rechargeable Battery + USB-C Cable
Microsoft’s own rechargeable pack for the Series X|S and One pads — and the pack xpadneo’s battery reporting explicitly covers.
Specs:
– Official Microsoft rechargeable battery pack
– USB-C cable included; charges inside the controller
– Fits Series X|S and Xbox One controllers
– Maker figure: full charge in under 4 hours
– Recharge while playing or between sessions
How to choose
Start with the pad you own or want. A model 1708 or 1914 pad gets the driver’s full documented feature set; an Elite Series 2 gets everything except profile editing. Check your Bluetooth adapter next: anything BLE-capable suits the Series pads, while older dongles without LE support will leave a 1914 pad undiscovered no matter which driver is installed. Then decide your maintenance appetite. A distribution package or self-rebuilding DKMS install is a small but real commitment — on a Secure Boot machine, budget the one-time signing step into the install, not as a surprise afterwards.
Who should skip this
Skip xpadneo if you only ever play on a cable: xpad already covers you and the driver adds nothing. Skip it if your wireless route is Microsoft’s dongle, since that is xone’s territory. Skip it if you need headset audio through the controller over Bluetooth — no driver can add what the firmware does not offer there. Owners of Xbox 360 pads can also pass; those are served by the stock drivers and sit outside this project’s scope. Finally, skip it if an unsigned kernel module is a hard no and you do not want to manage your own signing key.
FAQ
Does xpadneo work over USB or with the official dongle?
No. The driver handles Bluetooth connections only. Over USB the in-kernel xpad driver is in charge, and the official wireless dongle is served by the separate xone project. All three can coexist on one system.
Will xpadneo load on a Secure Boot system?
Not in its unsigned state. Secure Boot rejects an out-of-tree module until it is signed with a machine owner key you enrol yourself, using the openssl and mokutil route the project’s packaging notes describe.
Why does my Series X|S pad feel laggy or choppy over Bluetooth?
The project documents this as a known problem: the pad may not set its connection parameters properly, which produces laggy, choppy input. Its troubleshooting documentation covers the remedies, starting from a BLE-capable adapter and current controller firmware.
Can I update my controller’s firmware from Linux?
No. Microsoft delivers controller firmware only through the Xbox Accessories app on Windows or through an Xbox console. That matters because outdated firmware is a documented cause of Bluetooth pairing trouble on the Series pads, so a borrowed Windows machine or a console remains part of the toolkit.
Final verdict
xpadneo does one job — making Xbox controllers behave properly over Bluetooth on Linux — and its documentation shows the work: correct mapping, real rumble with trigger feedback, honest battery reporting and per-model support notes that admit their own limits. If Bluetooth is how your pad connects, installing it through DKMS is the closest thing to a default recommendation this niche has. If you live on a cable or the dongle, let xpad and xone do their jobs instead.











