Why RetroArch can start some cores without content on Android
RetroArch shows or honors Start Core only for a core whose current metadata declares that it supports running without content. Other cores need a lawful file in a documented format. If Start Core is absent, verify the installed core and its info metadata; if it appears but fails, capture a verbose log and check that core's official requirements instead of downloading a random ROM or BIOS pack.
Do this in order
- 01
Record the RetroArch package, core name and version, Core Information screen, and whether Start Core is visible after loading that core.
- 02
Read the core's official Libretro page and confirm whether it explicitly supports starting without content and whether firmware or other data is still required.
- 03
If no-content mode is supported, choose Start Core once with default settings and preserve the first verbose-log error if it fails.
- 04
If no-content mode is not supported, use Load Content with one lawful file whose extension and archive form match the core's official documentation.
- 05
If the menu capability contradicts the official page, verify or update the core info metadata through the package's official channel before replacing the core binary.
- 06
Retest unchanged, record the core and info versions, and redact private Android paths from any diagnostic receipt.
Decision and diagnostic table
| Observed state | Likely boundary | Next action |
|---|---|---|
| Start Core is available | Core declares no-content support | Check official requirements, then start |
| Start Core is absent | Content is required or metadata says so | Load one supported lawful file |
| Start Core fails immediately | Core runtime, firmware, or build issue | Read the first verbose-log error |
| Menu and official page disagree | Core info metadata may be stale | Verify the official package channel |
No-content support is a declared capability
It does not mean every core can boot to an internal menu. The frontend uses the installed core information to decide whether the no-file path is valid.
No game file does not mean no requirements
A core may start without content while still requiring lawful firmware, writable data directories, graphics support, or another documented dependency.
Keep capability separate from rights
A missing Start Core item never authorizes obtaining content elsewhere. Use a lawful test file only when the core actually requires content.
Use only game, firmware, artwork, and configuration files you created, dumped lawfully, or received under permission covering your use. Emulator compatibility never grants content rights; do not use unauthorized ROM, BIOS, CHD, artwork, or music mirrors.