Compatibility with Google Android 14

[Korb]

osmin 1.14.2 (2025-05-21):

This app isn't compatible with the latest version of Android. Check for an update or contact the app's developer.

Model: Vivo T1 (4G) / V2153
OS version: Funtouch OS 14
Hardware version: MP_0.1
Build number: PD22010F_EX_A_14.2.14.0.W20
Baseband version: .HA.1.1.c2-00054-DIVAR_GENSP_PACK-1.29062.10 7
Kernel version: 4.19.157-perf+. 1 Thu May 8 10:36:27 CST 2025
Compile time: 8 May 2025 05:31:38
Android security update: 1 May 2025
Google Play system update: 1 April 2025
Software parameter update: 14 March 2025

This is strange, given that this version of the app has a min SDK of 28 and a target SDK of 35.

[janbar]

My primary phone is on LineageOS 22 (Android 15) arm64, and my secondary phone is on Android 10 armhf. As I can see the app works without issues.

Do you have selected the right architecture ? From Android 12 you can only install app for arm64.

[Korb]

Do you have selected the right architecture?

F-Droid does not allow you to choose the architecture:

[janbar]

The Apk with architecture armeabi-v7a, are no longer usable from Android 12 and up.

You have to install the published Apk (arm64-v8a) in the release page https://github.com/janbar/osmin/releases/tag/1.14.2.

[Korb]

You have to install the published Apk (arm64-v8a) in the release page

You are right, after running osmin-arm64-v8a-release-signed.apk there is no warning about incompatibility of software with the OS. Are you planning to replace v7a with v8a on F-Droid, or will you host two versions of your application there at the same time? Should I rename this topic in connection with this, or close it as a mistake?

[janbar]

I have no control over what F-Droid publishes. I guess the F-Droid team is working to fix this issue, that impacts all users with Android 12 and up.

[Korb]

This is not entirely true on both counts.

Firstly, even the main F-Droid repository is edited mainly by third-party requests. The small team developing the F-Droid website, backend, and mobile app is mostly engaged in these requests, but not in user content. Since you did not personally submit an RFP for your application to F-Droid, then most likely someone else did, most likely not related to the F-Droid development team. In some cases, nothing is required from the project owner (in some cases, months of work are required).

As for the problems of users of current versions of Android, this also does not bother the F-Droid team much. Just look at the target API of their own application. And at their bug tracker, where the hated Google has been discussed for years, forcing developers to remake their applications to please the corporation, allegedly not receiving anything comparable in return.

What I mean is that if you, or I, or anyone else who is genuinely interested in updating an app in the F-Droid catalog submits a request, the app in the catalog will likely be updated. Otherwise, it will likely soon become a dead soul, where it will be displayed in the catalog, but will not show the option to install. Until it is moved to the F-Droid archive catalog. (also at someone's request.) Making it even less accessible for those users who, for one reason or another, do not use Google Play, but want to have the ability to automatically update installed applications.