Develop Reference

Emulator: emulator: ERROR: Running multiple emulators with the same AVD is an experimental feature

I removed the emulator and reinstalled it and got the same error.
Emulator: emulator: ERROR: Running multiple emulators with the same AVD is an experimental feature.
Emulator: Process finished with exit code 1.

Removing the .lock files did the trick for me. Find the avd and remove the lock files. In a Mac .android/avd/'NAMEOFAVD.avd directory . The files I removed were hardware-qemu.ini.lock and multiinstance.lock.

It can be solved using this method. It worked for me.
Follow the steps:
Open Android Studio.
Go to AVD Manager.
In the Actions column, for the respective avd, click on the down arrow and click on Stop.
This will stop the Emulator and then you can restart it from the command line.

This means that your AVD manager thinks that your emulator is running. It thinks that because it sees lockfiles in your avd directory. If your emulator is not running they you can (should) safely delete the lockfiles here :
$ rm $HOME/.android/avd/<name-of-your-avd>.avd/*.lock

Same emulator error
ERROR: Running multiple emulators with the same AVD is an experimental feature.
fixed with removed lock for AOSP device which located
./out/target/product/generic_car_x86_64/multiinstance.lock
./out/target/product/generic_car_x86_64/hardware-qemu.ini.lock
Also check permission for /dev/kvm

On Linux, you should try this:
sudo rm /home/${USER}/.android/avd/*/*.lock
On Mac:
rm $HOME/.android/avd/*.avd/*.lock
Hope it will help.

Make sure you don't have any physical device connected to your computer, in addition to removing all emulators' .lock

Removing the cache could help
sudo rm /home/${USER}/.android/avd/*/*.cache

The very simple solution which is working all the time is to stop the emulator before launching the new project. If this error comes back you make a duplication of the AVD and delete the old one and run the new one. It works all the time.

just open your task manger, look for adb.exe, end task of all abd.exe extensions and restart your emulator.

my problem solved by closing the emulator and letting the test run the emulator automatically

I faced the same issue, I tried all the solutions above not fixed,
then I used the wipe data option from the device manager then it works fine.

Failed to start Emulator console for 5554

I'm trying execute my application, but it occurs the following problem:
Failed to start Emulator console for 5554
I've already done:
Clean and Build Project and restart

Check:
if you have downloaded all of the emulator files from the SDK Manager for the version you're trying to use.
if you have enough RAM left to use for the emulator (remember that you define it in the device config)
if there's not another emulator already running.
Another way to know what's the problem is to check the LogCat, it provides very useful information about errors and all the stuff running, if you can't figure the problem reading it, try to ask a question with the error message FROM the LogCat, not only the one from the windows in your screen.

I had the same problem.
Finally I launched the emulator in command line. use "sudo ./emulator #(your device name)", and it can work properly with port 5554.

android: Installation Error:Unknown Failure-while running an apk file in

Yesterday I haven't got any error while using emulator but today I got this error check the image below. I have run as well as debugged many time but I am not getting the same error every time.
Error is popping up after installing the apk file. Please give the correct answer such that i can fix the emulator correctly and work on that
Now when I compile I got new error check the below image while shows
What I have to do ?

I was also facing this issue, I try this and works great.
adb.exe kill-server
adb.exe start-server

I don't exactly remember, but try to reset preferences by option in Windows tab.
Or create a new emulator and try to run your program again. If above things won't work then enable debugging on your android device and connect your device and run it to see if error persist.
Thanks

If running in eclipse, Please check the emulator settings..
This happens when AVD is already configured and a new andriod project is created.
So for this.. go to Run>> Run Congurations >> Target.. Select the AVD which is already configured and an option for choosing same AVD for future projects also.
This will start an emulator and thats it.. your application is up !!!

If You Running In Eclipse, Check Your Settings.
Run Configurations - Common - Select File In Standard Input And Output - Click
Workspace And Choose Your Project.
And Just Click Run.

Check if the package name contains an uppercase letter,If uppercase letters are included, change them to lowercase.it worked for me

Even I faced this issue. I used below steps for resolving the issue:
1] adb uninstall your_app_package_name
2] adb kill-server
3] adb start-server
restart the emulator/device after executing above steps.
Now try to run the application. That must work for you.

Reboot your computer. This has always worked for me.

could not access the package manager. is the system running while installing android application

While installing the android application in the emulator I am getting the following error.
Please help me to resolve this error.
Error message:
emulator.exe -avd avd_name
adb wait-for-device
adb install path-to.apk
could not access the package manager. is the system running while installing android application....

You need to wait for the emulator to full start - takes a few minutes. Once it is fully started (UI on the emulator will change), it should work.
You will need to restart the app after the emulator is running and choose the running emulator when prompted.

As other have said, this error occurs because the emulator is still in the process of launching. An attempt to access the package manager, for the device, at this time causes an error.
It's just a simple timing issue. Here are the steps to avoid this error:
Wait until the emulator 'lock screen' is showing.
Run the 'app' again (^R in most IDE's).
Choose the running device (Should be the same emulator).
App should install without error.

In my case it was just that the emulator took 9 minutes to start. Wait until you see the lock icon on the emulator LCD. Or use actual tablet or phone.

Facing Same issues following Link helped solving the problem. The above solutions were not helpful for me.
deployment-failed-could-not-access-the-package-manager-is-the-system-running
By restarting server using CMD application was back to work. Open cmd (Run as administrator), open this
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
(this path must specify your android-sdk installation folder )
Now, first write,
adb kill-server and then adb start-server.

Kill the process/server and restart it.! It worked.

You can avoid the error by setting default device before launching application. Launch the AVD before starting the app.

Once you see this error, wait for emulator to show lock screen. And then relaunch the app in your IDE and check the emulator again. It works for me always.
In Android studio, you can relaunch by clicking the green play button or ctrl + r.

If this error is gotten when using a rooted device's su prompt and not from emulator, disable SELinux first
setenforce 0
You may need to switch to shell user first for some pm operations
su shell
then re-run your pm command.
Same applies to am commands unavailable from su prompt.

The solution for me was to restart the IDE. I suspect that a slow emulator was hiding from view, blocking installation on my device.

Check your project build is in Debug mode not Release, I had some problem for debugging always I forget to change Release mode to Debug (Xamarin Users)

Emulator problem in Android

When I launch the emulator I face many problems (Errors):-
HttpConnectionApp]emulator-5554 disconnected!
Cancelling 'net.paxcel.http.HttpConnectionApp activity launch'!
Emulator]emulator: ERROR: the user data image is used by another emulator.
aborting
Each time I have to re-run it but all in vain.
How can I improve this so that I can re-run the application on same AVD?

I had the same issue after my computer locked up and I had to power cycle it.
Wiping the user data didn't fix my problem, I had to delete the following folders manually
C:\Users\%UserName%\.android\avd\AVD2.1.avd\cache.img.lock
C:\Users\%UserName%\.android\avd\AVD2.1.avd\userdata-qemu.img.lock

A quick-fix that obviously works is to restart the adb server each time this error occurs:
adb kill-server && adb start-server
Then, you simply run the application again (without restarting AVD) and that's it.

Run configurations → Target → Wipe user data → Run.
It fixed the problem in my case.

Here is the answer that helped me:
link text
Another solution for me is start the avd manager and start once emulator from there. After that everything turns to normal.

AFAIK, this happens when an emulator is started, but the Android Debug Bridge couldn't establish connection to it.
If you have just started the emulator with your application, watch if you get Waiting for HOME to launch... or something similar in your Console.
If you don't get that message, but the emulator has been started, chances are, you'll get into the ERROR: the user data image is used by another emulator situation again.

emulator: ERROR: the user data image is used by another emulator. aborting
Tried restarting the computer as I had done a lot of messing around earlier but no joy same error.
Went to shut down ADB so as I'm on XP I run > cmd then paste in > cd C:\Program Files\Android\android-sdk\platform-tools (the location of the location for the ADB on XP)
Tried
adb kill-server && adb start-server
Then moved the directories cache.img.lock and userdata-qemu.img.lock in the C:\Documents and Settings\.android\avd\ to a New folder (instead of deleting)
This worked fine.

Delete the existing emulators and then make a new one.
This worked for me, when I had this problem and couldn't find the folders to delete.

Under Run Configurations --> Target --> Add Command Line Options add this
adb kill-server && adb start-server
every time running your App will kill-restart the adb server.

It's probably a bad install of ADT. Try uninstalling the plugin, restarting Eclipse, then installing it again fresh.
That of you aren't letting the emulator boot all the way up and are closing it before ADT/ADB can install/run your app.

Please set wipe_data for emulator
Use same instance of application (after modification if any) to avoid error you are getting.

This can also happen if you're using a network share as your home folder, because some network file sharing systems may lock the image files.

Delete the directories cache.img.lock and userdata-qemu.img.lock (in my case these files are in /mylocalusername/.android/avd/avd7.avd

Thanks for this! Just to add for some people who develop in Windows XP.
The path to the avd directory can be C:\Documents and Settings\.android\avd
Thanks again for the answer! :)