I currently have Android SDK Platform-tools 14 installed. (Edit: Seems to be the current version)
Since this has a bug that makes Logcat unusable and it seems to be fixed in newer versions, Id like to update it.
How can this be done?
SDK Mangager.exe does not find a newer version than 14. I restarted it multiple times and installed all available updates.
The android page says the current version is 20 but they don't provide a download.
Installing the latest SDK starter package doesn't solve it.
Screenshot:
The Google page is talking about the tools not for platform tools.Actually there are two different folders in SDK one is tools and one is platform-tools so as per the latest release there latest version is
for platform-tools :platform Tools
for tools :Tools
so if you are having problem just download the zip and replace the old one with new one installed.
if you are getting problem with the new catlog use the old one (LogCat-Deprecated).
Launch standalone SDK manager and not from Eclipse. It then should fetch list of available packages and offer you to update all old packages, as your ADT v14 is quite ancient.
Alternatively, if everything else fail, you always can fetch ADT by hand from http://tools.android.com, unpack tools to your , replacing old stuff and then installing Eclipse plugin. Please note you need to download both and install as latest version will not work with outdated packages.
Related
I wish to use an older version of the ADT plugin for Eclipse, which I found a download link for HERE.
How can I install this within Eclipse, and do I need to uninstall the ADT Plugin that I currently have?
Also, Do I need to use a specific SDK to work with this older ADT version?
1 - Create your download url: http://dl.google.com/android/ADT-##.#.#.zip. Google uses the version number for the downloads, so if you need 10.0.1, your download would be http://dl.google.com/android/ADT-10.0.1.zip.
2 - Uninstall the current ADT version in Eclipse.
3 - Install the new version as an archive!
When creating a new android project, the target SDK does not show above 18. I have gone into the Android SDK Manager and updated everything up to version 21. Now when I start eclipse it comes up with the error "The Android SDK requires Android Developer Toolkit version 23.0.o0 or above. Current version is 22.3.0. Please update ADT to the latest version.".
So I check for updates and then it tells me there are no updates found. Has anyone else had this problem and know why possibly it finds no updates when it is specifying one needs to be made?
Also, I tried this link, This Android SDK requires ADT version 23.0.0 or above. Current version is 22.6. Please update ADT to the latest version?. The below gets me to install 23.0.0 but I keep getting dependency errors. There is a comment to uninstall the 22.3.0 versions but if I take that route it completely uninstalls eclipse as well. Text from that article below:
"You can also update the ADT plugin
Select Help > Install New Software
Work with: p2repo - https://dl-ssl.google.com/android/eclipse/
Select Developer Tools and Next
Next, Accept the license agreement* and Finish"
UPDATE: The quickest resolution I found to this, to at least be able to start a new project and target the newer SDKs, was to just download the newest Android SDK bundle. This downloaded all of the latest that I needed.
There can be many issue.Did you restart you eclipse.If not,try it.Your eclipse may be outdated.Eclipse should be kepler or mars or Your ADT didn't properly updated.So you have to update again from where it was.
I made a stupid mistake by upgrading my SDK version to r15 as the android repository was not loading. How do I revert back to my older version r10?
Or is sticking with the newer version better? I'll have to upgrade my ADT Plugin as well then.
Thanks a lot.
Anyway, for those who want to downgrade Android SDK Tools to a previous version, it can be possible following these steps:
Find your Android SDK folder
Locate the "tools" subfolder and rename it to "tools1" (just to keep a backup copy of the original tools folder)
Likewise, rename platform-tools to platform-tools1
Download from google repository the SDK Tool version you want to downgrade to (for instance: http://dl-ssl.google.com/android/repository/tools_r22.6.2-macosx.zip) and unpack it.
The ZIP file you downloaded contains a tools folder that has to be moved to your Android SDK folder.
Likewise, download the platform tools (for instance: http://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-macosx.zip), and extract it in your SDK folder.
That's it.
I want to follow up on the great answer provided by Ariel Iriarte, step 3 (Download from google repository the SDK Tool version you want to downgrade to).
To find the old tools, you need to determine the SDK version number that you want to revert to. On the Google Android SDK webpage, you will find a Revisions list that shows all the SDK numbers, e.g.
SDK Tools, Revision 22.6.2 (March 2014)
SDK Tools, Revision 22.3 (October 2013)
etc.
Make a note of the exact revision number, like "22.3".
Now download the tools by using the following pattern:
http://dl-ssl.google.com/android/repository/tools_rXXX-windows.zip
http://dl-ssl.google.com/android/repository/tools_rXXX-linux.zip
http://dl-ssl.google.com/android/repository/tools_rXXX-macosx.zip
where you must replace XXX with the exact revision number noted above. For example, to download revision 22.0.5 for Mac OS X, download the file:
http://dl-ssl.google.com/android/repository/tools_r22.0.5-macosx.zip
Once you download the file and unzip it, you will find a single folder called 'tools'. Now follow the answer by Ariel Iriarte and replace your android-sdk/tools folder with this new one. This is the folder that contains stuff like:
NOTICE.txt
adb_has_moved.txt
android
ant
apps
ddms
dmtracedump
etc.
Some of you probably found this thread due to the unstable versions of Android-Tools pushed (exclusively) since the stable 22.3 version. This causes a 'hang' in the emulator on the "Android Animation / Splash Screen" in Intel API's pre Version 19, and a "floating point exception" for Intel API-19. The ARM versions still work, though more slowly on Intel machines using acceleration.
To answer the questions of "how to find the older versions not listed in the GUI" - or present in the current xml which feeds it (https://dl-ssl.google.com/android/repository/repository-8.xml), in the comments above, I have no idea how they can be located (please enlighten me).
Fortunately, someone reporting the bug did post a direct link to the Linux and Windows versions of the stable 22.3 version in this thread:
https://code.google.com/p/android/issues/detail?id=66786
... which are:
http://dl.google.com/android/android-sdk_r22.3-linux.tgz
http://dl.google.com/android/android-sdk_r22.3-windows.zip
These also exist in unofficial locations on the web, should those get pulled down, along with the now-gone references to them.
After extracting that archive, you will have the "Tools" folder you need to replace the broken one, as per Ariel Iriarte's instructions above (though I renamed the existing 'Tools' folder something involving the letter 'f' - days into this problem).
In order to prevent this problem from re-occuring, do NOT count on the built-in method in Eclipse / Android-SDK to revert to a previous installation, nor for the older-versions of any file provided by Google to be available At All, Ever, in the future. Backup your entire 'android-sdks' tree prior to installing anything.
You can install multiple SDKs, and set the default SDK by editing the properties on the Android project.
The simple solution is :
1- Go to your graddle-wrapper.properties then change this line as you desire :
distributionUrl=https://services.gradle.org/distributions/gradle-4.4-all.zip
2- Go to File>Project Structure>Project then Change both Gradle version and Gradle Plugin Version
3- then Sync your Project
Done.
I have successfully installed Level 13 (3.2) during the Android SDK installation, but chose not to include any earlier levels at that time.
I now would like to install 2.2 or 2.3, but in the SDK / AVD manager I get the message:-
Failed to fetch URL
https://dl-ssl.google.com/android/repository/addons_list.xml, reason:
File not found
I've looked this up in other posts and so run the SDK manager with Administrator permissions, and have turned off the firewall. Eventually, it comes back with SDK tools revision 15, and SDK PLatform tools revision 9 only.
Should I have installed earlier packages during setup?
Would an uninstall / reinstall cure this behaviour? (Reluctant to do
this :-( for obvious reasons)
Is it possible to get earlier levels having installed just level 13?
Any help would be greatly appreciated. Thanks for looking.
Old Android SDK tool (r13 and earlier) fetch/download available SDK from here repository, after google release r14 and r15, they remove all SDK verion and only leave r15 in this URL, that means they want you use the latest SDK tool r15.
New Andorid SDK tool (r14 and r15) fetch/download available SDK from a new URL repository-5, which contains everything downloadable.
If you are not using anything else like Maven (currently incompatible with latest ADT) with your project, the simplest answer is upgrade both your Android SDK tools and ADT Eclipse plugin.
I just setted up my android environment yesterday - try to download the package manually and load them as Archive files, this worked for me! ;)
Owing to problems with the upgrade to SDK2.3, I now need to back out to an earlier version. Fortunately I had saved a cutdown version of SDK 2.1 which would allow me to continue development. However I upgraded my Eclipse pluigin to 8.0.0, which expects a 2.3 SDK environment. Eclipse now complains that it's now missing the new platform-tools folder when I point the SDK location to the old 2.1 version and won't allow me to compile.
I need to uninstall the 8.0.0 plugin and replace it with 0.9.9 but there is no option to download it on the can't find it on the developer.android pages.
Found it!
Although it's not visible on the site, typing
http://dl.google.com/android/ADT-0.9.9.zip
into the browser lets you download the thing. I've finally managed to back out to where I was 2 days ago before 'upgrading' to SDK2.3