Does closing the RG35XX SP save your Pokémon game?

Understand the three lid-close modes

This guide covers the H700 RG35XX SP with KNULLI, not stock firmware, RG34XXSP or another RG35XX model. Inspect Lid Close Mode in your installed KNULLI settings.

The power-management documentation describes these choices; it does not supply measured battery drain or a tested Pokémon result for your configuration.

What KNULLI's shutdown auto-save means

KNULLI documents a graceful emulator exit for RetroArch cores when auto-save is enabled in Game Settings and shutdown is triggered while playing. Its guarantee is conditional on the emulator supporting auto-save. Do not treat that as confirmation that the game menu's Save command ran.

Keep two questions separate: can the session resume, and can the game's own Continue entry load the expected progress after an ordinary start? A working resume path can hide an older cartridge save. Back up both file types before changing the core or firmware.

Run a short lid-close and save check

1. Record your KNULLI version, selected GBA core, exact hack version and lid mode. Back up existing progress or use a disposable new game.
2. Reach an identifiable point, use Pokémon's Save command and close the emulator normally. Reopen through Continue and verify that point.
3. Start another short session and close the lid using the recorded setting. Reopen or boot as appropriate for that mode and observe what returns.
4. Check input, sound and the game clock where relevant. Record any unexpected movement, time change, black screen or lost controls.
5. Finally, start without relying on a resumed state and verify Continue again. Keep the test notes with the configuration that produced them.

This is a proposed verification protocol, not a hands-on result. Test display-off, suspend and shutdown separately if you want to compare them; do not switch modes, hack version and emulator together.

If reopening shows the wrong progress

First identify whether you resumed an emulator session or loaded the game's cartridge save. Preserve both before troubleshooting. If Continue returns to an older location but a resumed session is newer, the two paths are not demonstrating the same saved progress.

If the game fails after reopening, record the lid mode and whether a fresh start works. Test a backed-up configuration before changing settings. If problems follow an update, investigate the emulator and game-version changes separately. Do not overwrite the only readable save just to recreate the failure.

For actual file locations and a first GBA setup, use the RG35XX SP overview and the GBA setup paths. Pokémon Unbound is a game-profile starting point with its own requirements, not a confirmed SP test.

Choose based on your own result

If you want a dark screen for a brief pause, investigate display-off behavior. If you want a suspended session, test resume before relying on it. If you want a shutdown, verify both your auto-save configuration and the independent in-game save.

Whichever mode you use, make a deliberate in-game save before ending a long session. No mode choice here establishes hinge durability, battery runtime or universal hack compatibility.

Match lid behavior to a real pause

For a brief interruption, first decide whether you want a dark screen, a suspended session or a powered-down device. These are distinct outcomes. KNULLI documents that display-off also mutes audio and that a key press can wake the device; a dark and silent screen alone does not prove shutdown.

This table chooses a test, not a measured battery recommendation. Do not infer hours of standby life or reliable transport in a bag from the mode name.

Use two checkpoints to distinguish resume from Continue

Here is a disposable test example. At checkpoint A, make an in-game save and confirm it through Continue after closing normally. Reopen, move to a recognizable checkpoint B, then test your chosen lid mode. A and B should be easy to distinguish without important progress at stake.

1. Record what returns after reopening the lid or powering on: A, B, a menu or a failure.
2. When the game is readable, preserve the files before experimenting further. If B matters, make an in-game save from the working session.
3. Inspect a normal Continue launch independently of automatic resume, using the appropriate documented setup for your core.
4. Compare what Continue restores with the deliberate in-game save. Keep the result attached to the exact core, firmware and mode you tested.

If resume shows B while Continue shows A, you have demonstrated two different progress paths. That observation is more informative than saying “closing the lid saves.” It does not mean either file should be deleted.

If reopening shows a black screen, record whether a fresh launch works before changing the hack or firmware. A problem that occurs only after suspend needs a different investigation from a game that never boots.

Source

KNULLI: lid-close modes and conditional shutdown auto-save.

Continue with your setup

RG35XX SP with KNULLI: full overview · All Pokémon handheld paths