Reporting Problems

Reporting problems

Found a bug? File it at github.com/lodordev/lodoros/issues. A report with the right log attached usually gets fixed in one round-trip; a report without one starts with us asking for it.

Where the logs live

Everything Lodor-related logs to the pak folder on the card:

Tools/<platform>/Lodor.pak/

where <platform> is your device's folder: miyoomini (Mini Plus), my282 (A30), my355 (Flip V2), rg35xxplus (H700 family), rgb30.

Log	What it covers
last-sync.log	The most recent library/catalog sync from the launcher
romm-run.log	Download-on-launch: fetching, verifying, and booting a game
wifi-debug.log	Wi-Fi bring-up and connectivity checks
syncd.log	The background save-sync daemon
session.log	Per-play-session save pull/push
tailscaled.log	The bundled Tailscale client (Tailscale setups only)

The MinUI launcher's own logs live in .userdata/<platform>/logs/ — worth grabbing if the UI itself crashes.

What to include in an issue

1. Device model (e.g. Miyoo Mini Plus, RG34XX) and platform folder.
2. LodorOS version — the contents of version.txt at the card root.
3. RomM server version (Settings → About in RomM's web UI). Must be ≥ 4.8.0 — see RomM server setup.
4. How the device reaches the server — Tailscale, Cloudflare Access, or LAN.
5. What you did, what you expected, what happened.
6. The tail of the relevant log — the last ~50 lines of whichever log above matches the failure. Paste it in a code block or attach the file.

Scrub before posting. Logs can contain your server hostname; config.json contains credentials — never attach it. Replace private hostnames with romm.example.com if you'd rather not share them.

Check Troubleshooting first — the common failures (exFAT cards, pairing errors, Wi-Fi quirks) are already written up there.