adb socket not working and daemon

Question

I am getting this type of error

error: could not install smartsocket listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket ad

Answer 1

In my case, none of the above solution worked. I solved it strangely maybe it can be a bug.

Do not run Genymotion emulator before Android Studio. Firstly, I opened android studio then I clicked run project and select deployment target windows appeared. Then I run genymotion emulator and now the emulator is shown in the select deployment target windows in Android Studio. Then deployed to the emulator without errors. Done!

As another way, you can try to set Genymotion sdk to the same as Android studio sdk. To do this, first find your sdk location. You can find it by right clicking the Android Studio project -> Open Module Settings-> Select SDK location -> under Android SDK location, it is shown. Then open Genymotion -> Settings -> ADB tab -> Click Use custom Android SDK tools radio button -> navigate to SDK folder used by Android studio -> Restart Genymotion virtual device

Answer 2

1. Close Eclipse or Android Studio if either is running (Optional).
2. Open Command Prompt.
3. Go to the Android SDK platform-tools directory.
4. Type adb kill-server.
5. Type adb start-server.
6. If no error message is thrown while starting ADB server, then adb is started successfully.

OR

1. Go to Task Manager, open the Processes tab, and end the adb.exe process.
2. Then restart Android Studio.

This may work if there is any problem with adb.

Answer 3

If none of the above worked for you, just make sure that you have closed Genymotion emulator as it caused this issue with me.

Answer 4

I came across same error.I gave below command.It got solved

COMMAND :- taskkill /f /im adb.exe

Answer 5

Easiest Way! I just ran into this issue trying to connect a React-Native App to an Android Studio emulator. If you read the error message it tells you that "Only one usage of each socket address (protocol/network address/port) is normally permitted." So you can assume that something other than React-Native is also attempting to connect to the emulator.

Terminate The Connections:

1. Leave the emulator running.

2. Close out of and uninstall any Android Studio/Eclipse Apps you have on the emulator. This terminates apps trying to connect.

3. Close Eclipse or Android Studio if either are running. Android Studio doesn't have to be open in order for the emulator to work (This is important). This terminates software trying to connect.

After doing so I went back into my React-Native App and connected to Expo no problem.

All you have to do is terminate all connections. However you so choose.

Answer 6

I came across the same error, it worked simply after restarting the AS on windows, of course, it asked for SDK update.