-
Notifications
You must be signed in to change notification settings - Fork 0
Heavy Emulators and BIOS
LodorOS's sweet spot is the systems MinUI runs natively — 8/16-bit consoles, GB/GBC/GBA, PS1 and friends — and those work out of the box on every supported Miyoo device.
The Miyoo A30 (my282) and Miyoo Flip V2 (my355) additionally ship standalone N64 and PSP emulator paks (mupen64plus and PPSSPP), integrated with LodorOS's save sync. These bundle the emulator but never a BIOS or game content.
The Miyoo Mini family stays with the MinUI-native set — that hardware's honest ceiling.
Bundled emulator licenses and source links are listed in CORE-LICENSES.txt at the root of the release zip.
LodorOS never ships console BIOS or firmware. Systems that require one won't boot until you supply your own files.
Since 0.9.5, a BIOS-dependent game that can't launch shows an honest error naming exactly which files are missing — no more silent black screen. Two ways to fix it:
- Download BIOS from your server — if your RomM library has firmware for the system, the Lodor menu's Download BIOS action pulls it to the right place on the card.
- Copy files manually to the emulator's BIOS/system directory on the card.
A game that "won't launch" on a BIOS-dependent system is almost always a missing BIOS, not a LodorOS bug — the launch error will tell you.
Prefer .chd — a single, compressed, self-contained file. It's the most reliable format on a handheld. .gdi/.cue reference separate track files and are easier to get wrong. Multi-disc games download and assemble automatically (.m3u).
No proprietary emulator is ever bundled (e.g. DraStic for NDS) — bring your own where you want them.
Anbernic H700 devices get their emulation from muOS itself — RomM sync comes from Lodor for muOS riding on top. Same story for TrimUI with Lodor for NextUI on stock NextUI: the host firmware owns emulation, Lodor owns the library + saves.