R36S Setup Guide 2026: First Boot, Saves and Safe Settings
Your R36S first session is a chance to check the device, learn the installed controls and confirm that progress saves correctly. The selected store offer lists Linux-based (ArkOS), with 64GB and 128GB card options. This guide covers package checks, charging, navigation, save states, fast forward and troubleshooting. Begin with a working game and a tested save, not a promised five-minute deadline.
iGameConsole Setup Guide · Updated: October 2026 · Check instructions for your actual R36S hardware and firmware build
⚡ First-Session Checklist
- Inspect the package — match your order and look for damage before powering on
- Check charging instructions — use the requirements for your actual unit
- Start the device as documented — allow the installed system to load
- Read the browser controls — confirm navigation from the on-screen prompts
- Launch one working game — check normal-speed play before changing settings
- Test a save and safe shutdown — protect progress before experimenting
📦 What's in the Box
Check the items you received against your order and its package description. The table below is an inspection checklist, not a guarantee that every accessory is included. Photograph missing or damaged items before contacting support.
| Item to check | What to verify |
|---|---|
| R36S Console | Confirm the ordered model, color and condition; a pre-applied screen protector is not guaranteed here. |
| USB-C Charging Cable | Confirm whether your package includes a cable and separate charger. Use actual unit instructions, not a universal phone-charger assumption. |
| microSD Card (preloaded) | Match the selected 64GB or 128GB option. Preserve working system and library cards; slot assignments can vary. |
| Quick Start Card | If supplied, use its hardware-specific instructions and compare them with the installed firmware. |
| Protective Pouch | Check your chosen package for a pouch or case; do not assume one is included. |
⚠ Important: Save progress, exit the game and use the installed shutdown option before handling a card. Wait until the device has finished shutting down. Back up accessible files before changing them; do not format a working card just because a computer asks to.
⚡ First Boot & Charging
Before First Use — Check the Charging Requirements
Use charging instructions and electrical ratings supplied for your actual unit. Do not assume that any phone charger or USB-C connection is suitable. Inspect the cable and charging port, keep the device on a stable uncovered surface and check for abnormal heat or damage. Initial charge level and charging duration are not established here; contact support if the required charger specification is unclear.
🔋 Charging Indicators
- Charging light — compare with the actual unit instructions
- Light changing or turning off — do not assume this alone proves a full battery
- Battery indication — check the installed system's display if available
- Charging duration: not established here; follow supplied instructions
- Charging during play: confirm whether supported rather than assuming USB-C makes it safe
⚡ Power Controls
- Power ON: follow the documented button action for your unit
- Power OFF: save, exit and use the installed shutdown option
- Sleep mode: check support and behavior before relying on it
- Wake: use documented controls; save first where possible
- Unresponsive device: contact support before guessed forced-restart timing
First Boot Sequence
- Inspect the supplied instructions and identify the documented power control
- Start the device and allow the installed firmware to load without removing cards
- Read the browser prompts once the interface appears
- Confirm which systems and titles are actually present on your selected card
- Launch a working title, check controls and test an in-game save before regular play
✅ First boot tip: Startup depends on the card, firmware and its condition. Allow the documented startup process to finish rather than applying a fixed stopwatch limit. If it repeatedly stalls, record the screen and power symptoms before changing files or firmware.
🎮 Navigating ArkOS & EmulationStation
The selected R36S listing describes Linux-based (ArkOS). ArkOS setups can use EmulationStation as the game browser, with controls and installed emulators differing by build. Read the prompts on your own screen. A system category or title in a browser does not establish that every game runs well or that a particular edition is included.
EmulationStation Navigation
| Action | Control to verify | Notes |
|---|---|---|
| Switch system | Read browser direction prompts | Browse categories actually present; menu organization can differ. |
| Browse games | Read list navigation prompts | Confirm movement without editing files or metadata. |
| Launch game | Confirm the on-screen launch control | Use one working title first; do not assume a universal A mapping. |
| Game options | Check the installed browser menu | Avoid changing emulator assignments before backing up configuration. |
| Main menu | Use the displayed menu control | Record relevant settings before making one reversible change. |
| Quick search | Check whether search is available | Search the actual title and edition; names can vary. |
| Jump to letter | Check list-jump controls if present | Do not assume R1 or L1 has the same browser action on every build. |
In-Game RetroArch Menu
Games may use RetroArch cores or standalone emulators. First identify the application running the game and its configured menu and exit controls. The following checklist replaces assumed universal shortcuts with functions to verify in your installed build.
| Action | Configured command to check |
|---|---|
| Open RetroArch menu | Identify the running emulator and its menu binding; not every game uses RetroArch. |
| Quick save state | Check save binding and active slot, then test on disposable progress. |
| Quick load state | Protect current progress before checking the load binding and slot. |
| Fast forward (hold) | Check whether a hold command is enabled in this emulator. |
| Rewind (if enabled) | Verify feature availability and configuration; it is not guaranteed. |
| Screenshot | Check the screenshot command and destination if supported. |
| Exit to EmulationStation | Use the configured quit action after saving; avoid a forced power cut. |
🎮 Button Layout & Controls
R36S Button Layout
Face Buttons (Right side)
- A — game or menu action depends on mapping
- B — game or menu action depends on mapping
- X — confirm its action in the current application
- Y — confirm its action in the current application
Shoulder Buttons
- L1 / R1 — check the physical labels and input mapping
- L2 / R2 — check how the running game uses these inputs
- Stick-click inputs — verify availability; do not assume L3/R3 support
Navigation
- D-pad — verify menu and game directions
- Left analog — assignment depends on the game and emulator
- Right analog — assignment depends on the game and emulator
System Buttons
- Start — inspect game and browser mapping
- Select — not a guaranteed universal hotkey modifier
- Power — use documented start and shutdown controls
- Volume — check the actual hardware or software adjustment
✅ Key concept — verify the hotkey: A hotkey modifier and a game button may work together, but Select is not certified as the universal modifier for every R36S build or emulator. Check the input configuration before testing a shortcut. Learn the actual menu and exit controls first, then test saving and loading on disposable progress.
💾 Save States — Complete Guide
Save states capture an emulator session where supported; in-game saves use the game's own save feature. They serve different purposes. A state may depend on the emulator, core version and game file, so do not treat it as a portable or permanent backup. Establish an in-game save and a separate file backup before experimenting.
Save State Shortcuts
| Action | Control to verify | Notes |
|---|---|---|
| Quick Save (active slot) | Configured save command | Check which slot is active; do not assume slot 0 or a screen flash proves success. |
| Quick Load (active slot) | Configured load command | A load replaces the current session state. Test only after protecting progress. |
| Save to specific slot | Installed emulator state menu | Choose an available slot and verify that a file or success message appears. |
| Load from specific slot | Installed emulator state menu | Use the matching game, emulator and compatible state; keep the original files. |
| Change active slot | State-slot option, if supported | Check the selected slot before saving; slot count and labels can vary. |
When to Use Save States
✅ Save Before These Moments
- Before a legendary encounter in a game you have verified
- Before a boss battle, using a supported spare slot
- Before a long challenge, preserving earlier progress
- Before a one-time item or irreversible choice
- Before difficult platforming, after testing state compatibility
- Before a story decision, alongside a normal in-game save
- Before stopping mid-level, then exit safely
💡 Pro Save State Strategy
- Use multiple slots where supported; keep an older working save
- Choose a current-session slot without overwriting your only recovery point
- Keep a separate area-start state if supported
- Keep a separate chapter-start state if supported
- States do not replace in-game saves or separate backups
- Test restoration on disposable progress before relying on it
⚠ Important: Removing a card does not automatically erase its files, but replacement, formatting, corruption or incompatible software can make progress unavailable. In-game saves can also be stored on the same card. Back up both save files and states where accessible, and preserve the game and emulator details needed to restore them.
⚡ Fast Forward — Complete Guide
Fast forward is an optional emulator feature for reducing waits in compatible games. Achievable speed depends on the game, emulator and processing headroom; a selected multiplier is not a measured speed guarantee. Test it after normal-speed play and saving work correctly, and return to normal speed for precise inputs or reading.
Fast Forward Controls
| Method | Control to verify | Behavior to test |
|---|---|---|
| Hold fast forward | Configured hold binding | Check that releasing it returns to normal speed; availability varies. |
| Toggle fast forward | Configured toggle binding | Learn how to switch it off before leaving it enabled. |
| Adjust speed | Rate option, if supported | A target multiplier is not guaranteed throughput. Change one option and retest. |
Best Uses for Fast Forward
| Use Case | Trial approach | What to watch |
|---|---|---|
| Pokémon EXP grinding | Normal speed first | Avoid missed choices; named-title examples do not establish inclusion. |
| Pokémon egg hatching | Optional acceleration if supported | Game-specific requirements still apply; no fixed completion time is promised. |
| RPG dialogue / cutscenes | Accelerate only familiar sections | Return to normal speed for dialogue choices and readable text. |
| Random encounter grinding | Short reversible trial | Watch audio and timing; do not expect a measured percentage saving. |
| Overworld travel | Use only when movement remains controllable | Turn it off near hazards, menus or precision actions. |
| Battle animations (Pokémon) | Compare normal and accelerated play | Protect progress first; stop if game behavior or audio becomes unstable. |
⚙️ Recommended Settings
Display Settings
| Setting | Starting approach | Why |
|---|---|---|
| Brightness | Comfortable readable level | Choose for your environment; no fixed percentage proves maximum runtime. |
| Aspect ratio | Original game ratio where supported | GBA uses 3:2; do not stretch every system to the screen's 4:3 shape. |
| Integer scaling | Compare on and off if available | It can preserve pixel proportions but may reduce the displayed image size. |
| Shader | Start without optional effects | Add effects only after checking readability and performance; available presets vary. |
| Screen filter | Compare available filter options | Choose your preferred sharpness or smoothing, not an assumed universal default. |
Audio Settings
| Setting | Starting approach |
|---|---|
| Volume | Start low and use the documented volume control; do not assume a hardware rocker. |
| Headphones | Verify the actual connector and supported headphones. Reduce volume before connecting; do not assume automatic adjustment. |
| Audio sync | Keep the working configuration first; investigate persistent symptoms without applying a universal latency preset. |
Battery Optimization Settings
| Setting | Conservative first-session approach |
|---|---|
| Brightness | Use a comfortable level; observe your own battery behavior without a runtime guarantee. |
| WiFi | Wireless availability is not confirmed for this offer. Do not assume built-in Wi-Fi or a measured saving from disabling it. |
| Volume | Use a comfortable level; headphones are a preference, not a verified battery-saving claim. |
| Sleep timer | Check whether supported; save before leaving the device idle and use safe shutdown when finished. |
🎮 Finding Games by System
The selected 64GB offer lists 15,000+ games and the 128GB offer lists 20,000+. These counts are not title manifests, language guarantees or proof of playability. Use the system labels below as search ideas. Check the actual library and the exact title with support if a particular game is essential; a larger card does not upgrade processing power.
| System | Possible browser label | 64GB check | 128GB check | Title ideas, not an inclusion list |
|---|---|---|---|---|
| Game Boy Advance | GBA | Verify actual library | Verify actual library | Pokémon Emerald, Zelda and Metroid titles: check exact editions. |
| Game Boy Color | GBC | Verify actual library | Verify actual library | Pokémon Gold, Silver or Crystal: check title and language. |
| Super Nintendo | SNES | Verify actual library | Verify actual library | Super Mario World, A Link to the Past and FFVI: confirm files and playability. |
| Nintendo Entertainment System | NES | Verify actual library | Verify actual library | Super Mario Bros., Mega Man and Contra: confirm exact versions. |
| PlayStation 1 | PSX / PS1 | Verify actual library | Verify actual library | FFVII, Crash Bandicoot and Spyro: check game, region and required files. |
| Sega Genesis | Genesis / MD | Verify actual library | Verify actual library | Sonic, Streets of Rage and Mortal Kombat: examples only. |
| Nintendo 64 | N64 | Variable performance | Variable performance | Mario 64, Ocarina of Time and GoldenEye: title-specific checks needed. |
| PSP | PSP | Variable performance | Variable performance | Patapon, Tactics Ogre and Crisis Core: no full-speed or inclusion guarantee. |
| Nintendo DS | NDS | Verify emulator and input needs | Verify emulator and input needs | HeartGold and Platinum: verify two-screen and touch-control requirements; capacity does not add hardware. |
🔧 Troubleshooting Common Issues
❌ Issue: Device won't turn on
Check in order:
- Check the charging requirement and visible power symptoms without assuming a fixed thirty-minute cure
- Use the documented power control, not guessed button-hold durations
- Inspect for damage; try another cable or power source only if it meets the actual unit specification
- If still unresponsive, record symptoms and contact support before formatting cards or force cycling
❌ Issue: Game won't launch / crashes on startup
Check in order:
- Use the confirmed emulator quit command if responsive; avoid cutting power while files may be written
- Record the exact title and whether another known working game launches
- Keep working files and configuration; a crash alone does not prove a corrupt ROM
- Confirm the running emulator and supported backend; do not force Vulkan as a universal remedy
❌ Issue: Screen is too dark / too bright
Check in order: Read the actual system menu or supplied instructions for brightness controls. Avoid guessed Power-plus-button combinations. Adjust to a comfortable readable level; if no adjustment is available or the display remains abnormal, record the symptom and contact support.
❌ Issue: Audio is crackling or out of sync
Check in order:
- Return to normal speed and compare whether the symptom persists
- Identify the running emulator and record its working audio settings
- Make only one reversible change, following instructions for that actual version
- Do not treat 64ms as a verified default or a guaranteed fix
- If persistent, note the game, emulator and output device and contact support
❌ Issue: Save state not working
Check in order:
- Check the actual state command and active slot rather than assuming a Select combination
- Read the success or error message, then test a load on disposable progress
- Confirm matching game and compatible emulator/core version; preserve the original state
- Check available storage without deleting important saves; back up before file changes
❌ Issue: PSP game running slowly
Check in order:
- Identify the PSP emulator and its configured menu command
- Check the available rendering-resolution option against that version's instructions
- Use a supported backend rather than assuming Vulkan is available or faster
- Remove optional effects only as a recorded reversible trial
- Do not enable Fast Memory or I/O options as universal fixes; some titles remain limited
- See the PSP buying and performance-check guide; settings do not guarantee full-speed play
❌ Issue: Device gets hot during PSP gaming
Safety first: Stop playing and stop charging if the unit becomes unusually hot, develops an unusual smell, shows swelling or has visible damage. Do not keep testing by switching games. If safe, shut it down and disconnect external power; let it cool away from combustible materials and contact support. This guide does not establish a normal temperature or diagnose thermal throttling.
✅ Still need help? Contact [email protected]. We respond to customer-support requests within 24 hours, 7 days a week. Include your order number, firmware or emulator version if available, the exact symptom and a photo or short video. A response commitment is not a guaranteed repair time.
Don't Have Your R36S Yet?
Choose 64GB at $79.99 or 128GB at $89.99. The $10 step buys a different listed card option, not a faster processor.
Check the selected offer, delivery conditions and applicable returns policy before ordering. Named games, accessories and measured runtime are not guaranteed by this guide.
❓ Frequently Asked Questions
How do I save my game on the R36S?
Use the game's own save function where available, then test the installed emulator's save-state command on disposable progress. Verify the slot and use the corresponding load-state command only after protecting important progress. Commands vary by build; keep separate backups of accessible save files.
How do I use fast forward on the R36S?
Identify the running emulator and its configured fast-forward control. Test at normal speed first, then enable acceleration only where supported. Actual speed varies; return to normal speed if audio, timing or inputs become difficult. No universal button combination or 2–4× result is promised.
How do I exit a game on the R36S?
Save progress and use the installed emulator's exit or quit command, confirmed from its configuration or instructions. Allow it to return to the game browser, then use the system shutdown option before removing a card. Do not substitute a forced power cut for routine exit.
How long does the R36S battery last?
Runtime varies with brightness, game workload, volume, battery condition and the actual unit. This guide has no verified capacity or controlled runtime measurement for your R36S. Observe your device's battery indication, save regularly and follow its charging instructions rather than relying on fixed hours.
Can I add more games to the R36S?
Back up the working card and saves before adding files. Shut down fully, use a suitable card reader and follow the exact firmware's supported formats and folder instructions. Do not assume one folder path or automatic detection. Preserve system partitions and safely eject the card. Use game files only where you have the appropriate rights; ask support before changing a working setup.
Related Articles
