Configuring the Android environment for problems and workarounds

Configure your Android environment for problems and workarounds:

1 Environment Installation Address

Http://pan.baidu.com/s/1jGzNzyI

2 Other:

2.1 Installation

2.1.1 Installation Jdk,jre

After successful installation, the test is really successful installation, click "Start"----"Run"----input CMD, enter "Java-version" at the command prompt and press ENTER, the version number is installed successfully.

2.1.2 Installing ADB

2.1.3 Open Eclipse

2.2 Configuring Environment variables:

2.2.1 Configuring Java Environment Variables ( see 2.2.1 below)

2.2.2 Configuring the ADB environment variable for Android ( see 2.2.2 below)

Related documents

2.3 Possible problems and workarounds

2.3.1 solve the ADB server didn ' t ack problem, connected to the phone problem

The following conditions occur

ADB server didn ' t ACK
* Failed to start daemon *

Workaround:

Method One:

(1) View Task Manager, close all Adb.exe, or run->cmd, enter ADB kill-server in the command window

(2) Restart Eclipse

More details ( see 2.3.1 below to resolve the ADB server didn ' t ack problem, connected to the phone problem)

2.2.1 Configuring Java Environment variables:

1. Start configuring environment variables, right-click My Computer---properties-----advanced---environment variables,

2. Select "New System Variable"--pops up the "New System Variable" dialog box, enter "Java_home" in the "Variable name" text box, enter the installation path of the JDK in the "Variable Value" text box (that is, the folder path of step 5), click the "OK" button,

3. View the path variable in the system Variables options area, and if it does not exist, create a new variable path, otherwise select the variable, click the Edit button, and add "%java_home%\bin;%java_home%\jre\bin;" At the beginning of the Variable Value text box. or direct "%java_home%\bin;", click the OK button,

4. View the CLASSPATH variable in the system Variables options area, and if it does not exist, create a new variable classpath, otherwise select the variable, click the Edit button, and add "in the start position of the Variable Value text box."; %java_home%\lib\dt.jar;%java_home%\lib\tools.jar; ".

5. The configuration of the test environment variable is now successful or not. Enter "JAVAC" in the DOS command line window and the output Help information is configured correctly.

2.2.2 Configuring the ADB environment variable for Android

1. The first step is to open the Environment Variables Configuration window. Right-click Computer, Properties-Advanced system settings-environment variables.

2. The second step is to add the Android system environment variable. under System variables, click the New button, enter the environment variable name Android (own custom name), the path of the Android development tool to import,

3. in the third step, add the environment you just added in path. Select the system variable in path, click the Edit button, enter the environment just built, method and configuration Java, remember to add climbed semicolon,

4. Fourth Step, test the environment variables.

   First open the Run command, run in the Start menu, if you can not find to search in the beginning, you can also directly press and hold the Win+r shortcut key, open run.

5. in the final step, enter CMD in the run and invoke the Command Action window. Enter ADB to view the results of the operation.

2.3.1 solve the ADB server didn ' t ack problem, connected to the phone problem

The following conditions occur

ADB server didn ' t ACK
* Failed to start daemon *

Workaround:

Method One:

(1) View Task Manager, close all Adb.exe, or run->cmd, enter ADB kill-server in the command window

(2) Restart Eclipse

Method Two,:

If the method is not, you can check whether your computer has started such as: 91 mobile phone assistant, 360 mobile phone pea pod, etc. first shut him down, reconnect try, and then uninstall these software should be able to solve. Because these software may occupy the ports of Android phone and Eclipse connection start adb

Method Three:

5037 ports are occupied, you will also see the following prompt ...

So, it's like finding a lifeline. In the command line, first enter the following instructions to see 5037 this port is now occupied by who:

Netstat-a-O 5037

And then get a result like this, and it's really taken up, OH:

What is this 4792 on my machine, exactly what is the process, OK, then enter the following command to find out the real killer:

Tasklist/fi "pid eq 4792"

Then, the amount ... It's the famous Pea pod:

Configuring the Android environment for problems and workarounds