Pocket Duo graphics drivers: choose and test a Turnip build

Use the system graphics driver as your first reference, then try a custom driver for a specific game or rendering problem. No driver has been shown to win across every Duo emulator and game, so a useful recommendation names the emulator, game, renderer and exact driver package together.

A graphics driver is software that lets an app use the device’s GPU. You usually don’t need to install one yourself: begin with the system driver, and only try a custom package when a game or emulator guide gives you a reason. The quick start covers the basic Android and emulator terms.

If colours look too intense across Android as well as games, start with the screen-colour comparisons before changing an emulator driver. That guide also covers why Nova calibration results may not match the Duo.

Match the regular Duo’s Adreno 722

Retroid specifies an Adreno 722 in the regular Pocket Duo. Check that GPU against a driver’s supported hardware before using a package. Advice written for the Duo Lite or another Adreno generation may not apply.

These projects in the directory address the Duo’s hardware:

• Turnip Duo targets the Pocket Duo and Adreno 722 in its project documentation.
• Vauzi Turnip lists Adreno 722 and offers separate baseline, Switch-focused and Windows-compatibility variants.
• Banner Turnip documents an experimental 710/720/722 variant alongside other packages. It passes automated build checks, but we haven’t seen a gameplay test.
• Faux123 Turnip v1.2.3 lists the regular Duo among its tested devices, using graphics test scenes rather than games.

Compare a candidate against your working driver in the game you want to play, because the projects’ version numbers and test results don’t rank against each other.

Change the driver inside an app that supports it

Use the emulator’s documented custom-driver manager if the installed build has one. These steps cover app-loaded graphics packages, which are separate from an Android system update or a firmware installation.

Keep the complete package filename, including its variant and revision. A larger version number from one maintainer doesn’t mean a newer or faster driver than another maintainer’s package. The Vauzi README shows why the package suffix matters for the intended workload.

Compare the same game scene and change one setting

Make an in-game save and write down the current emulator version, renderer and internal resolution. Play a scene that shows the problem on the system driver. Install one compatible candidate, restart the emulator if its instructions say to, and repeat that scene with the same settings.

Look beyond the FPS number. Check for missing effects, shadows, texture corruption, audio interruptions and whether the game still saves and resumes, and play past the menu or title screen. Keep your original driver available, and switch back if the new package causes a problem.

For a Duo example, Cloud Gaming France configures Azahar with Turnip Duo 5.1. The driver is visible on screen, but the Azahar build isn’t, and the example covers that one setup rather than every emulator.

A newer Retro Game Corps Duo update walks through loading a Turnip package in Azahar’s GPU Driver Manager and reports smoother 3DS play at 3×. The description links Turnip Duo 5.1, though the video doesn’t show which build was installed. The reviewer also turns Azahar’s hardware-shader option on by hand for some titles and reports a visual issue in Pokémon Ultra Sun with it enabled. Keep driver changes tied to a particular game for the same reason. See the DS and 3DS guide for the full profile and game-by-game links.

Check the package behind a new release

The November 1 Banner build includes a separate experimental A710/A720/A722 Android package ending in -710-720-Test.zip. Its maintainer says the build is checked by CI and has not been tested on a device. The Wayland and Linux variants are different packages. It’s worth a try for a specific problem, with no sign yet that it beats the Duo 5.1 package in the Azahar examples above.

The Faux123 Turnip v1.2.3 release lists the regular Pocket Duo (Adreno 722) among tested devices and describes 115 Vulkan-Samples scenes run on each device. It reports better frame times than v1.2.1 in several of those scenes, with a few slower Duo cases. These are driver test scenes, not games. If you’re chasing a specific rendering issue in an app with an AdrenoTools picker, try the exact package there and keep your working driver so you can switch back.

Keep a result you can reproduce

A November 5 community report gives a useful Dolphin example: on a regular Duo, a different driver improved the first battle in Paper Mario: The Thousand-Year Door compared with the system driver. There was still a brief stutter entering the fight. The owner hadn’t supplied the driver filename, Dolphin build or resolution, so the report doesn’t identify a package to install. Keep it as a reason to compare the same scene, then check the Dolphin reports for any more complete follow-up.

Note the game and region, firmware, emulator build, renderer, resolution, complete driver filename, the part of the game you tested and the outcome. Include refresh rates if both displays are active. If a package fixes one title but breaks another, keep both results and use per-game selection when the app supports it.

The release updates page lists new driver builds. Read a new release’s notes, and keep your working setup until a comparison gives you a reason to change.

For a CRT look, an LCD grid or a different colour treatment, use the shader guide. Those visual presets are separate from replacing a GPU driver.