Android Studio: 模拟器已经在运行

Run this command and try again:

adb kill-server

If "adb kill-server" dont work try killing the adb from System monitor app of ubuntu:

System monitor->processes

All processes will be listed here end adb from here, must be in the top of the list.

Thanks everyone.

I removed files of given location. but when I refresh the AVD manager, Existing emulator are all gone.

I recreated new emulator. Now it works fine.

Just follow the tips from Android Studio ... Delete the file corresponding to your avd and recreate it.

This happens when the virtual device is shut down in an unexpected state.

You don't have to completely delete the emulator when this happens. The files to delete should have a ".lock" extension:

You don't need to touch the configuration files.

You can easily find the files location by clicking on the arrow under the Actions tab (in the ADB manager), and selecting "Show on Disk".

In my case the emulator looked fine but it was hung.

Just killing the emulator and trying again did the trick.

Follow the instructions on the error and go to your C:\Users\directory\.android\avd/Nexus_5_API_24.avd/*.lock and delete all files with the .lock extension and it should work.

1. Open Settings
2. Goto developer options
3. Click revoke USB debugging authorizations

This worked for me:

Go to AVD Manager and click on the down-arrow on the right and click Stop. This stops the emulator and you can re-run it.

There are so many answer but i just extending to give answer of this question. What happen is when i follow Android Studio instruction and try to delete that folder Or file but i am not able to delete it, So what am i do is that i open the AVD Manager and click on down arrow which is on right side as you can see in below screenshot and click on stop after click on start and its working fine. There is no need to restart or recreate the AVD.

When you go to the specified location and try to delete those files sometimes you might get an error stating that the file or folder is already open or is used by another application

So the simple Solution is just to go to

Tools > Android > AVD Manager and Stop the AVD that you are trying to run

Then When you try to run the AVD again you might have the problem resolved

In your Android Studio go to Tools->Android->AVD Manager. It will list your virtual devices. Click the Action column corresponding to your virtual device. It will list many actions. Click on Stop. This will shutdown your android studio. Now start android studio. Your virtual device should work fine.

C:\Users\admin.android\avd\Nexus_5X_API_26.avd follow path and delete hardware-qemu.ini.lock this folder. make sure your problem can be solve :)

Or you can type a command in terminal as

1.killall Finder and then type,

2.defaults write com.apple.Finder AppleShowAllFiles true it shows hidden .android folder

Open .android folder and delete .android/avd/Nexus_5X_API_26.avd/*.lock file and now you run emulator it works fine.

For me, "delete .lock file" & "stop emulator then start" & "delete emulator then recreate" does't work.

but,delete "C/User/yourName/.android" folder can fix this problem

For MAC Users

Open Terminal, cd to the given path. List all the files using the command ls. You will see two files with .lock extensions or maybe more. Just delete those files.

C:\Users\.android\avd follow the path and open Emulator directory and delete all .lock extension folders.

I restarted the computer and it worked for me!

I closed the emulator, clicked the AVD Manager Icon on the menubar then under the emulators actions tab downward arrow I selected "Cold Boot Now" then ran the program normally by pressing SHIFT + F10

If you have followed all answers, and no success yet. And not able to find that specific lock.

Search all .lock extension files in /avd dir, and remove them. After then start again emultaor. It works for me without restart system.

Find and open the pid folder within your *.lock folder. Inside should be a number.

Kill pid:

Windows

taskkill /F /PID pid_number

You can also solve this problem by doing "Invalidate chaches/ restart".

I'm don't know if some one is still having this problem, but, in my case, it's was an issue related to VAGRANT.... more precisely whit Virtual Box. I just stop the vBox proccess (i'm ussing ubuntu), remove the .lock files related to the emulator inself and that's it... the emulator should by ready to go.

This working for me :

Invalidate chaches/ restart

Go to

1 - File

2 - Select Invalidate Cahes / Restart

Go to the down arrow and click on the "Show on Disk" link like attached image. You will get the list of all files, remove the file "hardware-qemu.ini.lock" and start again.

It works for me hope it will work for you too.

EASIEST SOLUTION:

1. Go to AVD Manager
2. Click on down arrow in the Actions column on the right
3. Click on Wipe data

You're done :)

For Windows: Step By Step Instructions below:

1. Locate the avd folder: *C:\Users\username\.android\avd*
2. Try delete *lock and figure out the process holding the lock
3. Ctrl+Shift+Esc to get to TaskManager
4. Select Pid and Process name by right clicking on the header
5. Get the PID number of the offending application
6. on cmd type: taskkill /F /PID /PIDnumber
7. Now go back to the avd folder & delete the *lock files. It will work.
8. Restart Emulator

I tried solutions above but nothing worked so I deleted the emulator, restart pc and create a new one and it was resolved

Go to (Windows)

C:\Users\directory.android\avd/Nexus_5X_API_26.avd

Or (Ubuntu)

~/.android/avd/name.avd/Nexus_5X_API_26.avd

and delete all files of with .lock extensions.

Check Updates... Emulator had an update. After I updated and restarted.. worked fine.

I Also have the same problem but in ubuntu 20.04 and I had to navigate to /home/your_username/.android/avd/Pixel_2_API_28.avd/*.lock and then delete all file with .lock

Note: you first need to enable show hidden files and I may have used different device (Pixel_2_API_28) from yours but it is applied to any device

When I was trying to delete multiinstance.lock it says

So, I opened Window's task manager and selected qemu-system-x86_64.exe and press End task

Use this for killing all emulator processes.

adb emu kill

For Linux this should clear them for all devices in one go if your issue is just .lock files

find $HOME/.android -type f -name '*.lock' -exec rm {} \;

Example with it just echoing out.

❯ find $HOME/.android -type f -name '*.lock' -exec echo rm {} \;
rm /home/mike/.android/build-cache.lock
rm /home/mike/.android/debug.keystore.lock
rm /home/mike/.android/avd/Pixel_6_Pro_API_33.avd/multiinstance.lock
rm /home/mike/.android/avd/Pixel_6_Pro_API_33.avd/hardware-qemu.ini.lock
rm /home/mike/.android/avd/Pixel_6_Pro_API_30.avd/multiinstance.lock
rm /home/mike/.android/avd/Pixel_6_Pro_API_30.avd/hardware-qemu.ini.lock
rm /home/mike/.android/build-cache/3.5.2.lock
~ at 10:16:27
❯

If you did not stop them all first can run this first beforehand.

adb devices | grep emulator | cut -f1 | while read line; do adb -s $line emu kill; done