Solution to the problem of the Android emulator port being occupied

First, the problem description

When running Android projects in Eclipse today, I encountered the "the connection to ADB are down, and a severe error have occured" issue, as shown in:

　　

The first time encountered this problem, the Internet check for a reason, the original "The connection to ADB are down, and a severe error has occured" refers to the Android emulator port is occupied.

Second, the problem of the process of troubleshooting

Now that the port is occupied, it is time to look at who is occupying the port.

There is a adb.exe executable in the Platform-tools directory in the SDK directory, which is the launcher for the Android emulator, as shown in:

　　

Open the CMD Command Line window, enter the Platform-tools directory under the SDK directory, enter the command: ADB START-SEREVR, as shown in:

　　

As I was building the Android development environment, I added the Platform-tools directory under the SDK directory to the PATH environment variable, as follows:

　　

　　

So I entered the command directly in the cmd command: ADB START-SEREVR is operational and no longer needs to go into the Platform-tools directory under the SDK directory.

From the results shown above, it is true that the port is occupied, and then you need to determine what the port number is occupied, enter the command: ADB Nodaemon server, as shown in:

　　

OK, now OK, Port 5037 is occupied, it is necessary to find out who dares to occupy 5037 ports.

In cmd, enter the command Netstat-ano |findstr "5037" as shown in:

　　

The original is 5040 this process occupies the port, we have to find out the process, in cmd input command tasklist/fi "pid eq 5040", as follows:

　　

OK, already found, is a name for Shuame_helper.exe, open Task Manager, kill this process can be.

Solution to the problem of the Android emulator port being occupied