R36S Performance Optimisation Guide: Best Settings and Tweaks

If you’re here for r36s performance, you’re probably chasing one of three things: fewer slowdowns, less audio crackle, or better results in the “spicy” systems like N64 and PSP. Fair. The R36S can feel amazing for the money, but it also has a talent for turning one innocent setting change into a stuttery mess.

Here’s the good news: most performance gains come from boring, fixable stuff. Storage speed, sane defaults, and not enabling features that quietly eat your frame time. Let’s get your handheld running clean and consistent.

Table of Contents

What “good” performance looks like on R36S

You’ll enjoy the R36S most when you treat it like a brilliant PS1-and-below machine, with bonus points for some N64 and PSP when you’re willing to compromise. If your expectation is “every N64 game at 60fps, no frameskip, upscale on”, you’re going to have a bad time.

The quick ceiling guide (what’s easy, what’s borderline)

Use this as a rough mental model:

Usually effortless: GB, GBC, GBA, NES, Mega Drive, most SNES, most arcade classics.
Usually great with the right core: PS1 (most games), lighter arcade sets.
Borderline and settings-dependent: N64, PSP, a few “special chip” SNES titles, some heavier MAME content.

Not because you’re doing something wrong. It’s just physics, and a small handheld CPU.

The 3 bottlenecks that usually cause stutter

When people say “lag”, they often mean three different problems:

CPU-bound: The emulator can’t finish a frame in time. You see slow motion.
GPU-bound: Filters, upscaling, and blending effects cost too much. FPS dips in busy scenes.
I/O-bound: Your microSD can’t keep up, so you get hitching, long loads, and weird pauses.

That last one is the sneaky one. It also happens to be the easiest win.

The “Ghost in the Machine”: Why Your Charger Affects Speed

Here is a quirk no one tells you: The R36S is incredibly picky about power. If you are using a high-wattage USB-C “Fast Charger” (like a MacBook or modern Samsung brick), you might experience weird CPU throttling or even a refusal to boot.

For the most stable performance, stick to a 5V/2A “dumb” charger and a USB-A to USB-C cable. Using the wrong power source can cause the battery indicator to hallucinate, leading the OS to throttle the chip because it thinks the battery is at 1%. If your FPS is randomly tanking after a charge, look at your wall plug first.

The biggest wins first (before you touch settings)

Nothing is more annoying than tweaking for an hour and realising the real problem was the microSD card all along. Been there. I’ve seen more “performance fixes” from swapping the card than from any single RetroArch toggle.

Use a decent microSD setup (and why it changes performance)

If you’re using the card that shipped with the device, you’re playing on hard mode. Those cards are famous for corruption, inconsistent speed, and random weirdness.

What to do instead:

Use a reliable microSD for the OS (even 16GB to 32GB is fine).
If you can, use a second card for ROMs. It keeps things cleaner and reduces “everything lives on one fragile card” stress.
Keep a simple ROM folder structure. Overly deep folders plus huge artwork libraries can make browsing feel sluggish.

If you want to be extra practical, check this site’s own resources on R36S SD card compatibility and the common failure modes in R36S troubleshooting. They’ll save you time when the handheld does handheld things.

Start from a clean OS image and keep it stable

Performance tuning on a messy install is like changing tyres while the car’s on fire.

My preferred approach:

Get ArkOS installed cleanly.
Confirm a few representative games run fine.
Only then start performance tuning.

If you haven’t installed (or reinstalled) ArkOS yet, follow a step-by-step guide like how to install ArkOS on R36S. A clean baseline makes every other recommendation in this article actually stick.

Don’t get trapped by DTB and “black screen” side effects

This is a performance guide, but it matters: if your screen panel needs a different DTB, you can end up with a black screen after flashing or updating. That often leads people to panic-update, reflash repeatedly, and generally create a messy setup that feels unstable.

Warning: The Screen Version Performance Trap

There are currently at least five different screen panels floating around in R36S shells (V1 through V5). If you follow a “performance update” guide and suddenly get a black screen, you haven’t “broken” the hardware, you’ve just lost your .dtb file.

Before you start chasing performance tweaks, back up your boot partition. If you lose your specific display driver during a “performance-boosting” OS update, your handheld is a paperweight until you hunt down the specific .dtb file for your version (usually the rk3326-rg351mp-linux.dtb).

If you hit boot issues, use the checklist in R36S troubleshooting common issues before you start throwing random “performance” settings at the problem.

R36S best RetroArch settings (baseline you can trust)

Let’s keep this simple: you want a baseline that’s fast, consistent, and easy to undo. Then you add performance tricks only where they pay off.

Also, one rule that’ll save you pain: don’t change global settings for a single stubborn system. Use overrides.

Video: speed-first settings (then visuals)

Start with these principles:

Prefer native resolution (or the default core resolution) unless you know the system can handle upscale.
Turn off expensive extras first: heavy shaders, bezel overlays, and anything doing lots of scaling work.
If you see an option for “Threaded Video”, test it. Sometimes it helps smoothness, sometimes it adds a touch of latency. Your eyes and hands decide.

Small visual choices that often help performance:

Disable bilinear filtering if the image looks fine without it.
Avoid shader stacks. One lightweight shader is the most I’d use when chasing performance.

Micro-insight most people miss: if you’re using overlays (bezels), try disabling them not just for speed, but for stability. On some setups they don’t tank average FPS, they cause brief frame-time spikes, which feel like stutter even when the FPS counter looks “okay”.

Audio: fix crackle without adding lag

Audio crackle is the classic R36S complaint. Here’s the thing: it’s often not “low FPS”. It’s the audio buffer underrunning because timing isn’t stable.

What usually works:

Slightly increase audio latency or buffer until crackle stops.
Use frameskip strategically (more on that below) so the emulator doesn’t fall behind and drag audio with it.
Don’t combine low latency tricks with unstable systems. Pick one goal: smooth audio or lowest possible lag.

If your game feels smooth but crackles, treat it as an audio timing problem first, not as a raw horsepower problem.

Latency traps to disable (the silent FPS killers)

If you want r36s improve performance results fast, disable the stuff that eats frame time in the background:

Rewind
Runahead
Hard GPU shaders (especially multi-pass)
Any “enhance resolution” type options in systems that already struggle

Hot take: chasing ultra-low latency on a budget handheld is often the wrong move. Turn off runahead and rewind, accept a touch more latency, and you’ll get a steadier frame pace. Steady feels better than “technically lower lag but constantly hitching”.

Feature	Performance Impact	Recommendation for R36S
Runahead	Massive (Heavy CPU hit)	OFF for everything except NES/GB.
Rewind	Medium (Constant RAM writes)	OFF if you experience “hitching.”
Threaded Video	Low (Helps smoothness)	ON for PS1 and N64.
Bilinear Filtering	Minimal (GPU)	PERSONAL CHOICE (Turn off for “sharp” pixels).
Max Run Speed	High (Battery drain)	OFF unless fast-forwarding RPGs.

How to save overrides properly (global vs core vs game)

This is where most people accidentally sabotage themselves.

A safe workflow:

Make your baseline changes.
Test a few systems.
For system-specific tuning, save a core override or game override, not a global config.

Realistic mistake I see all the time: someone tunes N64, saves globally, then wonders why SNES has audio delay and PS1 looks wrong. Overrides exist to stop that spiral.

R36S best emulator settings by system

Two quick notes before we go system-by-system:

You can only optimise what your emulator exposes. Some systems respond better to standalone emulators than RetroArch cores.
Your goal is “playable and consistent”, not “max everything”.

If you want to see what your device is using for each platform, keep the site’s R36S emulator list handy while you tune.

PS1 (PCSX-ReARMed): smooth gameplay without ugly hacks

PS1 is where the R36S often shines.

Best practice setup:

Stick to the default PS1 emulator/core unless you have a reason to change.
Avoid upscaling unless the specific game is easy to run.
If a game drops in heavy scenes, try light frameskip instead of cranking visuals down across the board.

Also, make sure your BIOS files are correct. Missing or wrong BIOS can cause odd behaviour and worse compatibility, which people mistake for “performance”.

N64 (Mupen): the playable setup (and what to avoid)

N64 is the “welcome to compromise” system.

A practical approach:

Try the default N64 option first.
If it struggles, switch emulator (or core) before you start toggling 30 graphics options.
Use frameskip as a tool, not a lifestyle. For many games, a tiny bit of frameskip makes them playable without turning the image into soup.

Counter-intuitive trick: if a game has both US (60Hz) and PAL (50Hz) versions, testing the PAL version can make a big difference. Lower target framerate can reduce how often the emulator falls behind, which often cleans up audio too.

N64 Real-World Expectations: The “Big Three”

To save you hours of tweaking, here is the baseline for the “tough” titles:

Mario Kart 64: Runs nearly perfect on default settings.
GoldenEye 007: Expect drops to 15–20 FPS in explosions regardless of settings. It is a CPU limitation, not a settings error.
F-Zero X: Needs a standalone emulator (Rice or Glide64MK2) to maintain the 60 FPS required for the game to feel right. If it feels “floaty,” check your frameskip settings, it should be set to 0 here.

PSP (PPSSPP): the “1x then tweak” method

PSP performance lives and dies on resolution.

My tuning order:

Start at 1x resolution.
Turn off expensive extras (buffer effects, heavy filtering).
Only then touch frameskip if you still need it.

If you go straight to 2x or 3x because the screen is crisp, you’re basically volunteering for slowdown. Get it running smoothly first, then experiment.

SNES and arcade: the tricky edge cases

Most SNES runs great. Then you hit “that one game” that doesn’t.

What helps:

Swap cores if your OS offers a choice.
Turn off runahead and rewind for SNES if a specific game is stuttering.
For arcade, prefer ROM sets that match your emulator. Mismatched sets cause glitches that look like performance issues.

And yes, overlays and shaders matter here too. If you’re right on the edge, keep it clean.

R36S best VRAM settings (what that slider really does)

Think of VRAM on the R36S like the size of your coffee table. Increasing it doesn’t make the coffee (your game) taste better or brew faster; it just gives you more room to spread out your magazines (the UI themes and box art). If your table is too small, you’re constantly shuffling papers (laggy menus). If it’s too big, you’ve taken up all the space in the room (the OS loses memory for actual emulation).

This setting confuses people because it sounds like “more VRAM equals more FPS”. On the R36S, the VRAM limit setting is mainly about how much memory the frontend is allowed to reserve for visuals and themes. It’s not a magic emulator speed knob.

When to leave it alone

Leave VRAM limit at default if:

Your menus feel fine.
Your theme is lightweight.
You’re not seeing frontend crashes, long pauses, or sluggish browsing.

If your games stutter, VRAM limit is rarely the first place to look.

When to raise it (and the signs you went too far)

Consider raising VRAM limit if:

Your frontend theme is heavy (lots of video previews, fancy transitions).
Scrolling through big lists feels choppy.
Artwork-heavy setups feel sluggish.

Signs you set it too high:

Random instability after long browsing sessions.
Slow return to menu after exiting games.
General “everything feels heavier” behaviour.

Tune it like seasoning. Small moves, test, stop.

Overclock R36S (useful, but not the first lever)

People love the idea of an overclock because it feels like a cheat code. Sometimes it helps. Sometimes it just adds heat and battery drain and you barely notice a difference.

Safe expectations and downsides

Overclocking tends to help most when you’re truly CPU-bound. If you’re GPU-bound (upscaling, shaders) or I/O-bound (slow SD), an overclock won’t feel like much.

Downsides to respect:

More heat.
More battery drain.
Potential instability (crashes, hangs, corrupted saves if you hard-reset too often).

A sensible order of operations

If you want the best chance of success, do this in order:

Fix storage and stability (quality SD, clean OS).
Apply the RetroArch baseline (disable performance traps).
Tune per-system settings (especially resolution for PSP, frameskip for N64).
Only then test an overclock, and keep it modest.

That order is boring. It also works.

FAQ: quick answers

How do I make my R36S run faster without overclocking?

Start with the microSD card and a clean OS install, then disable rewind, runahead, heavy shaders, and overlays. After that, use per-system overrides to apply frameskip or lower resolution only where needed.

What are the best RetroArch settings for R36S performance?

The “best” baseline is the one that avoids hidden costs: no rewind, no runahead, lightweight visuals, and sane audio latency so crackle disappears. Save changes as overrides so one stubborn system doesn’t ruin everything else.

Why is my R36S audio crackling even when FPS looks fine?

Because audio crackle is often timing and buffer underruns, not average FPS. Increase audio latency slightly and avoid low-latency features that make frame pacing unstable.

What does the VRAM limit setting do on R36S, and what should I set it to?

It mostly controls how much memory the frontend can use for themes and media. If your menus are smooth, keep it at default. If the UI is sluggish with a heavy theme, increase it a little and test.

What are the best N64 settings on R36S for playable performance?

Use the most efficient emulator option available on your setup, keep resolution modest, and use light frameskip when necessary. Testing PAL versions of some games can help because the performance target is lower.

What are the best PPSSPP settings on R36S to reduce slowdown?

Keep resolution at 1x first, disable expensive graphics extras, then add frameskip only if a game still dips. Upscaling is usually the thing that tips PSP from “fine” to “why is this crawling”.

Does frameskip reduce input lag or increase it?

It depends on how it’s implemented and how hard the game is struggling, but in practice frameskip is a trade: you lose visual smoothness to regain speed and stability. If you’re already dropping frames naturally, controlled frameskip often feels better than constant slow motion.

Is it safe to overclock R36S, and will it help N64/PSP?

A modest overclock can be okay, but stability and battery life can suffer. It can help some CPU-bound scenes, but for PSP and N64 you’ll usually get bigger gains from resolution, emulator choice, and disabling expensive features.

Final Thoughts

If you want better r36s performance, don’t start with tweaks. Start with fundamentals, then get surgical.

Do these three action steps:

Replace the stock microSD and keep your setup tidy (consider checking R36S SD card compatibility).
Lock in a clean baseline and use overrides, not global changes (this helps when you’re bouncing between systems).
Optimise the two big offenders: N64 with careful emulator choice and light frameskip, PSP by staying at 1x resolution first.

Want to keep going? Browse the broader R36S coverage like the R36S specs and hardware overview, and if anything gets weird (boot loops, black screens, charging quirks), jump straight to R36S troubleshooting common issues before you spend another night fiddling with settings.