Why is the android emulator starting but then dying immediately?

Question

I've installed Android Studio on my Ubuntu 16.04
I've set up a device using the AVD device manager

When I try to start the device the emulator flashes very quickly and then disappears.

I tried several different versions but for all of them the emulator window flashes for a fraction of a second then disappears.

How can I get the emulator to work? Where are logs that will show what problem I am having?

Is HAX enabled ? http://stackoverflow.com/questions/21031903/how-to-fix-hax-is-not-working-and-emulator-runs-in-emulation-mode — Sreehari, May 10 '17 at 13:30
This is a problem with 7.1 . Try removing break points. Check [link](http://stackoverflow.com/a/40908660/5954472) — Arpan Sharma, May 10 '17 at 13:31
Try running the emulator from the command line. From the `tools/` directory of your Android SDK, run `./emulator -avd "..."`, where the `...` is the name of the AVD. You might need to look at `~/.android/avd/` to determine the proper value of `...`. — CommonsWare, May 10 '17 at 13:41
this answer worked for me https://stackoverflow.com/questions/4791943/emulating-density-of-320-dpi-on-android-emulator — Faisal Hassan, Aug 21 '19 at 11:13

score 32 · Accepted Answer · answered May 10 '17 at 13:42

32

Try these method

Edit your AVD ,On Graphics select Software-GLES instead of Auto.

Open Android Monitor to see the errors.

answered May 10 '17 at 13:42

Nidhin

1,818
22
23

1

Yes, this fixed the problem ! – Michael Durrant May 10 '17 at 14:03
Although it's really slow. Now I need to figure out HAX, hopefully that is not just the hardware option here which didn't work! – Michael Durrant May 10 '17 at 14:43
fixes my problem, can you say @MichaelDurrant if you went further and did something with HAX, break points etc? – Mr-Programs Jan 08 '19 at 22:33
1

You save my day after 2 years. Mobile dev == every time one surprise. Miss when we just use a text editor to dev – Bruno Pitteli Gonçalves Apr 29 '19 at 15:08

score 4 · Answer 2 · answered Dec 13 '17 at 16:22

4

Heads up:

For the ones of you that use docker, make sure docker is closed before trying to run the emulator.

That fixed it for me.

answered Dec 13 '17 at 16:22

SudoPlz

20,996
12
82
123

1

Thanks- never would have figured that out – Suchipi Feb 12 '18 at 23:29
Actually worked, i have dockerized node.js and MySQL why is ruining the android emulator, that's strange – Tarek hemdan Feb 21 '22 at 16:40

score 2 · Answer 3 · answered May 30 '19 at 12:38

2

Or you can select cold boot now from AVD drop down menu. It works fine.

answered May 30 '19 at 12:38

devsinghindra

21
2

score 1 · Answer 4 · answered Feb 12 '20 at 14:05

1

What helped me was to change the emulated system to Cold boot instead od Quick boot. It is on ubuntu and before that change the emulated system just disappear after sometime.

answered Feb 12 '20 at 14:05

Luciano Billotta

11
1

score 0 · Answer 5 · answered Apr 10 '19 at 07:38

0

I've recently updated my Android Emulator to 29.0.1 and got this issue. The above solution may be true but that didn't worked for me. So, the method I used to make it work was to Wipe data of device from AVD Actions Drop-down.

answered Apr 10 '19 at 07:38

Feroz Khan

2,396
5
20
37

score 0 · Answer 6 · answered Oct 13 '19 at 08:59

0

If any of the above does not work for you, you should simply create another emulator using a different image from the image in crashing emulator.

answered Oct 13 '19 at 08:59

Thecarisma

1,424
18
19

score 0 · Answer 7 · answered Dec 16 '19 at 13:59

0

In my case, none of the other answers worked. Instead what did the trick was switching to an older Android Version (so instead of using Android Q I tried Android Marshmallow).

answered Dec 16 '19 at 13:59

Dan Crisan

137
7

score 0 · Answer 8 · answered Jan 04 '20 at 12:11

0

For me, it was just a wrong SDK. I tried to run Android Q Google APIs. When replaced it with Android Q Google Play, it got to work.

answered Jan 04 '20 at 12:11

Некто Лохматый

411
4
5

score 0 · Answer 9 · answered Jun 24 '20 at 13:30

0

What did the trick for me, was disabling the anti-cheat engine (Vanguard from Riot in my case ) that ran as kernel-mode driver on boot on my system.

answered Jun 24 '20 at 13:30

Ritwik Badola

1

Why is the android emulator starting but then dying immediately?

9 Answers9

Linked