Many many thanks to Kai Krakow who sponsored me a Xbox One Wireless Controller (including Wireless Adapter) and a pack of mouthwatering guarana cacao ;D

This Driver is currently in development - basic functionality works, but there is still A LOT to do.

Advanced Linux Driver for Xbox One S Wireless Gamepad

This is a driver for the Xbox One S Wireless Gamepad which I created for a student research project at fortiss GmbH.

At the moment of development there was no driver available which supports force feedback (Rumble) - at least not for the wireless version (Bluetooth). There still is none at January 2018, but until this driver is in a bit more presentable condition I won't submit it to the linux kernel.

The buildsystem consists not only of the driver itself, it also fixes a bug I found in L2CAP (which initially forced us to disable ertm completely), futhermore it adds the new driver to the hid-core (this way it automatically loads the new driver whenever the controller is registered). As an alternative, it offers a Udev-rule to load the driver, this is a workaround which is useful whenever you are not able to recompile hid-core (e.g. if it is not a module - e.g. on Raspbian - and you don't want to recompile the whole kernel).

Advantages

• Supports Bluetooth
• Supports Force Feedback over Bluetooth
• Supports Force Feedback at the triggers (not even supported at Windows)
  • take a look here https://www.youtube.com/watch?v=G4PHupKm2OQ
• Offers a consistent mapping, even if paired to Windows before
• Working Select, Start, Mode buttons
• Support for Battery Level Indication
  • On some KDE desktops it works, on others not. We've already fixed that and are currently waiting for a merge request: https://phabricator.kde.org/D11331 UPDATE: Merged in https://www.kde.org/announcements/kde-frameworks-5.45.0.php
  • Tested in GNOME
• Agile Development

Build

You have to build the driver yourself if there is no suitable version available in out/. To make life a bit easier, we offer you a Taskfile at the moment (you will need go-task https://github.com/go-task/task to execute that).

Furthermore, you need git, build-essential (gcc), linux-headers and make - please make sure those are installed. For cross-compilation (raspberry) you also need: arm-linux-gnueabihf-gcc-stage1.

• build driver(s) for your local system

  task
  

  Alternatively, you can also run either task default or task local

• build driver(s) for raspberry pi 3 (linux-raspberrypi-kernel_1.20171029-1)

  task raspi3
  

The Taskfile downloads your current kernel, copies the driver into the extracted folder and patches hid-core and l2cap. Then it compiles the kernel modules and copies the resulting driver to your local ./out directory.

Until now the Taskfile is tested under the following Distributions

• ARCH
• Antergos
• Gentoo

Installation

If Hid and Bluetooth are modules (not built-ins), then all you have to do is:

sudo task install

If bluetooth isn't a module but builtin, you can alternatively run echo 1 | sudo tee /sys/module/bluetooth/parameters/disable_ertm before connecting the controller to the computer.

If hid isn't a module, you can alternatively copy 99-xpadneo.rules to /etc/udev/rules.d/ (run udevadmn control --reload afterwards)

Configuration

The driver can be reconfigured at runtime by accessing the following sysfs files in /sys/module/hid_xpadneo/parameters:

• dpad_to_buttons: Set to Y to map dpad directional input to button events, defaults to N

Debugging

Debug Output

If you are asked to send debug info or want to fix bugs, enable debugging first in the driver and upon request send the xpadneo related part:

echo 3 | sudo tee /sys/module/hid_xpadneo/parameters/debug_level
dmesg | grep xpadneo > ~/xpadneo_log

where 3 is the most verbose debug level. Disable debugging by setting the value back to 0.

You may want to set the debug level at load time of the driver. You can do this by applying the setting to modprobe:

echo "options hid_xpadneo debug_level=3" | sudo tee /etc/modprobe.d/xpadneo.conf

Now, the driver will be initialized with debug level 3 during modprobe.

Mapping

The Gamepad has different button mappings, thats the reason why sometimes buttons like "select" and "start" do not work. I think this is fixed now, but if you ever see any wrong mapping please let me know!

Please activate debug messages, reconnect your gamepad (turn it off and on again), press every button (A, B, X, Y, L1, R1, Start, Select, X-Box, ThumbL, ThumbR, DpadUp, DpadRight, DpadDown, DpadLeft) and axis once (X, Y, Rx, Ry, Z, Rz) and upload your xpadneo-related dmesg output.