The R36S delivers genuinely strong retro gaming performance for a device at this price point, but factory defaults leave measurable headroom untouched. The gap between a stock R36S that chugs through N64 stages and one that runs them cleanly is almost entirely a software and configuration problem, not a hardware ceiling. This guide covers the specific, bench-tested ArkOS and RetroArch settings that close that gap for good.
KEY TAKEAWAYS
- The RK3326 chipset inside the R36S handles everything from Atari through PS1 brilliantly with zero configuration. N64 and PSP are the systems that need targeted work.
- Switching the CPU scaling governor to “performance” mode in ArkOS emulator settings is the single highest-impact change you can make for demanding titles.
- For N64: use RetroArch 32-bit mode, the Parallel_N64 libretro core, and conservative graphics settings before chasing visuals.
- For PSP: use standalone PPSSPP with Frame Skipping set to 2, Auto Frameskip on, and lightweight rendering choices before adding cosmetic extras.
- Replace the stock MicroSD card before diagnosing any emulator issue. It creates stuttering that looks identical to a software problem.
What the RK3326 Actually Does
The R36S is powered by the Rockchip RK3326, a quad-core ARM Cortex-A35 SoC paired with a Mali-G31 GPU. That chipset sits in a precise performance bracket: effortless on anything from Atari through the 16-bit era, genuinely good for PS1 emulation, workable for N64 with the correct libretro core, and firmly at its limits on graphically demanding PSP titles. Every optimisation decision in this guide is shaped by that bracket.
The stock firmware shipped on most R36S units does not use this hardware well. The default CPU scaling governor keeps the processor throttled during scenes that need full clock speed. The pre-installed emulator builds are generic rather than tuned for the RK3326. And the factory MicroSD card introduces read errors that masquerade as emulation bugs. Those three issues account for the vast majority of performance complaints, and all three are fixable.
For a granular look at the R36S hardware, panel variants, and realistic system-by-system emulation benchmarks, the full R36S hardware review and build quality breakdown covers what each revision can actually push. The controls are a little stiff on most units out of the box, but that is a physical reality no firmware update will address.
Install ArkOS First
ArkOS is the foundation every meaningful R36S performance optimisation is built on. This custom operating system replaces the stock Linux build with a stable, configurable environment. It includes updated libretro cores, a properly configured RetroArch frontend, standalone emulator support, and the PortMaster application repository. Trying to optimise performance on the factory firmware is working against yourself from the start.
Installing the wrong ArkOS image creates new problems instead of solving existing ones. Multiple R36S hardware revisions exist, each using a different IPS screen panel, and the correct DTB file must match your specific panel variant. Flashing a mismatched image produces a washed-out display, incorrect button mapping, or a device that boots to a black screen. That sounds dramatic, but it is usually a firmware mismatch, not a dead console.
The full walkthrough for identifying your hardware revision, selecting the correct ArkOS build, and completing initial configuration is documented in the ArkOS R36S complete guide and best builds, which is the essential reference for getting the platform foundation right before touching any of the performance settings below.
Replace the Stock MicroSD Card
The MicroSD card pre-installed in most R36S units is usually the weakest component in the box. It creates ROM loading delays, generates audio stuttering during gameplay, and produces random crashes that look exactly like emulator instability. Many owners spend hours adjusting RetroArch settings trying to fix a problem that is actually the card failing under sustained read load.
The annoying part is that a weak card rarely fails in a dramatic way. Menus can stay snappy, box art can still load, and lighter 16-bit games may look perfectly fine. Then you launch a longer PSP intro, create a save state, or hit an N64 area with texture streaming, and the handheld suddenly feels inconsistent. In my experience, that intermittent hitching is one of the clearest signs that storage is tripping over random reads rather than the emulator simply being too slow.
Card speed class matters in a specific way here. Application Performance Class ratings, A1 and A2, measure random read and write behaviour rather than just peak transfer speed. An A1 or A2 rated card from SanDisk, Samsung, or Lexar delivers more consistent access times and removes one of the most common fake performance bottlenecks on the R36S.
The best SD cards for the R36S, tested across speed classes and capacities covers specific recommendations at different budget levels, including the partition structure and formatting ArkOS expects. Replace the card before diagnosing any emulator performance issue. It removes an entire category of variables from the process.
Boosting R36S Performance with the CPU Governor
The CPU scaling governor controls how aggressively the RK3326 ramps clock speed in response to processing demand. The default “ondemand” governor waits for sustained high CPU utilisation before boosting frequency, which creates a lag between a demanding scene beginning and the processor catching up. That delay is exactly what produces the frame drops you notice at the start of an N64 level or during a PSP transition.
Switching to the “performance” governor forces the CPU to run at its highest clock profile continuously. Battery life drops a bit, but frame pacing improves immediately in any game that was sitting near the edge of playability. I tested this on Mario 64 specifically, and the opening stages were the clearest example of how much smoother the R36S feels once the chipset stops hesitating.
The tradeoff shows up fastest in real handheld use, not in menu screenshots. Performance mode gives you steadier pacing, but it also leaves less margin for messy sleep-resume behaviour and low-battery weirdness while troubleshooting. When I am testing borderline N64 or PSP games, I prefer a fresh boot over waking the device from sleep because it removes one more variable from the chain.
To apply the change in ArkOS: press Start from the EmulationStation main menu, navigate to Emulator Settings, select the specific emulator you want to configure, and set the Governor option to “Performance”. This setting applies per emulator rather than globally, so lighter systems like GBA and SNES can stay on “ondemand” to preserve battery during longer sessions.
N64 Optimisation: Core, Plugin, and Settings
Nintendo 64 emulation is the most configuration-sensitive system on the R36S, and the most rewarding to get right. The hardware can handle a large portion of the N64 library at playable frame rates with the correct setup. The wrong core or graphics setup, however, produces audio desync, heavy slowdown, and visual glitches regardless of how well everything else is tuned.
Core selection matters more than almost any other variable. In ArkOS Emulator Settings for N64, set the emulator to RetroArch 32-bit mode and start with Parallel_N64 as the core. That combination gives the RK3326 the best chance of staying stable. For stubborn titles, a different core can help, but changing three things at once usually makes diagnosis slower, not faster.
One small trap with N64 on the R36S is that a game can look fixed in menus and still fall apart in the first large 3D area. I always test three moments: the title screen, the first gameplay zone, and one effect-heavy scene with several enemies or particles on screen. If a setup only survives menus, it is not a setup, it is wishful thinking.
Once a game is running, press Select and X simultaneously to open the RetroArch quick menu. Navigate to Core Options and start with the following:
- Resolution: 640×480
- Framerate: Fullspeed
- Texture filtering: Leave it conservative while testing
- Graphics choices: Prioritise stable rendering over cosmetic upgrades
The real win on this handheld is not squeezing out prettier frames. It is avoiding frame pacing collapse. Start lean, confirm stable gameplay, and only then experiment.
| Symptom | Most likely cause | Best next step |
|---|---|---|
| Game boots but crawls after menus | Wrong emulator path or a heavier setup than the RK3326 can sustain | Switch to RetroArch 32-bit and retest with a lighter N64 setup |
| Audio crackles while the game still responds to input | CPU governor is too conservative for the scene load | Set the emulator governor to Performance and reboot the game |
| Visual glitches appear after changing graphics options | You changed too many variables at once | Revert to a conservative preset and retest one setting at a time |
| Brief pauses happen when loading new areas | Weak MicroSD performance or a compressed ROM | Test on a quality A1 or A2 card and use an uncompressed ROM if possible |
| Input feels worse after adding visual effects | Shader or overlay overhead | Disable all visual extras until performance is stable |
Save your configuration after every successful tweak. This sounds obvious, but it is where people quietly lose half an hour. A stable N64 setup on the R36S is usually built through a few small wins, not one magic toggle.
PSP Optimisation: PPSSPP Standalone Settings
PPSSPP standalone is the right place to start for PSP on the R36S. It gives you more direct control over performance options and avoids piling extra frontend overhead onto an already demanding system. On lighter PSP games the difference is modest. On harder ones, it can be the difference between annoying slowdown and something you will actually keep playing.
The easiest mistake on PPSSPP is chasing image quality before stabilising frame time. Texture scaling, fancy post-processing, and any option that sounds like a visual upgrade can eat into the tiny performance reserve this handheld has. I usually start ugly on purpose, get the game stable, and only then add back one visual tweak at a time.
These settings are a solid baseline for demanding PSP titles on the R36S:
- Frame Skipping: 2
- Auto Frameskip: On
- Alternative Speed: Off
- Rendering resolution: Keep it conservative
- Texture scaling: Leave off until the game is already stable
- Hardware Transform: On
- Software Skinning: On
- Lazy Texture Caching: On
- Spline Quality: Low
Auto Frameskip is the most important setting in that list because it keeps game logic and audio from drifting out of sync when the RK3326 hits a heavy scene. The goal is not perfect presentation. The goal is consistent playability. Once you accept that, PSP on the R36S becomes much easier to tune.
The emulated PSP CPU clock can also help on a game-by-game basis. Auto is usually fine, but some titles behave better when manually set to 333. Test it only after the baseline settings are stable, because changing CPU clock, rendering load, and frame skip all at once makes troubleshooting muddy fast.
RetroArch Global Settings That Affect Everything
Several global RetroArch settings affect performance across every libretro core on the R36S. These are not as dramatic as picking the right PSP or N64 setup, but they influence stability in ways people often miss. The complete RetroArch setup guide for R36S covers the broader menu structure and hotkey setup, while this section focuses on the settings that affect emulator headroom.
Start with the basics:
- Threaded Video: Enable
- Max Swapchain Images: 3
- Audio Latency: 64 ms as a practical starting point
- Run-Ahead: Disable for demanding systems like N64 and PSP
Shaders and overlays deserve a specific warning because they are one of the easiest ways to sabotage your own tuning session. The R36S has enough headroom to prettify PS1, SNES, and lighter arcade content, but the same shader chain can kneecap a borderline core instantly. I disable every visual extra while tuning, confirm stable gameplay, and only then bring back the lightest preset that does not disturb frame pacing.
Input response also feels better when the system is not juggling unnecessary extras in the background. That matters because people often blame the d-pad or the stiff controls when the real issue is inconsistent frame delivery. On a budget handheld, clean timing beats fancy visuals almost every time.
What the R36S Plays Without Any Tweaks
The R36S performs best when you stay honest about where the hardware naturally shines. It is excellent for everything up to PS1 and very comfortable across the 8-bit and 16-bit generations. NES, SNES, Mega Drive, GBA, Game Boy, and PS1 are where this device feels effortless. That is the heart of its value.
N64 and PSP are the systems where optimisation work matters. They are not hopeless, and they are not universally smooth either. They live in the middle, which is why specific configuration matters so much. Once you treat them as systems that need tuning rather than systems that should just work at default settings, the R36S becomes much less frustrating.
Getting Your ROM Library Right
Performance tuning only helps if the game files themselves are not creating extra friction. Compressed ROMs can add overhead during loading, inconsistent file naming can clutter your frontend, and bad dumps can look exactly like emulator instability. That is why a lot of “performance” troubleshooting quietly turns into file hygiene.
File quality matters more than it should. Mixed region dumps, random ROM hacks, duplicate disc images, and badly named folders create enough noise that you stop knowing whether the problem is the game, the core, or the storage. When a title behaves strangely, I test a clean known-good ROM before I touch another emulator setting. It saves a surprising amount of time.
The complete step-by-step guide to adding ROMs to the R36S explains the folder structure ArkOS expects and helps keep the library clean from the start. For first-time configuration after flashing ArkOS, the R36S initial setup guide for first-time configuration is the right companion page because it fixes the boring setup mistakes before they turn into fake performance problems.
Frequently Asked Questions
Is the R36S good for retro gaming?
The R36S is genuinely good for retro gaming if your expectations match the hardware. It plays everything up through the 16-bit systems incredibly well, PS1 performance is excellent, and a huge chunk of the retro library feels smooth and stable. The frustration starts when people treat N64 and PSP defaults as a fair test of the device.
Does the R36S have good build quality?
Build quality is decent for the price. The shell is functional, the IPS screen is a highlight, and the overall feel is better than the price tag suggests. The controls are a little stiff, though, and that can make borderline frame pacing feel worse than it really is because your fingers notice every tiny hesitation.
Is Boyhom R36S good?
Most R36S-branded units share the same basic platform, so the bigger variables are firmware quality, screen variant, and storage reliability rather than the name printed on the shell. In practical use, a well-set-up Boyhom unit with ArkOS and a good card will usually feel better than a badly configured “better” unit.
Does the R36S have speed up?
Yes, and there are two ways to think about it. Fast-forward exists in RetroArch for supported systems, which is useful for RPG grinding and slower titles. More importantly, switching to a performance-focused configuration is what actually improves r36s performance in demanding games, because it keeps the RK3326 from hesitating when scene load spikes.
R36S performance tuning path
The shortest path to better r36s performance is simple: install ArkOS properly, replace the stock card, set the CPU governor to Performance for heavier systems, and tune N64 and PSP with restraint instead of optimism. The R36S is not magical hardware, but it is more capable than the factory setup makes it look. Once the obvious friction points are removed, it becomes a very satisfying retro handheld with strong PS1 performance, smooth gameplay for a wide range of older systems, and stable day-to-day use.
