This question might be redundant or a possible duplicate, but I use an NDK library that runs only on ARM devices. Is there a way I could know what percentage of Android devices my app can support based on CPU architecture just like these statistics on Android Platform Versions?

My goal is to ascertain the number of devices my app won't support.

  • Currently there's only Chromebooks with Android capability that actually use x86 chips.
    – Mavrik
    Commented Oct 16, 2023 at 17:31

4 Answers 4


Since ultimately you're deciding whether x86 is still worthy of spending effort to support, I'm listing several facts about x86 for Android devices here:

  • Intel had decided to discontinue the Atom SoC line for phones/tablets.
  • The last generation of handheld Atom SoC - x3, x5 and x7 series - were at best equipped on lower-end Chinese Android tablets. Some come with phone/data capabilities (based on x3-C3230RK). Regardless, none made it onto mainstream devices, specifically phones.
  • The last x86 Android device that's widely popular was ASUS' Zenfone 2, released in March 2015 - and even its subsequent variants shifted to Qualcomm's Snapdragon 410/615, partly due to the compatibility issues Android on x86 had back then.
  • Spreadtrum (now UNISOC) has a partnership with Intel and just announced SC9861G-IA in March 2017 / SC9853I in August 2017. However, this has yet to come to fruition on consumer devices, and given Spreadtrum's focus on low-end devices for emerging markets, this SoC likely won't give x86 on Android much significance.

EDIT: The first device utilizing the above Spreadtrum SoCs, the Leagoo T5c, is now on pre-sale. Leagoo is a small China-based firm, and the device mainly targets India, not to mention another variant of the same device (the T5) with a conventional SoC is sold at the same time, so it doesn't change the assumptions above that it will remain unpopular.

  • 2
    This essentially means that there are not a lot of devices out there that are not ARM based. Hence, I think my app will support a larger part of the multitude of Android devices. Thanks!
    – sri
    Commented Nov 14, 2017 at 9:36
  • @iBug Same here (I actually owned 2, sold one of em). The driver issues make Windows on them sometimes a pain to use, let alone Android, I'd say.
    – Andy Yan
    Commented Nov 14, 2017 at 9:51
  • @AndyYan Driver issue? No problem if you disable driver auto-update in WU
    – iBug
    Commented Nov 14, 2017 at 10:28
  • 3
    OTOH, you may want x86 support and other tweaks to run the app on Chromebooks.
    – Alex Cohn
    Commented Apr 12, 2018 at 8:46
  • 1
    Checking on Spreadtrum, they only ever launched two x86-64 SoCs, both in 2017, so they would appear to have given up. Commented Sep 22, 2023 at 16:01

I ended up with this conclusion after searching a lot.

Useful info in Unity Stats.

  • ARMv7: 98.1%

  • Intel x86: 1.7%

However I was not satisfied so I verified it from many resources.

According to Android Documentation.

armeabi was deprecated in r16. Removed in r17. No hard float.


Historically the NDK supported 32-bit and 64-bit MIPS, but support was removed in NDK r17.

Summery after searching a lot

  • mips (deprecated)
  • mips64 (deprecated)
  • armeabi (deprecated)
  • armeabi-v7a (required — most popular architecture nowadays)
  • arm64-v8a (required — newer version of armeabi-v7a)
  • x86 (optional, very limited number of devices, like Asus Zenfone 2, Genymotion/ Android emulator)
  • x86_64 (optional, very limited number of devices, like Asus Zenfone 2, Genymotion/ Android emulator)

I should also mention that ChromeBook are using Intel processors based x86 and x86_64 architecture. (Only add these architure when you support ChromeBook)


If you app supports armeabi-v7a and arm64-v8a architectures because they have around 99% of Android devices.

Important Suggestion

Do you worry about app size (you should), you should split your apk for multiple abi. Android studio and play store support uploading multiple apk, so that app has only 1 architecture ndk files.

So this will be much efficient to build multiple apk.

Important links


From Google Play Console (supporting a minimum of Android 4.1 and landscape screen):

  • 2
    how did you find this information on google developer console? I can't find report with device architecture.
    – Saqib
    Commented Jul 9, 2020 at 22:42
  • Can you please update stats to current (2022)?
    – tunafish24
    Commented Oct 4, 2022 at 13:05

A new doc has dropped:


So officially Google says:

Most Android phones have ARM chipsets. However, many ChromeOS devices use x86 chips. The difference is not important for basic apps written in Kotlin or Java. However, for apps written in native code, including those created with game engines, the chipset in the device can be an important concern.

Ideally, all apps and games with native code ship with all four major Android ABIs (Application Binary Interfaces): armeabi-v7a (arm32), arm64-v8a (arm64), x86 (x86_32), and x86_64.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .