The followings are the number of supported devices for each ABI on GooglePlay Store.
Google Play Store shows us these number by uploading an application including native library which support each ABI.
Test application is
- min sdk 16
- no permission in android manifest
| ABI | The number of supported devices |
|---|---|
| None | 11661 |
| armeabi | 11655 |
| armeabi-v7a | 11614 |
| arm64-v8a | 1442 |
| x86 | 397 |
| x86_64 | 15 |
| mips | 1 |
| mips64 | 0 |
- Supported ABIs
https://developer.android.com/ndk/guides/abis.html#sa - Android NDK: A guide to deploying apps with native libraries
https://androidbycode.wordpress.com/2015/07/07/android-ndk-a-guide-to-deploying-apps-with-native-libraries/ - x86 hardware list
http://www.android-x86.org/hardware-list - State of MIPS, plus some statistics
https://www.reddit.com/r/Android/comments/4ofdkv/state_of_mips_plus_some_statistics/
Thanks for the stats. Hard numbers really help. If I release an app with abi splits arm-v7a and x86, will v8a and x86_64 be able to run the app, just slower (or rather not as fast as they could if i had targeted their abi)?