Skip to content

Add configurable save folders on Android - #2401

Open
JoeysRetroHandhelds wants to merge 1 commit into
flyinghead:devfrom
JoeysRetroHandhelds:android-custom-save-folders
Open

JoeysRetroHandhelds wants to merge 1 commit into
flyinghead:devfrom
JoeysRetroHandhelds:android-custom-save-folders

Conversation

@JoeysRetroHandhelds

Copy link
Copy Markdown

Added code so that users can choose where to move or write saves to (for VMU, Savestates & Game Saves).

In General, under Custom Paths, added three new options for VMU Folder, Savestate Folders & Game Save Folder. Users can click Add, navigate using SAF and choose a different directory to store data in. If there already is saves, it will ask the user if they want to move them to this new directory as well. Choosing not to will delete so there's no leftover files.

The main reason for this PR and code is there are devices that cannot access scoped storage and so can't backup saves easily, can't access the saves, and so on. Newer devices lock scoped storage access, this lets users have access to them.

This was tested on my end using a few devices, everything seems to work as intended - but could use more testers on this to triple check.

Created with the help of Claude AI.

Route VMU, savestate, and game-save (NVRAM/EEPROM/card) I/O through
hostfs::storage() instead of raw FILE*/nowide calls so these paths
work with SAF-backed custom folders on Android, and add a migration
flow to move or delete existing saves when a new folder is picked.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant