Choose license
DE EN FR ES IT CZ
Zurück Nach oben

32-bit Android compatibility

  • #1, by darren-beckett Yesterday Zitieren
    Hi,

    I'm building for Android using the Visionaire Android export (Gradle / vsplayer project). Recent exports appear to include only arm64-v8a native libraries under jniLibs/arm64-v8a/.

    I need to support devices that run 32-bit Android (armeabi-v7a) — for example older tablets that never received a 64-bit OS update, even though the hardware is 64-bit capable.

    Does Visionaire still support armeabi-v7a Android builds?
    If yes, is there an export setting, a separate Android player package, or documentation for obtaining the 32-bit .so files?
    If 32-bit is no longer exported by default, are legacy armeabi-v7a player libraries still available for developers who need them?
    I already ship arm64-v8a and meet Google Play's 64-bit requirement — I'm only looking to add 32-bit support alongside it for older devices.

    Any guidance or links would be appreciated.

    Thanks.
  • #2, by SimonS Yesterday Zitieren
    What models do you have in mind that are 32bit only? This segment has gotten very small and most are pretty slow. I don't think that it's worth it. You then need different min sdks that probably can't be combined with the settings in the 64bit version. 
  • #3, by darren-beckett Yesterday Zitieren
    Hey Simon,

    A device I had in mind is the Samsung Tab A SM-T510, Android 11, but 32-bit OS (armeabi-v7a). Not ancient API level, just 32-bit.

    Fair points on the small/slow segment.
    I get it may not be worth maintaining on your side, but are the armeabi-v7a player .so files still available anywhere? or has that been dropped entirely?

    Also, I thought 32/64 could share the same minSdk in one AAB via ABI splits; happy to be corrected if your pipeline differs.

    Thanks
  • #4, by SimonS 21 hours ago Zitieren
    Well, I stopped building them since I updated ffmeg last year. So would need to rebuild that. I'll check on that.