AetherSX2 APK

Mid-1.5, the mature stretch

AetherSX2 v1.5-3605 APK Download

Nobody picks 3605 as their first AetherSX2 build, and that is fine — it earns its place as the third thing you try. When 4248 and 3668 both misbehave on one specific game, this is the build that tells you whether a late-1.5 change is responsible or whether the problem is your device.

This archive APK stays available for people who need this exact build. The pages Google should index for version choice are the older versions hub, the current v1.5-4248 download, and the Mali-friendly v1.5-3668 build.

File details

Versionv1.5-3605
ReleasedJuly 2023
File size18 MB: 2 MB smaller than the final v1.5-4248 release
PositionBuild 3 of 12 in our archive, newest first : the release directly after it is v1.5-3668
RequiresAndroid 8.0 or newer (ARM64)
DeveloperTahlreth (development ended 2023)

Download AetherSX2 v1.5-3605

AetherSX2 v1.5-3605 v1.5-3605

Android 8.0+ (ARM64) · 18 MB · No bundled installers, no adware

Download AetherSX2 v1.5-3605
SHA-256:
b22bce0d141eff618456bdec8f5aeee8f43997169d0b66fa320a876c6709e5f2

Always verify the checksum after downloading. We never repackage binaries — this is the unmodified community build.

Should You Use v1.5-3605? Real-World Notes

v1.5-3605 comes from the mature stretch of the 1.5 line. It already includes most of the graphics-core fixes that built up through 2023, while sitting just before the changes some users blame for late-build quirks on specific phones.

Think of it as your troubleshooting build. If 3668 or 4248 misbehaves with a particular game on your device, builds this close together differ mainly in small per-game fixes, so dropping back one step is a quick, legitimate thing to test.

It runs on the same Android 8.0+ requirement as the rest of the line and uses the same BIOS, so switching to it costs you nothing but a reinstall.

What to Know Before Installing v1.5-3605

  • Released in the same month as 3668, so the two are close relatives — expect small differences in specific games rather than a different overall experience.
  • It is ad-free, like everything in the 1.5 line before the late builds.

Recommended Settings for v1.5-3605

RendererVulkan
Resolution1x native while you are diagnosing, then raise it
  • Use this build for A/B testing, not for tuning. Install it, load the exact game that failed on a newer build, and change nothing else — that is the only way the comparison tells you anything.
  • Keep the newer build's settings in mind but re-enter them by hand rather than assuming they carried over.
  • If the game behaves identically here, the problem is very unlikely to be the build, and your time is better spent in per-game settings or on the compatibility database.

Installing v1.5-3605

A standard single-file APK: enable "Install unknown apps" for your browser or file manager, tap the download, and approve the install.

Coming down from a newer release: v1.5-3668 or anything above it: means uninstalling that first, because Android refuses to install an older version over a newer one. Back up your memory cards before you uninstall. Those survive the move between builds; save states do not, so save inside the game rather than relying on a state you made on v1.5-3668.

The rest of setup is the same for every AetherSX2 release, so we publish it once rather than repeating it here: see the illustrated 12-step install and BIOS walkthrough, or go straight to the PS2 BIOS guide if that is the part you are stuck on. Once the app boots, apply our baseline graphics tuning before raising upscaling.

If v1.5-3605 Isn't Right for You

Skip this build if: Anyone installing their first AetherSX2. Start at 4248 or 3668 — come here only when you have a specific game misbehaving on both.

All 12 archived builds, with a comparison table, are on the AetherSX2 older versions page.

Frequently Asked Questions

How much actually differs between v1.5-3605 and v1.5-3668?

Very little in broad terms. They are weeks apart in the same development line, so the difference is a set of specific per-game fixes rather than any change to how the emulator works. That is precisely what makes 3605 useful: because so little else changed, a game that behaves differently between the two points at a real, narrow cause rather than at general instability.

When is it worth dropping back to this build?

When one particular game is broken and everything else runs fine. A device-wide problem — everything stutters, nothing boots, the app crashes on launch — is almost never fixed by moving one build sideways, and your time is better spent on the renderer setting or the BIOS. A single misbehaving title is the case this build exists for.

Will my saves from a newer build work if I move down to 3605?

Memory card saves carry over — those are ordinary files in your storage and are not tied to a build. Save states are the risk: they capture the emulator's internal state and are effectively build-specific, so a state made on 4248 may not load here. Before switching, save inside the game to a memory card rather than relying on a state.