Last I heard, Google only supports Google Play Service on emulators greater than Android 4.2, so if you need to test earlier versions, it won't work without some serious hacking. The Android emulator runs on 2015 Mac Pro machine is butter smooth, compared to Windows machine.
#MAC ANDROID EMULATOR ARM VS X86 MAC OS X#
Windows 圆4 Windows x86 Mac OS X Android: 3.5-2404: 8 yl önce: VideoCommon: fix ogl lighting bug which happens because of NaN emulation: Windows 圆4 Windows x86 Mac OS X Android: 3.5-2403: 8 yl önce ARM pssel implementation. If you're integrating Google Maps into your app, you can forget about using an emulator. Windows 圆4 Windows x86 Mac OS X Android: 3.5-2405: 8 yl önce ARM Add dcbt/dcbtst/dcba noops. It’s also true that switching to a qemu based emulator made a big difference in performances of the emulator.
Android 2.3–2.3.2 Gingerbread (API level 9) / Android 2.3.3–2.3.7 Gingerbread (API level 10) / Android 3.0 Honeycomb (API level 11) / Android 3.1 Honeycomb (API level 12) / Android 3.2–3.2.6 Honeycomb (API level 13) / Android 4.0–4.0.2 Ice Cream Sandwich (API level 14) / Android 4.0.3–4.0.4 Ice Cream Sandwich (API level 15) / Android 4.1–4.1.2 Jelly Bean (API level 16) / Android 4.2–4.2.2 Jelly Bean (API level 17) / Android 4.3–4.3.1 Jelly Bean (API level 18) / Android 4.4–4.4.4 KitKat (API level 19) / Android 4.4W–4.4W.2 KitKat, with wearable extensions (API level 20) / Android 5.0–5.0.2 Lollipop (API level 21) / Android 5.1–5.1.1 Lollipop (API level 22) / Android 6.0+ Marshmallow (API level 23) For more detailed differences between the two kind of processors you can read here: ARM vs X86 - Key differences explained Coming to your question, there is.