I have an instance where I shutdown while running a game, then attempted to reboot, and it was no longer possible to boot from the SD card. I then mounted the SD to run fsck -- this found some orphaned clusters and incorrect free space in FSInfo Block which imply an interrupted write. (It will boot just fine after the fsck fixes, but it's a hassle to not be able to use the device until such a fix if you're out and about)
The README states:
Hold 1-2 seconds for quick save and shutdown; game will autoresume on boot. (short triple vibrate)
This might be the culprit. Are you sure this is a safe default choice and can this be disabled? I'm skeptical this can really be made robust enough.
I have an instance where I shutdown while running a game, then attempted to reboot, and it was no longer possible to boot from the SD card. I then mounted the SD to run fsck -- this found some orphaned clusters and incorrect free space in FSInfo Block which imply an interrupted write. (It will boot just fine after the fsck fixes, but it's a hassle to not be able to use the device until such a fix if you're out and about)
The README states:
This might be the culprit. Are you sure this is a safe default choice and can this be disabled? I'm skeptical this can really be made robust enough.