GLUI, Ozone, XMB, or RGUI on Android: choose a RetroArch menu driver
Start with GLUI for a smartphone-oriented touch interface, Ozone for the common modern controller layout, XMB for a horizontal media-style layout, or RGUI for a basic low-complexity menu. Change only the Menu driver, restart RetroArch, and prove that Load Core, Load Content, Settings, and Quit remain reachable before customizing appearance.
Do this in order
- 01
Record the RetroArch package, current Menu driver, touch/controller needs, screen size, accessibility needs, and a configuration backup.
- 02
Choose one driver for the primary need: GLUI for phone touch, Ozone for modern controller navigation, XMB for horizontal navigation, or RGUI for a basic interface.
- 03
Change only Settings → User Interface → Menu, quit normally, and restart because Libretro documents a restart requirement.
- 04
Verify Load Core, Load Content, Settings, Online Updater visibility, Quick Menu access, and Quit without loading unauthorized content.
- 05
Test text scale, portrait and landscape, touch targets, controller back/select, and one long translated label before adding themes or thumbnails.
- 06
If navigation becomes unusable, restore the backed-up configuration or previous driver instead of clearing app data.
Decision and diagnostic table
| Primary need | Starting driver | Verify first |
|---|---|---|
| Phone-first touch | GLUI | Touch targets and rotation |
| Modern controller UI | Ozone | Sidebar, back/select, thumbnails |
| Horizontal media layout | XMB | Tabs, scale, long labels |
| Basic low-complexity menu | RGUI | Font coverage and navigation |
The menu is not the core
Changing a menu driver does not change the selected libretro core, its emulation revision, game compatibility, save format, or content rights. It changes the frontend navigation layer.
Choose by the control surface
A layout attractive on a television may be awkward on a narrow touch screen. Test the actual rotation, input method, and translated labels instead of ranking drivers universally.
Recovery belongs in the decision
Back up the configuration and change one setting. Clearing app data can erase unrelated paths, profiles, playlists, and saves, turning an interface choice into a larger recovery problem.
Use only games, firmware, artwork, audio, fonts, and other media you created, dumped lawfully, or received with permission covering your use. A frontend setting never grants redistribution rights, and ArcadeShelf does not link to ROM or BIOS packs.