ARMSX3

Raud · Games

Verified safeOpen sourceExclusive

Download APK

—

No reviews reviews

downloads

8.0

android

AI summary

Android port of the RPCS3 PlayStation 3 emulator. Runs PS3 games with touch or physical controller support; early builds achieve roughly 20–30 fps on flagship hardware. Version 0.4.2 fixes SPU cache compilation hangs that caused black screens in Demon Souls and other titles. Requires broad storage and Bluetooth permissions for game data and controllers.

Generated by AI. May contain inaccuracies.

About this app

Proof of concept Android port of RPCS3.

Uses the latest RPCS3 upstream code (the recent ARM64 improvements included).

Status From my testing, I only tried Skate 3. It boots, loads and reaches gameplay at roughly 20 to 30 fps on a Snapdragon 8 Gen 2. Rendering, audio, touch controls and physical controllers work. Almost nothing else has been tested. So the main stop gap at the moment is performance/speed.

emulator playstation 3 open source offline proof of concept

What's new

v0.4.2Aug 10, 2026

https://github.com/ARMSX2/ARMSX3/compare/0.4.1...0.4.2
Fixed Demon Souls hanging at 1s remaining while compiling SPU cache. Games that worked on 0.3 could hang on 0.4, a black screen or a frozen "building SPU cache" bar, with no crash and nothing in the log. Let me know if inFamous 2 works again as well. 0.4 sped up the RSX command loop by publishing the FIFO read pointer on a short delay instead of after every packet. It was published immediately on every path that could wait, except the one where the command ring runs empty, which is the one path where nothing further would ever publish it. The game then waited forever on progress the emulator had already made but never announced. Because it depended on where the ring happened to drain, the same game could boot one day and hang the next. The speedup is kept.
The emulator now says when a game has stopped. A stopped game left its last frame on screen forever. If that frame held the loading bar, it looked like a stuck compile, the same picture for five completely different faults, which sent a lot of bug reports the wrong way. After 30 seconds with no frame drawn and nothing actually loading, it now says so on screen and in the log.