Fix missing MAME software lists by auditing hashpath on Android
Record the embedded MAME version, then check whether the Android port ships the matching `hash` directory and exposes `hashpath`. A missing list is metadata failure, not proof that software archives are missing. Point `hashpath` only at the matching official XML directory, restart, and use `-listsoftware system`; audit authorized media separately afterward.
Do this in order
- 01
Record wrapper and embedded MAME versions, target system shortname, current `hashpath`, and whether any software lists appear.
- 02
Inspect the port's supplied files without downloading third-party packs; confirm a `hash` directory with XML matching that MAME build exists.
- 03
Use the port's configuration view or `-showconfig` to read the effective `hashpath`; do not confuse it with `rompath`.
- 04
Correct only `hashpath`, restart fully, and query `-listsoftware system` or the equivalent software selector.
- 05
If the list appears, audit one authorized item with the same build; missing media is now a separate `rompath` or identity issue.
- 06
Preserve version, path source, list name, query result, and audit result; revert if the wrapper overwrites unsupported options.
Decision and diagnostic table
| Result | Meaning | Action |
|---|---|---|
| No hash XML | Package omission | Use a build that supplies matching metadata |
| XML exists, list absent | Path/version/parser | Check effective hashpath and log |
| List appears, item absent | Catalog identity | Confirm system/list/item shortnames |
| Item known, audit fails | Media path/content | Check authorized media separately |
Hash XML is metadata
Software-list XML describes known items, parts, and expected media. It is searched through `hashpath`; it is not a ROM directory and contains no game program data.
Version pairing matters
Mixing a current hash directory into an older embedded build can create unsupported entries or parsing differences. Treat the wrapper's actual MAME generation as the contract.
Discovery and verification are separate
`-listsoftware` proves the catalog entry is known. A software audit proves whether your separately authorized media matches what that build expects.
Use only games, firmware, artwork, music, and media you created, dumped lawfully, or received under permission covering your use. Emulator compatibility does not grant content rights; never use an unauthorized ROM, BIOS, CHD, media pack, or mirror.