NetherSX2's stable download is 2.1 while its newest tag is a 2.2 development build

The first download link is not the newest build

The downloads section has two entries and they are not two versions of the same thing. The stable entry points at a 2.1 package built on the patched base, and the development entry points at a 2.2 build on the same base. The tag list tells the rest of the story: three 2.2 development builds published in October and December of 2025, the last one named for a networking build. The repository's last commit is dated September 2026, roughly nine months after the newest tag, so there are commits in the tree that no published package contains. The install section opens by telling you to grab the 2.1 package from the stable link, and only the downloads section mentions the development build at all, which is the wrong order of emphasis for anyone who wants the current code.

The warning disappears because the package is signed again

The last item in the project's list of goals is to re-sign the package so the Play Protect warning goes away, and that one line explains the whole distribution model. The build takes an existing application package, modifies it, and signs it with a different key, which is why it no longer matches the signature the operating system expects from the original publisher and why the platform can no longer vouch for it. The credits name the pieces: a third party project for generating the Android keystore used for signing, the upstream emulator this one continues, a controller mapping database, a separate project for game cheats, and the two people whose earlier work this continues. Nothing on the page offers a checksum for either download or any step for verifying what arrived, which is the honest gap in an otherwise unusually careful set of instructions.

One upgrade step deletes your saves, and the page says so

The installation section splits into two paths depending on what you are coming from, and the difference matters more than it first appears. If you are on 1.9a or later, you install the new package over the old one and your settings survive. If you are on anything older, or on the original project the page calls by its other name, the instructions are five steps long and the third of them is an uninstall with an explicit warning not to keep any files if the system offers to. That warning is the whole risk in the document: the data being removed is your bios images, memory cards, save states, game settings, covers and texture packs. The backup step above it uses the emulator's own transfer function, which exports those same items to a folder you choose, and step five is redoing your global settings by hand because they are not part of that export.

Two variants named after the base they were built from

The frequently asked questions split the project into a classic variant and a patched variant, and the names are version numbers of the base this one continues: one is 3668 and the other is 4248. The guidance is about hardware rather than features. The classic base is described as more performant, with some titles said to work well only on it, and it is the recommendation for devices with Mali graphics or less power. The patched base carries the graphical and bug fixes that only exist there, and it is the recommendation for more powerful devices or ones with Adreno graphics. The performance section then splits the difference with a setting advice that is the same for both: keep the default profile, switch the renderer to Vulkan, and turn readbacks off in the hardware download mode.

The game database is three bracketed files and a conversion script

Two of the project's goals are about the game database: updating it, and adding fixes for specific devices on top of it. The repository root shows how that work is actually organised. There are three files with the same base name in square brackets, one marked as converted, one as merged and one as an override, and a Python script whose name says it converts the database. So the pipeline is read something, convert it, merge the result, then apply overrides on top, which is a sensible three stage arrangement for a database that has to merge an upstream one with local patches. The square brackets in the names are the awkward part, since they need escaping in most shells and in most configuration files that want to reference them.

The project's homepage is a chat invite

The project homepage is recorded as a chat invite, which is unusual and tells you something about how the project is run. There is no separate site, no documentation domain and no issue template visible in the tree, so the conversation with the people who maintain it is the documentation. The readme itself links nothing outside the repository except the two people it credits and the upstream projects it depends on, and it credits those people by name and by channel rather than by document. For a project whose whole contribution model appears to be a chat server, that is a coherent choice, and it is also a single point of failure: the instructions, the release announcements and the support all live in one place with no written record.

The advertising removal is scoped to two base versions

One line in the frequently asked questions is easy to skim and says more about the project than the rest of the list does. The claim of no advertising carries a parenthetical limiting it to users of two specific base versions of the project it continues. Elsewhere on the page the removal of the advertising services left in the package is listed as a goal without qualification, so the two statements do not line up: the goal is general, the claim is scoped. The parenthetical is most likely there because the advertising code only exists in those bases and the others never had it, which would make the honest phrasing a statement about which builds are affected rather than a promise about all of them. Either way, a reader on an older base has to work out for themselves whether anything was removed, and the page does not help them check.

A public domain dedication with an inherited software lineage

The licence is the Unlicense, which is a dedication of the work to the public domain rather than a set of permissions anyone holds, and it covers the material in this repository. What it cannot cover is the emulator this project continues, the controller mapping database it uses and the game data it reads, none of which are in this tree and none of which become free because a patch file next to them was dedicated. The credits section is where the distinction is made, listing five separate projects and two individuals, and one of the five is a cheats repository that this project does not vendor. It is the tidiest part of the documentation and also the part that most affects what a reader can actually do with the result.

Editorial conclusion

Use this project if you already run the emulator it continues and you want the advertising services gone, the achievement notifications fixed and more settings exposed, because those are the changes it lists and the rest is inherited. Three things to know before you install anything. The warning about an unrecognised developer is gone because the package is signed with a different key, which is a re-signing, not a verification, so nothing on the page offers a checksum or a way to confirm what you downloaded. The stable link and the newest tag are two different builds, so decide which one you are installing rather than assuming the page's first link is current. And the upgrade path from an older install deletes your data at one step by design, so take the export first and keep it somewhere other than the phone.

Frequently asked questions

Official sources

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