First-Use Guide · Updated October 12, 2026
R36S First-Use Guide: Charging Checks, Saves and Safe Shutdown
The selected R36S listing describes Linux-based retro gaming OS (ArkOS community firmware). Confirm the supplied build before using shortcuts or changing files. These eight first-use checks prioritize charging instructions, deliberate saving and normal shutdown, not a timed setup or a factory-test claim. Keep a working card rather than flashing an unrelated image.
⏱ Quick Setup Summary
First-Use Goal
Identify your actual build and controls
First Charge
Follow supplied charging instructions
Boot Check
Observe; no fixed boot time promised
Game Check
Confirm title, controls, sound and saves
💡 Preserve a Working Setup
A listing that names ArkOS does not establish the exact delivered version, wireless accessories or all configured emulators. Check your unit’s documentation and save states controls. Do not reinstall a working system merely to follow a guide; preserve its card and backup before any later change.
🚀 Eight First-Use Checks
1
Check Charging Instructions and Device Condition
Identify the documented charging port and a compatible
USB-C cable and power source using the supplied instructions. Do not assume every connector or charger works. Stop using or charging a device with
damage, swelling or unusual heat and seek support. Identify the meaning of
actual indicator states from your unit’s documentation; this guide does not verify LED colors, a charging duration, included accessories or a universal electrical specification.
💡 Preparation: Inspect cables and ports without forcing connectors. Do not charge unattended or treat a guessed LED color as proof of full charge; follow the supplied safety instructions.
2
Power On Using the Documented Control
Follow the supplied power-on instructions without repeated forced restarts. The listed
ArkOS name does not establish a brand boot logo or a fixed timing. Allow
the documented startup process to complete. If your build uses
EmulationStation, learn the visible menu and control hints rather than assuming every system is installed.
💡 Observe: Record persistent blank screens, repeated boot loops or unusual behavior for support; do not dismiss a fault as normal flicker or try random firmware files.
3
Navigate the Main Menu
Identify how your
D-pad is mapped in the actual menu. Confirm the displayed
select control before opening a system and the
back control before returning. A menu category is not proof that every title is present or playable.
✅ Tip: Note the firmware/version information and the supplied menu help before changing settings. Do not assume a universal Start-button path.
4
Select and Launch a Game
Choose a title you can identify in the supplied library. Confirm navigation controls and the actual launch control. Observe loading and any error messages without assuming a fixed load time. Check buttons, sound and readable display before spending time on advanced settings.
💡 First Game Check: Choose a familiar game that is actually present. Assess pacing, sound and controls, not only
fps; no named title, locked frame rate or perfect compatibility is guaranteed here.
5
Learn the Essential Controls
Identify the documented bindings for these functions on your actual build and emulator. Do not treat this table as a universal button-combination list. Test saving and reloading with expendable progress before relying on it:
| Function to Identify |
Check Before Relying on It |
| Create a state |
Save state controls and slot selection vary; do not overwrite your only useful state |
| Reload a state |
Verify the intended slot and reload behavior with a test save |
| Exit a game |
Save deliberately, then use the documented exit control |
| Adjust brightness |
Identify the actual menu/control; avoid guessing volume combinations |
| Fast forward |
Confirm emulator support and binding; no fixed speed promised |
| Open emulator settings |
RetroArch applies only where that emulator is used; other emulators differ |
| Suspend/resume |
Check whether supported; suspension is not full shutdown |
| Normal shutdown |
Save, exit and use the documented shutdown menu; wait for complete power-off |
6
Check Wireless Requirements Only If Needed
Do not assume built-in Wi-Fi or a preconfigured radio. Identify
compatible hardware, adapter and drivers for your actual unit and build before attempting an online feature.
WiFi menu entries do not prove installed radio hardware, connectivity or accessory compatibility.
💡 Configuration: Follow the instructions for a supported accessory and build. Do not buy an arbitrary adapter or expect a generic network menu to work.
⚠️ Note: Offline use is different from game compatibility. Online features need suitable hardware and setup; no all-games-perfect claim is made.
7
Adjust Display Settings (optional)
Record existing settings before changing
one documented option such as a visual
theme. For brightness, identify
the actual supported control. Where the game uses
RetroArch, find the relevant
documented display setting for that build. Keep a way to undo changes; do not assume settings are lab-optimized or borrow menu paths from another version.
8
Add Files Only After Backup and Full Shutdown
The selected listing advertises 15,000+ games for 64GB and 20,000+ for 128GB, not a title manifest. Before adding
ROM files, save, exit, shut down normally and wait for full power-off before removing a card. Back up existing files and identify the actual card, partition, supported format and
documented system folder. Do not format an unfamiliar partition or overwrite a working system. Safely eject computer media before reinsertion; indexing and refresh behavior depend on the build.
⚠️ Permissions: Use files you are authorized to use. Ownership of a cartridge alone is not a blanket permission for every download or copying method. This guide supplies no game downloads or legal clearance.
🛠️ Troubleshooting Common Issues
🔊 No Sound
Check the documented volume control and whether headphones or a mute setting affect output. If the game uses RetroArch, inspect its documented audio configuration without random resets. Note whether the issue affects one game or the whole device; seek support if basic checks do not resolve it.
📺 Screen Too Dark
Identify the supported brightness control in your actual build. No universal combination or default percentage is verified here. The selected listing describes a 3.5-inch IPS display, not guaranteed readability in every lighting condition. Record persistent display faults rather than repeatedly changing unrelated settings.
🎮 Game Running Slowly
Check the exact game, edition, emulator and settings. A nominal fps result or listed RK3326 chipset does not certify every GBA/SNES/PS1 title or demanding N64/PSP game. Record the symptom before changing a core; preserve settings and saves, and do not randomly swap software to chase a claimed fixed frame rate.
❌ Device Won't Turn On
Follow the supplied charging and startup instructions with compatible equipment. Stop if there is damage, swelling, unusual heat or smell. Do not force repeated restarts, open the case, format the card or flash an unrelated image as a first response. Contact [email protected] with the model, version if accessible and observed symptoms. We respond to customer-support requests within 24 hours, 7 days a week; this is not a resolution guarantee.
❓ Frequently Asked Questions
How long does it take to set up the R36S?
No fixed setup time is verified here. Charging condition, the supplied build, controls and your learning needs matter. Preserve working
stock firmware instead of assuming it must be replaced with
ArkOS. Learn saving, reloading and normal shutdown before relying on a long game session.
Do I need to install ArkOS on the iGC R36S?
The selected listing names Linux-based retro gaming OS (
ArkOS community firmware), but the exact build can vary. If your unit boots and works, do not reflash it merely because this guide discusses firmware. Identify your unit and current version, preserve its card and backups, and resolve an exact compatible release and recovery path before any needed change.
How do I save my game progress on the R36S?
Use the actual game’s saving method and identify the emulator’s documented
save state controls and slots if supported. Bindings and behavior vary by build and emulator. Test saving and reloading with expendable progress; a state is not a universal substitute for an in-game save or backup. Do not load an old state over important unsaved progress.
How do I exit a game on the R36S?
Save deliberately and allow writes to complete, then use the exit control documented for the actual emulator. Confirm return to the menu; for power-off use the normal documented shutdown process and wait for complete shutdown. Do not assume Select + Start works everywhere or routinely hold the power button to cut power.
Can I add my own games to the R36S?
Compatible, authorized
ROM files may be added following your exact build’s instructions. Back up files first, save and shut down completely before removing a card. Identify the card, partition, supported file format and actual folder; do not format unfamiliar media. Card readers and menu-refresh behavior can vary. Nominal capacity and advertised counts do not guarantee inclusion or playable quality.
Choose R36S With Clear First-Use Expectations
Selected R36S 64GB $79.99 / 128GB $89.99. Its listing names ArkOS community firmware, not a sixty-second first session. Confirm essential games and the checkout total, and learn the controls on the supplied build.
→ Shop R36S — From $79.99
Game Compatibility Guide
📖 New to retro gaming terms? Visit the iGC Retro Handheld Glossary — definitions for ArkOS, CFW, SoC, RetroArch, save states and other terms used here.
