Update install-android.md: Installation via Obtainium, and DeGoogle notice#1109
Update install-android.md: Installation via Obtainium, and DeGoogle notice#1109davidhedlund wants to merge 57 commits intolibretro:masterfrom
Conversation
Make the "Installation notes" and its sub-sections visible in the menu bar
davidhedlund
changed the title
DeGoogle notices
Removed Yalp Store, not maintained
Added "Installation via Obtainium" section
The F-Droid release is incomplete
davidhedlund
changed the title
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! |
Added a new "RetroArch APK Package Variants" section with a table (6 builds: universal/stable/nightly + arch-specific aarch64/ra32) with Android 7.0+ multi-package compatibility notes distinguishing package name handling pre/post-Nougat.
|
Added
See 996997f for context. |
Wording
Clarified instructions for installing stable and nightly builds on the same device.
Move "Installing both stable and nightly builds on the same device" under "Android 7.0+ (Nougat)"
Rename the "Compatibility Notes" section to "Multi-Package Handling"
Removed my duplicated text that I already added under the "RetroArch APK Package Variants" section
Added "Universal APK" section
Move the "RetroArch APK Package Variants" section to the topmost position. This section defines essential technical terminology, package types, architecture support, and installation compatibility referenced throughout the rest of the document. Add the remaining sections under a "Sources" section.
Fix buildbot section
RetroArch Plus note: Despite the implication of superiority in its name, RetroArch Plus builds support approximately 80 fewer cores than APKs from retroarch.com across all variants.
Added "RetroArch (stable 32/64-bit, Play Store)" and "RetroArch Plus (stable 64-bit only, Play Store)" sections
Improve "RetroArch (stable 32/64-bit, Play Store)" section
Improve "RetroArch Plus (stable 64-bit only, Play Store)" section
Fix "Installation via Google Play servers (obsolete)" sectional indentations
On Android versions prior to 8.0, the APK installation prompt displays a pre-checked "Allow this installation only" checkbox—uncheck it to quickly install RetroArch updates, which is especially relevant when subscribing to daily RetroArch Nightly downloads via Obtainium.
Incorporated a table of custom RetroArch APK package variants into each section.
Fixed typo
Improved top table
Added "Overview" table section
Added "Title" column to the overview table
Converted the overview table to HTML to enable a colspan header.
improve multi-package installation examples
general improvements
Add subsections for issues to maintain clean section names. Improve the "Google Play servers" section.
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
3 participants
Uh oh!
There was an error while loading. Please reload this page.