Inconsistent but very frequent issue after updating to latest firmware (1.1 beta-7 as of today).
Game used is Lufia: Ruins of Lore, US version, original cartridge (not a repro, I've had the same cart since the game was released).
Steps to replicate:
At any point after the first Atlas splash logo, place Pocket in Sleep
Wait at least 30 seconds; the longer you wait, the more likely the problem will occur
Wake the Pocket. There will be a short pause w/black screen after waking, then game will reset to Atlas/Taito splash screens
Other notes:
-Normal cartridge game saves seem unaffected and can be loaded and played as usual even after crash/reset
-However, quick-save data, if it exists, will be deleted after crash/reset
-Issue appears significantly less likely to happen if Analogue OS Startup Action is set to "Cartridge," but leaving the system in sleep for long enough will still result in the crash/reset on wake. Out of 30 test tries each with Pocket left in sleep mode for 30 secs, 24 out of 30 sleep + wake attempts crashed if "OS Menu" was selected, while only 14 out of 30 sleep + wake attempts crashed if "Cartridge" was selected. No other settings seemed to affect the problem one way or another. I'm not sure why this would matter, but there you go.
-Ensured all cartridge contacts are clean and free of corrosion.
-Possibly related, but maybe a separate issue: saved game states for this particular cartridge will always fail to load. I have not been able to get a single save state for this cart to work. The state will be saved successfully, but cannot then be loaded again, even after powering the device fully off, re-seating the cart, and powering back on.
-Whether the Pocket is plugged into the charger or is running on battery power does not seem to affect the issue.
-Rolling firmware version back to 1.0B (which the pocket shipped with, and is what I was using prior to 1.1 beta-7) resolved the issue. The problem does not seem to be present in 1.0B. I have not tried any of the other 1.1 beta FW versions apart from beta-7.
It's worth noting that this game's stability is questionable even on real GBA/SP hardware, and on real hardware is prone to occasional crashes, frequent extreme slowdown, soft-locking during cut scenes and lost quick-saves, especially if you're trying to run it on a DS-Lite or GBA Player...so it's already known to have issues even with N's own GBA "clones." Therefore I'm not sure if this issue is really a problem with Analogue OS, per se, or if it's just that this is a temperamental cart under the best circumstances and maybe the way 1.1 saves states/sleeps is just too much/too unexpected for an already unstable game to handle. Not a programmer at all myself, but figured I'd mention that in case it's relevant. Honestly I was surprised to see that this particular game ran "perfectly" with the FW included out of the box, right down to the expected performance problems/glitchy behavior I'd see on my SP, and I was shocked that sleep/wake worked with no issues at all on 1.0B. So not surprised to see it having issues with more complicated beta FW versions.
Anyway, let me know if there are any other tests you want me to do that could help. Apologies if this was all too wordy. I'm not sure which pieces of information were useful and which were not, so I just included everything I could think of that I observed.
Inconsistent but very frequent issue after updating to latest firmware (1.1 beta-7 as of today). Game used is Lufia: Ruins of Lore, US version, original cartridge (not a repro, I've had the same cart since the game was released).
Steps to replicate:
Other notes: -Normal cartridge game saves seem unaffected and can be loaded and played as usual even after crash/reset -However, quick-save data, if it exists, will be deleted after crash/reset -Issue appears significantly less likely to happen if Analogue OS Startup Action is set to "Cartridge," but leaving the system in sleep for long enough will still result in the crash/reset on wake. Out of 30 test tries each with Pocket left in sleep mode for 30 secs, 24 out of 30 sleep + wake attempts crashed if "OS Menu" was selected, while only 14 out of 30 sleep + wake attempts crashed if "Cartridge" was selected. No other settings seemed to affect the problem one way or another. I'm not sure why this would matter, but there you go. -Ensured all cartridge contacts are clean and free of corrosion. -Possibly related, but maybe a separate issue: saved game states for this particular cartridge will always fail to load. I have not been able to get a single save state for this cart to work. The state will be saved successfully, but cannot then be loaded again, even after powering the device fully off, re-seating the cart, and powering back on. -Whether the Pocket is plugged into the charger or is running on battery power does not seem to affect the issue. -Rolling firmware version back to 1.0B (which the pocket shipped with, and is what I was using prior to 1.1 beta-7) resolved the issue. The problem does not seem to be present in 1.0B. I have not tried any of the other 1.1 beta FW versions apart from beta-7.
It's worth noting that this game's stability is questionable even on real GBA/SP hardware, and on real hardware is prone to occasional crashes, frequent extreme slowdown, soft-locking during cut scenes and lost quick-saves, especially if you're trying to run it on a DS-Lite or GBA Player...so it's already known to have issues even with N's own GBA "clones." Therefore I'm not sure if this issue is really a problem with Analogue OS, per se, or if it's just that this is a temperamental cart under the best circumstances and maybe the way 1.1 saves states/sleeps is just too much/too unexpected for an already unstable game to handle. Not a programmer at all myself, but figured I'd mention that in case it's relevant. Honestly I was surprised to see that this particular game ran "perfectly" with the FW included out of the box, right down to the expected performance problems/glitchy behavior I'd see on my SP, and I was shocked that sleep/wake worked with no issues at all on 1.0B. So not surprised to see it having issues with more complicated beta FW versions.
Anyway, let me know if there are any other tests you want me to do that could help. Apologies if this was all too wordy. I'm not sure which pieces of information were useful and which were not, so I just included everything I could think of that I observed.