How to use Xbox One controllers over Bluetooth on Linux

You’ve got Linux. You’ve got an Xbox One controller. You’ve got Bluetooth. In theory, you’re three steps away from gaming bliss. In practice, you might be one “connect… disconnect… connect… disconnect…” loop away from questioning reality. Don’t worrythis guide walks you from “Why is it blinking at me?” to “Why am I suddenly good at Rocket League?”

We’ll cover compatibility (the sneaky part), pairing (the straightforward part), and making it feel great in games (the part you’ll actually notice). Expect terminal commands, distro-friendly options, and troubleshooting that doesn’t assume you’re powered by moonlight and caffeine.

1) Check compatibility (aka “Does it even do Bluetooth?”)

Not every Xbox One controller speaks Bluetooth. The original Xbox One controllers used Microsoft’s proprietary wireless protocol (great on Xbox, not so great for random Linux laptops), and later revisions added Bluetooth for PC/phone friendliness. So before you spend an hour yelling at BlueZ, let’s make sure your controller can actually show up over Bluetooth.

Quick visual check (no microscope required)

• Bluetooth-capable Xbox Wireless Controller: the plastic around the Xbox button is part of the same faceplate as the controller body (it looks “all one piece”).
• Non-Bluetooth Xbox One controller: the area around the Xbox button looks like a separate piece (often glossier/different material).

If yours is the non-Bluetooth model, Bluetooth on Linux will never find itbecause it’s not broadcasting Bluetooth at all. Your options then are: use USB (easy), or use the official Xbox Wireless Adapter with a Linux driver (more on that later).

Model notes that matter

• Xbox One S-era controller (often referred to as the “1708” style): usually Bluetooth-capable.
• Xbox Series X|S controllers: Bluetooth capable (often BLE); generally supported on modern Linux, but can be pickier about adapters.
• Elite controllers: Bluetooth varies by generation; some features (like audio over BT) are typically limited in Bluetooth mode.

Pro tip: if your controller pairs perfectly to a phone via Bluetooth, that’s a strong sign it’s Bluetooth-capable. If your phone can’t see it either… it’s probably not Bluetooth, or it’s not actually in pairing mode (we’ll cover that too).

2) Prep your Linux Bluetooth stack

Linux Bluetooth is usually powered by BlueZ. Most distros already include it, but “installed” doesn’t always mean “enabled, running, and not currently sulking.” Let’s confirm the basics.

Step A: Make sure Bluetooth is unblocked

Step B: Start and enable the Bluetooth service

Step C: Install friendly tooling (optional but helpful)

You can pair via your desktop settings app, but having a Bluetooth manager can make device trust/reconnect less annoying.

Ubuntu/Debian

Fedora

Arch/Manjaro

Now you’re ready to pair. Pick your favorite route: GUI or terminal. (Terminal pairing is also the best way to see what’s actually happening.)

3) Pair using a GUI (GNOME/KDE/Blueman)

If you like clicking icons and living a peaceful life, the GUI method is for you.

1. Open Settings → Bluetooth and toggle Bluetooth on.
2. Put the controller in pairing mode:
   • Press the Xbox button to turn it on.
   • Press and hold the Pair/Sync button until the Xbox logo blinks rapidly.
3. On Linux, you should see something like “Xbox Wireless Controller” appear.
4. Select it → Pair/Connect.
5. If prompted, allow pairing (most of the time it’s “Just Works” with no PIN).

If it pairs but doesn’t reconnect later, that usually means the device isn’t marked as “trusted,” or the Bluetooth stack is being a drama queen. The terminal method below lets you force trust and remove stale pairings cleanly.

4) Pair using bluetoothctl (terminal method)

This is the “tell me what you’re doing” approach. It’s also the best option when the GUI can see the controller but refuses to connect.

Step-by-step pairing

Inside the bluetoothctl prompt, run:

Now put the controller into pairing mode (Xbox button on, then hold the Pair button until rapid blinking). Wait until you see the controller appearnote the MAC address.

How to confirm it’s actually working

Once connected, Linux should expose a gamepad device. Quick checks:

If it connects but no input device appears, that can be a driver/mapping issue (xpadneo often helps), or a Bluetooth LE quirk on some adapters. Keep goingthis is where the “good driver” section earns its keep.

5) Get better performance with xpadneo (recommended)

Linux has built-in controller support, but Bluetooth Xbox controllers can behave better with a dedicated driver stack. The fan-favorite is xpadneo, which focuses on Xbox One/Series controllers over Bluetooth and aims for consistent mapping, rumble support, and fewer weird edge cases.

Why people install xpadneo

• More consistent button mapping across games and layers (SDL/Steam Input/Wine).
• Better rumble behavior (including emulation for effects many games use).
• Battery reporting on many setups.
• Fixes/works around a bunch of “connects but feels wrong” Bluetooth behavior.

Prerequisites (the “don’t skip this” list)

You generally need DKMS, kernel headers, and BlueZ. Also note: for Bluetooth LE controllers (common with newer firmware/models), having the uhid module available matters because user-space (BlueZ) may create the HID device through it.

Ubuntu/Debian

Fedora

Arch/Manjaro

Install xpadneo (manual method)

If you’re using Secure Boot, kernel modules may need signing/enrollment to load. If your controller suddenly stops working right after installing and you see module load errors, Secure Boot is a prime suspect.

Pairing with xpadneo installed

Pairing is still done via your Bluetooth tools (GUI or bluetoothctl). After pairing, many users notice rumble/mapping improve. A small practical tip: once your controller shows up during scan, turning scanning off before pairing can reduce interference on some systems.

6) Use it in Steam and games (without losing your mind)

Once the controller is connected, most games “just see it” via SDL2 or the kernel input layer. Steam can also wrap it with Steam Input (great for remapping, sometimes confusing if you double-map).

Steam: quick setup

1. Open Steam → Settings → Controller.
2. Confirm the controller appears in the detected list.
3. If a game behaves oddly, test both modes:
   • Steam Input ON (good for remaps, gyro on other controllers, per-game layouts).
   • Steam Input OFF (lets the game read the controller directly).

Non-Steam games

For emulators and native Linux games, the controller is usually exposed as a standard gamepad device. If a game expects XInput specifically, Proton/Steam Input often bridges the gap.

Calibration and sanity checks

If you see drifting sticks: first confirm the controller itself is fine on another device; then check whether Steam Input is applying a deadzone, and whether the game has its own deadzone stacked on top. Two deadzones can make analog sticks feel like they’re stuck in molasses.

7) Troubleshooting: blinking, lag, reconnect loops

This is the section you came for. No judgment. Bluetooth can be… character-building.

Problem: The controller never shows up while scanning

• Confirm it’s Bluetooth-capable (see compatibility section).
• Make sure it’s actually in pairing mode: Xbox logo should blink rapidly, not slowly.
• Reset the controller: power it off (hold Xbox button ~6 seconds), then try pairing again.
• Restart Bluetooth:
• Check rfkill again (Bluetooth blocked is the silent villain).

Problem: It pairs, but immediately disconnects (or “connect-disconnect spam”)

This is a common symptom with certain controller/adapter/kernel combinations. One widely used workaround is disabling Bluetooth ERTM (Enhanced Re-Transmission Mode) for the session or via a persistent module option.

Temporary (until reboot)

Persistent (via modprobe config)

Then reboot, remove the old pairing, and pair again:

Important: disabling ERTM is a workaround, not a magic spell. On many modern kernels it’s not needed; on some setups it’s the difference between “unusable” and “works every day.” If you don’t need it, don’t keep itsimple.

Problem: It connects, but no input device appears

• If you’re using a newer controller over BLE, confirm the uhid module is available:
• Try installing xpadneo (it often resolves “connected but dead” symptoms).
• Check logs:

Problem: Input lag, choppy sticks, or “why is my aim haunted?”

• Move closer to the Bluetooth adapter (yes, really).
• Avoid 2.4GHz congestion (USB 3.0 ports, Wi-Fi 2.4GHz, cheap donglesBluetooth can suffer near noisy sources).
• Try a different Bluetooth adapter (some dongles are simply better at stable HID connections).
• Turn off scanning after pairing/connecting; constant scanning can degrade stability on some stacks.
• Use xpadneo for improved connection parameters/mapping on many setups.

Problem: It won’t reconnect after sleep or reboot

• Make sure the device is trusted in bluetoothctl.
• Remove and re-pair (stale keys happen, especially if you paired it to another OS/device).
• Consider using Blueman to mark it trusted and manage reconnection if your DE’s Bluetooth UI is limited.

Problem: Two controllers for couch co-op keep fighting

Bluetooth bandwidth and adapter quality matter. Some laptops handle multiple controllers fine; some dongles start acting like a bouncer at capacity. If you need reliable multi-controller play, the Xbox Wireless Adapter (with the right Linux driver) is often more consistent than Bluetooth.

8) When Bluetooth isn’t the best option

Option A: USB cable (the “it just works” classic)

Plug it in and you’re done. This is the fastest way to confirm the controller itself is healthy and your game detects input properly. If Bluetooth is messy, USB is your control group experiment.

Option B: Xbox Wireless Adapter (best for multiple controllers)

If your controller doesn’t support Bluetoothor you want fewer dropoutsusing the official wireless adapter can be a great upgrade. On Linux, this typically involves a dedicated driver/module (distro-specific tools and guides vary).

Option C: A better Bluetooth dongle

Not all Bluetooth adapters are created equal. A flaky dongle can make a perfect controller look broken. If everything else fails and you’re using a mystery-brand dongle from the bargain bin, consider testing with a reputable BT 4.0/5.x adapter.

9) Wrap-up checklist

Here’s the “I just want the short version” listbecause sometimes you want to play games, not roleplay as a Bluetooth archaeologist.

• Confirm Bluetooth support on your controller (faceplate clue).
• Enable Bluetooth service: sudo systemctl enable --now bluetooth
• Pair via GUI or bluetoothctl (remember trust).
• Install xpadneo for better mapping/rumble on many systems.
• If connect/disconnect loops happen, try removing the device, re-pairing, and (if needed) disabling ERTM.
• Test input with evtest or jstest-gtk.
• Configure in Steam (Steam Input on/off depending on the game).

Bluetooth gamepads on Linux can be flawlessor fussydepending on your controller revision, Bluetooth adapter, and kernel stack. The good news: once you get it stable, it tends to stay stable. The bad news: Bluetooth sometimes makes you earn it.

Real-world experiences (extra )

In real life, setting up an Xbox One controller over Bluetooth on Linux usually falls into one of three emotional journeys: “It worked instantly,” “It worked after one tweak,” or “I have now memorized my Bluetooth MAC address like it’s my childhood phone number.” Most people land in the middle category, where pairing succeeds, but the first few play sessions reveal tiny annoyancesrandom disconnects, input lag spikes, or the controller refusing to reconnect after a suspend/resume cycle.

The first common experience is the pairing mode misunderstanding. You press the Xbox button, it lights up, you assume it’s pairable, and Linux finds nothing. Then you realize the sync button has to be held until the Xbox logo blinks rapidlynot politely, but with the urgency of a microwave timer. Once you hit the right blinking pattern, the controller pops up immediately as “Xbox Wireless Controller,” and you feel briefly invincible. Enjoy that moment. Bluetooth likes to keep you humble later.

The second common story is the “connect-disconnect loop”. The controller appears, you click connect, it connects, then drops, then connects, then drops againlike it’s speed-dating your operating system. This is the point where people discover that Linux Bluetooth is a stack of components, not a single “Bluetooth thing.” Restarting the Bluetooth service helps surprisingly often, but if the loop continues, folks try removing the device and pairing again. That simple “remove and re-pair” step is more effective than it sounds because stale pairing keys (especially if you’ve paired the controller to Windows, an Xbox, or a phone recently) can make Linux act like it’s trying to handshake with a ghost.

Next comes the feel of the controller in games. When it’s good, it’s really good: smooth sticks, reliable button presses, rumble that actually rumbles, and Steam recognizing it instantly. When it’s not good, it’s usually not “broken”it’s “slightly off.” Maybe the right trigger behaves like it’s binary instead of analog, or the face buttons map strangely in one game but not another. This is where many people install a dedicated driver like xpadneo, not because Linux can’t see the controller, but because they want consistency across SDL games, Steam Input layers, and emulators. The experience often improves immediately: inputs feel cleaner, mappings become predictable, and rumble stops doing weird half-hearted buzzes like a phone on silent.

Finally, there’s the comfort phase: once the controller is stable, you stop thinking about it. That’s the goal. The controller becomes just another input device, like a keyboardexcept one you can throw onto the couch without offending your keys. People who game regularly on Linux often end up with a practical routine: keep the controller trusted, turn off scanning after pairing, avoid sketchy Bluetooth dongles, and when multiplayer night happens, consider the Xbox wireless adapter or USB cables for the “no surprises” experience. In other words: you’ll get there, and when you do, Bluetooth will quietly fade into the backgroundright where it belongs.