Update install-android.md: Installation via Obtainium, and DeGoogle notice

[davidhedlund]

• Added "Installation via Obtainium (recommended)" section.
• Noted that the F-Droid release is incomplete.
• Included notices about DeGoogling.

[fpscan]

I'm not sure about Obtanium being recommended.

[davidhedlund]

I'm not sure about Obtanium being recommended.

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.

[davidhedlund]

I'm not sure about Obtanium being recommended.

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.

[hizzlekizzle]

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:

F-Droid comes with a minimal set of assets to keep the installation size down. You'll want to stop by the Online Updater to fetch the complete assets, autoconfiguration profiles, etc. for a complete installation.

[davidhedlund]

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:

F-Droid comes with a minimal set of assets to keep the installation size down. You'll want to stop by the Online Updater to fetch the complete assets, autoconfiguration profiles, etc. for a complete installation.

I've spent a few hours today thoroughly reinvestigating all significant F-Droid-related issues that affect many users. See the commit:

• eeaf305

[davidhedlund]

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:

F-Droid comes with a minimal set of assets to keep the installation size down. You'll want to stop by the Online Updater to fetch the complete assets, autoconfiguration profiles, etc. for a complete installation.

I followed your advice: e286614

Thank you!

[hizzlekizzle]

I'm not clear on how the assets are missing for a specific arch. We use the same assets everywhere.

[davidhedlund]

I'm not clear on how the assets are missing for a specific arch. We use the same assets everywhere.

I have already replaced the ABI with just ozone, see a767ab9

I just added a detailed comparison table to libretro/RetroArch#18756 highlighting rendering failures with the ozone menu driver for the F-Droid release.