Please post here with information you think would be helpful to others, especially if you were new and you had to ask about it in Discord! My hope for this post is to help the moderators find information that would be good for a FAQ article.
If it’s something that’s not well documented, someone else can expand on information later, but the idea is to identify areas that need more documentation.
For loose information I’ll roll it up into a section up at the top, and it will eventually be moved to a User-Curated FAQ entry.
Things I wish I knew when I first installed muOS; there’s an app for Bluetooth, scrappy is amazing, and there’s actually a way to set the LED light to solid red instead of blinking red.
I think there’s a common misconception that muOS lacks Bluetooth, when in reality it’s been implemented in the backend, and a combination of Bluetooth App and support directly in Retroarch exist.
Scrappy, Artie and other community scrappers are also great.
Many settings that “can’t be adjusted” in muOS can be changed in Retroarch directly. And if settings need to be changed across all systems, Retroarch can be accessed in the App menu. Once your global settings are in place, any changes you make in an individual console can be set as a custom override, which plays nicer than a custom config.
If you screw up your Retroarch settings and don’t know how to fix it, you can restore the muOS Retroarch defaults in the task toolkit (also available in apps). You don’t need to perform a reflash to fix this.
DON’T DO THIS INSIDE RETROARCH. That will remove all of the tweaks that have been made to ensure that it runs properly on your device. A lot of work has gone into this.
Once you have all of your settings the way you want, you can save that as a configuration profile under Customisation. If you ever break Retroarch by messing with the settings, you can restore it from here.
For example:
I sync my saves with a PC running Batocera that’s connected to my TV at home through Syncthing. Batocera expects saves to be stored in a folder that matches the name of the source ROM folder (GBC is the ROM folder, so the save folder is called GBC as well). By default, muOS has the saves stored in a folder that matches the given emulator. So when I do a fresh install, one of the first things I do is launch Retroarch and change this setting. Once that configuration is saved, it works across all systems.
Retroarch is a program that entirely deserves its own guide, and which many guides do exist for, but some of the settings that pertain specifically to muOS could definitely be explained, such as saving overrides and some settings that affect performance.
The task toolkit is also a nifty thing to remember, not a lot of people know that you can basically revert to default by running restore scripts inside it.
I’m also planning on writing a guide for Syncthing at some point, it’s an interesting program.