How to Use the Stock Anbernic RetroArch Configs in the Daijisho Launcher

If you've swapped the stock RG Launcher on your Android-based Anbernic handheld for Daijisho, you've probably noticed something is missing: the per-system polish. Anbernic ships a hand-tuned RetroArch config for every platform — including the custom bezels and overlays that are sized to fit the device's screen perfectly. The stock launcher quietly passes those configs to RetroArch when it boots a game. Daijisho doesn't know they exist, so you lose them.

The good news is that those config files are still sitting on your device. The stock launcher never deletes them — it just stops being the thing that points RetroArch at them. With a couple of small changes per platform, you can get Daijisho to load the exact same configs, bezels and all.

I dug these paths out of my RG Rotate over ADB, but the same approach applies to other Android Anbernic units that ship with the RG Launcher and the com.retroarch.aarch64 build of RetroArch.

How This Works

The stock RG Launcher uses the 64-bit build of RetroArch (com.retroarch.aarch64) and, for each platform, launches it with a -e CONFIGFILE argument pointing at a platform-specific retroarch.cfg. Each of those configs lives in a folder named after the platform and the exact core it's meant for, and it's what pulls in the matching bezel and display tweaks.

So there are two things you need to line up in Daijisho for each platform:

1. Use the same RetroArch 64 core the RG Launcher used. The Anbernic config for a given system is written for one specific core. If you point it at a different core, the config won't apply cleanly (and the bezel won't match).
2. Pass the Anbernic config path to RetroArch. This is done by editing the platform's launch settings in Daijisho and adding the -e CONFIGFILE ... parameter.

Step 1: Set the Platform to the Right RetroArch 64 Core

In Daijisho, open the platform you want to fix, go into its player / launch settings, and set it to launch with RetroArch 64 (com.retroarch.aarch64) using the core listed for that platform in the table below.

This is important: the config path and the core are a matched pair. The folder name in each path includes the core filename (for example snes9x_libretro_android.so for SNES), which tells you exactly which core that config was authored for.

Step 2: Add the CONFIGFILE Launch Parameter

Still in that platform's launch settings, find the RetroArch config / extra parameters field and add the -e CONFIGFILE argument for that platform. This is the part that tells RetroArch to load Anbernic's config instead of its own default.

For example, for SNES you'd add:

-e CONFIGFILE /storage/emulated/0/Android/data/com.retroarch.aarch64/files/cfg/SNES/snes9x_libretro_android.so/retroarch.cfg

Save it, launch a game, and you should see the stock Anbernic bezel snap into place.

The Config Paths for Every Platform

Here's the full list. Set each platform to the matching core, then paste in the corresponding parameter.

A Few Notes

• The core has to match. If you set a platform to a different core than the one named in its config folder, the bezel and tweaks won't line up. Stick with the pairings in the table above.
• These paths assume the stock com.retroarch.aarch64 build. If you've installed a separate copy of RetroArch (the Play Store build uses a different package name), the configs won't be there. Use the 64-bit build that shipped with the device.
• I pulled these from an RG Rotate over ADB. Other Android Anbernic units that use the RG Launcher follow the same cfg/<PLATFORM>/<core>.so/retroarch.cfg layout, so the approach should carry over even if a particular system isn't on your device.

That's it — once each platform is pointed at its stock config, Daijisho gives you the clean front-end you switched to it for and the bezels Anbernic designed for the screen.