libretro / libretro/RetroArch

Only D-Pad won't map Android

Open
#15,487 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

I've been using my Ipega 9087s for over a year without issue with Retroarch. All of a sudden when starting after a month of not using it with Retroarch, when pressing any button that is not the d pad, it assigns correctly my ipega 9087s correctly to port 1. The moment I touch the dpad, it says Virtual configured on port 2. When playing any game, all buttons work, regardless of core in use except the dpad. Even when I disable the port in 2. Nothing works.

When I try to map the controls manually, I see the config as per attachment.
Screenshot_2023-07-17-15-30-40-80_a845f06d2c9842610668be6995f9e34f

It doesn't allow me to map the dpad. It doesn't even recognise an input.

Initially, I though the dpad was just broken, however, this is not the case. In AetherSX2, which is a superb PS2 emulator for android for those reading that are interested, no shade on Retroarch, the d pad and remapping of the dpad works no issues whatsoever. Therefore it would seem to be isolated to Retroarch.

Please help peeps. I don't want to have to use another emulator to PS1 and older.

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

Start by reproducing the issue in RetroArch on Android with the Ipega 9087s, focusing on automatic and manual D-pad mapping and the port assignment behavior described. Done means the D-pad is recognized and mappable, works in games on port 1, and does not incorrectly configure a virtual port 2.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.