libretro / libretro/RetroArch

DualSense analog triggers unresponsive in Android RetroArch, PS4 controllers unaffected

Open
#16,791 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

The Sony DualSense controller's analog triggers (L2/R2) are non-functional in RetroArch for Android. This issue affects pressure-sensitive controls in games and the Remote RetroPad feature. The analog trigger values should range from -10 to +10, but no input is registered regardless of configuration attempts. This problem is specific to the DualSense and does not occur with PS4 controllers.

Expected Behavior
  • Analog triggers should provide pressure-sensitive input
  • Values should range from -10 to +10
  • Input should be recognized in Remote RetroPad
Actual Behavior
  • No input is registered from analog triggers
  • Issue persists across various configuration attempts
  • Problem affects gameplay and testing tools
Steps to Reproduce

Pre-testing:

  1. Test the L2/R2 triggers in any gamepad testing app outside of RetroArch
  2. Confirm that the analog triggers function correctly in these tests
  3. This verification establishes that the issue is specific to RetroArch and not a hardware problem

RetroArch testing:

  1. Set the autoconfig directory to: /storage/emulated/0/RetroArch/autoconfig/
  2. Generate /storage/emulated/0/RetroArch/autoconfig/android/DualSense Wireless Controller.cfg
  3. Modify DualSense Wireless Controller.cfg by changing the L2/R2 configuration from buttons to axes since RetroArch cannot do this:
input_l2_axis = "+1"
input_r2_axis = "+2"
  1. Restart RetroArch and test using "Start Remote RetroPad"
  2. Repeat with different axis values (both positive and negative)
PS4 controller (control)

This section demonstrates that Remote RetroPad is working with L2/R2 analog pressure testing in Android.

RetroArch testing.

  1. Plug a PS4-controller
  2. Test the L2/R2 triggers in any gamepad testing app. They are working.
  3. Use the provided autoconfig: https://github.com/libretro/retroarch-joypad-autoconfig/blob/f7a398e6ebd7c62aeebb932668295f76882db824/android/Wireless%20Controller.cfg
  4. Restart RetroArch and test the analog trigger using "Start Remote RetroPad"
  5. The rectangles on L2/R2 should indicate that they are working
Additional Information
  • Tested axis values from -10 to +10
  • Issue persists across RetroArch restarts
  • May be related to RetroArch's handling of mixed input types
Version Information
  • RetroArch: 1.19.1, 1.20.
  • OS: Android
Hardware

Sony DualSense Wireless Controller

Notes
  • Affects games relying on analog triggers (e.g., GameCube, Dreamcast)
  • Problem likely related to RetroArch's input handling, not specific cores
  • Manual configuration attempts have been unsuccessful

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue on Android with a Sony DualSense, first verifying L2/R2 in an external gamepad testing app. Then inspect the generated android/DualSense Wireless Controller.cfg and test the listed axis mappings through Start Remote RetroPad, comparing the result with the provided PS4 controller configuration. Done means the DualSense triggers report analog values from -10 to +10.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c
Domain
frontend, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.