glui_minimal_assets.zip (used by the F-Droid release) does not ship with the current autoconfig assets

Is there an existing issue for this?

• This is a bug in RetroArch frontend
• I have searched the existing issues

Description

The RetroArch.apk from retroarch.com includes the latest autoconfigs in the directory /assets/assets/autoconfig/. However, the F-Droid 1.22.2 apk and earlier lacks this ozone subdirectory within /assets/assets/, because it uses glui_minimal_assets.zip, which contains outdated autoconfigs (from 22 March 2022 at this writing (24 February 2026).

Note: As a result, the “Back” function in menus fails to work when using a Sony DualSense (PS5) controller—the current PlayStation controller—as an example of an affected device.

Temporary workaround

• Main Menu → Online Updater → Update Controller Profiles
  • Note: This has worked and not worked for me after I've reset RetroArch 1.22.2. When it didn't work and only a DualSense controller was availble with broken back button (see above note) the only way was to change the controller directory by hand in retroarch.cfg because it's not possible to change Settings → Directory → Controller Profiles since the Android release requires that you to go back to Main Menu → Quit to save configurations.

Proposed workarounds

Remove autoconfig.zip

Remove autoconfig.zip to ensure that the F-Droid build includes the full asset bundle.

Automatically update autoconfig.zip

If autoconfig.zip is to be retained, its /assets/assets/autoconfig/ directory should automatically update with the latest autoconfig files whenever a new RetroArch version is released. This ensures that F-Droid developers include the same autoconfig version in their builds as the official RetroArch release, preventing version lag.

Version/Commit

1.22.2

Bisect Results

No response

Present in the nightly version

I don't know

Platform & operating system

Android

Affected Cores

No response

Environment information

F-Droid release

Relevant log output

Start by comparing glui_minimal_assets.zip with the official APK and autoconfig.zip, then inspect how the F-Droid build selects its asset bundle. Done means the F-Droid package contains current autoconfig files, including the ozone directory, and the affected controller menu behavior is restored.