[Feature Request] <MOVE THE ANDROID DEFAULT CFG>

Open
#19,932 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, c
Domain
mobile

Research direction

Start by tracing how RetroArch selects and persists its default configuration on Android, focusing on the config-directory setting and the Android/data/com.retroarch/files/retroarch.cfg path named in the report. Check where the Android default config is loaded and why changing the main config path does not persist across restarts. Done means the default config can be stored in a writable folder and existing config files can be used across app restarts.

Written by the indexing model from the issue text.

Description

feature request

It's possible I've missed something, but from what I can tell the default config is stored at Android/data/com.retroarch/files/retroarch.cfg and it is not possible to copy an existing cfg file into that directory on mobile. This means that existing cfg files can't be used unless loaded in .. but that doesn't persist an app restart. For whatever reason, setting the main cfg file to something besides the default cfg in the read-only Android/data folder simply doesn't persist.

The resulting experience is that without a separate device to manipulate the Android/data folder, I'm left redoing all my cfg tweaks on the default file just so it persists. Can we please move this file to a writeable folder?

I even attempted to change the configuration directory in the default config to point at my new config's folder. That setting persisted, but the app still loaded the Android/data default config, which is deeply confusing.

If anyone could shed light on this I would be very grateful. Thank you for all the excellent work on Retroarch!

Dominant language
C
Stars
14.6k
Forks
2.4k
Avg merge
2d 5h
Merged PRs (30d)
63

Getting set up

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.

More from libretro/RetroArch

All issues in libretro/RetroArch

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.