Use MAME autoboot_command and autoboot_delay in an Android wrapper
Put only the machine-side command in `autoboot_command`, set `autoboot_delay` long enough for that machine to accept input, and verify the effective configuration before launching through the Android wrapper. The delay is emulated startup timing, not an Android sleep and not proof that required media is valid.
Do this in order
- 01
Confirm the exact MAME binary and machine short name, then inspect its help or effective configuration for both autoboot options.
- 02
Launch the authorized machine and media manually first; record the moment its emulated prompt becomes ready.
- 03
Set a conservative `autoboot_delay`, then add the smallest machine-side `autoboot_command` that proves input reaches the prompt.
- 04
Launch once through the same Android wrapper and capture verbose output; increase only the delay if the command arrives too early.
- 05
Keep media paths, slot selection, and autoboot settings as separate evidence so a missing file is not misdiagnosed as timing.
- 06
Record binary version, machine, media identity, delay, command, and result; re-test after any MAME or wrapper update.
Decision and diagnostic table
| Symptom | What it indicates | Next check |
|---|---|---|
| Option is unknown | Wrapper/build lacks or filters it | Check binary help and wrapper mapping |
| Command appears too early | Emulated prompt is not ready | Increase delay only |
| Machine never boots | Media/dependency failure precedes automation | Audit lawful media and slot |
| Manual works, autoboot does not | Command syntax/timing boundary | Reduce command and capture verbose log |
The delay belongs to the emulated machine
`autoboot_delay` waits before MAME sends the configured command. It does not repair an Android storage grant or wait for a missing ROM, BIOS, or software-list item.
Prove manual boot first
Automation hides the first failing layer. A successful manual launch establishes that machine identity, media selection, and required dependencies precede command timing.
Treat wrapper support as evidence
An Android frontend may omit or transform upstream options. The installed binary's help and effective configuration are authoritative for that package.
Test only with games and firmware you created, dumped lawfully, or received under permission covering your use. Emulator settings and technical compatibility never grant rights to ROM, BIOS, CHD, artwork, music, or other media.