hello,
The F-Droid build only ships arm64-v8a and x86_64, so it can't be installed on devices running a 32-bit Android userspace. I hit this on an e-ink reader, where the installer refuses the app (INSTALL_FAILED_NO_MATCHING_ABIS) and F-Droid marks it incompatible.
Device
- Haoqing M6 e-ink reader (RK3566), Android 11 (API 30), so minSdk is fine
- ro.product.cpu.abilist = armeabi-v7a,armeabi, ro.product.cpu.abilist64 empty, zygote is zygote32
- The SoC is 64-bit capable, but the firmware only runs 32-bit apps. Many e-ink readers, Android TV boxes and other budget devices ship this way.
Request
Add an armeabi-v7a build, i.e. the Rust target armv7-linux-androideabi next to the two targets listed in BUILD.md (aarch64-linux-android, x86_64-linux-android), plus the matching ABI in the Gradle config.
As far as I can tell the native part is the vendored libgit2 / OpenSSL / OpenSSH crates, which I expect can be cross-compiled for that target too, but I haven't tried it.
If it helps, I can test a build on the device above.
hello,
The F-Droid build only ships arm64-v8a and x86_64, so it can't be installed on devices running a 32-bit Android userspace. I hit this on an e-ink reader, where the installer refuses the app (INSTALL_FAILED_NO_MATCHING_ABIS) and F-Droid marks it incompatible.
Device
Request
Add an armeabi-v7a build, i.e. the Rust target armv7-linux-androideabi next to the two targets listed in BUILD.md (aarch64-linux-android, x86_64-linux-android), plus the matching ABI in the Gradle config.
As far as I can tell the native part is the vendored libgit2 / OpenSSL / OpenSSH crates, which I expect can be cross-compiled for that target too, but I haven't tried it.
If it helps, I can test a build on the device above.