# Support Android 16 KB page sizes **URL:** \ **Category:** FMOD Engine\ **Tags:** android\ **Created:** [July 24, 2024, 6:28am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913 "2024-07-24T06:28:26Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![MaskHao](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@MaskHao](https://qa.fmod.com/u/MaskHao)\ **Post date:** [July 24, 2024, 6:28am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/1 "2024-07-24T06:28:26Z")
## Support 16 KB page sizes Beginning with Android 15, Android supports devices that are configured to use a [page size of 16 KB](https://developer.android.com/guide/practices/page-sizes) (16 KB devices). If your app uses any NDK libraries, either directly or indirectly through an SDK, then you will need to rebuild your app for it to work on these 16 KB devices. Related Files: libfmod.so libfmodL.so Version: 2.02.23 Test Method: [https://developer.android.com/guide/practices/page-sizes#test](https://developer.android.com/guide/practices/page-sizes#test) Cmd: ```auto objdump -p libfmod.so | grep LOAD ``` Result: ```auto LOAD off 0x0000000000000000 vaddr 0x0000000000000000 paddr 0x0000000000000000 align 2**12 LOAD off 0x0000000000050000 vaddr 0x0000000000050000 paddr 0x0000000000050000 align 2**12 LOAD off 0x000000000010a000 vaddr 0x000000000010a000 paddr 0x000000000010a000 align 2**12 LOAD off 0x0000000000110000 vaddr 0x0000000000110000 paddr 0x0000000000110000 align 2**12 ``` Not 16 KB ELF alignment.（actually the latest verison 2.03.02 does not align either） Could you please provide adapted 16kb elf alignment libfmod.so or source code for libfmod.so. ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [July 25, 2024, 5:51am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/2 "2024-07-25T05:51:57Z")
Hi, Thank you for bringing this to our attention. I have passed it on to our development team and it will be supported in an upcoming release. Unfortunately, I cannot provide source code or an adapted file. ---
**Author:** ![MaskHao](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@MaskHao](https://qa.fmod.com/u/MaskHao)\ **Post date:** [July 25, 2024, 6:35am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/3 "2024-07-25T06:35:23Z")
Thanks for your reply, looking forward to new version release. ---
**Author:** ![wizermil](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/wizermil/32/5607_2.png) [@wizermil](https://qa.fmod.com/u/wizermil)\ **Post date:** [November 25, 2024, 2:19pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/4 "2024-11-25T14:19:15Z")
Hi, FYI when I try to launch our game using fmod core 2.03 on 16KB aligned virtual device I have this crash: ```auto * thread #1, name = 'imple.elixirapp', stop reason = breakpoint 4.1 * frame #0: 0x00007095060b41b8 libart.so`art_sigsegv_fault frame #1: 0x00007095060b474c libart.so`art::FaultManager::HandleSigsegvFault(int, siginfo*, void*) + 1096 frame #2: 0x00007097a71ef06c libsigchain.so`art::SignalChain::Handler(int, siginfo*, void*) + 372 frame #3: 0x00007097cd5a4848 [vdso]`__kernel_rt_sigreturn frame #4: 0x00007093c111dbf0 libfmod.so`pthread_once frame #5: 0x00007093c10fb1f0 libfmod.so frame #6: 0x00007093c10c0690 libfmod.so frame #7: 0x00007097cd690560 linker64` __dl__ ZN6soinfo17call_constructorsEv + 708 frame #8: 0x00007097cd675c30 linker64` __dl__ Z9do_dlopenPKciPK17android_dlextinfoPKv + 756 frame #9: 0x00007097cd670b70 linker64` __dl__ ZL10dlopen_extPKciPK17android_dlextinfoPKv.__uniq.234527301065430621646263515731762262959 + 76 frame #10: 0x00007097a32940cc libdl.so`android_dlopen_ext + 20 frame #11: 0x00007097a90e989c libnativeloader.so`android::NativeLoaderNamespace::Load(char const*) const + 144 frame #12: 0x00007097a90d9348 libnativeloader.so`OpenNativeLibrary + 1576 frame #13: 0x00007095061638b4 libart.so`art::JavaVMExt::LoadNativeLibrary(_JNIEnv*, std:: __1::basic_string, std:: __1::allocator> const&, _jobject*, _jclass*, std::__ 1::basic_string, std::__ 1::allocator>*) + 608 frame #14: 0x00007094fd2e1918 libopenjdkjvm.so`JVM_NativeLoad + 360 frame #15: 0x00000000620fecc4 ``` ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [December 1, 2024, 11:50pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/5 "2024-12-01T23:50:33Z")
Hi, Thank you for sharing the information. The fix is currently in development and will be included in the upcoming release, version 2.02.26 and version 2.03.05. ---
**Author:** ![justin.wasilenko](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@justin.wasilenko](https://qa.fmod.com/u/justin.wasilenko)\ **Post date:** [March 27, 2025, 5:47pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/6 "2025-03-27T17:47:17Z")
Hi there, I just upgraded to 2.02.27 in hopes of fixing this warning in Unity. However when I build the project I still get this warning. I am using Unity 6000.0.42f1, Android ARM64, (Quest 3) and Fmod 2.02.27. ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [March 30, 2025, 10:15pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/7 "2025-03-30T22:15:47Z")
Hi, Thank you for sharing the information and version number. > [@justin.wasilenko](#): > > I just upgraded to 2.02.27 in hopes of fixing this warning in Unity. However when I build the project I still get this warning. I was unable to reproduce the issue on my end, I have checked that both the `libfmod.so` and `libfmodL.so` in 2.02.27 are aligned with a 16KB page size and should be compatible with devices that require it. Could you please share the exact warning message you are seeing in Unity? ---
**Author:** ![justin.wasilenko](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@justin.wasilenko](https://qa.fmod.com/u/justin.wasilenko)\ **Post date:** [April 1, 2025, 4:44pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/8 "2025-04-01T16:44:21Z")
Sure thing, you can also see in the editor just selecting the plugin will show the warning. Also the Oculus plugin needs the same update for the same reason (As you can see in the Logs) Not sure if that’s a you or them thing? > Plugin ‘Packages/com.meta.xr.sdk.platform/Plugins/Android64/libovrplatformloader.so’ is not 16KB-aligned. This may cause issues on ARM64 devices running Android 15+. > More info: [https://developer.android.com/guide/practices/page-sizes](https://developer.android.com/guide/practices/page-sizes). > Plugin ‘Assets/Plugins/FMOD/platforms/android/lib/arm64-v8a/libfmodstudioL.so’ is not 16KB-aligned. This may cause issues on ARM64 devices running Android 15+. > More info: [https://developer.android.com/guide/practices/page-sizes](https://developer.android.com/guide/practices/page-sizes). > Plugin ‘Assets/Plugins/FMOD/platforms/android/lib/arm64-v8a/libfmodL.so’ is not 16KB-aligned. This may cause issues on ARM64 devices running Android 15+. > More info: [https://developer.android.com/guide/practices/page-sizes](https://developer.android.com/guide/practices/page-sizes). > Plugin ‘Assets/Plugins/FMOD/platforms/android/lib/arm64-v8a/libMetaXRAudioFMOD.so’ is not 16KB-aligned. This may cause issues on ARM64 devices running Android 15+. > More info: [https://developer.android.com/guide/practices/page-sizes](https://developer.android.com/guide/practices/page-sizes). > Plugin ‘Assets/Plugins/FMOD/platforms/android/lib/arm64-v8a/libresonanceaudio.so’ is not 16KB-aligned. This may cause issues on ARM64 devices running Android 15+. > More info: [https://developer.android.com/guide/practices/page-sizes](https://developer.android.com/guide/practices/page-sizes). > Plugin ‘Packages/com.unity.xr.oculus/Runtime/Android/arm64/libOculusXRPlugin.so’ is not 16KB-aligned. This may cause issues on ARM64 devices running Android 15+. > More info: [https://developer.android.com/guide/practices/page-sizes](https://developer.android.com/guide/practices/page-sizes). ![fmod_16kb](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/8/84ec6906f5b717ee04d4aa61611d68661fbde246.png) ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [April 7, 2025, 11:13pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/9 "2025-04-07T23:13:57Z")
Thank you for sharing the screenshots and error messages. I have upgraded the Oculus plugin to the latest and tested on a similar setup, but I still couldn’t reproduce the warning on my end. ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/2/2be8b902cd12cc2a58769dd43ac89a839c890f82.jpeg) > [@justin.wasilenko](#): > > Also the Oculus plugin needs the same update for the same reason (As you can see in the Logs) Not sure if that’s a you or them thing? The Log you provided does seem like coming from Oculus plugin. However, the FMOD libraries such as `libfmod` and `libfmodL` should already be properly aligned. Could you please upload the `libfmod` file you are using to your [FMOD Profile](https://fmod.com/profile#uploads) so I can take a closer look? Also, have you tried deleting the FMOD plugin folder and reinstalling it to see if the issue persists? You might want to try updating to our latest release, [FMOD 2.02.28](https://www.fmod.com/download#fmodforunity) as well. Let me know if the issue continues after that. ---
**Author:** ![justin.wasilenko](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@justin.wasilenko](https://qa.fmod.com/u/justin.wasilenko)\ **Post date:** [April 10, 2025, 3:40pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/10 "2025-04-10T15:40:58Z")
I uploaded the `libfmod` to my profile to have a look at. I will delete the FMOD plugins folder and upgrade to [FMOD 2.02.28](https://www.fmod.com/download#fmodforunity) this morning and report back. ---
**Author:** ![justin.wasilenko](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@justin.wasilenko](https://qa.fmod.com/u/justin.wasilenko)\ **Post date:** [April 10, 2025, 5:02pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/11 "2025-04-10T17:02:25Z")
After updating to 2.02.28 I still get the same warning. When you had a look at your install, did you make sure CPU is set to ARM64 on the plugin? The warning is not there if you choose ARMv7 on libfmod but appears when set to ARM64. Edit: Just updated my project to: 2.03.07 and found the same thing. ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [April 11, 2025, 12:47am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/12 "2025-04-11T00:47:26Z")
Thanks for providing the `libfmod` file, it helped me confirm that it is correctly aligned to the 16kb requirement. > [@justin.wasilenko](#): > > When you had a look at your install, did you make sure CPU is set to ARM64 on the plugin? Yes, I have confirmed that the CPU is set to ARM64 on the plugin. I was also able to reproduce the warning messages on my end. From what I can tell, this appears to be a Unity-specific bug, as the warnings only show up in **Unity 6000.0.42f1**. Fortunately, they don’t seem to have any functional impact or block the build process. Interestingly, when I previously tested with **Unity 6000.0.27f1** , I couldn’t reproduce the issue as the warnings did not appear and everything worked as expected. So as a temporary workaround, I would recommend downgrading to **Unity 6000.0.27f1** to see if that resolves the issue on your end as well. Thank you for bringing this to our attention, and please let me know if the issue persists. ---
**Author:** ![jiyongman](https://avatars.discourse-cdn.com/v4/letter/j/ebca7d/32.png) [@jiyongman](https://qa.fmod.com/u/jiyongman)\ **Post date:** [June 16, 2025, 8:58am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/13 "2025-06-16T08:58:50Z")
Hi, just wondering if it’s now safe to say that FMOD supports 16KB page sizes on Android 15 and newer? Would simply plugging the latest version of FMOD into an existing project work smoothly across both older and newer Android versions? ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [June 19, 2025, 11:19pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/14 "2025-06-19T23:19:54Z")
Hi, Thank you for reaching out! > [@jiyongman](#): > > Hi, just wondering if it’s now safe to say that FMOD supports 16KB page sizes on Android 15 and newer? Yes, starting from FMOD version 2.02.26 and 2.03.05, support for 16KB page sizes on Android 15 and newer has been added. > [@jiyongman](#): > > Would simply plugging the latest version of FMOD into an existing project work smoothly across both older and newer Android versions? Theoretically, yes. As long as you’re using a compatible Android Gradle Plugin and your app, including all native libraries is built with support for 16KB page sizes, the latest version of FMOD should work smoothly across both older and newer Android versions. Please let me know If you encounter any issues during integration, I’d be happy to help! ---
**Author:** ![jiyongman](https://avatars.discourse-cdn.com/v4/letter/j/ebca7d/32.png) [@jiyongman](https://qa.fmod.com/u/jiyongman)\ **Post date:** [June 20, 2025, 1:33pm UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/15 "2025-06-20T13:33:58Z")
Thank you so much for the clear and helpful explanation! It’s great to hear! I’ll give the integration a try, and I’ll definitely reach out if anything comes up. Appreciate your support! ---
**Author:** ![32nguyen](https://avatars.discourse-cdn.com/v4/letter/3/3e96dc/32.png) [@32nguyen](https://qa.fmod.com/u/32nguyen)\ **Post date:** [July 3, 2025, 1:02am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/16 "2025-07-03T01:02:27Z")
I’m wondering if there’s been any update regarding this issue (in unity). I’m currently using **FMOD 2.03.08** with **Unity 2022.3.62f** , but I’m still encountering the following warning from the **Google Play Console** on my latest build: > **Recompile your app with 16 KB native library alignment** > Your app uses native libraries that are not aligned to support devices with 16 KB memory page sizes. These devices may not be able to install or start your app, or your app may start and then crash. Any guidance or solution would be appreciated. Thanks! ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [July 4, 2025, 6:53am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/17 "2025-07-04T06:53:13Z")
Hi, Thank you for sharing the information and version details. I’ve tested the FMOD 2.03.08 Android libraries again, and it appears that both `libfmod.so` and `libfmodL.so` are correctly aligned to support 16 KB memory page sizes: ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/d/d3c46fde2ff593bd436b6ec01991a2eedf4dc73c.png) > [@32nguyen](#): > > **Recompile your app with 16 KB native library alignment** > Your app uses native libraries that are not aligned to support devices with 16 KB memory page sizes. These devices may not be able to install or start your app, or your app may start and then crash. Does the warning in your Google Play Console specifically point to FMOD related .so files? Could you please also double-check any other native libraries included in your project? It’s possible the alignment issue comes from another .so file. For example, are you using any other third-party native libraries (e.g., Resonance Audio, Oculus SDK, etc.)? ---
**Author:** ![krynn](https://avatars.discourse-cdn.com/v4/letter/k/65b543/32.png) [@krynn](https://qa.fmod.com/u/krynn)\ **Post date:** [July 16, 2025, 8:57am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/18 "2025-07-16T08:57:13Z")
Hello, During the Unity build process, we encountered a warning indicating a 16KB size, as shown in the attached screenshot. Could you please confirm whether this warning poses any potential issues or if it can be safely ignored? unity 2022.3.59f1 FMOD 2.02.29 android/lib/arm64-v8a/libfmod.so android/lib/arm64-v8a/libreaonanceaudio.so android/lib/arm64-v8a/libfmodstudio.so ![FMOD_16Kb](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/8/82883be087a514b0b03f4408a041dfa77c5df82a.png) ![FMOD_16Kb2](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/d/dba1f8be557a1a18dcd025f99e84621f915e6bc8.png) lib link [https://drive.google.com/drive/folders/15dXW05Bi-4RQs61dO8LX2nLOXVqh5gyH?usp=sharing](https://drive.google.com/drive/folders/15dXW05Bi-4RQs61dO8LX2nLOXVqh5gyH?usp=sharing) ---
**Author:** ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)\ **Post date:** [July 21, 2025, 12:26am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/19 "2025-07-21T00:26:52Z")
Hi, Thank you for bringing this to our attention and for sharing your `.lib` files! I was able to reproduce the issue shown in your screenshot using **Unity 2022.3.59f1** , and I’ve also confirmed that the libraries you provided are correctly aligned to support **16 KB page sizes** : ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/f/f0602e591ba50d854642cf513be1c2364a8c0a3f.png) During investigation, I found that the 16 KB page size warning only appears in specific Unity versions, such as **2022.3.59f1** and **2022.3.62f** , but not in others like **2022.3.23f1**. > [@krynn](#): > > Could you please confirm whether this warning poses any potential issues or if it can be safely ignored? So far, I haven’t encountered any functional issues related to this warning when building the project. It appears to be a false positive triggered by certain Unity versions, and in those cases, the warning can likely be safely ignored. However, if you do experience build failures or runtime problems, please let me know. As a temporary workaround, using an earlier Unity version (e.g., 2022.3.23f1) may help avoid the warning altogether. I’ve also passed this information along to the dev team for further investigation and will follow up with any updates. ---
**Author:** ![krynn](https://avatars.discourse-cdn.com/v4/letter/k/65b543/32.png) [@krynn](https://qa.fmod.com/u/krynn)\ **Post date:** [July 21, 2025, 12:57am UTC](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913/20 "2025-07-21T00:57:46Z")
I really appreciate your detailed response. [Next page](https://qa.fmod.com/t/support-android-16-kb-page-sizes/21913.md?page=2)