10

I cannot start my emulator after update sdk to 23.0.5 with following errors on windows. Can anyone help? thank you

WARNING : No started emulators found, starting an emulator. Waiting for emulator... emulator: device fd:61HAX is working and emulator runs in fast virt mode emulator: warning: opening audio input failed

creating window 28 27 320 480

FATAL:.//android/base/sockets/SocketWaiter.cpp:89:Check failed: isValidFd(fd). fd 1044 max1024 Error accepting connection, aborting

gnokit
  • 113
  • 1
  • 7

6 Answers6

10

Start it from the command line:

emulator -avd <device_name> -no-audio
rnrneverdies
  • 15,243
  • 9
  • 65
  • 95
Mohanad Haddadin
  • 569
  • 6
  • 15
  • 1
    Your answer helped. I was able to keep the http proxy by just adding the "-no-audio". Thanks. – gtrig Jan 23 '15 at 19:32
  • It doesn't work for everybody - please star bug so we can get it fixed: https://code.google.com/p/android/issues/detail?id=102361 – damian1baran Jul 06 '15 at 20:20
3

Same here, it seems to be related to http proxy (on command line -http-proxy, or as environment variable http_proxy), if I don't use http proxy it works.

venergiac
  • 7,469
  • 2
  • 48
  • 70
J Rao
  • 59
  • 1
  • 3
  • Removing http_proxy env variable worked for me. Since I use Eclipse and AVD manager instead of command line, I had to restart Eclipse and AVD manager after removing http_proxy. And also, checking "Wipe user data" in the Start options helped, I guess. – IdleSun Nov 12 '14 at 23:13
2

Adding "-http-proxy none" (without quotes) in Run configuration also fixes this issue as shown in image attached.

enter image description here

Vinay Kadalagi
  • 1,315
  • 1
  • 8
  • 11
0

Related to this thread: Android emulator with proxy settings - Error FATAL:.//android/base/sockets/ Check failed: isValidFd(fd). fd 1404 max1024

It still doesn't work. Please star this bug report so we can get it fixed - I already suggested to modify FD_SETSIZE from winsock.h to higer value e.g. 2048 as it doesn't change windows socket implementation as per microsoft's documentation:

// Default FD_SETSIZE is 64 which is not enough for us.
#  define FD_SETSIZE 1024

https://code.google.com/p/android/issues/detail?id=102361

Community
  • 1
  • 1
damian1baran
  • 1,307
  • 1
  • 14
  • 13
0

Found another solution:

You can now use the new Android Emulator 2.0 Beta that has the defect fix.

The defect workarounds (-no-audio -http-proxy none) didnt work for me.

Get Android Emulator 2.0 Beta: By downloading the new "Android SDK tools" version 25.x.x . Full instructions can be found here.

-1

I hit this today, and deactivating proxy (or audio, as suggested in another recent question) made no difference. It affected all my AVDs. When I first opened the AVD Manager I was also getting the following error:

  Android SDK Content Loader
  parseSdkContent failed
  Could not initialize class android.graphics.Typeface

Following the advice from parseSdkContent failed Could not initialize class android.graphics.Typeface to:

  • shutdown eclipse
  • delete the .android directory (and all contents) in my home directory (e.g. C:\Users\<your user name> on Windows 7)
  • restart Eclipse

worked a treat for me.

Community
  • 1
  • 1
cjn
  • 369
  • 2
  • 9