R36S PortMaster Guide: Native Game Ports, Without Wi-Fi If Needed
PortMaster puts over 1,300 real PC and indie games on the R36S — not emulated, but compiled to run natively. Two things trip people up: it is built around a Wi-Fi connection the R36S does not have, and the folder it installs from is in a different place on ArkOS than on Rocknix.
A Port Is Not an Emulator
Everything else on the R36S works by emulation: a program pretends to be a SNES or a PlayStation, and your ROM runs inside that pretence. PortMaster mostly works differently — most of its entries are the game's own code built for ARM, running as an ordinary Linux program. But “port” covers more ground than that, and the difference matters for performance.
That distinction has a practical consequence worth understanding, because it changes what “too slow” means:
Five kinds of port, and only some are free of overhead
PortMaster's own porting documentation sorts ports into five categories, and they do not all cost the same:
- Open-source games — compiled straight from source for ARM. No overhead.
- Open-source engines — a reimplementation of the game's engine that reads your original data files. No overhead.
- Game-engine runtimes — GameMaker, Godot and Love2D games run on an ARM build of the engine. Little overhead, but you inherit the engine's own appetite.
- box86 — PortMaster describes it as a “Linux Userspace x86 Emulator that translate X86 Linux Games to arm”. This is a translation layer, and it costs.
- box64 — the same idea for x86_64 games on aarch64.
So the flat claim that ports escape emulation overhead is only true for the first three. A game reaching you through box86 is being translated instruction by instruction, which is much closer to emulation than to native code.
Where a port is native, the intuition you build from emulators genuinely does not transfer. Dreamcast struggles here because emulation pins one timing-critical thread to a single Cortex-A35 core, as our hardware breakdown explains; a natively compiled game pays no such tax. A 1997 3D game can outrun a 1994 console game under a demanding core. Just check which kind of port you are looking at before assuming it.
The trade is that someone has to do the porting work. PortMaster's library is whatever the community has built and tested, which is why it skews toward open-source engines, games whose source was released, and titles with a modern cross-platform rewrite.
The Wi-Fi Problem
PortMaster is designed around browsing and installing on the device itself, with no PC involved. That is genuinely excellent, and it assumes a network connection.
The standard R36S has no Wi-Fi
There is no wireless radio in the standard model. PortMaster's headline workflow — scroll the list, press a button, play — requires a USB Wi-Fi dongle first. Our Wi-Fi setup guide covers which dongles work and how to configure them, and the accessories guide notes the side effect worth knowing: an active dongle draws from the same power bus as the audio chip and can add background crackle.
If you would rather not add a dongle, you are not locked out. Skip to the autoinstall folder below — it does the same job over USB or a card reader.
Installing Without Wi-Fi: The Autoinstall Folder
PortMaster watches a folder for port packages and installs anything it finds there on next launch. Download the port's zip on a PC, drop it in, and the device does the rest. The folder is not in the same place on every firmware, and this is the detail that wastes people's afternoons:
| Firmware | Autoinstall folder |
|---|---|
| ArkOS | /roms/tools/PortMaster/autoinstall/ |
| Rocknix | /roms/ports/PortMaster/autoinstall/ |
Note that ArkOS treats PortMaster as a tool and Rocknix treats it as a port — hence tools versus ports. Copying a package into the wrong one produces no error and no game; the file simply sits there. If you are unsure which firmware you have, our ArkOS vs Rocknix comparison describes how each one looks on boot.
Once installed, ports appear in their own Ports section in the menu rather than alongside any console.
Ready to Run, or Bring Your Own Files
Cutting the library a different way — and this is the split that decides whether you can actually play something tonight — every entry either ships complete or expects you to supply the original game's data. The two groups are roughly the same size:
| Kind | What you get | Examples |
|---|---|---|
| Self-contained | Install and play. The game's assets are free to distribute, so the port includes everything. | Cave Story, OpenBOR engine games |
| Engine only | The port is a re-implementation of the game's engine. You supply the original data files from a copy you own. | DevilutionX (Diablo), Quake, DOOM |
The engine-only kind is the more common source of confusion: the port installs perfectly, then refuses to start, because it is waiting for game data that was never there. This is not a bug and not a compatibility problem. Each port tells you which files it needs and where to put them; read that before concluding something is broken.
A modest but real upside of engine ports: because they are modern rewrites, they often add widescreen support, better controller handling and save-anywhere — running better than the 1990s original ever did.
Keep PortMaster Itself Current
Recent ArkOS and Rocknix builds ship with PortMaster already present, which is convenient and also the source of a confusing failure: the bundled copy is only as new as the firmware image.
If a port you can see will not install
An older PortMaster can list ports it cannot correctly fetch or run, because the packaging and the runtime libraries it depends on have moved on. Update PortMaster before you troubleshoot an individual port — it can update itself from within the app, and PortMaster's own installer covers both ArkOS and Rocknix if yours is missing entirely.
The same logic applies to the firmware underneath. Our firmware guide covers keeping ArkOS or Rocknix current.
What This Hardware Actually Runs
PortMaster carries over 1,300 ports and supports a wide range of handhelds, from devices weaker than the R36S to ones several times more powerful. The list you see is not filtered to what your device can manage, so some honesty is useful.
The R36S sits at the low end of the supported range. What that means in practice:
- Comfortable: 2D games, puzzle and strategy titles, point-and-click adventures, sprite-based action games, and the classic 1990s 3D shooters whose engines were written for far weaker machines than this one.
- Depends on the port: early 3D games, 2D games on heavy modern engines, and anything arriving through box86 or box64. Two games that look equally simple can behave completely differently depending on how they were built and whether they are being translated.
- Out of reach: anything expecting a contemporary GPU or several gigabytes of memory. The R36S has neither.
Ports are tested per device by the people who make them, and that information travels with the port rather than living on this site — check the port's own notes for your device class. Two hardware realities are worth keeping in mind regardless: the panel is 640×480, so ports offering higher internal resolutions gain nothing from them, and games designed for a mouse or keyboard will be playable but never comfortable on a D-pad.
Controls Were Designed for Something Else
Every console the R36S emulates was played on a gamepad, so the buttons map onto the buttons. Ports have no such guarantee. These games were built for a keyboard, a mouse, or a controller layout that does not match this device, and the port author had to invent a scheme.
Three things follow from that:
- The port decides, not RetroArch. Ports run outside RetroArch, so RetroArch's input settings and its per-core remapping do not apply. Whatever the port ships with is what you get unless the port itself offers options.
- Read the port's own notes. Most document their layout, and many map something non-obvious — a hotkey combination to quit, or an analog stick standing in for a mouse pointer.
- Some games will never feel right. A strategy game built around a cursor is playable with a stick-driven pointer, and it is still slower than a mouse. That is a property of the game, not a fault in the port.
This is worth setting expectations about because it is the one area where ports are consistently worse than emulated console games. Our button mapping guide covers remapping for emulated systems; note that its RetroArch sections do not extend to ports.
Realistic Expectations
PortMaster is the closest thing the R36S has to a feature that grows after you buy it. The hardware is fixed, the emulation ceiling is fixed, but the port library keeps expanding, and some of what it contains is genuinely better than the retro library people buy this device for.
It asks two things in return: a Wi-Fi dongle for the easy path, or a few minutes with the autoinstall folder for the manual one. Neither is difficult once you know which folder your firmware uses.
Related Guides
- Wi-Fi Setup Guide — dongles, configuration and online features
- ArkOS vs Rocknix — which firmware you are running, and how they differ
- Firmware Guide — installing and keeping firmware current
- R36S Specs & Hardware — why native code behaves differently from emulation
- Accessories — dongles, cards and the audio side effect