Repository navigation
Create save-and-restart.md. Update install-android.md, install-gnu.md, and tv.md - #1109
davidhedlund wants to merge 75 commits into
Conversation
Make the "Installation notes" and its sub-sections visible in the menu bar
DeGoogle notices
Removed Yalp Store, not maintained
Added "Installation via Obtainium" section
The F-Droid release is incomplete
You don’t need to be signed in to adjust Play Protect settings
wording
Wording
improve "sideloading" text
Install unknown apps
Improved phrasing for sideloading steps
The step to disable Play Protection is complex and should be read carefully to ensure success on all Android devices.
wording
|
I'm not sure about Obtanium being recommended. |
Completed the Obtainium installation guide
The primary question is whether to recommend automated installation/upgrade methods like F-Droid or Obtainium over manual ones. I believe we should. If others agree, then Obtainium should be the recommended option, as the F-Droid release is still incomplete. I encourage anyone interested in forming their own opinion to try Obtainium from F-Droid firsthand. It’s become one of the most popular Android apps for download automation in recent years—for example, it ranks among the top apps in the GitHub Store—for good reason. It’s also worth noting that Obtainium is Android TV–friendly, making it suitable for use across all Android devices, and it is downloading the apks from the buildbot archive which also is used for manual downloads. |
wording
Added: "The only difference is that Obtainium automates this process and provides update notifications, helping users stay current and avoid reporting issues from outdated versions."
Added: "It’s also worth noting that Obtainium is Android TV–friendly, making it suitable for use across all Android devices"
Moved “Installation via Obtainium” section below “Manual Downloads” and removed “(recommended)” from its heading.
I’ve moved the “Installation via Obtainium” section below “Manual Downloads” and removed “(recommended)” from its heading, so this PR should now be ready for approval. |
|
I think this looks good overall, but the F-Droid stuff sounds a little negative. Perhaps it would make sense to explain why it's the way it is, like:
|
Updated the "Installation via F-Droid (incomplete)" section. Most issues in libretro/RetroArch#16126 have been solved, but I've submitted this report since the issue persists across Google streaming devices: * F-Droid release missing assets for armeabi-v7a ABI (32-bit ARM), pixelated fonts and icons - libretro/RetroArch#18756
I've spent a few hours today thoroughly reinvestigating all significant F-Droid-related issues that affect many users. See the commit: |
Following hizzlekizzle's advice (libretro#1109 (comment)), added note that the F-Droid RetroArch release ships with minimal assets to reduce APK size, and requires using the Online Updater (Main Menu → Online Updater) to match the retroarch.com release.
I followed your advice: e286614 Thank you! |
Fix "Google Play servers" sub-section names
add stable and nightly links to the overview table
Added "Compatibility of `com.retroarch.ra32` on 64-bit ARM Devices" section
Improve "Compatibility of `com.retroarch.ra32` on 64-bit ARM Devices" section
|
The rollout for the new Obtainium crowdsourced app website is dynamic, and the RetroArch items are working wonderfully at https://apps.obtainium.imranr.dev/apps?categoryMode=inclusive&q=RetroArch now that my previous issues have been sorted out. This PR is fully ready to be merged and will make a significant difference. |
@fpscan I haven't received any feedback yet. Would it make the review process easier if I split this PR into separate pull requests for Obtanium and the DeGoogle notice? |
Corrected spelling errors in the installation guide.
|
@davidhedlund Could you resolve the conflicts here? |
Done: 5f5363e |
Corrected spelling of 'available' in the documentation.
Added "AM/AppMan web catalog" sub-section
remove dup
…ghtly release * **Clarified Android Limitation:** Updated documentation to explain that the `Main Menu → Quit` option does not exist in RetroArch Android releases any more. * **Added HDMI-CEC Remote Support:** Clarified that basic buttons like **Arrows, OK, Back, and Exit** now work inside RetroArch, but because **Back** and **Exit** still will not exit the app, the virtual home button workaround is **still needed**.
Removed duplicate section on frame rate fluctuations and its fix.
Clarified functionality of HDMI-CEC remote buttons for RetroArch navigation and TV overlay.
Most modern Smart TVs and Digital Media Players include built-in HDMI-CEC hardware, though budget or older models on either side may lack this feature.
Added a guide for saving configurations and restarting RetroArch across different platforms.
Added export configuration section for mobile and desktop platforms, including limitations and methods for saving configurations.
Added note about ADB restrictions for Android TV file access.
Expand HDMI-CEC Remote Support: Updated documentation to explicitly cover and differentiate standalone Digital Media Player remotes alongside TV remotes.
|
@fpscan @LibretroAdmin I've run into a recurring issue where overlapping PRs get merged ahead of mine, causing frequent merge conflicts. Since I've been working on this PR for nearly a year, continually resolving these conflicts and re-checking overlaps creates a lot of extra overhead and increases the risk of missing details. If bandwidth is tight for reviews right now, could we look into onboarding more volunteers to help clear the review queue? |
Updated instructions for automatic saving on Android.
Clarify instructions for pulling configuration file via ADB.
Created
Updated: