HN-R36S-WiFi handheld — built-in WiFi for R36S multiplayer and RetroArch NetPlay

R36S Multiplayer Setup: NetPlay on ArkOS (Same WiFi + Internet)

By the Hobbyist Nirvana team · Updated September 2026 · 10 min read

R36S multiplayer is real — it is just not a Nintendo Switch invite. On ArkOS it means RetroArch NetPlay: two handhelds running the same core and the same ROM, one hosting, one joining. Same-room WiFi feels close to local. A friend in another city works, with more lag. A base (non-WiFi) unit cannot do any of this until you add a dongle, and even then it is a worse deal than buying the radio already on the board.

WiFi first, then NetPlay

If the console is not on a 2.4 GHz network yet, stop here and follow the R36S WiFi setup guide. 5 GHz SSIDs will not show up. Not sure your unit even has a radio? Does the R36S have WiFi?

What people mean by R36S multiplayer

Search results mash three different setups into one phrase. Pick the row you actually want before you touch RetroArch:

Mode What you need How it feels
Two handhelds, same house Two WiFi R36S (or one + a friend’s), same 2.4 GHz WiFi or a phone hotspot Best latency. This is the session most Indian buyers actually want — cousins on the sofa, two screens.
Friend in another city Internet on both sides, matching ROM/core, usually RetroArch’s relay server Playable on 2D fighters and co-op. Input delay is real. Turn-based or slightly lag-tolerant games win.
Two players, one screen A game that supports 2P on one device, plus a second controller if the core allows it Awkward on a 3.5″ panel. Possible for a few arcade/SNES titles. Not what most “R36S multiplayer” searches are asking.

This guide is the first two rows — NetPlay. HN units ship on ArkOS, so the menus below match that firmware, not JelOS write-ups copied from AliExpress listings.

Which model can actually host a session

Model Built-in WiFi R36S multiplayer
HN-R36S (base) — from ₹3,599 No Only with a USB WiFi dongle + OTG. Compatibility is a lottery; we do not recommend it for NetPlay.
HN-R36S-WiFi 64GB — ₹4,899 Yes The one to buy if multiplayer is the point. Dual-RAM board, radio on the PCB, NetPlay from the couch.
R36S Plus — ₹5,499 Yes Same NetPlay path, 4.0″ square screen. Fine as the second handheld in a house.
India: two consoles beat one console + a dongle

By the time a “compatible” RTL8188 dongle, OTG adapter and a weekend of driver luck are counted, you have spent most of the ₹1,100 gap to the WiFi model — and still occupy the only USB port. If R36S multiplayer is why you are shopping, get HN-R36S-WiFi (or two of them). We will show both connecting on a free 10-minute video call before you pay.

The four things that must match

NetPlay is picky. If any one of these differs, you get a refused join, a desync two minutes in, or two people staring at different frames:

  1. Same ROM dump. Same filename is not enough — region (USA/EUR/JPN), revision, and file hash must match. Copy the file from one SD card to the other if you are not sure.
  2. Same libretro core. Both on Snes9x, or both on Genesis Plus GX — not “SNES” on one and a random alternate core on the other. Set it per-game (highlight the game → Select → Edit metadata / emulator) so EmulationStation does not auto-pick differently.
  3. Same RetroArch generation. ArkOS has retroarch (64-bit) and retroarch32. Mix them and NetPlay will not handshake. Check Information → System Information → RetroArch Version on both.
  4. Same-ish ArkOS. A year-old image talking to a fresh card is the classic “it worked on YouTube” failure. Update cores from RetroArch’s Online Updater once you are on WiFi.
Save states are off-limits

RetroArch NetPlay does not support save states. One player loading a state mid-session is how you desync. Use in-game battery saves if the title has them, and agree who is allowed to reset.

Set a nickname (once)

Do this on both handhelds before the first session so the host list is readable:

  1. From EmulationStation, open RetroArch (or launch any RetroArch game and open the menu — hotkeys below).
  2. Settings → User → Username — something short you will recognise on a 3.5″ screen.
  3. Configuration File → Save Current Configuration so it survives a reboot.
  4. Repeat inside retroarch32 if you use 32-bit cores (arcade / some older systems).

Hotkeys on ArkOS:

  • RetroArch (64-bit): Select + X opens the menu. B backs out a level.
  • RetroArch32: Select + Start + L1 + R1.

Mode 1 — two R36S on the same WiFi (best)

This is the setup to learn first. Latency is lowest when both radios talk to the same access point and never leave the house.

Phone hotspot often beats a crowded home mesh

Jio/Airtel dual-band routers, mesh nodes, and “Smart Connect” SSIDs that hop between 2.4 and 5 GHz confuse these boards. For a living-room session, turn a phone into a 2.4 GHz hotspot, join both handhelds to it, and leave the home ISP out of it. You do not need mobile data — hotspot-only is enough.

Host

  1. Both consoles on the same 2.4 GHz network. Confirm an IP under ArkOS network/system info (looks like 192.168.x.x).
  2. On the host, launch the game with the core you agreed on. Let it reach a stable title screen — do not open NetPlay from a stuttering boot.
  3. Open the RetroArch menu → Netplay.
  4. Turn Use Relay Server off. Turn Netplay NAT Traversal off. You are on a LAN; the public relay only adds delay.
  5. Host → Start Netplay Host.
  6. Optional but worth it for LAN: Settings → Network (or Netplay network options) → Netplay Check Frames = 0, Input Latency Frames = 2 (try 3 if inputs feel too tight and the guest stutters).

Guest

  1. Launch the exact same ROM with the exact same core.
  2. RetroArch menu → Netplay → Refresh Netplay Host / LAN List.
  3. Select the host’s nickname. If the list is empty, Connect to Netplay Host and type the host’s local IP from step 1 (port default is 55435).

When it works, both screens lock to the same frame and both D-pads are live. Do a 30-second test in a menu or first stage before you start a “real” match.

Turn these off or NetPlay fights itself

Rewind and run-ahead must be disabled on both devices. They rewrite frames locally; NetPlay cannot reconcile that. Also pause big downloads, 4K YouTube, and torrent clients on the same WiFi.

Mode 2 — friend in another city

Same ROM, same core, same RetroArch — then you need a path through two consumer ISPs. In India that usually means CGNAT: Jio and many Airtel fibre connections do not give you a public IPv4 you can port-forward. Direct IP connect fails even when “the WiFi is fine.”

  1. Both players online (2.4 GHz to their own routers is fine).
  2. Host: RetroArch → Netplay → turn Use Relay Server on.
  3. Host: Start Netplay Host. Share the room / nickname, not a 192.168 address — that IP is useless outside the house.
  4. Guest: same ROM/core → Netplay → join via the relay host list, or paste whatever room ID the host’s build shows.
  5. If the public relay is congested, some ArkOS builds let you point at a custom relay. That is optional hobbyist territory — get the default relay working first.

Stay in-region. A host in Bengaluru and a guest in Pune is a different game from a guest on another continent. Fighting games feel the lag first; side-scrolling co-op is more forgiving.

Use WhatsApp voice on a phone for callouts. The handheld has no useful voice chat, and talking over the game on speaker howls.

Cores that stay in sync (and ones that will not)

NetPlay is a RetroArch feature. Standalone emulators (PPSSPP, N64 standalone, Dreamcast) have their own, often absent, story. For R36S multiplayer on this chip, stick to 2D systems:

System Core to lock on both NetPlay on R36S
NES FCEUmm or Nestopia Excellent. Start here if you have never hosted.
SNES Snes9x The sweet spot — fighters, co-op, karts.
Mega Drive / Genesis Genesis Plus GX Very good.
GB / GBC / GBA Gambatte / mGBA Works; GBA is heavier. Same core name on both.
Arcade FinalBurn Neo (fbneo) Great when the ROM set matches exactly (parent + clones).
PS1 PCSX-ReARMed Hit-and-miss. 2D / light 3D only. Do not start your first session here.
N64 / Dreamcast / PSP — Treat as unsupported for NetPlay on this hardware. Play them local, single-player.

If a join fails with a core mismatch, one of you is still on the standalone emulator. Force RetroArch in the game’s metadata and try again.

Games worth hosting first

Not every classic is a good first NetPlay. Frame-perfect fighters punish 80 ms of delay; a co-op run-and-gun does not. Use originals you own — we do not link dumps.

Kind Start with Why
Co-op Contra III, Turtles in Time, Metal Slug (Neo Geo / FBNeo) Lag shows up as a missed jump, not a lost round. Best “it works!” test.
Versus, 2D Street Fighter II Turbo (SNES), King of Fighters (FBNeo) The reason people buy a second WiFi unit. Learn on same-room WiFi before internet.
Racing / sports Super Mario Kart (SNES), F-Zero (SNES), NBA Jam Readable even when delay is a beat late.

Agree the ROM region in the WhatsApp chat before anyone launches. “Street Fighter II” is four different files in a typical library.

When it will not connect

Symptom Likely cause Fix
LAN list empty Relay still on, or different SSIDs (one device on 5 GHz / guest WiFi) Relay off, NAT off, both on the same 2.4 GHz name. Join by host IP.
Join refused / ROM mismatch Different dump or core Copy the host’s ROM onto the guest card. Lock the same core in metadata.
Connects, then desyncs Rewind, run-ahead, save state, or a heavy core Disable those three. Drop to NES/SNES. Raise Input Latency Frames to 3–4.
Internet join never appears CGNAT, relay off, or a 192.168 IP sent to the other city Relay on. Do not share LAN addresses. Try a phone-hotspot host as a test.
WiFi icon, no session Still on the base (no-radio) board Confirm in which models have WiFi. A menu entry without an adapter does nothing.
Audio noise / extra lag on a dongle USB WiFi on the base model Expected. This is why the WiFi SKU exists.

FAQ: R36S multiplayer

Does the R36S have multiplayer?

Yes, on WiFi models, through RetroArch NetPlay. Two handhelds play the same ROM over your home WiFi or the internet. The original base R36S has no radio — it is a single-player device unless you add a dongle.

Can two R36S play together?

Yes. That is the intended R36S multiplayer setup: two HN-R36S-WiFi (or a WiFi R36S and an R36S Plus) on the same 2.4 GHz network, same core, same ROM, one host and one guest.

Does R36S multiplayer work without WiFi?

Not over the network. Same-screen two-player exists only for games that already supported two pads on the original hardware, and you still need a way to plug in a second controller. For “play with a friend who has their own handheld,” you want WiFi.

Is NetPlay the same as Bluetooth?

No. NetPlay is WiFi + RetroArch. These boards are not pairing like two Switches over Bluetooth.

Why is my ping fine on the phone but NetPlay stutters?

Phones use 5 GHz and modern radios. The R36S is a 2.4 GHz handheld running an emulator that must lock every frame to the other device. Close other traffic, use a hotspot, and add a couple of latency frames.

Do I need the same firmware on both?

Close enough that RetroArch and the core versions match. Mixing a random marketplace image with a current ArkOS card is the usual failure. Our WiFi units ship QC-tested on ArkOS — if you bought elsewhere, start with the ArkOS install guide so you are at least on the same planet.

Two WiFi units, one living room

HN-R36S-WiFi is the SKU we recommend when someone asks for R36S multiplayer. Dual-RAM, radio on the board, ArkOS, 15,000+ games, GST-inclusive. Book a video call and we will host a NetPlay session on a real unit before you pay.

HN-R36S-WiFi 64GB — ₹4,899 R36S Plus — ₹5,499 Base HN-R36S — from ₹3,599

Ships from Gurgaon in 24–48h · free shipping pan-India · GST-inclusive · COD & UPI · 7-day returns · WhatsApp us

Keep reading

Written by the Hobbyist Nirvana team — we sell, open, test and support these consoles in India. Menu labels drift a little across ArkOS builds; the matching-ROM / matching-core rule does not. Something unclear? Message us on WhatsApp.

Back to blog