Ten practical setup tips for retro handhelds: firmware, storage, save states, shaders, controls and keeping your library tidy.
Most retro handhelds are fun out of the box, but a little setup makes a big difference. These tips apply to most Linux and Android devices.
- Replace the bundled microSD card. Cards shipped with budget devices are often unreliable. Copy anything you need, then use a reputable brand.
- Try community firmware. Projects such as muOS, Knulli, ROCKNIX or Onion (on Miyoo devices) often improve speed, menus and battery life. Read the install guide fully first.
- Keep two cards. One for the system, one for your games, where the device allows it. Updates become far less risky.
- Back up your saves regularly. Copy the saves folder to a computer once a month.
- Use save states sensibly. They are brilliant for long games, but keep a normal in-game save too, as states can break between emulator versions.
- Set integer scaling or a light shader. A simple scanline or LCD-grid shader often makes old games look closer to how you remember them.
- Remap controls per system. Most front ends let you save button layouts for each console.
- Add artwork and tidy names. Box art scraping makes a big library much easier to browse.
- Lower brightness for battery life. The screen is usually the biggest drain.
- Only play games you own. Buy official re-releases where they exist; see the note on the law below.
Setting up a new handheld: a simple order
- Charge it fully and check the screen for dead pixels and the buttons for sticking before you change anything. Most sellers' return windows are short.
- Back up the original card with an imaging tool on your computer, so you can restore it if something goes wrong.
- Decide on firmware: stock, or a community build. Check the project's supported device list carefully; firmware for a similar-looking model can fail to boot.
- Add BIOS files you're entitled to where an emulator needs them, such as for PlayStation. Firmware guides explain where they go.
- Organise your games into one folder per system, with the folder names your firmware expects.
- Test one game per system before copying a large library.
Performance tweaks
- Choose the right emulator core: front ends such as RetroArch offer several cores per system, trading accuracy for speed. If a game stutters, try a lighter core.
- Turn off rewind and run-ahead on weaker devices, as they use extra processing power.
- Frame skip is a last resort; it makes motion look choppy.
- CPU profiles: many firmwares let you set performance per system, saving battery on simple consoles.
Keeping things safe
- Only download firmware and tools from the projects' official pages, usually on GitHub. Unofficial "pre-loaded" images often contain pirated games and sometimes malware.
- Eject the microSD card properly from your computer to avoid corruption.
- Keep a note of your settings, so a reinstall takes minutes, not hours.
- Check for firmware updates every few months. Read the release notes first, back up your saves, and don't update in the middle of a long game if a new version changes the emulator cores your saves depend on.
A note on the law
Emulator software isn't illegal in itself, but downloading copies of games you don't own infringes copyright. UK law is also stricter than many people assume about copying games you do own: a private copying exception introduced in 2014 was quashed by the High Court in 2015, so making personal backups isn't clearly permitted. Official re-releases and legally sold collections are the safest route.
Sources and further reading
- Libretro / RetroArch documentation
- Onion OS for Miyoo Mini (GitHub)
- ROCKNIX (GitHub)
- GOV.UK: Exceptions to copyright
Facts checked on 20 October 2026. Spotted an error? Tell us and we will correct it.