[Feature Request] <MOVE THE ANDROID DEFAULT CFG>
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
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
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libretro/RetroArch
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
libretro/RetroArch#20108 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/RetroArch#20061 · 3 comments ·
Maintainers usually reply within 2 days
-
[Feature Request] [UX] Improve descriptions for "Rewind Buffer Size" and "Rewind Buffer Size Step"Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libretro/RetroArch#19915 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
All issues in libretro/RetroArch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
schrodinger/pymol-open-source#532 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
facebookexperimental/hermit#347 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
CTSRD-CHERI/cheribsd#2769 ·
Maintainers usually reply within 2 days
-
good first issue not started
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
CU-Robotics/firmware#257 ·
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100