Gameplay from Street Fighter II on Arcade. Image from the Retro Replay media library.

MAME4droid (Current)

ARCADE EMULATOR

MAME4droid (Current)

MAME4droid (Current) — an actively maintained Android port of the upstream MAME emulator, providing a native Android app that runs many arcade and classic computer/console drivers supported by recent MAME releases.

Jump to download ↓Jump to setup guide ↓

Gameplay from Street Fighter II on Arcade. Image from the Retro Replay media library.

ArcadePRIMARY SYSTEM

History documentedPROJECT BEGAN

Open sourcePROJECT MODEL

WHY IT MATTERS

Why use this build?

Provides a native Android front-end and builds of modern MAME sources (recent MAME 0.2xx series) with Android-specific input, rendering and performance work by developer David Valdeita (Seleuco). It is kept current with MAME upstream releases and adds Android conveniences such as storage paths, on-screen controls, controller mappings and optional NetPlay features.

BEST FOR

Best for

Android phone and tablet users who want a relatively up-to-date MAME experience on mobile devices without building MAME from source themselves.

The people behind MAME4droid (Current)

History and status

MAME4droid originally evolved from earlier Android ports of MAME. The 'Current' repository maintained by David Valdeita (Seleuco) packages recent upstream MAME sources into an Android application and is actively released and updated on GitHub and the Play Store. Recent releases in the repository track modern MAME version numbers and add features such as improved GLES rendering, HDR/CRT vector rendering improvements, input fixes, and a native P2P rollback NetPlay implementation. Releases are published on the project's GitHub releases page and an app listing exists on Google Play. The project is actively maintained by Seleuco with frequent releases.

What MAME4droid (Current) supports

Android (arm/arm64 builds via APK from releases / Google Play)
Arcade systems/drivers supported by the corresponding upstream MAME version (varies by release)
Some classic home computer and console drivers that MAME supports (varies by release)
Local and P2P NetPlay between app instances (release-dependent)

Download and availability

OFFICIAL DOWNLOADS

Get MAME4droid (Current)

Official binaries (APK) and source are provided from the project's GitHub repository Releases page; a Play Store listing exists for convenience. Use the GitHub releases for direct APK downloads and to inspect release notes and the exact upstream MAME version used in each build.

Get MAME4droid (Current) ↗

DOCUMENTATION

Official documentation

Read the official configuration, compatibility, and troubleshooting material before changing advanced options.

Read official documentation ↗

Broken or missing download? Emulator projects move and official links sometimes change. Please contact Retro Replay so the source can be verified and updated.

MAME4droid (Current) setup guide

Setup note: Verified, practical setup notes for Android users. Follow the release notes for the exact MAME engine version shipped with the APK you download. The app does not include game ROMs, BIOS files, or any commercial firmware.

1) Obtain the app: Preferred: download the official release APK from the project's GitHub Releases page and check the release notes to confirm the bundled MAME version. Alternatively install from Google Play if available for your device. Use the GitHub source to inspect tags and binary assets before installing.
2) Install APK (if using GitHub build): If sideloading, enable installation from unknown sources per your Android version, then install the downloaded APK. Verify the APK signature and release notes where possible. Prefer arm64 builds on 64-bit devices for best compatibility.
3) Prepare ROMs and resources: Place your legally obtained MAME ROM sets (zipped ROM sets titled with the MAME game driver name) into the app's configured ROM directory. Common default path used by releases and documentation: /storage/emulated/0/Android/data/com.seleuco.mame4d2024/files/roms/ — however confirm the configured path in the app’s Help/Settings because releases or package names may vary. Do not place loose files; use the zipped sets expected by MAME. The app does not supply BIOS or other commercial firmware files; if a particular driver requires a BIOS, you must obtain it yourself and place it in the appropriate place per the app's settings.
4) First run and permissions: On first run grant any requested storage permissions (or configure SAF/storage locations per Android version). Use the in-app help to point the app to custom ROM directories or to configure SAF access if you store ROMs on external SD cards.
5) Controls and input: Configure on-screen controls, touch input regions, or pair a physical Bluetooth/USB controller and map buttons in the app’s Input settings. Many builds expose MAME input configuration options similar to upstream MAME, but the UI is adjusted for Android.
6) Performance and video: Check the release notes for GPU/renderer specifics. Newer builds include GLES improvements and optional CRT/vector renderers. If games are slow, try changing the renderer, frame throttle, or using a lower MAME video complexity (found in Settings). CPU/GPU performance will vary greatly by device and by the MAME driver being emulated.
7) NetPlay (optional): Recent releases include a native P2P rollback NetPlay implementation. Read the relevant release notes and the in-app NetPlay help for how to create/join rooms and any networking permissions. NetPlay behavior and match-making details may change between releases—consult the release notes for the specific version you install.
8) Updating and verifying: Periodically check the GitHub Releases page for new builds and read release notes to see which upstream MAME version and changes are included. When updating, keep backups of any custom input mappings or saved game states if you rely on them across versions.

Software reminder: The app does not include commercial ROMs, BIOSes, or firmware. You are responsible for obtaining any game or BIOS files legally. Follow local laws and the upstream MAME project’s documentation for ROM naming and required files.