All guides

GPU drivers

Turnip Drivers on Android: What They Are, When to Use Them, and How to Install Them Safely

By Kenjiro · November 19, 2026 · 12 min read

If you emulate on a Snapdragon phone, you will hear one piece of advice more than any other: "install Turnip." It is good advice — sometimes. It is also the easiest way to turn a game that worked into a game that does not, if you install the wrong build for your chip, or change drivers when nothing was broken.

This guide explains what Turnip actually is, which phones it works on, when a driver change helps and when to leave the stock driver alone, how to install one safely in the emulators EmuHub lists, and — most importantly — how to get back to a working setup in under a minute if a new driver makes things worse.

The short version: Turnip is an open-source Vulkan driver for Qualcomm Adreno GPUs, built inside the Mesa 3D project. On Android it does not replace your phone's system driver. It is loaded by one app at a time — an emulator that supports custom drivers — and only while that app is running. No root is needed, nothing is flashed, and switching back to the system driver undoes the change.

What Turnip is, in plain terms

Your phone talks to its GPU through a graphics driver. The one that shipped with your phone is Qualcomm's driver, frozen at whatever version your phone maker included — often old, and tuned for mobile games, not for emulation.

Turnip is an independent, open-source rewrite of that same job, built by Mesa developers rather than by Qualcomm. Mesa describes Turnip as a Vulkan driver for Adreno 6xx GPUs, with support since extended to 7xx and, in newer community builds, 8xx chips. It often fixes graphics bugs, renders effects the stock driver gets wrong, and adds features emulators need — which is why emulator handbooks single it out: Eden's handbook, for example, says Adreno 6xx and 7xx GPUs with Turnip drivers have the best compatibility.

Two things Turnip is not:

  • It is not a system update. Android will not let an app swap the system-wide GPU driver. "Installing Turnip" means handing a driver package to one emulator, which loads it in place of the phone's own driver while that emulator runs. Your other apps are unaffected.
  • It is not made by Qualcomm, and it is not magic. A newer Turnip build can fix one game and break another. The stock driver may run a game that already works faster than Turnip does. The right question is never "which driver is best?" — it is "which driver runs *this* game, on *this* phone, best?"

Which phones can use Turnip?

Turnip only applies to Qualcomm Adreno GPUs — in practice, Snapdragon phones and handhelds. That is the first check, and it rules out a lot of devices:

  • Adreno 6xx (Snapdragon 865 / 870 and similar): Turnip's home turf. Stock 6xx drivers are old, and Turnip is usually the biggest improvement here.
  • Adreno 7xx (Snapdragon 8 Gen 1 / 8 Gen 2 / 8 Gen 3, Adreno 740 and similar): Turnip works well here too. Mesa's supported-chip list in late 2026 names the Adreno 610, 650, 722, 740, A32 and 830, covering most Retroid, AYN and AYANEO handhelds as well as Snapdragon phones.
  • Adreno 8xx (Snapdragon 8 Elite, Adreno 830/840): only use builds explicitly labelled a8xx or Gen8 (for example Turnip Gen8 V38, October 2026), or a Qualcomm v8xx driver. Regular Turnip builds from before 8xx support will not load on these chips.
  • Mali, PowerVR, Exynos, or other GPUs: Turnip does not apply at all. MediaTek / Unisoc handhelds with Mali GPUs need entirely different drivers, and no Turnip download will help them. If your phone is not Snapdragon / Adreno, stop here — this guide is not for your device.

How to check your GPU: on Android, Settings > About phone usually names the chipset (for example Snapdragon 8 Gen 2); a free system-info app will show the exact Adreno model. Write it down before you download anything — the Adreno generation decides which driver family you need.

You also need Android 9 or later on a 64-bit Arm chip for the per-app driver loader (libadrenotools) that Eden, Azahar and Dolphin use. That covers essentially every phone EmuHub targets.

When to change drivers — and when to leave them alone

Change drivers only when you have a specific problem to solve. That is the rule that saves the most time.

Change drivers when:

  • A specific game renders wrong on the stock driver — missing textures, black screens in 3D scenes, broken shadows or lighting — and other users with your chip report that Turnip fixes it.
  • An emulator's own guide or handbook recommends Turnip for your chip, as Eden's does for Adreno 6xx/7xx.
  • A PC game in Winlator / GameNative runs through DXVK/VKD3D to Vulkan and stutters or glitches on the stock driver. GameNative 1.4.0 (November 2026), for example, bundles Turnip Gen8 V38 for Adreno 8xx and Turnip v27.0.0-R1 for 6xx/7xx as its starting driver — in that app you are already using Turnip by default.

Leave the stock driver alone when:

  • Everything already runs well. A driver change is a troubleshooting step, not an upgrade you owe your phone.
  • The problem is speed, not graphics. Turnip fixes rendering bugs; it does not make a weak chip strong. If a game is slow on the stock driver, first drop the internal resolution before touching drivers.
  • You are about to play a game that already works. Test a new driver on a familiar game first, in a scene you know — never right before a long session, and never change drivers and three other settings at once.

One more warning: only change drivers when a specific game has a problem, and only use drivers from the official / EmuHub-listed source. Driver packages are just files from the internet; a random zip from a download site can be an old build, a build for the wrong chip, or worse. EmuHub's driver section exists precisely so you do not have to hunt for them elsewhere.

Where to get a driver

Get drivers from EmuHub's driver section, or from the official GitHub releases page the EmuHub listing points to. Community Turnip builds are published as .zip or .adpkg packages — the AdrenoTools package format emulators accept, containing the driver file plus a small meta.json description.

Practical rules, learned the hard way by the community:

  1. Match the build to your exact Adreno generation. 6xx/7xx builds and 8xx/Gen8 builds are not interchangeable.
  2. Start with a widely used, well-documented build, not the newest experimental one. A revision that fixes one title can introduce a regression in another. As of late October 2026, widely used reference points were Turnip v27.0.0-R1 for 6xx/7xx and Turnip Gen8 V38 (19 October 2026) for 8xx — but check the official releases page for the current stable before you download, because driver builds move fast and this guide will go stale.
  3. Do not unzip the package. Emulators read the compressed .zip / .adpkg file directly. Unzipping it is the single most common install mistake.
  4. Download on the device you will use it on, or copy the untouched zip to its Downloads folder. Do not rename it to something you cannot recognise later.

Do not install a system-wide Turnip module (Magisk) unless you know exactly what you are doing. That route replaces the system driver, needs root, and is a different, riskier thing from the per-app install this guide covers. For emulation, per-app is the right scope.

How to install a driver, app by app

The pattern is the same everywhere: open the emulator's driver manager, install the zip, select it as active, test one game. The menu names differ slightly by app and version — follow the wording in your build.

Eden, Azahar and Dolphin (the libadrenotools apps): these three use the same open-source loader, so the flow is nearly identical. In the emulator, go to Settings and find the GPU driver manager (in Eden it is under Settings > GPU driver manager; in Azahar and Dolphin it is in the graphics / driver settings). Tap Install, pick the driver .zip you downloaded — do not unzip it — then tap the circle next to the Turnip driver to set it as active. Eden also offers a Fetch option that lists drivers it recommends; that list is a good starting point if you are unsure which build to pick.

Winlator (PC games): Winlator works differently — it bundles a Turnip build inside the app rather than asking you for a file. Winlator 11.2 (August 2026) updated its bundled Mesa Turnip, and you pick the graphics driver per container: open the container's settings > Graphics Driver and choose Turnip (Adreno) if you have an Adreno GPU. On Bionic forks, the path is side menu > Settings > AdrenoTools GPU Drivers > Install to add a package, then the container's settings to select it.

GameNative: like Winlator, GameNative bundles its driver — 1.4.0 starts with the bundled Turnip (Gen8 V38 on Adreno 8xx, v27.0.0-R1 on 6xx/7xx) and leaves Adreno 710-family GPUs on the system driver. You can import a different package from its driver settings if a specific game needs it, but start with the bundled one.

GameHub / GameHub Lite: the stock GameHub app only offers its built-in driver list — you pick from the list in the game's settings rather than importing a file. GameHub Lite, the community build, has more options and adds new a8xx drivers quickly. Pick from the list; do not try to force a zip into an app that does not offer an import option.

After installing, expect your shader cache to be cleared. Switching drivers wipes shaders in most of these apps, so the first run after a change may stutter while shaders rebuild. That is normal — test the same familiar scene twice before judging the new driver.

How to revert (the step to learn first)

Reverting is the whole point of the per-app design: nothing was flashed, and the system driver was never touched.

  1. Go back to the same driver manager / container graphics-driver setting.
  2. Select System Driver (sometimes labelled "System" or "Default").
  3. Restart the game and test the same scene. If it renders correctly again, the Turnip build was the problem — not your phone, and not the game.

If a driver causes a black screen, do the same thing: switch back to the stock system driver, confirm the game renders correctly again, and only then try a different Turnip revision — often an older, more conservative one. Keep your last known-good driver installed alongside the new one so you can switch back without re-downloading anything, and note which driver version you were on when a game worked — driver versions matter as much as emulator versions when you report a bug.

Deleting the driver package also puts you back on stock, since the app can only load a package it still has. But selecting System Driver is faster, and it keeps the package around in case you want it for a different game.

Troubleshooting

"My custom driver is not showing." The usual causes are an app that does not support custom drivers, an app version too old to include the feature, a failed import, or a package built for a different Adreno generation. Confirm the driver option exists in your app version, re-import the untouched zip, and double-check your exact GPU model.

"The game worked, then broke after a driver change." Revert to System Driver first (above). If it works on stock, the new build regressed that game — try an older Turnip revision, or keep Turnip only for the games that need it. Per-game driver choice, where the app offers it, beats one global driver for everything.

"Static, noise or artefacts after switching." Usually a version mismatch — a build for the wrong generation, or a build that regressed that title. Step back to an older revision, or to stock, and test the same scene.

"It is slower on Turnip." That happens. Turnip may fix a game that renders wrong; the stock driver may run a working game faster. Speed alone is not a reason to keep a driver that renders correctly — pick per game.

"My phone is not Snapdragon." Turnip is Adreno-only. On Mali / Exynos devices, use the GL fallback at low settings in Winlator, or an app like GameHub that handles more GPU families — and do not install Turnip packages hoping they will load.

The checklist

  • Confirm your GPU is Adreno, and note the exact generation (6xx / 7xx / 8xx).
  • Only change drivers to fix a specific game's rendering problem.
  • Get the package from EmuHub's driver section or the official releases page it points to. Do not unzip it.
  • Install it in one emulator, set it active, and test a familiar scene twice (shaders rebuild after a switch).
  • Know how to revert: driver manager > System Driver. Test the revert once, so you trust it before you need it.
  • If a game gets worse, revert first, then try an older revision — never change five settings at once.

Frequently asked questions

Does Turnip require root? No. On supported apps the driver is imported and loaded inside the app's own sandbox, so root is not needed and the Android system driver is left untouched. If an app does not offer a custom driver option, no download will enable it — that capability has to be built into the app itself.

Can Turnip damage my phone? No, in the per-app form this guide covers: the driver runs inside the application's sandbox and the system driver is untouched, so the worst case is a game that renders wrong until you switch back to System Driver. Experimental builds are the least predictable — crashes, artefacts and regressions are common — so they are best for users comfortable testing and reverting quickly.

Can Turnip replace the Android system GPU driver? For normal use, no. The per-app install only affects the app you installed it in. System-wide replacement needs root and a Magisk module, which this guide does not recommend for emulation.

Which Turnip version should I install? The one that matches your exact Adreno GPU and your app version, and that other users with similar hardware report as stable. Start with a widely used build rather than the newest experimental one, test a familiar scene, and only move to another revision if something is actually broken. Driver builds change weekly; check the official releases page for the current stable.

Why do some games need Turnip and others do not? Because the stock Qualcomm driver and Turnip implement Vulkan slightly differently, and each game exercises different parts of it. A game that hits a stock-driver bug needs Turnip; a game that does not will often run just as well — sometimes faster — on stock.

Where do I get drivers? From EmuHub's driver section, which links to the official sources, or directly from the official GitHub releases page for the build you need. EmuHub lists drivers and official download sources; it does not host modified driver packages.

Sources

Found this useful?

Send it to someone setting up the same thing.