Unlike most of the other items you download through the SDK Manager, the HAXM driver doesn’t install automatically. Scroll down and you’ll see an ‘Intel x86 Emulator Accelerator (HAXM Installer)’ option - download it.
To install HAXM, launch the SDK Manager and make sure the ‘SDK Tools’ tab is selected. However, if you see an error message when you try to create an x86 AVD, or nothing appears in the ‘x86 Images’ tab, then you may not have the Intel Hardware Accelerated Execution Manager (HAXM) installed.
To download additional x86 system images for different versions of the Android operating system, you just need to click the corresponding ‘Download’ link.
When you’re creating a new AVD, simply select the ‘x86 Images’ tab in the ‘System Image’ window, and then choose from one of the available x86 images. If your IDE and SDK are up to date, then creating an x86 AVD is generally pretty straightforward. Using an x86 system image can speed up the emulator considerably, so this is the option you’ll typically want to opt for. The Android Phone emulator supports system images that emulate two different CPUs: ARM and Intel x86. Using these tips I’ve seen the emulator go from sluggishly terrible to actually usable on a few different systems. Many of these tips can be combined for better performance. Here are some tips to make your emulator faster for any Android development tool, but my examples are specific to Delphi XE5. Better get comfortable, because the emulator takes a long time to load. However, the emulator does have one massive flaw, which becomes glaringly obvious the first time you launch it.
It gives you the ability to test your Android projects across more devices than you could ever realistically hope to get your hands on. The emulator is one of the most powerful tools in the Android developer’s arsenal. In some parts of the world, Intel Atom-based Android devices are becoming more common, so those emulators do serve a purpose. So you are technically testing on a niche hardware configuration that is not likely to be what your app runs on in the real world. Yes, they are faster, but the majority of Android devices (in the USA at least) are ARMv7. These almost always are using an x86/Atom Android image, which runs faster because it doesn’t need to emulate the CPU, running x86 code on your host CPU (much like the iOS Simulator). You may see some articles or tips about using the Intel HAXM, BlueStacks Android Emulator for pc, Genymotion Emulator, Android-x86 or some other high-performance Android emulator.