Background compilation reduces interruptions
ARMSX3 1.7 is an Android emulator for PlayStation 3 software, built around code from the RPCS3 project and adapted for ARM64 devices. Its main change is a new background compilation system for SPU code, allowing games to continue running while additional code is prepared. Areas that previously paused while compilation finished can now load without stopping gameplay, although games that require the older pause behavior retain it.
Compiled SPU code also survives emulator updates and game updates. That means an update no longer discards all of the work already completed for a title. Each game does need to compile once more on its first launch after installing ARMSX3 1.7, but later starts can reuse the resulting code. The app also prevents waiting threads from consuming CPU time unnecessarily during compilation, which should reduce wasted processing while the emulator is busy preparing code. Clearing a game's cache removes its compiled SPU data, and uninstalling a game together with its cache now releases the associated compiled files as well.
The Last of Us receives extensive stability work
The Last of Us is the most heavily targeted game in this release. ARMSX3 now keeps the game's background jobs moving when they are submitted and then awaited. On phones, a stalled job list could previously leave unfinished work behind and freeze the game after anything from several minutes to several hours. Version 1.7 addresses that failure mode.
The update also fixes crashes caused by Android's limit on memory mappings. One problem could appear after extended play while newly generated shaders were waiting to be written to storage. Another could occur later in the game when its accumulated shaders reached the same system limit. The release notes report that the game uses about 1 GB less memory in the latter case, improving the amount of headroom available during long sessions.
Several startup failures are addressed at the same time. The game should no longer crash on its first boot while displaying its loading indicator and compiling SPU code, or encounter the related PPU trap on the next boot. New SPU code can now be compiled in the background during play. ARMSX3 also fixes the app closing when a user tried to exit or restart after the game had become stuck on its loading screen.
RPCS3's recommended patches for The Last of Us are enabled by default in this release. They cover the disc release, version 01.00, and the final update, version 01.11. The patches provide the documented performance and resolution-scaling fixes, along with fixes for the severed-head crash and the University nail-bomb softlock. These changes address several known obstacles in the game's emulation rather than simply adjusting visual settings.
Black Ops III and other games get targeted fixes
Call of Duty: Black Ops III receives fixes for the European and US releases, including updates 1.06 and 1.07. A freeze shortly after a profile loads is addressed, as is another profile-loading freeze that could still affect some phones after the first fix. The Zombies menu freeze is also fixed, giving users of those releases a more reliable path into the game.
Ashes Cricket 2009 can now get past the loading stop and reach gameplay. Killzone 3 and Ratchet & Clank: Tools of Destruction receive tuned settings, while Tools of Destruction specifically gets a fix for a crash at resolution scales below 100 percent, including an example scale of 83 percent. ARMSX3 also corrects the sorting of close-up draws on Android GPUs, which can affect objects such as the weapon shown in Call of Duty: Black Ops II.
The release notes identify specific fixes and settings for the listed games rather than offering a universal compatibility guarantee. Results can still depend on the Android device, graphics driver, game release and emulator configuration.
Device, graphics and driver improvements
Setup on phones using newer MediaTek chips, including the Nothing Phone (2a) example given in the release notes, no longer fails to install the firmware. Mesa drivers can now retain compiled shaders between sessions, which is intended to reduce stutter on later runs rather than requiring the same shader work every time the game starts.
Graphics behavior receives several lower-level corrections. Shader calculations now follow the RSX graphics processor's floating-point precision more closely, with native 16-bit floating-point support used where the GPU provides it. LOCAL FIFO mode supports games that keep their RSX command buffer in video memory. Frame generation is ordered correctly when Multithreaded RSX is enabled, and the shader interpreter receives additional fixes.
The update also incorporates upstream RPCS3 work affecting thread stack guard pages, save states, PPU branch alignment, RSX tile bank selection and memory management in several system modules. Controller buffers now begin in a clean state. NFC readers support additional reader and Mifare commands, while arcade card readers retain their card data. Threads waiting through futex_waitv no longer spin when the operating system blocks that operation.
Interface and diagnostic changes
Encrypted disc images now provide a clearer indication when a required key is missing or does not match. This gives users a more useful error state than a generic failure when the image cannot be opened.
The Display FPS Cap setting stays at the value selected by the user, including in games that impose their own frame limit. Overlay settings also behave more predictably: changing an individual OSD option switches the configuration to Custom, and Custom displays the choices that were actually made.
Motion controls can be calibrated to the way the device is being held. Users can set the neutral position and reset it whenever necessary. In XMB Mode, the first game's backdrop and icon appear immediately during startup, and the backdrop changes with the selected item.
Android pause and close events are now recorded in logs, together with information about how much of the memory map a game uses. That additional context should make it easier to identify whether a problem is related to an operating-system lifecycle event or memory pressure.
What users need to know
ARMSX3 1.7 was published on November 18, 2026, with Android packages for armv8.2 devices targeting SDK 30, SDK 33 and SDK 35, plus a legacy armv8.1 package targeting SDK 30. The project does not include PlayStation 3 firmware, games or other Sony-owned files. Running the emulator requires the user's own PS3 firmware, and the project states that users should play games they own.
The firmware installation supplies the system files used by Boot XMB. XMB Mode itself is ARMSX3's own interface, using information such as game icons, fonts and settings from the installed firmware rather than shipping Sony's files with the emulator. The project is not affiliated with or endorsed by Sony Interactive Entertainment.
For people already using ARMSX3, the most consequential change is the shift to persistent background SPU compilation. It should make later launches less repetitive and reduce pauses when new code is prepared. The game-specific fixes are particularly substantial for The Last of Us and Call of Duty: Black Ops III, while the device, graphics, cache and interface changes improve troubleshooting and day-to-day use across the Android emulator.




