CODEWITHSUNDEEP
androidandroid-studioandroid-emulator
Captain Jacky
Captain Jacky

Reputation: 1059

Emulator doesn't start (Connecting to the emulator)

I tried to launch an emulator long time ago, but neither I could launch it nor I found any information about how to fix this problem. When I start an emulator, I get this window below:

enter image description here

Emulator's details:

Name: Pixel_2_API_30
CPU/ABI: Google Play Intel Atom (x86)
Path: C:\Users\Me\.android\avd\Pixel_2_API_30.avd
Target: google_apis_playstore [Google Play] (API level 30)
Skin: pixel_2
SD Card: 512M
fastboot.chosenSnapshotFile: 
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: pixel_2
hw.lcd.width: 1080
hw.initialOrientation: Portrait
image.androidVersion.api: 30
tag.id: google_apis_playstore
hw.mainKeys: no
hw.camera.front: emulated
avd.ini.displayname: Pixel 2 API 30
hw.gpu.mode: auto
hw.ramSize: 1536
PlayStore.enabled: true
fastboot.forceColdBoot: no
hw.cpu.ncore: 2
hw.keyboard: yes
hw.sensors.proximity: yes
hw.dPad: no
hw.lcd.height: 1920
vm.heapSize: 256
skin.dynamic: yes
hw.device.manufacturer: Google
hw.gps: yes
hw.audioInput: yes
image.sysdir.1: system-images\android-30\google_apis_playstore\x86\
showDeviceFrame: yes
hw.camera.back: virtualscene
AvdId: Pixel_2_API_30
hw.lcd.density: 420
hw.arc: false
hw.device.hash2: MD5:55acbc835978f326788ed66a5cd4c9a6
fastboot.forceChosenSnapshotBoot: no
fastboot.forceFastBoot: yes
hw.trackBall: no
hw.battery: yes
hw.sdCard: yes
tag.display: Google Play
runtime.network.latency: none
disk.dataPartition.size: 6442450944
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes

SDK Tools I've got:

enter image description here

PC specs:

NVIDIA GeForce GT 630

enter image description here

I tried wiping the data, relaunching the emulator, creating new one - nothing helped. I hope someone could help me to launch this emulator. Thank you

Upvotes: 29

Views: 20051

Answers (6)

Andrej
Andrej

Reputation: 3225

Doing a cold boot fixed the issue for me.

Side bar > Device manager > More options (the three dots) > Cold boot

Upvotes: 0

Ben Robinson
Ben Robinson

Reputation: 1735

Moving the emulator out of the tool window didn't work for me; best solution for me (running on a Mac) was Force Quit the process in Activity Monitor.

Easy to find the process because it was using the most CPU, but mine is called qemu-system-x86_64

Upvotes: 0

Haylemicheal Berihun
Haylemicheal Berihun

Reputation: 131

I had the same issue on ubuntu 20 and the following steps work for me: file -> settings -> tools -> Emulator -> uncheck Launch in a tool window. Then launch the emulator.

Upvotes: 12

Andreea Both
Andreea Both

Reputation: 791

Had the same issue on a Mac and this worked for me: go to Android Studio -> Preferences -> Tools -> Emulator -> Uncheck “Launch in a tool window”. After that try to launch the emulator again.

Upvotes: 79

Biver
Biver

Reputation: 11

enter image description here

Check the Android Emulator option in SDK Tools to install

Upvotes: 1

Got Craziness
Got Craziness

Reputation: 55

there are many reasons for an emulator to get into a loop.

  1. Try to reinstall it
  2. Install a new device and Android version
  3. If you have an android device, unlock developer option and enable USB debugging. Then connect your Android device to your computer. Then run your program on your physical device.(Best option)

//Check whether V-Sync is enabled in your computer's BIOS. If not get it enabled.

Upvotes: -2

Related Questions