Nintendo DS and 3DS on the Pocket Duo: emulators and screen setup

Start with WatermelonDS for DS and Azahar’s stable Android build for 3DS, then check the particular games you want to play. Both appear in published Pocket Duo reviews, and their separate screen controls suit the handheld’s two-panel layout. Results still vary by game, so check each one you care about.

New to Android handhelds? The quick start glossary explains what an emulator, game file, APK and BIOS are before you choose one.

Watch a step-by-step example

The French Cloud Gaming France walkthrough, filmed on the regular Pocket Duo, reaches Azahar at 20:41 and melonDS at 28:19. The video page has the full chapter outline and related setup guides. Follow the chapter for the interface, and use the project links here for current downloads.

Choose a DS emulator with external-display support

WatermelonDS documents separate external-display layouts, touch-screen use and per-game display settings, along with several renderers and resolution scaling. How a layout behaves on your firmware still needs a quick test on the device. See the WatermelonDS README.

For a performance reference, Retro Game Corps reports using 4× resolution and the low-input-latency option on the Duo, on an unnamed WatermelonDS build. Try those settings once the basic screen assignment works.

Which Azahar version should I use?

Choose the stable channel for a first setup. At this source check, 2126.2 is the stable release, while 2127.0 Alpha 4 is explicitly a prerelease. Keep a working setup and a save backup before trying the preview for a particular feature or fix.

Alpha 4 adds Android per-game settings: long-press a game in the application list to configure it on its own. That helps when one game needs a different shader profile from another. Its release notes also describe ADPF CPU-work hints, lower latency and revised “disable right eye” heuristics. The quoted 15% performance gain was measured on a Mali device, not a Pocket Duo.

The project links below show checked versions separately from video settings, because an older review that says only “Azahar” can’t tell you which current release to install.

Assign the game screens and test touch input

Open the emulator itself first. In its layout or display controls, choose a separate-display arrangement if the installed build has one. Place the game’s touch screen on the Duo’s touch panel, then tap a menu item to confirm the touch lands where you expect. Check the screen-swap control too, particularly for games that change how they use the two displays.

Close the emulator and launch the same game again. Once the assignment sticks, repeat the launch from your frontend. If it works directly but changes when launched from your library, look at the frontend’s launch-display settings. The screen troubleshooting guide walks through that comparison.

Use 2× as an Azahar starting point, then test upward

TechDweeb describes 2× as a practical balance on the Duo. Another review’s Azahar setup uses Vulkan, 3× resolution and Turnip Duo 5.1; the driver is visible on screen, but the Azahar version isn’t.

Try 2× first, check a demanding part of your game, then increase resolution if there’s room. If a particular game stutters, lower its resolution before changing several settings together. The game notes directory links individual footage, including Super Mario 3D Land and Monster Hunter 4G.

For another regular-Duo profile, Retro Game Corps’ November driver update runs Azahar with Vulkan, asynchronous shaders and 3× resolution. The reviewer leaves Disable right eye rendering and Hardware shaders off as a smoother general profile, then turns hardware shaders on by hand for titles that need more speed. That build had no per-game hardware-shader setting; Alpha 4’s per-game controls came later. The Azahar build and Turnip package in the video aren’t named, though the description links Turnip Duo 5.1. Move up to 3× once 2× runs well.

The same video reports different results by title: Super Mario 3D Land gets fast-forward headroom from hardware shaders; Pokémon Ultra Sun shows Pokémon as outlines with that option on; Donkey Kong Country Returns 3D runs faster with it on; and Mario Kart 7 and Super Smash Bros. for Nintendo 3DS appear in short 3× samples. Newer builds may behave differently, and each game note links the exact clip.

What does Pretendo online play require?

Pretendo’s official Azahar guide requires access to a real, homebrewed 3DS or 2DS for initial setup with Artic Setup Tool, then Nimbus inside Azahar. A friend code or modded console alone does not finish the emulator setup.

The guide supports official Azahar builds, not third-party forks. Its required online LLE modules disable save states while enabled. Those modules emulate more of the console’s system services; they are separate from ordinary graphics settings.

Follow the official guide for prerequisites and account setup. It illustrates desktop menus; Android controls may differ, and we have no completed Duo online test. This does not establish support in Azahar Nano or other forks.

How useful are Duo Lite tests for a regular Duo?

Lite footage is good for shortlisting games and finding settings to try. Retroid lists different processors, graphics hardware and Android versions for the two models:

The regular Duo has more processing headroom, but a different emulator build or graphics driver can still change the result for a game. Duo Lite Plus is another model again: Retroid lists the Q-7790 and Adreno 722 for it, so check whether a video says Lite or Lite Plus.

For a Lite reference, forthenext tests 17 3DS games in this stream on a supplied GammaOS Nano 1.5 beta with the bundled Azahar Nano player, mostly starting at 2×. It includes a good Nano Assault EX sample, persistent flickering in Fire Emblem Fates and a hard lock in Mario & Luigi, which is why a per-game report beats a blanket “3DS works” label. Each game note links the exact passage.

That beta was a development build at the time. The official GammaOS supported-device table doesn’t list the regular Duo, so for a regular Duo, follow the Android emulator steps above. Don’t copy a Lite firmware image, and don’t assume its bundled player matches upstream Azahar.

For more historical samples, the earlier Lite 3DS stream includes driver experiments and crashes, while the DS stream compares SeedlessDS with a DraStic fork. The guide to reading game tests explains how to separate speed, frame pacing, input and firmware differences.

A second Lite beta test: dynamic resolution and remaining limits

V1cariousGaming’s separate GammaOS preview tests a 6 GB Duo Lite. The bundled player is Azahar Nano, but the firmware and emulator build numbers are unknown, so it may not match the other reviewer’s Nano 1.5 beta.

Its Pokémon X sample uses 2× with dynamic resolution enabled, so the scale can change during play. Fire Emblem Awakening has a good opening sample, but the reviewer had already run it once to compile shaders, so your first launch may look different.

The video also includes a useful failed test: Luigi’s Mansion: Dark Moon still struggles after the reviewer selects Native (1×) and switches dynamic resolution off.

For DS, the reviewer describes Sonic Rush as smooth with closely synchronized screens, while Spirit Tracks still has some noticeable touch delay. Test speed, touch and screen sync separately on your own games.

Once speed, touch and screen assignment work, the shader guide covers optional LCD effects and why each panel needs checking separately. Those cosmetic effects are separate from the shader-compilation hitches covered in game tests.

LineageOS is still a development lead

A November 6 developer progress report shows LineageOS using both screens of a regular Pocket Duo. No build number, release date or download was supplied. Keep using the Android setup above until a Duo-specific release and installation instructions are available; a firmware image for a different Retroid model is not a substitute. This report provides no new DS or 3DS performance results.

The developer also linked a shared LineageOS code change for choosing which display receives gamepad input. That is source-code progress, with no new firmware download or game test.