I will mention two things that may or may not help:
The first is app builds of armeabi-v7a, I found that even although they don't fall into the category of converting to 16kb page alignment, Google does not appear to like/want them anymore in your project, as soon as I removed armeabi-v7a the message went away, assuming your arm64-v8a libcontrols.so is aligned correctly to 16kb. All I needed to do was delete the armeabi-v7a folder/dir in the libs of the project. I know what folk will say, but that will drop a load of device support?...yep, no idea how to get around this, and would love to hear other's experiences with this.
Second, I never tried the useLegacyPackaging route, as I really wanted to be on Gradle/AGP > v8.5.1 as suspected the legacy route might come back to bite me later, although you may have a very valid reason for staying at your current gradle version.
I upgraded Gradle to v8.7 (it's also easier to have a generic named folder for the path so you don't have to keep changing config files/shell/bat files etc. to repoint to a new folder), or you can move the current data out of the current named gradle version path and copy your new upgraded v8.7 contents inside the current folder (saves a lot of messing about with paths), as long as you know what version it is, it should be fine.
Under your buildscript in build.gradle you may find that you need to change the dependency class as below if you upgrade gradle to v8.7, I believe this is the class supporting this version:
dependencies {
classpath 'com.android.tools.build:gradle:8.6.0'
}
You will also need to change the wrapper version in build.gradle to match.
This was my experience, armeabi-v7a being dropped is a big issue for me tbh, I get they (Google) want things to move forward to 64-bit and have technically been warning about this for a good few years, but there are still brand new phones being sold with armeabi-v7a architectures, albeit budget end phones.
Hopefully this will help.
Recent
