可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试):
问题:
Possible Duplicate:
The connection to adb is down, and a severe error has occured
I am currently trying to develop an application for Android in the latest release of Eclipse. When I try to build and run, the following comes up:
[2011-02-17 17:08:03 - <ProgramName>] The connection to adb is down, and a severe error has occured.
[2011-02-17 17:08:03 - <ProgramName>] You must restart adb and Eclipse.
[2011-02-17 17:08:03 - <ProgramName>] Please ensure that adb is correctly located at 'C:\<sdk-directory>s\platform-tools\adb.exe' and can be executed.
Now, I have updated the ADT plugin, I have the latest version of the Android SDK; adb.exe is, in fact, in the platform-tools directory and can be executed. I've tried everything I found on Google:
- I tried adb kill-server and adb start-server
- I tried to run it with an without an emulator started
- I have the given directory in my PATH (I tried with just the platform-tools in the path and I tried with having both platform-tools and tools in my PATH).
Notes: I am running Windows 7. Also, I have previously tested apps in Eclipse. This error is new to me since upgrading the SDK.
回答1:
I just got the same problem and to fix it, I opened the task manager and killed the adb.exe process, then I restarted Eclipse.
回答2:
Reinstall everything??? no way! just add the path to SDK tools and platform tools in your classpath from Environment Variables.
Then restart Eclipse.
other way go to Devices -> Reset adb
, or simply open the task manager and kill the adb.exe
process.
回答3:
I restarted eclipse and did the Project -> Clean -> select your project
One of them fixed my problem with adb
[2011-12-31 10:50:45 - HelloAndroid] Android Launch! good
[2011-12-31 10:50:45 - HelloAndroid] adb is running normally. good
[2011-12-31 10:50:45 - HelloAndroid] Could not find HelloAndroid.apk! bad
Thanks for the help. On to the next problem (sigh)
回答4:
Sounds a bit familiar with my problem: aapt not found under the right path
I needed to clean all open projects to get it working again...
回答5:
I had exactly the same problem with you. And after two days wondering why this occurs to me, I finally got through this by moving the adb.exe from the unreliable software list of the COMODO anti-virus to its reliable software list. At that time, I had tried at least 5 kinds of measures to make the adb work, including all above...
回答6:
I had a similar problem with adb.exe and Eclipse last time I updated ADT plugin. The solution was to run Eclipse as administrator and reinstall ADT.
回答7:
The problem might be with your firewall or antivirus.
- Disable all network connection
- Disable firewall
- Disable Antivirus
Make sure they all disabled.
Run your script in Eclipse. If it works, then 2 and 3 might be the culprit. For me, it was comodo firewall. I created a filter for Adb.exe
回答8:
For me the following worked:
Kill adb.exe from Task Manager
Restart Eclipse as administrator
For my app, the target was Google APIs level 10.. I went to Window-> AVD Manager and the entry for "Google APIs level 10" had a broken instead of a green tick - so I just clicked the entry and clicked the "repair" button and problem was fixed
(It was probably only 3 above..)
回答9:
Judging from what you've posted, and assuming it's not a typo, Eclipse is looking in C:\s\platform-tools...
If that's the case, then you should check Eclipse's Window/Preferences/Android option for the SDK Location. Maybe yours is set to "C:\s". You can't edit it to be a value such as that without causing an error, but maybe it's got corrupted somehow.
回答10:
It's also possible to get this error if you are running the test project using JUnit instead of Android JUnit. Naturally, the solution is just to change how you run it.
回答11:
The connection to adb is down, and a severe error has occured.
[2011-12-19 11:45:09 - RayhReport] You must restart adb and Eclipse.
[2011-12-19 11:45:09 - RayhReport] Please ensure that adb is correctly located at 'D:\android-sdk-windows\tools\adb.exe' and can be executed.
When you go to D:\android-sdk-windows\tools\adb.exe
path then you see the text file,the name of file is "adb_has_moved" thats means your adb.exe
is moved to platform-tools copied down the adb.exe and paste in tools folder and run it. I'm sure it works.