Софт-Архив

Android sdk tools

Рейтинг: 5.0/5.0 (827 проголосовавших)

Категория: Windows: Эмуляторы

Описание

Android SDK 24

Android SDK 24.4.1

The Android SDK is composed of modular packages that you can download separately using the Android SDK Manager. For example, when the SDK Tools are updated or a new version of the Android platform is released, you can use the SDK Manager to quickly download them to your environment. Simply follow the procedures described in Adding Platforms and Packages.

There are several different packages available for the Android SDK. The table below describes most of the available packages and where they're located once you download them.

  • SDK Tools
    • Contains tools for debugging and testing, plus other utilities that are required to develop an app. If you've just installed the SDK starter package, then you already have the latest version of this package. Make sure you keep this up to date.
  • SDK Platform-tools
    • Contains platform-dependent tools for developing and debugging your application. These tools support the latest features of the Android platform and are typically updated only when a new platform becomes available. These tools are always backward compatible with older platforms, but you must be sure that you have the latest version of these tools when you install a new SDK platform.
  • Documentation
    • An offline copy of the latest documentation for the Android platform APIs.
  • SDK Platform
    • There's one SDK Platform available for each version of Android. It includes an android.jar file with a fully compliant Android library. In order to build an Android app, you must specify an SDK platform as your build target.
  • System Images
    • Each platform version offers one or more different system images (such as for ARM and x86). The Android emulator requires a system image to operate. You should always test your app on the latest version of Android and using the emulator with the latest system image is a good way to do so.
  • Sources for Android SDK
    • A copy of the Android platform source code that's useful for stepping through the code while debugging your app.
  • Samples for SDK
    • A collection of sample apps that demonstrate a variety of the platform APIs. These are a great resource to browse Android app code. The API Demos app in particular provides a huge number of small demos you should explore.
  • Google APIs
    • An SDK add-on that provides both a platform you can use to develop an app using special Google APIs and a system image for the emulator so you can test your app using the Google APIs.
  • Android Support
    • A static library you can include in your app sources in order to use powerful APIs that aren't available in the standard platform. For example, the support library contains versions of the Fragment class that's compatible with Android 1.6 and higher (the class was originally introduced in Android 3.0) and the ViewPager APIs that allow you to easily build a side-swipeable UI.
  • Google Play Billing
    • Provides the static libraries and samples that allow you to integrate billing services in your app with Google Play.
  • Google Play Licensing
    • Provides the static libraries and samples that allow you to perform license verification for your app when distributing with Google Play.

Download links for previous version 24.3.4:

Software that can be used as an alternative to Android SDK.

Android sdk tools:

  • скачать
  • скачать
  • Другие статьи, обзоры программ, новости

    Android SDK 24

    Android SDK 24.4.1

    installer_r24.4.1-windows.exe

    Android SDK is the official software development package for developers who want to create Android applications that can take full advantage from entire Android hardware and software ecosystem. With fully integrated software stack that enables seamless access to SDK tools, plugins and utilities, anyone can easily start producing your first Android applications. The core parts of Android SDK including Tools, Android Platform Tools, latest Android platform, and latest Android system image for emulator are already included in the package. However, according to your own requirements, you can change system images and create your application for any android OS version you require.

    With Android SDK, programmers get immediate access to all the necessary tools for planning, building, testing, debugging and profiling apps for Android. Offline documentation is provided, but you can also contact large online community and Android SDK developers for help, tutorials and hint that will make your project run more smoothly. Additionally, you also get access to copy of the Android platform source code, which can make your debugging much more easier.

    Android SDK Features:

    Contains tools for debugging and testing, plus other utilities that are required to develop an app. If you've just installed the SDK starter package, then you already have the latest version of this package. Make sure you keep this up to date.

    SDK Platform-tools

    Contains platform-dependent tools for developing and debugging your application. These tools support the latest features of the Android platform and are typically updated only when a new platform becomes available. These tools are always backward compatible with older platforms, but you must be sure that you have the latest version of these tools when you install a new SDK platform.

    Documentation

    An offline copy of the latest documentation for the Android platform APIs.

    SDK Platform

    There's one SDK Platform available for each version of Android. It includes an android.jar file with a fully compliant Android library. In order to build an Android app, you must specify an SDK platform as your build target.

    System Images

    Each platform version offers one or more different system images (such as for ARM and x86). The Android emulator requires a system image to operate. You should always test your app on the latest version of Android and using the emulator with the latest system image is a good way to do so.

    Sources for Android SDK

    A copy of the Android platform source code that's useful for stepping through the code while debugging your app.

    Android Overview Tutorial: Development Environment

    Android Overview Tutorial: Development Environment

    Developers (using Java) need to use the Android SDK in order to build Android apps. As for the development environment, Google recommends developers to use the Eclipse IDE along with the ADT Plugin for Android development. This section talks about how to install the Android SDK, Eclipse IDE and the ADT Plugin in order to complete the Android development environment setup

    Android SDK Android SDK Download

    The Android SDK can be downloaded free from the Android Developer website. The Android SDK is available for Windows, Mac OS X and Linux platforms. For Windows, Google recommends downloading the Android SDK installer .

    Android SDK Tools Setup

    Once you’ve downloaded the installer, launch the Android SDK Tools Setup as shown below.

    The installer tries to detect a valid Java Development Kit installation (JDK) on your computer. If you do not have a JDK installed, you can download it from the Oracle Java Downloads page.

    In the next step, the installer prompts you to choose the location where to install the Android SDK. Unless you want to use another drive/ directory, it is recommended that you use the standard path chosen by the installer as shown below.

    In the next step, the installer prompts you to confirm whether you want to create a Start Menu folder for Android SDK Tools.

    If you do not want to create a shortcut, check the ‘Do not create shortcuts’ checkbox as shown below.

    Once you click ‘Next’, the installer copies the required files and creates the required shortcuts on your computer.

    That’s it – the Android SDK Tools installer has completed and the next step is to run the SDK Manager to download appropriate Android SDK.

    Android SDK Manager

    The Android SDK Manager shows a listing of various Android SDKs (along with corresponding API levels) and their installation status. By default, it will show the ‘Android SDK Tools’ as Installed and all other components as Not Installed.

    Unless you want to develop for a specific Android version, it is recommended to choose the latest Android SDK (4.0 in this case). Click the ‘Install 6 packages’ button in order to start installing the appropriate SDK. The Installer will list the various components chosen for installation and prompt you to accept the license terms as shown below.

    Click on the ‘Install’ button to start the SDK installation. The installer shows a progress bar reflecting the status of installation as well as the expected completion time.

    You can see the installation logs by clicking on the log window icon at the bottom right of the window.

    Once the installation completes, it will prompt you to restart ADB.

    Click on ‘Yes’ and the log window will show that the Android SDK installation has been completed successfully. Click the Close button in order to exit the installer.

    Installing Eclipse

    Most Java developers are familiar with Eclipse. The installation of Eclipse is beyond the scope of this tutorial. If you do not have Eclipse already installed on your computer, download the ‘Eclipse IDE for Java Developers ‘ installer and follow the standard installation steps.

    Installing ADT Plugin for Eclipse

    Google provides the Android Development Tools (ADT) plugin for Eclipse IDE for Java developers as it provides a powerful, integrated environment in which to build Android applications. ADT provides several useful tools including build, debug, and simulation of your Android apps. The system requirements for installing ADT Plugin are listed on the System Requirements page on Android Developer website.

    In order to install ADT, launch Eclipse and select the Help -> Install New Software option as shown below.

    Click the ‘Add’ button on the subsequent screen.

    Add the following values on the ‘Add Repository’ popup.

    Once you click the ‘OK’ button, Eclipse fetches the ADT Plugin information from the specified URL. It provides a list of tools available for installation as shown below.

    Select the ‘Developer Tools’ and click the ‘Next’ button to begin the ADT plugin installation. The installer then calculates dependencies and generates a list of components that will be installed as shown below.

    Click on ‘Next’ and then check the ‘I accept the terms of the license agreement’ radio button to continue the installation.

    Click on ‘Finish’ to proceed. The installer will show a progress bar indicating the installation status as shown below.

    Eclipse may prompt you that you’re installing software that contains unsigned content. Click ‘OK’ to continue the installation.

    Once the installation completes, the installer will prompt you to restart Eclipse.

    Restart Eclipse and that’s it – your ADT plugin is installed.

    Урок 2

    Урок 2. Установка Android Studio

    Подробности Создано 28.07.2011 01:56 Автор: damager82

    Для того, чтобы писать программы - нужна среда разработки. В этом уроке мы подробно рассмотрим, как установить и настроить эту среду разработки.

    Я буду описывать установку применимо к операционной системе Windows 7.

    Урок обновлен 02.02.2015

    В этой статье много скриншотов и инструкций. Учитывайте, что версии ПО постоянно меняются и у вас все может выглядеть по-другому и версии могут быть другими.

    1. Java SDK (JDK)

    Т.к. разработка приложений ведется на Java, нам нужно скачать и установить соответствующее SDK, называемое еще JDK (если, конечно, оно уже не установлено).

    Скачать можно здесь. Нажимайте там ближайшую кнопку JDK Download. выбирайте версию под вашу операционную систему, скачивайте и устанавливайте. Если ссылка не работает, то просто гуглите "java sdk download".

    После установки рекомендую перезагрузить комп.

    2. Среда разработки

    В среде разработки мы будем создавать программу и получать на выходе готовое приложение. Сейчас существует несколько сред разработки, мы выберем рекомендуемую гуглом Android Studio. Скачать его можно здесь. Жмете большую зеленую кнопку Download Android Studio for Windows. если у вас Windows. Если у вас другая операционная система, то жмите Other Download Options и выбирайте нужный вам файл из таблицы All Android Studio Packages .

    Итак, скачали exe-файл. Запускаем его. Жмем Next, пока не он не спросит пути.

    От нас требуется указать два пути. Первый путь будет использован для установки Android Studio. Второй - для установки Android SDK (о нем подробнее поговорим чуть дальше).

    Давайте заменим их на свои. Для этого с оздадим каталог android. На всякий случай сделайте так, чтобы путь к нему был без пробелов и русских символов. Например - <имя диска>:\android. У меня это будет F:\android. И этот путь подставим в визард.

    Жмем несколько раз Next, пока не начнется установка. Когда установка закончится, запустится Android Studio. Если не запустилась, то ищите ее ярлык в Пуске.

    Первым делом она спросит, не надо ли импортировать настройки с прошлой версии.

    Оставляем выбранным нижний пункт и жмем Ок. У нас пока нет старых настроек.

    Далее выполнится поиск и установка недостающих компонентов и обновлений.

    3. Android SDK

    Для разработки и тестирования приложений нам понадобятся SDK-платформы Android. В открывшемся стартовом окне Android Studio жмите пункт Configure

    и далее SDK Manager

    Открылся SDK Manager

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

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

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

    Нажмите снизу ссылку Deselect All . чтобы снять все галки, а затем Updates . чтобы выделить только те пункты, которые требуют обновления. И пока оставим все так, ничего не загружаем.

    Нас сейчас интересуют папки с именами версий Android. На текущий момент последняя доступная версия - Android 5.0.1 (API 21). (Когда вы будете читать урок, скорее всего уже будет более свежая версия, используйте ее для выполнения последующих инструкций).

    Как минимум для разработки нам необходимы два компонента в этой папке:

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

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

    Т.е. мы сможем создать приложение, использующее компоненты и возможности Android версии 5.0.1 и запустить это приложение на эмуляторе версии 5.0.1. Этого вполне достаточно для начала. Ставьте галки на двух этих пунктах в папке Android 5.0.1 (API 21). В моем случае SDK Platform уже установлен (статус Installed напротив пункта SDK Platform), поэтому я ставлю галку только для образа.

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

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

    Появится окно со списком установки (у вас может быть другое содержимое)

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

    В процессе может выскочить такое окно:

    Жмем ОК. Это он предложил нам переоткрыть окно AVD Manager (про которое мы пока ничего не знаем). Также, он предложил нам проверить обновления для Eclipse. Но у нас не Eclipse, а Android Studio. Поэтому игнорируем.

    После выполнения этих шагов мы получили среду разработки, с помощью которой можно кодить Android-приложения. Возможно, эти действия покажутся мутными и скучными, но без них никак. Дальше дело пойдет веселей. Если что-то не получается или выдает ошибку - попробуйте посмотреть форум или погуглить, наверняка вы не первый сталкиваетесь с такой проблемой и в сети уже есть описание решения.

    По идее, в SDK Manager надо заглядывать периодически и проверяться на обновления. Но иногда с этими обновлениями бывают проблемы и приходится расчехлять гугл и бубен, чтобы все поправить. Поэтому я, пожалуй, не буду вам рекомендовать обновляться) Тут очень подходит принцип "работает - не трогай". И если пока нет опыта, то лучше не рисковать.

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

    На следующем уроке мы настроим Android Virtual Device (AVD), создадим наше первое приложение и запустим его. AVD – это эмулятор смартфона с операционной системой Android, на котором можно запускать и тестировать приложения. Не подключать же свой смартфон каждый раз. Также мы рассмотрим структуру проекта приложения.

    Unity - Manual: Android SDK Setup

    Android SDK Setup

    There are some steps you must follow before you can build and run any code on your Android device. This is true regardless of whether you use Unity or write Android applications from scratch.

    1. Download the Android SDK

    Go to the Android Developer SDK webpage. Download and unpack the latest Android SDK.

    2. Installing the Android SDK

    Follow the instructions under Installing the SDK (although you can freely skip the optional parts relating to Eclipse). In step 4 of Installing the SDK be sure to add at least one Android platform with API level equal to or higher than 9 (Platform 2.3 or greater), the Platform Tools. and the USB drivers if you’re using Windows.

    3. Get the device recognized by your system

    This can be tricky, especially under Windows based systems where drivers tend to be a problem. Also, your device may come with additional information or specific drivers from the manufacturer.

    For Windows. If the Android device is automatically recognized by the system you still might need to update the drivers with the ones that came with the Android SDK. This is done through the Windows Device Manager. —>If the device is not recognized automatically use the drivers from the Android SDK, or any specific drivers provided by the manufacturer. —>Additional info can be found here: USB Drivers for Windows

    For Mac. If you’re developing on Mac OSX then no additional drivers are usually required.

    Note: Don’t forget to turn on “USB Debugging” on your device. Go to Settings -> Developer options. then enable USB debugging. As of Android Jelly Bean 4.2 the Developer options are hidden by default. To enable them tap on Settings -> About Phone -> Build Version multiple times. Then you will be able to access the Settings -> Developer options .

    If you are unsure whether your device is properly installed on your system, please read the trouble-shooting page for details.

    4. Add the Android SDK path to Unity

    The first time you build a project for Android (or if Unity later fails to locate the SDK) you will be asked to locate the folder where you installed the Android SDK (you should select the root folder of the SDK installation). The location of the Android SDK can also be changed in the editor by selecting Unity > Preferences from the menu and then clicking on External Tools in the preferences window.

    Getting Started with Android Development

    AndroidSDK - Community Help Wiki

    Preparation and Installation

    Before we set up the SDK, we have some preparation to do. Due to some major changes in the Android SDK made in the last couple of months, setting up the Android SDK is not as easy as it was two years ago, when Android was starting to take off. Setting up the SDK itself is relatively easy once the preparation has been done.

    Downloading the SDK Starter Package

    First things first, we have to obtain the starter package. The SDK starter package can be obtained at http://developer.android.com/sdk/index.html.

    Download the one for Linux (.tgz file) and once it's finished downloading, extract it to somewhere safe and easy to reach. For example, the home folder. To do so, open up a terminal, navigate to the directory where the SDK was downloaded and enter the following command:

    As of 12 May 2012, the Android SDK is currently up to r18, however that is set to change in the near future, and as such, replace XX with the version of your SDK.

    Setting up Java

    Prior to SDK r08, everything you'll need to develop applications was included on a 100-200MB .tgz archive. However, with the release of SDK r08, the tools necessary for creating and building applications was removed and can be obtained by using the Android SDK and AVD Manager which is located in the /<sdk>/tools folder.

    However, you should not execute the Android SDK and AVD manager just yet, as you'll most likely get a Parse: XML error notice. The reason for this is that after SDK r08, it's now required to have Java installed before you set up the SDK. To do this, we'll download the OpenJDK and the Icedtea browser plugin. In a terminal window, enter the following command:

    How to fix: Android SDK manager failing to open in Android Development Tools Bundle

    How to Fix. Android SDK Manager failing to open in Android Development Tools Bundle

    Some times you might encounter an issue with the Android Development Tools bundle where the Android SDK  manager fails to open or closes immediately after showing a command prompt like window. Fortunately it is really easy to solve.

    Go to [sdk-folder]/tools folder (For me it was C:\adt-bundle-windows-x86_64-20130522\sdk\tools).

    Open the file android.bat  in notepad by right clicking on it and selecting Edit  from the context menu.

    Find the line in the file that says java_exe .

    Now edit the “set java_exe= ” line to

    set java_exe="C:\Program Files\Java\jre7\bin\java.exe"

    Here “C:\Program Files\Java\jre7\bin\java.exe” is the path where the java.exe file for the JRE is installed. You should check your Java executable location and change the line accordingly.

    Now save the file and close it.  To test it out, in Eclipse go to Window > Android SDK Manager.

    Android SDK

    The Android SDK allows for integration with programming IDEs such as Eclipse, interaction with testing devices via ADB, as well as emulation of various platforms and software/hardware configurations via the Android Emulator. Physical device testing is highly recommended as emulation of the ARM processor on an x86 processor is extremely slow, especially with Honeycomb and Ice Cream Sandwich, which make use of hardware graphics acceleration. Further details are available on the Android SDK website.

    Outside of app development, its most common use is for two programs it includes: adb and fastboot.

    ADB, or Android Debug Bridge, is a multi-purpose tool created to allow interaction with Android devices over TCP/IP and USB. It allows for the sending (push) or receiving (pull) of files, pulling of system logs (logcat), starting a terminal (shell), mounting the system partition as read-write (remount), forwarding socket connections (tunneling), installing and uninstalling APKs, and backing up or restoring data.

    ADB runs as a client-server configuration, with a server that maintains the connection to a device, and a client that the user sends commands through. This is important, because if ADB is not installed properly on a Linux-based operating system, the ADB server will have to be started prior to use with sudo adb start-server.

    ADB does not require root access, except with the adb remount command.

    The following are commands usable via ADB:

    A simple diagnostic command, adb devices will list the serial numbers of any devices the ADB server is currently connected to.

    Note. If multiple devices are currently connected, use the -p (serial number) flag to specify which device you wish to execute the command to.

    Pushing is used to send files from the computer, to a connected Android device. The syntax is very simple: adb push (local file/folder) (device file/folder)

    For example, to push file.bin from the folder that the command prompt is currently in, to the directory /data/local on a device, one would simply use adb push file.bin /data/local/

    Pulling is similar to pushing but operates in reverse: It copies files from the device, to the computer. adb pull (device file/folder) (local file/folder)

    Specifying the local file and/or folder name is optional. If omitted, whatever directory the command prompt is currently in will be used instead, and file names will stay the same as they were on the device.

    Logcat is one of the most commonly used ADB commands. It outputs the system log from the connected device to the terminal window in real-time. For easier bug reports, the logcat can be outputted to a file: adb logcat > logcat.txt

    Frequently developers will ask for a logcat if an app has force-closed (created an ANR or App Not Responding dialog) or experienced another bug. The easiest way to is either provide them with the raw logcat file, or to copy the contents of the file to a public pastebin such as Pastebin.com. It is recommended that if you do so, specify the Paste Exposure as Unlisted, and have the paste expire after a reasonable amount of time. Otherwise, your paste may be logged by Google, and could potentially reveal sensitive information if another app has logged such data.

    Alternatively, the adb bugreport command can be used to get additional data.

    The adb shell command can be used to start an interactive shell session on the device. However, it will be limited by the capabilities of the command prompt it is open in, and the default shell on the device.

    Alternatively, adb shell can be used to specify a command to execute on the device. For example, to set the permissions on a file to be executable and readable by all users, and writable by the owner: adb shell chmod 0755 /data/local/file.bin

    adb remount can be used to re-mount the /system partition (which contains the Android system software) as writable by ADB and other root-using applications. However, it will not function if the system partition is protected by the bootloader (NAND lock), if root access is not available, or if root is not available by default to an adb shell session.

    The manual method of adb remount is:

    1. adb shell
    2. su
    3. mount -o remount,rw /system
    4. exit
    Install/Uninstall

    ADB can also be used to install APK (Android application packages) files on a device: adb install MyAmazingApp-1.0-signed.apk

    Various flags are available to specify additional options, such as the -r flag to reinstall an app and not remove its data, or -s to force installation to an SD card or external storage (if applicable).

    It can likewise be used to uninstall an app via its package name: adb uninstall com.example.amazingapp. The -k flag is available to specify that the app's cache and data should not be erased.

    Fastboot is a tool used to install raw partition images on Android devices via their bootloader, as well as interact with the bootloader directly, performing actions such as unlocking, deleting contents of permissions, booting off of partition images without overwriting installed partition data, and performing an RUU (ROM Update Utility) task. Like ADB, the -s (serial number) flag is available to specify what device Fastboot should communicate to if multiple devices are detected. However, unlike ADB, Fastboot can only operate via USB due to the fact that a device's bootloader does not run the Linux kernel, nor Android, meaning that it cannot manage nor connect to a WiFi, cellular, or other wireless network.

    Similar to ADB Devices. fastboot devices shows all of the devices Fastboot recognizes as being in their respective fastboot modes, usually an option within the bootloader.

    fastboot flash is used to install a raw image to a partition on a device. It can be used to flash kernels, custom recoveries, radio basebands, bootloaders, or entire system or data partitions. Its usage is simple: fastboot flash (partition) (file).

    For example, to flash ClockworkMod Touch Recovery 5.8.0.2 for the Samsung Galaxy Nexus (toro). one would cd to the directory which the image file has been downloaded, and run fastboot flash recovery recovery-clockwork-touch-5.8.0.2-toro.img.

    Some common partition names: recovery, boot, radio, radio-cdma, bootloader, system, userdata, cache, and wimax.

    fastboot erase is very straight-forward: It erases the specified partition. Example: fastboot erase cache will erase the contents of the /cache partition.

    fastboot boot is one of the most useful tools for kernel or custom recovery developers. It allows the device to boot off of, but not install, a custom kernel or recovery. This way, if there is a problem with the kernel or recovery, the device can simply be rebooted, and it will revert to the installed version.

    Syntax is very simple: fastboot boot (file) where (file) is the kernel or recovery image (also sometimes called a zImage). It must be in the same folder that the command prompt is currently open in, or else the path to it must be specified (eg, fastboot boot

    /Downloads/kernel.img

    OEM commands are proprietary commands created by the device's manufacturer. The most famous of which is fastboot oem unlock which unlocks a Nexus device's bootloader to allow the flashing of partitions, and its opposite, fastboot oem lock which re-locks the bootloader. HTC also uses the fastboot oem command for use with their HTCDev bootloader unlocking program.