Android MAME low-volume troubleshooting / 2026-08-05

Fix MAME volume that is too low on Android without masking missing sound

Trace low output through Android media volume, MAME attenuation, saved per-system configuration, mixer routes, and machine-specific sound.

9 minute audio-level diagnosticOfficial MAME 0.289 sound and menu behavior as exposed by an Android port; Android media routing and wrapper controls remain device-specific

Fix MAME volume that is too low on Android without masking missing sound

Start with Android media volume and the active output route, then inspect MAME's master attenuation. In upstream MAME, `volume 0` is full volume and negative values attenuate it; a value saved in the running system's configuration takes priority over general INI volume. Reset the master and channel sliders before changing audio latency or sample rate. If only one machine remains quiet or incomplete, follow its device, sample, and emulation-status evidence instead of amplifying every game.

Do this in order

  1. 01

    Record the Android media-volume level, active speaker, wired or Bluetooth route, Android port, upstream MAME revision, machine short name, and whether every known-good game or only one title is quiet.

  2. 02

    Use a verified control game, restore MAME master attenuation to 0 dB, and reset per-channel Slider Controls rather than raising unrelated machine inputs.

  3. 03

    Inspect the system-specific configuration because an in-UI volume change is saved there and takes priority over volume in general INI files.

  4. 04

    If the port exposes MAME 0.289 Audio Mixer, verify that an output route exists and that its route or channel level was not reduced; otherwise use only the wrapper's documented audio surface.

  5. 05

    Keep sample rate, audio latency, renderer, speed, and effects at the control baseline; they diagnose quality or continuity and should not hide a simple attenuation fault.

  6. 06

    Cold-relaunch the same game and a control game, then follow missing samples, device ROM, imperfect-sound, or Android route diagnostics only for the branch that remains different.

Decision and diagnostic table

ObservationLikely layerNext check
All games are quietAndroid route or MAME master attenuationMedia output, 0 dB master, mixer route
One game is quietSaved system CFG or machine audioReset its sliders and read driver status
Some effects are absentSamples or emulated sound deviceAudit named sample or device requirements
Audio is broken below full speedPerformance or buffer underrunRestore speed before changing volume

MAME volume is attenuation

MAME documents `volume` in decibels with zero as no attenuation, or full volume. A negative value such as -12 dB makes output quieter. Resetting to zero is the clean baseline before investigating gain elsewhere.

The running system can override the general INI

MAME saves a user-interface volume change in the system configuration, and that saved value has priority over general INI volume settings. Editing the global file alone can therefore appear to do nothing for one title.

Low level and missing sound are different failures

Slider and mixer controls change routed output. They cannot supply a missing sample file, repair a device ROM, correct imperfect emulation, or recover real-time performance. Compare one control game and follow the narrow evidence branch.

First-party sources

Related guides