Advanced R36S Configuration Guide
Deep dive into advanced R36S configuration for power users. Master emulator core selection, battery optimization strategies, RetroArch customization, and system-level tweaks.
Introduction
This guide is for intermediate and advanced R36S users who want to go beyond basic setup and squeeze maximum performance from their device. You should be comfortable with RetroArch menus, file management, and basic troubleshooting before proceeding.
We'll cover emulator core selection philosophy, advanced battery optimization techniques that can extend playtime by 30-50%, RetroArch's deep customization options, and system maintenance best practices. These techniques require more effort than default settings but deliver significant improvements.
Prerequisites:
- Familiarity with RetroArch Quick Menu navigation
- Understanding of basic emulation concepts (cores, ROMs, save states)
- Comfortable making system-level changes
Emulator Core Management
Understanding emulator cores and choosing the right one for each system is crucial for optimal performance and compatibility.
What Are Emulator Cores?
An emulator core is the actual emulation software that mimics a console's hardware. RetroArch is just a frontend that loads these cores. Most systems have multiple core options, each with different trade-offs.
Core Selection Philosophy:
- Speed cores: Prioritize performance over accuracy (e.g., Snes9x 2005)
- Accuracy cores: Prioritize compatibility and correctness (e.g., bsnes-mercury Accuracy)
- Balanced cores: Compromise between speed and accuracy (e.g., Snes9x Current)
Popular Cores by Console
| System | Speed Core | Balanced Core | Accuracy Core |
|---|---|---|---|
| NES | QuickNES | FCEUmm | Mesen |
| SNES | Snes9x 2005 | Snes9x Current | bsnes-mercury |
| Genesis | PicoDrive | Genesis Plus GX | BlastEm |
| Game Boy/GBC | Gambatte | SameBoy | mGBA |
| GBA | gpSP | VBA-M | mGBA |
| PS1 | PCSX ReARMed | PCSX ReARMed | DuckStation |
| N64 | Mupen64Plus | ParaLLEl N64 | N/A (too slow) |
💡 Pro Tip
On R36S, always start with speed cores for your default system configuration. The RK3326 chip isn't powerful enough to run accuracy cores at full speed for most systems beyond 8-bit. Reserve accuracy cores for specific games with known compatibility issues.
Changing Default Core Per System
Method 1: From the Game List (Easiest):
- Navigate to any game in the system you want to configure
- Highlight the game (don't launch it)
- Press START to open the menu
- Select "Emulator Settings" or "Advanced Settings"
- Choose your preferred core from the list
- The change applies to ALL games in this system
Method 2: Per-Game Override:
- Highlight the specific game
- Press START
- Select "Edit This Game's Metadata"
- Change the "Emulator" field
- Save
- This override affects ONLY this game
When to Use Different Cores
Use speed cores when:
- The game runs perfectly with the speed core (most common case)
- You're playing for extended periods and want better battery life
- Frame rate consistency matters more than perfect accuracy
Switch to accuracy cores when:
- Game has graphical glitches with the speed core
- Audio timing is noticeably off
- Game won't load or crashes immediately
- Special chip games (Super FX, SA-1) need better emulation
Advanced Battery Optimization
The R36S's 3500mAh battery can last 3-7 hours depending on usage. These advanced techniques can extend battery life significantly.
Understanding Power Consumption
Different components consume different amounts of power:
| Component | Power Draw | Impact on Battery |
|---|---|---|
| Screen @ 100% brightness | ~600mW | HIGH |
| Screen @ 50% brightness | ~300mW | MEDIUM |
| CPU (light load - NES) | ~400mW | MEDIUM |
| CPU (heavy load - PS1) | ~800mW | HIGH |
| Wi-Fi dongle | ~150mW | LOW-MEDIUM |
| Speaker audio | ~50mW | LOW |
Screen Brightness Optimization
Screen brightness is the single biggest battery drain. The relationship isn't linear - reducing from 100% to 70% saves far more power than 30% to 0%.
Brightness Recommendations by Environment:
- Indoor, dim lighting: 40-50% (extends battery ~40%)
- Indoor, normal lighting: 60-70% (extends battery ~25%)
- Outdoor, shade: 80-90% (minimal extension)
- Outdoor, direct sun: 100% (necessary for visibility)
Adjusting brightness:
- Most firmwares: SELECT + Volume Up/Down
- Or: Main Menu → System Settings → Display → Brightness
Core Efficiency Differences
Different cores consume different amounts of CPU power. Choosing efficient cores can extend battery life by 15-30% for demanding systems.
CPU-Efficient Core Choices:
- NES: QuickNES (30% less CPU than Mesen)
- SNES: Snes9x 2005 (40% less CPU than bsnes)
- Genesis: PicoDrive (25% less CPU than Genesis Plus GX)
- GBA: gpSP (50% less CPU than mGBA)
- PS1: PCSX ReARMed (20% less CPU than DuckStation)
Wi-Fi Power Management
Wi-Fi dongles consume power continuously when plugged in, even if not actively transferring data.
Power-saving strategies:
- Remove dongle when not using network features
- Use Ethernet-capable dongles instead of Wi-Fi (if your setup supports it)
- Disable automatic scraping and updates when on battery
Sleep Mode vs Full Shutdown
Sleep Mode (short press Power):
- Suspends system in ~1-2 seconds
- Drains ~2-3% battery per hour while asleep
- Good for: Short breaks (under 2 hours)
Full Shutdown (menu → power off):
- Takes ~10-15 seconds to shut down and restart
- Near-zero battery drain when off
- Good for: Longer breaks, overnight storage
✅ Battery Optimization Results
Real-world battery life improvements:
- NES at 50% brightness, QuickNES core: 6.5-7 hours (vs 4 hours at 100%)
- SNES at 60% brightness, Snes9x 2005: 5-5.5 hours (vs 3.5 hours at 100%)
- PS1 at 70% brightness, PCSX ReARMed: 3.5-4 hours (vs 2.5 hours at 100%)
Combined optimizations can extend battery life by 40-60%.
Advanced Power Settings
Auto-Sleep Configuration:
- Main Menu → System Settings → Power Management
- Set "Sleep after inactivity" to 3-5 minutes
- Enable "Dim screen before sleep" (saves power during idle)
Disable Unnecessary Features:
- Turn off achievement notifications if not using RetroAchievements
- Disable on-screen overlays (fps counter, notifications)
- Turn off rumble if using a controller with vibration
RetroArch Advanced Features
RetroArch has powerful features beyond basic emulation that many users never discover.
Shader System
Shaders apply visual filters to recreate CRT monitors, scanlines, or smooth pixel art. However, they consume GPU power.
Recommended shaders for R36S:
- None (default): Sharpest image, best performance
- lcd3x: Simulates handheld LCD effect, minimal performance hit
- zfast-crt: Simple CRT effect, light performance cost
- Avoid: crt-royale, crt-easymode (too demanding for R36S)
Applying shaders:
- Quick Menu → Shaders → Load Shader Preset
- Navigate to desired shader
- Apply
- If performance is good: Quick Menu → Shaders → Save → Save Core Preset
Network Features
ArkOS and Rocknix support network-based features when a Wi-Fi dongle is connected:
Netplay (Online Multiplayer):
- Settings → Network → Netplay → Enable
- Host or join games with other RetroArch users
- Works best with fast cores (NES, SNES, Genesis)
- Requires low-latency internet connection
RetroAchievements Integration:
- Settings → Achievements → Enable
- Log in with your RetroAchievements account
- Earn achievements while playing supported games
- Minimal battery impact when enabled
⚠️ Important
Netplay and achievements require constant internet connection. This drains battery faster due to Wi-Fi dongle power usage. Reserve these features for when plugged into power or when battery conservation isn't a priority.
Screenshot and Recording
Taking screenshots:
- Default: SELECT + R2 (varies by firmware)
- Saved to:
/roms/screenshots/ - Format: PNG (lossless)
Video recording:
- Not recommended on R36S due to SD card write speed limitations
- If needed: Quick Menu → Recording → Start Recording
- Expect performance drops and stuttering during recording
Custom Controls and Hotkeys
RetroArch allows extensive button remapping for both in-game controls and system hotkeys.
Default R36S Hotkeys
| Hotkey Combination | Function |
|---|---|
| SELECT + START | Open RetroArch menu |
| SELECT + R1 | Save state (quick save) |
| SELECT + L1 | Load state (quick load) |
| SELECT + R2 | Fast-forward (toggle) |
| SELECT + L2 | Rewind (if enabled) |
| SELECT + D-pad Up | Increase save state slot |
| SELECT + D-pad Down | Decrease save state slot |
| SELECT + X | Screenshot |
Remapping Hotkeys
- Settings → Input → Hotkeys
- Select the function you want to remap
- Press the desired button combination
- Main Menu → Configuration File → Save Current Configuration
💡 Pro Tip
Avoid remapping hotkeys that conflict with in-game controls. For example, if a game uses all face buttons, don't set a hotkey to just "A button" - always combine with SELECT to avoid accidental triggers during gameplay.
Per-Core Control Schemes
Different systems have different controller layouts. You can create optimal button mappings for each:
- Launch a game from the system
- Quick Menu → Controls → Port 1 Controls
- Remap buttons to your preference
- Quick Menu → Controls → Save Core Remap File
- All games using this core now use your custom mapping
System Maintenance
Regular maintenance prevents performance degradation and data loss.
Configuration Backup
What to backup:
/roms/- All your game ROMs/.config/retroarch/config/- RetroArch overrides and settings- Save states (location varies by firmware)
- Save files (.srm files in ROM folders)
Backup methods:
- Manual: Remove SD card, copy to computer monthly
- Network: Use SFTP/SCP if Wi-Fi enabled
- Cloud: Some firmwares support cloud sync (requires Wi-Fi)
Save State Management
Best practices:
- Use multiple save slots (SELECT + D-pad to change slots)
- Combine save states with in-game saves for redundancy
- Delete old states periodically to free SD card space
- Never rely solely on auto-save states (can be overwritten)
ROM Organization
Efficient folder structure:
/roms/
├── nes/
├── snes/
├── gba/
├── ps1/
│ ├── Final Fantasy VII (USA)/
│ │ ├── disc1.chd
│ │ ├── disc2.chd
│ │ └── disc3.chd
│ └── Metal Gear Solid.pbp
└── bios/
├── scph1001.bin
└── gba_bios.bin
Organization tips:
- Create subfolders for multi-disc games
- Keep BIOS files in a dedicated
/bios/folder - Use compressed formats (ZIP, CHD, PBP) to save space
- Name ROMs clearly with region tags: [USA], [Japan], [Europe]
📋 Maintenance Checklist
Perform these tasks monthly for optimal R36S health:
- ✓ Backup save states and save files
- ✓ Clean SD card slots with compressed air
- ✓ Check for firmware updates
- ✓ Delete unused save states
- ✓ Test SD card health with H2testw
- ✓ Verify RetroArch configuration is saved