ARMSX2 vs NetherSX2: the best PS2 emulator and settings for Android handhelds

ARMSX2 or NetherSX2 for PS2 games on your Android handheld? Which to pick for Snapdragon or Mali, the settings that matter, Turnip drivers and quick fixes.

"Should I use NetherSX2 or ARMSX2?" is one of the most-asked questions on r/EmulationOnAndroid right now. Short answer for October 2026: make ARMSX2 your main PS2 emulator and keep NetherSX2 installed for the few games that still run better on it. ARMSX2 is open source and updated almost daily. NetherSX2 is a polished community continuation of AetherSX2 that still wins on some games and weaker chips. Below is how they differ, which one suits your handheld, and the handful of settings that actually matter.

The two emulators in one minute

Both need a BIOS dumped from a PS2 you own, and your own game discs ripped to ISO or CHD. Neither app includes them, and Overclocked doesn't link to them.

Which one should you use on your handheld?

• Snapdragon 8 Gen 2 (Odin 2, Odin 2 Portal, Retroid Pocket 6, AYN Thor): ARMSX2 first. Community testing on 8 Gen 2 handhelds found nearly every game tested ran at full speed at 2.5x resolution on a 1080p screen (Skalablog's ARMSX2 guide).
• Snapdragon 8 Elite / Dragonwing Q8 (AYN Odin 3, and the upcoming Odin 3 Portal): ARMSX2. These chips brute-force almost the whole PS2 library; the main thing to get right is the GPU driver (see below).
• Snapdragon 865 (Retroid Pocket 5, Retroid Pocket Mini, Thor Lite): ARMSX2 with its own ARMSX2 Turnip driver, which the project recommends for Adreno 650 to 699 (Snapdragon 865, 870 and 888). Keep NetherSX2 for heavy games: in the same community testing, Jak 3's shadows and Shadow of the Colossus ran better on NetherSX2 Classic on an 865.
• MediaTek and Unisoc chips with Mali GPUs (RG557, RG477M, RG556): try both. NetherSX2's maintainer recommends its Classic (3668) build for Mali and less powerful devices, while some Dimensity 8300 owners report ARMSX2 now runs very well. Custom Turnip drivers don't apply to Mali GPUs.
• PC handhelds (Steam Deck, ROG Xbox Ally, Legion Go): neither. Use desktop PCSX2, the project ARMSX2 is based on. See our PC handhelds guide.

Set up ARMSX2 in five steps

1. Install it. Google Play is simplest. On GitHub, the 2.8.4 release has separate APKs named for Android versions (a15, a13, a11) plus a "legacy" build for older ARMv8.0 chips; pick the one matching your Android version (Settings → About). ARMSX2 needs Android 8.0 or newer on a 64-bit ARM device, and the project recommends 6 GB of RAM or more.
2. Choose a data folder. Internal storage is simplest. Android deletes app-private data when you uninstall, so pick an SD card or custom folder if you want saves to survive a reinstall.
3. Import your BIOS. Point BIOS Location at the folder with your own PS2 BIOS dump. ARMSX2 checks each file and lists the valid ones.
4. Add your games. Point ROM Location at your game folder (ISO, CHD, BIN, IMG, MDF and GZ are supported). CHD files take less space than ISO.
5. Boot one game at default settings and check video, audio, controls and memory-card saving before you tweak anything. That's the order ARMSX2's own setup guide recommends.

The settings that actually matter

Renderer: Vulkan on Snapdragon

Leave the renderer on Auto, or pick Vulkan on Snapdragon (Adreno) handhelds. Vulkan is faster and is the only renderer that can use custom GPU drivers. OpenGL is the compatibility fallback for games that render wrong on Vulkan, and the software renderer is the most accurate but stuck at native resolution.

GPU driver: the biggest speed swing

• Adreno 650 to 699 (Snapdragon 865/870/888): pick ARMSX2 Turnip from the in-app driver list. According to the ARMSX2 2.7.1 notes, it makes frame readbacks, which PS2 games do constantly, 2 to 3 times faster where they're the bottleneck (Splashdown on a Snapdragon 865 went from 54.7 ms to 22.4 ms a frame). In community testing, Black on an 865 went from half speed on the system driver to full speed with Turnip.
• Adreno 730 and newer (8 Gen 2, 8 Elite): ARMSX2 says any Turnip build makes Stuntman and WRC 3 run 17 to 21% faster. Try the stock driver and a recent Turnip and keep whichever is smoother. On the Odin 3's Adreno 830, only use builds labelled a8xx / Gen8.
• Mali: stay on the system driver.

Not sure which GPU you have? Pick your device on the GPU driver hub or read Turnip vs Qualcomm drivers, explained.

Resolution: start native, then raise it

ARMSX2's docs say to start at native resolution and only go higher once a game runs correctly. As a rough guide from community testing: 2x on a Snapdragon 865 and 2.5x on an 8 Gen 2 with a 1080p screen. 8 Elite handhelds have more headroom; raise it one step at a time. If a game slows down, drop the resolution first.

Patches: widescreen and no-interlacing

Turn on the widescreen and no-interlacing patches in a game's settings. Widescreen fills a 16:9 handheld screen without stretching (in games that have a patch) and no-interlacing removes the shimmer many PS2 games have. Apply them per game, not globally.

Per-game fixes, not global ones

Keep global settings at defaults and change things in each game's own settings. If a game is slow, try the Fast or Low-End speed-hack profiles in that game only. In community testing, Gran Turismo 4 reached full speed on an 865 once readbacks were disabled (Hardware Download Mode → Disable Readbacks), but that setting can break effects in other games.

Handheld comfort

Turn off the on-screen controls if your handheld has physical buttons, and bind hotkeys for save state, load state and fast forward. If your handheld has analog triggers, ARMSX2 2.7.1 added analog pressure for L2 and R2 (Pad → Button mapping, off by default), which games such as Gran Turismo 4 use for throttle and brake.

Using NetherSX2 alongside it

• Install it: download the ready-made APK from the NetherSX2-patch GitHub releases page. Since v2.0 you no longer have to patch your own AetherSX2 APK. Android may show a Play Protect warning because the APK is signed with test keys. You still need your own PS2 BIOS dumped from a console you own.
• Which build: the maintainer recommends 4248 (the standard patched build) for Adreno and more powerful devices, and Classic (3668) for Mali or less powerful devices. Classic is usually faster and some games (the NASCAR titles, for example) only work well on it, but it lacks fixes that 4248 has.
• Best performance settings: per the NetherSX2-patch README, start from the default Optimal/Safe settings, use the Vulkan renderer and set Hardware Download Mode to Disable Readbacks. On Classic (3668) with Vulkan, also turn on Threaded Presentation.
• Moving between them: NetherSX2 and ARMSX2 keep separate folders, so copy your BIOS and point both at the same game folder. Memory cards and save states aren't shared automatically.

Quick fixes

• Game is slow or stutters: lower the resolution, switch the GPU driver (Snapdragon), then try the game in the other emulator.
• Black screen or broken graphics: try OpenGL for that game, or turn off a custom driver. Broken shadows in Jak 3 on an 865 are a known case where NetherSX2 Classic does better.
• Games list is empty: reopen Setup, confirm Android still allows access to your game folder, then rescan.
• Handheld runs hot: some Snapdragon 865 owners report ARMSX2 runs warmer than NetherSX2. Lower the resolution, cap the CPU with ClusterTune or see heat and battery fixes.
• Want a console-style menu: launch ARMSX2 or NetherSX2 from ES-DE or Daijishō.

Found settings that work for a game? Submit a report with the emulator, driver and resolution so other owners of your handheld can copy them.

Compat reports: NetherSX2 → Snapdragon 865 reports → 8 Gen 2 reports →

Sources: ARMSX2 on GitHub (README, 2.8.4 release), ARMSX2 system requirements and setup docs, ARMSX2 2.7.1 notes, NetherSX2-patch README, Skalablog ARMSX2 guide (community testing on 865 and 8 Gen 2), r/EmulationOnAndroid owner threads (September 2026). Not yet tested by Overclocked on every device listed.

FAQ

More guides

Related on Overclocked