147

In my current project I make use of multiple .so files. These are located at the armeabi and armeabi-v7a folder. Unfortunately one of the .so files is a 6MB and I need to reduce file size. Instead of having a fat APK file, I would like to use just the armeabi files and remove the armeabi-v7a folder.

According to the NDK documentation, armeabi-v7a code is extended armeabi code which can contain extra CPU instructions. This all goes beyond my expertise, but I question why one would like to have both armeabi-v7a and armeabi code. There must be a good reason to have both, right?

On my test devices this all seem to work fine. These have ARM v7 CPU's. Is it safe to assume that everything works now?

Improve this question
3
  • 2
    You might want to give this blogpost a read now. It is thorough and up-to-date: androidbycode.wordpress.com/tag/armeabi-v7a Commented Aug 8, 2016 at 13:37
  • 2
    And now the doc says: armeabi is deprecated in NDK r16. Removed in NDK r17. No hard float. Commented Aug 15, 2018 at 5:02
  • 1
    For those coming later, take a look at here. Commented Aug 15, 2018 at 5:04

3 Answers 3

Reset to default
166

Depends on what your native code does, but v7a has support for hardware floating point operations, which makes a huge difference. armeabi will work fine on all devices, but will be a lot slower, and won't take advantage of newer devices' CPU capabilities. Do take some benchmarks for your particular application, but removing the armeabi-v7a binaries is generally not a good idea. If you need to reduce size, you might want to have two separate apks for older (armeabi) and newer (armeabi-v7a) devices.

Update 2012-09; Google's Play Store finally has support for uploading different APKs (each targeting a different CPU architecture), with the so-called "multiple APKs" feature:
https://developer.android.com/google/play/publishing/multiple-apks

Where maybe each APK needs to have a different version code (even if they all are actually the same version, just with different CPU target).

But Update 2023; Google recommends creating "App bundle" instead of using "multiple APKs" feature:
https://developer.android.com/guide/app-bundle

Where for "App bundle", the Play store can automatically bring down the download size, based on the device which's downloading.

Improve this answer
Sign up to request clarification or add additional context in comments.

8 Comments

Thanks for your clear reply. It will be a good idea to do benchmarking as well of splitting the application in 2 APK files. The latter is actually a very good idea! Many thanks!
Where Can I find difference between the both ABI ? I'm very instersted to understand real differences...
ARM manuals? infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344c/…
Not really. You are limited by Google Play used to differentiate APKs (screen size, target version, etc). There are some apps that have their native libs as a 'plugin' of sorts, but you need to download another APK for you platform. Check MX Player for example.
Long overdue. They seem to still recommend single APK when possible though.
|
61

EABI = Embedded Application Binary Interface. It is such specifications to which an executable must conform in order to execute in a specific execution environment. It also specifies various aspects of compilation and linkage required for interoperation between toolchains used for the ARM Architecture. In this context when we speak about armeabi we speak about ARM architecture and GNU/Linux OS. Android follows the little-endian ARM GNU/Linux ABI.

armeabi application will run on ARMv5 (e.g. ARM9) and ARMv6 (e.g. ARM11). You may use Floating Point hardware if you build your application using proper GCC options like -mfpu=vfpv3 -mfloat-abi=softfp which tells compiler to generate floating point instructions for VFP hardware and enables the soft-float calling conventions. armeabi doesn't support hard-float calling conventions (it means FP registers are not used to contain arguments for a function), but FP operations in HW are still supported.

armeabi-v7a application will run on Cortex A# devices like Cortex A8, A9, and A15. It supports multi-core processors and it supports -mfloat-abi=hard. So, if you build your application using -mfloat-abi=hard, many of your function calls will be faster.

Improve this answer

2 Comments

According to developer.android.com/ndk/guides/abis.html: The armeabi-v7a ABI uses the -mfloat-abi=softfp switch. So what do you mean by supports -mfloat-abi=hard?
Think of the EABI as a template for the compiler to follow. For instance, the register R0, in most situations, is both the first argument of a function and the return of that same function. It also tells the compiler how to implement floating operations. Depending on the abi it might only have one or the other or both.
9

Instead of having a fat APK file, I would like to use just the armeabi files and remove the armeabi-v7a folder.

The opposite is a much better strategy. If you have minSdkVersion to 14 and upload your apk to the play store, you'll notice you'll support the same number of devices whether you support armeabi or not. Therefore, there are no devices with Android 4 or higher which would benefit from armeabi at all.

This is probably why the Android NDK doesn't even support armeabi anymore as per revision r17b. [source]

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.