libretro / libretro/RetroArch

[Android] Not possible to map touch inputs.

Open
#11,021 1 comment 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

Description

[Touch inputs don't register when trying to bind hotkeys, like Ai service button, for example. Premade hotkeys like down+select to bring up the menu work ingame though. I can map external controller inputs, select for hotkey and L1 for Ai service, but nothing happens when pressing the same buttons after with touch.]

Expected behavior

[Be able to bind touch inputs or at least have a reference list of touch input names (recognized internally by retroarch) to bind manually in the cfg.]

Actual behavior

[No input is registered (time runs out) or "mouse1" is recognized because of pressing to much, with is not useful ingame.]

Steps to reproduce the bug
  1. [Go to Settings>Input>hotkeys]
  2. [Try to bind input using any touch overlay]
Bisect Results

[Never tried before last week when testing the Ai service, but I'll assume always.]

Version/Commit

You can find this information under Information/System Information

  • RetroArch: [4c6b139]
Environment information
  • OS: [Android 8.1.0 MIUI 10.3.2]

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 at Settings>Input>hotkeys on Android and reproduce binding attempts with a touch overlay, comparing them with external controller inputs and the premade down+select hotkey. Done means touch inputs can be bound and triggered reliably, or the internally recognized touch input names are documented for manual configuration.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.