The content explorer is designed as a read-only interface. It allows you to browse and launch games or media, but intentionally does not support management actions like deleting, renaming, copying, or moving files.
Why read only?
This is done by design. Allowing file management within the interface introduces risks. Accidental deletions, renaming, or moving files to incorrect locations can cause confusion or break expected behaviour. Even with confirmation prompts, mistakes are easy to make.
Content Management
File management should preferably be done outside of muOS.
- Use Dingux Commander, or Simple Terminal, directly on the device
- Connect your system to a computer and manage files via ADB or MTP
- There is also the SFTPGo WebUI or direct SSH if your device has network capabilities.
These options give you full control without putting essential files at risk during regular use.
Using a “Trash” like method
This idea has been considered, but even indirect deletion features introduce complexity and unwarranted results. The current approach keeps the system stable and simple, avoiding unexpected behaviours.
Supporting Power Users with Advanced Options?
We recognise that some users might want more control, but muOS prioritises stability and consistency as much as possible. By restricting changes inside the explorer, we avoid edge cases that could disrupt less technical users. Power users still have full file access externally through SSH or ADB.
Exploring not Managing!
Just to reiterate the above once again, we are not adding any file management functionality to the content explorer. If we were to add such functionality it would be a completely separate module.