Android support for 16 KB page sizes

[ditavo98]

Google Play now requires Android apps to support a 16KB SQLite page size to comply with memory usage policies and improve performance.

We noticed that this is not yet supported in the current version.

Could you please confirm if support for this is planned in an upcoming release?

Thanks for your support!

[amrgetment]

I don't know if I will be able to fix it, I found that I have to migrate the Flutter gradle first then I check the native package if it supports 16kb or it will block me

[amrgetment]

x86 / x86_64 builds are mainly for emulators (Android Studio emulators often run on Intel CPUs).
so if I removed the .so file from the x86_64 folder it will support the 16kb but it won't run on some emulators
so the best solution is someone with c knowledge to support 16kb for x86_64
https://github.com/TimothyGu/lame/tree/master/libmp3lame

[amrgetment]

I think if we can configure gradle to exclude x86_64 from the release build it would solve the issue

[ditavo98]

Yes, we can configure Gradle to exclude x86_64 to solve this issue, but we will run into problems when the app is running on an x86_64 device, right?

[amrgetment]

x86_64 is for intel emulator, no intel mobiles as far as I know
but I am not sure if I put it on my library gradle do it will work for you or not

    buildTypes {
        release {
            ndk {
                // Explicitly exclude x86 and x86_64 in release
                abiFilters "armeabi-v7a", "arm64-v8a"
            }
        }

[amrgetment]

My gradle fix works, I will make a new release with the fix later today or tomorrow

[amrgetment]

it should be solved by record_mp3_plus 1.4.0

[ludy-auror]

Hi @amrgetment thanks for the fix. After upgrading, I was able to pass the Google Play verification that now my app is 16kb compliant which is awwesome. I tested running my app on 4kb page sized devices, it can record MP3 audio just fine.

However, when I tested on a 16kb page sized Android 16 emulator, as soon as I start recording, my app crashes immediately. Here's the stack trace

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
ABI: 'arm64'
Timestamp: 2025-09-17
Process uptime: 55s
Page size: 16384 bytes
Cmdline: com.myapp
pid: 9041, tid: 9602, name: Thread-9  >>> com.myapp <<<
uid: 10214
agged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x00007488a7bd3210
   x0  b4007488b601a5f0  x1  00007488a7bd4210  x2  0000000041fcfb72  x3  00007488a7bd4000
   x4  000000004069b621  x5  000000003d5201fa  x6  000000000000002d  x7  b40074899e9d4054
   x8  0000000000000004  x9  00000000000001d8  x10 0000000000000007  x11 000000000000002f
   x12 0000000000000030  x13 000000000000002f  x14 0000000000000029  x15 ffffffffffffffff
   x16 0000000000000001  x17 0000748b78129694  x18 b4007488b601f9c8  x19 0000000000000001
   x20 b4007488b601a5f0  x21 00007488a7bd3000  x22 00007488a7bd3210  x23 0000000000000000
   x24 00007488a8f6fa78  x25 b4007488b602f5f0  x26 00007488a8f6fc78  x27 0000000000000002
   x28 0000000000000081  x29 00007488a8f70044
   lr  00007488a7bac488  sp  00007488a8f6f930  pc  00007488a7b93c30  pst 0000000080001000
16 total frames
backtrace:
     #00 pc 000000000000bc30  /data/app/~~JnIEdNWYAHZKG8r8i-bPqA==/com.myapp-6fRfvrJYFTOo_4gdM12K8A==/base.apk!libmp3lame.so (offset 0x21ec000) (init_fft+144)
     #01 pc 0000000000024484  /data/app/~~JnIEdNWYAHZKG8r8i-bPqA==/com.myapp-6fRfvrJYFTOo_4gdM12K8A==/base.apk!libmp3lame.so (offset 0x21ec000) (psymodel_init+2468)
     #02 pc 000000000001c1c4  /data/app/~~JnIEdNWYAHZKG8r8i-bPqA==/com.myapp-6fRfvrJYFTOo_4gdM12K8A==/base.apk!libmp3lame.so (offset 0x21ec000) (lame_init_params+3204)
     #03 pc 000000000033f500  /apex/com.android.art/lib64/libart.so (art_quick_generic_jni_trampoline+144) (BuildId: b229f9d1b6196afaae086f29f029f907)
     #04 pc 0000000000689588  /apex/com.android.art/lib64/libart.so (nterp_helper+152) (BuildId: b229f9d1b6196afaae086f29f029f907)
     #05 pc 0000000000b5baea  /data/app/~~JnIEdNWYAHZKG8r8i-bPqA==/com.myapp-6fRfvrJYFTOo_4gdM12K8A==/oat/arm64/base.vdex (j9.b.p+126)
     #06 pc 000000000068a444  /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: b229f9d1b6196afaae086f29f029f907)
     #07 pc 0000000000b5b9e0  /data/app/~~JnIEdNWYAHZKG8r8i-bPqA==/com.myapp-6fRfvrJYFTOo_4gdM12K8A==/oat/arm64/base.vdex (j9.b.d+0)
     #08 pc 0000000000689588  /apex/com.android.art/lib64/libart.so (nterp_helper+152) (BuildId: b229f9d1b6196afaae086f29f029f907)
     #09 pc 0000000000b5b4be  /data/app/~~JnIEdNWYAHZKG8r8i-bPqA==/com.myapp-6fRfvrJYFTOo_4gdM12K8A==/oat/arm64/base.vdex (j9.b$b.run+30)
     #10 pc 0000000000328194  /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+612) (BuildId: b229f9d1b6196afaae086f29f029f907)
     #11 pc 00000000002d9348  /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+216) (BuildId: b229f9d1b6196afaae086f29f029f907)
     #12 pc 0000000000421028  /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+932) (BuildId: b229f9d1b6196afaae086f29f029f907)
     #13 pc 0000000000420c74  /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallbackWithUffdGc(void*)+8) (BuildId: b229f9d1b6196afaae086f29f029f907)
     #14 pc 0000000000080df8  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+232) (BuildId: 2445fc73ede03b9536eef49355aff375)
     #15 pc 0000000000073dd8  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 2445fc73ede03b9536eef49355aff375)
Tombstone written to: tombstone_02

I did some quick research on the so library by running command, the output suggests the lib is 64kb 0x10000 aligned
I think the libmp3lame.so needs to be re complied

readelf -lW lib/arm64-v8a/libmp3lame.so | grep 'LOAD'
  LOAD           0x000000 0x0000000000000000 0x0000000000000000 0x0396a8 0x0396a8 R E 0x10000
  LOAD           0x03a3a8 0x000000000004a3a8 0x000000000004a3a8 0x000c60 0x0128e0 RW  0x10000

[amrgetment]

@ludy-auror it won't work on intel x86_64 emulator, please choose arm emulator not x86_64
That's why I added it to the readme
It would be helpful if you add a screenshot of the arm selection in the emulators list for me in the readme

[ludy-auror]

@amrgetment I have an Apple Silicon Macbook, so I was testing on the ARM64 16kb page size emulator.
Here's the screenshot, note that I am using "Pre-Release 16 KB Page Size Google Play ARM 64 v8a System Image" that Google suggested

Did you test on a 16kb page size device?

[amrgetment]

Oh no, it looks like the only solution for now is dropping support for all Intel x86_64 emulators
In the future if someone need it he need to find a C developer to fix the lame mp3 library
I will drop x86_64 fully to solve your issue

[ludy-auror]

Let me summaries:

• Dropping x86_64 support in 1.4.0 will solve the Google Play warning, so we can keep pushing new versions which is awesome
• But the libmp3lame.so wasn't built compatible from ground up, so we will run into runtime crashes once running on a true 16kb page size device, regardless of x86_64 or arm64. This is the crash that I shared earlier
• Luckily, there's no device on the market that is 16kb page size, so not a problem as for now
• In the future, someone needs to re compile ibmp3lame.so with new NDK toolchain. I may find some time to do it later, but I am pretty occupied at the moment

[amrgetment]

@ludy-auror @ditavo98

[amrgetment]

The windows devs will suffer 😂, arm is slow on windows 😎

[cdmunoz]

Thanks @amrgetment for your efforts with the lib.
Still it's failing on arm 64 v8a emulators. @ludy-auror, have you done any progress with recompilation of the lib?