What about when the Eclipse ADT plugin calls it? Well I was feeling rather lazy at that point and didn't want to dig around in the ADT plugin to see if it had a 'add these command line flags whenever running the emulator' option, so I made a little 'wrapper' shell script for the emulator command that always adds the -noaudio option. Now, that works if I manually call the emulator from the command line. No sound support either, but at least I can run the emulator now. I was digging around the other day and saw this message appear on the terminal: emulator: warning: opening audio input failed Ive seen this message many. To run tests on emulators, use the AVD Manager included with Android Studio or the.
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. The instructions for this step differ for Mac/Linux and for Windows. 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.
