NetherSX2-patch: What the AetherSX2 Continuation Actually Changes

What NetherSX2-patch adds on top of AetherSX2 4248

NetherSX2-patch is a continuation of NetherSX2, which is itself a continuation of AetherSX2. The README credits Anon and EZOnTheEyes for the earlier work and describes this repository as building on it. The stated goals are narrow and concrete: remove the unnecessary ad services bloat left in the APK, fix the RetroAchievements notifications, expose more global settings in the app settings to the user, update the GameDB plus controller support and the widescreen and no-interlace patches, add AetherSX2 and NetherSX2 specific fixes to the GameDB, and resign the APK to remove the Play Protect warning.

That list tells you who this is for. Someone who already ran AetherSX2 3036 or 4248 and wants the ads gone. Someone who wants RetroAchievements to notify correctly instead of silently failing. Someone who wants newer game compatibility data without waiting for an upstream release that is not coming. It is not a new emulator core and it is not a rewrite. The distribution channel is the releases page, and the README points at two builds: the stable NetherSX2-v2.1-4248.apk and the development NetherSX2-v2.2n-4248.apk.

The repository also carries the data side of that work in its top level: GameIndex[converted].yaml, GameIndex[merged].yaml and GameIndex[override].yaml, alongside a gamedb-convert.py script and patches/ and decomp/ directories. So the GameDB updates are not hand-edited binaries. They are YAML sources with a conversion step in front of them, which is the part of this project most worth understanding if you care about reproducibility.

How the GameDB pipeline and the APK build fit together

The layout implies two separate flows. The first is data: GameIndex YAML files in the repository are converted by gamedb-convert.py into the GameDB format the emulator reads at runtime. The three files suggest a split between converted output, a merged view, and an override layer where NetherSX2 specific entries can be layered on top of the upstream PCSX2 data without forking it. That override file is where the README's promise of additional AetherSX2 and NetherSX2 specific fixes to the GameDB would live.

The second flow is the APK: the emulator binary is patched, the ad services are stripped, the package is resigned so Android does not flag it, and the result is published as a release. The README does not describe the patching toolchain or how the APK is rebuilt, so if you need to audit that step, the repository alone will not answer it. The decomp/ directory exists, which suggests some reverse engineering work is part of the process, but nothing in the README documents what is decompiled or why.

What this means practically: the GameDB changes are reviewable in the repository as text, and the binary changes are not. That asymmetry is the honest summary of the project's transparency. If a game's compatibility entry looks wrong to you, you can read the YAML and open an issue. If you want to know exactly which bytecode was removed to kill the ad services, the README is silent.

Installing NetherSX2-patch and getting to a first game

The README's install path depends entirely on what you are coming from, and getting this wrong loses your data. Download the APK from the releases page first. The stable build is named NetherSX2-v2.1-4248.apk and the development build is NetherSX2-v2.2n-4248.apk.

If you were on NetherSX2 1.9a or above, you install over the top and keep your settings. The README marks the backup step as optional here, but it also names the mechanism, so do it anyway: the built in Transfer Data feature has an Export option that writes your bios files, memcards, save states, game settings, covers and texture packs to an external folder.

# Not a shell step. On-device flow from the README:
# 1. Open the existing app, go to Transfer Data, use Export, pick an external folder
# 2. Tap the downloaded APK in Files / File Manager to install over the top
# 3. Launch the app; settings, memcards and covers should still be present

If you were on AetherSX2 or a NetherSX2 older than 1.9a, the sequence is different and the uninstall is mandatory. Back up with Export, uninstall the old app, and when Android asks whether to keep files, do not keep them.

# On-device flow for pre-1.9a users, per the README:
# 1. Transfer Data -> Export your bios, memcards, save states, settings, covers, textures
# 2. Uninstall AetherSX2 / old NetherSX2, choosing NOT to keep app files
# 3. Open File Manager, tap NetherSX2-v2.1-4248.apk, install
# 4. Launch, reach the Game List screen, open Transfer Data -> Import, point at your backup folder
# 5. Redo your Global App Settings by hand

Step 5 is not optional and the README says so directly: global settings are not part of the import, so you will spend time redoing them. After that, the README's performance guidance is to keep the default Optimal/Safe settings, switch the GPU renderer to Vulkan, and set Hardware Download Mode to Disable Readbacks. On the 3668 Classic variant it adds one more: enable Threaded Presentation when using Vulkan.

Classic 3668 or Patched 4248: the choice that actually matters

This is the decision the README spends the most words on, and it is a hardware decision more than a preference one. The Patched 4248 line carries graphical and bug fixes that 3668 does not have. The Classic 3668 line is generally more performant, and the README names the Nascar games as titles that only function well on it. For Mali GPUs or less powerful devices, the recommendation is 3668 for performance. For more powerful devices or Adreno GPUs, 4248.

The wording is careful, and it should be. "Generally more performant" is not a benchmark, and the README does not publish frame rates or a device matrix. If your device sits between the two categories, you are guessing. The practical test is running the specific games you care about on both variants, because the split is per-title as much as per-device: a fix that matters for one game is irrelevant for another, and the performance gap that pushes you to 3668 may not exist in the titles you actually play.

There is also a naming trap. The project name contains "patch" and the README distinguishes a Patched 4248 variant from a Classic 3668 variant, while the repository itself is the patch project that produces both. If you are following a guide that says "use the patched one", check whether it means this repository's 4248 build or something else entirely. The README's own framing is variant, not patch level.

Where NetherSX2-patch is the wrong tool

The clearest limitation is the platform. This is an Android APK. If you want PS2 emulation on a desktop, the README's own credits point at PCSX2, and nothing here helps you. The GameDB YAML may be useful upstream, but the deliverable is an Android package.

The second limitation is the upgrade path for old installs. Going from pre-1.9a means a full uninstall with no files kept, then a re-import of bios, memcards, save states, settings, covers and textures, then manually redoing global app settings. That is a real cost, and the README does not document any rollback if the new build turns out worse for your games. Once you have uninstalled and reinstalled, going back means repeating the whole export and import cycle with the older APK, assuming you still have it.

The third is the ad removal itself. Stripping ad services from a resigned APK is exactly the kind of change that can break a login, a cloud feature or a store integrity check. The README does not list what was removed or what depended on it. If you use a feature that talks to a Google or ad-related service, treat it as untested rather than assume it survived.

Finally, the development builds. 2.2a, 2.2b and 2.2n are labelled Dev Build, and the README offers them next to the stable 2.1 build without describing what changed between them. The release names alone do not tell you whether a dev build is a small GameDB refresh or a larger change.

NetherSX2-patch against AetherSX2 and PCSX2

The honest alternative is the thing this project forked from. If you are on AetherSX2 3036 or 4248 and the ads do not bother you, and you do not need RetroAchievements or online play, staying put costs you nothing and keeps you on an unmodified, un-resigned package. The README's own comparison list is the difference: RetroAchievements, online gaming support, up to date configuration files, no ads for 3036 and 4248 users, NetherSX2 specific game bug fixes, better automatic controller setup, and more control over the emulator through exposed settings. If none of those seven matter to you, the fork has nothing to offer.

PCSX2 is the other real alternative, and the difference is architectural rather than a matter of taste. PCSX2 is the upstream desktop emulator that the README credits as the origin of the work; its GameDB is the data this project converts and overrides. Running PCSX2 on a PC gives you the same compatibility data through a different, actively developed codebase, with none of the APK resigning, none of the ad-service stripping, and no Android storage model to work around. What you give up is portability and the on-device controller handling. What you gain is a build you did not have to trust a third party to repackage.

The third path is the Classic 3668 variant, which the README treats as a distinct option rather than an older version. It is not a fallback for people who failed to install 4248. It is the recommended target for Mali and low-power hardware, and for specific titles.

Maintenance, licensing and what to check before you commit

The repository is not archived, and the last push was on 2026-09-22. The most recent release is 2.2n, tagged as a Net Dev Build, from 2025-12-25, with 2.2b and 2.2a before it in October 2025. The pattern is worth reading plainly: commits land more often than releases, and the newest published build is a development one. If you want the stable line, 2.1 is what the README's Downloads section calls Stable, and it is the APK the install instructions reference.

Upgrade cost is the part people underestimate. On 1.9a and above it is an in-place install plus an optional export. Below 1.9a it is a full teardown and rebuild of your configuration. Neither path is documented with a rollback, so the export is your only safety net and the README treats it as optional in the newer case. Do it regardless.

The licence is Unlicense, which places the work in the public domain. That is permissive in the extreme, and it means the repository imposes no conditions on reuse. It does not, however, resolve the question of the emulator binary being redistributed inside the APK. The README credits PCSX2, EZOnTheEyes, Saramagrean's NetherSX2-cheats, the Android Keystore project by jorfao and SDL_GameControllerDB, which tells you what components are in play, but it does not state the licence of each. If you plan to redistribute or bundle this, check the upstream licences yourself. Nothing here is legal advice.

Editorial conclusion

Adopt NetherSX2-patch if you are on an Adreno or otherwise capable Android device, you want RetroAchievements and online play working, and you accept that your library lives inside the APK's storage. Skip it if you are on a weak Mali device where the README itself points you at Classic 3668, or if you need a desktop PS2 emulator. Before installing, verify which build you are moving from: 1.9a and above updates in place, anything older requires a full uninstall with no files kept, and the README does not document any rollback path if the new build misbehaves.

Frequently asked questions

Official sources

1. License: Unlicense
2. Project website
3. README
4. Releases
5. Trixarian/NetherSX2-patch on GitHub