Fix a MAME black screen or missing audio on Android in the right order
Audit ROMs and CHDs first, then wait through the machine’s documented startup, reset only if the driver requires it, and test default video/audio settings. If the game runs but sound breaks, check Android output routing and whether emulation speed stays near 100% before lowering latency or changing renderers.
Do this in order
- 01
Record the emulator/core version, game short name, Android device, and the exact symptom.
- 02
Run the targeted ROM audit and confirm every required CHD is found.
- 03
Launch with default settings and wait through the machine’s normal initialization.
- 04
Open the emulator menu: if it renders, distinguish machine output from renderer failure.
- 05
Check emulation speed, then Android media volume, Bluetooth route, mute, and focus.
- 06
Change one video or audio option, retest, and revert it before trying the next.
Decision and diagnostic table
| Observation | Most useful inference | Next test |
|---|---|---|
| Menu visible over black game area | Frontend renders; machine output or data is suspect | Audit, startup wait, machine reset |
| Menu also invisible or corrupted | Renderer/device path is suspect | Return to default renderer, restart app |
| Video smooth, no sound | Routing, mute, or game-specific audio path | Android output route and another verified game |
| Audio crackles and speed is below 100% | CPU starvation, not primarily latency | Restore defaults and reduce workload |
Prove the content layer first
A frontend can enter a launch view even when a BIOS, parent, device ROM, or CHD is missing. Save the full audit result before changing rendering. “ROM set is good” and “all required disks were found” are separate checks.
Use another authorized game known to work in the same emulator. If it renders and sounds correct, the global Android path is less likely to be the cause.
Recognize expected blank startup
Some emulated hardware performs memory tests, drive initialization, or other long startup work. Consult the driver warning and wait without repeatedly backgrounding the app. A one-time reset may be documented, but random resets can restart the same sequence.
Keep throttle enabled during diagnosis so timing behavior remains representative.
Audio crackle often follows slow emulation
When emulation cannot sustain its target speed, the audio stream can underrun. Increasing latency may hide a small scheduling issue, but it cannot repair a machine running far below full speed.
Disconnect Bluetooth once to rule out route and codec delay, test the device speaker, and verify media—not ringtone—volume. Then profile performance using the separate performance checklist.
Troubleshoot with an authorized, audited test game. Do not use unknown ROM or BIOS packs as a diagnostic shortcut.