Azahar 2127.0 Update Adds Per-Game Settings on Android
Azahar 2127.0 adds per-game settings and ADPF performance boosts on Android. What changed, and how to install it.

Azahar 2127.0 has arrived as a release candidate, and it brings the feature the Android build has been missing: per-game settings. The release also adds Android's ADPF performance hints, opens custom GPU drivers to non-Adreno phones, and introduces a new single-file ROM format.
It isn't a stable release yet. The team shipped two candidates on November 6, and the second one fixes a crash the first one caused on older hardware. If you want the short version: test it if you're comfortable sideloading, wait if your current build works.
What changed in the Azahar 2127.0 update
The changelog is long, which is why the team calls this its biggest release. Here are the parts that change what you see on a phone.
Area | What changed |
|---|---|
Per-game settings | Long-press a game in the app list to open settings that apply to that title only |
Performance | ADPF CPU hints, measured at 15% faster on one Mali device |
GPU drivers | Custom driver checks relaxed on non-Adreno hardware |
ROM format | Support for |
Audio and input | Latency cut by one to two frames, time stretching off by default |
Emulation fixes | Shin Megami Tensei IV enemy outlines, Minecraft New 3DS textures, New Super Mario Bros. 2 launch errors |
Two housekeeping notes matter before you update. The license moved from GPLv2+ to GPLv3+, and the shader cache format changed, so the first session after updating rebuilds it. The Azahar update also arrives as a full APK rather than a patch, which is why the download is around 51MB.
Azahar per-game settings are the headline change
Until now, the Android build kept one settings file for everything. Raising the resolution for one game raised it for every game, and switching between OpenGL and Vulkan meant reopening the global menu before each launch.
The new build copies the desktop behaviour. Long-press a title in the application list and a settings screen opens that belongs to that game alone. Resolution scale, renderer, texture filtering and the rest save under that title, so the next launch picks them up without touching the settings any other game relies on.
This is the difference between a usable emulator and a fussy one. A light 2D game can run at 3x resolution on a mid-range phone while a heavier 3D title stays at 1x, and you stop re-tuning the whole app every time you switch carts.
The 15 percent ADPF gain depends on your GPU
Azahar now uses ADPF, the Android performance hint API that tells the operating system when a burst of CPU work is coming. The OS can then hold clocks higher for that window instead of guessing.
The team measured a 15% gain on a device with a Mali GPU and says most Android phones improve. That's a single measurement on one class of hardware, so treat 15% as the best case rather than a promise for your phone. Snapdragon and Exynos owners should expect something smaller, and a phone already throttling from heat won't gain much at all.
One behaviour change comes with it: turbo speed now switches off when a game starts, matching the desktop build. If you relied on launching at 2x speed, you'll need to toggle it manually.
Custom GPU drivers now work past Adreno
Adreno phones have had access to custom Vulkan drivers for a while, mostly through community driver packs. The 2127.0 build relaxes the check that blocked everything else, so Mali and other GPUs can load a driver too.
Nothing here feels finished. A wrong driver can break rendering across the whole app, and the fix is to remove it rather than to change a setting. Install one driver, test one game, and keep the previous driver package around in case you need to roll back.
ROM bundles and the fixes you'll notice
The new .bcxi and .bcci formats pack a base game with its update, DLC or required system data in one file. .bcia does the same for several CIA files at once. Desktop users can build these through Tools → Create ROM Bundle. Android can run a bundle but can't create one yet, so the file has to come from a PC.
The rest of the changelog is a list of long-standing annoyances finally closed. The black box around enemies killed in Shin Megami Tensei IV is gone, thanks to a Vulkan colour blending fix. Minecraft: New Nintendo 3DS Edition renders textures correctly and force-disables the right-eye setting while it runs. New Super Mario Bros. 2 no longer throws fatal errors when launched from the home menu, and StreetPass Mii Plaza SpotPass puzzles stop showing as invalid.
Save states also work again with LLE modules enabled, which matters if you play anything that needs the official system modules. Audio and input latency dropped by one to two frames in the team's testing, and audio time stretching is now off by default, so music plays at its original pitch when the emulator can't hold full speed.
What the release candidate label means for your phone
A release candidate is a build the team considers finished but wants tested before calling it stable. The plan is a seven-day window, extended if something serious turns up, and this time something did: 2127.0-rc2 exists because rc1 could crash immediately on older or lower-spec devices the moment a game launched.
Two warnings come with the build. Back up your Azahar user data folder before installing, because pre-release builds can corrupt config. And expect stutter in the first session after updating, since the shader cache is invalidated and has to rebuild. Performance returns to normal after you've played for a while.
The stable build is still 2126.2 from October 8. It has none of the 2127.0 features, and it's the version Google Play is serving today. APKPure lists the same 2126.2 Google Play build.
How to install Azahar 2127.0 on Android
Check that your phone qualifies first. Azahar needs Android 10 or newer on a 64-bit device, a Snapdragon 835 or better, a GPU with OpenGL ES 3.2 or Vulkan 1.1, and 2GB of RAM with 4GB recommended. The Android build ships in 64-bit only, with arm64 covering phones, so a 32-bit device can't run it at all.
- Open Settings → Apps → Azahar → App info and read the version number at the bottom. If it says 2126.2, you're on the stable build.
- For the stable build, open the Play Store listing named Azahar Emulator and tap Update. The listing was originally created for Lime3DS, so the page history looks older than the app.
- For 2127.0, open the project's GitHub Releases page and download
azahar-android-vanilla-2127.0-rc2.apkor the Google Play variant, both about 51MB. - Open the downloaded file. Android will ask permission to install from that app the first time; allow it, then tap Install.
- Launch Azahar and grant storage access when prompted, then point it at the folder holding your game dumps.
The two Android builds differ in how they reach your files. The vanilla build uses a faster file management method that Google Play doesn't allow. The Google Play build is the one that can update through the store. Both are the same emulator otherwise.
Azahar is one of the few 3DS emulator Android builds you can install straight from Google Play, which makes it the easy route for anyone who doesn't want to sideload. A free Azahar 3DS emulator build outside the store comes from the project's release page instead, and those files carry the project's signature rather than Google's.
An APK install doesn't update itself. You'll have to download each new release by hand, or add the GitHub repo to Obtainium and let it track releases for you.
Should you install the release candidate now?
If your phone is on 2126.2 and everything you play runs fine, wait. The stable 2127.0 should land within a week or two, and it will arrive through Play without a manual download.
Install the candidate if you specifically want per-game settings, if you're on a Mali phone chasing the ADPF gain, or if you're testing a game that one of the fixes targets. Back up the user data folder first, and keep the 2126.2 APK somewhere so a rollback doesn't cost you a save file.
A free open-source 3DS emulator
FAQs
- Is Azahar 2127.0 a stable release?
- No. It's a release candidate, currently 2127.0-rc2 from November 6. The latest stable build is 2126.2 from October 8, and that's what Google Play serves.
- Do per-game settings work on 2126.2?
- No. Per-game settings arrived in the 2127.0 builds. On 2126.2, every game shares one settings file.
- Why does the emulator stutter right after I update?
- The update invalidates the existing shader cache, so it rebuilds as you play. The first session is slower, then performance returns to normal.
- Can I go back to 2126.2 after installing the candidate?
- Only by uninstalling first, because Android won't install an older version over a newer one. That wipes app data, so copy your user data folder somewhere safe before you try.
- Will Azahar run on a 32-bit phone?
- No. The Android build is 64-bit only, and the app needs Android 10 or newer.
What to do next
Back up your user data folder, then decide whether you want the candidate or the stable build. The per-game settings alone justify the update for most people, but the shader rebuild and the rc1 crash are a reminder that release candidates are for testing, not for a phone you rely on.
Back to top