[Feature Request] Enable `Show 'Quit RetroArch'` by default on Android TV
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- android, c
- Domain
- mobile-dev
Research direction
Search the source for menu_show_quit_retroarch to find where its default is defined, then trace the existing Android TV detection used to default the menu driver to ozone rather than glui. Reuse that platform check so the option defaults to on only for Android TV while remaining off on mobile and unchanged on desktop. Verify by building/running the Android TV configuration and checking the setting's default in Settings → User Interface → Menu Item Visibility.
Written by the indexing model from the issue text.
Description
Description
Currently, the setting Settings → User Interface → Menu Item Visibility → Show 'Quit RetroArch' is disabled (Off) by default across all Android builds, including both standard Android (phones/tablets) and Android TV.
While keeping this option hidden makes sense on standard mobile devices, it creates a poor user experience on Android TV setups where users rely primarily on a gamepad—leaving you dependent on the physical remote just to exit the app.
Current Behavior
Show 'Quit RetroArch' default state:
- Desktop releases:
On - Android (Mobile/Tablet):
Off - Android TV:
Off
Expected Behavior
- Android (Mobile/Tablet): Remain
Off. Users can easily close the app via standard OS navigation (tapping the Overview/Recents button or swiping up and holding with gesture navigation, then swiping the app away). - Android TV: Set to
Onby default. Users on Android TV expect to navigate and exit the application entirely using a gamepad. When the option is hidden, users are forced to reach for their TV/streaming box physical remote to press the Home button—which is inconvenient in the dark, or problematic when traveling with a streaming device without bringing the remote along.
Additional Context
- Platform detection already exists: RetroArch is already capable of distinguishing between standard Android and Android TV environments at startup/initialization. For example, on 32-bit Android builds,
Settings→Drivers→Menuautomatically defaults to: gluion standard Android devicesozoneon Android TV devices (e.g., Google TV Streamer)
The same platform detection check used to determine the default menu driver could be leveraged to set menu_show_quit_retroarch to true on Android TV while keeping it false on standard Android.
- Restart behavior vs. background process state: Using Quit RetroArch still triggers RetroArch's proper shutdown/restart routine—any changes to settings that require a restart are properly applied the next time RetroArch launches. However, it is worth noting that even after selecting Quit RetroArch on Android TV, navigating to Android TV Settings → Apps → See all apps → RetroArch still shows the Force stop button as active, indicating that the underlying Android process remains cached/open in the background rather than being completely terminated by the OS.
Related Issue
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 2.4k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libretro/RetroArch
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/RetroArch#20061 · 3 comments ·
Maintainers usually reply within 2 days
-
[Feature Request] [UX] Improve descriptions for "Rewind Buffer Size" and "Rewind Buffer Size Step"Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libretro/RetroArch#19915 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
All issues in libretro/RetroArch
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libretro/parallel-n64#858 ·