Mapping and Navigation issues with 8BitDo Ultimate Wireless 2 w/ 2.4GHz dongle
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux, python
- Domain
- embedded-iot, frontend
Research direction
Start by tracing Batocera's controller mapping and menu-navigation handling for the Nintendo Pro Controller, using the reported sdl2-jstest and evtest behavior as evidence that the axes are detected. Compare Switch mode with the working XInput mode to locate where axis direction or repeated input is mishandled. Done means mapping records the correct left-stick directions and both up and down navigate reliably, without disrupting gyro support in Eden.
Written by the indexing model from the issue text.
Description
Batocera build version
43acu.1 2026/05/29 04:36
Your architecture
X86_64
Your Graphic Processor Unit(s) (GPU)
NVIDIA 1650 Super
Issue description
When the 8BitDo Ultimate Wireless 2 is started in Switch mode so I can use the motion/gyro in Eden, mapping and navigation don't work properly.
In mapping, it will consistently map the left analog left to "Axis 0+" instead of "Axis 0-", this reverses the left/right on some emulators.
For navigation, the d-pad works perfectly, up on the left analog stick works, but down on the left analog stick does not work. In menus nothing happens, on the Home Screen pressing down can cause the screen to start navigating without any further presses.
The gyro/motion works perfectly in Eden.
In sdl2-jstest everything looks great, upper left is -32768, lower right is 32767, the left analog settles back at (258, -259) with no pressure.
Likewise everything looks great in evtest on the controller without IMU.
If I reconfigure the gamepad in XInput mode, everything works perfectly, but I don't get any gyro/motion.
My goal is to be able to use the switch mode on these controllers so I can use the gyro/motion in the switch games, and not have to reconfigure back and forth.
Is there anything I can configure to fix this?
Detailed reproduction steps
- Connect 2.4GHz dongle to PC, make sure the gamepad switch is in 2.4GHz mode
- Turn on the gamepad holding the home+Y, feel the vibration confirming it's in switch mode
- Toast at the top confirms "Nintendo Co., LTD. Pro Controller" was connected
- With d-pad, navigate to the controller mapping
- Go through keypads, everything "works" except for "Left analog left" which will only ever map to "Axis 0+"
- Save and exit
- Pressing "Up" on the left analog stick works, pressing "Down" does not, or causes the Home Screen to start rapidly cycling on it's own
- Navigate to Switch with d-pad
- Eden works will full motion control
Details of any attempts to fix this yourself
Not sure where to start. Most instructions I've seen are for when Eden doesn't recognize the motion/gyro. Eden works, it's the main UI that doesn't.
Details of any modifications you have made to Batocera.
None.
Logs and data
8BitDo Ultimate Wireless 2 firmware is V1.10
From evtest showing a press to the upper left, then to the lower right
Testing ... (interrupt to exit)
Event: time 1790265697.046295, type 3 (EV_ABS), code 1 (ABS_Y), value -1564
Event: time 1790265697.046295, -------------- SYN_REPORT ------------
Event: time 1790265697.064346, type 3 (EV_ABS), code 0 (ABS_X), value -1257
Event: time 1790265697.064346, type 3 (EV_ABS), code 1 (ABS_Y), value -12400
Event: time 1790265697.064346, -------------- SYN_REPORT ------------
Event: time 1790265697.078377, type 3 (EV_ABS), code 0 (ABS_X), value -9820
Event: time 1790265697.078377, type 3 (EV_ABS), code 1 (ABS_Y), value -32767
Event: time 1790265697.078377, -------------- SYN_REPORT ------------
Event: time 1790265697.096323, type 3 (EV_ABS), code 0 (ABS_X), value -16270
Event: time 1790265697.096323, -------------- SYN_REPORT ------------
Event: time 1790265697.110276, type 3 (EV_ABS), code 0 (ABS_X), value -13077
Event: time 1790265697.110276, -------------- SYN_REPORT ------------
Event: time 1790265697.128333, type 3 (EV_ABS), code 0 (ABS_X), value -12932
Event: time 1790265697.128333, -------------- SYN_REPORT ------------
Event: time 1790265697.142240, type 3 (EV_ABS), code 0 (ABS_X), value -12895
Event: time 1790265697.142240, -------------- SYN_REPORT ------------
Event: time 1790265697.192298, type 3 (EV_ABS), code 0 (ABS_X), value -12940
Event: time 1790265697.192298, -------------- SYN_REPORT ------------
Event: time 1790265697.206323, type 3 (EV_ABS), code 0 (ABS_X), value -16560
Event: time 1790265697.206323, -------------- SYN_REPORT ------------
Event: time 1790265697.224421, type 3 (EV_ABS), code 0 (ABS_X), value -26977
Event: time 1790265697.224421, -------------- SYN_REPORT ------------
Event: time 1790265697.238376, type 3 (EV_ABS), code 0 (ABS_X), value -29832
Event: time 1790265697.238376, -------------- SYN_REPORT ------------
Event: time 1790265697.256269, type 3 (EV_ABS), code 0 (ABS_X), value 8643
Event: time 1790265697.256269, type 3 (EV_ABS), code 1 (ABS_Y), value 6401
Event: time 1790265697.256269, -------------- SYN_REPORT ------------
Event: time 1790265697.270400, type 3 (EV_ABS), code 0 (ABS_X), value 258
Event: time 1790265697.270400, type 3 (EV_ABS), code 1 (ABS_Y), value -258
Event: time 1790265697.270400, -------------- SYN_REPORT ------------
Event: time 1790265699.207333, type 3 (EV_ABS), code 0 (ABS_X), value 499
Event: time 1790265699.207333, type 3 (EV_ABS), code 1 (ABS_Y), value 387
Event: time 1790265699.207333, -------------- SYN_REPORT ------------
Event: time 1790265699.225379, type 3 (EV_ABS), code 0 (ABS_X), value 3208
Event: time 1790265699.225379, type 3 (EV_ABS), code 1 (ABS_Y), value 3870
Event: time 1790265699.225379, -------------- SYN_REPORT ------------
Event: time 1790265699.239195, type 3 (EV_ABS), code 0 (ABS_X), value 9304
Event: time 1790265699.239195, type 3 (EV_ABS), code 1 (ABS_Y), value 11965
Event: time 1790265699.239195, -------------- SYN_REPORT ------------
Event: time 1790265699.257209, type 3 (EV_ABS), code 0 (ABS_X), value 18399
Event: time 1790265699.257209, type 3 (EV_ABS), code 1 (ABS_Y), value 25478
Event: time 1790265699.257209, -------------- SYN_REPORT ------------
Event: time 1790265699.271279, type 3 (EV_ABS), code 0 (ABS_X), value 30702
Event: time 1790265699.271279, type 3 (EV_ABS), code 1 (ABS_Y), value 32767
Event: time 1790265699.271279, -------------- SYN_REPORT ------------
Event: time 1790265699.289198, type 3 (EV_ABS), code 0 (ABS_X), value 32541
Event: time 1790265699.289198, -------------- SYN_REPORT ------------
Event: time 1790265699.321264, type 3 (EV_ABS), code 0 (ABS_X), value 32585
Event: time 1790265699.321264, -------------- SYN_REPORT ------------
Event: time 1790265699.335218, type 3 (EV_ABS), code 0 (ABS_X), value 32630
Event: time 1790265699.335218, -------------- SYN_REPORT ------------
Event: time 1790265699.354245, type 3 (EV_ABS), code 0 (ABS_X), value 32664
Event: time 1790265699.354245, -------------- SYN_REPORT ------------
Event: time 1790265699.450343, type 3 (EV_ABS), code 0 (ABS_X), value 16738
Event: time 1790265699.450343, type 3 (EV_ABS), code 1 (ABS_Y), value 15238
Event: time 1790265699.450343, -------------- SYN_REPORT ------------
Event: time 1790265699.464351, type 3 (EV_ABS), code 0 (ABS_X), value 258
Event: time 1790265699.464351, type 3 (EV_ABS), code 1 (ABS_Y), value -258
Event: time 1790265699.464351, -------------- SYN_REPORT ------------
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 748
- Avg merge
- 9h 51m
- Merged PRs (30d)
- 170
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from batocera-linux/batocera.linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
batocera-linux/batocera.linux#17423 ·
Maintainers usually reply within 1 day
-
Bump `ledspicer` to v0.7.8 - Corrects Bug with newer Ultimarc IPAC Ultimate boards w/ newer firmwareOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
batocera-linux/batocera.linux#17329 · 1 reaction ·
Maintainers usually reply within 1 day
-
evmapy dies at startup if an input device disappears during its device scan -> game runs with no hotkeys (Select+Start exit etc.)Possibly taken @jonathanroehm claimed this 30 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
batocera-linux/batocera.linux#17210 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
batocera-linux/batocera.linux#16092 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
batocera-linux/batocera.linux#17422 ·
Maintainers usually reply within 1 day
All issues in batocera-linux/batocera.linux
Similar issues
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FAIRmat-NFDI/sand#239 ·
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coco-research/coco#539 ·
Maintainers usually reply within 1 day
-
dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
JustBeanie/hass-volcano-hybrid#34 ·
Maintainers usually reply within 1 day