Thread: Support droid explorer
View Single Post
Old May 20th, 2010, 10:38 PM   #52 (permalink)
camalot
New Member
 
Join Date: Dec 2009
Posts: 6
 
Device(s): ADP1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

@cbuy

The main reason for this is because Droid Explorer uses a local "minimized" sdk which has a version of ADB. this causes issues where there are other versions installed on the system.

This is something that I am going to correct in a future release, but in the mean time, a solution you could do is to stop the droid explorer service:

Command Prompt: net stop droidexplorerservice

(you may want to do an "adb kill-server" from the command line as well at this point, just to make sure adb is stopped)

copy over the files from your sdk/tools to C:\program files\droid explorer\sdk\tools

then restart the droid explorer service
net start droidexplorerservice
camalot is offline  
Reply With Quote