Emulation Handheld Firmware and Custom OS Options
Software support matters more than specs when choosing an emulation handheld.

The software determines how much of a device’s capability reaches the player, so the strongest purchase considers firmware support before price or hardware. The right choice is not one universal “best” OS, but an actively supported option that fits the device and the way it will be used.
Why firmware matters more than the hardware spec sheet
Stock firmware on budget devices is often slow to boot and short on features, and the makers often stop updating it soon after launch. The hardware has room to do more, but the software does not make that room available. Leaving stock firmware installed is the most common way buyers underuse what they paid for.
Custom firmware, or CFW, replaces that stock OS with a community-built alternative. Its gains include cleaner interfaces, proper save states, working sleep and wake, Wi-Fi file transfer, RetroAchievements, and PortMaster access to native game ports. Faster startup can matter as much as another feature when the goal is to spend limited time on a short game and minimize configuration. Every major project covered here is free and open source, so there is no license fee separating the hardware from better software.
The structural problem that makes "best firmware" the wrong question
Which firmware is best? First, which chipset is inside the handheld? muOS targets Allwinner H700 devices, ROCKNIX covers Rockchip hardware and selected higher-end devices, OnionOS serves the Miyoo Mini family, and Knulli spans multiple chipsets.
The major options also share underlying emulator cores, including RetroArch and standalone emulators such as PPSSPP and DuckStation. On the same chipset, raw emulation accuracy for a given system is therefore nearly identical across firmware. The meaningful differences are interface, boot speed, device coverage, and community depth. Firmware changes the experience around emulation more than the fidelity of emulation itself.
Linux firmware suits retro systems through PS1/Dreamcast territory, while Android provides the standalone emulator ecosystem for demanding targets such as PS2 and GameCube. Buying hardware before knowing those limits can leave an owner relying on a project in maintenance mode or on a single maintainer.
muOS: the benchmark for Allwinner H700 devices
muOS is the most polished actively maintained CFW for H700 devices and the default first choice for an Anbernic RG35XX-family handheld. Its focused support makes it a strong starting point for someone who wants a capable device to feel more direct and less encumbered by its stock software. That recommendation does not mean every update has been frictionless. An April 2026 r/SBCGaming thread comparing muOS, ROCKNIX, and Knulli on RG35XX-family devices raised recurring complaints about boot-time regressions after recent muOS updates. The same concern also appears on muOS’s community forum.
The ceiling is its device list, which contains 13 official device configurations in the supplied material. muOS does not support Rockchip devices or provide a path to newer high-end handhelds such as the Odin 3 or Retroid Pocket 6. Its artwork workflow also differs from the EmulationStation-based alternatives. For someone coming from Batocera or RetroPie, the practical distinction is that Knulli and ROCKNIX can scrape cover art and metadata directly over Wi-Fi, whereas muOS more commonly involves scraping on a computer first.
OnionOS: what a device-specific firmware can achieve
OnionOS takes device focus further by serving only the Miyoo Mini family. That narrow scope allows a level of polish that broader projects have not matched. Game Switcher shows this best: it lets players move quickly between recent games without going back to the main menu. There is no equivalent comfort feature in the broader CFW ecosystem. It has fewer settings and is built around how people use one family of hardware.
That depth comes with a lifespan tied to the devices themselves. OnionOS is in maintenance mode, and the hardware it serves is winding down. Yet “stable and finished” is not the same as “abandoned and broken”. For Miyoo Mini and Mini Plus owners, it is still the best and only real CFW choice, however slowly work on it moves. Completeness is a legitimate destination for device-specific software.
Knulli: one firmware across multiple chipsets
Knulli serves people who want the same familiar interface on handhelds from different makers. It is a Batocera fork built for portable devices rather than Batocera’s PC and single-board-computer focus. Its SCARAB build 20260511 was released May 11, 2026. Supported hardware includes the Anbernic RG35XX series, RG40XX series, Powkiddy RGB30, and TrimUI Smart Pro. That breadth makes it useful when a household’s handheld collection does not share one chipset.
The shared foundation also brings Batocera themes, scrapers, and configuration tools into Knulli. Its built-in scraper retrieves artwork and metadata over Wi-Fi, while Netplay provides online multiplayer on supported emulators. A theme from a Batocera or RetroPie setup is more likely to transfer to Knulli than to muOS because those systems share EmulationStation front-end technology. The benefit is continuity, both when changing devices and when configuring several of them.
The cost is real overhead. Knulli takes longer to boot than muOS, and its interface has lots of features but feels less snappy, which users who make that switch often complain about. For a multi-device household, consistent settings and presentation can be worth the wait. Knulli is also the stronger recommendation for first-time CFW installers on the RG35XX H because its installation process is well documented. It and muOS optimize for different needs rather than occupying different rungs of one quality ladder.
ROCKNIX: the Rockchip option for higher-end hardware
ROCKNIX is the direct successor to JELOS. JELOS officially retired in early 2024, and everyone on its development team moved to ROCKNIX, bringing the codebase, support for devices, and what the community had learned. Older JELOS guides thus lead to a project whose work now carries on under the new name. That lineage matters because search results do not retire when software does.
ROCKNIX is the main choice for newer high-end Rockchip hardware that is more powerful than H700 devices. Its support also extends beyond Rockchip. The June 2026 stable release added the Ayaneo Pocket line, including Ace, DMG, EVO, DS, S2K, and S2, and the AYN Odin 3 line, including Thor and Thor Lite. These newer, more powerful handhelds now have a documented way to run Linux.
Installing it is also easier for many R36S owners who have been following ArkOS guides. With most panels, owners can leave the device-tree blob files as they are, avoiding a step that caused many first-boot failures with ArkOS on newer screen panels. Once running, ROCKNIX offers pre-configured RetroAchievements and device-to-device save syncing through Syncthing, with cloud sync handled separately by rclone. OTA updates work over Wi-Fi, and built-in Moonlight adds game streaming to the device’s uses.
ArkOS, GarlicOS, and the projects that no longer take new installs
Older recommendations need a date attached to them, especially when the recommended software still arrives on factory cards. That is why ArkOS still matters to R36S buyers, even though dArkOS has taken its place. That successor’s last release was March 2026, and development runs essentially at one maintainer’s pace. Support for R36H/R36 Plus/Max/Ultra variants is still in beta and has yet to be finished. An active forum thread is not, by itself, evidence of finished support for the device in the shopping basket.
Other familiar names require different qualifications. JELOS has no current release to download, because its forward path is ROCKNIX. GarlicOS, an early community favorite, is effectively abandoned in 2026 after stalled development, with muOS and Knulli now covering its practical role more fully. AmberELEC, which lacks official support for R36S and was still receiving pre-release updates as of October 2026, is relevant chiefly to advanced users seeking its particular interface because of its slower development, manual configuration, and device-tree renaming.
These distinctions separate a retired name from a slow project and a complete device-specific system. They also help keep buyers from taking an old installation guide as advice on what to buy. Knulli and ROCKNIX are the only two major projects still taking new device requests in the landscape described here.
Android handhelds and why firmware replacement is the wrong lens for them
What about a Retroid Pocket? For an Android handheld, replacing firmware is largely the wrong question because the meaningful choices are standalone emulators and hardware capability. Users install emulators directly rather than beginning with SD card flashing and device-tree files. Android’s emulators work better for demanding systems such as PS2 and GameCube, which run poorly on Linux handhelds with chips that are just as fast or even faster.
The Retroid Pocket 5 makes that distinction concrete. It runs Android 13 with full Google Play access, allowing direct installation of RetroArch, PPSSPP, Dolphin, and other standalone emulators. It is the mid-range Android handheld pick in this comparison. No custom firmware closes the power gap between a budget Linux handheld and a higher-end Android device running native standalone emulators.
The buyer’s choice is therefore between Linux’s snappier retro-focused experience through PS1/Dreamcast and Android’s ecosystem for PS2 and above. Dual-boot devices offer both, but cost more and are harder to use. Cloud gaming is a separate bonus with its own limits. Starting November 2026, Xbox Cloud Gaming introduces monthly allowances of five, ten, and fifteen hours depending on plan tier, with extra hours available for purchase. PlayStation Plus Premium cloud streaming supports PlayStation consoles, Windows PCs, and Sony’s PlayStation Portal, but not Android/iOS devices or third-party handhelds.
Nintendo's legal campaign and what it means for Switch emulation specifically
Nintendo’s August 2026 legal campaign concerns Switch emulation specifically. On August 17, 2026, Nintendo filed seven DMCA notices at GitHub in one day and removed more than 400 repositories. The biggest single notice targeted the network of Suyu forks. Those actions disrupted an important emulation target without making every emulator or custom OS part of the same dispute.
Nintendo’s complaints rely on the DMCA’s anti-circumvention provisions. Playing Switch games through an emulator requires decrypting content protected by Nintendo’s encryption, and circumventing that protection is the specific target. This approach lets Nintendo pressure projects without litigating the abstract legality of emulation. muOS, ROCKNIX, Knulli, and OnionOS do not involve Switch decryption and are not subjects of this campaign.
For NES through PS1 retro emulation, the legal environment described here is unchanged. Buyers who chose higher-end Android handhelds just for Switch emulation now have a less settled set of software choices than they had a year ago. Their preferred emulator may be harder to find or in flux. Advice on which Switch-specific project to use can therefore go out of date fast, whatever platform it runs on.
Matching firmware to device before buying: a decision framework
The buying sequence begins with the chipset. H700 opens muOS and Knulli, while RK3326/RK3566/RK3588 hardware points toward ROCKNIX and, where supported, Knulli. Miyoo Mini hardware leads to OnionOS, and Android leads to standalone emulators. For a multi-handheld household, Knulli’s shared interface may outweigh the appeal of a faster, narrower option. For an R36S, ROCKNIX is the straightforward choice, with dArkOS an alternative when ArkOS lineage is specifically wanted.
Next, check the firmware’s official supported-device list at purchase time to verify the support described in an older review. Board revisions within one product line can require different image files, and support for a new model such as the TrimUI Brick Pro may take months after launch. Then check when the project last shipped a release. ROCKNIX’s monthly cadence, dArkOS’s single-maintainer pace, and OnionOS’s maintenance mode represent different support conditions.
Installation need not be treated as a permanent commitment. For the SD-card-based custom firmware path discussed here, the replacement goes on an SD card, and putting the stock card back restores the factory state. Android remains the separate app-installation path. The consequential commitment happens earlier, when money goes toward hardware with either a suitable software path or an uncertain one.


