How to Set Up NetherSX2 on Android — Complete PS2 Emulator Guide 2026

AetherSX2 vs NetherSX2 — Which to Use

AetherSX2 was the first serious PS2 emulator for Android. Its developer abandoned the project in early 2023 due to harassment, leaving the final build (r3732) on the Play Store briefly before removing it. NetherSX2 is an open-source community fork of that r3732 build — it fixes bugs, keeps the app working on newer Android versions, and is actively maintained. Use NetherSX2. Old AetherSX2 APKs floating around the internet may be outdated or modified with adware.

Hardware Requirements

• Minimum — most 2D and low-polygon 3D games: Snapdragon 855 / Dimensity 1000 / Exynos 990 (2019–2020 flagship class); 6 GB RAM; Android 8.0+ (Android 11+ recommended)
• Recommended — smooth on most games at 2× resolution: Snapdragon 8 Gen 1 / Dimensity 9000 or newer; 8 GB RAM; Android 11+
• Not suitable: low-end / mid-range phones (Snapdragon 680/695, Helio G-series). PS2 emulation will run below playable speed on nearly every title on these chips. Use PCSX2 on PC instead.

NetherSX2 uses Vulkan for best performance. Snapdragon 855+ and Dimensity 9000+ devices support Vulkan 1.1+. Mali (Samsung Exynos) GPUs may work better on OpenGL due to driver quirks — test both if you see visual glitches.

Install NetherSX2 APK

1. On your Android device, open a browser and search "NetherSX2 GitHub" — the repo is under the Trixarian account. Go to the Releases page.
2. Download the latest APK (named like NetherSX2-r3732-vX.X.X.apk).
3. Open the downloaded file. Android prompts you to allow installation from this source — tap Settings → Allow from this source for your browser, then return and install.
4. If you see a Play Protect warning, tap Install anyway — this is expected for sideloaded apps.
5. After installation, you can re-disable "Install unknown apps" for your browser.

PS2 BIOS Setup

NetherSX2 requires a PS2 BIOS file dumped from a real PS2 console. The most compatible file is scph5501.bin (US NTSC). PAL users use scph5502.bin; JP users use scph5500.bin. Having all three is fine.

• Android 10 and earlier: place the .bin file in Internal Storage/Documents/NetherSX2/bios/
• Android 11+ (scoped storage): NetherSX2 prompts you on first launch to select a data folder. Choose a folder you control (e.g. Documents/NetherSX2/). The emulator creates a bios/ subfolder — place your BIOS file there.

If the emulator can't find the BIOS: Settings → BIOS → Change BIOS Directory → point to the folder containing the .bin file.

For context on BIOS legality and what these files are, see Which emulators need a BIOS and where the files go.

Settings → Graphics for the core options:

Renderer

• Vulkan — best performance and accuracy on Snapdragon 8xx and Dimensity 9000+ devices. Try this first.
• OpenGL (ES) — better compatibility on Mali-based devices (Samsung Exynos) and older phones. If Vulkan causes visual glitches or crashes on the title screen, switch here.
• Software — accurate but very slow. Only for testing specific games that break on the hardware renderer.

Internal Resolution

• 1× Native (640×448) — lowest quality, highest performance. For weak devices or troubleshooting.
• 2× (1280×896) — sweet spot for Snapdragon 855+ phones. Clean pixels, manageable performance cost. Recommended for most users.
• 4× (2560×1792) — for Snapdragon 8 Gen 1+ flagships. Most PS2 games look excellent at this resolution.
• Auto — scales to your screen resolution; can be unexpectedly demanding on large-screen tablets.

Other graphics options:

• Texture Filtering: Bilinear (PS2) mimics original hardware filtering — recommended. Nearest is sharper for pixel-art titles.
• Anisotropic Filtering: 4× or 8× on mid-range+ devices — sharpens angled-surface textures at low GPU cost.
• Hardware Mipmapping: On — reduces texture shimmer in motion on most 3D games.
• Widescreen Patches: enable for 16:9 gameplay instead of 4:3. NetherSX2 includes built-in widescreen hacks for hundreds of games. For unsupported titles it may cause HUD stretching — disable per-game if so.

Supported game formats:

• .iso — standard disc image, works universally
• .chd (CHD v5) — recommended; 30–50% smaller than ISO, full accuracy. Convert on PC with: chdman createcd -i game.iso -o game.chd
• .cso / .zso — older compressed formats; work but CHD is preferred

Controller Setup

Physical controller (recommended for serious play): connect a Bluetooth controller before launching NetherSX2. Xbox Wireless, DualSense, DualShock 4, 8BitDo controllers, and Razer Kishi are detected automatically. NetherSX2 maps them to PS2 buttons without manual configuration in most cases.

Wired controllers: plug in via USB-C OTG adapter. Detected the same as Bluetooth.

Remap buttons: Settings → Controllers → Port 1 → tap any button to rebind.

On-screen virtual pad: functional but limited for fast-paced 3D games. Adjust layout and opacity via Settings → Controllers → Touchscreen Controller → drag buttons to preferred positions.

Analog stick dead zone: if a character walks by itself, increase the dead zone at Settings → Controllers → Analog Settings → Dead Zone.

Memory Card and Saves

Memory cards (PS2's native save system) are managed automatically. NetherSX2 creates virtual Mcd001.ps2 and Mcd002.ps2 in the data directory — they behave exactly like real memory cards. Saves write in-game automatically. Do not force-close the app mid-game to avoid memory card corruption.

Save states: swipe down from the top of the screen during gameplay to open the quick menu → Save State / Load State. Note: save states are emulator-specific and depend on current settings. Changing the renderer may invalidate them. Use in-game saves (memory card) as the primary backup.

Auto-save interval: Settings → System → Auto Save State Interval → set to 2 minutes for safety while dialing in settings.

Per-game memory cards: Settings → Memory Cards → "separate memory card per game" — cleaner when managing many titles (avoids a full shared card).

Performance Settings

• EE Cycle Rate: leave at 0 (100%, default). Setting to -1 or -2 improves performance on weak phones but can cause slowdowns or crashes in some games. Try -1 only if you need more headroom.
• EE Cycle Skip: leave at 0. Enabling this hurts accuracy.
• Enable Fast Boot: On — skips the PS2 startup animation. Safe for almost all games.
• Frame Limiter: On (default) — keeps games at their native frame rate and prevents the phone from running flat-out when the emulator gets ahead of real-time. Turn off only for benchmarking.
• Thermal throttling: PS2 emulation drains battery and generates heat quickly. A demanding game (God of War II, Shadow of the Colossus) can trigger throttling after 15–20 minutes. Use a clip-on fan/cooling pad for long sessions. Enable any "Game Mode" or "High Performance" power plan on your phone before launching.

Performance drop fix hierarchy: (1) drop Internal Resolution from 2× to native 1×; (2) try OpenGL instead of Vulkan; (3) set EE Cycle Rate to -1.

Common Issues

• "BIOS not found" on launch: BIOS .bin file is in the wrong directory — move it to the folder shown in Settings → BIOS directory, or re-select the folder
• Black screen after BIOS boot: renderer incompatibility or wrong game format — switch Vulkan → OpenGL (or vice versa); confirm game file is not corrupted
• Game runs at 20–30% speed: phone too weak for this title — drop to 1× resolution, set EE Cycle Rate to -1
• Controller not detected: Bluetooth not paired before launch — pair controller in Android settings first, then open NetherSX2
• Screen tearing / judder: VSync off — Settings → Graphics → Enable VSync → On
• HUD looks stretched: widescreen patch on for unsupported game — disable widescreen patches for this title
• Memory card full / can't save: Settings → Memory Cards → "separate memory card per game"
• Audio crackling: buffer size too small — Settings → Audio → Backend Buffer Size → increase to 100ms or higher
• App crashes on launch: incompatible Android version or Vulkan driver bug — try OpenGL renderer; update phone to latest OS; reinstall APK
• Save state won't load: state made with different settings or renderer — save states are NOT portable across renderer changes; use in-game memory card saves for permanence

For performance that doesn't match your hardware expectations, see → Emulator running slow despite strong hardware (thermal and CPU governor patterns that also apply on Android).