On a recent project I was working on, I wasn’t able to start the Android Emulator/Simulator anymore from within Android Studio. Make sure you’re running the latest version of Android Studio. You can set up an emulator on Android Studio via the AVD Manager.
UPDATE 2017.08.03: This should be fixed with the release of HAXM 6.1.1. An Android device or emulator to run our example app.
Now, that works if I manually call the emulator from the command line. on Fix for the Android Emulator (Android Simulator) crashing during launch. Incompatibility with 1.4.x Kotlin Multiplatform Mobile plugin. Citra Emulator for PC/MAC, and Gatewa圓DS/Sk圓DS Flashcarts for the 3DS Consoles. Known issues with the Android Gradle Plugin. Native debugger crashes with 'Debugger process finished with exit code 127'. No sound support either, but at least I can run the emulator now. Android Studio incorrectly force stops the app. Turns out the emulator has a "-noaudio" command line option, and when I ran it with that, it worked!! So now I just run emulator with the -noaudio option always, no freezes. But I decided to try an experiment that one particular day.
I was digging around the other day and saw this message appear on the terminal: emulator: warning: opening audio input failed I've seen this message many times before and I had always assumed that it was because the emulator didn't support sound or something like that. If you already have an Android Studio build on the Canary or Dev channel, you can get the update by clicking Help > Check for Update (or Android Studio >.