libretro / libretro/RetroArch

Touchscreen Controls random freeze

Open
#19,117 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

Is there an existing issue for this?
  • This is a bug in RetroArch frontend
  • I have searched the existing issues
Description

I had recently this problem with every core in Retroarch Android. When I play some games, even using customized overlays, I sometimes feel that the characters doesn't respond for some seconds to said action or direction. For example, when I'm going to right but now I want to make the character go left when I press the left button of the overlay with my finger, the characters doesn't responde by a second or two. This has been annoying me for a long time with every core I try.

Expected behavior

When playing, some of the touchscreen controls randomly don't respond during 1 second or two until they work again. This happens randomly with every core I tried even using customized overlays I got.

Steps to reproduce the bug
  1. Choose a core/game
  2. Play game
  3. Play it for some time until this happens.
Version/Commit

1.22.2

Bisect Results

No response

Present in the nightly version

I don't know

Platform & operating system

Android

Affected Cores

snes9X, Genesis Plus GX, mGba, Gearboy, Gambette, Nestopia

Environment information

Android Device:
Redmi Note 9 - MIUI Globlal 12.5.9 Stable
Android 11 RP1A.200720.011

Retroarch Android version tested: 1.22.2

Relevant log output

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 intermittent touchscreen-input freeze on Android with the listed cores and customized overlays. Compare behavior across the listed games and versions, including a nightly build if possible, and capture relevant log output; done means identifying a consistent trigger or narrowing the issue to the frontend input path.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
frontend, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.