-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Your RomM library, in your pocket. LodorOS is a MinUI fork that turns a Miyoo handheld into a thin client for your self-hosted RomM server — browse your whole collection offline, download a game on demand, and have your saves sync both ways automatically around every play session.
You keep your ROMs and saves on your server. The handheld holds only what you're playing. Wi-Fi-dark by default, sync when it can.
- Whole-library browsing offline — every game in your RomM collection appears in the menu as a lightweight stub, with box art, even when the device is offline.
- Download-on-launch — pick a game you don't have yet; it downloads, verifies, and boots.
- Two-way save sync — saves pull before you play and push after you quit, to RomM, automatically. Restore an older save from the server any time. Sync is decided by save content, never by the device clock — and your unpushed progress is never overwritten.
- Private by design — reach your server over Tailscale (a private tunnel, works anywhere) or Cloudflare Access (a service-token'd public endpoint) — your RomM is never exposed on the open internet.
- One release, every device — the same download boots the whole Miyoo fleet; each device reads its own platform folder.
| Device | Platform | Notes |
|---|---|---|
| Miyoo Mini Plus | miyoomini |
128 MB — Cloudflare Access only (no Tailscale) |
| Miyoo A30 | my282 |
ships standalone N64 + PSP |
| Miyoo Flip V2 | my355 |
ships standalone N64 + PSP |
Have a different device? The same sync engine ships for other families as native add-ons — no custom firmware flash needed:
- Anbernic H700 family (RG35XX Plus / H, RG34XX, RG40XX, RG CubeXX) → Lodor for muOS
- TrimUI (Brick / Smart Pro) → Lodor for NextUI
(Through v0.9.4.1, LodorOS itself also shipped for the H700 family and the Powkiddy RGB30. As of 0.9.5, LodorOS focuses on the Miyoo fleet; H700 owners get a better fit — and no reflash — via Lodor for muOS. The last all-platform build remains available as v0.9.4.1.)
You'll need a self-hosted RomM server, 4.8.0 or newer (the device-pairing API ships in 4.8.0) and a supported device.
- Installation — prepare a card for your device.
- Reaching your RomM server — Tailscale, Cloudflare Access, or LAN.
- RomM server setup — expose your server privately.
- Emulators & BIOS — what ships per device, and BYOB.
- Upgrading — move an installed card to a new release.
- Troubleshooting · Reporting problems.