This directory resides on the ANDROID_SDK_ROOT. Digging through the subfolders I figured out that the directory looks like this: android-sdk-windows\system-images\android-22\google_apis\armeabi-v7a The weird thing is, there is also an android-sdk folder in the ANDROID_SDK_ROOT so I thought maybe Eclipse is looking there. I did check on the path describe on his answer and yes my copy of system image resides under the subfolder default when I look on the user directory (on Windows). It doesn't make answer had shed some light into the problem. Having a system image for Android API 22 causes this error and the weird thing is that all of the environment variables pointing to the correct directories. Consulting each of the answers here, it didn't match my situation. Just wanted to share my experience on this problem. this XDA-Forum entry: How to use THE FAST! BlueStack as your alternate Android development emulator. In XDA-Forums I read about MEmu - Most Powerful Android Emulator for PC, Better Than Bluestacks. See also their site on Google+, this post from Cyril Mottier and this guide on reddit. In the comments of the post above you can find a reference to Genymotion which claims to be the "fastest Android emulator for app testing and presentation". Roman Nurik posts here that the Intel emulator with Android 4.3 is "blazing fast". See a tutorial for the Intel emulator here: HAXM Speeds Up the Android Emulator. Intel provides the " Intel hardware accelerated execution manager", which is a VM based emulator for executing X86 images and which is also served by the Android SDK Manager. Note : As per you786 comment if you have previously created emulator then you need to recreate it, otherwise this will not work. You are able to turn on GPU emulation to get a faster emulator: using SDK rev 3 and System Image rev 2 (or higher).The "ARM EABI v7a System Image" must be available.
0 kommentar(er)
