NDK 27 arm64 Navigation Native libraries have non-16 KB GNU_RELRO segment ends #7978

Android API: 36 (Android 16) for the bounded emulator result below; the static artifact check is API-independent.
Mapbox Navigation SDK version: 3.33.0, then 3.32.3 (-ndk27; Navigation Native 324.33.0, then 324.32.3).

Steps to trigger behavior

1. Download each official AAR linked below, for example curl -fLO '<AAR URL>'.
2. Extract the arm64 libraries: unzip '<artifact>.aar' 'jni/arm64-v8a/*.so' -d extracted (use a separate destination for each AAR).
3. Run the Android NDK tool llvm-readelf -lW extracted/jni/arm64-v8a/<library>.so for each library.
4. Check every LOAD: p_align is at least 0x4000, is a power of two, and (VirtAddr - Offset) % p_align == 0; all pass here. For GNU_RELRO, calculate (VirtAddr + MemSiz) % 0x4000; the nonzero values below reproduce the defect against the documented end-alignment check.

Official AARs (dash-native-ndk27 ships both libraries):

• dash-native-ndk27-324.33.0.aar — SHA-256 6535ae5b24bb8699c6b48ee979923f67c71000e81907fff8d969bfd8b7c609c3.
• dash-native-ndk27-324.32.3.aar — SHA-256 7bc055468a652eadf4d7450625ed252dcf04a36d3df07c68639f0094abc77cb8.

Expected behavior

The GNU_RELRO segment end is aligned to 16 KB, so (VirtAddr + MemSiz) % 0x4000 == 0, per Android's RELRO guidance, or Mapbox documents why this layout is safe on native 16 KB devices.

Actual behavior

Both libraries retain nonzero GNU_RELRO end remainders in the newest stable 3.33.0 dependency, although every LOAD meets 16 KB alignment:

In a prior bounded Android 16 / API 36 arm64 emulator run with 16 KB pages and linker/package compatibility mode disabled, Navigation 3.32.0 / Navigation Native 324.32.0 -ndk27 completed one Free Drive start/stop with seven emulator GPS fixes: no crash observed. No Active Guidance was exercised. That result does not establish safety, physical-device compatibility, or runtime behavior of 3.33.0/3.32.3; those versions were checked statically only.