mirror of
https://github.com/ARMSX2/ARMSX3.git
synced 2026-08-24 16:58:52 -07:00
jpolo1224
4b147a71af
Both failures in the savedata fixup were logged as fatal while the code carried straight on -- the loop continues, the emulator starts, and one save is left as it was. On Android a fatal line goes to logcat at ANDROID_LOG_FATAL, so it reads like a crash, and it was reported as one. It is also permanent rather than transient when it happens. Android storage can refuse a directory rename outright with EPERM, and nothing about launching again changes that, so it fired on every single launch and looked like a fault that was getting worse. A user hitting it has no way to tell that their games are unaffected. Both are errors now, and both say what the consequence is and what to delete if it keeps happening, rather than repeating an alarm about something the emulator has already decided to continue past.
