(Android) Retroarch doesn't write sram nor states to FAT32 formatted Drives
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
Retroarch doesn't write save files like sram or states and maybe everything to FAT32 formatted drives .
Expected behavior
I've got a drive formatted to 2 partitions one NTFS and one FAT32, the writing to NTFS partition works flawless, besides a Flash Drive FAT32 drive formatted was tested as well.
Actual behavior
Talking about save states a message pops up "Saving state X" and that message get stucks and the writing of the state doesn't happen, and about the sram save doesn't work even saving within the game.
Steps to reproduce the bug
Just change the directory of save files and states files to a drive FAT32 formatted.
Version/Commit
- RetroArch: 1.9.4
Environment information
- OS: ANDROID on Nvidia Shield TV
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
Reproduce the issue on Android with RetroArch 1.9.4 by placing save and state directories on a FAT32 drive, then compare the behavior with an NTFS location. Trace the save-state and SRAM write paths to identify where FAT32 writes stop. Done means both save states and SRAM are written successfully on FAT32 without the saving message hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- mobile-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100