- AlarmClock; BlockedNumberContract; BlockedNumberContract.BlockedNumbers; Browser; CalendarContract; CalendarContract.Attendees; CalendarContract.CalendarAlerts.
- The Android SDK provides you the API libraries and developer tools necessary to build, test, and debug apps for Android. If you're a new Android developer, we recommend you download the ADT Bundle to quickly start developing apps.
- Configure Android SDK Variable In Windows. 1.1 Get Android SDK Install Directory Path. Before you can configure it, you should first get the android sdk install directory follow below steps. Open android studio, click File — Settings menu item in the top men bar. Expand Appearance & Behavior — System Settings — Android SDK menu item.
Google is committed to advancing racial equity for Black communities. See how.
Android SDK is a toolset that enables developers to create and update different apps for Android devices. It gives mobile software developers the opportunity to manually fix, text, profile, debug.
This page provides release information about the SDK packages available for download from the SDK Manager, in the SDK Platforms tab.
Each SDK Platform version includes the following packages:
- The Android SDK Platform package. This is required to compile your app for that version.
- Several System Image packages. At least one of these is required to run that version on the Android Emulator. Each platform version includes a system image for each supported form factor (handsets, Android TV, and Android Wear). Each form factor may offer variations to match your computer's processor architecture (such as Intel x86 and ARM EABI). System images labeled Google APIs include access to Google Play services and those labeled Google Play also include Google Play Store.
- The Sources for Android package. This includes the source files for the platform. Android Studio may show lines of code from these files while you debug your app.
The revision numbers listed below are for the Android SDK Platformpackage only. The system images may receive separate updates, usually to resolvebugs with the emulator. There are no release notes for the system images, butyou should always keep them up to date.
Important: To see the most recent Androidsystem components in the Android SDK Manager, you must first updateSDK Tools to the most recentrelease and restart the SDK Manager.
Android 11 (API level 30)
For details about the platform changes, see the Android 11documentation.
Android 10 (API level 29)
For details about the platform changes, seeAndroid 10 for Developers.
Revision 5 (July 2020)
This revision adds Android Automotive OS stubs.
Android 9 (API level 28)
For details about the platform changes, seeAndroid 9 for developers.
Revision 1 (August 2018)
Released to stable channel (no longer in preview).
Android 8.1 (API level 27)
For details about the platform changes, seeAndroid 8.1 for developers.
Revision 1 (December 2017)
![Android Android](https://images.sftcdn.net/images/t_app-cover-l,f_auto/p/062a5f6a-9b32-11e6-80b3-00163ec9f5fa/1833504883/android-sdk-screenshot.jpg)
Released to stable channel (no longer in preview).
Android 8.0 (API level 26)
For details about the platform changes, seeAndroid 8.0 for developers.
Revision 2 (August 2017)
Released to stable channel (no longer in preview).
Android 7.1 (API level 25)
For details about the platform changes, seeAndroid 7.1 for developers.
Revision 3 (December 2016)
Incremental update. Released as the final Android 7.1.1 (no longer in preview).
Dependencies:
- Android SDK Platform-Tools 25.0.1 or higher is required.
- Android SDK Build-Tools 25.0.1 or higher is required.
Revision 2 (November 2016)
Incremental update. Released as Android 7.1.1 Developer Preview 2. For more information, see the Android 7.1 API Overview.
Dependencies:
- Android SDK Platform-Tools 25.0.1 or higher is required.
- Android SDK Build-Tools 25.0.1 or higher is required.
Revision 1 (October 2016)
Initial release for Android 7.1 (API level 25). Released as Android 7.1 Developer Preview 1. For more information, see the Android 7.1 API Overview.
Dependencies:
- Android SDK Platform-Tools 25.0.0 or higher is required.
- Android SDK Build-Tools 25.0.0 or higher is required.
Android 7.0 (API level 24)
For details about the platform changes, seeAndroid 7.0 for developers.
Revision 1 (August 2016)
Initial release for Android 7.0 (API level 24). For more information, see the Android 7.0 API Overview.
Dependencies:
- Android SDK Platform-tools r24 or higher is required.
- Android SDK Tools 24.0.0 or higher is required.
Android 6.0 (API level 23)
For details about the platform changes, see theAndroid 6.0 changes andAndroid 6.0 APIs.
Revision 2 (November 2015)
Fixed bugs in the layout rendering library used by Android Studio.
Dependencies:
- Android SDK Platform-tools r23 or higher is required.
- Android SDK Tools 24.3.4 or higher is required.
Revision 1 (August 2015)
Initial release for Android 6.0 (API level 23). For more information, see the Android 6.0 API Overview.
Dependencies:
- Android SDK Platform-tools r23 or higher is required.
- Android SDK Tools 24.3.4 or higher is required.
Android 5.1 (API level 22)
For details about the platform changes, see theLollipop overview andAndroid 5.1 API changes.
Revision 1 (March 2015)
Initial release for Android 5.1 (API level 22). For more information, see the Android 5.1 API Overview.
Dependencies:
- Android SDK Platform-tools r22 or higher is required.
- Android SDK Tools 23.0.5 or higher is required.
Android 5.0 (API level 21)
For details about the platform changes, see theLollipop overview andAndroid 5.0 API changes.
Revision 2 (December 2014)
Updated layouts in the Support Library and fixed various issues.
Dependencies:
- Android SDK Platform-tools r21 or higher is required.
- Android SDK Tools 23.0.5 or higher is required.
Revision 1 (October 2014)
Initial release for Android 5.0 (API level 21). For more information, see the Android 5.0 API Overview.
Dependencies:
- Android SDK Platform-tools r21 or higher is required.
- Android SDK Tools 23.0.5 or higher is required.
Android 4.4W (API level 20)
This version makes KitKat available for Android Wear.
Revision 2 (October 2014)
Updated the rendering library.
Dependencies:
- Android SDK Platform-tools r20 or higher is required.
- Android SDK Tools 23.0 or higher is required.
Revision 1 (June 2014)
Initial release for Android Wear.
Dependencies:
![Android sdk linux mint Android sdk linux mint](https://i.ytimg.com/vi/-OgYscP-bho/maxresdefault.jpg)
- Android SDK Platform-tools r20 or higher is required.
- Android SDK Tools 23.0 or higher is required.
Android 4.4 (API level 19)
For details about the platform changes, see theKitKat overview andAndroid 4.4 API changes.
Revision 2 (December 2013)
Maintenance release. The system version is 4.4.2. For more information, see the Android 4.4 API Overview.
- Dependencies:
- Android SDK Platform-tools r19 or higher is required.
- Android SDK Tools 22.3 or higher is recommended.
Revision 1 (October 2013)
Initial release. The system version is 4.4. For more information, see the Android 4.4 API Overview.
- Dependencies:
- Android SDK Platform-tools r19 or higher is required.
- Android SDK Tools 22.3 or higher is recommended.
Android 4.3 (API level 18)
For details about the platform changes, see theJelly Bean overview andAndroid 4.3 API changes.
Revision 2 (August 2013)
Maintenance update. The system version is 4.3.
- Dependencies:
- Android SDK Platform-tools r18 or higher is required.
- Android SDK Tools 22.0.4 or higher is recommended.
Revision 1 (July 2013)
Initial release. The system version is 4.3.
- Dependencies:
- Android SDK Platform-tools r18 or higher is required.
- Android SDK Tools 22.0.4 or higher is recommended.
Android 4.2 (API level 17)
For details about the platform changes, see theJelly Bean overview andAndroid 4.2 API changes.
Revision 2 (February 2013)
Maintenance update. The system version is 4.2.2.
- Dependencies:
- SDK Tools r21 or higher is required.
Revision 1 (November 2012)
Initial release. The system version is 4.2.
- Dependencies:
- SDK Tools r20 or higher is required.
Android 4.1 (API level 16)
For details about the platform changes, see theJelly Bean overview andAndroid 4.1 API changes.
Revision 3 (October 2012)
Maintenance update. The system version is 4.1.2.
- Dependencies:
- SDK Tools r20 or higher is required.
Revision 2 (July 2012)
Maintenance update. The system version is 4.1.1.
- Dependencies:
- SDK Tools r20 or higher is required.
Revision 1 (June 2012)
Initial release. The system version is 4.1.0.
- Dependencies:
- SDK Tools r20 or higher is required.
Android 4.0.3 (API level 15)
Revision 3 (March 2012)
Maintenance update. The system version is 4.0.4.
Note: This system image includes support for emulatorhardware graphics acceleration when used with SDK Tools r17 or higher.(more info)
- Dependencies:
- SDK Tools r17 or higher is required.
Revision 2 (January 2012)
Maintenance update. The system version is 4.0.3.
- Dependencies:
- SDK Tools r14 or higher is required.
Revision 1 (December 2011)
Initial release. The system version is 4.0.3.
- Dependencies:
- SDK Tools r14 or higher is required.
Android 4.0 (API level 14)
Android 4.0, Revision 2 (December 2011)
Maintenance update. The system version is 4.0.2.
- Dependencies:
- SDK Tools r14 or higher is required.
Android 4.0, Revision 1 (October 2011)
Initial release. The system version is 4.0.1.
- Dependencies:
- SDK Tools r14 or higher is required.
Android 3.2 (API level 13)
Android 3.2, Revision 1 (July 2011)
- Initial release. SDK Tools r12 or higher is recommended.
Android 3.1 (API level 12)
Android 3.1, Revision 3 (July 2011)
Requires SDK Tools r12 orhigher.
Improvements to the platform's rendering library to support the visual layout editor in the ADTEclipse plugin. This revision allows for more drawing features in ADT and fixes severalbugs in the previous rendering library. It also unlocks several editor features that were added inADT 12.
Android 3.1, Revision 2 (May 2011)
Requires SDK Tools r11 orhigher.
Fixes an issue with the visual layout editor rendering library that prevented Android 3.1 fromrunning in ADT.
Android 3.1, Revision 1 (May 2011)
Requires SDK Tools r11 orhigher.
Android 3.0 (API level 11)
Android 3.0, Revision 2 (July 2011)
Requires SDK Tools r12 orhigher.
Improvements to the platform's rendering library to support the visual layout editor in the ADTEclipse plugin. This revision allows for more drawing features in ADT and fixes severalbugs in the previous rendering library. It also unlocks several editor features that were added inADT 12.
Android 3.0, Revision 1 (February 2011)
Requires SDK Tools r10 or higher.
Android 2.3.3 (API level 10)
How To Install Android Sdk
Android 2.3.3, Revision 2 (July 2011)
Android Sdk Linux Mint
Requires SDK Tools r12 orhigher.
Improvements to the platform's rendering library to support the visual layout editor in the ADTEclipse plugin. This revision allows for more drawing features in ADT and fixes severalbugs in the previous rendering library. It also unlocks several editor features that were added inADT 12.
Android 2.3.3, Revision 1 (February 2011)
Requires SDK Tools r9 or higher.
Android 2.3 (API level 9)
Android 2.3, Revision 1 (December 2010)
Requires SDK Tools r8 or higher.
I’ve got at least two concepts for Android apps running around in my head, notebooks & text files at the moment. Being a web developer for some years now, and having developed a Windows app or two, I figured I would be able to start prototyping these concepts for Android without too much hassle.
So far, the hardest and most frustrating part of this process has been installing the SDK. Part of the hassle I’ve had is that most online resources only explain the steps required for users of Eclipse (which automates a bit of it for you). The most frustrating bit was forum answers which simply told you to install Eclipse to fix whatever code-related problem the asker was having.
I want to avoid Eclipse, for two main reasons:
- Eclipse is nasty to use, convoluted resource-hog. It’s slower than a wet week on my Mac, plus it hasn’t functioned as it should when I’ve attempted to use it in the past (and man, that interface is yuck).
- See reason 1.
The other hassles I’ve had is with the lack of accurate documentation. The resources I’ve been reading have overlooked some vital steps in the process of installing the SDK and getting your first app up and running.
Download Android Sdk Linux
I’m going to explain the steps I took to install the latest version of the Android SDK on my Mac OS X 10.7, plus the extra steps needed to get my first app working. These instructions are based on the official developer.android.com instructions on “Building Your First App“, but instead of any IDE I’ll be using the command line and TextWrangler.
The first step is to download the SDK. I opted to download the non-bundle version (under the heading “Use an existing IDE”). Open this and extract it. I chose to locate it in the directory /Android/ (in the root of my main hard drive). I will be referring to this path from now on. If you want to save it elsewhere, please translate that path in your head.
Next, go to /Android/tools/ and run the android file. It will open up a Terminal window, and then launch a GUI. This is the Android SDK Manager, and it is how you obtain the latest copy of the SDK, as well as extra tools and libraries you may need. I opted to download the entire “Tools” folder, the entire folder of the latest SDK (Android 4.2 – SDK 17), and the Android Support Library (under “Extras”).
The next step is to install Apache ANT. ANT is used to automate the build process, and is necessary for most users. You could build manually, but the ANT tool will save you a lot of time. This step was left out of the guides I read, and caused some confusion when it came time to build. Download the binary, and extract it. I then created the folder /Android/ant/ and copied the entire bin and lib folders into there.
The next step is to add ANT’s bin folder to PATH. This is a system-wide variable used by the operating system to allow you to directly open the contents of a folder without needing to specify it’s full folder path. As an example, I could type /Android/ant/bin/ant into the command line, or I could just type ant – they both do the same thing.
On Mac OS X, you add a folder to the PATH variable by running this command in Terminal:
- PATH=$PATH:/Android/ant/
Android Sdk Download
The manual also says you should add the environmental variable ANT_HOME and set it to the main ANT folder (/Android/ant/), but I didn’t do this and haven’t had any issues yet.
Check you’ve installed it correctly by typing ant into Terminal and looking for this output: “Buildfile: build.xml does not exist! Build failed”
You also need to add the /Android/platform-tools/ and /Android/tools/ folders to the path variable. Execute these commands one at a time:
- PATH=$PATH:/Android/platform-tools/
- PATH=$PATH:/Android/tools/
You are now ready to create, build, and run a bare bones app. The official instructions are fine here, so read the pages “Creating an Android Project“, “Running and Application“, and “Building a Simple User Interface“.
Tip about emulators: If your computer isn’t loaded up with a whole heap of CPU power, try create a virtual Android device with a smaller resolution and DPI. I’m running a 5.1″ WVGA 480 x 800 device on my several year old MacBook just fine, where as the higher res and DPI devices would take a long, long time to load and sometimes crash.
Tip about Reinstalling: The process where you install an app into the emulator doesn’t like it if you already have an older copy of that app installed. I have been manually deleting it each time by holding down the mouse on the icon and dragging it towards the “Uninstall” icon which appears. There is probably a way to automate this, but I haven’t found it yet.
The last page where you create another Activity lacks a few instructions. You need to manually add some imports to the top of your Java files before they will compile. These are listed in the instructions, except for one: import android.support.v4.app.NavUtils;
This last one tripped me up a bit, as I hadn’t installed the Android Support Library at the start. As you did, you shouldn’t have issues with this triggering a compile error.
By now you should have be able to run your app in the emulator and create a new view. For me, this whole process was incredibly painful and took well over an hour to figure out. Writing it all down, it does seem a lot easier than it felt at the time, but I suppose hindsight is 20/20. With any luck, my publication of these tips has helped you.
Also, stay tuned for information about our upcoming Android products.