CODEWITHSUNDEEP
androidandroid-emulator
Serkan Aydın
Serkan Aydın

Reputation: 873

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.

Upvotes: 84

Views: 63547

Answers (14)

Mister.Perfect
Mister.Perfect

Reputation: 488

On Linux, you should try this:

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

On Mac:

rm $HOME/.android/avd/*.avd/*.lock

Don't forget to shutdown the emulator before running above command if it's running. Hope it will help.

Upvotes: 24

Elmar
Elmar

Reputation: 4445

It usually happens after Force Qiut-ing Emulator when you turn off Macbook.. This command from the terminal can remove the .lock file and make emulators work again:

rm ~/.android/avd/*.avd/*.lock

Upvotes: 1

John Morgan
John Morgan

Reputation: 11

I have tried removing the device from the device manager and setting up the same device again. with deleting the old device file manually

C:\Users\userName.android\avd

and it worked fine with me

Upvotes: 0

Seth
Seth

Reputation: 97

I solved the problem doing this

Run cmd as administrator then

RD \S C:\Users\userName\AppData\Local\Temp

Upvotes: 0

Ameen Al-Othman
Ameen Al-Othman

Reputation: 1

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.

Upvotes: -1

Mahdieh Shavandi
Mahdieh Shavandi

Reputation: 8645

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

Upvotes: 0

Dmitry Podyachev
Dmitry Podyachev

Reputation: 153

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

Upvotes: 4

Omkar Kulkarni
Omkar Kulkarni

Reputation: 1215

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.

Upvotes: 18

dianakarenms
dianakarenms

Reputation: 2695

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

Upvotes: 3

Jand Edd
Jand Edd

Reputation: 1

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

Upvotes: 0

Mouradif
Mouradif

Reputation: 2714

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

Upvotes: 22

NYIRIMBORO GITUBA
NYIRIMBORO GITUBA

Reputation: 9

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.

Upvotes: 0

Mukundhan
Mukundhan

Reputation: 3477

Removing the cache could help

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

Upvotes: 0

flutter
flutter

Reputation: 6786

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.

Upvotes: 176

Related Questions