A Retroid Pocket can become a clean, controller-friendly retro gaming system, but the finished experience depends on far more than installing a few emulator applications.
Android storage permissions must be granted correctly. Game folders need to be organised before they are scanned. BIOS files must contain the correct data, use the filenames expected by the relevant emulator or core and be placed in the right directory. Each emulator needs its own controller, graphics, save and library configuration, and more demanding systems must be tested game by game rather than forced to use one universal performance profile.
This guide covers the:
- Retroid Pocket 5.
- Retroid Pocket Flip 2 Snapdragon 865.
- Retroid Pocket Flip 2 Dimensity 1100.
- Retroid Pocket Classic.
- Retroid Pocket 6.
- Retroid Pocket Nova.
Retroid Pocket Nova status: At the time of writing in July 2026, Retroid states that Nova shipments are due to begin at the end of July. Its hardware specifications are confirmed, but its model-specific interface and performance guidance should be treated as provisional until production handhelds are available with final retail firmware.
The emulator setup used throughout this guide is:
- PlayStation: DuckStation.
- PlayStation 2: NetherSX2.
- Nintendo 64: Mupen64Plus FZ.
- Dreamcast: Redream.
- PSP: PPSSPP.
- Nintendo DS: melonDS.
- Nintendo 3DS: Azahar, the maintained successor to Citra.
- GameCube & Wii: Dolphin.
- Point-and-click adventure games: ScummVM.
- Older cartridge, handheld and arcade systems: RetroArch.
This guide includes setup instructions for both Retroid Launcher and Daijisho. Both frontends can remain installed at the same time, but only one can be selected as Android’s Home application at once.
Game and firmware files are not included with these emulators. Use game backups and BIOS or firmware dumped from hardware you own.
In This Article
- Important Differences Between Retroid Models
- The Correct Setup Order
- Complete First Boot Properly
- Install Official Retroid Updates
- Update Retroid Launcher
- Switch To Three-Button Navigation
- Configure Android
- Configure The Retroid Controls
- Performance & Cooling Modes
- Prepare The microSD Card
- Transfer Files From A Computer
- Create The Folder Structure
- Recommended Game Formats
- Configure Multi-Disc Games
- BIOS & Firmware Explained
- Exact RetroArch BIOS Filenames
- Verify BIOS Files
- Install The Emulator Applications
- Safely Install APK Files
- Configure RetroArch
- Configure DuckStation
- Configure Mupen64Plus FZ
- Configure Redream
- Configure PPSSPP
- Configure melonDS
- Configure Azahar For Nintendo 3DS
- Configure Dolphin
- Configure NetherSX2
- Configure ScummVM
- Configure Retroid Launcher
- Configure Daijisho
- Set The Correct Retroid Launcher File Suffixes
- Set Retroid Launcher Or Daijisho As The Home Application
- Recommended Starting Settings By Model
- Normal Saves, Save States & Backups
- Update Emulators Without Breaking The Setup
- Detailed Troubleshooting
- Final Setup Checklist
- Official Downloads & Documentation
Important Differences Between Retroid Models
The same applications can be installed across these Retroid handhelds, but they should not all receive identical performance or controller settings.
| Model | Processor & Graphics | Android | Important Setup Difference |
|---|---|---|---|
| Retroid Pocket 5 | Snapdragon 865 with Adreno 650 | Android 13 | Use the Adreno-focused NetherSX2 4248 branch. Suitable for dual-stick systems and analogue-trigger GameCube games. |
| Retroid Pocket Flip 2 SD865 | Snapdragon 865 with Adreno 650 | Android 13 | Use NetherSX2 4248. Test lid-close sleep and resume separately in every emulator. |
| Retroid Pocket Flip 2 D1100 | Dimensity 1100 with Mali-G77 graphics | Android 13 | Use NetherSX2 Classic 3668. Vulkan remains the first test, but OpenGL may behave better in individual games with Mali graphics. |
| Retroid Pocket Classic | Snapdragon G1 Gen 2 with Adreno A12 | Android 14 | No analogue sticks. Prioritise D-pad systems, PlayStation games that do not require analogue input and point-and-click games. Use NetherSX2 Classic 3668 only for lighter, control-suitable games. |
| Retroid Pocket 6 | Snapdragon 8 Gen 2 with Adreno 740 | Android 13 | Use NetherSX2 4248. Higher internal resolutions are practical, but native or low-resolution testing should still come first. |
| Retroid Pocket Nova | QCS8550 with Adreno 740 | Android 13 | Use NetherSX2 4248. Model-specific recommendations remain provisional until final retail firmware is available. |
The Correct Setup Order
Complete the setup in this order:
- Charge the handheld.
- Complete the Android welcome process.
- Restart the handheld once.
- Install every available Retroid firmware update.
- Update Retroid Launcher.
- Choose the Android navigation style.
- Choose the Retroid controller style and trigger mode.
- Configure Android display and battery behaviour.
- Format and test the microSD card.
- Create the ROM, BIOS, saves and backup folders.
- Copy one or two test games for each system.
- Install the emulator applications from their official sources.
- Configure and test each emulator directly.
- Create and reload a normal in-game save in each emulator.
- Configure Retroid Launcher, Daijisho or both one platform at a time.
- Test direct game launching and returning to the selected frontend.
- Back up the complete working configuration.
Do not begin by scanning the entire library into a frontend. Retroid Launcher and Daijisho can organise games and send them to an emulator, but neither can correct a missing BIOS, unsupported file format, invalid controller profile or missing Android folder permission.
Complete First Boot Properly
Switch the Retroid Pocket on and follow the welcome screens shown automatically.
Select the correct language, region and time zone, then connect to Wi-Fi. Enable Google services and sign in to a Google account if you intend to install applications through Google Play.
The setup wizard may offer to install a selection of emulator applications. The available list can differ between Retroid models and firmware revisions.
Because this guide installs current builds from their official sources, leave unfamiliar or duplicate emulator entries unticked. Retroid Launcher can be selected because it is used later in this guide.
Continue until the normal Android or Retroid Home screen appears. Check that the status bar shows the correct time and an active Wi-Fi connection.
Hold the power button, select Restart and allow Android to load again. This confirms that the first-run setup has finished correctly before firmware or emulator configuration begins.
If the wrong language was selected, open:
Settings > System > LanguagesSelect System Languages, add the correct language if necessary, then drag it to the top of the list. Move the original language back to the top to reverse the change.
If the time or time zone is incorrect, open:
Settings > System > Date & TimeEnable automatic date and time and automatic time zone. The status bar should update within a few seconds. These options can be switched off again if a manual clock is required.
Remove An Emulator Installed By Mistake
Open Settings > Apps > See All Apps and select the unwanted emulator.
Select Uninstall, confirm the warning and wait for the application to disappear from the installed-app list.
Before uninstalling an emulator that has already been used, export or back up its normal saves. Reinstalling the same application later does not guarantee that Android will preserve its previous data.
Install Official Retroid Updates
Open the Android Settings application, scroll down and select:
Settings > System > Retroid Pocket FOTASelect Check Version.
The FOTA screen should either report that the installed version is current or display a newer firmware version with an option to download it.
If an update is available:
- Connect the handheld to its charger.
- Confirm that Wi-Fi is connected.
- Select the download option shown by FOTA.
- Wait until the download reaches 100%.
- Select Install or the equivalent restart-and-install option.
- Leave the handheld connected to power while it restarts.
- Do not press the power button during installation.
- After Android loads, return to Settings > System > Retroid Pocket FOTA.
- Select Check Version again.
Continue checking until FOTA reports that no newer version is available.
If Retroid Pocket FOTA Is Missing
Return to the main Settings page, select the search box and search for:
FOTA
If there is no result, search for:
update
Open the result named Retroid Pocket FOTA or the closest Retroid-specific update entry.
Handheld Settings is not normally the firmware-update page. Handheld Settings contains Retroid-specific controller, trigger, fan, display-output and background-process options. Firmware updates are handled through the FOTA entry under System on current Retroid firmware.
If Check Version Fails
Open a webpage or Google Play to confirm that Wi-Fi is working.
Then open:
Settings > System > Date & TimeEnable automatic date, time and time zone. Return to FOTA and select Check Version again.
If the update still fails, restart the handheld and retry. Do not install a firmware package intended for a different Retroid model.
Undoing A Firmware Update
Opening FOTA and checking the version changes nothing. You can press Back before downloading or installing an available update.
Once installation begins, do not interrupt it. Retroid FOTA does not provide a normal one-button rollback. A failed or unwanted firmware installation requires a recovery procedure made specifically for the exact Retroid model and hardware revision.
Update Retroid Launcher
Connect the handheld to Wi-Fi and open Retroid Launcher.
On the launcher’s main screen, highlight and open the circular red-and-white icon that resembles a Poké Ball. It is normally the second icon from the left.
Select Update.
If a newer launcher build is available, follow the prompts to download and install it. Once complete, reopen Retroid Launcher and return to the same update page. It should report that the current version is installed or no longer offer the same update.
If Android asks whether the launcher may install an update, allow the permission only for the current installation. The permission can be removed afterwards under:
Settings > Apps > Special App Access > Install Unknown AppsSelect Retroid Launcher and disable Allow From This Source.
An updated launcher may alter platform definitions or interface behaviour. Before installing future launcher updates, back up the launcher data if the version provides an export option and photograph or record any custom platform Config and Suffix settings.
Switch To Three-Button Navigation
Open:
Settings > System > Gestures > System NavigationOn some firmware versions, the final entry is called Navigation Mode.
Select 3-Button Navigation.
Back, Home and Recent Apps buttons should appear along the bottom edge of the screen.
Open Settings and press Back to confirm that it returns to the previous page. Press Home to return to the launcher. Open an application, press Recent Apps and confirm that the open application appears.
If the option is not shown in the path above, return to the main Settings page and search for:
navigation
Open System Navigation or Navigation Mode from the results.
Three-button navigation is useful during setup because the Back button provides a consistent way to open emulator menus or return from Android folder pickers.
To restore gesture navigation, return to the same page and select Gesture Navigation. If the three buttons fail to appear after being selected, restart the handheld and check the option again.
Configure Android
Increase The Screen Timeout
Open:
Settings > Display > Screen TimeoutSelect five or ten minutes while setting up the handheld.
The chosen duration should appear beneath Screen Timeout. Leave the handheld untouched and confirm that the display does not switch off before the selected period has passed.
After configuration is complete, return to the same page and select a shorter duration if preferred.
Disable Automatic Rotation During Setup
Swipe down twice from the top edge of the screen to open the full Quick Settings panel.
Tap Auto-Rotate. Hold the handheld in landscape while doing this so the tile changes to a locked landscape state where supported.
Rotate the device gently. Android should remain in the chosen orientation.
To restore automatic rotation, open Quick Settings and tap the same tile until it reads Auto-Rotate.
If the tile is not visible, select the pencil or Edit control in Quick Settings and drag Auto-Rotate into the active tile area.
Keep Android Battery Optimisation Enabled Initially
Do not make every emulator unrestricted during initial setup. Most should work correctly with Android’s normal Optimised setting.
If a library scan stops when the screen switches off, an emulator is removed from memory immediately or a frontend restarts after returning from a game, open:
Settings > Apps > See All Apps > Application Name > BatteryThe final option may be called App Battery Usage.
Select Unrestricted, repeat the action that was failing and confirm whether the application now remains open.
If the problem continues or battery consumption increases, return to the same page and select Optimised.
Do Not Enable Aggressive Process Cleaning
Open:
Settings > Handheld Settings > PowerReview Clean Process When Standby and Background Process Limit.
Leave aggressive cleaning disabled while configuring emulators. A strict background-process limit can close Retroid Launcher, Daijisho or an emulator while Android’s file picker is open.
After setup, these options can be tested one at a time. If an emulator starts forgetting its place, library scans stop or the selected frontend repeatedly reloads, return to Handheld Settings and restore the previous value.
Configure The Retroid Controls
Choose The Controller Style
Open:
Settings > Handheld Settings > Input > Controller StyleSelect the Nintendo-style or Xbox-style layout you intend to keep.
This changes how Android reports the physical face buttons. It should be set before creating emulator controller profiles.
Open the Retroid input tester from Handheld Settings > Input Control, or open the controller test supplied by the firmware.
Press A, B, X and Y one at a time. The on-screen tester should highlight the input corresponding to the selected controller style.
To reverse the change, return to Controller Style and select the previous layout. Any emulator or frontend hotkey configured before the change must then be checked again.
Choose The Trigger Mode
On models with analogue triggers, open:
Settings > Handheld Settings > Input > L2/R2 ModeSelect the analogue or combined analogue-and-digital mode recommended by the firmware for games that use gradual trigger movement.
Open the controller tester and squeeze L2 and R2 slowly. The displayed value should increase gradually rather than changing immediately from released to fully pressed.
GameCube games can distinguish between a partial trigger pull and the final digital click. If Dolphin cannot detect both states, return to L2/R2 Mode and test the combined mode before remapping the triggers in Dolphin.
To restore the original behaviour, return to L2/R2 Mode and select the previous option, then retest trigger mappings inside Dolphin and other affected applications.
Test Every Physical Control
Use the Retroid input tester to check:
- D-pad in all four directions.
- A, B, X and Y.
- L1 and R1.
- L2 and R2.
- Start and Select.
- Left and right analogue sticks on supported models.
- L3 and R3.
Move each analogue stick slowly around its complete range and release it. The displayed position should return to the centre.
If an input is incorrect in the Retroid tester, correct the global Retroid setting before configuring an emulator. Emulator remapping should not be used to conceal a system-wide controller fault.
Performance & Cooling Modes
Swipe down twice from the top edge of the screen to open the full Quick Settings panel.
Locate the Retroid performance tile. Depending on the model and firmware, it may cycle through names such as:
- Standard.
- Balanced.
- Performance.
- High Performance.
Tap the tile until the required mode is displayed.
Use Standard for older cartridge and handheld systems. Start Nintendo 64, Dreamcast, PSP and Nintendo DS in Standard or Balanced mode. Begin demanding GameCube, Wii, PlayStation 2 and Nintendo 3DS games in Balanced mode, moving to High Performance only when the emulator cannot maintain full speed at conservative settings.
On models with active cooling, locate the fan tile and use Smart or automatic cooling for normal use. A stronger fan profile may be selected when running High Performance mode for an extended period.
The performance tile should display the selected mode. On actively cooled models, the fan may become audible as the processor warms.
Test a demanding section of the game for at least fifteen minutes. Watch for repeating audio crackle, slow motion or unstable frame pacing.
To reverse the change, return the performance tile to Standard and the fan to Smart or automatic.
If higher performance does not improve the game, restore Standard mode. The problem may instead be caused by internal resolution, renderer compatibility, shader compilation or a damaged game image.
Prepare The microSD Card
Format The Card As Portable Storage
Insert the microSD card into the powered-on Retroid Pocket.
Tap the notification stating that a new storage device has been detected. If no notification appears, open:
Settings > StorageSelect the microSD card, then choose Set Up or Format.
Select Portable Storage, confirm the warning and wait for formatting to finish.
The card should appear separately from internal storage in Settings and in the Files application. Its usable capacity will be slightly lower than the capacity printed on the card.
Do not choose internal or adopted storage for a removable game card. Adopted storage is tied more closely to the Android installation and is harder to manage on a computer.
Formatting erases the card. It cannot be reversed. To format it again later, first copy everything you need to another drive, then return to Settings > Storage, select the card and use its Format option.
Test The Card Before Copying The Library
Open the Android Files application and select the microSD card.
Open the three-dot menu, select New Folder, enter:
Card Test
Select Create or Done.
Copy a small image or text file into Card Test, open it and then delete both the file and the folder.
The folder should be created immediately, the file should open correctly and both should delete without an error.
If writing fails, restart the handheld and repeat the test. If it fails again, reformat or replace the card before copying a large library.
Safely Remove The Card
Before removing a card while Android is running, open:
Settings > Storage > microSD CardSelect Eject or Unmount.
Android should report that the card is safe to remove and it should disappear from the active storage list.
Reinsert the card to mount it again. If it does not reappear, restart the handheld.
Transfer Files From A Computer
Using A Card Reader
The simplest method is to switch the Retroid Pocket off, remove the microSD card and insert it into a computer using a card reader.
Open File Explorer and select the card under This PC.
After copying files, right-click the card in File Explorer and select Eject. Wait for Windows to report that it is safe to remove, then return the card to the Retroid Pocket.
Using A USB Cable
Connect the powered-on Retroid Pocket to the computer with a USB data cable.
Swipe down from the top of the Retroid screen and tap the notification reading Charging This Device Via USB or similar.
Select File Transfer or File Transfer / Android Auto.
The Retroid Pocket should appear in Windows File Explorer. Open it, select the microSD card and copy the required files.
When finished, close any open files, use Windows’ eject control where available and disconnect the cable.
To return USB behaviour to charging only, open the same Android USB notification and select No Data Transfer.
If the handheld does not appear on the computer, try another USB cable. Many charging cables do not contain the data connections required for file transfer.
Create The Folder Structure
Create the following structure on the microSD card:
Retroid
├── BIOS
│ ├── DuckStation
│ ├── melonDS
│ ├── NetherSX2
│ └── RetroArch
│
├── ROMs
│ ├── Arcade
│ ├── Atari 2600
│ ├── Dreamcast
│ ├── Game Boy
│ ├── Game Boy Advance
│ ├── Game Boy Color
│ ├── Game Gear
│ ├── GameCube
│ ├── Master System
│ ├── Mega Drive
│ ├── Neo Geo
│ ├── NES
│ ├── Nintendo 64
│ ├── Nintendo DS
│ ├── Nintendo 3DS
│ ├── PC Engine
│ ├── PC Engine CD
│ ├── PlayStation
│ ├── PlayStation 2
│ ├── PSP
│ ├── ScummVM
│ ├── Sega CD
│ ├── SNES
│ └── Wii
│
├── Saves
│ ├── RetroArch
│ │ ├── Saves
│ │ └── States
│ ├── melonDS
│ ├── PPSSPP
│ └── ScummVM
│
└── Backups
├── Daijisho
├── Emulator Data
└── Retroid Launcher
On a computer, right-click empty space inside the card, select New > Folder and enter each folder name exactly as shown.
Open several of the folders afterwards and confirm they are in the correct parent directory. For example, PlayStation must be inside ROMs, not beside it.
Empty folders can be renamed or deleted. However, renaming a folder after an emulator or frontend has been granted access to it breaks that stored path. Remove the old path and add the renamed folder again.
Use Clear Game Filenames
Use:
Game Title (Region) (Revision).extension
Examples:
Super Mario World (Europe).sfc The Legend of Zelda - The Wind Waker (Europe).rvz Final Fantasy VII (Europe) (Disc 1).chd
Avoid adding website names, release-group tags, random numbering or phrases such as “GOOD DUMP”. These make the library harder to read and reduce automatic artwork-matching accuracy.
Recommended Game Formats
| System | Recommended Format | Important Detail |
|---|---|---|
| Game Boy | GB | Leave uncompressed for straightforward scanning. |
| Game Boy Color | GBC | Leave uncompressed. |
| Game Boy Advance | GBA | Leave uncompressed. |
| NES | NES | The ROM header must identify the cartridge hardware correctly. |
| SNES | SFC or SMC | SFC is commonly used for headerless images. |
| Master System | SMS | Leave cartridge files uncompressed. |
| Game Gear | GG | Leave cartridge files uncompressed. |
| Mega Drive | MD or GEN | BIN is supported but can be confused with CD track files in mixed folders. |
| Sega CD | CHD or CUE/BIN | The regional Sega CD BIOS is required. Multi-disc games should use M3U playlists. |
| PC Engine | PCE | Leave cartridge files uncompressed. |
| PC Engine CD | CHD or CUE/BIN |
syscard3.pce is the recommended BIOS. |
| Arcade & Neo Geo | ZIP | Keep archives zipped and use a set matching the installed FinalBurn Neo core. |
| Nintendo 64 | Z64 | N64 and V64 are also supported by Mupen64Plus FZ. |
| PlayStation | CHD | Use M3U playlists for multi-disc games. CUE/BIN also works when track filenames are correct. |
| Dreamcast | CHD or GDI | Redream strongly discourages CDI where a better dump is available. |
| PSP | ISO or CHD | CSO saves space but can add decompression overhead. |
| Nintendo DS | NDS | Uncompressed NDS files are easiest to manage and launch from a frontend. |
| Nintendo 3DS | A game image recognised by the installed Azahar build | CIA packages are installed inside Azahar rather than treated as ordinary loose ROMs. |
| GameCube | RVZ | RVZ provides lossless compression designed for Dolphin. |
| Wii | RVZ | WBFS and ISO are also supported. |
| PlayStation 2 | CHD or ISO | Test unusual and dual-layer games individually. |
| ScummVM | Original game data files | Place each game in its own folder. |
Configure Multi-Disc Games
PlayStation M3U Playlist
Place every disc for one game in the same folder:
Final Fantasy VII (Europe) (Disc 1).chd Final Fantasy VII (Europe) (Disc 2).chd Final Fantasy VII (Europe) (Disc 3).chd
Open Notepad and enter the exact filename of each disc on its own line:
Final Fantasy VII (Europe) (Disc 1).chd Final Fantasy VII (Europe) (Disc 2).chd Final Fantasy VII (Europe) (Disc 3).chd
Select File > Save As, set Save As Type to All Files and save the file as:
Final Fantasy VII (Europe).m3u
Enable file extensions in Windows using View > Show > File Name Extensions. Confirm that the file is not named Final Fantasy VII (Europe).m3u.txt.
Launch the M3U file in DuckStation rather than opening the individual disc files.
When a disc change is requested, open DuckStation’s pause menu, select the disc-change option and choose the next disc from the playlist.
Deleting the M3U file removes the playlist but does not alter the disc images. If it fails to launch, open it in Notepad and compare every line with the actual filenames, including spaces, punctuation and extensions.
Sega CD Multi-Disc Games
Create an M3U file in the same way, listing each CHD or CUE file in the correct order.
While the game is running in RetroArch, open:
Quick Menu > Disk ControlSelect Eject Disc, change Current Disc Index and then select Insert Disc.
If the wrong disc is selected, eject it again and restore the previous index.
BIOS & Firmware Explained
Three things determine whether a BIOS works:
- The file must contain the correct firmware data.
- It must use the filename expected by an emulator that searches automatically.
- It must be in the directory that the emulator is actually using.
Renaming an invalid file does not turn it into a valid BIOS.
Emulators That Import A BIOS
DuckStation and NetherSX2 allow you to browse to a BIOS dump and import it. There is no single universal filename that every valid PlayStation or PlayStation 2 BIOS must use.
The important confirmation is that the emulator identifies and accepts the selected file.
Emulators That Do Not Require A Conventional BIOS
- PPSSPP: does not require a PSP BIOS.
- Redream: includes a replacement Dreamcast BIOS for ordinary game launching.
- Dolphin: does not require a separate GameCube or Wii BIOS to launch normal retail games.
- Mupen64Plus FZ: does not require an external Nintendo 64 BIOS.
- Azahar: does not use one universal file called a 3DS BIOS.
- ScummVM: uses the original data files from supported games rather than a console BIOS.
- melonDS: can run normal Nintendo DS games using internal replacement firmware. Original DS files are optional unless original firmware behaviour or DSi mode is required.
Exact RetroArch BIOS Filenames
| System & Core | Exact Filename | Requirement | MD5 |
|---|---|---|---|
| Game Boy boot ROM — Gambatte | dmg_boot.bin |
Optional | 32fbbd84168d3482956eb3c5051637f5 |
| Game Boy Color boot ROM — Gambatte | cgb_boot.bin |
Optional | dbfce9db9deaa2567f6a84fde55f9680 |
| Game Boy Advance BIOS — mGBA | gba_bios.bin |
Optional | a860e8c0b6d573d191e4ec7db1b1e4f6 |
| Mega Drive startup ROM — Genesis Plus GX | bios_MD.bin |
Optional | 45e298905a08f9cfb38fd504cd6dbc84 |
| Mega CD Europe — Genesis Plus GX | bios_CD_E.bin |
Required for European Mega CD games | e66fa1dc5820d254611fdcdba0662372 |
| Sega CD USA — Genesis Plus GX | bios_CD_U.bin |
Required for US Sega CD games | 854b9150240a198070150e4566ae1290 |
| Mega CD Japan — Genesis Plus GX | bios_CD_J.bin |
Required for Japanese Mega CD games | 278a9397d192149e84e820ac621a8edd |
| Master System Europe — Genesis Plus GX | bios_E.sms |
Optional | 840481177270d5642a14ca71ee72844c |
| Master System USA — Genesis Plus GX | bios_U.sms |
Optional | 840481177270d5642a14ca71ee72844c |
| Master System Japan — Genesis Plus GX | bios_J.sms |
Optional | 24a519c53f67b00640d0048ef7089105 |
| Game Gear — Genesis Plus GX | bios.gg |
Optional | 672e104c3be3a238301aceffc3b23fd6 |
| PC Engine CD — Beetle PCE Fast | syscard3.pce |
Required for Super CD-ROM² games | 38179df8f4ac870017db21ebcbf53114 |
| Neo Geo — FinalBurn Neo | neogeo.zip |
Required for applicable Neo Geo sets | Must match the installed FinalBurn Neo ROM set |
Place these files directly inside:
Retroid/BIOS/RetroArch
Do not extract neogeo.zip. The archive and the files inside it must match the ROM-set version expected by FinalBurn Neo.
melonDS Original Firmware Files
Original Nintendo DS firmware is optional for ordinary DS game launching. When original firmware boot is required, the selected DS BIOS folder must contain:
-
bios7.bin— 16KB. -
bios9.bin— 4KB. -
firmware.bin— normally 256KB for a regular DS or 512KB for an iQue DS.
DS-mode firmware dumped from a DSi or 3DS can be 128KB and is not suitable for fully booting the original DS firmware menu. Direct Boot should be used with that type of firmware.
DSi mode additionally requires matching DSi BIOS, firmware and NAND data. Configure normal DS mode successfully before attempting DSi mode.
Verify BIOS Files
Show File Extensions In Windows
Open File Explorer and select:
View > Show > File Name ExtensionsWindows should now display extensions such as .bin, .pce and .zip.
Confirm that a file shown as bios7.bin is not actually named bios7.bin.bin.
To hide extensions again, return to View and untick File Name Extensions. Keeping them visible is recommended while managing emulator files.
Calculate An MD5 Hash
Open the BIOS folder in File Explorer.
Click the address bar, type:
powershell
Press Enter.
Enter a command such as:
Get-FileHash ".\gba_bios.bin" -Algorithm MD5
PowerShell should display the file path and a hexadecimal hash.
Compare the hash character for character with the value in the BIOS table. Letter case does not matter, but every number and letter must otherwise match.
This command only reads the file. It does not alter it. Close PowerShell when finished.
Check Firmware Recognition In RetroArch
Open RetroArch and select Load Core.
Select the core being checked, then open:
Main Menu > Information > Core InformationScroll to the firmware section.
Correctly recognised files should be marked Present. Missing files should be marked Missing beside the exact filename RetroArch expects.
If a required file remains missing, check the configured System/BIOS path, filename and MD5 hash, then fully close and reopen RetroArch.
Install The Emulator Applications
| Application | Recommended Source | Important Current Note |
|---|---|---|
| RetroArch | Official RetroArch Android download | Use the official 64-bit AArch64 build. Do not use the Google Play edition with Daijisho. |
| DuckStation | Official DuckStation download | Preserve a known-working installer and configuration. |
| Mupen64Plus FZ | Official Google Play listing | The free and paid editions may appear as different frontend players. |
| Redream | Official Redream download | No external Dreamcast BIOS is required for normal launching. |
| PPSSPP | Official PPSSPP download | PPSSPP and PPSSPP Gold provide the same emulation functionality. |
| melonDS | Official melonDS Android project | Use the current stable Android release. |
| Azahar | Official Azahar project | The Google Play and Vanilla builds use different Android package identities. |
| Dolphin | Official Dolphin release | Use the latest stable release unless a development build contains a fix you specifically need. |
| NetherSX2 | Official NetherSX2 patch project | Use 4248 for powerful Adreno devices and Classic 3668 for Mali or less powerful hardware. |
| ScummVM | Official ScummVM download | ScummVM requires the original game data. |
| Daijisho | Official Daijisho Google Play listing | Daijisho is a frontend and does not include emulators or games. |
After installing an emulator, open it once. It should reach its setup wizard or main screen without crashing.
Do not add it to Retroid Launcher or Daijisho until it has successfully launched a test game directly.
Safely Install APK Files
Applications such as NetherSX2, RetroArch and the Vanilla build of Azahar may be supplied as APK files rather than installed directly through Google Play.
Download the APK from the project’s official release page.
Open the Android Files application, select Downloads and tap the APK.
If Android blocks the installation, select Settings on the warning screen. Enable Allow From This Source for the Files application or browser that opened the APK.
Return to the installer and select Install.
When installation finishes, select Open. The emulator should reach its setup screen.
Remove the temporary installation permission afterwards:
Settings > Apps > Special App Access > Install Unknown AppsSelect the Files application or browser used for installation and disable Allow From This Source.
If the wrong APK was installed, open Settings > Apps > See All Apps, select the application and choose Uninstall. Back up its data before uninstalling if it has already been configured.
Configure RetroArch
Update RetroArch’s Support Files
Open:
Main Menu > Online UpdaterSelect each of the following, waiting for it to finish before selecting the next:
- Update Core Info Files.
- Update Assets.
- Update Controller Profiles.
- Update Databases.
A completion message should briefly appear after each update.
If Core Downloader is hidden, open:
Settings > User Interface > Menu Item VisibilityEnable Show Core Downloader, then return to Online Updater.
To hide it later, disable the same option.
Install The Recommended Cores
Open:
Main Menu > Online Updater > Core DownloaderInstall:
- Gambatte: Game Boy and Game Boy Color.
- mGBA: Game Boy Advance.
- Mesen: NES.
- Snes9x Current: SNES.
- Genesis Plus GX: Master System, Game Gear, Mega Drive and Sega CD.
- Beetle PCE Fast: PC Engine and PC Engine CD.
- FinalBurn Neo: supported arcade and Neo Geo games.
- Stella 2014: Atari 2600.
Return to Load Core. Every installed core should appear in the list.
Set The BIOS Directory
Open:
Settings > Directory > System/BIOSBrowse to:
Retroid/BIOS/RetroArch
Select Use This Folder and approve access if Android asks.
The System/BIOS entry should now display the selected directory.
Load a core and open Core Information to confirm that its firmware is marked Present.
To restore the previous BIOS directory, return to Directory and select the original location. Keep a record of the old path before changing it.
Set Save Directories
Open:
Settings > DirectorySet Save Files to:
Retroid/Saves/RetroArch/Saves
Set Save States to:
Retroid/Saves/RetroArch/States
The selected paths should appear beside both entries.
Changing these paths does not move existing saves. If RetroArch has already been used, copy the old save and state files into the new folders before changing the directory.
To reverse the change, restore the old directories and move the files back before launching a game.
Configure Port 1
Open:
Settings > Input > RetroPad Binds > Port 1 ControlsPress each physical control and confirm that its displayed binding is correct.
The RetroPad names describe RetroArch’s virtual controller, not the labels printed on every original console. Test the physical positions in a game before changing them unnecessarily.
If the entire mapping is wrong, use the reset or auto-configure option shown by the current menu. The control used to reset an individual binding is displayed in RetroArch’s footer and is commonly Start.
Configure Hotkeys
Open:
Settings > Input > HotkeysUse this starting layout on models with analogue sticks:
- Hotkey Enable: Select.
- Menu Toggle: X or L3.
- Save State: R1.
- Load State: L1.
- Fast Forward Toggle: R2.
- Close Content: Start.
These become combinations. Save State is therefore Select + R1 rather than R1 by itself.
On the Pocket Classic, choose an unused face or shoulder combination instead of L3 where necessary.
Launch a test game and press Select + R1. A save-state notification should appear. Press Select + L1 and confirm that the state reloads.
To remove a hotkey, return to Hotkeys, highlight its binding and use the reset control shown at the bottom of the screen.
Save The Global Configuration
Open:
Main Menu > Configuration File > Save Current ConfigurationA confirmation message should appear.
If an unwanted global change has been saved, return the affected setting to its previous value and save the current configuration again.
Use Core, Folder & Game Overrides Correctly
Launch a game and open:
Quick Menu > Overrides- Save Core Override: applies to every game using that core.
- Save Content Directory Override: applies to games in the current folder.
- Save Game Override: applies only to the current game.
Use a Game Override when only one title needs a different aspect ratio, shader or latency option.
To reverse it, return to Quick Menu > Overrides and select the option to remove or unload the active override. If that command is not shown, restore the global value and save a new game override containing the corrected setting.
Remap Controls For One Core Or Game
Launch the content and open:
Quick Menu > ControlsChange the required controls, then open Manage Remap Files.
Select Save Core Remap File for every game using that core or Save Game Remap File for the current game only.
To remove it, return to Manage Remap Files and delete the relevant remap file.
FinalBurn Neo ROM-Set Rule
Keep arcade and Neo Geo game archives zipped.
The game archive, parent ROMs and BIOS archive must match the FinalBurn Neo database used by the installed core.
Renaming a random MAME ZIP does not make it compatible with FinalBurn Neo.
If the core reports missing files, restore the original archive and use a matching ROM set. Do not extract files from several different sets and combine them manually.
Configure DuckStation
Complete The Setup Wizard
Open DuckStation and follow its first-run wizard.
When asked for a BIOS, select the import option, browse to:
Retroid/BIOS/DuckStation
Select the uncompressed BIOS dump.
DuckStation should identify the BIOS and display its region or description. If it reports that the file is invalid, renaming it will not help. Replace it with a correctly dumped BIOS.
When asked for a game directory, select:
Retroid/ROMs/PlayStation
Choose Use This Folder and approve access.
The PlayStation test games should appear in DuckStation’s library after the scan completes.
Change The BIOS Later
Open DuckStation’s menu and go to:
App Settings > BIOSImport or select the replacement BIOS.
Launch a known-working game and confirm it reaches the PlayStation boot or game screen.
To reverse the change, return to BIOS settings and reselect the previous accepted BIOS.
Configure Controller Port 1
Open:
Controller Settings > Port 1Select DualShock, then use Automatic Mapping and choose the Retroid controller.
Check:
- D-pad.
- Cross, Circle, Square and Triangle.
- L1, R1, L2 and R2.
- Start and Select.
- Both analogue sticks.
- L3 and R3.
Each input should register beside the corresponding PlayStation control.
If the mapping is incorrect, use Clear Mapping or Reset Mapping on the same page and run Automatic Mapping again.
A small number of early PlayStation games expect a digital controller. Long-press that game in DuckStation, open its Properties and set the controller type to Digital Controller for that game only. Remove the game-specific setting to return it to the global DualShock profile.
Set A Stable Graphics Baseline
Open:
App Settings > GraphicsUse:
- Renderer: Vulkan.
- Aspect Ratio: Auto or 4:3.
- Widescreen Hack: Off.
- PGXP: Off for initial testing.
- Texture Filtering: Nearest or Bilinear.
Start with these internal resolutions:
- Pocket Classic: 2x.
- Pocket 5 & Flip 2: 3x.
- Pocket 6 & Nova: 4x.
Launch a test game. It should run at full speed in a correctly proportioned 4:3 image.
Once stable, enable PGXP Geometry Correction for an individual game if you want to reduce polygon wobble. Long-press the game, open Properties and enable the feature there.
If graphics break, disable PGXP and widescreen options, return internal resolution to 1x and test OpenGL. Remove the game Properties override to restore global settings.
Configure Memory Cards
Open DuckStation’s Memory Card settings.
Use one card per game for simple organisation or shared cards when games need to detect data from another title.
Create a normal save using the game’s own menu, fully close DuckStation, reopen it and load the game again. The save should appear in the game’s Load or Continue menu.
If it is missing, confirm that the same regional game image and the same memory-card type are being used.
PAL LibCrypt Games
Some PAL PlayStation games require an SBI subchannel file.
Place the SBI beside the game image and give it the same base filename:
Game Name.chd Game Name.sbi
DuckStation should load it automatically.
If the game still hangs at a protection check, compare both filenames exactly. Removing the SBI returns the game to its previous behaviour without altering the disc image.
Configure Mupen64Plus FZ
Add The Nintendo 64 Folder
Open Mupen64Plus FZ and tap the plus button.
Select Select Folder, browse to:
Retroid/ROMs/Nintendo 64
Select Use This Folder and approve access.
The test games should appear in the library after scanning.
To remove the folder, open Mupen’s library or ROM settings, clear the current ROM path and rescan. This removes the library entries without deleting the game files.
Create A Retroid Controller Profile
Open:
Profiles > Controller > Manage ProfilesSelect New, name the profile Retroid and map:
| Nintendo 64 Input | Retroid Input |
|---|---|
| Analogue Stick | Left Analogue Stick |
| D-pad | D-pad |
| A | Lower face button |
| B | Left face button |
| C-Up | Right Stick Up |
| C-Down | Right Stick Down |
| C-Left | Right Stick Left |
| C-Right | Right Stick Right |
| L | L1 |
| R | R1 |
| Z | L2 or R2 |
| Start | Start |
Save the profile, then open:
Profiles > Select Profiles > Controller 1 ProfileSelect Retroid.
Launch a test game. The left stick should move the character and the right stick should operate the C buttons.
To reverse the mapping, return to Controller 1 Profile and choose the previous profile. Do not delete Retroid until another working profile is active.
The Pocket Classic has no analogue sticks, making many Nintendo 64 games unsuitable without an external controller. A game-specific profile can map the Nintendo 64 stick to the D-pad for titles that tolerate digital movement, but this should not be used as the global configuration.
Select An Emulation Profile
Open:
Profiles > Select Profiles > Emulation ProfileStart with the application’s recommended default or a GlideN64 accurate profile.
Launch a game and check menus, shadows, framebuffer effects and performance.
To change only one game, select the game once, open its Settings and choose a different Emulation Profile.
The selected game should retain the new profile while other games use the global setting.
Return the game to Global Default to remove the override.
Change Rendered Resolution
Open Mupen’s Display or Emulation Profile settings and locate Rendered Resolution.
Start with the default value. Increase it one step and test a demanding area.
If speed falls or graphics break, restore the previous resolution. Use a game-specific profile rather than reducing the entire library for one difficult title.
Configure Redream
Add The Dreamcast Folder
Open Redream and go to:
Library > Add DirectorySelect:
Retroid/ROMs/Dreamcast
Approve Android folder access.
CHD, GDI, BIN/CUE and CDI images should appear in the library. Redream recommends avoiding CDI images when a cleaner dump is available.
To remove the folder, return to Library and delete the directory entry. The game files remain on the microSD card.
Dreamcast BIOS Requirement
Redream’s built-in replacement BIOS is sufficient for ordinary retail games.
An optional original Dreamcast BIOS must be named:
boot.bin
On Android, Redream expects it inside its application-data files directory. Modern Android versions restrict access to this location, so the original BIOS should be treated as an optional advanced configuration rather than a setup requirement.
When correctly installed, Redream’s System menu can boot to the original Dreamcast BIOS.
Delete or move boot.bin to return Redream to its built-in replacement BIOS.
Configure Controls
Open Redream’s Input page.
Select the Retroid controller for Port 1. If automatic configuration is incomplete, choose the option to customise bindings and map:
- D-pad.
- Analogue stick.
- A, B, X and Y.
- Left and right triggers.
- Start.
Launch a game and confirm that movement, face buttons and both triggers work.
Once confirmed, disable or hide Redream’s touchscreen controls.
If the physical mapping stops working, re-enable the touchscreen overlay, return to Input and reselect or remap the Retroid controller.
Set Display Options
Open Redream’s Video settings.
Use a 4:3 aspect ratio and begin at the default or native resolution. Leave frame skipping off.
The game should run without stretched menus or repeating skipped frames.
Increase resolution one step at a time. If performance drops, return to the previous value and restart the game.
Configure PPSSPP
Choose The Memory-Stick Folder
During first launch, PPSSPP may ask you to create or choose a PSP folder.
Select a dedicated folder such as:
Retroid/Saves/PPSSPP
Approve the folder through Android’s picker.
PPSSPP should create a PSP directory containing folders such as:
-
SAVEDATAfor normal PSP saves. -
PPSSPP_STATEfor save states. -
GAMEfor applicable installed content.
If PPSSPP was configured previously, open Settings > System and locate its memory-stick folder option.
Before selecting a new folder, copy the complete old PSP directory into the new location. Do not delete the original until a normal save loads successfully from the replacement folder.
Open The PSP Game Folder
Return to PPSSPP’s Games screen and select Browse.
Open:
Retroid/ROMs/PSP
The game icons should appear. Select a test game and confirm it launches.
If a game is missing, confirm that it is an ISO, CSO or supported CHD rather than a ZIP, RAR or 7Z archive.
Configure Controls
Open:
Settings > Controls > Control MappingUse automatic mapping if shown, then verify:
- D-pad.
- Analogue stick.
- Cross, Circle, Square and Triangle.
- L and R.
- Start and Select.
Return to Controls and switch On-Screen Touch Controls off.
Launch a game. The touchscreen overlay should disappear and all physical controls should work.
If they do not, re-enable On-Screen Touch Controls, return to Control Mapping and use Clear All or Restore Defaults before mapping again.
Set Graphics
Open:
Settings > GraphicsUse:
- Backend: Vulkan.
- Frame Skipping: Off.
- Auto Frameskip: Off.
- Texture Filtering: Auto.
- Texture Scaling: Off initially.
- Post-Processing Shader: Off initially.
Start with:
- Pocket Classic: 2x rendering resolution.
- Pocket 5 & Flip 2: 4x.
- Pocket 6 & Nova: 4x.
A 4x PSP image already exceeds or closely matches the useful detail available on these displays. Raising resolution further often increases heat and load without a meaningful visible improvement.
Launch a demanding game and display PPSSPP’s speed counter. It should remain close to 100%.
If it does not, lower rendering resolution by one step before changing anything else.
Create A Per-Game Configuration
Launch the game and open PPSSPP’s pause menu.
Select Create Game Config.
Any subsequent settings changes should now apply only to that game.
Return to the pause menu and select Delete Game Config to make the game inherit the global settings again.
Reset Broken Settings
If PPSSPP begins crashing or several games stop working after configuration changes, open Settings > System and select the option to restore PPSSPP’s settings to default.
This resets application settings, so record custom paths and controls first.
After resetting, reselect the memory-stick folder, remap the controls and test one game before adding further changes.
Configure melonDS
Add The Nintendo DS Search Directory
Open melonDS and go to:
Settings > ROMs > Search DirectoriesSelect:
Retroid/ROMs/Nintendo DS
Approve folder access.
melonDS scans the selected folder and its subfolders. NDS games should appear in the library.
To change the folder, return to Search Directories and select a replacement. If the library shows old entries, use the rescan or refresh option.
Use Internal Firmware For The Initial Setup
Open:
Settings > System > Custom BIOS And FirmwareLeave custom BIOS disabled for the first test.
melonDS should use its internal replacement firmware and launch ordinary Nintendo DS games without bios7.bin, bios9.bin or firmware.bin.
Select a test game. It should launch directly.
Enable Original DS Firmware
Only enable this after internal firmware is working.
Copy these files into:
Retroid/BIOS/melonDS
-
bios7.bin— 16KB. -
bios9.bin— 4KB. -
firmware.bin— normally 256KB or 512KB.
Open Settings > System > Custom BIOS And Firmware, enable the custom option and set the DS BIOS directory to the melonDS folder.
If all required files are found, the red or orange warning icon beside the directory should disappear.
Enable Show Boot Screen to start through the original DS menu. Disable it to launch games directly.
If games stop booting, disable custom BIOS and firmware. melonDS will return to its internal replacements.
Enable JIT
Open:
Settings > System > Enable JITEnable the option.
Launch a 3D-heavy DS game and confirm that it runs at full speed.
If one game repeatedly freezes, disable JIT and test the same point again.
Enable Threaded Rendering
Open:
Settings > Video > Threaded RenderingEnable it and test a 3D game.
Performance should improve or remain stable. If graphical faults appear, disable Threaded Rendering and restart the game.
Configure Normal Save Location
Open:
Settings > Save FilesDisable Save Next To ROM File if you want saves kept separately.
Select Save File Directory and choose:
Retroid/Saves/melonDS
Choose a save-state location on the same page.
Create a normal in-game save, close melonDS and reload the game. The save should appear.
Changing the save directory does not move existing saves. Copy old save files into the new folder before changing the path.
Configure Controls & Screen Layout
Open:
Settings > Input > Key MappingMap the D-pad, A, B, X, Y, L, R, Start and Select.
On models with analogue sticks, map screen swap to R3. On the Pocket Classic, choose an unused extra button or retain the on-screen layout control.
Disable Show Soft Input after physical controls work.
Open the screen-layout editor and create:
- A large primary screen with a smaller secondary screen.
- An equal-screen layout for games that use both displays continuously.
Launch a game and use the mapped screen-swap control. The large and small screens should exchange positions.
If the custom layout becomes unusable, return to the layout editor and select a built-in default layout. Re-enable Show Soft Input if the physical controller mapping fails.
Configure Azahar For Nintendo 3DS
Why This Guide Uses Azahar Instead Of Citra
The original Citra project is no longer the current maintained Android option. Azahar combines work from later Citra-derived projects and is actively maintained.
A pre-existing Citra installation does not need to be removed immediately. Keep it until Azahar has launched your games and loaded a normal save successfully.
Choose The Google Play Or Vanilla Build
The Google Play build is the easiest choice because it receives normal store updates.
The Vanilla build uses faster native file access but is installed manually from Azahar’s official releases and does not automatically update when installed as a standalone APK.
Do not install both unless you deliberately want separate applications and separate user data.
The Vanilla build uses package name:
org.azahar_emu.azahar
The Google Play build uses a different package identity. This matters when choosing the Azahar player inside Retroid Launcher or Daijisho.
Complete First-Run Storage Setup
Open Azahar and follow its setup screens.
When asked for a user-data location, select a folder that can be backed up easily. Record the chosen path before continuing.
The application should reach its Games or Applications screen.
If setup becomes trapped in a loop, fully close Azahar from Recent Apps, reopen it and repeat the storage selection. Do not clear application storage unless you have backed up the Azahar user-data directory.
Add The Nintendo 3DS Game Folder
Select Add Games or Add Game Directory.
Choose:
Retroid/ROMs/Nintendo 3DS
Approve folder access.
Recognised game images should appear with their titles and icons.
If the folder is accepted but remains empty, confirm that the files are supported by the installed Azahar build and were dumped in a usable form. Renaming an encrypted or unsupported file does not make it compatible.
Remove the directory through Azahar’s folder settings to undo the scan. The game files remain on the card.
Install CIA Content
Open Azahar’s menu and select Install CIA.
Browse to the CIA file, select it and confirm installation.
When complete, the installed title should appear in Azahar’s Applications or Games list.
Deleting the original CIA after successful installation does not remove the installed application. To remove the installed title, use Azahar’s title-management or uninstall command rather than deleting random files from the user-data folder.
Configure Controls
Open:
Settings > ControlsSelect Auto-Map Controller and choose the Retroid controller.
| Nintendo 3DS Input | Retroid Input |
|---|---|
| Circle Pad | Left Analogue Stick |
| C-Stick | Right Analogue Stick |
| D-pad | D-pad |
| A, B, X and Y | Corresponding face-button positions |
| L and R | L1 and R1 |
| ZL and ZR | L2 and R2 |
| Start and Select | Start and Select |
Set Hotkey Enable to Select, then assign screen swap to R3 on models with analogue sticks.
The Pocket Classic lacks analogue sticks and is not a suitable general 3DS controller. Use it only for games that can be mapped sensibly to its available controls or connect an external controller.
If automatic mapping is wrong, reset controls from the same page and map each input manually.
Configure Screen Layout
Open Azahar’s Layout or Screen Layout settings.
Select a landscape layout with one large primary screen and a smaller secondary screen.
Launch a game and press the mapped screen-swap hotkey. The primary and secondary displays should exchange positions.
Create an equal-screen layout for games that use both displays continuously.
To remove a custom layout, return to Layout and select the built-in Default option.
Set A Stable Graphics Baseline
Open:
Settings > GraphicsSelect Vulkan where available and begin at 1x internal resolution.
Leave widescreen, texture replacement and texture-enhancement options off for the first test.
Launch a game and reach normal gameplay. Brief first-time stutters can occur while shaders are compiled. Replay the same section; shader-related stutter should reduce on the second pass.
Once stable, increase resolution to:
- Pocket Classic: remain at 1x for initial use.
- Pocket 5 & Flip 2: test 2x.
- Pocket 6 & Nova: test 3x.
If slowdown repeats every time rather than only during first-time effects, return to 1x, disable enhancements and test OpenGL.
For one game, long-press it and open Properties or Game Settings. Apply the renderer or resolution change there.
Remove or reset the game-specific settings to return it to the global configuration.
Back Up Azahar
Before updating, copy the complete Azahar user-data folder selected during initial setup to:
Retroid/Backups/Emulator Data/Azahar
Copy that backup to a computer as well.
Do not rely only on save states. Create a normal in-game save and confirm it reloads before changing Azahar builds.
Configure Dolphin
Add GameCube & Wii Folders
Open Dolphin’s game library and select the plus button or Add Games.
Select:
Retroid/ROMs/GameCube
Approve access, then repeat the process for:
Retroid/ROMs/Wii
GameCube and Wii titles should appear under their respective platform tabs.
To remove a path, open Dolphin’s Game Folders or Paths settings and delete the directory entry. Removing the path does not delete the game files.
GameCube & Wii BIOS Requirement
Dolphin does not require a separate GameCube or Wii BIOS to launch ordinary retail games.
A Wii NAND or system update is used for advanced Wii Menu, channel and online configurations. It is not required for the normal disc-game setup covered here.
Configure GameCube Controller 1
Open:
Settings > GameCube Input > GameCube Controller 1Select Emulated or Standard Controller.
Map:
- Control Stick to the left analogue stick.
- C-Stick to the right analogue stick.
- D-pad to the D-pad.
- A, B, X and Y to the corresponding physical positions.
- Z to L1 or R1.
- Start to Start.
- L and R analogue axes to L2 and R2.
- L and R digital clicks if Dolphin displays separate full-press bindings.
Move both sticks and squeeze both triggers slowly. The input indicators should move across their full range.
Save the controller configuration as a named Retroid profile.
If later changes break the mapping, reload that profile. Use Reset or Clear to remove an unwanted mapping.
Configure Wii Controls Per Game
Wii games can expect entirely different controllers.
Determine whether the game supports:
- A Wii Remote held vertically.
- A Wii Remote held sideways.
- A Wii Remote and Nunchuk.
- A Classic Controller.
- A GameCube controller.
- Pointer input.
- Motion gestures.
Long-press the Wii game and open Edit Game Settings or Game-Specific Settings.
Open Wii Input, select an emulated Wii Remote and choose the required extension or sideways option.
Map only the controls required by that game, then launch it and test its menus and gameplay.
The mapping should affect the selected game without altering other Wii titles.
Return to the same game-specific page and choose Reset or Use Global to remove the special profile.
Set A Stable Graphics Baseline
Open:
Settings > Graphics SettingsUse:
- Video Backend: Vulkan.
- Internal Resolution: 1x for the first test.
- Anti-Aliasing: None.
- Anisotropic Filtering: 1x.
- Aspect Ratio: Auto.
- Widescreen Hack: Off.
- Shader Compilation: the stable default mode.
Once the game remains at full speed, test:
- Pocket Classic: 1x only for control-suitable games.
- Pocket 5 & Flip 2: 2x.
- Pocket 6 & Nova: 2x or 3x.
Return to the previous resolution if audio crackles or game speed falls.
Create Per-Game Graphics Settings
Long-press the game and select Edit Game Settings.
Change the renderer, resolution or compatibility option there rather than globally.
Launch the game and confirm that the fix applies only to it.
Return to its game-specific settings and select Reset or Use Global to remove the override.
Back Up Dolphin
Open Dolphin’s Settings or Config menu and locate the User Data export option where provided.
Export the user data to:
Retroid/Backups/Emulator Data/Dolphin
The export should include configuration, controller profiles, GameCube memory cards and Wii save data.
Copy the backup to a computer before uninstalling or moving between major versions.
Configure NetherSX2
Choose The Correct NetherSX2 Branch
| Retroid Model | Recommended Branch | Reason |
|---|---|---|
| Pocket 5 | Patched 4248 | Adreno graphics and sufficient performance. |
| Flip 2 Snapdragon 865 | Patched 4248 | Adreno graphics and sufficient performance. |
| Flip 2 Dimensity 1100 | Classic 3668 | Recommended for Mali graphics. |
| Pocket Classic | Classic 3668 | Recommended for less powerful hardware. |
| Pocket 6 | Patched 4248 | Powerful Adreno hardware. |
| Nova | Patched 4248 | Powerful Adreno hardware; retail results remain provisional. |
Do not install APK files from websites imitating the NetherSX2 name. Use the Trixarian NetherSX2 patch project.
Back Up An Existing AetherSX2 Or NetherSX2 Setup
Open the existing application and locate Transfer Data or Backup Data.
Select Export and choose:
Retroid/Backups/Emulator Data/NetherSX2
Do not delete the export until normal memory-card saves have been tested in the new build.
Complete The Setup Wizard
Open NetherSX2 and select the Optimal or Safe preset during first-run setup.
At the BIOS step, browse to:
Retroid/BIOS/NetherSX2
Select the uncompressed PlayStation 2 BIOS dump.
NetherSX2 should display the BIOS region and version or accept it without an invalid-file warning.
If rejected, renaming the file will not repair it. Repeat the BIOS dump from the console.
At the game-directory step, select:
Retroid/ROMs/PlayStation 2
Choose Use This Folder and approve access.
The PlayStation 2 test games should appear in the library.
Configure Controller Port 1
Open:
App Settings > Controller Settings > Port 1Use Automatic Mapping and select the Retroid controller.
Verify the D-pad, face buttons, shoulder buttons, triggers, analogue sticks, stick clicks, Start and Select.
Disable the touchscreen controller after the physical mapping works.
If input fails, re-enable the touchscreen overlay, clear Port 1 and run Automatic Mapping again.
Set The Global Graphics Baseline
Open:
App Settings > GraphicsUse:
- GPU Renderer: Vulkan.
- Upscale Multiplier: 1x initially.
- Aspect Ratio: Auto or 4:3.
- Blending Accuracy: default.
- Hardware Download Mode: default during initial testing.
- EE Cycle Rate: Normal.
- EE Cycle Skip: 0 or Normal.
On NetherSX2 Classic 3668 using Vulkan, enable Threaded Presentation.
If stable, raise the resolution one step:
- Pocket Classic: remain at 1x.
- Pocket 5 & Flip 2: test 1.5x or 2x.
- Pocket 6 & Nova: test 2x, then 3x only when the game remains stable.
If performance drops, restore the previous multiplier before using speed hacks.
Change Advanced Settings Only Per Game
Long-press the affected game and open Game Properties.
Apply options such as Disable Readbacks, EE Cycle Rate or Cycle Skip only to that game.
Check graphics, speed, physics and audio after every change.
Return the values to Default or select Reset Game Settings if the game becomes unstable.
Test A Memory-Card Save
Create a normal save using the game’s own save menu.
Fully close NetherSX2 from Recent Apps, reopen it and launch the same game.
The save should appear on the emulated memory card.
If it does not, confirm that the same game region and memory-card slot are being used.
Configure ScummVM
Organise Game Data
Create one folder for each supported game:
Retroid/ROMs/ScummVM ├── Beneath A Steel Sky ├── Broken Sword ├── Day Of The Tentacle ├── Full Throttle ├── Monkey Island └── Sam & Max
Each folder must contain the original game data, not merely an installer, shortcut or compressed download.
Authorise The ScummVM Parent Folder
Open ScummVM and select Add Game.
Use Go Up in ScummVM’s file browser until the root page shows Add A New Folder.
Select it, then use Android’s file picker to choose:
Retroid/ROMs/ScummVM
Select Use This Folder and then Allow.
The ScummVM parent folder should now appear in ScummVM’s own file browser.
To revoke the permission, open:
Global Options > Backend > Remove Folder AuthorisationsAdd A Game
Select Add Game, open the authorised ScummVM folder and select the subfolder containing one game.
Select Choose.
ScummVM should identify the title. If several editions are detected, select the correct platform and language.
Select OK, highlight the game and press Start.
To remove the library entry, highlight the game and select Remove Game. This removes the entry but does not delete the game data.
Configure Pointer Controls
Open:
Global Options > KeymapsMap the left analogue stick to pointer movement, A to left click, B to right click and Start to the ScummVM menu.
Launch a game. The stick should move the pointer and A and B should perform the two mouse clicks.
To change one game only, highlight it, open Game Options > Keymaps and create its mapping there.
Reset the game keymap to return to the global controls.
Choose A Save Folder
Open:
Global Options > PathsSet the save path to:
Retroid/Saves/ScummVM
Create a save inside a game, close ScummVM, reopen it and load the save.
Configure Retroid Launcher
Download The Required Platforms
Open Retroid Launcher and select the Download icon.
Select the platforms you want to add, then select Download.
The selected platform icons should appear on the launcher’s main platform row.
To remove a platform later, highlight it, press X for Details, select Edit and use Delete Platform. This removes the launcher entry but not the game files.
Add A ROM Directory
Highlight a platform without opening it.
Press X for Details.
Scroll right to Directories and select Add.
Browse to the matching system folder under:
Retroid/ROMs
Select the folder and confirm it.
Return to the platform and run its scan or update command. The test games should appear.
Repeat this process one platform at a time.
To remove a path, return to Details > Directories and delete the directory entry. Removing the entry does not delete the game files.
Select The Emulator Or RetroArch Core
Highlight the platform and press X for Details.
Select Edit in the lower-right corner, then open Config.
Select the required emulator or RetroArch core.
- PlayStation — DuckStation.
- PlayStation 2 — the installed NetherSX2 package.
- Nintendo 64 — Mupen64Plus FZ.
- Dreamcast — Redream.
- PSP — PPSSPP or PPSSPP Gold.
- Nintendo DS — melonDS.
- Nintendo 3DS — the installed Azahar variant.
- GameCube and Wii — Dolphin.
- Game Boy and Game Boy Color — RetroArch Gambatte.
- Game Boy Advance — RetroArch mGBA.
- NES — RetroArch Mesen.
- SNES — RetroArch Snes9x.
- Mega Drive and Sega CD — RetroArch Genesis Plus GX.
- PC Engine and PC Engine CD — RetroArch Beetle PCE Fast.
- Arcade and Neo Geo — RetroArch FinalBurn Neo.
Return to the game list and launch one test game.
A correct direct launch should open the selected emulator, launch the game automatically, use the physical controls and return to Retroid Launcher after the emulator is closed.
If the emulator opens at its own library rather than launching the game, return to Config and select another player entry matching the exact installed package.
Restore the previous Config entry to undo an unsuccessful change.
ScummVM In Retroid Launcher
For the most reliable setup, keep ScummVM available in the launcher’s Apps section and manage its game library inside ScummVM.
Configure Daijisho
Daijisho is an alternative Android gaming frontend. It organises platforms, scans game folders, launches standalone emulators and RetroArch cores, displays artwork and can replace the normal Android Home screen.
Daijisho does not include emulators, BIOS files or games. Configure and test every emulator directly before connecting it to Daijisho.
Retroid Launcher and Daijisho can remain installed together. Test both before choosing one as Android’s Home application. Changing the Home application does not remove either frontend or its library.
Install & Open Daijisho
Open Google Play and search for:
Daijisho
Select the listing published by TapiocaFox, then press Install.
When installation finishes, press Open.
Daijisho should load its main interface with sections for platforms, widgets, applications and settings. The platform area may initially be empty.
To remove Daijisho later, back up its settings first, then open Settings > Apps > See All Apps > Daijisho and select Uninstall. Uninstalling Daijisho does not delete the ROM files stored on the microSD card, but it can remove Daijisho’s own library, artwork and settings.
Import The Required Platforms
Open Daijisho’s Download page.
Select the platforms you want to add, such as Game Boy, Game Boy Advance, NES, SNES, Mega Drive, PlayStation, Nintendo 64, Dreamcast, PSP, Nintendo DS, Nintendo 3DS, GameCube, Wii and PlayStation 2.
Press Import.
Return to the Platforms page. A platform card should now appear for every imported system.
Platforms can also be added through:
Daijisho > Settings > Library > PlatformsTo remove a platform, open:
Daijisho > Settings > Library > Inspect PlatformsSelect the unwanted platform and use its delete option. Deleting a platform removes its Daijisho entry but does not delete games from the microSD card.
Add A Game Folder & Synchronise The Platform
Open Daijisho’s Platforms page and move to the platform being configured.
Select Add More.
Android’s folder picker should open. Browse to the matching ROM folder, such as:
Retroid/ROMs/PlayStation
Select Use This Folder, then select Allow.
Daijisho should return to the selected platform. Press Sync.
A progress indicator should appear while Daijisho scans the folder. When the process finishes, the platform should show a game count and the test games should appear in its Library view.
Repeat the process one platform at a time. Launch one test game before importing a large library.
If the wrong folder was selected, open the platform editor using the pencil icon, remove the incorrect path, add the correct folder and press Sync again. Removing a path from Daijisho does not delete the files inside it.
Select The Default Player
In Daijisho, the word Player means the emulator or RetroArch core used to launch a game.
Open the Platforms page and move to the platform being configured.
Select the pencil icon to edit the platform.
Open the Default Player drop-down menu and select the player that matches the emulator installed on the Retroid Pocket.
| Platform | Daijisho Player To Select |
|---|---|
| Game Boy & Game Boy Color | The RetroArch player containing Gambatte and -lr
|
| Game Boy Advance | The RetroArch player containing mGBA and -lr
|
| NES | The RetroArch player containing Mesen and -lr
|
| SNES | The RetroArch player containing Snes9x Current and -lr
|
| Master System, Game Gear & Mega Drive | The RetroArch player containing Genesis Plus GX and -lr
|
| Sega CD | Genesis Plus GX-lr |
| PC Engine & PC Engine CD | Beetle PCE Fast-lr |
| Arcade & Neo Geo | FinalBurn Neo-lr or FBNeo-lr |
| PlayStation | DuckStation |
| PlayStation 2 | NetherSX2 matching the installed package |
| Nintendo 64 | Mupen64Plus FZ |
| Dreamcast | Redream |
| PSP | PPSSPP or PPSSPP Gold, matching the installed edition |
| Nintendo DS | melonDS matching the installed Android build |
| Nintendo 3DS | Azahar matching the installed Google Play or Vanilla build |
| GameCube & Wii | Dolphin Official |
Select Save.
Return to the platform library and launch a test game. The selected emulator should open and the game should start automatically rather than stopping at the emulator’s normal library screen.
If the wrong emulator opens, return to the platform editor, restore the previous Default Player or select another entry matching the exact emulator package installed on the handheld.
Use The Correct RetroArch Build
Do not use the Google Play edition of RetroArch with Daijisho. Install the official 64-bit AArch64 Android build from the RetroArch website.
After installing the official RetroArch build, open it, install the required cores and launch one test game directly inside RetroArch.
Return to Daijisho and select the player whose name contains the required core and -lr.
If a game produces a black screen, confirm that the selected core is installed under RetroArch > Online Updater > Core Downloader and that any required BIOS is marked Present.
If you previously installed the Google Play build, do not uninstall it until saves and configurations have been backed up. Install the official build, configure it separately, update Daijisho’s players and confirm that normal saves load before removing the old application.
Use A Different Player For One Game
Open the platform’s Library view and highlight the game.
Select Edit Item.
Enable Custom Player.
Open the Custom Player drop-down menu, select the required emulator and press Save.
Launch the game. It should use the custom player while the rest of the platform continues using its normal Default Player.
To remove the override, return to Edit Item, disable Custom Player and save. The game will inherit the platform’s Default Player again.
Repair Missing Or Incorrect Artwork
Daijisho normally attempts to scrape artwork and metadata when a platform is synchronised.
If a game has no artwork or has been matched to the wrong title, open its Library entry and select Edit Item.
Find the Scraper Keyword field and enter a clean version of the game title without region codes, revision labels or disc numbering.
Add the keyword to the list, then select Save & Scrape.
The game entry should refresh with new artwork and metadata.
If the result is still wrong, edit the keyword again or open Edit Preview Media and select a local image manually.
To restore automatic artwork later, remove the custom media and scrape the game again.
Use Aggressive Scraping Only As A Fallback
Open:
Daijisho > Settings > Library > Aggressive ScrapingEnable the option, return to the affected platform and press Sync.
Aggressive scraping uses fewer matching restrictions and may find artwork for unusually named games, but it can also produce incorrect matches.
Check several games after the scan. Disable Aggressive Scraping again if it creates wrong artwork, then correct individual games through their Scraper Keyword field.
Update Platform Definitions & Players
Open:
Daijisho > Settings > LibraryEnable Update Players Automatically or Update Platforms Automatically where shown.
Alternatively, return to the Download page, select the affected platform and import it again.
The platform should update without removing its existing game records.
If an updated definition selects the wrong emulator, reopen the platform editor and restore the correct Default Player.
Fix A Supported File That Does Not Appear
First confirm that the game extension is supported by the selected player.
Re-import the platform definition and press Sync again.
If the extension is supported but still excluded, open:
Daijisho > Settings > Library > Inspect PlayersSelect the active player and locate Player Accepted Filename Regex.
Before changing it, copy the complete existing value into a text file or take a clear photograph.
Add the required extension using the same pattern already used by the other extensions, then press Save and synchronise the platform again.
The missing game should appear after the new scan.
If other games disappear or the player stops working, return to Inspect Players and restore the original regex exactly. Re-importing the platform definition can also restore its standard player settings.
Fix A Player That Opens But Does Not Launch The Game
Open the game directly inside the emulator first. If it fails there, repair the emulator rather than Daijisho.
If the game works directly, re-import the platform definition and select the player again.
If the emulator still opens without the selected game, open:
Daijisho > Settings > Library > Inspect PlayersSelect the active player and locate Player AM Start Argument.
Copy the complete original argument into a text file before editing it.
If the argument contains {file.path}, replace only that part with:
{file.uri}
If it already contains {file.uri}, test:
{file.path}
Save the player and launch the same game again.
If the change does not work, restore the original argument exactly or re-import the standard platform definition.
Configure Daijisho Navigation Hotkeys
Open:
Daijisho > Settings > Navigation > HotkeysDaijisho provides assignments for Search, Tabs, Switching, First Additional and Second Additional actions.
Select an action and press the physical Retroid button you want to assign.
Use controls that are not required for normal frontend navigation. Avoid assigning the same button to several actions until each one has been tested.
Return to the Platforms page and test the new controls. The Tabs hotkey should move between Daijisho’s main pages, while the Switching hotkey should move between platforms.
To undo a binding, return to Navigation > Hotkeys and clear it or assign the previous button again.
Download Platform Wallpapers
Open:
Daijisho > Settings > Appearance > Download Platform Wallpapers PackSelect a wallpaper pack and allow it to download.
Return to the Platforms page. Each platform should now display artwork from the selected pack.
To change the appearance, download another pack or open the individual platform editor and select its Wallpaper Settings.
Changing or removing a wallpaper does not affect game artwork, emulator settings or ROM files.
Use ScummVM Through Daijisho
The simplest setup is to open ScummVM from Daijisho’s Apps page and manage the game library inside ScummVM.
Direct per-game launching is possible through Daijisho player-template files, but each game requires its ScummVM ID and a separate .dpt file.
After adding a game to ScummVM, record its game ID.
Create a text file containing:
# Daijishou Player Template [scummvm_id] GAME-ID-HERE ...
Replace GAME-ID-HERE with the real ScummVM ID, then save the file and change its extension from .txt to:
.dpt
Place the DPT files in a dedicated folder, import the ScummVM platform into Daijisho, add the DPT folder as its path and press Sync.
Select the standalone ScummVM player provided by Daijisho and launch a test entry.
If direct launching fails, remove the ScummVM platform and continue using ScummVM through the Apps page. Removing the DPT files does not delete the original game data.
Back Up Daijisho
Open Daijisho’s Settings page and scroll to Backup & Restore.
Select the backup option and save the file under:
Retroid/Backups/Daijisho
Wait for the export to finish, then open the backup folder in the Files application and confirm that a new backup file is present.
Copy that file to a computer or external drive. A backup stored only on the same microSD card does not protect against card failure.
To restore it, install Daijisho, open Backup & Restore, select Restore and choose the saved backup file.
After restoration, synchronise one platform and launch a test game. If the restored player no longer matches the installed emulator package, select the correct Default Player again.
Set Daijisho As Home Only After Testing
Do not set Daijisho as Android’s Home application until several platforms launch games correctly and the Settings page remains accessible.
The full Home application procedure and recovery route are covered later in this guide.
Set The Correct Retroid Launcher File Suffixes
This section applies to Retroid Launcher. Daijisho controls supported extensions through each player’s accepted filename rules.
In Retroid Launcher, highlight a platform, press X for Details, select Edit and open Suffix.
Enable only the file extensions that should appear for that platform.
| Platform | Recommended Suffixes | Important Exclusion |
|---|---|---|
| Game Boy | .gb |
None |
| Game Boy Color | .gbc |
None |
| Game Boy Advance | .gba |
None |
| NES | .nes |
None |
| SNES |
.sfc, .smc
|
None |
| Master System | .sms |
None |
| Game Gear | .gg |
None |
| Mega Drive |
.md, .gen, .smd
|
Avoid BIN if Sega CD files share the same directory. |
| Sega CD |
.chd, .cue, .m3u
|
Do not enable BIN. |
| PC Engine | .pce |
None |
| PC Engine CD |
.chd, .cue
|
Do not enable BIN. |
| Arcade & Neo Geo | .zip |
Do not extract the archives. |
| Nintendo 64 |
.z64, .n64, .v64
|
None |
| PlayStation |
.chd, .m3u, .cue
|
Do not enable BIN. |
| Dreamcast |
.chd, .gdi, .cdi
|
Do not enable individual GDI track extensions. |
| PSP |
.iso, .cso, .chd
|
None |
| Nintendo DS | .nds |
Uncompressed NDS files are simplest. |
| Nintendo 3DS | Only formats recognised by the installed Azahar build | CIA packages should be installed inside Azahar. |
| GameCube |
.rvz, .iso, .gcm
|
None |
| Wii |
.rvz, .wbfs, .iso
|
None |
| PlayStation 2 |
.chd, .iso
|
None |
Run Update Platform after changing suffixes.
Duplicate track entries should disappear when BIN and other underlying track extensions are excluded.
To reverse the change, reopen Suffix and restore the previous extension selection, then update the platform again.
Set Retroid Launcher Or Daijisho As The Home Application
Do this only after the selected frontend can launch games correctly and you know how to reach Android Settings from it.
Open:
Settings > Apps > Default Apps > Home AppSelect either Retroid Launcher or Daijisho.
Press the Android Home button. The selected frontend should open immediately.
If the Home App entry is not visible, use the main Settings search box and search for:
home app
To switch between the two frontends, return to Home App and select the other one.
To restore the standard Android launcher, select Quickstep, Launcher3 or the launcher name that was active before the change.
If the chosen frontend prevents easy access to Settings, swipe down twice from the top of the screen and select the Settings cog.
Changing the Home application does not uninstall a frontend, delete its library or alter any emulator settings.
Recommended Starting Settings By Model
These are starting points, not guarantees. Individual games can require lower settings or a different renderer.
| Emulator | Pocket Classic | Pocket 5 / Flip 2 SD865 | Flip 2 D1100 | Pocket 6 / Nova |
|---|---|---|---|---|
| DuckStation | Vulkan, 2x | Vulkan, 3x | Vulkan, 3x; test OpenGL for faults | Vulkan, 4x |
| Mupen64Plus FZ | Limited by missing analogue sticks | Default accurate profile | Test profiles per game | Default accurate profile |
| Redream | Default resolution for control-suitable games | Default, then increase one step | Default, then increase one step | Increase after full-speed testing |
| PPSSPP | Vulkan, 2x | Vulkan, 4x | Vulkan, 4x; test OpenGL if needed | Vulkan, 4x |
| melonDS | JIT and Threaded Rendering on unless faults appear | JIT and Threaded Rendering on | JIT and Threaded Rendering on | JIT and Threaded Rendering on |
| Azahar | 1x; limited controls | Vulkan, 2x | Vulkan, 2x; test OpenGL | Vulkan, 3x |
| Dolphin | 1x; control-suitable games only | Vulkan, 2x | Vulkan, 1x or 2x | Vulkan, 2x or 3x |
| NetherSX2 | Classic 3668, Vulkan, 1x | 4248, Vulkan, 1x then 1.5x or 2x | Classic 3668, Vulkan, 1x then 1.5x | 4248, Vulkan, 1x then 2x or 3x |
Always return to native or 1x resolution before applying speed hacks.
Normal Saves, Save States & Backups
Normal Saves
Normal saves are created through the game’s own save system and emulate cartridge memory, memory cards or console storage.
- Launch a game directly inside the emulator.
- Create a normal in-game save.
- Fully close the emulator from Recent Apps.
- Reopen it.
- Launch the same game.
- Load the save through the game’s own menu.
Do not move to frontend configuration until this works.
Save States
Save states can become incompatible after an emulator update, a switch between emulator branches, a major renderer change or a RetroArch core update.
Use normal saves as the main progress record and save states as an additional convenience.
Back Up The Complete Setup
Back up:
- RetroArch saves, states, configuration, overrides and remaps.
- DuckStation memory cards and settings.
- Mupen64Plus FZ profiles and saves.
- Redream save data.
- PPSSPP’s complete PSP folder.
- melonDS normal saves and configuration.
- Azahar’s complete user-data directory.
- Dolphin user data, memory cards and controller profiles.
- NetherSX2 exported data and memory cards.
- ScummVM saves and configuration.
- Retroid Launcher platform settings.
- Daijisho’s backup file, platform settings and custom artwork.
- BIOS files.
Copy the backups to the microSD card’s Backups folder and then to a separate computer or external drive.
A backup kept only on the same microSD card does not protect against card failure.
Restore Safely
Close the relevant emulator or frontend before restoring its data.
Rename the current save or data folder by adding:
-current-backup
Copy the older backup into the original location, reopen the application and test a normal save or direct game launch.
If the restore fails, remove the copied folder and rename the safety copy back to its original name.
Update Emulators Without Breaking The Setup
Before updating an emulator:
- Record its current version and branch.
- Back up normal saves and application data.
- Keep a copy of the working APK when possible.
- Test an important normal save.
- Install the update.
- Open the emulator directly.
- Confirm its game-folder permissions.
- Load the normal save.
- Launch the same game from Retroid Launcher and Daijisho if both are configured.
An update can change the Android package, launch activity, storage permissions, controller mappings, renderer defaults, save-state compatibility or frontend player compatibility.
If direct launching stops working but the game still launches inside the emulator, update or reselect the frontend player.
In Daijisho, re-import the affected platform before manually editing its Player AM Start Argument.
If the emulator itself stops working, restore its backed-up data and reinstall the previously working APK.
Detailed Troubleshooting
The Emulator Cannot See The microSD Card
- Open Android’s Files application.
- Confirm that the microSD card appears.
- Open the system ROM folder and confirm that the test game is visible.
- Open the emulator and remove its existing game-directory entry.
- Add the directory again through Android’s folder picker.
- Select Use This Folder and Allow.
- Rescan the library.
If the game still does not appear, check whether its extension is supported.
A Frontend Opens The Emulator But Not The Game
- Open the game directly inside the emulator.
- If it fails there, repair the emulator setup first.
- If it works, return to the frontend’s platform settings.
- Select another player entry matching the exact installed emulator package.
- Launch the game again.
Restore the previous player if the replacement opens the wrong application.
Daijisho Synchronises A Platform But Finds No Games
- Open Android’s Files application and confirm that the games are present.
- Check the file extensions.
- Open the Daijisho platform editor and confirm that the correct folder is listed.
- Re-import the platform definition.
- Press Sync again.
- Check the active player’s accepted filename extensions.
If editing the player regex causes more games to disappear, restore the original value or re-import the platform.
Daijisho Shows A Black Screen After Selecting A Game
Confirm that the selected emulator is installed.
For a RetroArch player, open RetroArch and confirm that the selected core is installed and any required BIOS is Present.
Launch the game directly inside the emulator.
If it works directly, update the Daijisho platform definition and reselect its Default Player.
Daijisho Scrapes The Wrong Artwork
Open the game’s Edit Item page, replace the Scraper Keyword with a clean title and select Save & Scrape.
Disable Aggressive Scraping if it is active.
Use Edit Preview Media to assign a local cover manually.
RetroArch Reports Missing Firmware
- Load the affected core.
- Open Main Menu > Information > Core Information.
- Write down the exact missing filename.
- Check Settings > Directory > System/BIOS.
- Confirm the filename and extension.
- Verify its MD5 hash.
- Fully close and reopen RetroArch.
PlayStation Games Appear More Than Once
The frontend may be scanning the CUE, every BIN track, every disc and the M3U playlist.
In Retroid Launcher, disable BIN under the platform’s Suffix settings.
In Daijisho, use a player whose accepted extensions include CUE, CHD and M3U without treating each underlying BIN track as a separate game.
FinalBurn Neo Reports Missing ROMs
The game archive, parent set or BIOS archive does not match the installed FinalBurn Neo database.
Keep the game ZIP and neogeo.zip intact. Do not combine files from unrelated sets.
PPSSPP Runs Below Full Speed
- Reduce rendering resolution by one step.
- Disable post-processing.
- Disable texture scaling.
- Keep frameskip off initially.
- Confirm Vulkan is selected.
- Use a higher Retroid performance mode only after these changes.
Dolphin Has Repeating Audio Crackle
- Set internal resolution to 1x.
- Disable anti-aliasing.
- Set anisotropic filtering to 1x.
- Disable widescreen hacks.
- Test Vulkan and OpenGL.
- Use High Performance mode.
NetherSX2 Is Slow At 2x
Return to 1x before changing CPU timing.
Disable graphics enhancements, test both Vulkan and OpenGL and use the Retroid High Performance mode.
Apply advanced changes only through the game’s Properties page.
Controls Work In Android But Not In An Emulator
Open the emulator’s Input or Controller settings, select Port 1 or Player 1 and run automatic mapping where available.
Verify every binding manually.
Clear the mapping and reload the saved Retroid profile if the new configuration is worse.
The Flip 2 Does Not Resume A Game Correctly After Closing The Lid
Save normally before closing the lid during testing.
Close the lid, wait thirty seconds, reopen it and check controls, audio and game speed.
If the emulator freezes or loses audio, fully close it and reload the normal save.
Check Handheld Settings > Power for aggressive process cleaning and disable it before retesting.
Final Setup Checklist
- Android first boot has been completed and the handheld has been restarted.
- Retroid Pocket FOTA reports that no newer update is available.
- Retroid Launcher has been updated.
- Three-button or gesture navigation has been selected and tested.
- The controller style and trigger mode have been selected before emulator mapping.
- Every physical control passes the Retroid input test.
- The microSD card is formatted as portable storage.
- The card passes a create, open and delete test.
- Every system has a separate ROM folder.
- RetroArch’s System/BIOS directory is correct.
- Required RetroArch firmware is marked Present.
- DuckStation accepts the PlayStation BIOS.
- NetherSX2 accepts the PlayStation 2 BIOS.
- Every emulator launches a test game directly.
- Every emulator has a tested controller profile.
- A normal in-game save has been closed and reloaded in every emulator.
- Each Retroid Launcher platform has the correct directory, player and suffixes.
- Each Daijisho platform has the correct path and Default Player.
- Daijisho uses the official RetroArch build rather than the Google Play edition.
- Games launch directly from the selected frontend.
- Closing an emulator returns to the selected frontend.
- Retroid Launcher or Daijisho can be selected and reversed as the Android Home application.
- Retroid Launcher and Daijisho settings have been backed up.
- Saves, emulator data and BIOS files are backed up away from the microSD card.
Official Downloads & Documentatio
- RetroArch Android Download
- Libretro & RetroArch Documentation
- DuckStation
- Mupen64Plus FZ
- Redream
- PPSSPP
- melonDS Android
- Azahar (Citra)
- Dolphin Download
- NetherSX2 Patch Project
- ScummVM Download
- Daijisho Google Play Listing
- Daijisho Official Project Page
- Daijisho Official Setup Wiki
- Daijisho Players & File Extensions
The Bottom Line
A properly configured Retroid Pocket should feel like one complete handheld system rather than a collection of unrelated Android applications.
The reliable way to achieve that is to work in a fixed order: update the Retroid firmware, configure Android and the physical controls, prepare the storage, verify firmware, configure each emulator directly, test normal saves and only then connect everything to Retroid Launcher or Daijisho.
Retroid Launcher provides the integrated Retroid experience, while Daijisho provides a more customisable multi-platform frontend with player selection, artwork scraping, widgets and platform themes. Both can be installed and tested before choosing the one that best suits the finished setup.
Use conservative emulator settings first. Confirm that a game is accurate and stable before increasing resolution, adding widescreen patches or applying performance hacks. Keep unusual changes inside game-specific profiles so one difficult title does not affect the rest of the library.
Retrolize provides a set configuration service for the Android handheld consoles we sell, giving customers a prepared, ready-to-use starting point without requiring them to build the complete setup from a blank device.