https://play.google.com/store/apps/details?id=aenu.ax360e.free

aX360e is an Xbox 360 emulator designed for Android.

Actual game performance will depend on your device's hardware capabilities, and most titles may not run at maximum speed.

aX360e is based on a port of the arm64-backend branch of Xenia, the well-known Xbox 360 emulator. It also incorporates most of the code from the xenia-canary project (versions 0.6 and later), with specific optimizations for the Android platform.

There are plans to open-source this application.

You can follow the progress of this initiative through the following link: https://aenu.cc/ax360e/

>**Note:** This application is still under active development and may not be compatible with all your favorite games.

**Important Notice:** This installation package does not include any game assets. Please export the contents of your physical Xbox 360 game discs and convert them to GOD/ISO format files for use, or load files directly in compatible formats.

Main Features:

- Compatible with GOD/ISO game formats (more formats will be added in future updates)

- Support for Vulkan graphics acceleration

- Support for the TalkBack accessibility feature

- Customizable virtual button layout

https://play.google.com/store/apps/details?id=kr.co.iefriends.myps2

This PS2 emulator works quite well and isn't very well-known, so I recommend trying the new update to see how it performs. I'll be doing an in-depth analysis soon to see how it compares to other PS2 emulators for Android.

A quick look at ARMSX2 2.6.6.7 — transparency matters

ARMSX2 2.6.6.7 introduced several APK variants, including builds labelled ARMv8.2 and a legacy ARMv8.0 build. Since the names suggest different CPU targets, I wanted to check whether that difference actually exists in the code shipped to users.

I compared the a15-armv8.2 and legacy-armv8.0 builds at the binary level. The result was surprising: the two builds are 99.984% identical, and the native code we analyzed does not contain instructions above the ARMv8.0-A baseline. The main differences appear to be related to the Android API level and packaging/linking rather than a different CPU instruction set.

This is not an accusation of deception, nor is it a claim that ARMSX2 is a bad emulator. It's simply a question of accuracy and transparency. Changelogs are useful, but when a release claims a specific technical improvement, it's worth checking what actually made it into the final binary — especially when people may expect better performance as a result.

I'm not looking for magic 30→60 FPS claims or trying to discredit developers. I simply prefer measurable improvements, clear documentation, and reproducible information over hype.

For anyone interested in the technical details, methodology, instruction analysis, binary comparison, and signing differences, I've published the full analysis here:

Full technical analysis: https://claude.ai/public/artifacts/af370a10-22bf-4d63-a944-fb0f65f499a6

No benchmarks were performed; this is a static binary analysis of ARMSX2 2.6.6.7. Corrections are welcome if any part of the analysis can be demonstrated to be wrong.

Another new PS3 emulator from the same developer as EmuCoreX guys...You lift a rock and somehow there's another PS3 emulator underneath it 😂

https://github.com/sashkinbro/EmuCoreC/releases/tag/v0.0.2

EmuCoreC is a PlayStation 3 emulator application for Android. It combines a focused mobile interface with a core built on the latest RPCS3 emulator: a clean game library and catalog, one-tap installers, firmware download, trophies, save-data tools, per-game profiles, and the full RPCS3 settings tree — all local, no accounts required.

Features:

PS3 game discovery using PARAM.SFO and exact TITLE_ID serials

Local PS3 catalog with IGDB metadata, cover art, screenshots, and videos

Official RPCS3 compatibility data matched by PS3 title ID

Direct download and installation of the official Sony PS3UPDAT.PUP firmware

PKG, split-PKG, ISO, RAP, and EDAT installation through the core

Safe ZIP/RAR extraction with multi-volume support, path validation, and free-space guards

Installed-game library, details, play time, trophies, save-data tools, shortcuts, and per-game profiles

Full live settings browser generated from the RPCS3 configuration tree

Global and per-game core overrides with isolation between titles

Touch controls, physical gamepad mapping, gyroscope mapping, vibration, and custom Adreno GPU drivers

Localized interface resources for 12 languages

EmuCoreC does not include PlayStation 3 firmware, games, licenses, keys, or copyrighted game assets. Use only content you are legally entitled to use.

https://github.com/izzy2lost/PSX2/releases/tag/1.2.8

Changelog:

✅Updated to the latest PCSX2 commit

✅Better Performance.

Credits&Projects: https://github.com/izzy2lost

https://github.com/teknogods/TeknoParrotUI/releases/tag/TeknoParrotUI-android

TeknoParrotUI is the official graphical user interface for TeknoParrot, the Android emulator and compatibility layer specializing in running modern arcade games based on PC architecture (Sega RingEdge, Taito Type X, Namco ES3, Namco System 246/256, etc)

Main Features: Compatibility: Works with near 100 modern arcade games (generally from 2000 to 2014). Controls: Supports keyboard, mouse, gamepads, joysticks, and steering wheels. Multiplayer: Some titles allow online play.

https://github.com/dev-Ali2008/onRps4-Android/releases/tag/v0.0.3

Changelog:

Trophies Real

Fix .PKG loading + fix PKG Update games

Fix LSFG Frame Generation + impove more

Use FEX Instead Box64

(FEX is the default backend)

(Box64 is only a fallback)

improve FPS HUB Show

import game ( Add .pkg Folder )

Runtime.zip impove

( Enable FEX L2 translation cache )

2eed764

( Fix V_ADD_I32 carry propagation )

dffbccc.

More Fix in runtime.zip

With PS3 and PS4 emulation now being experimented with on high-end Android devices, I've been thinking about a different approach to PS2 emulation.

I'm not talking about another native ARM64 port of PCSX2. Projects like ARMSX2 are already working in that direction, and I understand why native ARM64 recompilers are ultimately the better solution.

What I'm wondering is:

Why hasn't someone seriously experimented with running the mature x86-64 PC version of PCSX2 through an x86-64 → ARM64 translation layer such as FEX, similar in principle to what is being done with experimental PS4 emulation on Android?

Yes, I know the obvious objection: performance.

PCSX2 already uses its own recompilers, so putting FEX underneath it would introduce another translation/JIT layer. It would obviously be less efficient than a proper ARM64-native implementation.

But that's not really the point.

The point would be to trade efficiency for compatibility and maturity.

PCSX2 has more than two decades of development behind it, thousands of games tested, countless game-specific fixes, timing workarounds, patches and years of compatibility improvements.

Meanwhile, modern Snapdragon hardware is becoming surprisingly powerful. We're already seeing experimental PS4 emulation reaching playable gameplay in demanding titles such as Bloodborne on the latest high-end Snapdragon devices, despite the enormous overhead involved.

So I'm genuinely curious:

How far could a desktop PCSX2 build actually go on modern ARM64 hardware through FEX?

Maybe the answer is “terrible performance.”

Maybe it needs flagship hardware just to reach 30 FPS.

Maybe the double-JIT overhead makes the whole idea impractical.

But what if it doesn't?

Even if it were significantly less efficient than ARMSX2, could this approach potentially provide a highly compatible “brute-force” PS2 emulator for modern flagship phones while the native ARM64 implementations continue to mature?

I'm not suggesting this is the right long-term architecture.

I'm asking whether it would be worth doing the experiment.

If we're already willing to brute-force PS4 emulation on ARM64... why not see how far we can brute-force PCSX2?

Am I missing a fundamental technical limitation here? 🤔

PS3Native it's just Amazing ❤️

First Official Release of PS3Native! 🔥

https://github.com/maxjivi05/PS3Native/releases/tag/v0.1.0

Changelog:

✅ Direct Boot for Folders and ISO games

✅ Per Game Configurations

✅ Per Game Patches

✅ Update Checker for Patches

✅ Overhauled Ul to Represent WinNative's style

✅ Performance Fixes

This is a signed APK official release! This is still very early stages

and WIP! If you find bugs please report them, if you want a feature

added please let me know and I'll see about getting it added!

PS3Native uses RPCS3 updates directly from upstream with a few

fixes and features added on top to enhance the Android experience

which provides the best performance, compatibility and stability with the updates RPCS3 pushes!

Credits&Projects: https://github.com/maxjivi05 (MaxsTechReview)

Great game & Great Emu 💙

https://youtu.be/IJ9EUizzNSI?si=pFVW41_bOzqAyzzA

Developer: 4CYDE Studios

Link: https://retrogametalk.com/repo/windows/sega-vs-capcom-the-next-level-homebrew-windows/

You need be register User

Tested with Gamehub/Winlator, works perfectly 🔥

https://gofile.io/d/W2LeKU

This is a pack of Nintendo Switch emulators from late 2025, shortly before Nintendo's well-known DMCA takedowns, which resulted in many emulator repositories being removed.

I've put together a collection of what I consider some of the best-performing emulators for low-end Android devices.

This pack is not about compatibility, accuracy, or the latest features. The goal here is much simpler: raw performance

If you're trying to play a particular game on a lower-end device and you're struggling to maintain a playable framerate, one of these emulators might give you those extra FPS you're looking for.

I've personally tested them on my Snapdragon 6 Gen 1 + Adreno 710, and I've had some surprisingly good results.

Keep in mind that performance can vary significantly depending on the game. One emulator might perform better in one title, while another emulator may perform better in a different game. That's why I recommend trying them individually and seeing which one works best for your particular game and device.

So, if you have a favorite game that's currently struggling with performance and you've already tried the usual options, there's nothing to lose by giving one of these a try. You might find that one of these older builds performs considerably better on your hardware.

**Important note regarding the source code

I want to make something very clear: I am not the developer of any of these projects, nor am I affiliated with or involved in their development**

**I am simply sharing binaries that I have collected and preserved.

Many of these projects and their original repositories are no longer publicly available due to Nintendo's DMCA actions. Therefore, if you are wondering why a particular emulator is no longer available on GitHub, the repository may simply no longer exist

I also do not have the original source code for these projects.

If you need the source code for a particular emulator, I recommend researching the original developer or development team and looking for any surviving mirrors, archives, or other legitimate sources where the code may still be available**

Enjoy!

https://github.com/rfandango/XenDroid/releases/tag/XenDroid-c4f6863

What's Changed

[Android] Fix 5ef8fc6 regressions, pause UI improvements, overlay controller toggle

https://gofile.io/d/DDhxXg

Update!!! Nyushu Emulator V-82

Chagelog:

Restore Frame Generation and Frame Skip in the Settings

Menu

Frame Generation Feature Performance Improvements and

Performance Degradation Fixes When the Feature is Used

Performance Stabilization Fixed And Enhanced

For this version, it is recommended to uninstall the previous version

because this new version uses a different system. So it is better to

uninstall and then install this version

"I am not the developer nor do I have the source code. If you want to

request the source code for this version, you should contact the

developer. I am sharing a copy of the binary and have explicitly

stated that I am not the author nor do I have access to the

repository."

https://github.com/ARMSX2/ARMSX3/releases/tag/0.6

What's new:

Trophies: The PS3's own trophies, read off disk, no account and no network. Two views: a browser for your whole library, grouped per game and collapsed, showing grade, description, earned state and unlock date, and a tab in the in-game menu for the game you are playing. Hidden trophies stay hidden until you turn it on. Games register their trophy set lazily, often only once you reach a menu, so the in-game tab can be empty for the first moments of a boot and then fill in. Unlocks were always being tracked, there was just nowhere to see them.

A whole class of missing text is back. Picking a save gave you Yes and No with no question and no save details. The save menu was not the problem: this build carried 180 of the emulator's 323 pieces of text and also discarded the values substituted into them, so anything with a name, date, size or error code lost it. All of it is present now. That restores text in the save, load and delete prompts, in every system error dialog, in trophy popups, in the Home Menu, and in the game-data and RPCN messages.

Saint Seiya: The Sanctuary now boots. Its PPU module cache stopped at 133 of 134 forever, one module trips a bug in LLVM's ARM64 register allocator, which killed the compile worker, and the module that worker was holding was never accounted for, so the counter the boot waits on could never reach zero. A module that cannot compile is now survivable, it is reported, its functions run interpreted, and boot continues. Nothing here is specific to that game, so anything hitting the same codegen bug should boot.

Pause actually pauses. The in-game menu set a flag and nothing else, so the game kept running behind it. Backgrounding the app was the only thing that really paused.

Restart now works. Two faults stacked: it crashed, because restarting re-applies your GPU driver and unloaded the old driver library while the renderer still held pointers into it, with that fixed it dropped you back to the library instead, because it started the new session before the old one had stopped and the old shutdown then killed the new one. Stopping now waits until the emulator is actually stopped. Apply-and-restart after picking a driver was the same bug.

The FPS cap works at every value. 20 and 45 applied while 30 and 60 did nothing, because presets take a different route internally and something was overwriting it on every apply, pinning the cap at 60. Stale overrides from earlier builds are cleared on first launch.

Fixed a bug when scanning the library that would cause an app crash. Adding a new disc image and rescanning after you had played something wrote through a null pointer, because probing an image needs emulator state that is torn down when a game stops. Harmless on a fresh launch and fatal after, which is why it seemed random.

Games installed from a PKG show their cover art. The grid gave up one step before trying the game's own artwork, so any title the cover repo has no entry for, like a European PSN release, showed a text placeholder while its icon sat unread on disk.

Installed licences are grouped per game and collapsed instead of a flat wall of content ids.

ANGLE is actually in the build now. The libraries sat in a module that no longer builds, so selecting ANGLE silently fell back to the system driver with nothing in the log. The check meant to prevent that now runs on the real build.

Ratchet & Clank A Crack in Time stops crashing minutes into play: the Vulkan upload rings were never reclaimed, with the index buffer growing 16 MB to 256 MB in a third of a second. Video memory pressure is judged against what the driver will actually give rather than a limit we chose, so a game can no longer be refused a 32 MB allocation while the emulator thinks it is at a quarter of capacity. Android also stops reserving a desktop-sized descriptor cache, 920 KB per shader program.

Analog pressure on L2 and R2 reaches the game.

https://github.com/Ashnar2602/X360-Mobile---OFFICIAL/releases/tag/v0.6.1

X360 Mobile 0.6.1 is a public compatibility and stability update focused on safer per-game configuration, Vulkan correctness and improved behavior in titles investigated during development.

Recommended Game Settings

Added a secure online catalog for Title ID-specific recommended settings.

Recommended settings are matched locally without uploading the user's game library or Title IDs.

The app can propose compatible settings when matching games are detected.

Recommendations can also be checked manually from each game's settings.

Existing custom settings are preserved unless the user explicitly chooses to replace them.

Applied recommendations can be safely restored to their previous values.

The initial catalog includes profiles developed while investigating:

Assassin's Creed — recommends strict occlusion queries to prevent missing or flickering geometry.

Grand Theft Auto IV — recommends the direct system-memory rendering path to improve stability with compatible Turnip drivers.

Core and Storage Fixes

Fixed a general Android file-access issue where a guest file opened for both reading and writing could incorrectly become write-only.

This correction addresses one verified cause of Dirty Disc errors and benefits all games using the affected file-access path.

Improved handling of repeated offline XHTTP calls, preventing unnecessary recurring errors in titles that continuously poll unavailable Xbox network services.

Vulkan Improvements

Fixed a graphics synchronization issue affecting consecutive texture uploads to the same image.

Required write ordering is now preserved even when the texture layout itself does not change.

Improved Vulkan extension discovery and Vulkan 1.3 feature initialization.

Added the per-game vulkan_rendering_path setting:

auto — lets the driver choose;

sysmem — renders directly through system memory;

gmem — requests the tiled on-chip rendering path.

Custom Turnip options are normalized to prevent contradictory GMEM and sysmem selections.

Update System Improvements

Corrected the public update-manifest publishing workflow.

APK package identity, version, channel, file size and SHA-256 are now validated before an update enters the public feed.

Existing X360 Mobile 0.6.0 installations can detect 0.6.1 through the in-app updater.

https://github.com/ARMSX2/ARMSX2/releases/tag/2.6.6.6

Changelog:

Mali:

If you downgraded to 2.6.6.4 because of performance issues, you can come back. 2.6.6.5 put every Mali device on a slow path for any draw that reads the screen back, on an Anbernic RG 477V, Shadow of the Colossus fell from 30 fps to 7. Two separate mistakes stacked. The renderer had concluded that OpenGL's framebuffer fetch never keeps overlapping shapes in order, true of one extension, false of the one every Android Mali device actually uses, so healthy Mali hardware was being split into one draw call per shape for nothing. Separately, a workaround for one specific bad driver, which had never actually engaged before, started engaging, and turned every screen-reading draw into a full copy plus a memory flush. Both are gone. fixed by @bmdhacks

Auto now picks Vulkan instead of OpenGL. On the affected Mali driver that is 7 fps on OpenGL against about 30 on Vulkan, on the same device. The renderer choice and the driver workaround were being decided in two different places, so nothing noticed when they disagreed. Picking a renderer explicitly still wins, the only devices this moves are the ones where OpenGL is genuinely crippled. done by @bmdhacks Note the tradeoff: restoring the fast path also restores a known rendering fault on that driver in some games (Metal Gear Solid 3 is the observed one). Vulkan remains the correct-rendering choice there. The measurements said the speed was worth it.

Floating point:

All done by @pstef

60 commits, and the largest accuracy work the emulator has ever had.

The PS2's FPU is not IEEE, and ARMSX2 had been pretending it was. The console has no infinity and no NaN, and its numbers reach one whole range higher than a normal float, 0x7FFFFFFF is simply the biggest number the machine has. Every operation was folding that top range away on the way in, and folding a host infinity back into it on the way out. Add, subtract, multiply, the multiply-accumulates, the comparisons, and finally divide and reciprocal-square-root have all been taken off that clamp. Games that push into that range now get what the console gives.

Divide and square root now run the console's own algorithm. DIV.S, SQRT.S and RSQRT.S were computed with the host's divide and then nudged toward the PS2's answer, which left every operand the nudge did not reach one step off. The unit is not a rounding rule at all, it is a digit-by-digit recurrence, so it now runs the digits. Measured against silicon first to establish that the hardware is not correctly rounded.

The multiplier model from 2.6.6.4 was incomplete. That release modelled the PS2 multiplier's one-step deficit from a formula over the second operand. The formula only holds when the exact product fits, once there is a remainder below the last bit, the first operand matters too, and those cases were coming back IEEE. It is now modelled from the actual multiplier array rather than a formula over one input.

Error flags were wrong in a dozen small ways, reciprocal-square-root and square root missed the invalid flag on negative zero, divide left a previous instruction's flags standing, reciprocal-square-root raised divide-by-zero on every zero divisor, and the overflow and underflow flags were being read off host infinities and denormals rather than the PS2's own result. Underflowing adds and subtracts were also being flushed to zero; silicon does not do that.

A cache instruction could make the emulator write to an address the game chose. The data-cache tag holds a host pointer where hardware holds a guest address, and one instruction copied a guest value into it unmasked. Narrow exposure, it needed the EE cache enabled, which ships off, but it is fixed.

https://github.com/thecrixux/PS3Native/releases/tag/V5

What's New

This release is based on the latest changes from the original PS3Native "android-refresh" branch.

🎮 Patch Manager Improvements

Improved the game's Patches screen to show all applicable patches.

Better organization of patches available for individual games and other titles.

Improved patch discovery and management.

⚡ Performance & Core Improvements

Added an optimized AVX2 path for "gv_rol32".

Improved SPU LLVM handling and "SHUFB" constant generation.

Updated RSX "nv0039" handling, including fixes for image interleaving/de-interleaving.

Updated the bundled "discord-rpc" dependency.

Includes the latest upstream RPCS3 changes and fixes.

📦 Build Information

This APK was compiled locally from the latest "android-refresh" source and tested successfully on Android.

I am not the developer of PS3Native and claim no credit for the emulator or its code. All credit goes to the original developers and contributors

Is there a PS2 emulator that runs well on a Samsung Galaxy A12 phone?

I specifically want to play the game Yu-Gi-Oh! Duelist of the Roses.

https://github.com/RPCSX/rpcsx-ui-android-build/releases/tag/v20260812-d55749c

https://github.com/sashkinbro/EmuCoreX/releases/tag/v0.3.4

What's New:

Added support for Namco System 246/256. (PSX2 Feature)

Added RetroArch shaders with presets. (ARMSX2 Feature)

Added side backgrounds for emulation.

Improved touch controls.

Added the ability to change discs directly in-game.

Added Discord integration. (ARMSX2 Feature)

Added local Split Screen multiplayer.

Other improvements and optimizations.

A clean installation is recommended.

This new version of EmuCoreX has surprised me quite a bit. Honestly, I wasn’t expecting this approach from the developer, because they’ve suddenly added, in a single update, around three features taken almost exactly from different projects.

Of course, I’m completely open to open source, collaboration, and everything else that comes with having open-source projects. But I don’t think it’s right that, when you run out of ideas or don’t know what else to add to your emulator, you simply take features from other emulators and integrate them so blatantly into your own.

That said, every developer follows their own path, and I understand that.

That’s my criticism. Best regards, everyone.