I upgraded to Gingerbreak 2.3 SDK today and started receiving this error when I try to run DDMS:
Failed to get adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified.
How can I fix this? Running Windows 7, 64bit.
It seems that adb.exe is now in the SDK's platform-tools folder. I had to add the platform-tools folder to my PATH in my Environment Variables.
I tried to upgrade my perfectly working Android dev system yesterday with the new 2.3 SDK and associated ADT. After the upgrade, I couldn't get Eclipse to compile my project correctly, nor could I access the Android SDK and AVD Manager from Eclipse. Eclipse seems to have lost track of where the Android SDK was installed. I would give it the name of the folder, but then it could come back saying it couldn't find .../tools/adb.exe. Yes I know adb.exe moved. But notice that the error was looking for it in the old spot. It's like I didn't have the new ADT, but I checked and rechecked and I did. I'm thinking that the new ADT didn't install correctly for some reason, and/or I wasn't checking it's version properly.
When I searched around for a solution, everyone pointed out that adb moved and that the classpath needed to change. But there isn't really a relevant classpath in this situation. There is just a path to the Android SDK that needs to be set in Eclipse. I even tried the trick were I copied adb.exe back to the tools folder. At that point, Eclipse could find the Android SDK, but then some other problem that crept up so I gave up on that hole.
Anyway, I ended up blowing away my eclipse and Android SDK folders and starting over. Now it works fine. I'm sure there's a better solution, but I was sick of messing with it.
I'm now 2 for 4 on using Android SDK and AVD Manager to do an upgrade.
Hope this helps someone.
Update: Upon further review, I seem to have my stackoverflow topics mixed up since the OP never mentioned Eclipse.
I had the same problem and it works like this . First run adb.exe , after open ddms.bat
Related
I have recently installed Android SDK on my computer running Windows 7 x64.
I then installed the Eclipse ADT plugin. I am running Eclipse Juno JEE.
When I attempt to run the SDK Manager through Eclipse, I receive the following errors:
Nothing I have tried has allowed me to download/install/update Android SDK and its packages.
I have tried https and forcing http
I have tried running calling program as administrator.
I have added Eclipse, SDK Manager to Firewall exceptions.
I have turned off my antivirus.
I have turned off my firewall.
I have tried various combinations of the above.
I can navigate my browser to both URLs (using Firefox). That should negate "Failed to read..." options 1 and 2. Option 3 seems to be the likely candidate as the XML files do not, in fact, include the <'xsd:schema'> tag. However, I don't know how, if, or where I might be able to point SDK Manager to a local, modified copy of these XML files, or if that would even solve anything.
Any help would be greatly appreciated.
Note: I have installed Android SDK/ Eclipse ADT Plugin on the same machine in the past. This is a fresh install after a recent reimage.
I am not sure if this answer's your question exactly to the point but yet I hope this helps you.
As u wrote it looks like you have downloaded eclipse from its website and android sdk separately from Android website. Why don't you download the Android SDK ADT package with pre-eclipse setup.
That will make your job way lot easier.
The file name would be something like this:
adt-bundle-windows-x86_64-20130729.zip
I recently updated my version of eclipse from 3.6 to 3.7
(Using Mac OS X 10.6.8 & Eclipse 3.7). I did this to install EGit. Since, then I have noticed that none of the changes to my App are being reflected in my AVD's.
When setting up EGit I realized that it had moved my working location to another location on my system. I figured this might be the issue, so I removed my EGit repository and restored my App from a backup. The problem continue leading me to believe the problem likely lies (I could be wrong) with the upgrade to Eclipse 3.7.
I have tried many other things, but none seem to work. So far I have..
Uninstalled my App from the AVD, and then re-ran application. This made no difference.
I have tried creating a new fresh AVD. Same deal here, same un-change version of app is applied.
I tried stop and restarting the adb.
I have tried to 'Clean up' the Project.
All attempts so far have failed.
Has anyone else out there seen this problem or have any suggestions?
I think the next thing I might try is updating my Android plug-ins. If this fails I Afraid my next option is to uninstall Eclipse completely and start from scratch.
Any suggestions would be great.
I solved the problem.
My guess of updating the Android SDK was correct.
In Elipse I went to Window -> Android SDK Manager.
I installed the available updates:
Android SDK Tools 22.0.1,
Android SDK Platform-Tools 17,
Android SDK Build Tools 17. After the install restarted Eclipse and then boom! My AVD was back and showing my newest changes. Hope this helps some one.
I recently updated to ADT r17. Ever since then, none of the android tools could see java on my system. I could not launch AVD Manager, SDK Manager, Draw-9patch, anything. The only way I could get an AVD to launch was to compile from eclipse without my phone plugged it. Java is still on my system, everything was working perfectly on r16. I can still go into the command line and type java and javac and everything works.
I uninstalled the sdk (by deleting the folder) and am attempting to reinstall it. The installer doesn't even see java. I tried clicking back and next again. No dice. I have in my system variables:
JAVA_HOME C:\Program Files\Java\jdk1.7.0_03\bin
I just did that one after the first failed attempt to reinstall since that's what is recommended on the installer. Did not help. What was working before was:
...F:\Development\Android\android-sdk\platform-tools;C:\Program Files\Java\jdk1.7.0_03\bin;...
I can confirm that at the end of the filepath, in the bin folder, java.exe and all it's other programs are there. I'm downloading the .zip sdk, but I don't think that's going to help much, since none of the tools seem to see java even when extracted. Edit: I can confirm, simply extracting the .zip did not help.
I'm on a 64bit system. Everything was working with r16. Any ideas? Should I go back to r16?
You can reference here: http://code.google.com/p/android/issues/detail?id=28196
I set JAVA_HOME=d:\jdk1.7\jre\ (which is my JDK's directory) to solve this problem.
For whatever reason, adt r17 decided it did not like 64bit Java, even though r16 was fine with it. Installed 32bit java and added that to my path. Everything is fine now.
I am going nuts.I update to the Android SDK in Eclipse, Eclipse can't find the SDK. There is a text not that saids the the file has been moved to /platform-tools, however the file ADB.exe is nowhere to be found in any of my folders. The SDK Manager works find but for some reason Eclipse will not find the file its looking for. I have looked everywhere for the answer. It work find for about 4 months until I upgraded. I also now using a real device a Droid X2. But I don't believe this is the issue. I can't find the ADB.exe file. Help been working on this for about 2 days
adb.exe was relocated from {ANDROID_SDK_FOLDER}/tools to {ANDROID_SDK_FOLDER}/platform-tools: find your SDK folder and look inside it for the platform-tools folder.
EDIT: in Eclipse, if you open the Preferences dialog (Window->Preferences) and select the Android option on the left it will show you what Eclipse THINKS is your Android SDK folder. If you moved the SDK folder you should update the path to match the new location of the SDK folder, and then (a restart might be necessary) Eclipse should work fine with the Android tools.
EDIT: well, I can't tell if your ADT isn't properly installed or if the SDK location is broken, so lets try and brute force set the SDK location. Create a text file on your desktop called "adt.pref", and then place only this line in it:
/instance/com.android.ide.eclipse.adt/com.android.ide.eclipse.adt.sdk=C\:\\Program Files\\Android\\android-sdk
then in Eclipse select File->Import then select General->Preferences and then pick that file. This should force the ADT location to match what that is. Restart Eclipse and see if that improves things.
I had the same problem and solved it by running the android sdk-manager (you can do that without running eclipse, using the start menu shortcut) and installing the Android SDK Platform-Tools through it (select the square and click install packages...).
Download the SDK here.
Once that's done, I would just follow the Google installation instructions again from the beginning. Perhaps you're missing something fairly simple?
Installation instructions.
I got the same problem. In my case it was caused by an upgrade on the Java JDK. I was using 1.6 and upgraded to 1.7.
Just manually add the new JDK to Eclipse.
Right click on your project JRE System Library. Select installed JRE, and then find it on your computer.
I had the same problem, and when I looked inside the platform-tools folder, it was empty.
After searching for downloading the contect of this folder, I found the below link.
http://venomvendor.blogspot.com/2012/06/android-adt-20-updated-download-offline.html
But it also could not help me.
At last I found that it's related to my internet connection.
I'm using Windows 7 and installed the 64 bit version of Eclipse 3.5.2. I then installed the Android ADT plugin, but when I try to configure it in the Windows > Preferences dialog, the Android Plugin doesn't show up in the left pane. Instead I see DDMS. This prevents me from specifying the location of the Android SDK (unless there is another way) to give me the appropriate templates and such.
Someone posted a fix to this that includes setting the permissions of Eclipse, but that didn't work for me. I tried installing the Android Plugin from both online installation (thru the URL install) and the offline Archive method.
If you're running Windows Vista or 7, make sure you right-click Eclipse and RUN AS ADMINISTRATOR. I literally spent six hours figuring this out, and this was what fixed it.
Dear people from the future:
I had roughly the same problem in linux, except that i didn't see anything at all but vanilla eclipse after installing. by combining both previous answers i got it to work:
start eclipse with sudo eclipse -clean, install the plugins and restart eclipse. the plugins showed up including the welcome screen that's supposed to be there.
after that it should work when running as regular user as well.
works for both the android sdk and the gwt sdk. (and probably other eclipse plugins)
Remove the plugin, then restart as follows:
eclipse -clean
Now try reinstalling the ADT from the online installation
For users having similar problem and not luck with other solutions:
I have windows XP but had same problem. I realized that I had JDK5/bin folder in my PATH environment variable (though my JDK_HOME was pointing to JDK6), as soon as I modified the PATH to replace bin of JDK5 with JDK6, the Android buttons on eclipse (after restart with -clean) along with Android option in Preferences & New Project showed up. (Weird eh!)
Also, consider to install the bundle android installation having eclipse with pre-configured Android SDK if a new eclipse installation doesn't matter to you
http://developer.android.com/sdk/installing/bundle.html
The above answers do not confront the heart of the problem. There is a feature in Windows 7 that prevents downloaded files from direct access of local files. All of the state is perfectly maintained in the Eclipse workspace instance. The problem is easily resolved by doing the following:
Find the "Eclipse" executable
Right-click on it.
Click "Properties".
Select the "General" tab.
Look for -> Security: "This file came from another computer and might be blocked..."
Click Unblock.
This is a much better solution than uninstalling and reinstalling the ADT or Eclipse which can be a pain.