[Android][nightly] Default retroarch.cfg file pulls from wrong location when first opened
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
From the best I can tell the app defaults to saving and loading in this directory on my Android TV device any time the app first opens.
/sdcard/Android/data/com.retroarch.ra32/files/
The app indicates that it will save and load the file from this location however and it does - while it is opened.
/sdcard/RetroArch/config
Expected behavior
I expect it to use the path the application indicates that it is going to use even for when the app initially opens. How it works on iOS, and probably other platforms. Not how it works on Android however.
So retroarch.cfg ought to save and default load (on initially opening the app) from here
/sdcard/RetroArch/config
Actual behavior
Any time the program first opens it uses
/sdcard/Android/data/com.retroarch.ra32/files/
which does not have my latest changes - because the app saves my latest aka current changes to /sdcard/RetroArch/config.
Steps to reproduce the bug
- Change a setting such as a controller mapping
- Save your current retroarch.cfg in the menu system
- Quit the app and then re-open.
- Discover your settings where not in fact saved.
Note: if this does not work then adb into your android device or use a file manager and copy from /sdcard/Android/data/com.retroarch.ra32/files/retroarch.cfg to /sdcard/RetroArch/config/retroarch.cfg so
cp /sdcard/Android/data/com.retroarch.ra32/files/retroarch.cfg /sdcard/RetroArch/config/retroarch.cfg
And then watch it save to the default config location but then open from files.....
Bisect Results
[Try to bisect and tell us when this started happening]
Version/Commit
You can find this information under Information/System Information
- RetroArch: nightly
Environment information
- OS: Android TV (9 I think)
- Compiler: [In case you are running local builds]
Contributor 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.
Research direction
Start with the Android app's initial configuration-loading path and compare it with the save path described in the report. Reproduce the issue by changing a controller mapping, saving retroarch.cfg, quitting, and reopening. Done means reopening loads /sdcard/RetroArch/config/retroarch.cfg rather than the Android app files directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100