Fix a missing RetroArch Core Downloader on Android
First enable Show Core Downloader under Settings → User Interface → Menu Item Visibility. If the item remains unavailable, identify the exact Android distribution: core availability varies by platform and package, and old Google Play builds are not the same as current retroarch.com or official F-Droid releases. Confirm that the configured cores directory is writable, then update through the same official channel or make a backed-up, deliberate migration.
Do this in order
- 01
Record the RetroArch version, package source, CPU architecture, configured cores directory, and whether existing cores still load; back up configuration, saves, states, playlists, and remaps before changing the app.
- 02
Open Settings → User Interface → Menu Item Visibility and enable Show Core Downloader, then restart RetroArch and check Online Updater again.
- 03
If the entry appears but installation fails, verify that Settings → Directory → Cores points to a location the installed package can write and that Android storage is not full.
- 04
If the entry stays absent or the list is limited, compare the installed channel with Libretro's Android guide; do not assume an old Google Play build, F-Droid build, or sideloaded APK has the same bundled and downloadable cores.
- 05
Update through the same official channel when possible; if changing channels, save a directory inventory, install only an official correctly matched architecture, and restore data selectively rather than overwriting every folder.
- 06
After restart, download one lawful test core, record its displayed version, load one authorized test item, and stop if Android package identity or signing prevents a safe in-place update.
Decision and diagnostic table
| What you see | Most likely boundary | Safe next step |
|---|---|---|
| Core Downloader hidden | Menu Item Visibility | Enable it and restart |
| Downloader visible, write fails | Cores directory or storage | Verify the configured directory and free space |
| Downloader/list differs by install | Distribution channel or architecture | Check the official Android package guide |
| Update would replace app identity | Signing/channel migration | Back up, inventory, and use the official source deliberately |
Visibility is the cheapest failure to rule out
Libretro's core installation guide places Show Core Downloader under Menu Item Visibility. The XMB map also notes that core availability varies by platform and device.
Restart after changing visibility so a stale menu is not mistaken for a missing network service. This check does not install, delete, or move a core.
The Android package defines the updater boundary
Libretro's Android guide lists retroarch.com stable/nightly APKs, buildbot architecture variants, and the official F-Droid repository. It explicitly marks the Google Play versions as not recommended because policy changes left them years behind and gave the two Play packages different core coverage.
A channel migration can change signing identity, default directories, architecture, or bundled assets. Treat it as an application migration, not a cosmetic menu repair.
A visible updater still needs a writable destination
Core download and core loading are separate stages. A network request can succeed while the configured cores directory rejects the write or points to a stale location.
Prove the path with one core and one authorized test item. Do not delete a working core library until the replacement package, directory, and core version are recorded.
The Core Downloader installs emulator cores, not commercial game content. A core's availability does not authorize ROM, BIOS, CHD, artwork, or music downloads; obtain content only from your own lawful dumps or an explicit rights-holder source.