Files
faceclaw/docs/validation-android-16k.md
T

1.7 KiB

Android 16 KiB page compatibility

The initial debug APK triggered Android's page-size compatibility warning. Its libfaceclaw_llama.so LOAD segments were aligned to 4096 bytes. The other six packaged arm64 libraries were aligned to 16384 bytes, and APK ZIP alignment already passed zipalign -c -P 16 4.

The llama JNI shared library now links with both max-page-size=16384 and common-page-size=16384, matching the LC3 JNI library. This changes the native binary layout rather than hiding the compatibility warning or disabling debug. Gradle already tracks CMakeLists.txt as an input, and Ninja reconfigures and relinks existing builds after this change.

Reproduce the regression and artifact checks inside devenv shell:

python3 -m unittest discover -s tests -p test_apk_pages.py
bash build.sh
python3 scripts/check-apk-pages.py platforms/android/app/build/outputs/apk/debug/app-debug.apk
"$ANDROID_HOME/build-tools/35.0.1/zipalign" -c -P 16 4 platforms/android/app/build/outputs/apk/debug/app-debug.apk

The checker rejects the initial APK and reports its misaligned llama library. Five unit tests cover 4 KiB rejection, 16 KiB acceptance, RELRO boundaries and invalid ELF program headers. APK checks inspect all arm64/x86_64 shared libraries.

Reference: Android's 16 KiB guidance. Static alignment and successful installation do not prove every native code path works on-device; voice/LLM features still require functional testing.

The rebuilt APK passes all seven native-library checks, ZIP alignment and APK signature verification. The connected Pixel 10 Pro Fold reports getconf PAGE_SIZE = 4096; actual execution with 16 KiB pages remains untested.