ASIC

Android Security Intelligence Center — System Images, CVE Tracker, Exploit Database & Emulator Testing

-
Total CVEs
-
Bulletins
-
Critical
-
High
-
Medium
-
Emulator Testable
-
Has Public Exploit

Filters & Search

Which ABI should I use? Architecture Guide

Intel / AMD (x86 family)

Linux, Windows, older Intel Macs

ABIPerformance
x86_64Native — fastest Uses KVM/HAXM hardware acceleration
x86Native (32-bit compat) Slightly less efficient
arm64-v8aRuns, very slow Translated via software emulation
armeabi-v7aRuns, very slow Translated via software emulation

Always use x86_64 images on Intel/AMD. ARM images will run but extremely slowly (software emulation).

Apple Silicon (ARM Macs)

M1, M2, M3, M4 chips

ABIPerformance
arm64-v8aNative — fastest
armeabi-v7aWorks (32-bit compat)
x86_64Translated (Rosetta)
x86Translated (Rosetta)

Always use arm64-v8a images on Apple Silicon Macs.

Quick Reference

ABIIntel/AMD (Linux & Windows)Apple Silicon (macOS)
x86_64NativeTranslated via Rosetta
x86Native (legacy)Translated via Rosetta
arm64-v8aRuns, very slowNative (best)
armeabi-v7aRuns, very slowWorks (compat)

Practical rule: On Intel/AMD → use x86_64. On Apple Silicon → use arm64-v8a. Modern Android is moving toward 64-bit only (x86_64 + arm64-v8a), so stick to 64-bit ABIs unless doing compatibility testing.

Non-native images (e.g. x86_64 on Apple Silicon via Rosetta) will run significantly slower as every instruction must be translated at runtime. Always prefer images matching your host CPU architecture for usable performance.

Loading...
CVE Type Severity Component Emu Exploit Affected Versions Patch Level Bulletin Source Test Image
Loading CVEs...