It failed 3 times in a row! What can be the reason for that? I made significant changes to the project since the last run (which succeeded), so can it be something in my code that makes it crash?
Thanks.
Please post any other errors that are relevant.
Here are some things to try:
Shut down and restart adb:
Open command prompt (Start > Run > cmd)
Type adb kill-server and then hit enter
Type adb devices and then hit enter
Clean and rebuild your project completely. If you are using Eclipse:
Click the Project menu at the top, go to Clean
Select your project, then click OK
I'm sure you have done this, but also try restarting your IDE.
This may sound stupid, but make sure your AVD IS running (and not locked up).
Related
I just wanted to use the genymotion Emulator and now nothing works anymore. I downloaded genymotion and added the plugin for eclipse. Now I'm getting every time these errors:
First a dialog appears with "Failed to parse the output of 'adb version'". Then the console shows this:
The connection to adb is down, and a severe error has occured.
You must restart adb and Eclipse.
Please ensure that adb is correctly located at
'.../android-sdks/platform-tools/adb' and can be executed.
I restart my computer 2 times, restart eclipse 6-7 times. Tried to kill-server and start-server in the terminal (I was wondered, because if i'm say ./adb start-server nothing appears in the terminal, that he's something doing. He just accept the line and directly then i could enter a new line)
I checked 10 times, that the adb is in the right folder and i do any other stuff, which i could found (Update,...)
After 3,5 hours i don't feel like it. So pleeeeeeaase help me!! I really don't know, what i should try anymore!!
(I'm using a mac :D )
just go to the program files and open genymotion.exe
go to settings
go to adb
change to choose custom sdk
browse to your sdk
click ok
You can try cleaning all your projects in Eclipse?
Project -> Clean
Answered myself :) -> "Just" reinstall android sdk :) .. If you doing that, you can clean up your computer and reinstall eclipse, too :) I did all and now all work's fine and fast :)
I have some error with my android project and eclipse, when I start the emulation it fails:
I think its a problem with eclipse, because it worked yesterday but today I have this error.
I have no more information, the console has nothing ando so does the LogCat.
I tried to clean the project, but the error continues.
How can I solve this?
Go to Task manager kill adb.exe
and relaunch the eclipse
And than clean project.
Go to cmd, type following command:
adb kill -server
adb start server
then run program, surely it is working.
I'm new with android development, and I have problems installing all the recent platform. I'm a java developer that I would like learning android.
I've installed all programs succesfully in windows xp sp3 (JDK 1.6 with environment vars created, eclipse 3.5, 3.6 & 3.7 well configured, Android SDK with all the features, devices, platform-tools, APi's, etc, and ADT Plugin 12 for eclipse with an emulator to API 8 -Target 2.2-), but, when I'm running an android project into eclipse (Run -> Android Application), the eclipse console show me: "The connection to adb is down, and a severe error has ocurred... You must restart adb and eclipse... Ensure that adb is in this path 'D:\Android\android-sdk-windows\platform-tools\adb.exe'" (or something similiar).
I'm very sure that the path is right, adb is correctly running on command-line, and the commands 'adb kill-server' and 'adb start-server' works fine, but doesn't solve my problem (like I've read in other answers).
The emulator, via Eclipse, not working, but if I start the emulator via Eclipse ADV Manager, emulator starts fine, but when I runs the android app, I take the same error.
I suppose that Eclipse can't start adb,but I don't know why.
Other issue, when I executed 'adb devices', console show me an empty list, no 'no devices' message, but when I plugged my HTC, adb is running fine in console, but Eclipse doesn't.
In addition, I also try restarting adb with Eclipse - Devices tab, but the list of devices are empty too.
Anyone can help me, please? I've read so much that my eyes are pixelated. xD
Best regards!!
PD: sorry, but my english is a bit poor ;)
in the DDMS perspective (if it doesn't show, add it by click window>open perspective>other...>DDMS)
then click the triangle of the devices tab > reset adb.
this works for me.
I finally resolved the problem, please see my blog
you can do this steps to solve the problem:
task manager-> process
right click on adb.exe and left click on "properties"
check the path of the process:
-if the path is like "Programs\android-sdk\platform-tools", which means it is the android sdk that is running this process.
-if not, that means there is another process this is running adb.exe, you have to kill the process or service which runs adb.exe.(you can identify the process by the path)
I've had this problem too. The solution I've found is to kill eclipse, open up task manager and kill the adb.exe process. Then when you start eclipse again, that should also kick start adb and it should work from there.
Try the following steps :
- Close Eclipse IDE
- Go to the Android SDK platform-tools directory in Command Prompt
- run adb kill-server
- run adb start-server
- Now start Eclipse again.
Hope this may help you :)
In my case, in Windows7
Close all opened emulators
Go to task manager > processes and then click on adb.exe and press the button 'end process'.
Then go to command prompt go to plate-form tools and type
adb start-server
Then run your application through eclipse.
It worked fine for me.
you try
Open Task Manager > Processes > eclipse.exe > End Process > restart eclipse
In my case the problem was the FIREWALL!.Turn off your windows firewall , Then restart adb and eclipse from task-manager
I am running Windos 7 and Eclipse 3.5 and I don't know why I keep getting this error. When I try run the program it gives me:
[2010-02-13 23:09:41 - HelloAndroid]The connection to adb is down, and a severe error has occured.
[2010-02-13 23:09:41 - HelloAndroid]You must restart adb and Eclipse.
[2010-02-13 23:09:41 - HelloAndroid]Please ensure that adb is correctly located at 'C:\Users\Mohit\Documents\AndroidSDK\tools\adb.exe' and can be executed.
I even tried runing Eclipse and adb.exe as admin. What is going on? How can I fix this and start making Android apps?
turned off COMODO Defense+ module and all worked....
If you have comodo internet security installed, you dont have to shut this feature down:
run comodo settings
defense+
list active processes
add adb.exe to trusted processes
restart server: run "adb kill-server" "adb start-server"
EDIT: For user of Comodo 6.x
Open Comodo
Click Tasks Icon at right top
Click Advanced Tasks
Click Open Advanced Settings
Select Security Settings --> File Rating --> Trusted files from
left panel
Click on the upward arrow icon at the bottom
Click Add --> add the adb.exe
there you go :) Hope this helps
Yes i had the same problem after i had did the update,
however, i have just fixed it :)
TO FIX THE PROMBLEM:
in folder: \android-sdk-windows\
go to folder \platform-tools ; copy the files
and paste in to folder \tool
Restart the Eclipse
I messed with all the solutions provided above, but I found another one-
Try launching eclipse with administrator privileges
RUN AS ADMINISTRATOR
hope it'll do the job.
After installing 2.3 SDK I got adb inside D:\AndroidSetup\android-sdk-
windows\platform-tools directory. I had set this path in environment
variable and my problem is solved.
Two options to solve this problem on windows:
Option 1:
Close the eclipse, if it is running.
Run the command prompt.
Go to the tools location of the android sdk.
run 'adb kill-server'
then run 'adb start-server'.
start the eclipse.
Option 2:
Open the task manager.
kill the adb process.
start the eclipse.
Problem should be solved.
What it work for me and this was because I move from one eclipse to another is to re install SDK and then re install ADT again, remove completly from eclipse ADT and re install.
As illustrated by this thread, you may need to kill an exisiting abd process, or unblock the 5037 port (remnants of previous adb start attempts).
Try closing Eclipse, issuing a
'C:\Users\Mohit\Documents\AndroidSDK\tools kill-server' command from terminal and retrying.
If that still doesn't work, you could try opening Activity Monitor to see if there are any existing adb processes running, and kill them.
Hi, it's OK now, I'saw with the nestat - a command line that theer was several processus on the 5037 port. The port wich serves for the emulator.
Thanks
force to start sdk manager several times (try directly from the file explorer). when you could do that comodo may send a mesage. allow the issue. then start again the sdk manager and update.
update eclipse then.
When I launch the emulator I face many problems (Errors):-
HttpConnectionApp]emulator-5554 disconnected!
Cancelling 'net.paxcel.http.HttpConnectionApp activity launch'!
Emulator]emulator: ERROR: the user data image is used by another emulator.
aborting
Each time I have to re-run it but all in vain.
How can I improve this so that I can re-run the application on same AVD?
I had the same issue after my computer locked up and I had to power cycle it.
Wiping the user data didn't fix my problem, I had to delete the following folders manually
C:\Users\%UserName%\.android\avd\AVD2.1.avd\cache.img.lock
C:\Users\%UserName%\.android\avd\AVD2.1.avd\userdata-qemu.img.lock
A quick-fix that obviously works is to restart the adb server each time this error occurs:
adb kill-server && adb start-server
Then, you simply run the application again (without restarting AVD) and that's it.
Run configurations → Target → Wipe user data → Run.
It fixed the problem in my case.
Here is the answer that helped me:
link text
Another solution for me is start the avd manager and start once emulator from there. After that everything turns to normal.
AFAIK, this happens when an emulator is started, but the Android Debug Bridge couldn't establish connection to it.
If you have just started the emulator with your application, watch if you get Waiting for HOME to launch... or something similar in your Console.
If you don't get that message, but the emulator has been started, chances are, you'll get into the ERROR: the user data image is used by another emulator situation again.
emulator: ERROR: the user data image is used by another emulator. aborting
Tried restarting the computer as I had done a lot of messing around earlier but no joy same error.
Went to shut down ADB so as I'm on XP I run > cmd then paste in > cd C:\Program Files\Android\android-sdk\platform-tools (the location of the location for the ADB on XP)
Tried
adb kill-server && adb start-server
Then moved the directories cache.img.lock and userdata-qemu.img.lock in the C:\Documents and Settings\.android\avd\ to a New folder (instead of deleting)
This worked fine.
Delete the existing emulators and then make a new one.
This worked for me, when I had this problem and couldn't find the folders to delete.
Under Run Configurations --> Target --> Add Command Line Options add this
adb kill-server && adb start-server
every time running your App will kill-restart the adb server.
It's probably a bad install of ADT. Try uninstalling the plugin, restarting Eclipse, then installing it again fresh.
That of you aren't letting the emulator boot all the way up and are closing it before ADT/ADB can install/run your app.
Please set wipe_data for emulator
Use same instance of application (after modification if any) to avoid error you are getting.
This can also happen if you're using a network share as your home folder, because some network file sharing systems may lock the image files.
Delete the directories cache.img.lock and userdata-qemu.img.lock (in my case these files are in /mylocalusername/.android/avd/avd7.avd
Thanks for this! Just to add for some people who develop in Windows XP.
The path to the avd directory can be C:\Documents and Settings\.android\avd
Thanks again for the answer! :)