MAME current vs MAME 2003-Plus on Android: choose by evidence
Choose current MAME when your Android device can sustain it and you value current hardware documentation, set definitions, and upstream fixes. Choose MAME 2003-Plus only when a measured device constraint or a specific supported title justifies its older base, then use the core-generated DAT and its own romset rules; the two cores are not drop-in replacements.
Do this in order
- 01
Record the Android device, OS version, RetroArch build, and exact revision of each candidate core.
- 02
Choose three authorized test systems that represent simple 2D, demanding audio/video, and any CHD or special-control need you actually have.
- 03
Generate or obtain the matching core DAT and audit the same lawful source material separately for each core.
- 04
Test sustained emulation speed, input, sound, suspend/resume, and one cold relaunch with default settings.
- 05
Compare missing-driver and imperfect-feature status; do not treat a faster boot as proof of better accuracy.
- 06
Keep the winning core, matching set record, configuration, and rollback note together; do not share the game data.
Decision and diagnostic table
| Decision factor | Current MAME | MAME 2003-Plus |
|---|---|---|
| Definition line | Moving current branch; verify exact revision | Older 0.78 base plus selected additions and fixes |
| Romset contract | Must match the current core revision | Use the MAME 2003-Plus DAT and documented packaging rules |
| Device demand | Often needs more CPU and storage headroom | Can fit constrained devices, but measure the target games |
| Best default | Current documentation and upstream behavior | A deliberate compatibility/performance exception |
The year in a core name is a compatibility contract
Libretro documents each arcade core as a distinct emulator with its own supported romset. A set that audits in one core can fail in another because driver definitions, parent relationships, and expected hashes differ.
MAME 2003-Plus is not simply current MAME with a speed switch. Its documentation says it began with MAME 0.78 drivers and later incorporated selected fixes and games, so its generated DAT is the decisive inventory.
Benchmark a task, not a menu
A useful Android comparison measures target emulation speed, audio stability, controller behavior, and resume/relaunch on the same device. Keep shaders, run-ahead, frameskip, and per-game overrides off for the baseline.
If current MAME sustains the workload, its current definitions and upstream maintenance usually make it the clearer default. If it does not, document the exact title and device constraint that makes an older core necessary.
Freeze every dependency with the decision
Record the frontend build, core revision, DAT, set style, BIOS and CHD dependencies, and configuration scope. Updating only the frontend or only the core can invalidate a previously reproducible result.
Retest a small authorized sample before changing a frozen setup. A rollback archive should contain configuration and audit records, not redistributed commercial game data.
Core availability and technical compatibility do not authorize ROM, BIOS, CHD, artwork, or sample downloads. Use your own lawful dumps or creator-approved releases.