Problem description encountered:
Running the Android program console output
[2013-11-04 16:18:26-] The connection to ADB are down, and a severe error has occured.
[2013-11-04 16:18:26-] You must restart ADB and Eclipse.
[2012-11-04 16:18:26-] Please ensure the ADB is correctly located in ' D:\java\sdk\platform-tools\adb.exe ' and can be executed.
1. Problem Solving:
Baidu Google said that the task manager kill the ADB or restart the ADB server, but my task manager does not have the ADB, speculation is that a program occupies the ADB port. So follow this idea to find.
5037 View the port for the ADB default port as follows:
Netstat-aon|findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 Listening 6540
Found that 6540 took up 5037 ports and continued to view 6540 of the task and found it was Wandoujia. as shown below
Tasklist|findstr "6540"
Wandoujia_daemon.exe 6540 Console 1 4,276 K
The next question is solved, kill Wandoujia_daemon.exe in Task Manager, run Android program, OK.
2. Add both Android-sdk-windows/platform-tools and android-sdk-windows/tools to the environment variable.
(Classpath or path)
I have tried or not, continue to Baidu.
3. I unloaded the pea pods, or not, and finally:
Today I met this problem because I updated the latest ADT to appear adb server didn ' t ACK, failed to start daemon then you want to start a program this time it will appear again please ensure that ADB is Corr ectly located at ' D:\android-sdk-windows\platform-tools\adb.exe ' and can be executed. "
First of all, check to see if you want to view the task Manager, turn off all adb.exe.
Add both Android-sdk-windows\platform-tools and android-sdk-windows\tools to the environment variable.
Test to be able to start not if not
Run the command line
ADB kill-server
ADB start-server
This time may appear
D:\ANDROID-SDK-WINDOWS\PLATFORM-TOOLS>ADB Kill-server
D:\ANDROID-SDK-WINDOWS\PLATFORM-TOOLS>ADB Start-server
* Daemon not running. Starting it now on Port 5037 *
ADB server didn ' t ACK
* Failed to start daemon *
If there is something wrong with this time the only option, I do not listen to the internet to say what restart the machine to restart Eclipse, my approach is
In Eclipse, in the Android manager, select the first option virtual device virtural device from the inside to find a simulator to start when you start up, turn off your eclipse, AVD.
The point of life here is to be aware that the virtual device must first be opened and then the eclipse will be restarted at least that's my way.
Notice a sequence problem
So my problem was solved, but it came up again:
ActivityManager:Starting:Intent {act=android.intent.action.main cat= [Android.intent.category.LAUNCHER] cmp= com.android_denglu/. Mainactivity}
ActivityManager:Warning:Activity not started, it current task has been brought to the front
is very tangled, continue to Baidu ing ....... ......
Baidu in the Great God said: "Deleted AvD, I try to build a, hope to succeed."
I fainted, and there was the problem of Emulator-arm.exe stopped working. Now the virtual machine is not out of one ....
Workaround: When creating AVD, there is a hardware option, click New, you can see the GPU emulation Select Yes, and then my Android interface comes out, the problem is really tangled.
See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/OS/extra/