CODEWITHSUNDEEP
androidandroid-studioandroid-emulator
ichen2
ichen2

Reputation: 683

Android Studio stuck 'Connecting to emulator'

I recently updated Android studio, and as usual, it broke. Whenever I try to launch an emulator, Android Studio gets stuck in the 'Connecting to emulator' screen forever.

Things I've tried:

I'm on an M1 Macbook and running Android Studio Bumblebee 2021.1.1 Patch 3

edit: I've also tried switching to Cold Boot

Upvotes: 34

Views: 36752

Answers (16)

Khaleesi
Khaleesi

Reputation: 469

I dealt wis this issue for many hours, i tried everything mentioned here.

  1. I reinstall the SDK in the IDE
  2. I recreate the emulator
  3. I restart AS
  4. I restart my laptop
  5. I delete another local installation of SDK done with brew

After reading this documentation and installing the APK from command line I played a bit with the configurations on the port used by adb.

Finally this settings made it work (with a invalidate caches restart) adb settings using automatically start and manage server

I am on Mac btw

Upvotes: 0

Vignesh
Vignesh

Reputation: 160

Go to File -> Project structure -> Project -> select SDK version. Then you can see emulator name in android studio

enter image description here

Upvotes: -1

Bruce Bruce
Bruce Bruce

Reputation: 99

my fix was to download some emulator components update. just check for updates in Android Studios under Help->check for updates. hope this helps someone save a day of headache!

Upvotes: 4

Ye Htun Z
Ye Htun Z

Reputation: 2107

As for me shutdown or restart the computer, it is work. (masos)

Upvotes: 0

Bayu Wijaya Permana Putra
Bayu Wijaya Permana Putra

Reputation: 316

I also have the same issue. I solved it by removing data:

  1. To stop a running emulator, click Menu and select Stop.
  2. To clear the data for an emulator, click Menu and select Wipe Data. enter image description here

I hope this help you too. Happy coding!

Upvotes: 1

user3526918
user3526918

Reputation: 681

Android Studio Hedgehog: in the Device Manager select the device - right menu: Wipe Data then Cold Boot.

Upvotes: 2

Mhd Wael Jazmati
Mhd Wael Jazmati

Reputation: 667

wiping user data fixed the issue on my side,

Upvotes: 1

Satria Yusuf
Satria Yusuf

Reputation: 1

for my case I made a new virtual device to crank or stop the "AVD still running" error. The "Pixel 2 API" is the new virtual device I made because I can't delete, cold boot, and wipe data the "Test HP General" virtual device from "AVD still running" error.

Then, I checked out what should I do with that error and found out you have to uninstall the IDE. But, I don't really want to uninstall the AVD because from other case when I reinstall the AVD I got many problem that makes me have to reset my PC. Because my AMD emulator got bricked.

In short, from making another Virtual Device and run it. The AVD would restart and make the error and booting problem go away.

If this doesn't help, then you should try to do it manually by going to the AVD file section and try to stop it from running in the background.

Upvotes: 0

Yutaka KATO
Yutaka KATO

Reputation: 11

In my case, I was able to connect by using the "1:1" view when displayed in the tool window. Once it is displayed, you can resize window size.

Steps:

  1. [Connecting to Emulator] prompt shown
  2. Click [1:1] button

The environment is as follows

  • MacBook Air (M1, 2020)
  • Android Studio Dolphin | 2021.3.1 Patch 1
  • Android Emulator 31.3.14
  • Android Tiramisu arm64-v8a

Upvotes: 0

Tal Haham
Tal Haham

Reputation: 1628

If you are running a flutter project, run from the terminal flutter doctor. In my case, it reported that the SDK was not properly set up for flutter.

Upvotes: 0

Amol Chaudhari
Amol Chaudhari

Reputation: 841

I fixed my issue using the following steps:

Go to Android Studio -> Preferences -> Tools -> Emulator -> Uncheck “Launch in a tool window”.

And retry to launch emulator again OR run app on using the same emulator.

Upvotes: 67

Anrimian
Anrimian

Reputation: 4477

For me helped to enable checkbox "Enable device frame" in avd config.

Upvotes: 3

ichen2
ichen2

Reputation: 683

I was able to fix this by reinstalling Android Studio and the emulator.

Upvotes: -3

David Kariuki
David Kariuki

Reputation: 1756

Solution1

  1. Stop Emulator from AVD Manager
  2. From Android Studio, select “Tools” > “Android” > AVD Manager.
  3. Right-click the emulator you are using, then choose “Stop“.
  4. Try running the emulator again.

Solution 2 – Exit Docker (MacOS)

Exit out of the Docker application on your Mac computer, then attempt to launch the emulator again.

Solution 3 – Wipe Image

  1. From Android Studio, select “Tools” > “Android” > AVD Manager.
  2. Right-click the emulator you are using, then choose “Wipe Data“.
  3. Try running the emulator again.

Solution 4 – Uninstall and Reinstall AVD

  1. From Android Studio, select “Tools” > “SDK Manager” > “SDK Tools“.
  2. Uncheck “Android Emulator“.
  3. Select “Apply” to have the emulator uninstalled.
  4. Once the emulator has been removed, check the “Android Emulator” box again, then select “Apply” to reinstall it.

Solution 5 - Coldboot

  1. Go to Device Manager.
  2. Right-click your virtual device.
  3. Select Cold Boot Now.

Extra

  1. Make use of Android Studio’s ‘Instant Run’
  2. Install HAXM and Switch to x86. …
  3. Virtual machine acceleration. …
  4. Disable the emulator’s boot animation.
  5. Free your ram by closing unnecessary apps.

Upvotes: 17

user18910680
user18910680

Reputation: 79

This help me

Go to Device Manager and right-click your virtual device and select Cold Boot Now

Or you can make new virtual device

Upvotes: 7

rafiulah
rafiulah

Reputation: 159

Me Problem Solve By creating new Virtual device by changing from Quick boot to Cold boot.
"In quick boot emulator start from stat that saved when the device last exited"
"while Cold boot emulator start as from a power up"
how to change from QUICK BOOT to COLD BOOT

Upvotes: 0

Related Questions