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.
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.
I have tried to delete the AVD and have created a new one again and again, but it didn't help with the problem. Press question mark to learn the rest of the keyboard shortcuts Log in sign up. 'emulator: warning: opening audio input failed' The above message is displayed in the console everytime an AVD is launching, and then no sound is coming out from the emulator.
#ANDROID STUDIO EMULATOR WARNING OPENING AUDIO INPUT FAILED MAC HOW TO#
But I decided to try an experiment that one particular day. Android Studio Emulator Warning Opening Audio Input Failed How To Deal With. 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.
0 kommentar(er)
