Related
I'm currently running Android Studio Bumblebee 2021.1.1 in windows 10.
The problem I have is each time I start android studio the device list is stuck in loading devices.
I tried these solutions
android studio device list stuck on loading/51101178
android device list showing in android studio got stuck/65177069
The soulutions provided in the threads sometimes work and sometimes don't but the real problem is even if I did fix it in the run time, The next time I open android studio it's still there.
I already tried updating android studio to latest version, reinstalling android studio, deleting all the caches and plugins and resetting it to default. Completely Deleting Sdk folder and downloading again. But nothing helped I don't know where this problem could be originate from
In my case deleting the "platform-tools" folder as Dyenal said didn't work because it said that the folder was open elsewhere (even when I had shut down android studio). If that's your case too, do this.
Close android studio
Go to your task manager
Go to the "Details" tab and look for "adb.exe" as seen in the image below.
Right-click on it and "End task".
Open android studio and pretend you weren't interrupted. Cheers :)
Go to SDK folder delete platform-tools folder.. invalidate and restart the studio..works for me!
After hours of research and try and error I finally figured out what was going on.
Turns out my adb configuration was conflicting with genymotion's. Nothing could have done at the side of android studio. I went to the genymotion settings ADB tab and changed from Use Genymotion Android Tools to Use custom Android SDK Tools and it went away at last
This is a temporary solution. Open terminal and type adb devices. Once your device starts showing up in terminal, it will start showing up in loading devices too.
This problem occurs due to Windows folder accessing especially when you change the AVD folder.
Windows prevent access to Windows partition root. you have multi options for solving this problem.
Move AVD folder to another driver. Then define it on the Environment variable
Move the AVD to C:\Users\<User>\.android\avd folder. this folder is accessible for Android studio.
Run emulator from device manager, then type adb devices in cmd prompt
Restarting my computer fixed the problem for me
When using Android Studio, or any other IDE which use their own ADB, it is necessary to set Genymotion to use the correct ADB instead of its inbuilt one. It is documented here: https://docs.genymotion.com/desktop/02_Application/#use-third-party-adbsdk
I only opened task manager and there were a bunch of adb.exe open so i ended all of them while android studio is running in the background so then adb.exe started again and then i go to android studio and find out that the issue was resolved.
After updating to Android Studio 2 when I try to run my application and choose an emulator, I wait for the emulator to start and it suddenly gets killed. I can see the emulator process for some minutes but never the GUI. In Android studio, I get the error
android studio Error while waiting for the device: The emulator process for AVD was killed
This happens even if I run the emulator outside Android Studio. I have tried both an Android 6 and an Android 4.4-based emulator.
Running on a Windows 7 x64 PC. Similar post to another StackOverflow post which was closed. I have tried various ram, VM heap, and resolution settings.
I hit this issue trying to run Android API 30. In the end, I had to upgrade Android Emulator to 30.1.5 (it was 30.1.2 before this).
I had the same issue, the problem was there is not enough space in my disk drive.. you can see details about your specific situation in layer 'Event Log' this layer regularly is at the bottom on Android studio, it was my output Log:
"02:45 PM Emulator: emulator: ERROR: Not enough space to create userdata partition. Available: 3310.363281 MB at /home/user/.android/avd/my_Nexus_5X_API_27.avd, need 7372.800000 MB."
I had just 7 GB free, so just delete some GB's in my D.D. and it's working fine.
For me it seems it was a problem that OpenGL didn't work on my machine. I fixed it as follows:
Go to: Tools > Android > AVD Manager
Press the "edit" (pencil) icon next to your AVD
Change "Graphics" to "Software".
Check the free space of the emulator installation drive is more than 5 GB
Install the Intel x86 Emulator Accelerator worked for me.
This worked for me:
Tools -> SDK Manager -> SDK Tools (tab) -> Deselect 'Android Emulator' -> OK
Now, when you try to run your app, or launch device from AVD Manager, it will give the 'Install Emulator' error -> Click Ok.
This will automatically download the correct version.
For Android Studio v4.1 and above:
Menu -> Android Studio -> Preferences -> Tools -> Emulator
Uncheck Launch in a tool window option.
This issue happens when you have two Android SDK installations on your machine and the environment variable "ANDROID_HOME" points to the wrong location.
To fix it go to Android Studio settings, find the proper Android SDK location, update the environment variable and restart Android Studio / your PC.
I resolved the same issue by updating the Android Emulator.
Steps:
1. In Android Studio Go to TOOLS
2. SDK Manager
3. Android SDK
4. SDK Tools
5. Update the Android Emulator.
Then it will Run.
Check this for reference https://stackoverflow.com/a/64384372/13952516
Faced a similar issue, tried the above solutions as well and it didn't work.
Would like to suggest a simple solution which could help if the above suggestions didn't address the issue.
Solution - Try cleaning up space in the system. My problem was I had only 1GB left while trying to launch the emulator after cleaning up space got 8GB and was able to launch the emulator.
In android studio version 4.0 (WINDOWS), I could find the solution by just checking android studio welcome screen and clicking on the "Events" dropdown AFTER trying to launch the emulator (hence after getting the error):
the events section clearly shows that ANDROID_SDK_ROOT was not set in my system.
In a nutshell, whenever you see such error when starting the emulator, just check the "events" section in the welcome to android studio screen to find the real problem.
Beware that if ANDROID_HOME is not set properly, it will still tell you that ANDROID_SDK_ROOT is broken.
In my case, after installing the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 (both x86 and x64 version), the issue is solved.
But wait! Why did I know this? I will tell you my experience.
When your program meets a bug, the first thing you need to do is finding the log to debug. But where is the log file that records all the events of the Android emulator? Click Help→Show log in Explorer. And then a new window is oepned, where a file called idea.log is located, and that log file is what we are looking for.
But this file may has recorded too much verbose info, so let's do following processes to get a more simple one:
·Exit Android Studio
·Delete the idea.log
·Open Android Studio
·Click Tools→ AVD Manerger
·Start one of emulators you have created, and needless to say, the error will occur again. But the idea.log will be created and the error is recorded into the log file now!
·Exit Android Studio.
·Open the idea.log and begin to analyze it.
·Search "emulator", and in my case there are 2 messages catching my eyes:
INFO - manager.EmulatorProcessHandler - Emulator: E:\cache\SDK\emulator\emulator.exe -netdelay none -netspeed full -avd Nexus_5_API_22
INFO - manager.EmulatorProcessHandler - Emulator: Process finished with exit code -1073741515 (0xC0000135)
Obviously, the "exit code 1073741515" is something important, and actually many people have asked what it means in StackOverFlow, but unfortunately, I can't find any useful info about it. So let's pass it and focus on the first message.
Open the command line (Press "Win"+"R" → Enter "CMD" → Click "OK"), copy the above message E:\cache\SDK\emulator\emulator.exe -netdelay none -netspeed full -avd Nexus_5_API_22
and paste it to the command line. Press Enter.
I totally didn't know what this command meaned, but it's reasonable to deduce that Android Studio ran this command and resulted in the error, so I will try to reproduce the issue.
After that, an error window pop up, saying "...VCRUNTIME140_1.dll is missing...". I know I have been close to the answer. So I serch "VCRUNTIME140_1.dll Missing" on google, and people said that "downloading and installing both the x86 and x64 versions of the Microsoft Visual C++ 2015 - 2019 Redistributable will resolve this problem".
So I download both the x86 and x64 version and install them. After doing this, I run the emulator again, and everything goes well.
You need to update the following tools.
Please check your free space on your disk also. I had a same problem and finally I got I need to free up space to fix this.
If you're on the Apple Silicon (M1) chip, make sure you're using an ARM64-based emulator:
If you're not, create a new Virtual Device and use the arm64-v8a image from Other images.
Go to: Tools > Android > AVD Manager and Press the "edit" (pencil)
icon next to your AVD , Change "Graphics" to "Software".
work on my Windows 10 machine and ubuntu 18.04
If your username is not in ascii/ has spaces then this may help, as I tried all of the solutions here and couldn't fix this problem:
Note: I found this solution on this video, suggested by a user called "tatachka", this is her comment (she kindly let me share it here).
For example, I had this path
c:\Users\Таня.android\avd\Nexus_One_API_24.avd My name in Windows is
Таня, written in Cyrillic in windows encoding (cp1251). I changed the
path to e:\Distribu\AVD.android\avd\Nexus_One_API_24.avd I moved
files from disk C there and edited Nexus_One_API_24.ini changing the
path in it and everything worked.
How to change the folder path: My computer -> properties -> advanced
system parameters -> environment variables - > lower 'New...' button:
variable name: ANDROID_SDK_HOME variable value: e:\Distribu\AVD
(in my case)
After the reboot, a new folder(.android) appears in the folder
e:\Distribu\AVD containing the 'avd' folder
EDIT: For clarification, the idea here is that you don't want the path to have non-ascii characters. I moved it to C:\programs_that_cant_read_hebrew (and preformed the other steps) and it worked just fine.
EDIT: changed "English" to "ascii/ spaces" after the comments
I get this same error if you upgrade the emulator to version 30+ and run mac < 10.15
You see the real error if you run it from commandline
~/Library/Android/sdk/emulator/emulator -avd <name>
emulator: Android emulator version 30.5.3.0 (build_id 7196367) (CL:N/A)
dyld: Library not loaded: /System/Library/Frameworks/IOUSBHost.framework/Versions/A/IOUSBHost
You can fix this to upgrade to Big Sur or downgrade the emulator with these steps.
wget https://dl.google.com/android/repository/emulator-darwin-6885378.zip
unzip emulator-darwin-5395263.zip
mv ~/Library/Android/sdk/emulator ~/Library/Android/sdk/previous-emulator
mv emulator ~/Library/Android/sdk/emulator
cp ~/Library/Android/sdk/previous-emulator/package.xml ~/Library/Android/sdk/emulator/package.xml
Check if it succeed:
cd ~
~/Library/Android/sdk/emulator/emulator -version
28.0.25.0
~/Library/Android/sdk/emulator/emulator -list-avds
Source https://groups.google.com/g/flutter-dev/c/uEthfwjZBAQ/m/HSFqTgYsAgAJ
Edited April 8th 2021: I updated the emulator link to a newer version as mentioned in the comments
My case was: GOOGLE PLAY.
My virtual device was Pixel 4...
As shown on pic, Pixel4 has Google Play support, so that it give this error: " The emulator process for AVD Pixel4 was killed."
It gives error on Android Studio 4.1.1.
So that, I created a new virtual device(Pixel 4XL) and selected "SOFTWARE" for emulated performance...
Because this device doesnt have Google Play support, it worked for me.
Simple solution 2021
Go to AVD Manager
Find the emulator you are trying to use and then click on the down arrow
Select the option Show on Disk
delete every file that ends with .lock
Runs again the emulator and after this will initialize
goto tools>android>sdkmanager and update emulator and install related API level.It worked for me
This was working for me. You must update to android studio to latest version and then follow step below to update sdk tool:
Tools -> SDK Managers
Select Android SDK
Tab on SDK Tools
Check to update options available.
Press ok button
After that this procedure will take you some minutes, after it completed, everything will works fine.
I know so many people have given answers to this question many have valid points as well.
I have tried all the above possible ways, but it was not working, after reading logs from the android studio, I came to know it was a storage issue, for the emulator keep 11 GB space free and it will work.
Despite the question has been asked specifically for Windows, I will give my answer for MacOS 11.4 Big Sur, since this thread is the first hit on google when searching for this issue, and none of the answers already given solved the problem for me.
I found the solution to my problem here - for retention reasons, i will repeat the detailed steps anyway:
open Terminal and go to the directory /Users/<username>/Library/Android/sdk/emulator/qemu/darwin-x86_64/
create an xml file named entitlements.xml with the following content:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.apple.security.hypervisor</key>
<true/>
</dict>
</plist>
resign the emulator
codesign -s - --entitlements entitlements.xml --force qemu-system-x86_64
start the simulator
For me it was a problem of available space left in my computer and deleting unnecessary files solved the problem. Causes are vary from situations and you should see event tab which detailed event log are showed.
To summarize the above:
Install and reinstall HAXM 7.5.6 (only available version) under 'Android SDK' settings. Try downloading it manually, even other versions (they don't work with Android SDK), installing it from the Android/Sdk folder, etc. sc query intelhaxm in cmd should show if it is running correctly.
Virtualization is enabled in your BIOS and has been tested
Made sure the PATH variables are correct (ANDROID_HOME / ANDROID_SDK_ROOT) but NOT (ANDROID_SDK_HOME) to the folder in your settings per Here. Otherwise, you will see EVENTS on the Android Studio splash screen.
Try unchecking / rechecking Launch in a tool window in Emulator settings (and even Enable Device Frame in AVD settings)
Try rebuilding in several different combinations of android, different phones, etc (but with same levels and packages ... 30 for example)
Try Rebooting in several different configurations
Make sure all SDK Tools are up-to-date, and even try a fresh install of Android Studio. However, tried removing all of them, and adding them back.
Check your space, try to have 25GB maybe or more free
Check for Virtual Box, Antivirus Software, etc.
Open Android Studio with Administrator privileges
RUNNING ON DUAL MONITORS / DOCKING STATION ?
A) Run the emulator with everything unplugged, then plug back in your monitor! (Odd I know)... OR Better yet...
B) Create a New Hardware Profile, which will enable you to change Graphics: Automatic to Software.
In Android Studio Go to Help -> Show logs in explorer
Try to run the Emulator again of the errors are as below :
handleCpuAcceleration: feature check for hvf
cannot add library vulkan-1.dll: failed
cannot add library vulkan-1.dll: failed
Then install Microsoft VS Code and go to below path
C:\Users<User>\AppData\Local\Programs\Microsoft VS Code
Copy the vulkan-1.dll and paste in below path
C:\Users<User>\AppData\Local\Android\emulator\lib64
For me this solutions worked
For me, just deleting ANDROID_SDK_HOME from the environment variable list solved the problem
I tried every single answer in here but none of them worked, but finally I got it working when I run it on an emulator device with Android API 28. I think the problem is the emulator device couldn't run Android API 30.
I think this is problem of Android studio 2 Update or Problem to solve please Update also Android sdk version also then work properly.
I am getting the same issue as mentioned in below link.But this one has been put on hold and I am still seeking for a solution.
https://stackoverflow.com/questions/27146511/panic-missing-emulator-engine-program-for-arm-cpus-eclipse
So I would like to frame the question and ask here. Until yesterday, emulator were working fine. But since today I am receiving the following error while I am trying to open emulator
PANIC: Missing emulator engine program for 'arm' CPUS
My AVD:
This is the error I am receiving:
I have updated and installed components through SDK Manager and I even tried to restart eclipse and my pc as well.
I tried creating new AVD But nothing worked here.
Thank You in advance.
In my case, my PATH environment variable was set incorrectly. It was including
<sdk-path>/sdk/tools
Instead of
<sdk-path>/sdk/emulator
emulator.exe exists in both of these directories, so the emulator command will work either way. However, emulator-arm.exe only exists in my emulator directory.
It is related to Avast Antivirus, has found bunch of emulator-arm files in its quarantine. Problem started couple of hours ago.
What I did as temporary solution: restored emulator-arm from quarantine, added it to avast exception, paused Avast, run AVD, then resumed Avast
This error happened to me when I re-formatted my computer and tried to copy and paste my old SDK files into my newly formatted computer.
I needed to re-download the SDK’s API stuff. For example, when I re-download API 19, it added these files in red and my Emulator for API 19 worked. API 18 & 17 kept giving me the "PANIC: Missing emulator engine program for 'arm' CPUS." error message. API 18 & 17 were the files I copied and pasted in.
Just delete everything and re-install it. Especially the Tools folder.
I had the same error but I solved it differently from the others. I was trying to create an emulator to test on an older Android version on my Mac.
My mistake was I had selected the wrong tab (see screenshot). I should have clicked the "x86 Images" tab instead of the "Other Images" tab to avoid this error:
Emulator: PANIC: Missing emulator engine program for 'arm' CPU.
This error indicates that there are some missing components in the Android SDK Tools!
In my case, for some reason, Avast Antivirus recognizes the tools/emulator-arm.exe as a threat and puts it in the virus chest!
This started happening since I've updated the SDK manager and everything to latest (tools 23.0.5)
Once I've restored the emulator-arm.exe file and disabled Avast for 10 minutes, I was able to start the emulator without problems!
Note: I've tried to add the file as exception to the Avast AV but it still removes the file from my system.
Please check if your SDK Tools installation is complete and update (delete first?) everything, or at least the Tools section in the SDK Manager!
I hope that helps!
I got the same error a few minutes ago. Look into antivirus chest and try to check if emulator-arm.exe is there. Try add the file to exception of antivirus.
It is working for me. (I have got avast!). Hope this will help you
I had the same problem in the same time as you guys and I am also using Avast. But I could not find the file in the chest of Avast.
So what worked for me was to reinstall the Tools of Android SDK:
Open Android SDK Manager
Select Android SDK Tools
Click "Delete 1 package"
Once it is done, reselect Adroid SDK Tools and click "Install 1 package".
Hope it helps.
I know this is a crazy old topic, but I ran into this same problem and had a hard time solving it. This topic kept popping up on all the searches
The quick work around is to simply copy everything from
/sdk/tools To /sdk/emulator without overwriting anything.
My path looks like this
C:\Users\MyProfile\AppData\Local\Android\sdk\tools
I got the same error too this morning... and I've got Avast !
"Restore and add to exclusion" seems not to work in this case, so i manually added the exclusion...
Solution:
1- Go to Avast Control Panel > Scan > Quarantine > Right Click on "emulator-arm.exe" > Restore and add to exclusion...
2- From Avast Main Screen > Parameters > Active protection (2nd item) > File Agent (click on the wheel) > Exclusions (4th item on the left menu) > Add the complete file path of emulator-arm.exe at the bottom of the list.
Then it works for me...
Avast Antivirus is sensing emulator-arm.exe as a thread and blocking from some reasons. When you add it exclusions in Virus Chest page with right-click -> "restore and add to exclusions" it's not solved in future runnings. To solve this permanently in Avast 2015 :
Settings ->
Active Protection ->
File System Shield ->
Customize ->
Exclusions then add thread as a exclusion . And then press ok.
in my case,there was missing arm eabi v7a system image for api level 22. After downloading it started to work. so make sure that Your arm eabi v7a system image is installed for the particular API Level
If you are trying to use an Android Virtual Device (AVD) with an Android Version, whose SDK platform version you have not installed, this error also appears.
Download all the Android SDK versions whose AVD you might use, i.e., be sure you have the API level installed whose AVD you will use.
Furthermore, check the first line the next image in the column CPU (this was also giving an error). Change the CPU of your AVD, to x86 and then it will work.
There can be the bugs / updates happened in the OS. So, instead of updating in .profile, /etc/environment, or .bashrc file to point adb, emulator etc, put (copy and paste) all the emulator folder inside /usr/bin directory. Install adb tool from the terminal. This should solve everything.
And/Or, update your all environment variables in /etc/bash.bashrc file. Note that: /etc/bash.bashrc file is what gets executed everytime you open the bash terminal.
This problem sounds similar to a few others, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...
Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens.
I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.
I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.
I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.
Any clues?
(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)
THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS
Download and install new ADT v22.6.1 from here (zip) or use SDK manager to update
Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.
However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.
May be we have to wait for any conformation from Android community
Worked for me, sort of.. .
(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)
Update 1
Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.
Update 2
More bad news is AVD creation not working from command line tool too.
Update 3
Assuming some parameter passed during launching AVD manager from Eclipse causes these problems
Update 4
Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.
Update 5
At https://code.google.com/p/android/issues/detail?id=66661 android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version version 22.3.0
To uninstall current ADT go to
Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall
I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.
Hope this will solve this problem temporarily. And wait for new release of ADT here.
Update 6
New ADT, version 22.6.1 is out now which will solve these problems
To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:
Run the following on the command line
<android-sdk-location>/tools/android avd (on Linux in this case)
This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.
1 minute solution
I used a quick workaround where I cloned a device that already existed. The Clone button worked and I was able to successfully edit the clone.
Steps:
Select a Device by Google
Click the "Clone..." button
A window will pop up, click "Clone device"
Select the newly cloned Device, it should say "... by User"
Click the "Edit" button on the side
There you have it, you now have your own custom virtual device
Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.
Historical Workaround As #Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:
First: Uninstall ADT plugin and all related plugins for android:
help->about
Installation details
Select android plugins and press uninstall button
Restart
Second: Download ADT 22.3.0 Archive from https://dl.google.com/android/ADT-22.3.0.zip
and install it
add repository from archive on local disk
Select android plugins
INFO:
I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.
I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...
I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .
So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6
I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it.
I also heard that it may help things if you install the Android SDK to a path without spaces.
Hope this helps someone keep some hair.
Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit!
I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!
This time it only took a total of twenty minutes to fix.
Per the release notes, this problem has been resolved in revision 22.6.1, which is now available for download.
Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting Window > Android SDK Manager and follow the prompts to install the update.
After that update finishes, select Help > Check for Updates and follow the prompts to update the appropriate Eclipse components.
After completing these updates, I tested the AVD functionality and it appears to be working properly.
i just copied the avds from a different system as descriped here:
Android - How to copy the emulator to a friend for testing
I faced the similar issue. I am using 23.0.2 version of android SDK.
"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:
C:\Program Files\Android\android-sdk\
and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.
Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!
I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)
For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed
Give some value for your sd card. May be something like 100 or 200
So I'm trying to create an AVD Simulator, and I keep getting the "No system images installed for this target" error when trying to create a 4.2.2 system even though the image is installed (See picture of SDK Manager).
My system is x64, does that make a difference?
After SDK Update I had the same problems with API Level 19 and
in my case restarting eclipse didn't solve it.
For some reason, in the sdk/system-images/android-19 directory, sub-folders with system images (armeabi-v7a and x86) were placed within "default" directory.
I just moved them into android-19 directory (if eclipse is running at the same time, you will have to restart it).
You just need to restart the tools. I have seen this bug before. The appropriate installed images will show up after the restart.
You can also try to refresh within the 'Packages' menu, but the easiest thing, is to restart the tools.
Goto sdk\system-images and open the folder of the current API you are using (eg.android-19 folder in your case).
Now you'll find a folder named 'default', open it and you'll see the folder named 'armeabi-v7a' or which ever system image you've installed.
Now move the folder 'armeabi-v7a' to the directory sdk\system-images...i.e simply out of the 'default' folder.
That's it.
I had the same problem and this method worked for me. :D
I restart eclipse.it worked out for me,issue is resolved.
I just had this same issue. My problem was solved by killing eclipse (Command + Q) because I'm a Mac user. So, if you're under other operative system be sure to kill the Eclipse's process and relaunch it.
Lots of potentially useful answers here, but none of them were worked for me.
On my Mac, I have both Android Studio and Visual Studio installed. One would hope that they would automatically look for an Android SDK in the same place, but no, not necessarily.
In Android Studio, go to Tools -> Android -> SDK Manager. In the window that pops up, make a note of the Android SDK Location. It should be something like
/Users/[user]/Library/Android/sdk
Next, in Visual Studio, go to Tools -> SDK Manager. In the window that pops up, the path that should be selected on the left is Projects -> SDK Location -> Android. On the right, click the Locations tab. For me, the Android SDK Location path was set to something like
/Users/[user]/Library/Developer/Xamarin/android-sdk-macosx
I changed this to the path that Android Studio was using, and that fixed the problem for me.
Very simple. I restarted Eclipse, reloaded my project and when creating a new emulator, the problem is gone
Found this thread when I did a search on Google for the same error.
So I just wanted to add that if anyone comes across this thread but you are using Android Studio. You only have to restart the Android Studio. I did and now I can see what I installed.
Make sure you have rights to all the files in the android-sdk-linux directory using:
sudo chown $USER -R ./android-sdk-linux