Retroid Pocket Duo quick start: from Android to your first game

Start with one game that launches, responds to the controls and saves correctly. Once that works, you have a reference setup to return to when you try a different driver, emulator or frontend.

This guide covers the regular Pocket Duo, which Retroid lists with Android 16 and an Adreno 722 GPU. The Duo Lite is a different device, so its setup and performance reports may not match yours. Check the manufacturer’s specifications before choosing hardware-specific downloads.

A few terms before you start

• Android app: a program installed on the handheld, such as an emulator or a frontend.
• Emulator: an app that imitates another console so it can run a game made for that console.
• Game file: a digital copy of a game that the emulator opens. Guides may call this a ROM, disc image or game dump, depending on the original system. The Duo doesn’t include commercial game files; use content you’re entitled to use.
• Frontend: an optional library screen that organises games and launches the emulator. It doesn’t run the game itself.
• APK: an Android app installer, similar to an installer package on a computer. Only download one from the app developer or another source you’ve deliberately chosen.
• BIOS or firmware file: system software some emulators require to imitate a console. It’s separate from the emulator and game file; follow the emulator’s documentation and use a copy you’re entitled to use.

You don’t need to learn every term or install every tool at once. The safest first milestone is one emulator, one game file, working controls and a save you can reopen. To see where the compatibility information on this site comes from, read how these guides assess compatibility.

Finish Android setup and create your folders

Connect to Wi-Fi, set your time zone and check Android’s system-update settings. If an update is offered, let it finish before configuring your emulators, so you’re testing against a settled system version.

The regular Pocket Duo has 128 GB of built-in storage and a TF card slot (TF card means microSD here). Android and your installed apps live in built-in storage, and a microSD card adds removable space for files such as game backups, music and frontend artwork. You can begin without one.

The Duo starts Android from built-in storage. Some Linux-first retro handhelds start their operating system from a microSD card instead, so don’t apply instructions for those devices to the Duo. Alternate operating systems are an advanced, model-specific project. The ROCKNIX instructions for some Android devices warn that their process removes Android, so only follow steps like those if the guide supports your exact model and you mean to replace the stock system.

Not sure how much space to buy? Use the microSD size planner to estimate a card size from the systems and game counts you expect to keep. Retroid’s published specifications don’t state a maximum card capacity, so confirm that limit before buying.

For a simple first setup, leave Android, emulators, settings and saves in built-in storage, and put larger game files on a microSD card if you need more room. Android treats a portable card as separate, removable storage, so each app may need you to grant access to its folders. The official Android storage overview explains why one app doesn’t automatically get access to every other app’s private files.

When Android asks whether to use a card as portable storage or adopt it as internal storage, choose portable: the card stays removable and other devices can read it. Adopting a card erases it and encrypts it for that handheld, so it won’t work as an ordinary card in a computer or another device. Android’s storage documentation explains the tradeoff. Back up a card before formatting it, and only choose the internal/adopted option if you specifically want that behaviour.

Create a Games folder on the storage you choose, then a separate folder for each system, such as Games/DS and Games/3DS. Keep a second copy of your files somewhere safe. When an emulator or frontend asks for folder access, choose the matching folder in Android’s file picker. You may need to grant the same card access separately in each app. For frontend-specific library setup, see frontends.

Follow a full video walkthrough

For an English-language companion, Joey’s single- and dual-screen Android setup guide has chapters for general Android settings at 11:27, second-screen settings at 16:34 and Obtainium at 19:27. It covers multiple Android handhelds; its full chapter list is indexed here, with Duo-specific settings and performance review still pending.

Cloud Gaming France’s Pocket Duo setup guide is a French-language, chaptered walkthrough of the regular Duo (the creator points out where the Duo Lite differs). It starts with SD-card folders and Obtainium, then covers several emulator setups. Use the chapters as visual references alongside the written guides.

• Storage and first folders: SD card and ROM folders at 0:51. That’s one way to set up folders; you don’t have to keep every app or save on the card.
• App updates and emulators: Obtainium at 7:45, then RetroArch at 14:10. Obtainium is optional; check each imported app’s source and release before installing it.
• Nintendo DS and 3DS: Azahar at 20:41 and melonDS at 28:19, with the DS and 3DS setup guide.
• Other systems: PPSSPP, ARMSX2, Flycast, Dolphin, Cemu DS, HakuX and Eden appear in later chapters; see the HakuX guide for the original Xbox section and its limits.
• Library launchers: the video ends with DroidDeck for PC games; compare the choices in the frontend guide.

For the full outline and chapter links, open the video notes and setup-guide links.

Install one emulator and launch one game

WatermelonDS for Nintendo DS and Azahar for Nintendo 3DS are sensible first picks: both are recommended in this retail Duo review’s setup section.

Use the WatermelonDS project or Azahar release page for downloads. For a first Azahar setup, choose the stable channel; the newer alpha is meant for testing. The DS and 3DS guide explains the version and screen choices.

If an app comes as an APK, Android may ask you to let the app you downloaded it with install apps. Allow that only for the trusted source you chose, install the package, then turn the permission back off if you won’t need it again. Google Play installs skip this step.

What is Obtainium, and do you need it?

Obtainium is an optional Android app that checks selected developer release pages for app updates and can download them for Android to install. It updates apps such as emulators, and the Duo doesn’t need it. If you’re new to Android handhelds, start with Google Play when an app is available there, or install an app from the developer’s official source and update it by hand.

If a guide recommends Obtainium for a particular project, install Obtainium from its official website or official GitHub releases, then add the app using that developer’s official source URL. Obtainium only tracks the apps you add to it. Its tracking guide explains how sources and APK selection work.

If you want a prepared app list, Joey’s Obtainium guide explains his optional JSON import pack. JSON is a file of app sources and settings, not a script you need to run. Importing the pack adds entries to Obtainium; review them and install only the apps you need. You still configure each emulator separately, and the pack does not provide game files. His maintained guide explains how to refresh the list when it changes. See the Obtainium resource page for its official downloads and other setup notes.

Keep an app on the same distribution source when updating it. An app installed from F-Droid, for example, may use a different signing key from a build published on GitHub, and Android can refuse an update from a different signer. Don’t import random app lists or install an update because it showed up: check the developer, the release notes and whether the release is stable. Keep a working version if you rely on a particular emulator setup.

Open the emulator directly, grant access to the game’s folder and launch a title you know. Map the buttons if needed. For a touch-heavy game, check that touching the lower panel reaches the intended game screen. Make an ordinary in-game save, close the app and reopen that save, which tests far more of the setup than reaching a title screen.

Check both screens before changing performance settings

Set the emulator’s game-screen layout and check which picture appears on each physical panel. Try a scene that uses both screens, then close and reopen the game to see whether the layout sticks. If the panels are reversed or one is blank, use the dual-screen troubleshooting guide before changing graphics drivers.

Start with the emulator’s default renderer and system driver. If performance is poor, reduce internal resolution and repeat the same scene. Note the app version and the setting you changed so you can tell which adjustment helped.

Add your library frontend and back up the result

A frontend gives your games a shared library and launch screen. Add one once direct emulator launching works; compare the frontend options by the layout and features you want.

Keep a short setup note with the emulator version, renderer, resolution, driver choice and screen layout. Back up in-game saves using the app’s export options or documented save location. Save states are handy during play, but they can stop working between emulator builds. With a working game and a save you can reopen, you’re ready to add the next platform.

Add a visual finish when the basics work

After you can launch, play, save and reopen a game, try optional shaders and screen effects. That guide explains CRT textures, LCD grids and colour effects, with a short list of Russ’s Nova favourites to compare on your own device. Start with one game preset so you can keep your working setup.