Fix RetroArch content that closes immediately on Android
Reproduce the exit once with file logging enabled, then compare a direct Load Core → Load Content launch with the playlist launch. Read the first core or frontend error, verify the core version and required system files from that core's official documentation, and test one known-good lawful title. Do not replace ROMs, BIOS files, or drivers until the log identifies the failing layer.
Do this in order
- 01
Record the RetroArch build, Android version, core name/version, content path, launch method, and the last visible message.
- 02
Enable Settings → Logging → Logging Verbosity, Log to File, and Timestamp Log Files; note the System Event Logs directory.
- 03
Use Load Core to select the intended core, then Load Content to reproduce the exit once outside the playlist.
- 04
Open the newest log and capture the first core or frontend error before any later cascade messages.
- 05
Compare the content type and required system files with that exact core's official documentation, then test one lawful known-good title with the same core.
- 06
Change one layer only—association, system path, core build, or video driver—restart, and reproduce with a new timestamped log.
Decision and diagnostic table
| First evidence | Likely layer | Controlled next test |
|---|---|---|
| No compatible core or unsupported extension | Core/content pairing | Load the exact core first and verify supported formats |
| Missing firmware or system file | System directory or authorized dependency | Verify official filename/hash and configured path |
| Core loads another title but not this one | Content identity or core compatibility | Audit the lawful file; do not rename it |
| Menu also disappears or log ends in video error | Frontend/video path or native crash | Return to a known-good driver and collect Android crash evidence |
An immediate return is not one diagnosis
The same visible symptom can come from a playlist choosing the wrong core, a core rejecting the file, required firmware being absent, a native crash, or a video driver that cannot restore the menu.
A direct launch removes playlist metadata from the first test. A second known-good lawful title separates a core-wide failure from one content-specific failure.
Keep the first error, not the longest log
Libretro's logging guide lets the frontend and core write to a timestamped file in the configured System Event Logs directory. The first specific error usually names the layer that triggered later shutdown messages.
Redact private storage paths, account names, and tokens before sharing a log. Do not post ROM, BIOS, save-state, or copyrighted game data with the report.
Core requirements are not interchangeable
RetroArch is a frontend; each libretro core defines supported content formats, firmware expectations, serialization, and arcade-set generation. A file that opens in one core is not proof it belongs to another.
If the log identifies missing or mismatched data, return to your own dump or an explicitly authorized provider. Downloading an unreviewed BIOS pack removes provenance and may create a second incompatibility.
Logs and error names are diagnostic evidence, not download instructions. Obtain every ROM, BIOS, CHD, key, artwork file, and soundtrack only from your own lawful source or an explicit rightsholder-authorized release.