mlkit icon indicating copy to clipboard operation
mlkit copied to clipboard

Why don't armeabi-v7a and x86 support the 16KB page size?

Open Mouadabdelghafouraitali opened this issue 9 months ago • 1 comments

Hi,

implementation 'com.google.mlkit:segmentation-selfie:16.0.0-beta6'

As you can see, I ran a small test to check whether all .so files in my app support the 16KB page size. Here's what I got:

Checking folder: 
F:\Sdk\ndk\27.0.12077973\toolchains\llvm\prebuilt\windows-x86_64\bin\jni\arm64-v8a\libxeno_native.so => Align: 0x4000
✅ 16KB page size supported

Checking folder: 
F:\Sdk\ndk\27.0.12077973\toolchains\llvm\prebuilt\windows-x86_64\bin\jni\armeabi-v7a\libxeno_native.so => Align: 0x1000
⌠Only 4KB page size

Checking folder:
F:\Sdk\ndk\27.0.12077973\toolchains\llvm\prebuilt\windows-x86_64\bin\jni\x86\libxeno_native.so => Align: 0x1000
⌠Only 4KB page size

Checking folder: 
F:\Sdk\ndk\27.0.12077973\toolchains\llvm\prebuilt\windows-x86_64\bin\jni\x86_64\libxeno_native.so => Align: 0x4000
✅ 16KB page size supported

Why don't armeabi-v7a and x86 support the 16KB page size?

Mouadabdelghafouraitali avatar May 26 '25 12:05 Mouadabdelghafouraitali

I am also facing this same issue \e[31mFound 2 unaligned libs (only arm64-v8a/x86_64 libs need to be aligned).\e[0m I am using implementation "com.google.mlkit:barcode-scanning:17.3.0" could you please fix this issue

adarsh-dhakad avatar May 27 '25 17:05 adarsh-dhakad

The hint is in the comment (i.e., only arm64-v8a/x86_64 libs need to be aligned) - if you are doing this to meet Google's impending Play Store Requirement, you do not need to worry about these architectures :

Image

In fact, there is no practical benefit to supporting 16kb page sizes on these legacy architectures because Android doesn't support 16kb page sizes on anything other than arm64 processors (even the x86_64 Cuttlefish support is emulated).

mefsap avatar Jul 10 '25 22:07 mefsap

The hint is in the comment (i.e., only arm64-v8a/x86_64 libs need to be aligned) - if you are doing this to meet Google's impending Play Store Requirement, you do not need to worry about these architectures :

Image In fact, **there is no practical benefit** to supporting 16kb page sizes on these legacy architectures because [Android doesn't support 16kb page sizes on anything other than arm64 processors](https://source.android.com/docs/core/architecture/16kb-page-size/16kb) (even the x86_64 Cuttlefish support is emulated).

Thanks for the help. Closing this issue.

zhouyiself avatar Jul 14 '25 06:07 zhouyiself

i notice this too: here is my v8 / v7 so:

Image

xiebaiyuan avatar Aug 28 '25 11:08 xiebaiyuan

i notice this too: here is my v8 / v7 so:

Image

Please update your camera and ML kit to the latest version

adarsh-dhakad avatar Aug 28 '25 11:08 adarsh-dhakad