Avd is already running if that is not the case delete the files at

Android Studio: эмулятор уже запущен

Я пытаюсь запустить эмулятор на своей студии Android 8.14. Когда я нажимаю «запустить», он говорит, что он уже запущен. Любая помощь будет оценена по достоинству.

If that is not the case, delete the files at /home/sayem/.android/avd/api21.avd/*.lock and try again

В этом случае нет необходимости полностью удалять эмулятор. Удаляемые файлы должны иметь расширение «.lock»:

Файлы конфигурации трогать не нужно.

Вы можете легко найти расположение файлов, щелкнув стрелку на вкладке «Действия» (в диспетчере ADB) и выбрав «Показать на диске».

Это сработало для меня:

Перейдите в AVD Manager, щелкните стрелку вниз справа и щелкните Остановить. Это остановит эмулятор, и вы сможете его повторно запустить.

Есть так много ответов, но я просто расширяюсь, чтобы дать ответ на этот вопрос. Что происходит, когда я следую инструкциям Android Studio и пытаюсь удалить эту папку или файл, но я не могу его удалить, поэтому я открываю диспетчер AVD и нажимаю стрелку вниз, которая находится справа от вас. можно увидеть на снимке экрана ниже и нажать кнопку « Стоп» после нажатия кнопки «Пуск», и все работает нормально. Нет необходимости перезапускать или воссоздавать AVD.

Перейдите к стрелке вниз и щелкните ссылку «Показать на диске», как прикрепленное изображение. Вы получите список всех файлов, удалите файл «hardware-qemu.ini.lock» и начните заново.

Это работает для меня, надеюсь, это сработает и для вас.

Я перезагрузил компьютер, и у меня все заработало!

Это работает для меня:

Недействительные чачи / перезапуск

Android Studio: «The emulator process for AVD Pixel_2_API_30 has terminated.» on MacBook Pro M1 (Apple Silicon)

I have a problem to start an Android Emulator on my MacBook Pro M1 (Apple Silicon). When I try to start an emulator (API 30, CPU/ABI arm64), I get this error: «The emulator process for AVD Pixel_2_API_30 has terminiated.»

I’m using 2020.3.1 Beta 5 of Android Studio.

Does anyone know how to solve this problem?

/.android/avd was full, so had to move+symlink it to a another partition with more space available.

11 Answers 11

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

It would seem due to the fact you are using a beta version of android studio the message «The emulator process for AVD Pixel_2_API_30 was killed.» has been changed to «The emulator process for AVD Pixel_2_API_30 has terminated.» but fundamentally they should still have the same solutions the most common solution being:

«All of the answers are too confusing to follow. Replace SDK or upgrade OS. The quickest way I found is to:

Tools > SDK Manager > SDK Tools

Now, by default the Emulator version shown will be 30.6.5. Select the checkbox and click apply. This version of emulator will be installed.

That is it, just 2 minutes of you time.

Update: 1 Jul 2021 Issue solved with latest Emulator version 30.7.5″

Credits to: Karan Sharma in the post found here

If this does not fix the error then there are a multitude of different solutions that can be found by googling «Android studio MacBook emulator process for AVD was killed.» or simply downgrading/upgrading your emulator works too, because it is a common issue with the v30.6.x emulator versions.

Can’t Delete AVD from AVD Manager in Android Studio

I am running Android Studio on OS X Yosemite. I am trying to simply delete an AVD from Android Studio AVD Manager. Every time I attempt to delete it I get the message «The selected AVD is currently running in the Emulator. Please exit the emulator instance and try deleting again.» The problem is that the emulator is NOT running. I even closed down all the studio and rebooted the computer. It still says the same thing. Anybody seen this before? I would really like to remove the AVD.

Thanks in Advance!

19 Answers 19

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

To delete any android emulators (and thereby stop them, if they have been running in the background of the system) close Android Studio and go to the following folder:

Delete all the files and folders inside it and restart the IDE.

Now when you open the Android Studio Device Manager it will ask you to create a new AVD.

On Android studio go to: Tool > Android > AVD Manager, on the action column you can delete your avd

For Linux users:

/.android/avd from the command line). Delete whichever avd you want to. Then restart Android Studio.

In Linux/*nix and OSX:

I had an issue were I couldn’t delete the files in the folder located at:

You cannot delete this file even if you close AndroidStudio and some other bug sending programs that didn’t even close after you close AndroidStudio

There is a file called ‘pid’ inside the hardware-qemu.ini.lock folder that you can open up with notepad and it gives you the number of the process number. Go into task manager>Details tab>order by PID by clicking on the columb>search for the PID>end process; The process name should be something like quemu. exe I think.

After that, your AndroidStudio will no longer be locked. Maybe you could of solved it with a restart too.

Android emulator won’t shut down

The emulator starts up fine. But when you long-press the power button (or F7 ) and choose «Power off», it displays a «Shutting down» message which remains on-screen forever and the emulator won’t actually shut down.

I can close the emulator window or kill its process. But I’m wondering if this is the correct way to shut down an Android emulator.

13 Answers 13

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

If the device is stopped in a bad state, this may persist when relaunching the emulator. To get around this, simply select ‘Cold Boot Now’ from the virtual device’s drop down menu in the manager.

According to the documentation I found at google, simply closing the emulator window is the correct way to shut the emulator down.

To stop an emulator instance, just close the emulator’s window.

Okay so do this:

2.Go to AVD Manager

3.Select Your Emulator and Cold Boot Now

Open Virtual Device Manager, locate the virtual device you are concerning, check «Cold Boot Now» on the drop down menu of actions column of it.

This is for Mac Users.

It will then save its present state and then it will shut down.

I’m running Android Studio Chipmunk 2021.2.1 and most of the solutions in this thread no longer work.

adb solution

What does work is using adb to shutdown the emulated device:

If you have multiple devices attached you’ll need to specify which one:

(You can find the list of device serial numbers by running adb devices )

Alternate pkill solution

Shutting down via adb is the clean way to shutdown the device. If for some reason that doesn’t work, you can kill the emulator by running:

This will kill every running instance of QEMU on your computer (QEMU is what the Android Emulator uses under-the-hood). pkill(1) is installed on most computers, but you may have to install it if it’s not built-in.

No idea

I really don’t know.

Here’s what I do know.

Getting a list of running Android instances

You can get a list of running Android instances by entering this command:

What else you can try

Now you can visit «How I shutdown Android phone with adb command?» and try all the proposed solutions.

I don’t know whether any of them work. Please leave a comment below and inform us.

More thoughts

You can connect to a running emulator by entering this command:

Now you can enter Unix-like shell commands which will do things. These are similar to the usual Linux shell commands.

Maybe the following will work? But, does it truly shut down, or does it reboot?

In fact, does any «shut down» command work, or do they all just cause the running Android instance to reboot?

Please file a bug report

Someone should file a bug report, in the Android issue tracker, against the current version of the Android emulator — plus one of Google’s newest available emulator ROMs. Once you do so, please leave a comment below and provide us with a link to the bug report.

Android emulator won’t shut down

The emulator starts up fine. But when you long-press the power button (or F7 ) and choose «Power off», it displays a «Shutting down» message which remains on-screen forever and the emulator won’t actually shut down.

I can close the emulator window or kill its process. But I’m wondering if this is the correct way to shut down an Android emulator.

13 Answers 13

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

If the device is stopped in a bad state, this may persist when relaunching the emulator. To get around this, simply select ‘Cold Boot Now’ from the virtual device’s drop down menu in the manager.

According to the documentation I found at google, simply closing the emulator window is the correct way to shut the emulator down.

To stop an emulator instance, just close the emulator’s window.

Okay so do this:

2.Go to AVD Manager

3.Select Your Emulator and Cold Boot Now

Open Virtual Device Manager, locate the virtual device you are concerning, check «Cold Boot Now» on the drop down menu of actions column of it.

This is for Mac Users.

It will then save its present state and then it will shut down.

I’m running Android Studio Chipmunk 2021.2.1 and most of the solutions in this thread no longer work.

adb solution

What does work is using adb to shutdown the emulated device:

If you have multiple devices attached you’ll need to specify which one:

(You can find the list of device serial numbers by running adb devices )

Alternate pkill solution

Shutting down via adb is the clean way to shutdown the device. If for some reason that doesn’t work, you can kill the emulator by running:

This will kill every running instance of QEMU on your computer (QEMU is what the Android Emulator uses under-the-hood). pkill(1) is installed on most computers, but you may have to install it if it’s not built-in.

No idea

I really don’t know.

Here’s what I do know.

Getting a list of running Android instances

You can get a list of running Android instances by entering this command:

What else you can try

Now you can visit «How I shutdown Android phone with adb command?» and try all the proposed solutions.

I don’t know whether any of them work. Please leave a comment below and inform us.

More thoughts

You can connect to a running emulator by entering this command:

Now you can enter Unix-like shell commands which will do things. These are similar to the usual Linux shell commands.

Maybe the following will work? But, does it truly shut down, or does it reboot?

In fact, does any «shut down» command work, or do they all just cause the running Android instance to reboot?

Please file a bug report

Someone should file a bug report, in the Android issue tracker, against the current version of the Android emulator — plus one of Google’s newest available emulator ROMs. Once you do so, please leave a comment below and provide us with a link to the bug report.