{"id":13589986,"url":"https://github.com/atar-axis/xpadneo","last_synced_at":"2026-04-09T13:15:57.902Z","repository":{"id":37445318,"uuid":"119148271","full_name":"atar-axis/xpadneo","owner":"atar-axis","description":"Advanced Linux Driver for Xbox One Wireless Controller (shipped with Xbox One S)","archived":false,"fork":false,"pushed_at":"2025-04-10T12:05:03.000Z","size":21299,"stargazers_count":2207,"open_issues_count":59,"forks_count":121,"subscribers_count":24,"default_branch":"master","last_synced_at":"2025-05-06T07:29:51.227Z","etag":null,"topics":["dkms","dkms-packages","gamepad","hid","linux-driver","linux-drivers","xbox","xbox-controller","xbox-one","xpad","xpadneo"],"latest_commit_sha":null,"homepage":"https://atar-axis.github.io/xpadneo/","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/atar-axis.png","metadata":{"files":{"readme":"docs/README.md","changelog":"NEWS.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2018-01-27T08:49:26.000Z","updated_at":"2025-05-05T11:31:21.000Z","dependencies_parsed_at":"2024-01-31T07:02:09.914Z","dependency_job_id":"beabc45c-8e3e-444c-97c9-755d75ddff4e","html_url":"https://github.com/atar-axis/xpadneo","commit_stats":{"total_commits":722,"total_committers":40,"mean_commits":18.05,"dds":0.5373961218836565,"last_synced_commit":"70ef8ee276354eb82bd1de224fcc9c0f8a6390c9"},"previous_names":[],"tags_count":22,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/atar-axis%2Fxpadneo","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/atar-axis%2Fxpadneo/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/atar-axis%2Fxpadneo/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/atar-axis%2Fxpadneo/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/atar-axis","download_url":"https://codeload.github.com/atar-axis/xpadneo/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254070107,"owners_count":22009559,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["dkms","dkms-packages","gamepad","hid","linux-driver","linux-drivers","xbox","xbox-controller","xbox-one","xpad","xpadneo"],"created_at":"2024-08-01T16:00:37.282Z","updated_at":"2026-04-09T13:15:57.895Z","avatar_url":"https://github.com/atar-axis.png","language":"C","funding_links":["https://ko-fi.com/O4O43SURE"],"categories":["C"],"sub_categories":[],"readme":"\u003c!-- SPDX-License-Identifier: GPL-3.0-or-later --\u003e\n\n[![ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/O4O43SURE)\n\nIf you want to support me or accelerate the development of a special feature, consider a small donation :heart:\nJust leave a message if your donation is for a specific use (like a new hardware or a specific function).\n\n[![Build Status](https://dev.azure.com/dollingerflorian/dollingerflorian/_apis/build/status/atar-axis.xpadneo?branchName=master)](https://dev.azure.com/dollingerflorian/dollingerflorian/_build/latest?definitionId=1?branchName=master)\n[![Average time to resolve an issue](http://isitmaintained.com/badge/resolution/atar-axis/xpadneo.svg)](http://isitmaintained.com/project/atar-axis/xpadneo \"Average time to resolve an issue\")\n[![Packaging status](https://repology.org/badge/tiny-repos/xpadneo.svg)](https://repology.org/project/xpadneo/versions)\n[![Discord](https://img.shields.io/discord/733964971842732042)](https://discord.gg/nCqfKa84KA)\n\n\n# Advanced Linux Driver for Xbox One Wireless Gamepad\n\n![xpadneo Logo](img/xpadneo.png)\n\nQuote from [@atar-axis (Florian Dollinger)](https://github.com/atar-axis), creator of the initial driver:\n\n\u003e This is the first driver for the Xbox One Wireless Gamepad (which is shipped with the Xbox One S). I wrote it for a\n\u003e student project at fortiss GmbH and it is fully functional but does only support the connection via Bluetooth as\n\u003e yet - more will follow.\n\u003e\n\u003e Many thanks to *Kai Krakow* who **sponsored** me a Xbox One Wireless Controller :video_game: (including Wireless\n\u003e Adapter) and a pack of mouthwatering guarana cacao :coffee:\n\n\n## Other Projects\n\n- [xone](https://github.com/dlundqvist/xone) is a driver aiming for fully supporting all Microsoft GIP devices thus\n  replacing the xpad driver in the kernel. It supports Xbox One and Xbox Series X|S accessories.\n- [xow](https://github.com/medusalix/xow) is an unmaintained driver for the Xbox One S controllers, which has been\n  superseded by xone. Kudos to [@medusalix](https://github.com/medusalix) for working together on finding some\n  work-arounds for controller firmware bugs.\n- [xpad](https://github.com/paroj/xpad) supports this and many other controllers in USB mode.\n- [MissionControl](https://github.com/ndeadly/MissionControl) aims to support the controller on Nintendo Switch via\n  Bluetooth.\n\nThese other projects may not support some of the advanced features of xpadneo.\n\n\n## Heads Up Package Maintainers\n\nLicensing of the project has changed, so please update your packaging if you maintain a package for this driver.\nPlease refer to [LICENSE.md](../LICENSE.md) for details. If you have any questions, please ask.\n\nThe project introduced some packaging helpers and changed the installation process. Please see\n[Packaging](https://atar-axis.github.io/xpadneo/#packaging).\n\nVersion v0.11 dropped the dependency on `CONFIG_INPUT_FF_MEMLESS` and uses a more precise method to run rumble effects,\neliminating aliasing effects due to different frequencies of games (60 fps and above) and `ff-memless` (20 hz). Our\nnew method allows frequencies up to 100 hz which is the limit of the controller's hardware.\n\n\n## Breaking Changes\n\n### Kernel 4.18 or newer required\n\nAs of xpadneo v0.10, we require kernel 4.18 or later to utilize `HID_QUIRK_INPUT_PER_APP` which splits the gamepad into\nmultiple sub-devices to fix problems and incompatibilities at several layers.\n\n\n### Paddle Button Codes Changed\n\nTo stay compatible with SDL and current kernel development, the button codes for the grip paddles of XBE2 controllers\nhave been moved to the official kernel standards as of kernel 6.17. We will also reflect this change for older kernel\nversions so user-space can rely on a consistent mapping. If you remapped those buttons with third-party software, you\nwill need to redo those mappings.\n\n\n### SDL2 2.28 Compatibility\n\nThanks to [@slouken](https://github.com/slouken) from SDL2, xpadneo mappings are now auto-detected in the upcoming\nSDL2 2.28 release. This will fix long-standing problems with Steam Input and SDL2 games. With this release, we will\nalso have full paddle support.\n\nIf you still see problems, ensure that you didn't create custom controllerdb entries. See also:\n- https://github.com/atar-axis/xpadneo/issues/428\n- https://github.com/libsdl-org/SDL/commit/9567989eb3ce9c858f0fe76806c5ccad69da89ba\n- https://github.com/libsdl-org/SDL/commit/0f4b15e16b7f07a46db6dc8e651f8c1849d658c5\n\nKnown issues:\n- The Share button will currently not be recognized by SDL2, scheduled to be fixed in xpadneo v0.11\n- If SDL2 uses hidraw, mappings will be wrong, export `SDL_JOYSTICK_HIDAPI=0` in your profile or find which software\n  enabled hidraw device access to all drivers\n\n\n### Quirks by Design\n\nWith BLE firmware, all models switched to a unified HID report descriptor, only the XBE2 controller identifies with\nPID 0x0B22 while the other models identify with PID 0x0B13. This has some known consequences:\n\n- All non-XBE2 controllers will claim to have a Share button no matter if it physically exists. As HID doesn't report\n  the internal model number, xpadneo cannot fix it currently. The button is currently mapped to F12, so this has no\n  consequences.\n- All XBE2 controllers will claim to have a full keyboard and the Share button is actually the Profile button. Since\n  Share is currently mapped to F12, this will have no consequences.\n\n\n## Advantages of this Driver\n\n- Supports Bluetooth\n- Supports direct rumble effects avoiding aliasing effects by not using `ff-memless` (streaming mode only)\n- Supports [Trigger Force Feedback](https://www.youtube.com/watch?v=G4PHupKm2OQ) in every game by applying a\n  pressure-dependent effect intensity to the current rumble effect (not even supported in Windows)\n- Supports adjusting rumble intensity including disabling rumble\n- Offers a consistent mapping, even if the Gamepad was paired to Windows/Xbox before, and independent of software\n  layers (SDL2, Stadia via Chrome Gamepad API, etc)\n- Working paddles (buttons on the backside of the controller)\n- Correct axis range (signed, important for e.g. RPCS3)\n- Supports battery level indication (including the Play 'n Charge Kit)\n  ![Battery Level Indication](./img/battery_support.png)\n- Easy installation\n- Exposes the currently selected profile to user-space (Xbox Elite 2 controllers, or emulated)\n- Supports customization through profiles (work in progress)\n- Supports grip paddles (as shipped with the Xbox Elite 2 controller)\n- Optional high-precision mode for Wine/Proton users (disables dead zones so games don't apply an additional one)\n- Share button support on supported controllers\n- Works as a mouse if you are in couch-mode (press \u003ckey\u003eGuide\u003c/key\u003e+\u003ckey\u003eSelect\u003c/key\u003e)\n\n\n## Unavailable Features\n\nAcross all models, xpadneo won't support audio features of the controllers because the firmware doesn't support audio\nin Bluetooth mode. In the future, xpadneo may support audio when USB and dongle support will be added.\n\nThere are two modes for rumble: Streaming and non-streaming. Streaming means, a game will send one rumble command per\nframe. Non-streaming means, effects are sent in advance, planned into the future, and can potentially play at the same\ntime. This is mostly useful for force feedback effects, which Xbox controllers cannot replicate, they only support\nhaptic feedback. Thus, non-streaming rumble programming is not supported, and we found no game that uses it. We will\nstill detect it and log that incident to dmesg once, so users can report if they found a game that uses it.\n\n\n### Xbox One S Wireless Controller\n\nThis is the initial controller supported from the first version of xpadneo. All features are fully supported. This\ncontroller uses emulated profile switching support (see below).\n\n\n### Xbox Elite Series 2 Wireless Controller\n\nBasic support for the Xbox Elite Series 2 Wireless controller is present, covering all the features of the driver.\nThe following features are missing:\n\n- Upload of profile mappings and sensitivity curves is currently not supported.\n\nThis controller uses native profile switching support (see below).\n\n\n### Xbox Series X|S Wireless Controller\n\nFull support for the Xbox Series X|S controller is present including the share button. This is currently statically\nmapped to keyboard event `KEY_F12` to take screenshots with Steam. It will be configurable in the future. This\ncontroller uses emulated profile switching support (see below).\n\nThis controller uses BLE (Bluetooth low energy) and can only be supported if your Bluetooth dongle also supports BLE.\n\n**Known problems:** The controller may not properly set its connection parameters, resulting in laggy and choppy\ninput experience. See also: [Troubleshooting](https://atar-axis.github.io/xpadneo/#troubleshooting).\n\n\n### 8BitDo Controllers\n\nThis driver supports the Nintendo layout of those controllers to exposes them correctly as button A, B, X, and Y\nas labelled on the device. This is swapped compared to the original Xbox controller layout. However, this feature is\nnot enabled by default. If you want to use this feature, you have to add a quirk flag to the module options:\n\n```\n# /etc/modprobe.d/99-xpadneo-quirks.conf\noptions hid_xpadneo quirks=E4:17:D8:xx:xx:xx+32\n```\n\nwhere you replace `xx:xx:xx` with the values from your controller MAC (as shown in `dmesg`). The value `32` enables\nNintendo layout. If you'll want to add other quirk flags, simply add the values,\ne.g. `32` + `7` (default quirks for 8BitDo) = `39`. After changing this, reload the driver or reboot.\n\nThis controller uses emulated profile switching support (see below).\n\n**Breaking change:** Users of previous versions of the driver may want to remove their custom SDL mappings. Full\nsupport has been added for these controllers and broken mapping of previously versions no longer needs to be\napplied. See also: [SDL](https://atar-axis.github.io/xpadneo/#troubleshooting#sdl).\n\n\n### GuliKit KingKong Controller Family\n\nThis driver supports the GuliKit King Kong controller family, the driver was tested with model NS09 (using firmware\nv2.0) and NS39 (aka KK3 MAX, firmware v3.6) but should work just fine for the older models, too. If in doubt, follow\nthe firmware upgrade guides on the GuliKit home page to receive the latest firmware. Both the Android mode and the\nX-Input mode are supported but it may depend on your Bluetooth stack which mode works better for you (Android mode\ndidn't pair for me).\n\nThis driver supports the Nintendo layout of those controllers to exposes them correctly as button A, B, X, and Y\nas labelled on the device. This is swapped compared to the original Xbox controller layout. However, this feature is\nnot enabled by default. If you want to use this feature, you have to add a quirk flag to the module options:\n\n```\n# /etc/modprobe.d/99-xpadneo-quirks.conf\noptions hid_xpadneo quirks=98:B6:EA:xx:xx:xx+32\n```\n\nwhere you replace `xx:xx:xx` with the values from your controller MAC (as shown in `dmesg`). The value `32` enables\nNintendo layout. If you'll want to add other quirk flags, simply add the values,\ne.g. `32` + `131` (default quirks for GuliKit) = `163`. After changing this, reload the driver or reboot.\n\nHowever, alternatively the controller supports swapping the buttons on the fly, too: Just press and hold the settings\nbutton, the click the plus button. Thus, the quirks flag is just a matter of setting the defaults.\n\nThis controller uses emulated profile switching support (see below).\n\n\n### GameSir T4 Cyclone Family\n\nThis driver supports the GameSir T4 Cyclone controller family, tested by the community. The Pro-models also support\ntrigger rumble but since we cannot distinguish both models by the Bluetooth MAC OUI, we simply enable the trigger\nrumble protocol for both variants. This should not introduce any problems but if it does, and your model does not have\ntrigger rumble support, you can explicitly tell the driver to not use the trigger rumble motors by adding a quirk flag:\n\n```\n# /etc/modprobe.d/99-xpadneo-quirks.conf\noptions hid_xpadneo quirks=A0:5A:5D:xx:xx:xx+2\n```\n\nThis controller uses emulated profile switching support (see below).\n\n\n### GameSir T4 Nova Lite Family\n\nThis driver supports the GameSir T4 Nova Lite controller family, tested by the community. These models have a quirk of\nonly allowing rumble when all motor-enable bits are set and does not have trigger rumble motors. It looks like these\nmodels are available with different MAC OUIs, so your particular controller may not be automatically detected. In this\ncase, manually add the quirk flags for your controller:\n\n```\n# /etc/modprobe.d/99-xpadneo-quirks.conf\noptions hid_xpadneo quirks=3E:42:6C:xx:xx:xx+6\n```\n\nThis controller uses emulated profile switching support (see below).\n\nThis manufacturer uses random MAC addresses, so we cannot rely on known OUIs. Heuristics try to detect this controller.\n\n\n### A Note About GameSir Devices\n\nGameSir devices do not use officially registered MAC OUIs on the Bluetooth radio part, and they come with various\nflaky firmware behavior and bugs, while mimicking all other identifiable feature of genuine Microsoft controllers\nperfectly. This makes such devices hard to detect to work around the bugs in the rumble implementation but we will\nneed a correct implementation in a future version of xpadneo. This means that xpadneo will probably drop official\nsupport for GameSir devices in the future: Base functionality should work out of the box but advanced future rumble\nfeatures may show erratic behavior. There's nothing we can do about that and you should instead complain at the\nmanufacturer: either properly implement the full rumble protocol, or just stick to officially registered OUIs.\n\nIf you've come here because your kernel logged `enabling heuristic GameSir Nova quirks` but you don't have a GameSir\ndevice, try the following module option and report the incident on our issue tracker:\n\n```\n# /etc/modprobe.d/99-xpadneo-quirks.conf\noptions hid_xpadneo quirks=78:86:2E:xx:xx:xx+512\n```\n\n\n\n## Profile Switching\n\nThe driver supports switching between different profiles, either through emulation or by using the hardware\nswitch that comes with some models. This switching can be done at any time even while in a game. The API for\ncustomizing each profile does not exist yet.\n\nThe currently selected profile is exposed to user-space as an additional axis `ABS_PROFILE` (supported since kernel\n6.0-rc1) with 4 positions, indicating which profile has currently been selected. For user-space to make full use of\nthis knowledge, one would need to remap the paddles to distinctive, unique buttons in each profile. Otherwise you are\nlimited to the generic gamepad buttons. Thus, the \"profile axis\" can be used as a shift operator in software that\nsupports it.\n\n\n### Native Profile Switching Support\n\nThe driver support native profile switching for the Xbox Elite Series 2 controller. However, the feature is not\nfinalized yet:\n\n- The default profile (no LED) exposes the paddles as extra buttons.\n- The other three profiles behave the same way by default. While there is no support for modifying them currently,\n  configurations set in the [Xbox Accessories app (Windows only)](https://apps.microsoft.com/store/detail/xbox-accessories/9NBLGGH30XJ3)\n  will carry over and operate as intended.\n\n\n### Emulated Profile Switching Support\n\nThe driver emulates profile switching for controllers without a hardware profile switch by pressing buttons A, B, X,\nor Y while holding down the Xbox logo button. However, the following caveats apply:\n\n- Profiles currently behave all the same, and there is no support for configuring them.\n- Full support will be available once the Xbox Elite Series 2 controller is fully supported.\n- If you hold the button for too long, the controller will turn off - we cannot prevent that.\n\n**Important:** Emulated profile switching won't work if you disabled the shift-mode of the Xbox logo button (module\nparameter `disable_shift_mode`).\n\n\n### Mouse Profile Support\n\nThe driver can switch to emulating a mouse (and limited keyboard) on all supported controllers. Press\n\u003ckey\u003eGuide\u003c/key\u003e+\u003ckey\u003eSelect\u003c/key\u003e to switch to mouse mode or back to controller mode:\n\n- Left stick moves the mouse pointer\n- Right stick can be used as a scrolling wheel/ball\n- Triggers for left and right mouse button\n- Shoulder buttons for back and forward button\n- D-pad for cursor movement\n- Menu to show on-screen keyboard (untested, we send `KEY_ONSCREEN_KEYBOARD` on the consumer device)\n- A for \u003ckey\u003eEnter\u003c/key\u003e\n- B for \u003ckey\u003eEscape\u003c/key\u003e\n\n**Important:** The mouse profile won't work if you disabled the shift-mode of the Xbox logo button (module parameter\n`disable_shift_mode`). If you set the new `disable_mouse` module parameter to `1`, xpadneo will no longer register a\nmouse device at all, so the Guide button combo will simply pass through to the desktop and no mouse emulation will be\nstarted.\n\n\n## Getting Started\n\n### Distribution Packages\n\nIf your distribution has a maintained package, you can just use that and do not need to follow the manual install\ninstructions below:\n\n[![Packaging status](https://repology.org/badge/vertical-allrepos/xpadneo.svg)](https://repology.org/project/xpadneo/versions)\n\n\n### Notes for Package Maintainers\n\nTo properly support module signing and UEFI secure boot, `openssl` and `mokutil` are required additionally to the\nprerequisites below. The [DKMS readme](https://github.com/dell/dkms/blob/master/README.md) has more instructions.\n\n\n### Prerequisites\n\nMake sure you have installed *dkms*, *linux headers* and a bluetooth implementation (e.g. *bluez*) and their\ndependencies.\n\nKernel maintainers should also include the `uhid` module (`CONFIG_UHID`) because otherwise Bluetooth LE devices (all\nmodels with firmware 5.x or higher) cannot create the HID input device which is handled in user-space by the bluez\ndaemon.\n\n- On **Arch** and Arch-based distributions (like **EndeavourOS**), try\n  `sudo pacman -S dkms linux-headers bluez bluez-utils`\n- On **Debian** based systems (like Ubuntu) you can install those packages by running\n  `sudo apt-get install dkms linux-headers-$(uname -r)`\n- On **Fedora**, it is\n  `sudo dnf install dkms make bluez bluez-tools kernel-devel-$(uname -r) kernel-headers`\n- On **Manjaro** try\n  `sudo pacman -S dkms linux-latest-headers bluez bluez-utils`\n- On **openSUSE** (tested on Tumbleweed, should work for Leap), it is\n  `sudo zypper install dkms make bluez kernel-devel kernel-source`\n- On **OSMC** you will have to run the following commands\n  `sudo apt-get install dkms rbp2-headers-$(uname -r)`\n  `sudo ln -s \"/usr/src/rbp2-headers-$(uname -r)\" \"/lib/modules/$(uname -r)/build\"` (as a [workaround](https://github.com/osmc/osmc/issues/471))\n- On **Raspbian**, it is\n  `sudo apt-get install dkms raspberrypi-kernel-headers`\n  If you recently updated your firmware using `rpi-update` the above package may not yet include the header files for\n  your kernel. Please follow the steps described [here](https://github.com/notro/rpi-source/wiki) in this case.\n- On **generic distributions**, it doesn't need DKMS but requires a configured kernel source tree, then:\n  `cd hid-xpadneo \u0026\u0026 make modules \u0026\u0026 sudo make modules_install`\n- **Module singing and UEFI secure boot:** If installing yourself, you may need to follow the instructions above for\n  package maintainers.\n\nPlease feel free to add other distributions as well!\n\n\n### Installation\n\n- Download the Repository to your local machine\n  `git clone https://github.com/atar-axis/xpadneo.git`\n- `cd xpadneo`\n- If using DKMS, run `sudo ./install.sh`\n- If not using DKMS, follow steps above (generic distribution)\n- Done!\n\n\n### Connection\n\n- `sudo bluetoothctl`\n- `[bluetooth]# scan on`\n- wait until all available devices are listed (otherwise it may be hard to identify which one is the gamepad)\n- push the connect button on upper side of the gamepad, and hold it down until the light starts flashing fast\n- wait for the gamepad to show up in bluetoothctl, remember the \u003cMAC\u003e address (e.g. `C8:3F:26:XX:XX:XX`)\n- `[bluetooth]# scan off` to stop scanning as it may interfere with properly pairing the controller\n- `[bluetooth]# pair \u003cMAC\u003e`\n- `[bluetooth]# trust \u003cMAC\u003e`\n- `[bluetooth]# connect \u003cMAC\u003e` (should usually not be needed but there are [open bugs](https://github.com/atar-axis/xpadneo/issues/198))\n- The `\u003cMAC\u003e` parameter is optional if the command line already shows the controller name\n\nYou know that everything works fine when you feel the gamepad rumble ;)\n\nIf it doesn't, please check our documentation in [Troubleshooting](https://atar-axis.github.io/xpadneo/#troubleshooting).\n\n\n### Configuration\n\n- If using DKMS: Use `sudo ./configure.sh` to configure the driver as you wish. The script will guide you through the\n  available options.\n\n\n### Update\n\nIn order to update xpadneo, do the following\n\n- Update your cloned repo: `git pull`\n- If using DKMS: Run `sudo ./update.sh`\n- otherwise follow the steps above (generic distribution)\n\n\n### Uninstallation\n\n- If using DKMS: Run `sudo ./uninstall.sh` to remove all installed versions of hid-xpadneo\n- otherwise follow the steps above (generic distribution)\n\n\n## Further Information\n\nFor further information please visit the GitHub Page \u003chttps://atar-axis.github.io/xpadneo/\u003e which is generated\nautomatically from the content of the `/docs` folder.\n\nYou will find there e.g. the following sections\n\n- [Troubleshooting](https://atar-axis.github.io/xpadneo/#troubleshooting)\n- [Debugging](https://atar-axis.github.io/xpadneo/#debugging)\n- [Compatible BT Dongles](https://atar-axis.github.io/xpadneo/#bt-dongles)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fatar-axis%2Fxpadneo","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fatar-axis%2Fxpadneo","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fatar-axis%2Fxpadneo/lists"}