[Feature request] Android: "RetroArch settings were potentially modified but not saved last time you opened it"
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Steps to reproduce the bug
- Open RetroArch in Android.
- Modify any setting.
- Close Retroarch from Android. This will not save the setting.
- Open Retroarch again. If: Settings -> Configuration -> Save Configuration on Quit: Enabled [default] it would be useful if RetroArch displayed a "RetroArch settings were modified but not saved last time you opened it, because it was not closed from "Main Menu -> Quit RetroArch"
Version/Commit
- RetroArch: 1.16.0 (F-Droid)
Environment information
- OS: Android
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 by tracing Android close-and-reopen behavior and the Configuration setting at Settings → Configuration → Save Configuration on Quit. Reproduce the scenario with that option enabled, then identify how RetroArch can detect settings changed without a save through Main Menu → Quit RetroArch. Done means Android displays the requested warning on the next launch when applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100