R36S Setup Guide 2026: First Boot, Save Checks and Safe Use
Start with the instructions supplied with your R36S and check the actual device, card and controls before your first session. This is a practical checklist, not a five-minute setup guarantee or a universal shortcut sheet. Use it to check your package, navigate your installed build, test a game and its saves, and shut down safely. The selected R36S listing describes Linux-based firmware (ArkOS); menus, emulator settings and key bindings can differ between builds. Keep a working setup intact rather than changing firmware before you have tested it.
iGameConsole Editorial Team · Updated October 2026 · R36S first-use checklist; follow the instructions for your supplied device
✅ Quick Start — 3 Checks Before Your First Session
- Power on — inspect the device and follow its supplied power-on instructions; do not assume a fixed hold duration
- Browse games — follow the directional and confirm/back prompts shown by your installed menu
- Launch and test — choose an available game, check its controls and test saving before a long session
Read the four-step checklist below before relying on shortcuts or shutting down.
📦 Check Your Package
| Item | Notes |
|---|---|
| R36S device and selected card | Compare the received color, capacity and accessories with your order and packing information. The selected listing gives 64GB: 15,000+ and 128GB: 20,000+ game figures, not a verified title-by-title manifest. A pre-applied protector is not established by this guide. |
| Charging cable, if included | Confirm the actual cable and the device-specific charging instructions. A USB-C connector alone does not establish charger, cable or power-bank compatibility. |
| Instructions, if supplied | Keep the instructions for your delivered unit. Do not assume a branded quick-start card or the shortcut map in an older guide is included or current. |
| Pouch or case, if ordered | Check your selected bundle and received package. A protective pouch is not guaranteed for every R36S order; contact support about an order-specific discrepancy. |
⚠ Before connecting power: Inspect the device and cable, then use the charging port and power source specified for your delivered unit. Do not guess a charger rating or treat a data port as the charging port. Stop if there is damage, swelling, a burning smell or excessive heat. This guide does not establish a first-charge percentage or a fixed charging time.
▶ First Boot — Step by Step
Power On
Use the power button identified in your supplied instructions. Allow the installed system to start without repeatedly forcing power cycles. There is no verified universal two-second hold, branded boot screen or 20–30-second boot time. If it does not reach a usable menu, use the troubleshooting checks below rather than formatting or reflashing the card.
Navigate the Main Menu
Follow the menu prompts for directional navigation to browse available systems. Menu themes and organization can vary, and a displayed list does not certify that every title is present or playable. Use the shown confirm control to enter a system; check the on-screen back control before proceeding.
Select a Game
Follow the game-list navigation prompts to select an available title. Use the shown launch control and allow loading to complete. A title may require suitable files, configuration or emulator support; instant loading and optimal settings for every system are not guaranteed.
Start Playing
Check directional input, action buttons and the exit command with a short, low-stakes session. Make an in-game save where available and test returning to it before relying on a long session. Test saves and shut down through the installed system’s normal shutdown process. A familiar title can be a useful first check, but Pokémon Emerald is not a guaranteed included game or a verified performance result for your unit.
🎮 Button Layout & Controls
| Button | Identify on Your Unit | Function |
|---|---|---|
| D-pad | Identify the directional pad on your actual unit | Directional input where assigned; check the menu prompts and each game’s control options. |
| Left analog stick | Identify the left stick on your actual unit | Its effect depends on the game and emulator mapping. A stick does not guarantee analog support or smooth PSP/N64 gameplay. |
| Right analog stick | Identify the right stick on your actual unit | Check whether the emulator assigns it a function. Camera control is not universal, especially for games originally designed without a second stick. |
| A / B / X / Y | Identify the labeled face buttons | Game actions depend on mapping. Confirm/back assignments may differ between the system menu and emulators; follow the displayed prompts. |
| L1 / R1 | Identify the L1/R1 labels on your unit | Shoulder input where supported and mapped; do not infer a hotkey from the button name alone. |
| L2 / R2 | Identify the L2/R2 labels on your unit | Additional button input where assigned. A shortcut works only when the installed emulator/build has that binding. |
| Start | Identify the Start label | Start or pause where the game assigns it; it is not a substitute for a verified exit or shutdown command. |
| Select | Identify the Select label | Select input where assigned. The hotkey modifier can differ by build; do not assume Select is always the modifier. |
| Power button | Identify using the supplied device instructions | Use the device-specific power procedure. Neither a fixed hold duration nor short-press sleep is established here; save and use normal system shutdown when available. |
⚡ Check Your Actual Shortcuts Before Using Them
Shortcut assignments depend on firmware, emulator and configuration, not just the R36S name. Read the installed help or key-binding menu before testing; guessed combinations can load an old state, reset a game or exit it.
| Verify the Binding | Action | When to Use |
|---|---|---|
| Check Save State binding | Save State | Use a spare slot and disposable progress first; do not overwrite your only checkpoint. |
| Check Load State binding | Load State | Confirm the correct game, core and slot; loading can discard newer unsaved progress. |
| Check fast-forward hold binding | Fast Forward, if supported | Try a low-stakes section after checking how to stop it; actual speed depends on the game and emulator. |
| Check fast-forward toggle binding | Toggle Mode, if supported | Verify the off command before enabling it. Holding and tapping the same key are not universally different speed modes. |
| Check rewind support and binding | Rewind | Use only if the current emulator supports and enables it. Availability and performance cost vary; keep ordinary saves. |
| Check exit/quit binding | Exit to Menu | Save first, then use the verified emulator exit command. Exiting alone does not establish that progress was saved. |
| Check emulator-menu binding | RetroArch Menu | Open the menu documented for the emulator currently running; it may not be RetroArch. Record settings before changes. |
| Check reset binding | Reset Game | Treat reset as potentially destructive to unsaved progress; save first and do not test it during an important session. |
| Check screenshot support and binding | Screenshot | Use only when capture is supported; check storage and privacy before sharing. Screenshots are not game saves. |
| Check mute/volume binding | Mute Audio | Use verified audio controls; restore a comfortable level without guessing key combinations. |
💡 The two checks worth learning first: Save and reload using verified commands, then exit and shut down after saving. Test with disposable progress before a long session. Do not assume Select + R1 or Select + R2 performs the same action across emulators or firmware builds.
💾 Save States — How to Use
A save state captures emulator state when supported; it is separate from the game’s own save system. It is not guaranteed to work at every point or across game editions, cores and emulator versions. Use in-game saves where available, keep backups, and test both saving and loading with progress you can afford to lose.
💾 Saving a State
- Choose a low-stakes moment and a supported emulator
- Use the verified Save State command
- Check the chosen slot and any save confirmation; do not overwrite your only state
- Test loading that state before treating it as a reliable checkpoint
Read the installed emulator’s slot controls and current slot. There is no universal slot-0 default or Select + A menu binding. Back up important saves before changing cores, firmware or cards.
💾 Loading a State
- Confirm the same game, emulator/core and intended slot
- Use the verified Load State command
- Check that the expected position actually returns
- Keep a separate backup and in-game save; loading may discard newer progress
Compatibility is not guaranteed after a game, core or firmware change. Keep the original files and configuration; do not assume a reusable state is a permanent or portable save.
When to Use Save States — iGC Recommendations
| Situation | Save State Strategy |
|---|---|
| Before legendary Pokémon | If the title and core support states, test a spare slot before an encounter. A saved state is not a guarantee of the game being included or an encounter’s outcome. |
| Before boss fights | Keep an in-game checkpoint and, if supported, a tested spare state. Loading replaces the current session’s state; preserve progress you want to keep. |
| Before important choices | Use separate, clearly identified slots if supported. Check the actual saved position before experimenting with alternate choices. |
| Before spending an in-game item | Item rules differ by title and edition. Keep a tested checkpoint if you intend to revisit a decision; do not generalize one-use rules across Pokémon generations. |
| Before difficult platforming | A tested state can help practice a section when supported. It does not make every point safe to save or eliminate input/performance limitations. |
| Before stopping for the day | Use the game’s save system where available, optionally make a tested state, wait for saving to finish, then exit and shut down normally. Keep separate backups of important progress. |
⚡ Fast Forward — How to Use
Fast forward is an optional emulator feature, not a fixed 2x/4x performance promise. Check whether the running emulator supports it, how it is bound and how to disable it. Speed, sound and input behavior can change with the title and settings; use normal speed for timing-sensitive actions.
⚡ Hold Mode — Only If Supported
Shortcut: Check the current emulator’s fast-forward hold binding
If a hold mode is available, test a short, low-stakes section and confirm that releasing the control returns to normal speed. No particular multiplier or key combination is verified here.
⚡ Toggle Mode — Only If Supported
Shortcut: Check the current emulator’s fast-forward toggle and off commands
If toggle mode is available, learn the off command before using it. Stop acceleration before important decisions or precision input. Tapping and holding the same combination do not universally select 4x and 2x modes.
Fast Forward Use Cases — What to Check
| Activity | At Normal Speed | With Acceleration | Practical Check |
|---|---|---|---|
| Pokémon egg hatching | Follow the title’s ordinary mechanics | Test only if supported | Keep a checkpoint |
| Pokémon EXP grinding (1 level) | Watch health, moves and choices | Input and audio may change | Return to normal for decisions |
| JRPG random battle | Read the battle state | Check command timing | Avoid unintended choices |
| Overworld travel (Pokémon) | Check route and encounters | Test control responsiveness | Slow down before precision input |
| Dialogue / cutscene | Read at your preferred pace | Important text may be missed | Keep story choices at normal speed |
☀ Brightness & Volume
| Setting | Verified Control | Recommended Setting |
|---|---|---|
| Brightness Up | Use the documented display control for your build | Choose a comfortable level for ambient light; no universal indoor percentage is required. |
| Brightness Down | Use the documented display control for your build | Reduce glare as needed while keeping text readable; do not rely on an invented battery-hour improvement. |
| Volume Up | Use the documented audio control for your build | Start low and raise only to a comfortable level. Games and audio outputs can differ. |
| Volume Down | Use the documented audio control for your build | Lower volume before switching audio output. A headphone connection is not a guarantee of superior sound. |
✅ Battery tip: Lower display brightness or audio when comfortable, but do not use fixed percentages as a runtime formula. Battery duration depends on the game, settings, device condition and battery. Save before low-battery shutdowns and do not rely on a stated 6-to-7.5-hour gain.
🎮 Finding Your Games
Use the system categories and search/filter tools actually available in your installed menu. The selected listing states 64GB: 15,000+ and 128GB: 20,000+ games; those figures do not verify named titles, editions, languages, unique additions or smooth play. The examples below identify original platforms, not your card’s guaranteed contents.
Finding Pokémon Games
- GBA system → Emerald, FireRed, Ruby, Sapphire and LeafGreen are GBA examples; check actual files and support rather than assuming inclusion.
- GB / GBC systems → Red, Blue and Yellow are Game Boy examples; Gold, Silver and Crystal are Game Boy Color examples. Check the appropriate category and actual edition.
- NDS system → HeartGold, SoulSilver, Platinum, Diamond and Pearl are Nintendo DS examples. A 128GB card does not certify inclusion, dual-screen/touch controls or acceptable DS performance.
Finding Other Popular Games
- SNES system → Chrono Trigger, A Link to the Past, Final Fantasy VI and Super Mario World are SNES examples, not a verified package list.
- PS1 system → Final Fantasy VII/VIII/IX, Crash, Spyro and Symphony of the Night are PS1 examples; check files, edition and emulator requirements.
- PSP system → Patapon, Tactics Ogre and Crisis Core are PSP examples, not guaranteed included or smoothly playable titles. Check the exact game and input/performance needs.
- N64 system → Ocarina of Time, Super Mario 64 and GoldenEye are N64 examples. Available files and acceptable gameplay require separate checks.
💡 Search tip: Use the installed menu’s documented search, sorting or filter options if available. A D-pad has directional controls, not letter keys; a particular Y-button filter is not universal. Check alternate titles, language/edition and hidden filters before concluding a game is absent.
🔋 Charging & Battery
| Topic | Details |
|---|---|
| Charging port | Identify the charging port from the supplied instructions. Use a compatible cable and power source specified for that device; connector shape alone does not establish compatibility. |
| Charge time | Depends on battery state, condition and the supported charging setup. A 2.5-hour full charge has not been verified here; follow the supplied instructions rather than a fixed timer. |
| Battery indicator | Read the status shown by your installed build and supplied instructions. Indicator location and meaning may vary; a displayed percentage alone is not proof of battery health. |
| GBA battery life | No verified 7.5-hour benchmark is available here. Save during long sessions and use actual behavior on your unit, not an invented brightness/runtime formula. |
| PS1 battery life | No verified 6.5-hour benchmark is available here. Title, settings and battery condition matter; preserve progress before the battery is depleted. |
| PSP battery life | No verified 4.5-hour benchmark is available here. Runtime and acceptable performance are separate checks, not guarantees based on system names. |
| Play while charging | This guide does not establish that gaming while charging is safe for your unit. Follow the supplied charging instructions, keep the device ventilated and stop using or charging it if it becomes excessively hot or shows damage. |
❓ Troubleshooting — 10 Common Questions
1. The screen is black after powering on — what do I do?
Check for damage or excessive heat first and stop use if either is present. Follow the supplied power and charging instructions; do not repeatedly force shutdowns or assume fixed hold/wait times. If a menu remains unavailable, note indicator behavior and what happened before the fault, then contact support. Keep the original card intact; do not format, reflash or swap firmware as the first response.
2. I can't find a specific game — where is it?
Check the original platform, alternate title, language/edition and any active filters in the actual game list. Capacity and game-count labels do not establish that a named title is supplied. A 128GB card does not guarantee HeartGold or any DS library; ask about the exact title before purchase or contact support with your order and the observed list.
3. The game is running slowly — how do I fix it?
Save where possible and check whether acceleration, filters or emulator settings were changed; record the original settings before making one reversible adjustment at a time. A slow title does not prove a defective unit or a corrupt file. Demanding PSP games can have limitations, and a larger card does not upgrade processing capability. Read the PSP buying and game-requirement guide for decision checks, not a verified FPS result for your delivered unit.
4. How do I exit a game and return to the menu?
First make an in-game save where supported and wait for writing to finish. Use the documented exit command for the running emulator, not an assumed Select + Start combination. If you also want a checkpoint, use a verified Save State command in a suitable slot and test it separately. Normal exit is not proof that either save succeeded; verify returning to progress before relying on it.
5. The audio is distorted or too loud — how do I adjust?
Use the documented volume control for your build and start at a low, comfortable level. Check whether the issue affects one title or multiple titles and whether acceleration is enabled. Lower volume before changing audio output. Do not assume a universal Select combination, speaker percentage or headphone quality improvement.
6. How do I save my game progress?
Use the game’s own save system where available, wait for saving to finish, and test reloading it. A tested save state can be an additional checkpoint when supported, but is not interchangeable with an in-game save or guaranteed portable across versions. Back up important saves and avoid power loss or removing a card during writes.
7. Can I add more games to the R36S?
Before adding files, back up the working card and saves, shut down through the installed system’s normal process, and wait for completion before removing a card. Identify the correct slot and storage layout from your supplied build’s instructions, not a guessed back-slot location or universal /roms/gba/ path. Use only files you are entitled to use and formats supported by the actual emulator; safely eject computer storage before reinsertion. Do not format an unrecognized partition or accept a repair prompt without preserving the original.
8. The device won't charge — what do I do?
Stop if the device or cable is damaged, swollen, smells burnt or becomes excessively hot. With power disconnected, inspect externally without inserting objects or liquids into a port. Use only the correct charging port and a known compatible cable/power source documented for your unit; do not assume any phone charger works. If it still will not charge, contact support through the store’s Contact Us page with the order, charger details and symptoms rather than repeatedly testing unknown chargers.
9. How do I use multiple save state slots?
Open the emulator’s menu using its documented menu command and inspect the actual save-slot controls, if supported. Identify which slot is selected before saving or loading; slot labels, number ranges and default selection vary. Keep a separate checkpoint and test a spare slot with disposable progress. Do not rely on a universal Select + A binding or a fixed 0–9 range.
10. The device feels warm during PSP gaming — is this normal?
This guide cannot certify that warmth is safe or that thermal protection prevents damage. If the device becomes excessively hot, smells unusual or shows swelling, stop use and charging and seek support; do not keep playing by switching games. Record the game, settings, session conditions and charging state when reporting heat. Do not open the device or treat an unverified protection claim as a safety guarantee.
🎮 Next Steps — What to Play First
Game Ideas to Check, Not a Guaranteed Included Library
- Pokémon Emerald (GBA) — A GBA RPG idea if available to you and supported; check edition, controls and saves first.
- Super Mario World (SNES) — A SNES platforming idea; test directional input and responsiveness at normal speed.
- Final Fantasy VII (PS1) — A PS1 RPG idea; check requirements and save behavior before a long session. Fast forward is optional, not guaranteed.
- Zelda: A Link to the Past (SNES) — A SNES adventure idea; keep the game’s own saves and use tested states only where supported.
- Chrono Trigger (SNES) — A SNES RPG idea; title availability, edition and acceptable play are separate checks, not promised results.
Related Articles
