Emulator does not start (c066d201: unhandled exit 1d)

Question

After I deleted some old AVDs and creating a new one, I cant get any AVD to start. If I start them through Android-Studio, the AVD window will launch but the screen stays black and Android-Studio stops responding. If I start the AVD through the command line with the following command:

./emulator @Pixel_3_Api_19

The behaviour is the same and I get the following output in the console:

emulator: WARNING: encryption is off
emulator: WARNING: Running on a system with less than 6 logical cores. Setting number of virtual cores to 1
emulator: WARNING: EmulatorAdvertisement.cpp:80: Overwriting existing discovery file: /Users/koljenka/Library/Caches/TemporaryItems/avd/running/pid_2730.ini
c066d201: unhandled exit 1d
c066d201: unhandled exit 1d
c066d201: unhandled exit 1d
c066d201: unhandled exit 1d

The c066d201: unhandled exit 1d line is printed constantly.

I'm running a 2017 MacBook Pro with MacOS Big Sur Dev Beta, but i had the emulator running fine on the dev beta before deleting the old AVDs.

I am on Big Sur latest beta and also having this issue. Its intermittent. I have had to delete the emulator and recreate it a few times. Same issue with Android Studio 4.1 beta — adrian.coroian, Jul 29 '20 at 17:50
Thanks thats good to know. Maybe I'll just return back to Catalina for the time being. — Koljenka, Jul 30 '20 at 07:01
This other question is linked with Google Issue Tracker: https://stackoverflow.com/questions/63576252/android-emulators-are-not-working-on-osx-big-sur . I'm linking for someone in the future — Erick M. Sprengel, Aug 31 '20 at 00:32
I think this question is duplicate of well described: https://stackoverflow.com/questions/63576252/android-emulators-are-not-working-on-osx-big-sur — Duna, Sep 01 '20 at 04:29
It's the other way around, your question is a duplicate of mine, as mine is a month older. But I think it's fine. — Koljenka, Sep 01 '20 at 08:21
I updated macOS Big Sur to 11.0 (Beta) and the emulator is just working. Can someone else check it? — Erick M. Sprengel, Sep 10 '20 at 01:01

smoothdvd · Accepted Answer · 2020-08-01T03:41:17.107

24

Use option -gpu host.

You run emulator correctly like this

~/Library/Android/sdk/emulator/emulator -gpu host -avd Pixel_2_API_30

or try this:

create a file named advancedFeatures.ini in ~/.android

Put following settings in it:

Vulkan = off GLDirectMem = on

edited Aug 01 '20 at 03:41

answered Jul 30 '20 at 08:38

smoothdvd

2,389
4
20
25

3

Sadly, this didn't change anything. – Koljenka Jul 31 '20 at 08:10
@Koljenka Working for me with Big Sur beta 2, Android Studio 4.0.1 and emulator 30.0.12 – smoothdvd Jul 31 '20 at 13:23
@Koljenka You can also try create a file named advancedFeatures.ini in ~/.android. Put content like this: Vulkan = off GLDirectMem = on – smoothdvd Aug 01 '20 at 03:39
Both solutions proved useful. When the .ini file no longer worked the terminal command did. – Jordan Grant Aug 09 '20 at 23:18
4

Make sure to do `chmod 755 ~/.android/advancedFeatures.ini`, otherwise you'll get the same error – C13 Aug 11 '20 at 23:14
1

hi the solution partially works for me.. It works if i try to run the command couple of times. Then if i close the emulator and try again it kept giving me unhandled exit 1d. Anyone had similar experience or know how to resolve this? Any help is much appreciated. thanks in advance.. – Adi Aug 12 '20 at 11:27
@Adi got the same issue, I will try the canary preview, If I didn't answer then it hasn't worked – Stanislav Sobolev Aug 12 '20 at 17:47
2

@Adi You can try remove and then add -gpu option to make it work, or reset emulator data. – smoothdvd Aug 13 '20 at 02:04
@smoothdvd launching once without the -gpu host option and then turning it back on again worked for me! Thanks alot! – Koljenka Aug 13 '20 at 06:49
@smoothdvd i have tried removing and creating new ones, cold boot.. none of them helped.. – Adi Aug 13 '20 at 18:08
2

thanks it works, but what is the difference with running the emulator on this mode? – rsanath Aug 28 '20 at 18:30
This makes emulator slow and laggy – Matin Zadeh Dolatabad Aug 29 '20 at 16:03
The upper solution is verified and is NOT working on OSX Big Sur – Duna Sep 03 '20 at 15:30
1

@Duna It works for me with macOS Big Sur from beta 3 to 6. – smoothdvd Sep 05 '20 at 07:55
I'm on Big Sur beta 5 and I had to first create advancedFeatures.ini with options mentioned above and then start avd with -gpu host option – Doms Sep 09 '20 at 04:54

score 3 · Answer 2 · edited Sep 04 '20 at 14:30

3

Using Mac OS 11 Beta 6 (20A5364e) here. None of the solutions I found worked until I've tried this:

Completely wipeout and reinstall Android Studio (not sure if this is necessary, try skipping this step first. Use THIS as a guide)
Create your virtual device (if haven't already).
Now instead of running your device normally, open AVD manager and click Cold Boot Now:
You will see a warning message, just click DISMISS and your device will start booting:

edited Sep 04 '20 at 14:30

Dharman

30,962
25
85
135

answered Sep 04 '20 at 14:24

butaminas

672
7
23

1

This always works or does the process have to be done every time I launch the emulator? – user3154785 Sep 04 '20 at 14:36
1

I do the cold boot thing everytime I need to turn on the emulator. it works that way for me every time. – butaminas Sep 05 '20 at 19:08

Emulator does not start (c066d201: unhandled exit 1d)

2 Answers2

Linked