libretro / libretro/RetroArch

Android Nightly - Input bindings cannot be reset to default

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

After changing an input binding in Settings → Input → Port 1 Controls and save, it can no longer be reset to its default value in the latest Android Nightly build. Both methods that work in the Stable release—holding the modified binding and using Reset to Default, have no effect.

I also noticed a difference in controller profile saving. The Stable build saves the profile as android/Xbox Wireless Controller.cfg, while the Nightly build saves it as Xbox Wireless Controller.cfg.

I changed the controller profile directory, deleted the saved profile, and created a new one, but RetroArch still appeared to load the profile from the other location.

Expected behavior

The input binding should be restored to its default value.

Steps to reproduce the bug
  1. Go to Settings → Input → Port 1 Controls.
  2. Change any input binding (for example, D-Pad Up).
  3. Save controller profile
  4. Try to reset the binding by pressing and holding the modified binding, or by selecting Reset to Default Controls
Version/Commit

Nightly build (Jun 27 2026, 4a0c274)

Bisect Results

69a4f0e

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system

Android 15

Affected Cores

No response

Environment information

*Nightly build (Jun 27 2026, 4a0c274)
*from the official Libretro buildbot
*Android: 15
*Controller: Xbox One Controller

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 reset failure in Settings → Input → Port 1 Controls on the Android 15 nightly build, then compare it with Stable. Use bisect result 69a4f0e and the reported controller-profile paths as the starting points for tracing profile loading and reset behavior. Done means changed bindings can be restored to their defaults and profiles load from the selected directory.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.