Bachata S4 PS4 emulation on Android
Experimental ARM64 emulation

PlayStation 4 emulation on Android.

Bachata S4 is an experimental PlayStation 4 emulator for ARM64 Android devices, built on the shadPS4 emulator core. Every compatibility result on this site comes with the exact release, phone, graphics driver, screenshots, and logs behind it.

Explore compatibility View on GitHub Get Bachata S4
PlayableCompletable without major issues
IngameGameplay works with major issues
MenusReaches menus, not gameplay
BootsVisual or audio output before menus
NothingCrash, hang, or black screen
The project

What is Bachata S4?

A PS4 emulator that runs on your phone

Bachata S4 adapts the shadPS4 emulator core to modern ARM64 Android hardware. PlayStation 4 software is built for x86-64 processors, so Bachata S4 runs PS4 game code through FEX, an open-source x86-64 emulator for ARM devices, inside a managed Linux (glibc) runtime packaged with the app. Graphics are rendered with Vulkan, using either the system's Vulkan driver or an explicitly selected driver such as Mesa Turnip.

Why it is experimental

PS4 emulation on Android is demanding: the emulator must translate game code, keep a full Linux environment alive, and drive a modern GPU in real time — all on mobile-class silicon and power budgets. Games that run on one phone may not run on another, and results can change with every release, driver, and thermal state. Treat compatibility reports as evidence for a specific configuration, not as promises.

Public source and evidence

The ARM64 emulator client and core remain open source. This release and community repository publishes the compatibility database, issue discussions, release notes, and downloads. Anyone can inspect report evidence or contribute a test of a game they legally own.

This website

This site publishes the compatibility database: one canonical entry per game serial (CUSA ID), with every report tied to an exact emulator release, device, SoC, GPU, Android version, and graphics driver — plus screenshots, logs, and measured performance.

Explore

What you can find here

Compatibility Database

Compare actual game test reports — one entry per CUSA serial, with search and filters for release, status, device, driver, and GPU.

Browse the database

Devices & Drivers

See the exact phone, SoC, GPU, Android version, and Turnip or system driver used for each test before comparing with your own setup.

See test configurations

Evidence

Open the screenshots, compressed session logs, and measured performance behind every report. Evidence is public by design.

How evidence is collected

Community Discussions

Jump directly to the canonical GitHub issue for each title, or browse all game reports in the issue tracker.

Open discussions
Generated from real reports

Live project numbers

—Tested games
—Total reports
—Devices represented
—Playable
—Ingame
Fresh from testers

Latest compatibility reports

Most recent test results, from the generated site data.

Loading latest reports…
Browse all compatibility reports Full updates feed
Reading reports correctly

Why results differ

Every report is a snapshot

A compatibility result describes one emulator release on one device on one day. The same game can behave differently depending on the Bachata S4 release, the SoC or CPU architecture generation, the GPU, the Android version, and the graphics driver — including the exact Turnip version when a custom driver is used.

Beyond the hardware

Results also vary with thermals (long sessions throttle mobile chips), the game update or version tested, and emulator settings such as resolution scale. Two phones with the same chip can still give different results because of cooling, firmware, and driver builds.

Check before you compare

Before trusting a report, match its release, device, driver, and game version against your own setup. If your result differs, that is normal — and the project would like to hear about it: new reports are how compatibility gets better.

Results can regress

Emulator development is not a straight line. A release that improves one game can change rendering or audio for another. That is why multiple reports per game are preserved instead of overwritten — history stays visible.

Evidence-first

How testing works

Full methodology →

  1. Pick an official release

    Testers select a published Bachata S4 release — never a local or dirty build.

  2. Record the environment

    Exact device, SoC, GPU, Android version, and graphics driver (including Turnip version) are recorded up front.

  3. Test legally owned software

    Only software the tester legally owns is launched — games, or open-source homebrew.

  4. Publish evidence

    Screenshots, compressed logs, and measured performance are submitted for review before the report is merged.

Status meanings

Status definitions

Playable

Suitable for normal play in the tested configuration, with no major blocker found.

Ingame

Reaches controllable gameplay, but completion and full stability are not verified. Ingame is not the same as playable.

Menus

Reaches menus or title screens, but not controllable gameplay.

Boots

Starts and produces meaningful visual or audio output before an early blocker.

Nothing

Crashes, hangs, or fails to produce useful output in the tested configuration.

Open source

Development happens publicly

Source code

The emulator, Android frontend, and runtime build recipes are on GitHub under an open-source license.

JICA98/Bachata-S4

Game discussions

One canonical issue per game, labelled game-report, with the best confirmed status kept up to date.

Browse game issues

Compatibility data

Structured reports, screenshots, and compressed logs live in a separate repository with validation on every change.

Bachata-S4-Compatibility

Test something

Have a game not listed yet? The contribution skill walks through the full evidence workflow.

Contribution workflow
Clear and honest

Legal & trust

Independent project

Bachata S4 is an independent open-source project and is not affiliated with, endorsed by, or sponsored by Sony Interactive Entertainment. “PlayStation” and related marks are trademarks of their respective owners.

No distribution of protected content

Bachata S4 does not distribute games, firmware, decryption keys, or licenses. Users are expected to run only software they legally own, such as their own dumps or open-source homebrew. Every compatibility report follows the same rule.

Learn before comparing

Compatibility knowledge base

Read reports correctly

Learn why the same title can behave differently across Bachata S4 releases, Android devices, GPU drivers, thermals, and game updates.

Compatibility guide

Understand the evidence

See how statuses are assigned, what testers record, and why screenshots and logs are preserved with every report.

How testing works

Common questions

Get answers about supported devices, Turnip drivers, FPS numbers, regressions, legal game ownership, and reporting a result.

Read the FAQ

Permanent game pages

Open one crawlable page per CUSA serial with report history, device details, driver details, performance, screenshots, and logs.

Browse all games