Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
2026-11-16 · Setup guide
Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
ARMSX2 is our pick for PS2 emulation on Android handhelds in 2026. It is free, open source and built on current PCSX2 code, and it ships a new release every week or two. This guide takes you from install to your first game. It also covers the parts other guides skip: what the Play Store version leaves out, which of the four APKs your handheld needs, and which graphics driver ARMSX2 will offer you during setup.
It is written against ARMSX2 2.9.4, released on 15 November 2026.
Everything here assumes you are playing games you already own. ARMSX2 needs a BIOS file dumped from your own PS2. We do not link to BIOS files or games.
The Short Version
- Install it from the Play Store if you want the simplest route. The official site links that listing, and updates arrive on their own.
- Take the APK from the official site, armsx2.net, if you want frame generation or want to keep app data in a folder of your choice. Both are missing from the Play build.
- The setup wizard does most of the work. It asks where to keep app data, then for your BIOS folder, your games folder, and whether ARMSX2 should tune performance for you.
- Accept the driver it offers. On Adreno 6xx and 7xx handhelds that is ARMSX2's own Turnip build. On most Mali handhelds it is MaliSX2. Both are tuned for this emulator.
- Do not leave app data on Internal if you care about your saves. ARMSX2 says plainly that its internal folder is wiped on uninstall.
- Start at native resolution. Raise it once a game runs well.
Step 1: Play Store or APK?
ARMSX2 comes two ways, and they are not quite the same app. The Play build is made to fit Google's store rules, so three things are left out on purpose.
| Play Store | APK from armsx2.net | |
|---|---|---|
| Updates | Through the Play Store | Built in updater |
| Frame generation | Not included | Included |
| Where app data can live | Internal or SD card | Internal, SD card or any folder you pick |
| Installs as | Its own app | Its own app |
Frame generation uses Lossless Scaling, a paid Windows app. You supply its Lossless.dll file yourself. ARMSX2 says it needs the Vulkan renderer and "an Adreno 7xx or newer GPU, or an Adreno 6xx running a Turnip driver". So it is a Snapdragon feature. Mali handhelds cannot use it in either build.
Our advice: take the Play Store version unless you want frame generation. The two builds install as separate apps, so you can try both, but they do not share saves or settings. Pick one and stick with it.
Which APK?
If you go the APK route, the official site offers four Android builds. They are named after the oldest Android version each one runs on.
| Build | Use it on |
|---|---|
| A15 | Android 15 or newer, such as the AYN Odin 3 |
| A13 | Android 13 or 14, which covers most current Retroid, AYN and Anbernic Android handhelds |
| A11 | Android 11 or 12 |
| Legacy | Android 8 to 10, or a chip without the newer ARM instructions the others use, such as the Snapdragon 845 or Exynos 850 |
If you pick a build your processor cannot run, ARMSX2 2.9.4 tells you so instead of crashing. Check your Android version in the system settings under About before you download.
There is also a nightly build for testers. It installs as a separate app called ARMSX2 Nightly, so it will not touch your main install. The project marks nightlies as unsigned community test builds, so most people should skip them.
Step 2: The Setup Wizard
The first time you open ARMSX2, a setup wizard runs. These are its pages, in order.
1. Welcome. Tap Next.
2. App Data Folder. This is where ARMSX2 keeps memory cards, save states, settings and shader data. Your games are added separately. You get these choices:
- Internal. App private storage. ARMSX2's own description says it is "wiped on uninstall". Your memory cards go with it.
- SD Card. A folder on your microSD card. This is what we would pick on a handheld.
- Custom folder. APK only. Any folder you like, after you grant all files access.
Moving app data later takes effect after a restart, and ARMSX2 asks you to restart when it does.
3. BIOS Location. Tap Pick BIOS Folder and choose the folder that holds your PS2 BIOS. ARMSX2 adds every BIOS it finds there, with any matching .mec and .nvm files. If a folder holds several, you pick one now and can switch later. A common mistake has its own error message now: the ps1_rom.bin file from a PS3 is a PS1 BIOS, and it will not run PS2 games.
4. ROM Location. Tap Pick ROMs Folder and choose where your PS2 games live. ARMSX2 reads ISO, CHD, BIN, IMG, MDF and GZ files, and you can include subfolders or add more than one folder.
5. Performance. This page asks whether ARMSX2 should tune performance for you. It is called Automatic Performance Tuning. When a game cannot hold full speed, ARMSX2 "tries lighter settings for that game one at a time and keeps the ones that help". It saves the result per game and you can reset it per game. On a Snapdragon 865 or a Mali handheld we would switch it on. On a Snapdragon 8 Gen 2 or newer, most games will never trigger it.
6. GPU driver. This page appears only if ARMSX2 has its own driver for your GPU. Step 3 explains what you will see.
7. Recommended Settings, then Apply & Finish. The last page offers starting values for the renderer, internal resolution, aspect ratio, widescreen patches, deinterlacing and anti blur. All of them can be changed later. Leave widescreen patches off for now (Step 4 explains why).
To run the wizard again, open the menu in the games list and pick Setup / Change Folders.
Step 3: The GPU Driver It Offers You
ARMSX2's setup page describes it like this: "ARMSX2 builds its own graphics driver for your GPU. It is the driver the emulator is tuned for." What you are offered depends on your graphics chip.
| Your GPU | Handhelds | What setup offers |
|---|---|---|
| Adreno 6xx and 7xx | Retroid Pocket 6, Pocket 5, Pocket Flip 2, AYN Thor, Odin 2 Portal Pro | ARMSX2's own Turnip build |
| Adreno A12 | Anbernic RG 55G1 | ARMSX2's own Turnip build. ARMSX2 identifies this GPU as an Adreno 613 |
| Adreno 830 | AYN Odin 3 | Nothing. The system driver stays |
| Mali G57 to G78, G615, G715 and others | Anbernic RG557, RG477M, RG477V, RG556, RG476H | MaliSX2 |
ARMSX2's own Turnip is Mesa's open source Adreno driver with ARMSX2's patches applied. Of all the Turnip builds out there, this is the one written with this emulator in mind. On Adreno 6xx GPUs from the 650 up, which means the Retroid Pocket 5 family, the emulator recognises its own build and uses a rendering path it keeps for that build.
MaliSX2 is an open source Mali driver written for ARMSX2, and its target device is the Anbernic RG477V. ARMSX2 warns that on some Mali devices it needs a newer kernel driver than the device has. If yours is too old, ARMSX2 quietly keeps using the system driver.
The Odin 3 gets no offer because ARMSX2 does not build its driver for Adreno 8xx GPUs. Start on the system driver. If a game draws wrongly, the GPU Driver list in Settings has community Turnip builds for the Adreno 830 to try.
You can skip this page. The setup page itself says the same driver is in Settings, under GPU Driver, where you can also import a driver ZIP or go back to the system driver. If a game looks corrupt after a driver change, use Clear Shader Cache in the renderer settings and start it again.
For the wider picture on custom drivers, see our Turnip and Mali drivers guide.
Step 4: The Settings That Matter on a Handheld
Most games run well on what the wizard sets. When one does not, these are the settings worth knowing. Most can be set per game.
- Upscale. This is the internal resolution. Start at native. Raise it to 2x once a game runs well. There is also a custom percentage: ARMSX2's own example is 107%, which renders at roughly true 480p height, sharper than native without the cost of 2x.
- Display Resolution (HW scaler). A handheld specific setting. It lowers the resolution sent to the screen "to significantly decrease device heat and battery drain", separately from the internal resolution. Screen is full quality. 2x PS2 is the balanced step and 1x PS2 the battery saver.
- Sustained Performance. Holds a steady clock for long sessions, which ARMSX2 says reduces "mid-session throttling, heat and battery drain on handhelds". The trade is a lower peak, so the most demanding games may run a little slower. Try it on a fanless handheld.
- Display upscaler. FSR 1 or SGSR. ARMSX2 describes SGSR, Qualcomm's upscaler, as "cheaper than FSR 1". Use it on a Snapdragon handheld.
- Auto-Apply Widescreen (16:9) Patches. It patches every game that has a widescreen patch, all at once. ARMSX2 warns that some games come out "stretched, cropped, or missing on-screen text". Leave it off until you have checked your favourite games with it on.
- Screen resolution override. Fixes 16:10 or misreported screens that squash 16:9 games and widescreen patches.
- Low Latency Mode. Off by default. Worth trying if controls feel laggy. Turn it back off if the frame pacing suffers.
- Frame Skip. For weak devices only. It draws fewer frames while the game runs at full speed underneath.
Shaders now survive updates. Since 2.9.4, updating ARMSX2 keeps every game's shader cache. The first start after that update rebuilds them once. After that, games start with their shaders ready.
Automatic Performance Tuning shows its work. If you switched it on in setup and a game looks different, ARMSX2 lists what it changed for that game. You can reset it for that game, and settings you changed yourself are left alone.
Step 5: Back Up Before You Need To
ARMSX2 has a Back up app data option that saves one ZIP file. It holds save states, memory cards, artwork, per game settings, controller profiles, patches and all settings. Games and the BIOS are not included. Restore app data loads it back and restarts the app.
Make a backup before you uninstall, switch between the Play and APK builds, or reset the handheld. If your app data lives on Internal, an uninstall without a backup loses your memory cards.
Frame Generation (APK Only)
The APK build can add generated frames between real ones, using the shaders from Lossless Scaling. ARMSX2 does not include those shaders. You must own Lossless Scaling and choose its Lossless.dll yourself in the frame generation settings.
The requirements, in ARMSX2's own words: "the Vulkan renderer and an Adreno 7xx or newer GPU, or an Adreno 6xx running a Turnip driver. On anything else it stays off."
The options include how many frames to generate, a lighter Performance Mode, half precision shaders that phone GPUs often run faster, and Adaptive frame pacing. That last one varies the number of generated frames to hold your display's refresh rate. ARMSX2 says it helps most in games that swing between 60 and 30 frames per second.
Generated frames look smoother but do not make a game respond faster. Treat this as a fix for 30 frames per second games, not as a speed boost.
Playing With a Friend: Remote Play
ARMSX2 includes a Remote play feature that lets a friend play your game as player 2. Your game streams to their device and they play with their own controller. It works on the same Wi-Fi, or online with a code that lasts 10 minutes. The friend does not need a copy of the game, because only the stream runs on their device.
To host, start a game, open the in game menu, tap Friends, then Host on this Wi-Fi or Invite online.
ARMSX2 on Linux Handhelds
ARMSX2 also publishes Linux builds for ARM devices. The stable release includes two AppImages. The 4K page one is for most systems. The 16K page one is for Apple Silicon kernels such as Asahi Linux.
The nightly notes add guidance for handhelds. On ROCKNIX and Batocera, use the regular AppImage, because both run a compositor. Nightlies also include a package for bare display handhelds and a RetroArch core. Neither is in the stable release yet. On a Linux handheld with a Mali GPU, ARMSX2's Linux version can offer MaliSX2 too, as our Turnip and Mali drivers guide explains.
Known Problems, and What to Do About Them
"A PS1 BIOS". You picked a PS1 BIOS, often the ps1_rom.bin file from a PS3. ARMSX2 needs a PS2 BIOS from your own console.
The app crashes at launch, or warns about your processor. You installed an A11, A13 or A15 build on a chip without the newer ARM instructions. Install the Legacy build.
A game draws wrongly after a driver change. Clear the shader cache in the renderer settings and start the game again. If it is still wrong, go back to the system driver for that game.
It is slow right after an update. Expected once after 2.9.4, while the shader cache rebuilds. From 2.9.4 on, later updates keep the cache.
The handheld gets hot. Try Display Resolution at 2x PS2, then Sustained Performance. Both are aimed at exactly this.
A game you love still struggles. Some PS2 games are hard on every handheld. Our most demanding PS2 games page lists them, with the lightest games too.
ARMSX2 or NetherSX2?
ARMSX2 is the one we recommend in 2026. NetherSX2 still works, but its last release was in December 2025, and it is a patch on the final AetherSX2 build. ARMSX2 is built on current PCSX2 code and is updated every week or two. Our PS2 emulators guide covers the full comparison. If you already have AetherSX2 set up, our AetherSX2 guide still explains its settings.
If you are choosing a handheld for PS2, our best handhelds for PS2 emulation guide ranks them. The Retroid Pocket 6 is the one we point most people to.
Frequently Asked Questions
Is ARMSX2 on the Play Store?
Yes. ARMSX2's official site links the Play Store listing, which follows the same releases. The Play build leaves out frame generation, the built in updater and the option to keep app data in a custom folder. The APK from armsx2.net has all three.
Which ARMSX2 APK should I download?
The newest one your Android version allows. A15 for Android 15 or newer, A13 for Android 13 or 14, A11 for Android 11 or 12. Use Legacy on Android 8 to 10, or on chips such as the Snapdragon 845 and Exynos 850 that lack the newer ARM instructions.
Does ARMSX2 need a BIOS?
Yes. It needs a PS2 BIOS dumped from your own console. During setup you point it at a folder and it adds every BIOS it finds there. A PS1 BIOS, such as the ps1_rom.bin file from a PS3, will not work.
Which GPU driver should I use with ARMSX2?
The one its setup offers. On Adreno 6xx and 7xx handhelds that is ARMSX2's own Turnip build, and on most Mali handhelds it is MaliSX2. On the AYN Odin 3's Adreno 830 setup offers nothing, so start on the system driver.
Does ARMSX2 work on Mali or Anbernic handhelds?
Yes. ARMSX2 offers MaliSX2, an open source Mali driver written for it, on most Mali GPUs from the G31 to the G715. Its 2.6.9 release was benchmarked on the Dimensity 8300 used in the Anbernic RG557 and RG477M. Frame generation is Adreno only.
Does ARMSX2 have frame generation?
The APK build from armsx2.net does. The Play Store build does not. It needs the Vulkan renderer, an Adreno 7xx or newer GPU (or a 6xx running Turnip), and your own copy of Lossless Scaling's Lossless.dll.
Will I lose my saves if I uninstall ARMSX2?
If your app data is on Internal storage, yes. ARMSX2 says its internal folder is wiped on uninstall. Choose the SD card for app data during setup, or use Back up app data before you uninstall.
Is ARMSX2 better than NetherSX2?
For most people in 2026, yes. ARMSX2 is built on current PCSX2 code and releases every week or two. NetherSX2's last release was in December 2025. NetherSX2 still works if you already use it.
Related Guides
- PS2 emulators for Android and handhelds
- Turnip and Mali drivers guide
- Obtainium setup guide, for keeping APK emulators updated
- The best emulator for every system on Android handhelds
- Best handhelds for PS2 emulation
- The most demanding PS2 games, and the lightest
- ARMSX2 2.6.9 was tuned for your handheld
- AetherSX2 setup guide
- Retroid Pocket 6 setup guide
- Retroid Pocket 5 setup guide
- AYN Odin 3 setup guide
Written 16 November 2026 against ARMSX2 2.9.4. Features, menus and setup steps come from the project's release notes and its source code, read the same day. We have not run ARMSX2 on any handheld and publish no performance figures of our own.

