in the toolbar.- Windows: Double-click the
SDK Manager.exefile at the root of the Android SDK directory.
@@ -77,7 +77,7 @@ style="vertical-align:bottom;margin:0;height:17px" /> in the toolbar.
To start adding packages, launch the Android SDK Manager in one of the following ways:
in the toolbar.SDK Manager.exe file at the root of the Android
SDK directory.When you open the SDK Manager for the first time, several packages will be selected by +
When you open the SDK Manager for the first time, several packages are selected by default. Leave these selected, but be sure you have everything you need to get started by following these steps:
diff --git a/docs/html/sdk/installing/index.jd b/docs/html/sdk/installing/index.jd index 45d189059706b..dc258db963c1e 100644 --- a/docs/html/sdk/installing/index.jd +++ b/docs/html/sdk/installing/index.jd @@ -87,7 +87,7 @@ where they are installed. For example:To set up Android Studio on Mac OSX:
@@ -97,13 +97,11 @@ where they are installed. For example:
Allow applications downloaded from, select Anywhere. Then open Android Studio again.The individual tools and other SDK packages are saved outside the Android Studio application -directory. If you need access the tools directly, use a terminal to navigate into the location -where they are installed. For example:
-/Applications/sdk/
If you need use the Android SDK tools from a command line, +you can access them at:
+/Users/<user>/Library/Android/sdk/
To set up Android Studio on Linux:
There are two ways to build your application using the Ant build script: one for - testing/debugging your application — debug mode — and one for building your - final package for release — release mode. Regardless of which way you build your application, - it must be signed before it can install on an emulator or device—with a debug key when building - in debug mode and with your own private key when building in release mode.
- -Whether you're building in debug mode or release mode, you need to use the Ant tool to compile - and build your project. This will create the .apk file that you can install on an emulator or device. - When you build in debug mode, the .apk file is automatically signed by the SDK tools with - a debug key, so it's instantly ready for installation onto an emulator or attached - development device. You cannot distribute an application that is signed with a debug key. - When you build in release mode, the .apk file is unsigned, so you - must manually sign it with your own private key, using Keytool and Jarsigner.
- -It's important that you read and understand Signing Your Applications, particularly once - you're ready to release your application and share it with end-users. That document describes the - procedure for generating a private key and then using it to sign your .apk file. If you're just - getting started, however, you can quickly run your applications on an emulator or your own - development device by building in debug mode.
- -If you don't have Ant, you can obtain it from the Apache Ant - home page. Install it and make sure it is in your executable PATH. Before calling Ant, you - need to declare the JAVA_HOME environment variable to specify the path to where the JDK is - installed.
- -Note: When installing JDK on Windows, the default is to install
- in the "Program Files" directory. This location will cause ant to fail, because of
- the space. To fix the problem, you can specify the JAVA_HOME variable like this:
-
set JAVA_HOME=c:\Progra~1\Java\<jdkdir>- -
The easiest solution, however, is to install JDK in a non-space directory, for example:
- -c:\java\jdk1.7- -
For immediate application testing and debugging, you can build your application in debug mode - and immediately install it on an emulator. In debug mode, the build tools automatically sign your - application with a debug key and optimize the package with {@code zipalign}.
- -To build in debug mode:
- --ant debug -- -
This creates your debug .apk file inside the project bin/ directory, named
- <your_project_name>-debug.apk. The file is already signed with
- the debug key and has been aligned with
- zipalign.
-
Each time you change a source file or resource, you must run Ant again in order to package up - the latest version of the application.
- -To install and run your application on an emulator, see the following section about Running on the Emulator.
- -When you're ready to release and distribute your application to end-users, you must build your - application in release mode. Once you have built in release mode, it's a good idea to perform - additional testing and debugging with the final .apk.
- -Before you start building your application in release mode, be aware that you must sign the - resulting application package with your private key, and should then align it using the {@code - zipalign} tool. There are two approaches to building in release mode: build an unsigned package - in release mode and then manually sign and align the package, or allow the build script to sign - and align the package for you.
- -If you build your application unsigned, then you will need to manually sign and align - the package.
- -To build an unsigned .apk in release mode:
- --ant release --
This creates your Android application .apk file inside the project bin/
- directory, named <your_project_name>-unsigned.apk.
Note: The .apk file is unsigned at this point and can't - be installed until signed with your private key.
- -Once you have created the unsigned .apk, your next step is to sign the .apk with your private - key and then align it with {@code zipalign}. To complete this procedure, read Signing Your Applications.
- -When your .apk has been signed and aligned, it's ready to be distributed to end-users.
- You should test the final build on different devices or AVDs to ensure that it
- runs properly on different platforms.
If you would like, you can configure the Android build script to automatically sign and align - your application package. To do so, you must provide the path to your keystore and the name of - your key alias in your project's {@code ant.properties} file. With this information provided, - the build script will prompt you for your keystore and alias password when you build in release - mode and produce your final application package, which will be ready for distribution.
- -Caution: Due to the way Ant handles input, the password that - you enter during the build process will be visible. If you are concerned about - your keystore and alias password being visible on screen, then you may prefer to perform the - application signing manually, via Jarsigner (or a similar tool). To instead perform the signing - procedure manually, build unsigned and then continue with - Signing Your Applications.
- -To specify your keystore and alias, open the project {@code ant.properties} file (found in - the root of the project directory) and add entries for {@code key.store} and {@code key.alias}. - For example:
--key.store=path/to/my.keystore -key.alias=mykeystore -- -
Save your changes. Now you can build a signed .apk in release mode:
- --ant release --
Caution: As described above, your password will be - visible on the screen.
-This creates your Android application .apk file inside the project bin/
- directory, named <your_project_name>-release.apk. This .apk file has
- been signed with the private key specified in {@code ant.properties} and aligned with {@code
- zipalign}. It's ready for installation and distribution.
Once you have signed your application with a private key, you can install and run it on an - emulator or device. You can - also try installing it onto a device from a web server. Simply upload the signed .apk to a web - site, then load the .apk URL in your Android web browser to download the application and begin - installation. (On your device, be sure you have enabled - Settings > Applications > Unknown sources.)
- -Before you can run your application on the Android Emulator, you must create an AVD.
- -To run your application:
- -From your SDK's platform-tools/ directory, execute the {@code android} tool
-with the avd options:
-android avd -- -
In the Virtual Devices view, select an AVD and click Start.
-From your SDK's tools/ directory, install the {@code .apk} on the
- emulator:
-adb install <path_to_your_bin>.apk -- -
Your .apk file (signed with either a release or debug key) is in your project {@code bin/} - directory after you build your application.
- -If there is more than one emulator running, you must specify the emulator upon which to
- install the application, by its serial number, with the -s option. For
- example:
-adb -s emulator-5554 install path/to/your/app.apk -- -
To see a list of available device serial numbers, execute {@code adb devices}.
-If you don't see your application on the emulator, try closing the emulator and launching the - virtual device again from the AVD Manager. Sometimes when you install an application for the - first time, it won't show up in the application launcher or be accessible by other applications. - This is because the package manager usually examines manifests completely only on emulator - startup.
- -Be certain to create multiple AVDs upon which to test your application. You should have one - AVD for each platform and screen type with which your application is compatible. For instance, if - your application compiles against the Android 4.0 (API Level 14) platform, you should create an - AVD for each platform equal to and greater than 4.0 and an AVD for each screen type you support, then test your - application on each one.
- -Tip: If you have only one emulator running, you can
- build your application and install it on the emulator in one simple step. Navigate to the root of
- your project directory and use Ant to compile the project with install mode: ant
- install. This will build your application, sign it with the debug key, and install it on
- the currently running emulator.
Before you can run your application on a device, you must perform some basic setup for your - device:
- -Note: On Android 4.2 and newer, Developer - options is hidden by default. To make it available, go - to Settings > About phone and tap Build number - seven times. Return to the previous screen to find Developer options.
-Read Setting up a Device for - Development for more information.
- -Once your device is set up and connected via USB, navigate to your SDK's platform-tools/
- directory and install the .apk on the device:
-adb -d install path/to/your/app.apk -- -
The {@code -d} flag specifies that you want to use the attached device (in case you also have - an emulator running).
- -For more information on the tools used above, please see the following documents:
- -As you begin developing Android applications, understand that all Android applications must be - digitally signed before the system will install them on an emulator or device. There are two ways - to do this: with a debug key (for immediate testing on an emulator or development - device) or with a private key (for application distribution).
- -The Android build tools help you get started by automatically signing your .apk files with a - debug key at build time. This means that you can compile your application and install it on the - emulator without having to generate your own private key. However, please note that if you intend - to publish your application, you must sign the application with your own private - key, rather than the debug key generated by the SDK tools.
- -The ADT plugin helps you get started quickly by signing your .apk files with a debug key, - prior to installing them on an emulator or development device. This means that you can quickly - run your application from Eclipse without having to generate your own private key. No specific - action on your part is needed, provided ADT has access to Keytool. However, please note that if - you intend to publish your application, you must sign the application with your - own private key, rather than the debug key generated by the SDK tools.
- -Please read Signing Your - Applications, which provides a thorough guide to application signing on Android and what it - means to you as an Android application developer. The document also includes a guide to exporting - and signing your application with the ADT's Export Wizard.
- -ant cleanall target before clean
-(ant all clean), other projects are also cleaned. For instance if you clean a
-test project, the tested project is also cleaned.ant debugant emma debugant releaseant instrument
- emma
- target)ant <build_target> installinstall by itself fails.ant installd.apk is not
- already built.ant installr.apk is not
- already built.ant installt.apk of the
- tested application. This fails if the .apk is not already built.ant installi.apk is not already
- built.ant test.apk files must be
- previously installed.ant debug installt test.apk files, and
- runs the tests.ant emma debug install test.apk files, and
- runs the tests with code coverage enabled.This document shows you how to run your application on an emulator or a real device from Eclipse—all of which is done using the debug version of your application. For more information about how to sign your application with a private key for release, see Signing Your Applications
+ "{@docRoot}tools/publishing/app-signing.html#ExportWizard">Signing Your ApplicationsBefore you can run your application on the Android Emulator, you must create an AVD.
+ "{@docRoot}tools/devices/managing-avds.html">create an AVD.To run (or debug) your application, select Run > Run (or Run > Debug) from the Eclipse menu bar. The ADT plugin will @@ -100,7 +100,7 @@ parent.link=index.html
Read Using Hardware Devices +
Read Using Hardware Devices for more information.
Once set up and your device is connected via USB, install your application on the device by diff --git a/docs/html/training/basics/firstapp/creating-project.jd b/docs/html/training/basics/firstapp/creating-project.jd index 79268a00eba33..4bd92ee751459 100644 --- a/docs/html/training/basics/firstapp/creating-project.jd +++ b/docs/html/training/basics/firstapp/creating-project.jd @@ -24,8 +24,6 @@ next.link=running-app.html
An Android project contains all the files that comprise the source code for your Android -app. The Android SDK tools make it easy to start a new Android project with a set of -default project directories and files.
+app.This lesson shows how to create a new project either using Android Studio or using the diff --git a/docs/html/training/basics/firstapp/index.jd b/docs/html/training/basics/firstapp/index.jd index 1b6e00f39c224..4e3689a3e7b6b 100644 --- a/docs/html/training/basics/firstapp/index.jd +++ b/docs/html/training/basics/firstapp/index.jd @@ -12,7 +12,7 @@ helpoutsWidget=true
Note: Make sure you install the most recent versions of Android -Studio and the Android SDK before you start this class. The procedures described in this class may -not apply to earlier versions.
+Note: Although most of this training class +expects that you're using Android Studio, some procedures include alternative +instructions for using +the SDK tools from the command line instead.
-If you haven't already done these tasks, start by downloading the - Android SDK and following the install steps. - Once you've finished the setup, you're ready to begin this class.
- -This class uses a tutorial format that incrementally builds a small Android app that teaches +
This class uses a tutorial format to create a small Android app that teaches you some fundamental concepts about Android development, so it's important that you follow each step.
diff --git a/docs/html/training/basics/firstapp/running-app.jd b/docs/html/training/basics/firstapp/running-app.jd index fdf0d1f59a534..6e4605f003750 100644 --- a/docs/html/training/basics/firstapp/running-app.jd +++ b/docs/html/training/basics/firstapp/running-app.jd @@ -25,7 +25,7 @@ helpoutsWidget=true
- Figure 1. The AVD Manager showing a virtual device.
-When you select a device type, most of the fields auto-populate.
-It really doesn't matter what you enter here since you're not using any storage. But if you - reuse this AVD, you might have to adjust this setting.
For more information about using AVDs, see +Managing AVDs with AVD Manager.
+