Why Is AetherSX2 APK Not Working?
Most AetherSX2 problems trace back to one of five causes: a missing BIOS, a storage permission, an install mismatch, a renderer issue, or a controller mapping. Most of these take a couple of minutes to check.
Quick Fixes to Try First
| Check | What to do |
| BIOS imported? | Open AetherSX2, confirm a BIOS is selected in setup |
| Storage permission granted? | Check your file manager has access when Android asks |
| Device architecture | Confirm your phone is 64-bit (arm64-v8a) |
| Renderer glitching? | Switch between Vulkan and OpenGL, or try the software renderer |
| Controller not responding? | Re-run automatic mapping in Controller Settings |
Games Won’t Start (No BIOS Imported)
Cause: AetherSX2 requires a BIOS file to run any game, and this isn’t optional. Without one imported, the app has nothing to boot from.
Fix: Open AetherSX2, go through setup, and confirm your BIOS is selected and active. Use only a BIOS file you have created from hardware you own, and check applicable local law. See our AetherSX2 BIOS guide for that process.
Saves or Games Not Appearing (Android 11+ Storage Permissions)
Cause: On Android 11 and newer, scoped storage changes how apps access files. AetherSX2 can’t place saves in a normal directory the way older Android versions allowed.
Fix: When Android prompts for file manager permission, grant it through the standard Android permission dialog. This is a normal Android permission request, not something to bypass, it’s what lets AetherSX2 read and write its own data folder correctly.
App Won’t Install
Cause: AetherSX2 is a 64-bit (arm64-v8a) build only. Installing on a 32-bit device will fail regardless of anything else you try. An incomplete download or insufficient storage space can also cause an install to fail.
Fix: Confirm your device is 64-bit. If it is, try downloading the file again in case the first attempt was interrupted, and check you have enough free storage before installing.
Rendering Glitches or Graphics Errors
Cause: Emulating PS2 hardware through a GPU-based renderer is genuinely complex, and some games trigger visual glitches more than others.
Fix: Switch renderers first, Vulkan and OpenGL behave differently game to game. If a title still glitches on both, try the software renderer instead. See our AetherSX2 best settings guide for the full breakdown.
Controller Not Responding
Cause: Automatic controller mapping doesn’t always catch every input, particularly triggers and analog sticks.
Fix: Open Controller Settings and re-run automatic mapping. If specific inputs still don’t respond, map those manually. See our AetherSX2 controller setup guide for the full walkthrough.
Slow Performance or Lag
Cause: This usually isn’t a bug. Different games use different parts of the PS2’s hardware unevenly, so the same phone can run one game smoothly and struggle with another.
Fix: There’s no single setting that fixes this everywhere. Adjust settings per game rather than expecting one global change to solve it.
Why Development Being Suspended Matters Here
Official AetherSX2 development is suspended, so there’s no update coming that will patch a bug you’re running into today. This doesn’t mean the app stops working, it means fixes have to come from settings and troubleshooting, not a future patch.
Frequently Asked Questions
Conclusion
Most AetherSX2 issues resolve with the checks above. For controller-specific problems, see our AetherSX2 controller setup guide. For BIOS-related errors, our AetherSX2 BIOS guide covers the process. If performance is the real issue rather than a hard error, our AetherSX2 best settings guide goes deeper on what to adjust.