Replies: 1 comment 2 replies
-
|
Downloading and installing an apk on mobile is basically the same process as you would do on PC.
*If you've never done this before, you might have to grant your file manager "All files access" permission. The confusion to know which apk to download is understandable. Unfortunately, this falls on the users knowledge of their specific device. If your device doesn't say somewhere within its Settings you can find this info by using 3rd party utility/tool apps or by researching online. A decent place for online mobile research is phonedb.net which I'll reference to below. Moto G Power XT2041-4: ARMv8-A (32bit or 64bit) is your main target architecture but your device does support others as well which are not listed. Otherwise, if your not sure which architecture you should install you can usually install the "universal" apk or *When using Obtainium to install apps, Obtainium will tell you what architectures your device supports if using the selector to pick an apk to install. More advanced users won't use this selector. |
Beta Was this translation helpful? Give feedback.
-
When I'm installing apps from within AuroraStore, I don't have to make a choice and in NeoStore, one version is highlighted as "recommended". I suspect that this is not possible in Obtainium because Obtainium is technically not an app store app (and sites like github aren't app stores), correct? |
Beta Was this translation helpful? Give feedback.
-
|
With F-Droid/NeoStore, the NeoStore makes this selection automatically (Obtainium also tries to do this when installed; but since Obtainium can download any APKs from any source and the naming of the APKs is not standardized in any way (F-Droid has the advantage that it is standardized between the individual F-Droid repositories) and not everyone would comply with such a standard, the user often has to manually intervene). The Google Play Store does not store APKs, but AABs. They work more like XAPKs: There is one APK file in the AAB that contains the app, one APK per configuration for the screen diagonal, one APK per configuration for the resolution and one APK per configuration for the arch. The Google Play Store downloads this AAB and extracts the app and the appropriate configurations for your respective device and then installs them in a specific order. The AuroraStore downloads the appropriate configurations and the app for your device and also installs the APKs in a specific order. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I am interested in trying Obtainium, but I'm finding the documentation for installation somewhat lacking. From the repo's README, there is a heading called "Installation", but all it contains is a link to the Releases page to download the files.
My main confusion here revolves around what to do with the files. It looks like each release version has 18 files associated. I believe the relevant file for installation will be one of
app-arm64-v8a-release.apk,app-armeabi-v7a-release.apk,app-release.apk, orapp-x86_64-release.apk, but there is nothing to indicate to me which one I should be using, or how to install an APK onto my phone. It would be greatly appreciated if the installation steps could be more directly listed as a procedure that users can follow.In the meantime, any guidance in this thread for me specifically would be nice. Particularly, I have a Moto G Power (Model number XT2041-4) and I'm not clear on whether I need to download the file by opening Github on my phone's browser, or if I need to download it to my computer (running Linux Mint 21) and then install it onto the phone via USB.
Thank you for your time.
Beta Was this translation helpful? Give feedback.
All reactions