Save Data is Lost when suspending device without manually closing content before exiting RetroArch about retroarch HOT 6 CLOSED

Duplicate / related:

#4837
#4901
#5046
#6803
#14518
(and probably more)

Past response from RA contributors (e.g. 1, 2, and the whole of #4901) indicate that this behaviour (SaveRAM not written to disk when saving) is intended, and "SaveRAM Autosave Interval" (autosave_interval) is the intended solution/workaround.

However, if SaveRAM Autosave Interval is not working on iOS (as mentioned in your follow-up comment), then that is a different issue worth reporting separately.

from retroarch.

for platforms with enforced memory cleanup / forced background application closing, it may be a good idea to set the default for SaveRAM Autosave Interval to be a lower value.

side question - does the autosave interval decrement only while content is active, or does it also decrement while in the menu? if the former, that behavior should probably be changed (or made into an option, with the default being set to "menu included" on impacted platforms).

on Android, it looks like you can use onPause() to flush volatile data to file; is writing a savestate and flushing current content/core and any volatile config data to a temp file feasible? if so, onStart() could check for the presence of that temp file and reload the relevant data.

from retroarch.

Yeah, on the iPhone I had that set as 10 seconds already, but it doesn’t persist if I don’t close the content and reopen the game if I want to continue.

from retroarch.

Thanks for your detailed comment @jn64. I will then close this one and open a new one, making some tests recording the screen to try to document it better.

from retroarch.

@jn64 just tested again and indeed it does not respect SaveRAM Autosave Interval on iOS. Created a new bug #16323 and attached a video to it.

from retroarch.

Created one for PSVita too: #16324

from retroarch.