R36S Best Settings: The Complete Tuning Guide for Every System (2026)

R36S Best Settings: The Complete Tuning Guide for Every System (2026)

The R36S ships with settings chosen to be safe on every unit, not optimal on yours. Ten minutes of tuning meaningfully changes how the device feels — smoother scrolling, better battery, fewer audio crackles — and a lot of it is counter-intuitive. Several of the settings people reach for first make things measurably worse.

This is the whole picture, in the order we'd change things on a new console.

Menu names vary by firmware. These settings exist across ArkOS, DarkOS and stock, but the paths differ. We've used ArkOS naming since it's the most common. If you're deciding which firmware to run, start with our OS comparison.

The settings that affect everything

CPU governor — the big one

The governor decides how aggressively the chip clocks up. It is the single highest-impact setting on the device, and the right answer is per-system, not global:

System Governor Why
NES, SNES, Genesis, GB/GBC, GBA On-demand Full speed regardless. Performance mode only burns battery and makes the console warm.
PS1, arcade, Neo Geo On-demand Comfortable headroom. Switch to Performance only for the handful of heavy 3D PS1 titles.
N64, PSP, Dreamcast Performance These need every cycle. The governor's ramp-up lag causes stutter on its own.

People who set Performance globally report worse battery life and a hotter console, and gain nothing on the systems that make up most of their playing. Set it per-system.

Screen scaling — leave integer scaling off

The R36S panel is 640×480, which is an exact 4:3 match for most retro systems. That makes scaling simpler than on most handhelds:

  • SNES, NES, Genesis, PS1: full-screen 4:3. These scale to 640×480 cleanly. Integer scaling leaves black bars for no visible gain on a 3.5-inch panel.
  • GBA (240×160): this is the one case where integer scaling is worth trying. Some people prefer the sharpness; others find the border distracting. Try both for five minutes.
  • Never stretch to 16:9. Nothing was drawn for it and everything looks wrong.

Shaders — the honest verdict

Skip them. CRT and scanline shaders look wonderful on a 27-inch monitor and cost real framerate here, on a screen too small to show what they're doing. If you want one, scanline is the cheapest; avoid anything with "crt-royale" or "hq4x" in the name entirely.

Audio latency

Default latency is usually 64ms. Crackling and pops are the most common complaint on these consoles and the fix is almost always here:

  • Crackling? Raise latency to 96ms or 128ms. The added delay is imperceptible in practice; the crackling stops.
  • Everything smooth already? Try dropping to 48ms for slightly tighter response, and revert at the first pop.
  • Bluetooth audio (WiFi model): expect noticeable lag. Fine for RPGs, bad for anything needing timing. Wired is better.

Frame throttling and rewind

Leave vsync on — off produces tearing and no useful speed here. Turn rewind off unless you actively use it; it constantly writes state in the background and costs framerate on exactly the heavy systems where you can least afford it.

Per-system settings

SNES

Use snes9x2010 as your default core. It's the sweet spot on this chip. snes9x2005 is faster but less accurate — keep it for the handful of SuperFX titles (Star Fox, Yoshi's Island) that need the headroom. Avoid bsnes entirely; it's cycle-accurate and far too heavy for an A35.

Game Boy Advance

gpSP for speed, mGBA for accuracy. mGBA handles everything at full speed on the R36S, so start there and only move to gpSP if you hit a problem title. Turn on the bias/colour-correction option if GBA games look washed out to you — it recreates the original screen's palette.

PlayStation 1

Use PCSX ReARMed. Enable dynarec (it's on by default; if you've turned it off, that's your speed problem). Keep the enhanced resolution multiplier at 1x — raising it is the most common self-inflicted slowdown on this hardware. Add the PS1 BIOS files for best compatibility; a few games need them.

Arcade

FBNeo for most boards, MAME 2003-Plus for older sets. Match your ROM set version to the core version — mismatched sets are why arcade games refuse to load, far more often than any setting.

N64 and PSP

These two deserve their own treatment and we've written it: our N64 and PSP realistic settings guide has the per-plugin and per-core detail, and which PSP games run full speed lists what's actually worth loading. The short version: native resolution, frameskip on, enhancements off.

Battery and thermals

Settings affect runtime more than most people expect:

  • Brightness is the biggest drain. Level 4–5 of 10 is comfortable indoors and adds an hour or more versus maximum.
  • Turn WiFi off when you're not using it on the WiFi model. Idle radio costs real battery.
  • Set a sleep timeout. Five minutes. Falling asleep mid-RPG and waking to a flat battery is a rite of passage nobody needs.
  • Don't charge while playing PSP or N64. Charging heat plus sustained load is the fastest way to heat-soak the board, and a hot chip throttles. Our battery tips guide goes deeper, which matters in an Indian summer.

Expect roughly 6–8 hours on 8/16-bit systems at sensible brightness, and 3–4 on PSP with Performance governor. If you're getting significantly less than that, the cell may be tired — a 3500mAh replacement is ₹699 and a 20-minute job.

Overclocking

The R36S can be pushed past stock clocks, and it's a real gain on N64 and PSP — but it's the last thing you should touch, not the first. Silicon quality varies between units, heat becomes the limiting factor quickly, and an unstable overclock produces crashes that look like firmware bugs and waste hours. Our overclocking guide covers safe clock speeds and how to test stability properly.

Tune everything above first. Most people find they don't need the overclock afterwards.

The settings to leave alone

  • Texture filtering / upscaling. Costs frames, and on a 3.5-inch screen you cannot see the difference.
  • Run-ahead. Reduces input lag by predicting frames — and needs CPU this chip doesn't have spare.
  • Threaded video. Helps on some hardware; on RK3326 it usually adds stutter.
  • Resolution multipliers above 1x, on any emulator.
  • Aggressive frameskip on systems that don't need it. Skipping frames on SNES makes a smooth game choppy for no reason.

A sensible starting configuration

  1. Governor: on-demand globally, Performance for N64/PSP only.
  2. Brightness: 4–5 of 10.
  3. Audio latency: 96ms.
  4. Shaders: off. Vsync: on. Rewind: off.
  5. Scaling: full-screen 4:3 everywhere; try integer for GBA.
  6. Cores: snes9x2010, mGBA, PCSX ReARMed, FBNeo.
  7. Sleep timeout: 5 minutes. WiFi off unless in use.

That configuration is smooth across the whole 8/16-bit and PS1 library with good battery life, and leaves N64 and PSP set up correctly for when you get to them. Tune individual games from there — both ArkOS and PPSSPP let you save per-game settings, which is far better than compromising globally.

New to the R36S? Our setup guide covers first boot, and 50 games to play first is a good place to point a freshly tuned console.
Back to blog