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

AndroidAndroid Emulator

Android Problem Overview


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.

Android Solutions


Solution 1 - Android

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.

Solution 2 - Android

It can be solved using this method. It worked for me. Follow the steps:

  1. Open Android Studio.
  2. Go to AVD Manager.
  3. 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.

Solution 3 - Android

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

Solution 4 - Android

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

Solution 5 - Android

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

Solution 6 - Android

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.

Solution 7 - Android

Removing the cache could help

sudo rm /home/${USER}/.android/avd/*/*.cache

Solution 8 - Android

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

Solution 9 - Android

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

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSerkan AydınView Question on Stackoverflow
Solution 1 - AndroidflutterView Answer on Stackoverflow
Solution 2 - AndroidOmkar KulkarniView Answer on Stackoverflow
Solution 3 - AndroidKi JéyView Answer on Stackoverflow
Solution 4 - AndroiddianakarenmsView Answer on Stackoverflow
Solution 5 - AndroidDmitry PodyachevView Answer on Stackoverflow
Solution 6 - AndroidNYIRIMBORO GITUBAView Answer on Stackoverflow
Solution 7 - AndroidMukundhanView Answer on Stackoverflow
Solution 8 - AndroidJand EddView Answer on Stackoverflow
Solution 9 - AndroidMahdieh ShavandiView Answer on Stackoverflow