Sdk android для android studio


Android Studio – как изменить путь к SDK Android Oh! Android

Панкадж кумар said:

Из Android Studio 1.0.1

Идти к

  1. Файл -> Структура проекта в структуре проекта
  2. Слева -> местоположение SDK
  3. Местоположение SDK выбирает местоположение Android SDK (использование старой версии Нажмите +, добавьте еще один SDK)

JosephN said:

Для проектов по умолчанию:

1. Закрыть текущий проект (Файл-> Закрыть проект)

Вы получите приветствие в диалоговом окне Android Studio. В этом:

2. Нажмите «Настроить» -> «По умолчанию проекта» -> «Структура проекта»

3. Нажмите «Расположение SDK» в левой колонке

4. Поместите путь к Android SDK в поле «Android SDK location».

( Пример расположения SDK : C:\android-sdk ; У меня есть подпапки, такие как add-ons , platforms т. Д. Под C:\android-sdk )

5. Нажмите «ОК», чтобы сохранить изменения.

6. Получайте удовольствие!

Следующие шаги были для более старых версий (<1.0) Android Studio

4. В среднем столбце Нажмите на Android SDK (с Android-значком) или нажмите + вверху, если вы не видите запись с значком Android.

5. Измените основной путь SDK и выберите действительную целевую

Dira said:

В окне быстрого запуска выберите «Настроить», затем выберите «По умолчанию по умолчанию», а затем «Структура проекта». Затем слева в разделе «Настройки платформы» выберите SDK. Затем справа от него выберите текущую платформу для Android, моя платформа Android 4.2.2 и удалите ее с помощью красной кнопки «минус» вверху, затем добавьте новую платформу для Android с помощью кнопки «зеленый плюс» наверху и укажите ее на Ваша текущая папка SDK и все.

bersen said:

Я настроен таким образом

на

Добро пожаловать на Android Studio Screen

Нажмите « Настроить»

Значения по умолчанию проекта, а затем структура проекта

Затем Android SDK и выберите путь к моему текущему местоположению Android SDK

SanketSB said:

Изменение местоположения sdk в настройках проекта частично устранит проблему. Когда Android Studio используется для загрузки нового SDK, он поместит новый SDK во внутреннюю папку SDK (внутри Android Studio).

Существующие разработчики Android уже будут иметь большую папку sdks (далее называемую внешней папкой SDK), содержащую все SDK, загруженные до появления Android Studio.

Для пользователей Mac / Linux, хотя есть хороший выход. Мягкие ссылки!

Выйдите из Android Studio и выполните следующие действия:

cp -r <Android Studio>/sdk/ <external SDK folder>/ cd <Android Studio>/ mv <Android Studio>/sdk/ mv <Android Studio>/sdk.orig ln -s <external SDK folder>/ sdk

И нам хорошо идти. Запустите SDK Manager после запуска Android Studio, следите за тем, как он обнаруживает все ваши существующие SDK как шарм :).

SanketSB said:

Вот как вы можете изменить путь sdk для Android в студии Android:

  1. Откройте требуемый проект Android в студии Android
  2. Нажмите на основную папку проекта и нажмите F4
  3. Теперь нажмите «SDK» в разделе «Настройки платформы» (в левой части диалогового окна)
  4. Теперь вы должны увидеть знак плюса сверху, нажмите его и выберите «Android SDK»,
  5. Теперь вас попросят выбрать нужную папку SDK
  6. Выберите требуемую цель сборки (если необходимо) и нажмите «ok»
  7. Теперь вы должны увидеть новую запись в списке SDK
  8. Нажмите «Модули» в разделе «Настройки проекта»
  9. Выберите папку проекта и в раскрывающемся списке «Модуль SDK», выберите новую запись SDK и нажмите «применить»,
  10. Теперь нажмите «ОК» и сделайте все.

Примечание. Если изменения не вступят в силу, перезапуск студии Android должен устранить проблему.

vbence said:

EUREKA Я ​​нашел это!

С текущей Studio 1.3 каждый проект имеет файл local.properties где вы можете редактировать SDK!

oceanfeeling said:

Сделайте вашу жизнь легкой с помощью сочетаний клавиш ctrl+shift+alt+S или

Перейдя в файл-> структуру проекта:

Он откроет это окно, где вы можете выбрать свой SDK

Дурга Мохан said:

Я заметил, что в последней версии Android Studio отсутствует опция «SDK», упомянутая во многих ответах. Я предполагаю, что исчез в одном из обновлений, где-то в очереди?

Как я решил эту проблему (osx):

  1. Перейдите в Настройки проекта ( Cmd +; )
  2. В местоположении SDK убедитесь, что вы указываете правильное местоположение SDK (обычно / Приложения / Android Studio.app/sdk), а затем нажмите Apply
  3. Самый важный шаг – нажмите «Sync Project with Gradle files»

Я не делал Шаг 3, и это меня отбрасывало. После синхронизации все ваши источники r принадлежат нам ….

Абдул Манан said:

Вы также можете создать переменную окружения (в Windows) ANDROID_HOME для местоположения Android SDK, и Android Studio будет использовать это.

raudi said:

Выше ответы довольно верны, но в некоторых случаях Android Studio не любит обновляться после изменения пути к SDK, быстрое решение заключается в том, чтобы внести некоторые изменения в ваш файл сборки и нажать «Синхронизация». Он обновит ваш проект.

Счастливое кодирование … 🙂

Адитья Гайкар said:

В окнах нажмите ctrl + shift + alt + s, который откроет свойства проекта, где вы можете найти первый вариант с именем SDK Location, нажмите на него, и там вы можете изменить путь к SDK, путь JDK и путь NDK

crossle said:

Во время первой установки Есть две ситуации, которые вы предварительно предустановили Android SDK, если вы использовали ее в прошлом или у вас ничего нет. Во время установки установщик всегда спрашивает у пользователя, как вы хотите настроить SDK в своей студии.

Вы можете просто указать путь сюда или просмотреть папку, где sdk доступен в локальной системе. Если у вас уже есть SDK, другой вариант, как показано на рисунке ниже в левом нижнем углу, есть хороший вариант для загрузки SDK , щелкнув его, вы можете скачать SDK с последним выпуском прямо оттуда, вы также можете использовать третий вариант в правом нижнем углу Угловая настройка Android SDK для меня , нажав на нее, вы можете шаг за шагом установить свой sdk.

Хотя вы также можете настроить его, когда Android показывает список доступных проектов, окно с приглашением запуска показано ниже

Это довольно просто, и когда-нибудь, если вы хотите изменить свой SDK, вы всегда можете изменить его прямо в своей студии Android от

В системе Windows File -> Project Structure, а затем вы увидите вариант определения SDK и оттуда вы можете настроить его, указав путь или просмотрев его.

Или, если вы находитесь в системе MAC, то из настроек платформы.

Ana 01 said:

Попробуйте этот способ, я попробую в Android Studio 2.0. Шаг 1: Файл-> Настройка Шаг 2: Вариант Seting-> SDK. Шаг 3: Нажмите «Изменить» в Sdk Location. Шаг 4: Показать «Настройка компонентов SDK» Шаг 5: Нажмите «Три». .. "в" SDK Components Wizad "Шаг 6: Выберите новый путь SDK

Адитья Гайкар said:

Возможно, это не то, что вы хотите, но, будучи пользователем eclipse, у меня была та же проблема с дублирующимися папками sdk, которые ест все пространство ssd. В настоящее время вы можете изменить только путь sdk внутри проекта студии Android, что раздражает. Вместо этого я скопировал все предыдущие файлы sdk для Android, которые я использовал с eclipse в /Android Studio/sdk/ а затем просто изменил путь sdk внутри eclipse.

Теперь и андроидская студия, и eclipse довольны.

Dira said:

  1. Tap -> file -> закрыть текущий проект.

У вас будет домашняя страница Android Studio

  1. Нажмите «Настройка» -> «По умолчанию проекта» -> «Структура проекта»

  2. Нажмите «Расположение SDK» в левом столбце и скопируйте путь.

  3. Вставьте путь в «Мой компьютер» -> «Щелчок правой кнопкой мыши» -> «Свойства» -> щелкните «Дополнительные параметры системы» -> «Переменные среды» и измените домашний путь Android.

  4. Нажмите «ОК», чтобы сохранить сеанс.

  5. Добавьте инструменты и платформы в путь и сохраните изменения.

  6. Откройте командную строку [window + R] и введите adb + enter.

Dira said:

  1. Нажмите меню « File .
  2. Выберите Project Structure .
  3. Отредактируйте путь в текстовом поле « SDK Location . В следующий раз Android Studio будет использовать это местоположение для всех ваших проектов.

NB: Избегайте наличия пробелов в пути, поскольку это может иногда приводить к проблемам.

RobbyPatel said:

В Android Studio 2.2.3 я думаю, что вы можете изменить местоположение SDK по умолчанию для всех проектов из верхнего меню:

Файл -> Другие настройки -> Структура проекта по умолчанию …

Появится следующее окно:

mayank_io said:

Спасибо, DheeB, действительно! Но мое решение заключается в том, чтобы связать каталог SDK android с андроидной студией: ln -s <FULL_PATH_TO_ANDROID_SDK> <PATH_TO_ANDROID_STUDIO>/sdk И, конечно, заранее, на всякий случай, вам нужно двигаться mv <PATH_TO_ANDROID_STUDIO>/sdk to <PATH_TO_ANDROID_STUDIO>/sdk_orig Кроме того, мне пришлось исправить файл build.gradle проекта и указать classpath 'com.android.tools.build:gradle:0.6.+' (Вместо 0,5. +)

Для гуру said:

У меня была та же проблема, но с пути sdk, указывающим на смонтированный диск. Я обнаружил, что просто закройте Android Studio, отключите устройство и перезапустите Android Studio, попросив у него местоположение sdk, потому что у него не было (Android Studio Beta 0.8.7).

Поэтому я думаю, что если вы просто закроете Android Studio, удалите \ android-studio \ sdk или переместите его в другое место и снова запустите Android Studio, он также попросит указать местоположение sdk.

SanketSB said:

Хотя многие из приведенных выше ответов служат этой цели, есть одна прямая вещь, которую мы можем сделать в самом проекте.

В Eclipse перейдите в Window-> Preferences, выберите «Android» в меню слева. На правой панели вы увидите «Местоположение SDK». Укажите путь здесь.

Удачи.

Abhijeet said:

В Android-студии 1.2.2 вы можете просто изменить SDK на основе проектов, Шаги:

  1. Щелкните правой кнопкой мыши на модуле и выберите параметр «Открыть модуль» или нажмите F12
  2. Выберите местоположение SDK с левой стороны
  3. Теперь вы можете изменить местоположение SDK, а также местоположение JDK с этой страницы

Для гуру said:

В Android Studio вы можете установить общий путь Android SDK в файле:% Home% .AndroidStudio2.1 \ config \ options \ jdk.table.xml

oceanfeeling said:

Вот как это делается, в Android Studio для окон

Готово

Sumeta Pongpanna said:

Android Studio придирчива к расположению SDK, если вы заметили, когда вы впервые нажмете кнопку обзора, по умолчанию она поместится в ваш домашний каталог, закройте sdk и используйте его, тогда ваш проект должен найти sdk без проблем.

ohandroid.com

Android SDK Manager

Android SDK Manager – это среда для разработки приложений под операционную систему Android. Эта программа позволяет создавать приложения, которые используют возможности камеры, Wi-Fi, Bluetooth, данных GPS, 3G. Также Android SDK Manager поддерживает работу с браузерами, различными форматами видео и аудио. Популярность программа получила благодаря встроенному модулю, который позволяет тестировать разработанные приложения на различных версиях Android.

Читайте также: Программа Zona для Android

Как установить Android SDK Manager?

Для того, чтобы начать использовать программу Android SDK Manager, нужно изначально её установить. Для этого выполняем следующее:

  • Скачиваем архив SDK Manager на своё устройство.
  • Параллельно запускаем установку самой последней версии Java Development Kid на свой ПК и следуем инструкциям.
  • Из архива запускаем распаковку файла «SDK Manager».
  • Если распаковать не удалось, стоит создать на диске C папку «Android» и распаковать через Total Commander все файлы с архива.
  • Далее запускаем файл «SDK Manager.exe». В течение нескольких секунд появится рабочее оно программы.
  • Однако работать с программой ещё нельзя. Нужно установить Eclipse. Она есть в архиве.
  • Из Total Commander установить этот элемент не получится. Нужно на диске С в папке «Android» создать новую папку с названием «Workspace» и поместить все содержимое папки.
  • Далее нужно обновить саму программу. Для этого в меню нажимаем «Deselect All», чтобы не устанавливать все версии Android.
  • Теперь станет активной кнопка «Update». Отмечаем версию своей ОС Android. И нажимаем «Install».
  • В новом окне ставим отметку «Accept License» и нажимаем «Install».
  • Ждём завершения установки Android SDK Manager.

Также о том, как установить и настроить программу можно узнать из видео:

Как правильно установить Eclipse для SDK Manager и программу Android Studio?

Часто в пользователей возникают проблемы с установкой компонента Eclipse. Зачастую он идет в комплекте с программой Android SDK Manager. Однако его можно отдельно скачать с сайта разработчика, предварительно выбрав версию и разрядность Windows.

Установка данного элемента следующая:

  • Скачиваем и распаковываем архив в папку Windows, что на диске С.

Важно! Известна проблема с распаковкой архива Eclipse. Рекомендуем для этой цели использовать программу 7-Zip или WinRAR. До начала распаковки архива нужно установит Java.

  • Если извлечь в указанную папку не удалось, некоторые опытные пользователи отмечают успех выполнения действия, в случае выбора папки «Program File (х86)».
  • Далее запускаем файл exe.

Однако этот метод не всегда работает и часто возникают ошибки.

Учитывая отзывы пользователей программы и их рекомендации, предлагаем ознакомиться с 100% способом установки Eclipse:

  • Вводим в Google запрос «Java SE Runtime». Открываем первую ссылку.
  • Выбираем последнюю версию программы в соответствии с разрядностью системы.
  • Начнётся загрузка архива. Возвращаемся назад к поисковику и вводим «Android SDK». Вновь выбираем первую ссылку.
  • Открываем страницу и опускаемся вниз к разделу «SDK Tools». Здесь выбираем «Includes Android SDK»
  • Принимаем условия лицензионного соглашения и жмём «Скачать».
  • Файл будет весить более 1,2 Гб. Поэтому пока будет скачиваться файл, устанавливаем Java.
  • Теперь устанавливаем Android Studio. На диске С понадобиться до 4,5 Гб свободной памяти.
  • Отмечаем нужные элементы.
  • Принимаем условия лицензионного соглашения и жмём «Установить».
  • Нужно выбрать тип установки. Выбираем «Стандартную».
  • Установка программы завершена.
  • Теперь без проблем можно установить Eclipse IDE for Java Development. Запускаем файл .exe с архива. Программа сама создаст нужную папку. Просто следуем инструкции.
  • Программа успешно установлена.

Важно! Eclipse можно установить только при соблюдении вышеуказанных рекомендаций. В противном случае появится ошибка sdk tools directory is missing.

Что делать, если появляется ошибка SDK tools directory is missing?

С ошибкой sdk tools directory is missing мы столкнулись во время установки Android Studio. Возникла она из-за неустановленного компонента Eclipse. Поэтому, если вы пытаетесь установить программу до инсталляции Java и Eclipce, будьте готовы столкнуться с этой проблемой.

Также эта проблема может возникнуть при сохранении проекта. В этом случае в меню программы нужно нажать «Configure», «Project Defaults», «Project Structure» и скопировать правильный адрес C:/Users/user/AppData/Local/android/SDK.

Далее повторяем попытку сохранить проект.

В первом же случае, когда ошибка возникла при установке программы, это значит, что отсутствует папка «Tools». Стоит удалить программу полностью, освободить до 5 Гб памяти и по новому выполнить установку программы по инструкции для Eclipse.

softikbox.com

SDK Platform Tools Release Notes

Before downloading, you must agree to the following terms and conditions.

Terms and Conditions

This is the Android Software Development Kit License Agreement

1. Introduction

1.1 The Android Software Development Kit (referred to in the License Agreement as the "SDK" and specifically including the Android system files, packaged APIs, and Google APIs add-ons) is licensed to you subject to the terms of the License Agreement. The License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK. 1.2 "Android" means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL: http://source.android.com/, as updated from time to time. 1.3 A "compatible implementation" means any Android device that (i) complies with the Android Compatibility Definition document, which can be found at the Android compatibility website (http://source.android.com/compatibility) and which may be updated from time to time; and (ii) successfully passes the Android Compatibility Test Suite (CTS). 1.4 "Google" means Google LLC, a Delaware corporation with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States.

2. Accepting this License Agreement

2.1 In order to use the SDK, you must first agree to the License Agreement. You may not use the SDK if you do not accept the License Agreement. 2.2 By clicking to accept, you hereby agree to the terms of the License Agreement. 2.3 You may not use the SDK and may not accept the License Agreement if you are a person barred from receiving the SDK under the laws of the United States or other countries, including the country in which you are resident or from which you use the SDK. 2.4 If you are agreeing to be bound by the License Agreement on behalf of your employer or other entity, you represent and warrant that you have full legal authority to bind your employer or such entity to the License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity.

3. SDK License from Google

3.1 Subject to the terms of the License Agreement, Google grants you a limited, worldwide, royalty-free, non-assignable, non-exclusive, and non-sublicensable license to use the SDK solely to develop applications for compatible implementations of Android. 3.2 You may not use this SDK to develop applications for other platforms (including non-compatible implementations of Android) or to develop another SDK. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose. 3.3 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you. 3.4 You may not use the SDK for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK. 3.5 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software license and not the License Agreement. 3.6 You agree that the form and nature of the SDK that Google provides may change without prior notice to you and that future versions of the SDK may be incompatible with applications developed on previous versions of the SDK. You agree that Google may stop (permanently or temporarily) providing the SDK (or any features within the SDK) to you or to users generally at Google's sole discretion, without prior notice to you. 3.7 Nothing in the License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features. 3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the SDK.

4. Use of the SDK by You

4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under the License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications. 4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) the License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries). 4.3 You agree that if you use the SDK to develop applications for general public users, you will protect the privacy and legal rights of those users. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so. 4.4 You agree that you will not engage in any activity with the SDK, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of any third party including, but not limited to, Google or any mobile communications carrier. 4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so. 4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under the License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach.

5. Your Developer Credentials

5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials.

6. Privacy and Information

6.1 In order to continually innovate and improve the SDK, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the SDK are being used and how they are being used. Before any of this information is collected, the SDK will notify you and seek your consent. If you withhold consent, the information will not be collected. 6.2 The data collected is examined in the aggregate to improve the SDK and is maintained in accordance with Google's Privacy Policy.

7. Third Party Applications

7.1 If you use the SDK to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources. 7.2 You should be aware the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners. 7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party. In that case, the License Agreement does not affect your legal relationship with these third parties.

8. Using Android APIs

8.1 Google Data APIs 8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service. 8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so.

9. Terminating this License Agreement

9.1 The License Agreement will continue to apply until terminated by either you or Google as set out below. 9.2 If you want to terminate the License Agreement, you may do so by ceasing your use of the SDK and any relevant developer credentials. 9.3 Google may at any time, terminate the License Agreement with you if: (A) you have breached any provision of the License Agreement; or (B) Google is required to do so by law; or (C) the partner with whom Google offered certain parts of SDK (such as APIs) to you has terminated its relationship with Google or ceased to offer certain parts of the SDK to you; or (D) Google decides to no longer provide the SDK or certain parts of the SDK to users in the country in which you are resident or from which you use the service, or the provision of the SDK or certain SDK services to you by Google is, in Google's sole discretion, no longer commercially viable. 9.4 When the License Agreement comes to an end, all of the legal rights, obligations and liabilities that you and Google have benefited from, been subject to (or which have accrued over time whilst the License Agreement has been in force) or which are expressed to continue indefinitely, shall be unaffected by this cessation, and the provisions of paragraph 14.7 shall continue to apply to such rights, obligations and liabilities indefinitely.

10. DISCLAIMER OF WARRANTIES

10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE SDK IS AT YOUR SOLE RISK AND THAT THE SDK IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND FROM GOOGLE. 10.2 YOUR USE OF THE SDK AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SDK IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE. 10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

11. LIMITATION OF LIABILITY

11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.

12. Indemnification

12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from (a) your use of the SDK, (b) any application you develop on the SDK that infringes any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you with the License Agreement.

13. Changes to the License Agreement

13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available.

14. General Legal Terms

14.1 The License Agreement constitutes the whole legal agreement between you and Google and governs your use of the SDK (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the SDK. 14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in the License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google's rights and that those rights or remedies will still be available to Google. 14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the License Agreement is invalid, then that provision will be removed from the License Agreement without affecting the rest of the License Agreement. The remaining provisions of the License Agreement will continue to be valid and enforceable. 14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party beneficiaries to the License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of the License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party beneficiaries to the License Agreement. 14.5 EXPORT RESTRICTIONS. THE SDK IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE SDK. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE. 14.6 The rights granted in the License Agreement may not be assigned or transferred by either you or Google without the prior written approval of the other party. Neither you nor Google shall be permitted to delegate their responsibilities or obligations under the License Agreement without the prior written approval of the other party. 14.7 The License Agreement, and your relationship with Google under the License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from the License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction. December 9, 2016

developer.android.com

SDK Tools Release Notes | Android Studio

Android SDK Tools is a component for the Android SDK. It includes the complete set of development and debugging tools for Android. It is included with Android Studio.

Revisions

The sections below provide notes about successive releases of the SDK Tools, as denoted by revision number. To ensure you have the latest version, check SDK Manager for updates.

SDK Tools, Revision 26.0.2 (April 2017)

Changes:
  • When creating an AVD with avdmanager, it is no longer necessary to specify --tag if the package specified by --package only contains a single image (as is the case for all images currently distributed by Google).

SDK Tools, Revision 26.0.1 (March 2017)

Changes:
  • Hierarchy Viewer and Pixel Perfect tools returned to Android Device Monitor (the command-line versions are still removed, as of revision 25.3.0)

SDK Tools, Revision 26.0.0 (March 2017)

Dependencies:
  • Android SDK Platform-Tools revision 24 or later.
Changes:
  • tools/android now attempts to reproduce the functionality of android in tools prior to version 25.3.0 by invoking the new tools.
    • All avd, target, and device commands should work as before.
    • sdk commands will be translated to similar commands using tools/bin/sdkmanager on a best-effort basis.
  • tools/bin/avdmanager now supports the list target command.

SDK Tools, Revision 25.3.0 (March 2017)

Dependencies:
  • Android SDK Platform-Tools revision 24 or later.
Changes:
  • Android Emulator is removed from this package and moved to a different SDK directory. See the new Android Emulator Release Notes. This change is backward compatible with older Android Studio versions.
  • android avd command-line functionality replaced with new avdmanager tool.
  • Obsolete/deprecated tools have been removed:
  • Executables have been moved to bin/:
    • jobb
    • lint
    • monkeyrunner
    • screenshot2
    • Uiautomatorviewer
  • Enhanced sdkmanager:
    • View and accept all licenses from the command line
    • Improved verbose-mode package list

SDK Tools, Revision 25.2.5 (January 2017)

Dependencies:
  • Android SDK Platform-Tools revision 24 or later.
Android Emulator bug fixes:
  • Fixed a crash on async socket reconnect.
  • Fixed a crash on Mac when glDeleteTextures() is called after the corresponding context was destroyed.

SDK Tools, Revision 25.2.4 (December 2016)

Dependencies:
  • Android SDK Platform-tools revision 24 or later.
Android Emulator bug fixes:
  • Fixed a crash in gles pipe when accessing a closed one.
  • Fixed a rare crash if emulator is closed during location loading.

SDK Tools, Revision 25.2.3 (November 2016)

Dependencies:
  • Android SDK Platform-tools revision 24 or later.
Added new sdkmanager command line tool to view, install, update, and uninstall individual Android SDK packages. New Android Emulator features and bug fixes:
  • Fixed -gpu guest (issue 227447).
  • Added support for WebP image decoding.
  • Added support for ETC2 texture decompression.

SDK Tools, Revision 25.2.2 (September 2016)

Dependencies:
  • Android SDK Platform-tools revision 23 or later.
New Android Emulator features:
  • Added new Virtual Sensors and Cellular > Signal Strength extended controls.
  • Added an LTE option to the Cellular > Network type extended controls.
  • Added simulated vertical swipes for scrolling through vertical menus with a mouse wheel.

SDK Tools, Revision 25.1.6 (May 2016)

Dependencies:
  • Android SDK Platform-tools revision 23 or later.
General Notes:
  • To improve the security of the Android Emulator and to address a reported security vulnerability, the Android Emulator Console now requires authentication before you can enter commands. Enter the auth auth_token command after you telnet to an emulator instance. auth_token must match the contents of the .emulator_console_auth_token file in your home directory.

SDK Tools, Revision 25.0.0 (April 2016)

Android Emulator 2.0:
  • Performance improvements:
    • Emulator now uses CPU acceleration on x86 emulator system images by default.
    • Added SMP support to take advantage of host multi-core architecture when emulating Android 6.0 (API level 23) or higher, resulting in much better performance and speed than the physical counterpart. Also with SMP support, you can test apps that specifically target multi-core Android devices.
    • Improved data and APK push-pull protocol between the Android Debug Bridge and devices running Android 5.0 (API level 21) or higher. See speed improvements up to five times faster than using a physical device.
  • Extended UI controls and a floating toolbar provide easy access to features previously available only through the command line, such as taking screen captures, adjusting the battery level, rotating the screen, and managing virtual calls.
  • Upload KML and GPX files to play back a set of custom location points.
  • Dynamically resize the emulator by dragging a corner or zoom into the emulator window.
  • Install APKs or add media files to the emulator’s internal SD card by dragging and dropping files into the emulator window.
  • Simulate multi-touch input. While interacting with the emulator screen, enter multi-touch mode by holding down the Ctrl key on Windown/Linux, or Command key on Mac OSX.
  • The Android Emulator works best with Android Studio 2.0. To find out more about what's included in the newest version of the official Android IDE, read the release notes.
  • Read the documentation to find out more about using the Android Emulator.

SDK Platform-tools, Revision 23.1.0 (December 2015)

General Notes:
  • Changed Linux requirements for Android SDK Platform-tools revision 23.1.0 and later: it now requires 64-bit Linux.

SDK Tools, Revision 24.4.1 (October 2015)

Dependencies:
  • Android SDK Platform-tools revision 23 or later.
General Notes:
  • Fixed a problem where the emulator title bar was hidden off screen. (Issue 178344)
  • Enabled the emulator to resize the user data partition by including e2fsprogs binaries. (Issue 189030)
  • Fixed a regression on the 32-bit Windows OS where the emulator fails to boot Android 6.0 (API level 23) through Android 5.0 (API level 21) system images. (Issue 188326)

SDK Tools, Revision 24.4.0 (October 2015)

Dependencies:
  • Android SDK Platform-tools revision 23 or later.
General Notes:
  • Updated the emulator so it can display an upgrade notification when a new version is available.
  • Added the ability for the emulator to send basic crash reports. You must opt-in through Android Studio preferences to enable crash report transmission.

SDK Tools, Revision 24.3.4 (August 2015)

Dependencies:
  • Android SDK Platform-tools revision 23 or later.
General Notes:
  • Added support for Android 6.0 (API level 23) platform.
Emulator:
  • Improved emulator performance on multi-core Windows desktops. (Issue 101040)
  • Added support for GPU emulation on Windows and Linux platforms using the -gpu mesa command line option.
  • Enabled support for running emulators with GPU emulation through remote desktop services, including Chrome Remote Desktop, Windows Terminal Services, and NoMachine.
  • Added support for emulators with 280 dpi and 360 dpi screen resolutions.
  • Improved support for GLES 2.0 extensions.
  • Fixed several issues with GPU emulation support.
  • Added support for setting the storage size on emulators using Android 4.4 (API level 19) and higher. (Issue 75141)
  • Fixed problem with sending long SMS messages between emulators. (Issue 3539)
  • Fixed issue with emulator getting incorrect time from location objects. (Issue 27272)
  • Added handling for unusual characters in paths and file names when starting emulators. (Issue 35889)

SDK Tools, Revision 24.3.3 (June 2015)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Fixed issues with using Ant build tasks with the Eclipse ADT build structure.
  • Fixed the emulator boot problem on Mac OS X 10.8.5.

SDK Tools, Revision 24.3.2 (June 2015)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Fixed issues with the ARM 64-bit emulator.

SDK Tools, Revision 24.3.1 (June 2015)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Fixed issue with the root/ and lib/ folders.

Caution: This release is known to contain issues which prevent builds from completing. We strongly recommend that you update to SDK Tools 24.3.2 as soon as possible.

SDK Tools, Revision 24.3.0 (June 2015)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Fixed several minor emulator issues.

Caution: This release is known to contain issues which prevent builds from completing. We strongly recommend that you update to SDK Tools 24.3.2 as soon as possible.

SDK Tools, Revision 24.2.0 (May 2015)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Fixed several minor emulator issues.

SDK Tools, Revision 24.1.2 (February 2015)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Fixed boot failures of MIPS system images on Mac OS X.
  • Fixed AVD screen capture issues when using GPU emulation.
  • Fixed memory leaks in emulator system.

SDK Tools, Revision 24.0.2 (December 2014)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Fixed issue with creating projects and activities from templates using Eclipse ADT.

SDK Tools, Revision 24.0.1 (December 2014)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Fixed Java detection issue on 32-bit Windows systems.

SDK Tools, Revision 24.0.0 (December 2014)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
General Notes:
  • Added support for Android Studio 1.0 and emulator enhancements.

SDK Tools, Revision 23.0.5 (October 2014)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 23.0.4 and later. If you haven't already, update your ADT Plugin to 23.0.4.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed Windows 32-bit compilation issue.

SDK Tools, Revision 23.0.4 (October 2014)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 23.0.4 and later. If you haven't already, update your ADT Plugin to 23.0.4.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed duplicate devices in AVD for Wear and TV.

SDK Tools, Revision 23.0.2 (July 2014)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 23.0.2 and later. If you haven't already, update your ADT Plugin to 23.0.2.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Added ProGuard .bat files that were missing.
  • Added the proguard-android.txt file that was missing.
  • Renamed the lombok-ast-0.2.2.jar file to lombok-ast.jar, which should allow running lint from the command line.

SDK Tools, Revision 23.0.0 (June 2014)

Dependencies:
  • Android SDK Platform-tools revision 19 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 23.0.0 and later. If you haven't already, update your ADT Plugin to 23.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Added the Android Wear tools and system images.

SDK Tools, Revision 22.6.4 (June 2014)

Dependencies:
  • Android SDK Platform-tools revision 18 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.6.3 and later. If you haven't already, update your ADT Plugin to 22.6.3.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed an issue with the x86 emulator that caused Google Maps to crash. (Issue 69385)
  • Fixed minor OpenGL issues.

SDK Tools, Revision 22.6.3 (April 2014)

Dependencies:
  • Android SDK Platform-tools revision 18 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.6.3 and later. If you haven't already, update your ADT Plugin to 22.6.3.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed a problem where the AVD manager allowed creating Android Wear virtual devices with a target API Level lower than 19.
  • Fixed the description of Android Wear system images in the SDK Manager.
Known Issues:

When you create an Android Wear virtual device in the AVD manager, a target API Level lower than 19 may be selected by default. Make sure you select the target API Level 19 when creating Android Wear virtual devices.

SDK Tools, Revision 22.6.2 (March 2014)

Dependencies:
  • Android SDK Platform-tools revision 18 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.6.2 and later. If you haven't already, update your ADT Plugin to 22.6.2.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed a problem where the SDK Manager threw a NullPointerException after removing a virtual device that was created using the Android Wear system image. (Issue 67588)
  • Fixed a problem with Nexus 5 Android virtual devices created from the command line where the SD card file system was read-only.

SDK Tools, Revision 22.6.1 (March 2014)

Dependencies:
  • Android SDK Platform-tools revision 18 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.6.1 and later. If you haven't already, update your ADT Plugin to 22.6.1.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed a problem where the Android Virtual Device Manager could not create new virtual devices. (Issue 66661)
  • Fixed a problem with virtual devices created using ADT 22.3 or earlier.

    If you created an Android Virtual Device using ADT 22.3 or earlier, the AVD may be listed as broken in the AVD Manager in 22.6.1. To fix this problem, select the virtual device on the AVD Manager and click Repair.

  • Fixed a problem with the command line tools when creating virtual devices. (Issue 66740)
  • Fixed a problem with the command line lint script.
Known Issues:

When you create an Android virtual device using the Nexus 5 device definition, you must enable the Use Host GPU option, otherwise the virtual device will not start.

SDK Tools, Revision 22.6 (March 2014)

Dependencies:
  • Android SDK Platform-tools revision 18 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.6.0 and later. If you haven't already, update your ADT Plugin to 22.6.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • The command line lint script (tools\lint.bat on Windows platforms, tools/lint on other platforms) and the lint target on ant builds fail with the following error:

    Exception in thread "main" java.lang.NoClassDefFoundError: lombok/ast/AstVisitor

    As a temporary workaround, rename the file tools\lib\lombok-ast-0.2.2.jar to tools\lib\lombok-ast.jar. We will release an updated version of the tools with a fix for this issue as soon as possible.

  • Added support for Java 7 language features like multi-catch, try-with-resources, and the diamond operator. These features require version 19 or higher of the Build Tools. Try-with-resources requires minSdkVersion 19; the rest of the new language features require minSdkVersion 8 or higher.
  • Added new lint checks:
    • Security:
      • Look for code potentially affected by a SecureRandom vulnerability.
      • Check that calls to checkPermission use the return value.
    • Check that production builds do not use mock location providers.
    • Look for manifest values that are overwritten by values from Gradle build scripts.
  • Fixed a number of minor issues in the SDK and build system.
  • Emulator:
    • Fixed a problem with the emulator shutting down immediately for Android 1.5 on the Nexus One and Nexus S devices. (Issue 64945)
    • Fixed a problem with port numbers longer than four digits. (Issue 60024)
    • Fixed battery errors for the Nexus One and Nexus S devices. (Issue 39959)
    • Fixed a problem with paths or arguments that contain spaces on Windows platforms. (Issue 18317)
    • Fixed a problem with long path values on Windows platforms. (Issue 33336)
    • Fixed a problem with the -snapshot-list command line option on 64-bit systems. (Issue 34233)
  • Fixed an issue with RenderScript support. Using RenderScript support mode now requires version 19.0.3 of the Build Tools.

SDK Tools, Revision 22.3 (October 2013)

Dependencies:
  • Android SDK Platform-tools revision 18 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.3.0 and later. If you haven't already, update your ADT Plugin to 22.3.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Added support for Android 4.4 (API level 19).
  • Fixed a number of minor bugs in the SDK and build system.

SDK Tools, Revision 22.2.1 (September 2013)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.2.1 and later. If you haven't already, update your ADT Plugin to 22.2.1.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed problem with templates that causes the new project wizard to hang. (Issue 60149)
  • Fixed crash when using the lint command line tool because of mis-matched library dependency. (Issue 60190)

SDK Tools, Revision 22.2 (September 2013)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.2 and later. If you haven't already, update your ADT Plugin to 22.2.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Updated build tools to allow use of RenderScript on older versions of Android using new features in the Support Library.
  • Moved the Systrace tool to the >sdk</platform-tools/ directory.
  • Modified Tracer for OpenGL ES to support OpenGL ES 3.0.
  • Lint
    • Fixed problem with lint not detecting custom namespaces. (Issue 55673)
    • Fixed problem with the XML report including invalid characters. (Issue 56205)
    • Fixed command-line execution of lint to work in headless mode to support execution by build servers. (Issue 55820)
  • Improved support for path names with spaces in the Windows command-line tools.

SDK Tools, Revision 22.0.5 (July 2013)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with the ADT Plugin, note that this version of SDK Tools is designed for use with ADT 22.0.5 and later. If you haven't already, update ADT to 22.0.5.
  • This version of the SDK Tools is designed to work with Android Studio 0.2.x and later.
  • If you are developing without an integrated development environment (IDE), you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed RenderScript compilation issue for Windows platforms with ant.
  • Updated Systrace to work with the Android 4.3 platform image.
  • Fixed packaging of RenderScript compiler.
  • Build tools 18.0.0 is obsolete and 18.0.1 should be used instead.

SDK Tools, Revision 22.0.4 (July 2013)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with the ADT Plugin, note that this version of SDK Tools is designed for use with ADT 22.0.4 and later. If you haven't already, update ADT to 22.0.4.
  • This version of the SDK Tools is designed to work with Android Studio 0.2.x and later.
  • If you are developing without an integrated development environment (IDE), you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed problem with compiling RenderScript code.

SDK Tools, Revision 22.0.1 (May 2013)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.0.1 and later. If you haven't already, update your ADT Plugin to 22.0.1.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Fixed issue with Lint ServiceCast check and fully qualified class names. (Issue 55403)
  • Fixed crash issue with Lint ArraySizeDetector check. (Issue 54887)
  • Fixed a problem with the monkeyrunner tool failing to import standard python classes. (Issue 55632)
  • Fixed a problem with DDMS monitor not opening heap and network statistics views due to a class not found exception. (Issue 55394)

SDK Tools, Revision 22 (May 2013)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 22.0.0 and later. If you haven't already, update your ADT Plugin to 22.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Changed the structure of the SDK by adding a new build tool SDK Component, which is based on the existing platform-tools component. This change decouples the build tools versions from the IDE versions, allowing updates to the tools without requiring an IDE update.
  • Updated tools to allow libraries to share the same package name as the applications that use them.
  • Updated draw9patch tool to allow easier changing of markers.
  • Added new Lint checks, including checks for layout consistency, RelativeLayout siblings, Parcel creator, JavaScript interfaces, Service casting, quantity strings, manifest typos, orientation tags in layouts, overlapping names for 9-patches and images, and class existence checks.
  • Updated build tools to sign applications using the BouncyCastle library instead of relying on Sun JVM specific APIs.
  • Released some of the Android tools into Maven Central to assist third-party tool developers. The following tools are available in the repository: manifest-merger, common/sdk_common, ddmlib, dvlib, layoutlib_api, sdklib, and lint.
Bug fixes:
  • Fixed a number of minor bugs in the SDK and build system.

SDK Tools, Revision 21.1 (February 2013)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 21.1.0 and later. If you haven't already, update your ADT Plugin to 21.1.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Improved error reporting in dx when dex merging fails in the build system.
  • Added more than 15 new Lint checks, including checks for overriding older APIs, XML resource problems, graphic asset issues and manifest tags.
  • Added new aapt feature to compile resources.

SDK Tools, Revision 21.0.1 (December 2012)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 21.0.1 and later. If you haven't already, update your ADT Plugin to 21.0.1.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Build
    • Updated build to detect and handle package name conflicts between an application and the libraries it depends on. Libraries cannot share package names unless all of them share the same package name. (Issue 40152, Issue 40273)
    • Added a flag to disable dex merging to deal with cases where merging could generate a broken dex file. If this happens to your project, add the following setting to your project.properties file: dex.disable.merger=true This setting causes the build system to revert to the older, slower dex processing that does not pre-dex libraries.
  • RenderScript
    • Added support for Filterscript compilation.
    • Added new project setting to control the RenderScript compilation target separately from an Android project. Adding the following line to a project.properties file causes RenderScript code to be compiled for Android API Level 17, while the containing application can target a different (lower) API level: renderscript.target = 17 Previously, the RenderScript compilation target was tied to the android:minSdkVersion setting in the manifest. (Issue 40487)
Bug fixes:
  • Lint
    • Corrected check for 0px values in style XML elements. (Issue 39601)
    • Fixed incorrect flagging of formatting strings. (Issue 39758)
    • Fixed problem where tools:ignore directive in the manifest file was ignored by the Lint tool. (Issue 40136)
    • Fixed problem with flagging a wakelock release inside a conditional. (Issue 40424)
    • Fixed incorrect reporting of missing layout_width and layout_height XML fields. (Issue 38958)
    • Fixed handling of custom namespace attributes.
    • Added fixes for filtering out library project warnings.
    • Removed warnings about missing classes before a build.
  • Fixed problem with UI Automator Viewer execution script where Android tools directory is not set.
  • Fixed problem with the SDK Manager so that it auto-selects the most recently released platform on startup.
  • Fixed Java finding script to look for the currently supported version of Java (1.6 or higher).
  • Fixed the SDK Manager launcher in the ADT bundle so that it can properly launch the SDK Manager program when it is placed at the root of the bundle.

SDK Tools, Revision 21 (November 2012)

Dependencies:
  • Android SDK Platform-tools revision 16 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 21.0.0 and later. If you haven't already, update your ADT Plugin to 21.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General Notes:
  • Build System
    • Added a flag that sets jumbo mode for DEX files, which allows a larger number of strings in the DEX files. Enable this mode by adding the following line to the project.properties file of your project: dex.force.jumbo=true
    • Improved the build time by pre-dexing libraries (both JAR files and library projects).
    • Updated the build to generate R resource classes for library projects with only the IDs needed by the libraries, reducing the risk of hitting DEX file limits for fields and methods.
    • Improved the build so that several editing features (code completion, resource chooser, go to declaration) properly handle library project resources.
  • Lint
    • Added over 25 new lint rules for resources, locale settings, layout files, incorrect use of SparseArray and PowerManager.WakeLock and manifest issues.
    • Updated reporting to include errors in library projects if the library project is in the list of projects to be checked.
    • Added a new lint target to the Ant build system for easier integration with continuous build systems.
    • Added new --sources and --classpath arguments to point to sources with different directory structures.
    • Improved the XML export function to support the Jenkins Lint plugin.
    • Added support for class file flow analysis.
  • Android Virtual Devices (AVD)
    • Added new Device Definitions tab in the AVD Manager for configuring standard size and Nexus virtual devices.
    • Improved emulators so that they launch with a skin that is dynamically generated and reflects the actual hardware configured in the AVD Manager.
    • Improved support for developing Android apps on MIPS-based devices with new MIPS System Images for Android Virtual Devices.
  • Added jobb tool for creating and encrypting APK Expansion Files. (more info)
  • Improved the Android JUnit test runner to allow a test to be run on all connected devices simultaneously.
Bug fixes:
  • Fixed manifest merger to properly adapt library classes in the merged manifest.

SDK Tools, Revision 20.0.3 (August 2012)

Dependencies:
  • Android SDK Platform-tools revision 12 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 20.0.3 and later. If you haven't already, update your ADT Plugin to 20.0.3.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
Bug fixes:
  • Fixed problem with cached download lists in SDK Manager.

SDK Tools, Revision 20.0.1 (July 2012)

Dependencies:
  • Android SDK Platform-tools revision 12 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 20.0.1 and later. If you haven't already, update your ADT Plugin to 20.0.1.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
Bug fixes:
  • Fixed wrong check on build state that forced repetitive Java code recompilation.
  • Fixed problems with running more than one emulator and running multiple emulators with GPU acceleration.
  • Improved resize algorithm for better rendering on scaled emulator windows.
  • Fixed a bug in the lint check for unprotected broadcast receivers to ignore unprotected receivers for default Android actions.
  • Fixed build issue for projects using RenderScript.
  • Fixed memory leak in the emulator.

SDK Tools, Revision 20 (June 2012)

Dependencies:
  • Android SDK Platform-tools revision 12 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 20.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 20.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General notes:
  • Added new Device Monitor application, grouping Android debugging tools into a single application, including ddms, traceview, hierarchyviewer and Tracer for GLES. (more info)
  • Added new System Trace new tool for tracing Android system activity. This tool allow you to capture a slice of system activity, plus additional information tagged from the Settings > Developer Options > Monitoring: Enable traces or with specific calls added to your application code.
  • Build System
    • Added automatic merging of library project manifest files into the including project's manifest. Enable this feature with the manifestmerger.enabled property.
    • Added automatic ProGuard support for the aapt -G flag. This change causes the build system to generate a temporary ProGuard keep-rules file containing classes that are referenced from XML files (such as custom views) and pass this to ProGuard at shrink time. This can make the resulting APK much smaller when using just a small portion of a large library project (such as the Android Support library), since the catch-all rules to keep all custom views from the default ProGuard configuration file have also been removed.
    • Added two ProGuard configuration files for use in projects: proguard-android-optimize.txt which enables optimizations and proguard-android.txt which disables them.
  • SDK Manager
    • Improved caching to reduce downloading of repository definitions.
    • Added Tools > Manage Add-on Sites option to improve performance by allowing temporary deactivation of third-party sites if they are loading slowly.
    • Added settings for the SDK Manager download cache (SDK Manager > Tools > Options).
Bug fixes:
  • Build
    • Fixed problem where test projects did not have access to the full classpath of tested projects, including Library Projects and third-party jars.
    • Fixed deployment logic so that applications with embedded tests can now be deployed and tested like test applications, including code coverage information.
    • Fixed Ant support for testing projects with libraries.

SDK Tools, Revision 19 (April 2012)

Note: This update of SDK Tools is only available through the Android SDK Manager. Use this tool to download and install this update.

Dependencies:
  • Android SDK Platform-tools revision 9 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 18.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 18.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
Bug fixes:
  • Fixed an issue that prevented some developers from running the emulator with GPU acceleration.

SDK Tools, Revision 18 (April 2012)

Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

Dependencies:
  • Android SDK Platform-tools revision 9 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 18.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 18.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General notes:
  • Updated the SdkController app to encapsulate both sensor and multitouch emulation functionality.
Bug fixes:
  • Fixed Ant issues where some jar libraries in the libs/ folder are not picked up in some cases.

SDK Tools, Revision 17 (March 2012)

Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

Dependencies:
  • Android SDK Platform-tools revision 9 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 17.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 17.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General notes:
  • Emulator
  • Added viewing of live detailed network usage of an app in DDMS. (more info)
  • ProGuard
    • Updated the bundled ProGuard tool to version 4.7. In addition to many new features, this update fixes the Conversion to Dalvik format failed with error 1 error some users have experienced.
    • Updated the default proguard.cfg file with better default flags for Android.
    • Split the ProGuard configuration file has been in half, with project specific flags kept in project and the generic Android flags distributed (and updated) with the tools themselves.
  • Build
    • Added a feature that allows you to run some code only in debug mode. Builds now generate a class called BuildConfig containing a DEBUG constant that is automatically set according to your build type. You can check the (BuildConfig.DEBUG) constant in your code to run debug-only functions.
    • Fixed issue when a project and its libraries include the same jar file in their libs folder. (more info)
    • Added support for custom views with custom attributes in libraries. Layouts using custom attributes must use the namespace URI http://schemas.android.com/apk/res-auto instead of the URI that includes the app package name. This URI is replaced with the app specific one at build time.
  • Lint
    • Updated Lint to check Android application code. Lint rules which previously performed pattern based searches in the application code (such as the unused resource check) have been rewritten to use the more accurate Java-style parse trees.
    • Added support for checking library projects. This change means that rules such as the unused resource check properly handle resources declared in a library project and referenced in a downstream project.
    • Added ability to suppress Lint warnings in Java code with the new @SuppressLint annotation, and in XML files with the new tools: namespace and ignore attribute. (more info)
    • New Lint checks:
      • Added check for Android API calls that require a version of Android higher than the minimum supported version. You can use the new @TargetApi annotation to suppress warnings when the code is wrapped in a system version condition. (more info)
      • Added over 20 new Lint rules, including checks for performance, XML layouts, manifest and file handling.

SDK Tools, Revision 16 (December 2011)

Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

Dependencies:
  • Android SDK Platform-tools revision 9 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 16.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 16.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General notes:
  • Added Lint tools to detect common errors in Android projects. (more info)
  • Added sensor emulation support, which allows the emulator to read sensor data from a physical Android device. (more info)
  • Added support for using a webcam to emulate a camera on Mac OS X.
Bug fixes:

SDK Tools, Revision 15 (October 2011)

Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

Dependencies:
  • Android SDK Platform-tools revision 9 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 15.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 15.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
Bug fixes:
  • Fixed emulator crash on Linux due to improper webcam detection (Issue 20952).
  • Fixed emulator issue when using the -wipe-data argument.
  • Fixed build issue when using RenderScript in projects that target API levels 11-13 (Issue 21006).
  • Fixed issue when creating an AVD using the GoogleTV addon (Issue 20963).
  • Fixed ant test (Issue 20979).
  • Fixed android update project (Issue 20535).
  • Fixed scrolling issue in the new Logcat panel of DDMS.
  • Fixed issue with MonkeyRunner (Issue 20964).
  • Fixed issues in the SDK Manager (Issue 20939, Issue 20607).

SDK Tools, Revision 14 (October 2011)

Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

Dependencies:
  • Android SDK Platform-tools revision 8 or later.
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 14.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 14.0.0.
  • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
General notes:
  • Added webcam support to Android 4.0 or later platforms to emulate rear-facing cameras when one webcam is present, and to emulate both rear-facing and front-facing cameras when two webcams are present. Webcam support is for Windows and Linux only. Mac support will come in a later release.
  • Changed default.properties to project.properties and build.properties to ant.properties. Any existing projects that you build with Ant must be updated with the android update project command.
  • Changed Ant build.xml file to support improvements to the build system and added and modified Ant commands to support these changes. For a list of Ant commands, see the Ant Command Reference.
  • Changed how library projects are built.
  • Improved incremental builds, so that resource compilation runs less frequently. Builds no longer run when you edit strings or layouts (unless you add a new id) and no longer run once for each library project.
  • Introduced a "PNG crunch cache" that only runs on modified PNG files, instead of crunching all existing PNG files, all the time.
  • Revamped the SDK Manager UI (more info).

For a complete overview of the build system changes and what you need to do to support them, see the Android Tools Project site.

SDK Tools, Revision 13 (September 2011)

Dependencies:

If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 12.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 12.0.0.

If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

General notes:
  • Fix compilation issue in Ant (dex step) when paths have spaces.
  • Fix issue in emulator installation when paths have spaces.
  • Fix issue when AVD paths have spaces.
  • Fix rendering issue when using emulator scaling (see more).

SDK Tools, Revision 12 (July 2011)

Dependencies:

If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 12.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 12.0.0.

If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

General notes:
  • The AVD manager and emulator can now use system images compiled for ARM v7 and x86 CPUs.

SDK Tools, Revision 11 (May 2011)

Dependencies:

If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 10.0.1 and later. If you haven't already, we highly recommend updating your ADT Plugin to 10.0.1.

If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

General notes:
  • Miscellaneous emulator changes to support Android 3.1.

SDK Tools, Revision 10 (February 2011)

Dependencies:

If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 10.0.0 and later. After installing SDK Tools r10, we highly recommend updating your ADT Plugin to 10.0.0.

If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

General notes:
  • The tools now automatically generate Java Programming Language source files (in the gen directory) and bytecode (in the res/raw directory) from your native .rs files

SDK Tools, Revision 9 (January 2011)

Dependencies:

If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 9.0.0 and later. After installing SDK Tools r9, we highly recommend updating your ADT Plugin to 9.0.0.

If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

Upgrading to SDK Tools r9:

If you are upgrading to SDK Tools r9 from SDK Tools r7 or earlier, the default installed location for the adb tool has changed from <SDK>/tools/adb to <SDK>/platform-tools/adb. This means that you should add the new location to your PATH and modify any custom build scripts to reference the new location. Copying the adb executable from the new location to the old is not recommended, since subsequent updates to the SDK Tools will delete the file.

General notes:
  • The default ProGuard configuration, proguard.cfg, now ignores the following classes:
  • Ant lib rules now allow you to override java.encoding, java.source, and java.target properties.
  • The default encoding for the javac Ant task is now UTF-8.
  • The LogCat view in DDMS now properly displays UTF-8 characters.
  • The SDK Manager is more reliable on Windows. For details on the improvements, see the Android Tools Project Site.
  • Early look at the new snapshot feature: To improve startup time for the emulator, you can enable snapshots for the system state. The emulator will then restore to the state when it last closed almost instantly. Note: The snapshot feature is still under active development and might not always perform as expected.
  • Fixed the missing JAR file error that prevented draw9patch from running.
  • Fixed the Windows launch scripts hierarchyviewer and ddms to support the new location of adb.
  • Known issues with emulator performance: Because the Android emulator must simulate the ARM instruction set architecture on your computer, emulator performance is slow. We're working hard to resolve the performance issues and it will improve in future releases.

SDK Tools, Revision 8 (December 2010)

Dependencies:

If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 8.0.0 and later. After installing SDK Tools r8, we highly recommend updating your ADT Plugin to 8.0.0.

If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

Also note that SDK Tools r8 requires a new SDK component called Platform-tools. The new Platform-tools component lets all SDK platforms (Android 2.1, Android 2.2, and so on) use the same (latest) version of build tools such as adb, aapt, aidl, and dx. To download the Platform-tools component, use the Android SDK Manager.

Upgrading from SDK Tools r7:

If you are upgrading to SDK Tools r8 from an earlier version, note that the the default installed location for the adb tool has changed from <SDK>/tools/adb to <SDK>/platform-tools/adb. This means that you should add the new location to your PATH and modify any custom build scripts to reference the new location. Copying the adb executable from the new location to the old is not recommended, since subsequent updates to the SDK Tools will delete the file.

General notes:
  • All SDK platforms now support Library Projects.
  • Support for a true debug build. Developers no longer need to add the android:debuggable attribute to the <application> tag in the manifest — the build tools add the attribute automatically. In Eclipse/ADT, all incremental builds are assumed to be debug builds, so the tools insert android:debuggable="true". When exporting a signed release build, the tools do not add the attribute. In Ant, a ant debug command automatically inserts the android:debuggable="true" attribute, while ant release does not. If android:debuggable="true" is manually set, then ant release will actually do a debug build, rather than a release build.
  • Automatic ProGuard support in release builds. Developers generate a ProGuard configuration file using the android tool — the build tools then automatically run ProGuard against the project sources during the build. For more information, see the ProGuard documentation.
  • New overridable Ant javac properties: java.encoding, java.source, and java.target (default values are "ascii", "1.5", and "1.5", respectively).
  • New UI for the HierarchyViewer tool.

SDK Tools, Revision 7 (September 2010)

Dependencies:

If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 0.9.8 and later. After installing SDK Tools r7, we highly recommend updating your ADT Plugin to 0.9.8.

General notes:
  • Added support for library projects that depend on other library projects.
  • Adds support for aidl files in library projects.
  • Adds support for extension targets in Ant build to perform tasks between the normal tasks: -pre-build, -pre-compile, and -post-compile.
  • Adds support for "headless" SDK update. See android -h update sdk for more information.
  • Fixes location control in DDMS to work in any locale not using '.' as a decimal point.

SDK Tools, Revision 6 (May 2010)

Dependencies:

If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 0.9.7 and later. After installing SDK Tools r6, we highly recommend updating your ADT Plugin to 0.9.7.

Library projects:

The SDK Tools now support the use of library projects during development, a capability that lets you store shared Android application code and resources in a separate development project. You can then reference the library project from other Android projects and, at build time, the tools compile the shared code and resources as part of the dependent applications. More information about this feature is available in the Creating and Managing Projects document.

If you are developing in Eclipse, ADT provides the equivalent library project support.

SDK Tools, Revision 5 (March 2010)

Dependencies:
  • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 0.9.6 and later. After installing SDK Tools r5, we highly recommend updating your ADT Plugin to 0.9.6.
  • For Mac OS platforms, OS X 10.4.x (Tiger) is no longer officially supported.
SDK and AVD Manager:
  • Fixes SSL download for the standalone version of the SDK Updater.
  • Fixes issue with 64-bit JVM on Windows.
  • Adds support for platform samples components.
  • Improves support for dependency between components.
  • AVDs now sorted by API level.
  • The AVD creation dialog now enforces a minimum SD card size of 9MB.
  • Prevents deletion of running AVDs.
  • Settings are now automatically saved, no need to click "Apply".
Emulator:
  • Emulator now requires SD card to be 9MB or more.
Layoutopt:
  • Fixes layoutopt.bat to execute correctly on Windows.

SDK Tools, Revision 4 (December 2009)

Dependencies:

This version of SDK Tools is compatible with ADT 0.9.5 and later, but not compatible with earlier versions. If you are developing in Eclipse with ADT, you must update your ADT plugin to version 0.9.5 or higher if you install SDK Tools r4 in your SDK.

General notes:
  • Launcher script now forces GDK_NATIVE_WINDOW=true (linux only), to fix a compatibility issue between GTK and SWT.
Android SDK and AVD Manager:
  • AVD Launch dialog now shows scale value.
  • Fixes potential NPE in SDK Manager on AVD launch, for older AVD with no skin name specified.
  • Fixes XML validation issue in on older Java versions.
  • No longer forces the use of Java 1.5 on Mac OS X.
Emulator:
  • No longer limits the size of the system partition.
Ant build tools:
  • .apk packaging now properly ignores vi swap files as well as hidden files.

SDK Tools, Revision 3 (October 2009)

Dependencies:

This version of SDK Tools is compatible with ADT 0.9.4 and later, but not compatible with earlier versions. If you are developing in Eclipse with ADT, you must update your ADT plugin to version 0.9.4 or higher if you install SDK Tools r3 in your SDK.

Android tool:
  • Adds new android create test-project and android update test-project commands to allow for greater flexibility in the location of the main and test projects.
DDMS:
  • Adds a button to dump HPROF file for running applications (app must be able to write to the sdcard).
  • Button to start/stop profiling of a running application (app must be able to write to the sdcard). Upon stop, Traceview will automatically be launched to display the trace.
  • Fixed DDMS, Traceview, and the AVD Mananger/SDK Updater to run on Mac OS X 10.6.
  • Fixed screenshot support for devices running 32-bit framebuffer.
Android SDK and AVD Manager:
  • Provides a new UI that lets you set options for controlling the emulator skin, screen size/density, and scale factor used when launching an AVD.
  • Provides improved AVD creation UI, which lets you customize the hardware properties of your AVDs.
  • Now enforces dependencies between platforms and tools components, and between SDK add-ons and platforms.
Layoutopt, a new tool for optimizing layouts:

The SDK Tools r3 package includes layoutopt, a new command-line tool that helps you optimize your layout hierarchies. When run against your layout files, the tool analyzes their hierarchies and notifies you of inefficiencies and other potential issues. The tool also provides simple solutions for the issues it finds. For usage, see layoutopt.

developer.android.com

Установка Eclipse и подключение плагина Android Development Tools (ADT) для разработки андроид-приложений

В этом уроке:

После выхода официального релиза Android Studio у начинающих разработчиков появились проблемы с загрузкой и установкой все еще популярной среды разработки Eclipse и плагина Android Development Tools (ADT) для разработки андроид-приложений. Ниже приводим перевод инструкции с официального сайта, в которой вы узнаете, как скачать и установить Eclipse, а также как подключить и настроить плагин Android Development Tools (ADT), чтобы начать программировать под андроид.

Вы должны сначала загрузить Eclipse, затем скачать Android SDK и  установить плагин ADT (Android Development Tools).

Если Eclipse уже установлен, перед установкой ADT проверьте соответствие следующим требованиям:

Установлен Eclipse 3.7.2 (Indigo) или вышеПримечание: Eclipse 3,6 (Helios) больше не поддерживает последние версии ADT.Установлен Eclipse JDT плагин (входит в большинство пакетов Eclipse IDE)Установлена JDK 6 (пакет JRE не является достаточным)

Если все условия выполняются, можно пропустить несколько пунктов и перейти к загрузке и установке ADT плагина для Eclipse.

Если вы начинаете с нуля, то выполните все последующие шаги.

Установите JVM

Независимо от вашей операционной системы, вам нужно будет установить виртуальную машину Java (JVM). Вы собираетесь использовать Eclipse для разработки Java android, поэтому  установите JDK (JDK включает в себя – среди других полезных вещей – исходный код для стандартных Java библиотек).

Если вы используете Windows, вы, возможно, уже устанавливали JRE, но этого не достаточно.

  • При использовании Linux:

Установка JDK (Java Development Kit)

Если у вас не установлен пакет JDK, следуйте инструкции: Установка JDK (Java Development Kit)

 

 

Скачать Eclipse

Скачать среду разработки Eclipse, со страницы загрузки. Выберите Eclipse IDE for Java Developers.

Загрузка будет в виде сжатого (т.е. “.zip”, или “.tar.gz”) файла. Распакуйте этот файл в директорию по вашему выбору (например, “C:\eclipse” на Windows) и убедитесь, что у вас есть полный доступ на чтение и выполнение. При желании вы можете создать ярлык исполняемого файла (“eclipse.exe” на Windows, или “Eclipse” на Linux).

Обратите внимание, что есть известная проблема с распаковкой архива во всех текущих версиях Windows . Мы рекомендуем использовать более надежный архиватор, такие как, например, архиватор с открытым исходным кодом 7zip, при распаковке пакета Eclipse. Некоторые пользователи сообщают об успехах при первоначальной распаковке Eclipse в корневом каталоге (например, C: \), а затем перемещении его на более подходящее место (например, C: \ Program Files \ Eclipse)

Для разработки приложений Android в Eclipse предлагается пользовательский плагин для Eclipse IDE, называемый Android Development Tools (ADT). Этот плагин представляет собой мощную, интегрированную среду разработки приложений для Android. Это расширяет возможности Eclipse, что позволит вам быстро создать новые Android проекты, построить интерфейс приложения, отлаживать свое приложение, а также подписывать и экспортировать пакеты приложения (APK) для распространения.

 

 

Загрузить ADT плагин для Eclipse:

Запустите Eclipse, затем выберите в главном меню Help > Install New Software.

Нажмите Add , в верхнем правом углу.

В хранилище диалоге Добавить окне введите “ADT Plugin” в поле Name и следующий адрес в поле Location:

https://dl-ssl.google.com/android/eclipse/

Примечание: для обновления Android Developer Tools требуется безопасное соединение. Убедитесь, что URL обновления, который вы вводите начинается с HTTPS.Нажмите OK .В диалоге Software, установите флажок рядом с Developer Tools и нажмите Next .В следующем окне вы увидите список инструментов для загрузки. Нажмите Next.Прочитайте и примите условия лицензионного соглашения, а затем нажмите Finish.Если вы получаете предупреждение системы безопасности, что подлинность и достоверность программного обеспечения не может быть установлена, нажмите ОК .После завершения установки, перезагрузите Eclipse.

Если вы не смогли использовать Eclipse, чтобы скачать плагин ADT с удаленного сайта обновлений, вы можете скачать ADT архив на свой компьютер и вручную установить его:

Скачать сжатый файл ADT Plugin (не распаковывать его!):

Запустите Eclipse, затем выберите Help > Install New Software .Нажмите Добавить , в верхнем правом углу.В диалоговом окне репозитория добавить, нажмите кнопку Архив .Выберите загруженный ADT-23.0.6.zip файл и нажмите OK .Введите “ADT Plugin” в качестве имени и нажмите ОК .В диалоге Software, установите флажок рядом с Developer Tools и нажмите Next .В следующем окне вы увидите список инструментов для загрузки. Нажмите Next.Прочитайте и примите условия лицензионного соглашения, а затем нажмите Finish.Если вы получаете предупреждение системы безопасности, что подлинность и достоверность программного обеспечения не может быть установлена, нажмите ОК .После завершения установки, перезагрузите Eclipse.

 

 

Скачайте пакет SDK

Скачайте пакет инструментов Android SDK по этой ссылке.

Cкачайте пакет Android SDK для вашей операционной системы

В открывшейся по ссылке таблице выберите пакет для вашей операционной системы. Для Windows их два: установщик и архив (на выбор). Архив следует распаковать в папку, например, D:\android\sdk. Если выберете установщик, он по умолчанию укажет путь, например, C:\Users\<username>\AppData\Local\Android\android-sdk, лучше изменить его на более короткий, как в примере выше.

Внимание! В пути к SDK не должно быть кириллицы! Это может быть источником многих проблем в будущем.

 

 

Настроить Android SDK

После того, как Eclipse, перезагрузится, необходимо указать расположение каталога Android SDK:

В окне приветствия выберите Использовать существующие пакеты SDK (Use existing SDKs).Нажмите Обзор (Browse)  и выберите расположение каталога SDK (там, куда вы указали путь при загрузке SDK).Нажмите Next .Ваше Eclipse IDE теперь настроена для разработки приложений для Android, но вы должны добавить новые средства SDK платформы и андроид платформу для вашей среды. Чтобы получить эти пакеты , запустите менеджер SDK, и выберите для загрузки необходимые платформы и пакеты.

В Eclipse в меню открывайте Window > Android SDK Manager.

Android SDK Manager

 

Здесь нам показывают SDK-компоненты, которые мы можем скачать, обновить или удалить.

Сначала идет папка Tools – в ней находятся утилиты, необходимые для разработки под Android. Далее идет список версий Android. И в самом низу еще есть папка Extras, в которой обычно находятся дополнительные библиотеки.

Справа от каждого компонента в списке виден его статус: Installed – установлен, Not installed – не установлен, Update available – доступно обновление.  Мне сразу автоматически предлагают обновить и установить некоторые компоненты, на них включены чекбоксы. Нажмите снизу ссылку Deselect All, чтобы снять все галки, а затем Updates, чтобы выделить только те пункты, которые требуют обновления. И пока оставим все так, ничего не загружаем.

Нас сейчас интересуют папки с именами версий Android. Для начала установите Android 4.4.2. Когда освоитесь в разработке, вы всегда сможете вернуться сюда и скачать те версии Android, которые вам необходимы. А пока будем работать с проверенной Android 4.4.2 (API 19).

Как минимум для разработки нам необходимы два компонента в папке Android 4.4.2 (API 19):

1) SDK Platform – используется для разработки. Говоря простыми словами, здесь содержатся все программные компоненты системы Android, которые мы будем использовать при создании приложений – т.е. окна, кнопки и т.п.

2) ARM EABI v7a System Image – образ Android системы. Используется для создания эмулятора Android, который нужен будет для тестирования приложений прямо на компе, без подключения реальных устройств.

Т.е. мы сможем создать приложение, использующее компоненты и возможности Android версии 4.4.2 и запустить это приложение на эмуляторе версии 4.4.2. Этого вполне достаточно для начала.  Ставьте галки на двух этих пунктах в папке Android 4.4.2 (API 19).

Если вам понадобятся другие версии Android, заходите в SDK Manager и устанавливайте эту пару компонентов для нужной вам версии.

Снизу справа жмем кнопку Install <число> packages, чтобы он установил все компоненты которые мы выделили. Учтите, что плафтормы могут весить несколько сотен мегабайт.

Появится окно со списком установки, отмечаем в нем Accept license и жмем Install. Процесс пошел, снизу замелькали проценты, килобайты и секунды.  По завершению процесса снизу будет надпись Done loading package. Все готово для работы. Закрываем и начинаем обучение разработке android приложений.

Продолжение: Создание Android проекта

www.fandroid.info

Download Android Studio and SDK Tools

 

Before installing Android Studio or the standalone SDK tools, you must agree to the following terms and conditions.

Terms and Conditions

This is the Android Software Development Kit License Agreement

1. Introduction

1.1 The Android Software Development Kit (referred to in this License Agreement as the "SDK" and specifically including the Android system files, packaged APIs, and Google APIs add-ons) is licensed to you subject to the terms of this License Agreement. This License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK. 1.2 "Android" means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL: http://source.android.com/, as updated from time to time. 1.3 "Google" means Google Inc., a Delaware corporation with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States.

2. Accepting this License Agreement

2.1 In order to use the SDK, you must first agree to this License Agreement. You may not use the SDK if you do not accept this License Agreement. 2.2 By clicking to accept, you hereby agree to the terms of this License Agreement. 2.3 You may not use the SDK and may not accept the License Agreement if you are a person barred from receiving the SDK under the laws of the United States or other countries including the country in which you are resident or from which you use the SDK. 2.4 If you are agreeing to be bound by this License Agreement on behalf of your employer or other entity, you represent and warrant that you have full legal authority to bind your employer or such entity to this License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity.

3. SDK License from Google

3.1 Subject to the terms of this License Agreement, Google grants you a limited, worldwide, royalty-free, non-assignable and non-exclusive license to use the SDK solely to develop applications to run on the Android platform. 3.2 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you. 3.3 You may not use the SDK for any purpose not expressly permitted by this License Agreement. Except to the extent required by applicable third party licenses, you may not: (a) copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK; or (b) load any part of the SDK onto a mobile handset or any other hardware device except a personal computer, combine any part of the SDK with other software, or distribute any software or device incorporating a part of the SDK. 3.4 You agree that you will not take any actions that may cause or result in the fragmentation of Android, including but not limited to distributing, participating in the creation of, or promoting in any way a software development kit derived from the SDK. 3.5 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software license and not this License Agreement. 3.6 You agree that the form and nature of the SDK that Google provides may change without prior notice to you and that future versions of the SDK may be incompatible with applications developed on previous versions of the SDK. You agree that Google may stop (permanently or temporarily) providing the SDK (or any features within the SDK) to you or to users generally at Google's sole discretion, without prior notice to you. 3.7 Nothing in this License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features. 3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the SDK.

4. Use of the SDK by You

4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under this License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications. 4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) this License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries). 4.3 You agree that if you use the SDK to develop applications for general public users, you will protect the privacy and legal rights of those users. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so. 4.4 You agree that you will not engage in any activity with the SDK, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of any third party including, but not limited to, Google or any mobile communications carrier. 4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so. 4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under this License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach.

5. Your Developer Credentials

5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials.

6. Privacy and Information

6.1 In order to continually innovate and improve the SDK, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the SDK are being used and how they are being used. Before any of this information is collected, the SDK will notify you and seek your consent. If you withhold consent, the information will not be collected. 6.2 The data collected is examined in the aggregate to improve the SDK and is maintained in accordance with Google's Privacy Policy.

7. Third Party Applications

7.1 If you use the SDK to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources. 7.2 You should be aware the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners. 7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party. In that case, this License Agreement does not affect your legal relationship with these third parties.

8. Using Android APIs

8.1 Google Data APIs 8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service. 8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so.

9. Terminating this License Agreement

9.1 This License Agreement will continue to apply until terminated by either you or Google as set out below. 9.2 If you want to terminate this License Agreement, you may do so by ceasing your use of the SDK and any relevant developer credentials. 9.3 Google may at any time, terminate this License Agreement with you if: (A) you have breached any provision of this License Agreement; or (B) Google is required to do so by law; or (C) the partner with whom Google offered certain parts of SDK (such as APIs) to you has terminated its relationship with Google or ceased to offer certain parts of the SDK to you; or (D) Google decides to no longer provide the SDK or certain parts of the SDK to users in the country in which you are resident or from which you use the service, or the provision of the SDK or certain SDK services to you by Google is, in Google's sole discretion, no longer commercially viable. 9.4 When this License Agreement comes to an end, all of the legal rights, obligations and liabilities that you and Google have benefited from, been subject to (or which have accrued over time whilst this License Agreement has been in force) or which are expressed to continue indefinitely, shall be unaffected by this cessation, and the provisions of paragraph 14.7 shall continue to apply to such rights, obligations and liabilities indefinitely.

10. DISCLAIMER OF WARRANTIES

10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE SDK IS AT YOUR SOLE RISK AND THAT THE SDK IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND FROM GOOGLE. 10.2 YOUR USE OF THE SDK AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SDK IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE. 10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

11. LIMITATION OF LIABILITY

11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.

12. Indemnification

12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from (a) your use of the SDK, (b) any application you develop on the SDK that infringes any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you with this License Agreement.

13. Changes to the License Agreement

13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available.

14. General Legal Terms

14.1 This License Agreement constitutes the whole legal agreement between you and Google and governs your use of the SDK (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the SDK. 14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in this License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google's rights and that those rights or remedies will still be available to Google. 14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of this License Agreement is invalid, then that provision will be removed from this License Agreement without affecting the rest of this License Agreement. The remaining provisions of this License Agreement will continue to be valid and enforceable. 14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party beneficiaries to this License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of this License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party beneficiaries to this License Agreement. 14.5 EXPORT RESTRICTIONS. THE SDK IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE SDK. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE. 14.6 The rights granted in this License Agreement may not be assigned or transferred by either you or Google without the prior written approval of the other party. Neither you nor Google shall be permitted to delegate their responsibilities or obligations under this License Agreement without the prior written approval of the other party. 14.7 This License Agreement, and your relationship with Google under this License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from this License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction. November 13, 2012

 

The official Android IDE

  • Android Studio IDE
  • Android SDK tools
  • Android 5.0 (Lollipop) Platform
  • Android 5.0 emulator system image with Google APIs
Download Android Studio

To get Android Studio or stand-alone SDK tools, visit developer.android.com/sdk/

Intelligent code editor

At the core of Android Studio is an intelligent code editor capable of advanced code completion, refactoring, and code analysis.

The powerful code editor helps you be a more productive Android app developer.

Code templates and GitHub integration

New project wizards make it easier than ever to start a new project.

Start projects using template code for patterns such as navigation drawer and view pagers, and even import Google code samples from GitHub.

Multi-screen app development

Build apps for Android phones, tablets, Android Wear, Android TV, Android Auto and Google Glass.

With the new Android Project View and module support in Android Studio, it's easier to manage app projects and resources.

Virtual devices for all shapes and sizes

Android Studio comes pre-configured with an optimized emulator image.

The updated and streamlined Virtual Device Manager provides pre-defined device profiles for common Android devices.

Android builds evolved, with Gradle

Create multiple APKs for your Android app with different features using the same project.

Manage app dependencies with Maven.

Build APKs from Android Studio or the command line.

More about Android Studio

Download Android Studio
  • Built on IntelliJ IDEA Community Edition, the popular Java IDE by JetBrains.
  • Flexible Gradle-based build system.
  • Build variants and multiple APK generation.
  • Expanded template support for Google Services and various device types.
  • Rich layout editor with support for theme editing.
  • Lint tools to catch performance, usability, version compatibility, and other problems.
  • ProGuard and app-signing capabilities.
  • Built-in support for Google Cloud Platform, making it easy to integrate Google Cloud Messaging and App Engine.

For more details about features available in Android Studio, read the guide to Android Studio Basics.

If you have been using Eclipse with ADT, be aware that Android Studio is now the official IDE for Android, so you should migrate to Android Studio to receive all the latest IDE updates. For help moving projects, see Migrating to Android Studio.

System Requirements

Windows

  • Microsoft® Windows® 8/7/Vista/2003 (32 or 64-bit)
  • 2 GB RAM minimum, 4 GB RAM recommended
  • 400 MB hard disk space
  • At least 1 GB for Android SDK, emulator system images, and caches
  • 1280 x 800 minimum screen resolution
  • Java Development Kit (JDK) 7
  • Optional for accelerated emulator: Intel® processor with support for Intel® VT-x, Intel® EM64T (Intel® 64), and Execute Disable (XD) Bit functionality

Mac OS X

  • Mac® OS X® 10.8.5 or higher, up to 10.9 (Mavericks)
  • 2 GB RAM minimum, 4 GB RAM recommended
  • 400 MB hard disk space
  • At least 1 GB for Android SDK, emulator system images, and caches
  • 1280 x 800 minimum screen resolution
  • Java Runtime Environment (JRE) 6
  • Java Development Kit (JDK) 7
  • Optional for accelerated emulator: Intel® processor with support for Intel® VT-x, Intel® EM64T (Intel® 64), and Execute Disable (XD) Bit functionality

On Mac OS, run Android Studio with Java Runtime Environment (JRE) 6 for optimized font rendering. You can then configure your project to use Java Development Kit (JDK) 6 or JDK 7.

Linux

  • GNOME or KDE desktop
  • GNU C Library (glibc) 2.11 or later
  • 2 GB RAM minimum, 4 GB RAM recommended
  • 400 MB hard disk space
  • At least 1 GB for Android SDK, emulator system images, and caches
  • 1280 x 800 minimum screen resolution
  • Oracle® Java Development Kit (JDK) 7

Tested on Ubuntu® 12.04, Precise Pangolin (64-bit distribution capable of running 32-bit applications).

Other Download Options

SDK Tools Only

If you prefer to use a different IDE or run the tools from the command line or with build scripts, you can instead download the stand-alone Android SDK Tools. These packages provide the basic SDK tools for app development, without an IDE. Also see the SDK tools release notes.

All Android Studio Packages

Select a specific Android Studio package for your platform. Also see the Android Studio release notes.

www.androiddocs.com

Устанавливаем и настраиваем Android SDK и Android Studio в Debian 8

Android является самой популярной, открытой операционной системой, основанной на ядре Linux. С каждым днём на него выходят всё больше и больше различных приложений, разработка которых весьма прибыльное занятие. Освоить разработку ПО под Андроид не сложно. В сети полным полно различной литературы, плюс куча официальной документации от Google (которая, забегая вперёд, идёт в комплекте с SDK).

SDK (Software Developmnet Kit) - комплект для разработки приложений. Он включает в себя необходимые системные библиотеки, документацию, драйверы, а также (в данном случае) - эмулятор Android для PC. SDK абсолютно бесплатен, и доступен на операционных системах Microsoft Windows, GNU/Linux и Mac OS X. Устанавливать его мы будем в Debian 8.1 "Jessie"

Первым делом нужно установить Java. Официально рекомендуется использовать Oracle JDK, но можно поставить и OpenJDK. Раньше с ним были серьёзные проблемы, тормоза. Но сейчас всё работает сносно. Опишу оба варианта. Выбор за вами.

OpenJDK

Чтобы поставить последнюю версию OpenJDK, сперва нужно подключить репозиторий Backports (если он у вас ещё не подключён). Открываем файл /etc/apt/sources.list и прописываем:

deb http://mirror.yandex.ru/debian jessie-backports main contrib non-freedeb-src http://mirror.yandex.ru/debian jessie-backports main contrib non-free

Далее обновляем список пакетов и ставим OpenJDK:

sudo apt-get updatesudo apt install openjdk-8-jdk openjdk-8-jre

Oracle JDK

Идём на сайт Oracle, где скачиваем архив, соответствующий разрадности вашей системы.

Сохраните его в домашнем каталоге. Далее открываем терминал:

cd /home/usernametar -xfv jdk-8u5-linux*sudo mkdir -p /usr/lib/jvm/jdk1.8.0/sudo mv jdk1.8.0_05/* /usr/lib/jvm/jdk1.8.0/ sudo update-alternatives --install "/usr/bin/java" "java" "/usr/lib/jvm/jdk1.8.0/bin/java" 1sudo update-alternatives --set java /usr/lib/jvm/jdk1.8.0/bin/java

После этого проверьте версию Java:

java -version

Должно быть примерно так:

java version "1.8.0_05"Java(TM) SE Runtime Environment (build 1.8.0_05-b13)Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)

Далее создадим ещё несколько символьных ссылок:

sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/lib/jvm/jdk1.8.0/bin/javac" 1sudo update-alternatives --set javac /usr/lib/jvm/jdk1.8.0/bin/javacsudo update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk1.8.0/bin/javaws" sudo update-alternatives --set javaws /usr/lib/jvm/jdk1.8.0/bin/javawssudo update-alternatives --install "/usr/bin/jar" "jar" "/usr/lib/jvm/jdk1.8.0/bin/jar" 1 sudo update-alternatives --set jar /usr/lib/jvm/jdk1.8.0/bin/jar

Вот и всё. Довольно муторно, но теперь все необходимые компоненты установлены. Осталось сделать ещё кое-что. Открываем ~/.bashrc и в конец прописываем путь к Java:

export JAVA_HOME=/usr/lib/jvm/jdk1.8.0

Сохраняем и вводим:

sudo update-alternatives --config java

Теперь нам нужно скачать Android SDK и Android Studio. Идём по ссылке, и скачиваем соответствующие архивы.

Архивы можно распаковать в любое, удобное для вас, место. Распакуем в каталог /opt:

cd /home/usernametar -xfv android-sdk_r24.3.3-linux.tgzsudo mv android-sdk-linux/* /opt/android-sdk-linux

Далее запустим менеджер:

/opt/android-sdk-linux/tools/android

Выбираем нужную версию API и жмём Install.

Android Studio скачиваем и аналогично распаковываем в /opt. Дополнительная настройка не требуется. Если вы используете OpenJDK, то при запуске выведится предупреждение, что лучше использовать JDK от Oracle. Для удобного запуска Android Studio, создадим ярлык на рабочем столе:

touch AndroidStudio.desktopnano AndroidStudio.desktop

Вписываем следующее:

[Desktop Entry]Encoding=UTF-8Terminal=0Exec=/opt/android-studio/bin/studio.shIcon=/opt/android-studio/bin/idea.pngType=ApplicationCategories=Development;StartupNotify=trueName=AndroidStudioGenericName=AndroidStudio

Сохраняем.

Если вы собираетесь писать приложения для Android на Qt, то можно настроить для этих целей Qt Creator. Он есть в стандартных репозиториях (или вы можете его скачать с официального сайта). Запустите его, перейдите в Инструменты - Параметры - Android и укажите путь к SDK.

На этом всё!

linuxoidblog.blogspot.ru


Смотрите также