android: Merge Sony DualShock 4 v1 and v2 to Wireless Controller.cfg
#1276
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…roller.cfg * Merge Sony_DualShock_4_Controller.cfg (v1) and v2 by using alternative vid/pid: libretro/RetroArch#16990 * The merged autoconfigs makes the Sony DualShock 4 Controller v1 use correct mappings - Sony_DualShock_4_Controller.cfg file used `input_menu_toggle_btn = "109"` which is now set to `input_menu_toggle_btn = "110"` in `Wireless Controller.cfg`: Changes the menu button from the Touchpad (does not work at all) to the PS button. - Sony_DualShock_4_Controller.cfg file used `input_select_btn = "4"` which is now set to `input_select_btn = "109"` in `Wireless Controller.cfg` * Renamed the controller to the official name generated by RetroArch. * Added " Trigger" to the labels for the triggers.
Merged `Sony_DualShock_4_Controller.cfg` to `Wireless Controller.cfg`; Merged Sony_DualShock_4_Controller.cfg (v1) and v2 by using alternative vid/pid: libretro/RetroArch#16990 See commit * d6b8ed1
davidhedlund
changed the title
Sony_DualShock_4_Controller_v2.cfg to Wireless Controller.cfgWireless Controller.cfg
RobLoach
reviewed
Nov 13, 2025
Comment on lines
-4
to
-5
| input_vendor_id = "1356" | ||
| input_product_id = "1476" |
Member
There was a problem hiding this comment.
We lose this vendor/product id pair by doing this. Would it be worth just having the files be the same, but with the diff product_id?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Wireless Controller.cfg, generated for Sony DualShock 4 v2 by RetroArch.input_menu_toggle_btn = "109"which is now set toinput_menu_toggle_btn = "110"inWireless Controller.cfg: Changes the menu button from the Touchpad (does not work at all) to the PS button.input_select_btn = "4"which is now set toinput_select_btn = "109"inWireless Controller.cfgCompatibility
Reviewing
This PR (#1276) is stable. It is a duplicate of my old PR that has already been reviewed.
Sony_DualShock_4_Controller_v2.cfgtoWireless Controller.cfg#1171Sony_DualShock_4_Controller_v2.cfgtoWireless Controller.cfg#1171 (comment)#1171 had merge conflicts that no one could help me solve. So I merged it to this PR (#1276) after I asked hizzlekizzle for help and he told me "I would recommend copying those files somewhere else temporarily, close your PRs, resync your repo by discarding your commits (via github web interface), delete your local copy of the repo, re-clone your now-synced repo, re-apply your changed files, make a new commit, submit a new PR". I followed his instructions, so let's hope that it working this time!
Check issue: Travis CI through GitHub services integration
My fresh fork of retroarch-joypad-autoconfig was made today (2025-11-12). But this PR (#1276) still get:
I was informed by the GitHub community that the Travis check is stuck because Travis CI is no longer active or linked to the repository. There is nothing wrong with the pull request; the repository maintainers need to remove or replace the Travis check in the branch protection settings. Once that is done, your pull request will show all checks as complete.
I encountered this check issue with at least one pull request in my previous fork of the repository as early as July 2025. Therefore, the issue definitely exists in the main repository.