diff options
Diffstat (limited to 'docs/html/tools')
22 files changed, 1363 insertions, 750 deletions
diff --git a/docs/html/tools/adk/adk.jd b/docs/html/tools/adk/adk.jd index 1651747..7e75c11 100644 --- a/docs/html/tools/adk/adk.jd +++ b/docs/html/tools/adk/adk.jd @@ -1,5 +1,5 @@ page.title=Accessory Development Kit 2011 Guide -page.tags="adk" +page.tags=adk @jd:body <div id="qv-wrapper"> diff --git a/docs/html/tools/adk/adk2.jd b/docs/html/tools/adk/adk2.jd index c60e920..d69125a 100644 --- a/docs/html/tools/adk/adk2.jd +++ b/docs/html/tools/adk/adk2.jd @@ -1,5 +1,5 @@ page.title=Accessory Development Kit 2012 Guide -page.tags="adk" +page.tags=adk @jd:body <div id="qv-wrapper"> diff --git a/docs/html/tools/adk/index.jd b/docs/html/tools/adk/index.jd index e035115..e08748fc 100644 --- a/docs/html/tools/adk/index.jd +++ b/docs/html/tools/adk/index.jd @@ -1,5 +1,5 @@ page.title=Accessory Development Kit -page.tags="adk" +page.tags=adk @jd:body <p>The Accessory Development Kit (ADK) is a reference implementation for hardware manufacturers and diff --git a/docs/html/tools/debugging/debugging-memory.jd b/docs/html/tools/debugging/debugging-memory.jd index a7f443c..fccb67e 100644 --- a/docs/html/tools/debugging/debugging-memory.jd +++ b/docs/html/tools/debugging/debugging-memory.jd @@ -1,5 +1,5 @@ page.title=Investigating Your RAM Usage -page.tags="memory","OutOfMemoryError" +page.tags=memory,OutOfMemoryError @jd:body <div id="qv-wrapper"> @@ -492,4 +492,4 @@ the Home screen, then return to your app).</li> <p class="note"><strong>Tip:</strong> You can also perform the above steps by using the "monkey" test framework. For more information on running the monkey test framework, read the <a href= "{@docRoot}tools/help/monkeyrunner_concepts.html">monkeyrunner</a> -documentation.</p>
\ No newline at end of file +documentation.</p> diff --git a/docs/html/tools/device.jd b/docs/html/tools/device.jd index a1fb817..89b3857 100644 --- a/docs/html/tools/device.jd +++ b/docs/html/tools/device.jd @@ -5,6 +5,7 @@ page.title=Using Hardware Devices <div id="qv"> <h2>In this document</h2> <ol> + <li><a href="#device-developer-options">Enabling On-device Developer Options</a></li> <li><a href="#setting-up">Setting up a Device for Development</a> <ol> <li><a href="#VendorIds">USB Vendor IDs</a></li> @@ -30,9 +31,8 @@ device directly from Eclipse or from the command line with ADB. If you don't yet have a device, check with the service providers in your area to determine which Android-powered devices are available.</p> -<p>If you want a SIM-unlocked phone, then you might consider a Nexus phone. To find a place -to purchase the Nexus S and other Android-powered devices, visit <a -href="http://www.google.com/phone/detail/nexus-s">google.com/phone</a>.</p> +<p>If you want a SIM-unlocked phone, then you might consider a Nexus phone. To purchase a +Nexus phone, visit the <a href="https://play.google.com/store/devices">Google Play</a> store.</p> <p class="note"><strong>Note:</strong> When developing on a device, keep in mind that you should still use the <a @@ -44,6 +44,29 @@ allow you to verify that your application functions properly on different versio platform, in different screen sizes and orientations, and more.</p> +<h2 id="developer-device-options" style="margin-bottom: 0px;">Enabling On-device Developer Options</h2> + +<img src="/images/tools/dev-options-inmilk.png" alt="" style="float:right;margin-left:30px"> + +<p>Android-powered devices have a host of developer options that you can +access on the phone, which let you:</p> +<ul> + <li>Enable debugging over USB.</li> + <li>Quickly capture bug reports onto the device.</li> + <li>Show CPU usage on screen.</li> + <li>Draw debugging information on screen such as layout bounds, + updates on GPU views and hardware layers, and other information.</li> + <li>Plus many more options to simulate app stresses or enable debugging options.</li> +</ul> +<p>To access these settings, open the <em>Developer options</em> in the +system Settings. On Android 4.2 and higher, the Developer options screen is +hidden by default. To make it visible, go to +<b>Settings > About phone</b> and tap <b>Build number</b> seven times. Return to the previous +screen to find Developer options at the bottom.</p> + + + + <h2 id="setting-up">Setting up a Device for Development</h2> <p>With an Android-powered device, you can develop and debug your Android applications just as you @@ -90,11 +113,11 @@ Ubuntu Linux: <p>Use this format to add each vendor to the file:<br/> <code>SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"</code> <br /><br /> - + In this example, the vendor ID is for HTC. The <code>MODE</code> assignment specifies read/write permissions, and <code>GROUP</code> defines which Unix group owns the device node. </p> - + <p class="note"><strong>Note:</strong> The rule syntax may vary slightly depending on your environment. Consult the <code>udev</code> documentation for your system as needed. For an overview of rule syntax, see @@ -138,7 +161,7 @@ target your connected device.</p> <p>This table provides a reference to the vendor IDs needed in order to add USB device support on Linux. The USB Vendor ID is the value given to the -<code>ATTR{idVendor}</code> property in the rules file, as described +<code>ATTR{idVendor}</code> property in the rules file, as described above.</p> <table> @@ -193,6 +216,10 @@ above.</p> <td><code>12d1</code></td> </tr> <tr> + <td>Intel</td> + <td><code>8087</code></td> + </tr> + <tr> <td>K-Touch</td> <td><code>24e3</code></td> </tr> @@ -277,6 +304,10 @@ above.</p> <td><code>0fce</code></td> </tr> <tr> + <td>Sony Mobile Communications</td> + <td><code>0fce</code></td> + </tr> + <tr> <td>Teleepoch</td> <td><code>2340</code></td> </tr> diff --git a/docs/html/tools/help/adb.jd b/docs/html/tools/help/adb.jd index c339943..e2dd196 100644 --- a/docs/html/tools/help/adb.jd +++ b/docs/html/tools/help/adb.jd @@ -1,13 +1,14 @@ page.title=Android Debug Bridge parent.title=Tools parent.link=index.html -page.tags="adb" +page.tags=adb @jd:body <div id="qv-wrapper"> <div id="qv"> <h2>In this document</h2> <ol> + <li><a href="#Enabling">Enabling adb Debugging</a></li> <li><a href="#issuingcommands">Syntax</a></li> <li><a href="#commandsummary">Commands</a></li> <li><a href="#devicestatus">Querying for Emulator/Device Instances</a></li> @@ -72,6 +73,19 @@ instances and handles commands from multiple adb clients, you can control any em instance from any client (or from a script).</p> +<h2 id="Enabling">Enabling adb Debugging</h2> + +<p>In order to use adb with a device connected over USB, you must enable +<strong>USB debugging</strong> in the device system settings, under <strong> +Developer options</strong>.</p> + +<p>On Android 4.2 and higher, the Developer options screen is +hidden by default. To make it visible, go to +<b>Settings > About phone</b> and tap <b>Build number</b> seven times. Return to the previous +screen to find <strong>Developer options</strong> at the bottom.</p> + +<p>On some devices, the Developer options screen may be located or named differently.</p> + <p class="note"><strong>Note:</strong> When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures @@ -80,6 +94,11 @@ device and acknowledge the dialog. This requires that you have adb version 1.0.3 SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.</p> +<p>For more information about connecting to a device over USB, read +<a href="{@docRoot}tools/device.html">Using Hardware Devices</a>.</p> + + + <h2 id="issuingcommands">Syntax</h2> diff --git a/docs/html/tools/help/adt.jd b/docs/html/tools/help/adt.jd index 4dac574..1bb3015 100644 --- a/docs/html/tools/help/adt.jd +++ b/docs/html/tools/help/adt.jd @@ -1,5 +1,5 @@ page.title=Android Developer Tools -page.tags="adt" +page.tags=adt @jd:body <div id="qv-wrapper"> diff --git a/docs/html/tools/help/draw9patch.jd b/docs/html/tools/help/draw9patch.jd index ebf2c6c..859b1cf 100644 --- a/docs/html/tools/help/draw9patch.jd +++ b/docs/html/tools/help/draw9patch.jd @@ -1,5 +1,5 @@ page.title=Draw 9-patch -page.tags="NinePatch" +page.tags=NinePatch @jd:body <p>The Draw 9-patch tool allows you to easily create a diff --git a/docs/html/tools/help/sdk-manager.jd b/docs/html/tools/help/sdk-manager.jd index 57271bb..b084237 100644 --- a/docs/html/tools/help/sdk-manager.jd +++ b/docs/html/tools/help/sdk-manager.jd @@ -3,7 +3,9 @@ page.title=SDK Manager <p>The Android SDK separates tools, platforms, and other components into packages you can - download using the SDK Manager.</p> + download using the 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.</p> <p>You can launch the SDK Manager in one of the following ways:</p> <ul> @@ -25,6 +27,14 @@ click <strong>Install</strong> to install the selected packages.</p> SDK packages that are available, already installed, or for which an update is available.</p> +<p>There are several different packages available for the Android SDK. The table below describes +most of the available packages and where they're located in your SDK directory +once you download them.</p> + + + + + <h2 id="Recommended">Recommended Packages</h2> <p>Here's an outline of the packages required and those we recommend you use: @@ -69,3 +79,77 @@ matches the API Level of the Android platform that you plan to use.</dd> <p class="note"><strong>Tip:</strong> For easy access to the SDK tools from a command line, add the location of the SDK's <code>tools/</code> and <code>platform-tools</code> to your <code>PATH</code> environment variable.</p> + + +<p>The above list is not comprehensive and you can <a +href="#AddingSites">add new sites</a> to download additional packages from third-parties.</p> + +<p>In some cases, an SDK package may require a specific minimum revision of +another package or SDK tool. +The development tools will notify you with warnings if there is dependency that you need to +address. The Android SDK Manager also enforces dependencies by requiring that you download any +packages that are needed by those you have selected.</p> + + + + + +<h2 id="AddingSites">Adding New Sites</h2> + +<p>By default, <strong>Available Packages</strong> displays packages available from the +<em>Android Repository</em> and <em>Third party Add-ons</em>. You can add other sites that host +their own Android SDK add-ons, then download the SDK add-ons +from those sites.</p> + +<p>For example, a mobile carrier or device manufacturer might offer additional +API libraries that are supported by their own Android-powered devices. In order +to develop using their libraries, you must install their Android SDK add-on, if it's not already +available under <em>Third party Add-ons</em>. </p> + +<p>If a carrier or device manufacturer has hosted an SDK add-on repository file +on their web site, follow these steps to add their site to the Android SDK +Manager:</p> + +<ol> + <li>Select <strong>Available Packages</strong> in the left panel.</li> + <li>Click <strong>Add Add-on Site</strong> and enter the URL of the +<code>repository.xml</code> file. Click <strong>OK</strong>.</li> +</ol> +<p>Any SDK packages available from the site will now be listed under a new item named +<strong>User Add-ons</strong>.</p> + + + + +<h2 id="troubleshooting">Troubleshooting</h2> + +<p><strong>Problems connecting to the SDK repository</strong></p> + +<p>If you are using the Android SDK Manager to download packages and are encountering +connection problems, try connecting over http, rather than https. To switch the +protocol used by the Android SDK Manager, follow these steps: </p> + +<ol> + <li>With the Android SDK Manager window open, select "Settings" in the + left pane. </li> + <li>On the right, in the "Misc" section, check the checkbox labeled "Force + https://... sources to be fetched using http://..." </li> + <li>Click <strong>Save & Apply</strong>.</li> +</ol> + + + + + + + + + + + + + + + + + diff --git a/docs/html/tools/publishing/app-signing.jd b/docs/html/tools/publishing/app-signing.jd index 1de1fd7..53e6e65 100644 --- a/docs/html/tools/publishing/app-signing.jd +++ b/docs/html/tools/publishing/app-signing.jd @@ -4,33 +4,26 @@ page.title=Signing Your Applications <div id="qv-wrapper"> <div id="qv"> -<h2>Quickview</h2> - -<ul> -<li>All Android apps <em>must</em> be signed</li> -<li>You can sign with a self-signed key</li> -<li>How you sign your apps is critical — read this document carefully</li> -<li>Determine your signing strategy early in the development process</li> -</ul> - <h2>In this document</h2> <ol> -<li><a href="#signing">Signing Process</a></li> -<li><a href="#strategies">Signing Strategies</a></li> -<li><a href="#setup">Basic Setup for Signing</a></li> -<li><a href="#debugmode">Signing in Debug Mode</a></li> -<li><a href="#releasemode">Signing Release Mode</a> - <ol> - <li><a href="#cert">Obtain a suitable private key</a></li> - <li><a href="#releasecompile">Compile the application in release mode</a></li> - <li><a href="#signapp">Sign your application with your private key</a></li> - <li><a href="#align">Align the final APK package</a></li> - <li><a href="#ExportWizard">Compile and sign with Eclipse ADT</a></li> - </ol> +<li><a href="#overview">Signing Overview</a> + <ol> + <li><a href="#debug-mode">Signing in Debug Mode</a></li> + <li><a href="#release-mode">Signing in Release Mode</a></li> + <li><a href="#wear-apps">Signing Android Wear Apps</a></li> + </ol> </li> +<li><a href="#studio">Signing Your App in Android Studio</a> + <ol> + <li><a href="sign-auto">Automatically Signing Your App</a></li> + </ol> +</li> +<li><a href="#adt">Signing Your App with the ADT plugin for Eclipse</a></li> +<li><a href="#considerations">Signing Considerations</a></li> <li><a href="#secure-key">Securing Your Private Key</a></li> - +<li><a href="#expdebug">Expiry of the Debug Certificate</a></li> +<li><a href="#signing-manually">Signing Your App Manually</a></li> </ol> <h2>See also</h2> @@ -43,588 +36,288 @@ page.title=Signing Your Applications </div> </div> -<p>The Android system requires that all installed applications be digitally signed with a -certificate whose private key is held by the application's developer. The Android system uses the -certificate as a means of identifying the author of an application and establishing trust -relationships between applications. The certificate is not used to control which applications the -user can install. The certificate does not need to be signed by a certificate authority: it is -perfectly allowable, and typical, for Android applications to use self-signed certificates.</p> - -<p>The important points to understand about signing Android applications are:</p> - -<ul> - <li>All applications <em>must</em> be signed. The system will not install an application -on an emulator or a device if it is not signed.</li> - <li>To test and debug your application, the build tools sign your application with a special debug - key that is created by the Android SDK build tools.</li> - <li>When you are ready to release your application for end-users, you must sign it with a suitable - private key. You cannot publish an application that is signed with the debug key generated - by the SDK tools.</li> - <li>You can use self-signed certificates to sign your applications. No certificate authority is - needed.</li> - <li>The system tests a signer certificate's expiration date only at install time. If an -application's signer certificate expires after the application is installed, the application -will continue to function normally.</li> - <li>You can use standard tools — Keytool and Jarsigner — to generate keys and -sign your application {@code .apk} files.</li> - <li>After you sign your application for release, we recommend that you use the - <code>zipalign</code> tool to optimize the final APK package.</li> -</ul> -<p>The Android system will not install or run an application that is not signed appropriately. This -applies wherever the Android system is run, whether on an actual device or on the emulator. -For this reason, you must <a href="#setup">set up signing</a> for your application before you can -run it or debug it on an emulator or device.</p> - -<h2 id="signing">Signing Process</h3> - -<p>The Android build process signs your application differently depending on which build mode you -use to build your application. There are two build modes: <em>debug mode</em> and <em>release -mode</em>. You use debug mode when you are developing and testing your application. You use -release mode when you want to build a release version of your application that you can -distribute directly to users or publish on an application marketplace such as Google Play.</p> - -<p>When you build in <em>debug mode</em> the Android SDK build tools use the Keytool utility -(included in the JDK) to create a debug key. Because the SDK build tools created the debug key, -they know the debug key's alias and password. Each time you compile your application in debug mode, -the build tools use the debug key along with the Jarsigner utility (also included in the JDK) to -sign your application's <code>.apk</code> file. Because the alias and password are known to the SDK -build tools, the tools don't need to prompt you for the debug key's alias and password each time -you compile.</p> - -<p>When you build in <em>release mode</em> you use your own private key to sign your application. If -you don't have a private key, you can use the Keytool utility to create one for you. When you -compile your application in release mode, the build tools use your private key along with the -Jarsigner utility to sign your application's <code>.apk</code> file. Because the certificate and -private key you use are your own, you must provide the password for the keystore and key alias.</p> - -<p>The debug signing process happens automatically when you run or debug your application using -Eclipse with the ADT plugin. Debug signing also happens automatically when you use the Ant build -script with the <code>debug</code> option. You can automate the release signing process by using the -Eclipse Export Wizard or by modifying the Ant build script and building with the -<code>release</code> option.</p> - -<h2 id="strategies">Signing Strategies</h2> - -<p>Some aspects of application signing may affect how you approach the development -of your application, especially if you are planning to release multiple -applications. </p> - -<p>In general, the recommended strategy for all developers is to sign -all of your applications with the same certificate, throughout the expected -lifespan of your applications. There are several reasons why you should do so: </p> +<p>Android requires that all apps be digitally signed with a certificate before they can be +installed. Android uses this certificate to identify the author of an app, and the certificate +does not need to be signed by a certificate authority. Android apps often use self-signed +certificates. The app developer holds the certificate's private key.</p> -<ul> -<li>Application upgrade – As you release updates to your application, you -must continue to sign the updates with the same certificate or set of certificates, -if you want users to be able to upgrade seamlessly to the new version. When -the system is installing an update to an application, it compares the -certificate(s) in the new version with those in the existing version. If the -certificates match exactly, including both the certificate data and order, then -the system allows the update. If you sign the new version without using matching -certificates, you must also assign a different package name to the -application — in this case, the user installs the new version as a -completely new application. </li> - -<li>Application modularity – The Android system allows applications that -are signed by the same certificate to run in the same process, if the -applications so requests, so that the system treats them as a single application. -In this way you can deploy your application in modules, and users can update -each of the modules independently if needed.</li> - -<li>Code/data sharing through permissions – The Android system provides -signature-based permissions enforcement, so that an application can expose -functionality to another application that is signed with a specified -certificate. By signing multiple applications with the same certificate and -using signature-based permissions checks, your applications can share code and -data in a secure manner. </li> -</ul> +<h2 id="overview">Signing Overview</h2> -<p>Another important consideration in determining your signing strategy is -how to set the validity period of the key that you will use to sign your -applications.</p> +<p>You can sign an app in debug or release mode. You sign your app in debug mode during development +and in release mode when you are ready to distribute your app. The Android SDK generates a +certificate to sign apps in debug mode. To sign apps in release mode, you need to generate +your own certificate.</p> -<ul> -<li>If you plan to support upgrades for a single application, you should ensure -that your key has a validity period that exceeds the expected lifespan of -that application. A validity period of 25 years or more is recommended. -When your key's validity period expires, users will no longer be -able to seamlessly upgrade to new versions of your application.</li> - -<li>If you will sign multiple distinct applications with the same key, -you should ensure that your key's validity period exceeds the expected -lifespan of <em>all versions of all of the applications</em>, including -dependent applications that may be added to the suite in the future. </li> - -<li>If you plan to publish your application(s) on Google Play, the -key you use to sign the application(s) must have a validity period -ending after 22 October 2033. Google Play enforces this requirement -to ensure that users can seamlessly upgrade applications when -new versions are available. </li> -</ul> +<h3 id="debug-mode">Signing in Debug Mode</h3> -<p>As you design your application, keep these points in mind and make sure to -use a <a href="#cert">suitable certificate</a> to sign your applications. </p> +<p>In debug mode, you sign your app with a debug certificate generated by the Android SDK tools. +This certificate has a private key with a known password, so you can run and debug your app +without typing the password every time you make a change to your project.</p> -<h2 id="setup">Basic Setup for Signing</h2> +<p>Android Studio and the ADT plugin for Eclipse sign your app in debug mode automatically when +you run or debug your project from the IDE.</p> -<p>Before you begin, make sure that the Keytool utility and Jarsigner utility are available to -the SDK build tools. Both of these tools are available in the JDK. In most cases, you can tell -the SDK build tools how to find these utilities by setting your <code>JAVA_HOME</code> environment -variable so it references a suitable JDK. Alternatively, you can add the JDK version of Keytool and -Jarsigner to your <code>PATH</code> variable.</p> +<p>You can run and debug an app signed in debug mode on the emulator and on devices connected +to your development manchine through USB, but you cannot distribute an app signed in debug +mode.</p> -<p>If you are developing on a version of Linux that originally came with GNU Compiler for -Java, make sure that the system is using the JDK version of Keytool, rather than the gcj -version. If Keytool is already in your <code>PATH</code>, it might be pointing to a symlink at -<code>/usr/bin/keytool</code>. In this case, check the symlink target to be sure it points -to the Keytool in the JDK.</p> +<p>For more information about how to build and run apps in debug mode, see +<a href="{@docRoot}tools/building/index.html">Building and Running</a>.</p> -<h2 id="debugmode">Signing in Debug Mode</h2> +<h3 id="release-mode">Signing in Release Mode</h3> -<p>The Android build tools provide a debug signing mode that makes it easier for you -to develop and debug your application, while still meeting the Android system -requirement for signing your APK. -When using debug mode to build your app, the SDK tools invoke Keytool to automatically create -a debug keystore and key. This debug key is then used to automatically sign the APK, so -you do not need to sign the package with your own key.</p> +<p>In release mode, you sign your app with your own certificate:</p> -<p>The SDK tools create the debug keystore/key with predetermined names/passwords:</p> -<ul> -<li>Keystore name: "debug.keystore"</li> -<li>Keystore password: "android"</li> -<li>Key alias: "androiddebugkey"</li> -<li>Key password: "android"</li> -<li>CN: "CN=Android Debug,O=Android,C=US"</li> -</ul> - -<p>If necessary, you can change the location/name of the debug keystore/key or -supply a custom debug keystore/key to use. However, any custom debug -keystore/key must use the same keystore/key names and passwords as the default -debug key (as described above). (To do so in Eclipse/ADT, go to -<strong>Windows</strong> > <strong>Preferences</strong> > -<strong>Android</strong> > <strong>Build</strong>.) </p> - -<p class="caution"><strong>Caution:</strong> You <em>cannot</em> release your application -to the public when signed with the debug certificate.</p> +<ol> +<li><em>Create a keystore.</em> A <strong>keystore</strong> is a binary file that contains a +set of private keys. You must keep your keystore in a safe and secure place.</li> +<li><em>Create a private key.</em> A <strong>private key</strong> represents the entity to +be identified with the app, such as a person or a company.</li> +<li><em>Build your project</em>. Generate an unsigned APK for your app.</li> +<li><em>Sign your app.</em> Use your private key to generate a signed version of your APK.</li> +</ol> -<h3>Eclipse Users</h3> +<p>After you complete this process, you can distribute your app and publish it on Google Play.</p> -<p>If you are developing in Eclipse/ADT (and have set up Keytool and Jarsigner as described above in -<a href="#setup">Basic Setup for Signing</a>), -signing in debug mode is enabled by default. When you run or debug your -application, ADT signs the {@code .apk} file with the debug certificate, runs {@code zipalign} on -the package, then installs it on -the selected emulator or connected device. No specific action on your part is needed, -provided ADT has access to Keytool.</p> +<p class="warning"><strong>Warning:</strong> Keep your keystore and private key in a safe and +secure place, and ensure that you have secure backups of them. If you publish an app to Google +Play and then lose the key with which you signed your app, you will not be able to publish +any updates to your app, since you must always sign all versions of your app with the same +key.</p> -<h3>Ant Users</h3> +<p>The rest of this document provides detailed instructions about how to generate a private +key and sign your apps in release mode with Android Studio and with the ADT plugin for Eclipse.</p> -<p>If you are using Ant to build your {@code .apk} file, debug signing mode -is enabled by using the <code>debug</code> option with the <code>ant</code> command -(assuming that you are using a <code>build.xml</code> file generated by the -<code>android</code> tool). When you run <code>ant debug</code> to -compile your app, the build script generates a keystore/key and signs the APK for you. -The script then also aligns the APK with the <code>zipalign</code> tool. -No other action on your part is needed. Read -<a href="{@docRoot}tools/building/building-cmdline.html#DebugMode">Building and Running Apps -on the Command Line</a> for more information.</p> +<h3 id="wear-apps">Signing Android Wear Apps</h3> +<p>When publishing Android Wear apps, you package the wearable app inside of a handheld app, +because users cannot browse and install apps directly on the wearable. Both apps must be signed. +For more information on packaging and signing Android Wear apps, see +<a href="{@docRoot}training/wearables/apps/packaging.html">Packaging Wearable Apps</a>.</p> -<h3 id="debugexpiry">Expiry of the Debug Certificate</h3> -<p>The self-signed certificate used to sign your application in debug mode (the default on -Eclipse/ADT and Ant builds) will have an expiration date of 365 days from its creation date.</p> +<h2 id="studio">Signing Your App in Android Studio</h2> -<p>When the certificate expires, you will get a build error. On Ant builds, the error -looks like this:</p> +<p>To sign your app in release mode in Android Studio, follow these steps:</p> -<pre>debug: -[echo] Packaging bin/samples-debug.apk, and signing it with a debug key... -[exec] Debug Certificate expired on 8/4/08 3:43 PM</pre> +<ol> +<li>On the menu bar, click <strong>Build</strong> > <strong>Generate Signed APK</strong>.</li> +<li><p>On the <em>Generate Signed APK Wizard</em> window, click <strong>Create new</strong> to create +a new keystore.</p><p>If you already have a keystore, go to step 4.</p></li> +<li><p>On the <em>New Key Store</em> window, provide the required information as shown +in figure 1.</p><p>Your key should be valid for at least 25 years, so you can sign app updates +with the same key through the lifespan of your app.</p> +<img src="{@docRoot}images/tools/signstudio2.png" alt="" + width="416" height="364" style="margin-top:15px"/> +<p class="img-caption"><strong>Figure 1</strong>. Create a new keystore in Android Studio.</p> +</li> +<li><p>On the <em>Generate Signed APK Wizard</em> window, select a keystore, a private key, and enter +the passwords for both. Then click <strong>Next</strong>.</p> +<img src="{@docRoot}images/tools/signstudio1.png" alt="" + width="349" height="232" style="margin-top:15px"/> +<p class="img-caption"><strong>Figure 2</strong>. Select a private key in Android Studio.</p> +</li> +<li><p>On the next window, select a destination for the signed APK and click +<strong>Finish</strong>.</p> +<img src="{@docRoot}images/tools/signstudio3.png" alt="" + width="350" height="175" style="margin-top:15px"/> +<p class="img-caption"><strong>Figure 3</strong>. Generate a signed APK in Android Studio.</p> +</li> +</ol> -<p>In Eclipse/ADT, you will see a similar error in the Android console.</p> +<h3 id="sign-auto">Automatically Signing Your App</h3> -<p>To fix this problem, simply delete the <code>debug.keystore</code> file. -The default storage location for AVDs is in <code>~/.android/</code> on OS X and Linux, -in <code>C:\Documents and Settings\<user>\.android\</code> on Windows XP, and in -<code>C:\Users\<user>\.android\</code> on Windows Vista and Windows 7.</p> +<p>In Android Studio, you can configure your project to sign your release APK automatically +during the build process:</p> +<ol> +<li>On the project browser, right click on your app and select <strong>Open Module +Settings</strong>.</li> +<li>On the <em>Project Structure</em> window, select your app's module under <em>Modules</em>.</li> +<li>Click on the <strong>Signing</strong> tab.</li> +<li><p>Select your keystore file, enter a name for this signing configuration (as you may create +more than one), and enter the required information.</p> +<img src="{@docRoot}images/tools/signstudio10.png" alt="" + width="623" height="372" style="margin-top:15px"/> +<p class="img-caption"><strong>Figure 4</strong>. Create a signing configuration in Android Studio.</p> +</li> +<li>Click on the <strong>Build Types</strong> tab.</li> +<li>Select the <strong>release</strong> build.</li> +<li><p>Under <em>Signing Config</em>, select the signing configuration you just created.</p> +<img src="{@docRoot}images/tools/signstudio11.png" alt="" + width="623" height="372" style="margin-top:15px"/> +<p class="img-caption"><strong>Figure 5</strong>. Select a signing configuration in Android Studio.</p> +</li> +<li>Click <strong>OK</strong>.</li> +</ol> -<p>The next time you build, the build tools will regenerate a new keystore and debug key.</p> +<p>You can also specify your signing settings in Gradle configuration files. For more information, +see <a href="{@docRoot}sdk/installing/studio-build.html#configureSigning">Signing settings</a>.</p> -<p>Note that, if your development machine is using a non-Gregorian locale, the build -tools may erroneously generate an already-expired debug certificate, so that you get an -error when trying to compile your application. For workaround information, see the -troubleshooting topic <a href="{@docRoot}resources/faq/troubleshooting.html#signingcalendar"> -I can't compile my app because the build tools generated an expired debug -certificate</a>. </p> +<h2 id="adt">Signing Your App with the ADT Plugin for Eclipse</h2> -<h2 id="releasemode">Signing in Release Mode</h2> +<p>To sign your app in release mode in ADT, follow these steps:</p> -<p>When your application is ready for release to other users, you must:</p> <ol> - <li><a href="#cert">Obtain a suitable private key</a></li> - <li><a href="#releasecompile">Compile the application in release mode</a></li> - <li><a href="#signapp">Sign your application with your private key</a></li> - <li><a href="#align">Align the final APK package</a></li> +<li>Select the project in the Package Explorer and select <strong>File</strong> > +<strong>Export</strong>.</li> +<li>On the <em>Export</em> window, select <strong>Export Android Application</strong> and click +<strong>Next</strong>.</li> +<li>On the <em>Export Android Application</em> window, select the project you want to sign and +click <strong>Next</strong>.</li> +<li> +<p>On the next window, enter the location to create a keystore and a keystore password. If you +already have a keystore, select <strong>Use existing keystore</strong>, enter your keystore's +location and password, and go to step 6.</p> +<img src="{@docRoot}images/tools/signadt3.png" alt="" + width="488" height="270" style="margin-top:15px"/> +<p class="img-caption"><strong>Figure 6</strong>. Select a keystore in ADT.</p> +</li> +<li><p>On the next window, provide the required information as shown in figure 5.<p> +<p>Your key should be valid for at least 25 years, so you can sign app updates with the same key +through the lifespan of your app.</p> +<img src="{@docRoot}images/tools/signadt4.png" alt="" + width="488" height="448" style="margin-top:15px"/> +<p class="img-caption"><strong>Figure 7</strong>. Create a private key in ADT.</p> +</li> +<li><p>On the next window, select the location to export the signed APK.</p> +<img src="{@docRoot}images/tools/signadt5.png" alt="" + width="488" height="217" style="margin-top:15px"/> +<p class="img-caption"><strong>Figure 8</strong>. Export the signed APK in ADT.</p> +</li> </ol> -<p>If you are developing in Eclipse with the ADT plugin, you can use the Export Wizard -to perform the compile, sign, and align procedures. The Export Wizard even allows you to -generate a new keystore and private key in the process. So if you use Eclipse, you can -skip to <a href="#ExportWizard">Compile and sign with Eclipse ADT</a>.</p> - +<h2 id="considerations">Signing Considerations</h2> -<h3 id="cert">1. Obtain a suitable private key</h3> - -<p>In preparation for signing your application, you must first ensure that -you have a suitable private key with which to sign. A suitable private -key is one that:</p> +<p>You should sign all of your apps with the same certificate throughout the expected lifespan +of your applications. There are several reasons why you should do so:</p> <ul> -<li>Is in your possession</li> -<li>Represents the personal, corporate, or organizational entity to be identified -with the application</li> -<li>Has a validity period that exceeds the expected lifespan of the application -or application suite. A validity period of more than 25 years is recommended. -<p>If you plan to publish your application(s) on Google Play, note that a -validity period ending after 22 October 2033 is a requirement. You can not upload an -application if it is signed with a key whose validity expires before that date. -</p></li> -<li>Is not the debug key generated by the Android SDK tools. </li> +<li>App upgrade: When the system is installing an update to an app, it compares the certificate(s) +in the new version with those in the existing version. The system allows the update if the +certificates match. If you sign the new version with a different certificate, you must assign a +different package name to the application—in this case, the user installs the new version as +a completely new application.</li> +<li>App modularity: Android allows apps signed by the same certificate to run in the same process, +if the applications so requests, so that the system treats them as a single application. In this +way you can deploy your app in modules, and users can update each of the modules independently.</li> +<li>Code/data sharing through permissions: Android provides signature-based permissions +enforcement, so that an app can expose functionality to another app that is signed with a +specified certificate. By signing multiple apps with the same certificate and using +signature-based permissions checks, your apps can share code and data in a secure manner.</li> </ul> -<p>The key may be self-signed. If you do not have a suitable key, you must -generate one using Keytool. Make sure that you have Keytool available, as described -in <a href="#setup">Basic Setup</a>.</p> - -<p>To generate a self-signed key with Keytool, use the <code>keytool</code> -command and pass any of the options listed below (and any others, as -needed). </p> - -<p class="warning"><strong>Warning:</strong> Keep your private key secure. -Before you run Keytool, make sure to read -<a href="#secure-key">Securing Your Private Key</a> for a discussion of how to keep -your key secure and why doing so is critically important to you and to users. In -particular, when you are generating your key, you should select strong passwords -for both the keystore and key.</p> - -<p class="warning"><strong>Warning:</strong> Keep the keystore file you generate with Keytool -in a safe, secure place. You must use the same key to sign future versions of your application. If -you republish your app with a new key, Google Play will consider it a new app. For more information -on settings that must remain constant over the life of your app, see the Android Developer Blog post -<a href="http://android-developers.blogspot.com/2011/06/things-that-cannot-change.html">Things -That Cannot Change</a>.</p> - -<table> -<tr> -<th>Keytool Option</th> -<th>Description</th> -</tr> -<tr> -<td><code>-genkey</code></td><td>Generate a key pair (public and private -keys)</td> -</tr> -<tr> -<td><code>-v</code></td><td>Enable verbose output.</td> -</tr> -<tr> -<td><code>-alias <alias_name></code></td><td>An alias for the key. Only -the first 8 characters of the alias are used.</td> -</tr> -<tr> -<td><code>-keyalg <alg></code></td><td>The encryption algorithm to use -when generating the key. Both DSA and RSA are supported.</td> -</tr> -<tr> -<td><code>-keysize <size></code></td><td>The size of each generated key -(bits). If not supplied, Keytool uses a default key size of 1024 bits. In -general, we recommend using a key size of 2048 bits or higher. </td> -</tr> -<tr> -<td><code>-dname <name></code></td><td><p>A Distinguished Name that describes -who created the key. The value is used as the issuer and subject fields in the -self-signed certificate. </p><p>Note that you do not need to specify this option -in the command line. If not supplied, Jarsigner prompts you to enter each -of the Distinguished Name fields (CN, OU, and so on).</p></td> -</tr> -<tr> -<td><code>-keypass <password></code></td><td><p>The password for the -key.</p> <p>As a security precaution, do not include this option in your command -line. If not supplied, Keytool prompts you to enter the password. In this way, -your password is not stored in your shell history.</p></td> -</tr> -<tr> -<td><code>-validity <valdays></code></td><td><p>The validity period for the -key, in days. </p><p><strong>Note:</strong> A value of 10000 or greater is recommended.</p></td> -</tr> -<tr> -<td><code>-keystore <keystore-name>.keystore</code></td><td>A name -for the keystore containing the private key.</td> -</tr> -<tr> -<td><code>-storepass <password></code></td><td><p>A password for the -keystore.</p><p>As a security precaution, do not include this option in your -command line. If not supplied, Keytool prompts you to enter the password. In -this way, your password is not stored in your shell history.</p></td> -</tr> -</table> - -<p>Here's an example of a Keytool command that generates a private key:</p> - -<pre>$ keytool -genkey -v -keystore my-release-key.keystore --alias alias_name -keyalg RSA -keysize 2048 -validity 10000</pre> - -<p>Running the example command above, Keytool prompts you to provide -passwords for the keystore and key, and to provide the Distinguished -Name fields for your key. It then generates the keystore as a file called -<code>my-release-key.keystore</code>. The keystore and key are -protected by the passwords you entered. The keystore contains -a single key, valid for 10000 days. The alias is a name that you — -will use later, to refer to this keystore when signing your application. </p> - -<p>For more information about Keytool, see the documentation at -<a -href="http://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html"> -http://docs.oracle.com/javase/6/docs/technotes/tools/windows/keytool.html</a></p> - - - -<h3 id="releasecompile">2. Compile the application in release mode</h3> - -<p>In order to release your application to users, you must compile it in release mode. -In release mode, the compiled application is not signed by default and you will need -to sign it with your private key.</p> - -<p class="caution"><strong>Caution:</strong> -You can not release your application unsigned, or signed with the debug key.</p> - -<h4>With Eclipse</h4> - -<p>To export an <em>unsigned</em> APK from Eclipse, right-click the project in the Package -Explorer and select <strong>Android Tools</strong> > <strong>Export Unsigned Application -Package</strong>. Then specify the file location for the unsigned APK. -(Alternatively, open your <code>AndroidManifest.xml</code> file in Eclipse, select -the <strong>Manifest</strong> tab, and click <strong>Export an unsigned APK</strong>.)</p> - -<p>Note that you can combine the compiling and signing steps with the Export Wizard. See -<a href="#ExportWizard">Compiling and signing with Eclipse ADT</a>.</p> - -<h4>With Ant</h4> - -<p>If you are using Ant, you can enable release mode by using the <code>release</code> option -with the <code>ant</code> command. For example, if you are running Ant from the -directory containing your {@code build.xml} file, the command would look like this:</p> - -<pre>$ ant release</pre> - -<p>By default, the build script compiles the application APK without signing it. The output file -in your project {@code bin/} will be <code><em><your_project_name></em>-unsigned.apk</code>. -Because the application APK is still unsigned, you must manually sign it with your private -key and then align it using {@code zipalign}.</p> - -<p>However, the Ant build script can also perform the signing -and aligning for you, if you have provided the path to your keystore and the name of -your key alias in the project's {@code ant.properties} file. With this information provided, -the build script will prompt you for your keystore and alias password when you perform -<code>ant release</code>, it will sign the package and then align it. The final output -file in {@code bin/} will instead be -<code><em><your_project_name></em>-release.apk</code>. With these steps -automated for you, you're able to skip the manual procedures below (steps 3 and 4). -To learn how to specify your keystore and alias in the {@code ant.properties} file, -see <a href="{@docRoot}tools/building/building-cmdline.html#ReleaseMode"> -Building and Running Apps on the Command Line</a>.</p> - - - -<h3 id="signapp">3. Sign your application with your private key</h3> - -<p>When you have an application package that is ready to be signed, you can do sign it -using the Jarsigner tool. Make sure that you have Jarsigner available on your -machine, as described in <a href="#setup">Basic Setup</a>. Also, make sure that -the keystore containing your private key is available.</p> - -<p>To sign your application, you run Jarsigner, referencing both the -application's APK and the keystore containing the private key with which to -sign the APK. The table below shows the options you could use. </p> - -<table> -<tr> -<th>Jarsigner Option</th> -<th>Description</th> -</tr> -<tr> -<td><code>-keystore <keystore-name>.keystore</code></td><td>The name of -the keystore containing your private key.</td> -</tr> -<tr> -<td><code>-verbose</code></td><td>Enable verbose output.</td> -</tr> -<tr> -<td><code>-sigalg</code></td><td>The name of the signature algorithim to use in signing the APK. -Use the value {@code SHA1withRSA}.</td> -</tr> -<tr> -<td><code>-digestalg</code></td><td>The message digest algorithim to use in processing the entries -of an APK. Use the value {@code SHA1}.</td> -</tr> -<tr> -<td><code>-storepass <password></code></td><td><p>The password for the -keystore. </p><p>As a security precaution, do not include this option -in your command line unless you are working at a secure computer. -If not supplied, Jarsigner prompts you to enter the password. In this -way, your password is not stored in your shell history.</p></td> -</tr> -<tr> -<td><code>-keypass <password></code></td><td><p>The password for the private -key. </p><p>As a security precaution, do not include this option -in your command line unless you are working at a secure computer. -If not supplied, Jarsigner prompts you to enter the password. In this -way, your password is not stored in your shell history.</p></td> -</tr> -</table> - -<p>Here's how you would use Jarsigner to sign an application package called -<code>my_application.apk</code>, using the example keystore created above. -</p> - -<pre>$ jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore -my_application.apk alias_name</pre> - -<p>Running the example command above, Jarsigner prompts you to provide -passwords for the keystore and key. It then modifies the APK -in-place, meaning the APK is now signed. Note that you can sign an -APK multiple times with different keys.</p> - -<p class="caution"><strong>Caution:</strong> As of JDK 7, the default signing algorithim has -changed, requiring you to specify the signature and digest algorithims ({@code -sigalg} and {@code --digestalg}) when you sign an APK.</p> - -<p>To verify that your APK is signed, you can use a command like this:</p> - -<pre>$ jarsigner -verify my_signed.apk</pre> - -<p>If the APK is signed properly, Jarsigner prints "jar verified". -If you want more details, you can try one of these commands:</p> - -<pre>$ jarsigner -verify -verbose my_application.apk</pre> - -<p>or</p> - -<pre>$ jarsigner -verify -verbose -certs my_application.apk</pre> - -<p>The command above, with the <code>-certs</code> option added, will show you the -"CN=" line that describes who created the key.</p> - -<p class="note"><strong>Note:</strong> If you see "CN=Android Debug", this means the APK was -signed with the debug key generated by the Android SDK. If you intend to release -your application, you must sign it with your private key instead of the debug -key.</p> - -<p>For more information about Jarsigner, see the documentation at -<a href="http://docs.oracle.com/javase/6/docs/technotes/tools/windows/jarsigner.html"> -http://docs.oracle.com/javase/6/docs/technotes/tools/windows/jarsigner.html</a></p> - +<p>If you plan to support upgrades for an app, ensure that your key has a validity +period that exceeds the expected lifespan of that app. A validity period of 25 years or more is +recommended. When your key's validity period expires, users will no longer be able to seamlessly +upgrade to new versions of your application.</p> -<h3 id="align">4. Align the final APK package</h3> +<p>If you plan to publish your apps on Google Play, the key you use to sign these apps must have +a validity period ending after 22 October 2033. Google Play enforces this requirement to ensure +that users can seamlessly upgrade apps when new versions are available.</p> -<p>Once you have signed the APK with your private key, run <code>zipalign</code> on the file. -This tool ensures that all uncompressed data starts with a particular byte alignment, -relative to the start of the file. Ensuring alignment at 4-byte boundaries provides -a performance optimization when installed on a device. When aligned, the Android -system is able to read files with {@code mmap()}, even if -they contain binary data with alignment restrictions, rather than copying all -of the data from the package. The benefit is a reduction in the amount of -RAM consumed by the running application.</p> -<p>The <code>zipalign</code> tool is provided with the Android SDK, inside the -<code>tools/</code> directory. To align your signed APK, execute:</p> - -<pre>$ zipalign -v 4 <em>your_project_name</em>-unaligned.apk <em>your_project_name</em>.apk</pre> - -<p>The {@code -v} flag turns on verbose output (optional). {@code 4} is the -byte-alignment (don't use anything other than 4). The first file argument is -your signed {@code .apk} file (the input) and the second file is the destination {@code .apk} file -(the output). If you're overriding an existing APK, add the {@code -f} flag.</p> +<h2 id="secure-key">Securing Your Private Key</h2> -<p class="caution"><strong>Caution:</strong> Your input APK must be signed with your -private key <strong>before</strong> you optimize the package with {@code zipalign}. -If you sign it after using {@code zipalign}, it will undo the alignment.</p> +<p>Maintaining the security of your private key is of critical importance, both to you and to +the user. If you allow someone to use your key, or if you leave your keystore and passwords in +an unsecured location such that a third-party could find and use them, your authoring identity +and the trust of the user are compromised.</p> -<p>For more information, read about the -<a href="{@docRoot}tools/help/zipalign.html">zipalign</a> tool. +<p>If a third party should manage to take your key without your knowledge or permission, that +person could sign and distribute apps that maliciously replace your authentic apps or corrupt +them. Such a person could also sign and distribute apps under your identity that attack +other apps or the system itself, or corrupt or steal user data.</p> +<p>Your private key is required for signing all future versions of your app. If you lose or +misplace your key, you will not be able to publish updates to your existing appn. You cannot +regenerate a previously generated key.</p> -<h3 id="ExportWizard">Compile and sign with Eclipse ADT</h3> +<p>Your reputation as a developer entity depends on your securing your private key properly, at +all times, until the key is expired. Here are some tips for keeping your key secure:</p> -<p>If you are using Eclipse with the ADT plugin, you can use the Export Wizard to -export a <em>signed</em> APK (and even create a new keystore, -if necessary). The Export Wizard performs all the interaction with -the Keytool and Jarsigner for you, which allows you to sign the package using a GUI -instead of performing the manual procedures to compile, sign, -and align, as discussed above. Once the wizard has compiled and signed your package, -it will also perfom package alignment with {@code zipalign}. -Because the Export Wizard uses both Keytool and Jarsigner, you should -ensure that they are accessible on your computer, as described above -in the <a href="#setup">Basic Setup for Signing</a>.</p> +<ul> +<li>Select strong passwords for the keystore and key.</li> +<li>Do not give or lend anyone your private key, and do not let unauthorized persons know your +keystore and key passwords.</li> +<li>Keep the keystore file containing your private key in a safe, secure place.</li> +</ul> -<p>To create a signed and aligned APK in Eclipse:</p> +<p>In general, if you follow common-sense precautions when generating, using, and storing +your key, it will remain secure.</p> -<ol> - <li>Select the project in the Package -Explorer and select <strong>File > Export</strong>.</li> - <li>Open the Android folder, select Export Android Application, - and click <strong>Next</strong>. - <p>The Export Android Application wizard now starts, which will - guide you through the process of signing your application, - including steps for selecting the private key with which to sign the APK - (or creating a new keystore and private key).</p> - <li>Complete the Export Wizard and your application will be compiled, - signed, aligned, and ready for distribution.</li> -</ol> +<h2 id="expdebug">Expiry of the Debug Certificate</h2> +<p>The self-signed certificate used to sign your application in debug mode has an expiration date +of 365 days from its creation date. When the certificate expires, you will get a build error.</p> -<h2 id="secure-key">Securing Your Private Key</h2> +<p>To fix this problem, simply delete the <code>debug.keystore</code> file. The default storage +location is in <code>~/.android/</code> on OS X and Linux, in <code>C:\Documents and +Settings\<user>\.android\</code> on Windows XP, and in +<code>C:\Users\<user>\.android\</code> on Windows Vista and Windows 7.</p> -<p>Maintaining the security of your private key is of critical importance, both -to you and to the user. If you allow someone to use your key, or if you leave -your keystore and passwords in an unsecured location such that a third-party -could find and use them, your authoring identity and the trust of the user -are compromised. </p> +<p>The next time you build, the build tools will regenerate a new keystore and debug key.</p> -<p>If a third party should manage to take your key without your knowledge or -permission, that person could sign and distribute applications that maliciously -replace your authentic applications or corrupt them. Such a person could also -sign and distribute applications under your identity that attack other -applications or the system itself, or corrupt or steal user data. </p> +<p>Note that, if your development machine is using a non-Gregorian locale, the build tools may +erroneously generate an already-expired debug certificate, so that you get an error when trying +to compile your application. For workaround information, see the troubleshooting topic +<a href="{@docRoot}resources/faq/troubleshooting.html#signingcalendar">I can't compile my app +because the build tools generated an expired debug certificate</a>.</p> -<p>Your private key is required for signing all future versions of your application. If you lose or -misplace your key, you will not be able to publish updates to your existing application. You cannot -regenerate a previously generated key.</p> -<p>Your reputation as a developer entity depends on your securing your private -key properly, at all times, until the key is expired. Here are some tips for -keeping your key secure: </p> +<h2 id="signing-manually">Signing Your App Manually</h2> -<ul> -<li>Select strong passwords for the keystore and key.</li> -<li>When you generate your key with Keytool, <em>do not</em> supply the -<code>-storepass</code> and <code>-keypass</code> options at the command line. -If you do so, your passwords will be available in your shell history, -which any user on your computer could access.</li> -<li>Similarly, when signing your applications with Jarsigner, -<em>do not</em> supply the <code>-storepass</code> and <code>-keypass</code> -options at the command line. </li> -<li>Do not give or lend anyone your private key, and do not let unauthorized -persons know your keystore and key passwords.</li> -<li>Keep the keystore file containing your private key that you <a href="#cert">generate with the -Keytool</a> in a safe, secure place.</li> -</ul> +<p>You do not need Android Studio or the ADT plugin for Eclipse to sign your app. You can sign +your app from the command line using standard tools from the Android SDK and the JDK. To sign +an app in release mode from the command line:</p> -<p>In general, if you follow common-sense precautions when generating, using, -and storing your key, it will remain secure. </p> +<ol> +<li> + <p>Generate a private key using + <code><a href="http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html">keytool</a></code>. + For example:</p> +<pre> +$ keytool -genkey -v -keystore my-release-key.keystore +-alias alias_name -keyalg RSA -keysize 2048 -validity 10000 +</pre> + <p>This example prompts you for passwords for the keystore and key, and to provide the + Distinguished Name fields for your key. It then generates the keystore as a file called + <code>my-release-key.keystore</code>. The keystore contains a single key, valid for 10000 days. + The alias is a name that you will use later when signing your app.</p> +</li> +<li style="margin-top:18px"> + <p>Compile your app in release mode to obtain an unsigned APK.</p> +</li> +<li style="margin-top:18px"> + <p>Sign your app with your private key using + <code><a href="http://docs.oracle.com/javase/6/docs/technotes/tools/windows/jarsigner.html">jarsigner</a></code>: + </p> +<pre> +$ jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 +-keystore my-release-key.keystore my_application.apk alias_name +</pre> + <p>This example prompts you for passwords for the keystore and key. It then modifies the APK + in-place to sign it. Note that you can sign an APK multiple times with different keys.</p> +</li> +<li style="margin-top:18px"> + <p>Verify that your APK is signed. For example:</p> +<pre> +$ jarsigner -verify -verbose -certs my_application.apk +</pre> +</li> +<li style="margin-top:18px"> + <p>Align the final APK package using + <code><a href="{@docRoot}tools/help/zipalign.html">zipalign</a></code>.</p> +<pre> +$ zipalign -v 4 your_project_name-unaligned.apk your_project_name.apk +</pre> + <p><code>zipalign</code> ensures that all uncompressed data starts with a particular byte + alignment relative to the start of the file, which reduces the amount of RAM consumed by an + app.</p> +</li> +</ol> diff --git a/docs/html/tools/publishing/preparing.jd b/docs/html/tools/publishing/preparing.jd index 413b56e..5265fce 100644 --- a/docs/html/tools/publishing/preparing.jd +++ b/docs/html/tools/publishing/preparing.jd @@ -22,7 +22,7 @@ page.title=Preparing for Release <ol> <li><a href="{@docRoot}tools/publishing/publishing_overview.html">Publishing Overview</a></li> <li><a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a></li> - <li><a href="{@docRoot}distribute/googleplay/publish/preparing.html">Launch Checklist for Google Play</a></li> + <li><a href="{@docRoot}distribute/tools/launch-checklist.html">Launch Checklist for Google Play</a></li> </ol> </div> </div> @@ -44,7 +44,7 @@ application marketplace such as Google Play.</p> <p>This document summarizes the main tasks you need to perform to prepare your application for release. The tasks that are described in this document apply to all Android applications regardless how they are released or distributed to users. If you are releasing your application through Google -Play, you should also read <a href="{@docRoot}distribute/googleplay/publish/preparing.html">Publishing +Play, you should also read <a href="{@docRoot}distribute/tools/launch-checklist.html">Publishing Checklist for Google Play</a> to be sure your release-ready application satisfies all Google Play requirements.</p> @@ -191,6 +191,13 @@ were created in your project.</p> added to your code, such as {@link android.os.Debug#startMethodTracing()} and {@link android.os.Debug#stopMethodTracing()} method calls.</p> +<p class="caution"><strong>Important:</strong> Ensure that you disable debugging for +your app if using {@link android.webkit.WebView} to display paid for content or if using JavaScript +interfaces, since debugging allows users to inject scripts and extract content using Chrome +DevTools. To disable debugging, use the +{@link android.webkit.WebView#setWebContentsDebuggingEnabled(boolean) WebView.setWebContentsDebuggingEnabled()} +method.</p> + <h4>Clean up your project directories</h4> <p>Clean up your project and make sure it conforms to the directory structure described in <a @@ -353,7 +360,7 @@ done testing and you are satisfied that the release version of your application behaves correctly, you can release your application to users. For more information, see <a href="{@docRoot}tools/publishing/publishing_overview.html#publishing-release">Releasing Your Application to Users</a>. If you are publishing your application on Google Play, see -<a href="{@docRoot}distribute/googleplay/publish/preparing.html">Launch Checklist +<a href="{@docRoot}distribute/tools/launch-checklist.html">Launch Checklist for Google Play</a>.</p> diff --git a/docs/html/tools/publishing/publishing_overview.jd b/docs/html/tools/publishing/publishing_overview.jd index ea01e20..c4b3bdf 100644 --- a/docs/html/tools/publishing/publishing_overview.jd +++ b/docs/html/tools/publishing/publishing_overview.jd @@ -16,7 +16,7 @@ page.title=Publishing Overview </ol> <h2>See also</h2> <ol> - <li><a href="{@docRoot}distribute/googleplay/publish/preparing.html">Publishing on Google Play</a></li> + <li><a href="{@docRoot}distribute/tools/launch-checklist.html">Publishing on Google Play</a></li> </ol> </div> </div> @@ -35,7 +35,7 @@ publish an Android application you perform two main tasks:</p> </li> </ul> -<p>Usually, you release your application through an application marketplace, such as <a href="{@docRoot}distribute/index.html">Google Play</a>. +<p>Usually, you release your application through an application marketplace, such as <a href="{@docRoot}distribute/googleplay/index.html">Google Play</a>. However, you can also release applications by sending them directly to users or by letting users download them from your own website.</p> @@ -157,7 +157,7 @@ marketplace for selling and buying Android applications.</p> </li> </ul> -<p>For information complete information, see <a href="{@docRoot}distribute/index.html">Google Play</a>.</p> +<p>For information complete information, see <a href="{@docRoot}distribute/googleplay/index.html">Google Play</a>.</p> <h3 id="publishing-email">Releasing your application through email</h3> diff --git a/docs/html/tools/publishing/versioning.jd b/docs/html/tools/publishing/versioning.jd index a1cfb30..6d3ec2f 100644 --- a/docs/html/tools/publishing/versioning.jd +++ b/docs/html/tools/publishing/versioning.jd @@ -25,7 +25,7 @@ page.title=Versioning Your Applications <ol> <li><a href="{@docRoot}tools/publishing/preparing.html">Preparing to Publish Your Application</a></li> -<li><a href="{@docRoot}distribute/googleplay/publish/preparing.html">Launch Checklist for Google Play</a></li> +<li><a href="{@docRoot}distribute/tools/launch-checklist.html">Launch Checklist for Google Play</a></li> <li><a href="{@docRoot}guide/topics/manifest/manifest-intro.html">The AndroidManifest.xml File</a></li> </ol> diff --git a/docs/html/tools/revisions/build-tools.jd b/docs/html/tools/revisions/build-tools.jd index c3c83ef..0abec2e 100644 --- a/docs/html/tools/revisions/build-tools.jd +++ b/docs/html/tools/revisions/build-tools.jd @@ -77,6 +77,45 @@ listing in the Android SDK Manager.</p> <div class="toggle-content opened"> <p><a href="#" onclick="return toggleContent(this)"> <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-content-img" + alt=""/>Build Tools, Revision 20.0.0</a> <em>(June 2014)</em> + </p> + <div class="toggle-content-toggleme"> + + <dl> + <dt>General Notes:</dt> + <dd> + <ul> + <li>Added support for Android Wear.</li> + </ul> + </dd> + </dl> + + </div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" + alt=""/>Build Tools, Revision 19.1.0</a> <em>(May 2014)</em> + </p> + <div class="toggle-content-toggleme"> + + <dl> + <dt>General Notes:</dt> + <dd> + <ul> + <li>Added <code>zipalign</code> to the Build Tools.</li> + <li>Modified <code>aapt</code> to ignore XML files that fail to compile.</li> + </ul> + </dd> + </dl> + + </div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" alt=""/>Build Tools, Revision 19.0.3</a> <em>(March 2014)</em> </p> <div class="toggle-content-toggleme"> diff --git a/docs/html/tools/revisions/platforms.jd b/docs/html/tools/revisions/platforms.jd index 5d1d13b..b5495c2 100644 --- a/docs/html/tools/revisions/platforms.jd +++ b/docs/html/tools/revisions/platforms.jd @@ -47,6 +47,34 @@ most recent release and restart the SDK Manager. If you do not, the latest Andro components will not be available for download.</p> +<h2 id="4.4">Android 4.4W</h2> + +<div class="toggle-content opened"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-opened.png" +class="toggle-content-img" alt="" />Revision 1</a> <em>(June 2014)</em> + </p> + + <div class="toggle-content-toggleme"> + + <p>Initial release for Android Wear.</p> + <p>Dependencies:</p> + <ul> + <li>Android SDK Platform-tools r20 or higher is required.</li> + <li>Android SDK Tools 23.0 or higher is required.</li> + </ul> + </div> + + <h3>Device Definitions</h3> + + <p>The platform includes the following device definitions for use in creating Android Virtual + Devices in the <a href="{@docRoot}tools/help/avd-manager.html">AVD Manager</a>:</p> + + <ul> + <li>Android Wear Round (320 x 320, hdpi)</li> + <li>Android Wear Square (320 x 320, hdpi)</li> + </ul> +</div> <h2 id="4.4">Android 4.4</h2> diff --git a/docs/html/tools/sdk/eclipse-adt.jd b/docs/html/tools/sdk/eclipse-adt.jd index 7d20d5e..cf33200 100644 --- a/docs/html/tools/sdk/eclipse-adt.jd +++ b/docs/html/tools/sdk/eclipse-adt.jd @@ -53,10 +53,152 @@ the ADT Plugin, as denoted by revision number. </p> <p>For a summary of all known issues in ADT, see <a href="http://tools.android.com/knownissues">http://tools.android.com/knownissues</a>.</p> - <div class="toggle-content opened"> <p><a href="#" onclick="return toggleContent(this)"> <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-content-img" + alt=""/>ADT 23.0.3</a> <em>(August 2014)</em> + </p> + + <div class="toggle-content-toggleme"> +<dl> + <dt>Dependencies:</dt> + + <dd> + <ul> + <li>Java 7 or higher is required if you are targeting the L Developer Preview.</li> + <li>Java 1.6 or higher is required if you are targeting other releases.</li> + <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li> + <li>This version of ADT is designed for use with + <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r23.0.2</a>. + If you haven't already installed SDK Tools r23.0.2 into your SDK, use the + Android SDK Manager to do so.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li>Fixed an issue where ADT displayed a <code>NullPointerException</code> warning dialog + when a valid SDK was not configured. (<a href="http://b.android.com/73313">Issue + 73313</a>)</li> + <li>Fixed a minor issue with RenderScript support.</li> + <li>Disabled APK compression.</li> + </ul> + </dd> +</dl> +</div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" + alt=""/>ADT 23.0.2</a> <em>(July 2014)</em> + </p> + + <div class="toggle-content-toggleme"> +<dl> + <dt>Dependencies:</dt> + + <dd> + <ul> + <li>Java 7 or higher is required if you are targeting the L Developer Preview.</li> + <li>Java 1.6 or higher is required if you are targeting other releases.</li> + <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li> + <li>This version of ADT is designed for use with + <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r23.0.2</a>. + If you haven't already installed SDK Tools r23.0.2 into your SDK, use the + Android SDK Manager to do so.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li>ADT Bundle shows the Java perspective by default.</li> + <li>ADT Bundle 23.0.0 and prior versions would not allow updating the ADT plugins + due to conflicting dependencies. This version fixes that bug and should allow + updating to future versions of the ADT plugins.</li> + </ul> + </dd> +</dl> +</div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" + alt=""/>ADT 23.0.0</a> <em>(June 2014)</em> + </p> + + <div class="toggle-content-toggleme"> +<dl> + <dt>Dependencies:</dt> + + <dd> + <ul> + <li>Java 7 or higher is required if you are targeting the L Developer Preview.</li> + <li>Java 1.6 or higher is required if you are targeting other releases.</li> + <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li> + <li>This version of ADT is designed for use with + <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r23.0.0</a>. + If you haven't already installed SDK Tools r23.0.0 into your SDK, use the + Android SDK Manager to do so.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li>Added the Android Wear tools and system images.</li> + </ul> + </dd> +</dl> +</div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" + alt=""/>ADT 22.6.3</a> <em>(April 2014)</em> + </p> + + <div class="toggle-content-toggleme"> +<dl> + <dt>Dependencies:</dt> + + <dd> + <ul> + <li>Java 1.6 or higher is required.</li> + <li>Eclipse Indigo (Version 3.7.2) or higher is required.</li> + <li>This version of ADT is designed for use with + <a href="{@docRoot}tools/sdk/tools-notes.html">SDK Tools r22.6.3</a>. + If you haven't already installed SDK Tools r22.6.3 into your SDK, use the + Android SDK Manager to do so.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li>Fixed a problem where the AVD manager allowed creating Android Wear virtual devices + with a target API Level lower than 19.</li> + <li>Fixed the description of Android Wear system images in the SDK Manager.</li> + </ul> + </dd> + + <dt>Known Issues:</dt> + <dd> + <p>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.</p> + </dd> +</dl> +</div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" alt=""/>ADT 22.6.2</a> <em>(March 2014)</em> </p> @@ -78,6 +220,11 @@ href="http://tools.android.com/knownissues">http://tools.android.com/knownissues <dt>General Notes:</dt> <dd> <ul> + <li><p>Changed the URL for the Android Developer Tools update site to require HTTPS.</p> + <p class="note"><strong>Note:</strong> If you are + <a href="{@docRoot}sdk/installing/installing-adt.html">updating ADT</a>, make sure + you use HTTPS in the URL for the Android Developer Tools update site.</p> + </li> <li>Fixed a problem where Eclipse was non-responsive for a few seconds after opening an XML file. (<a href="http://b.android.com/67084">Issue 67084</a>)</li> <li>Fixed a problem where the SDK Manager threw a <code>NullPointerException</code> after @@ -88,7 +235,6 @@ href="http://tools.android.com/knownissues">http://tools.android.com/knownissues <code>drawable-large-*</code> directories.</li> <li>Fixed a problem with Nexus 5 Android virtual devices created from the command line where the SD card file system was read-only.</li> - <li>Changed the URL for the Android Developer Tools Update Site from HTTP to HTTPS.</li> </ul> </dd> </dl> diff --git a/docs/html/tools/sdk/ndk/index.jd b/docs/html/tools/sdk/ndk/index.jd index a22dc90..71b15d5 100644 --- a/docs/html/tools/sdk/ndk/index.jd +++ b/docs/html/tools/sdk/ndk/index.jd @@ -2,33 +2,59 @@ ndk=true page.template=sdk -ndk.mac64_download=android-ndk-r9d-darwin-x86_64.tar.bz2 -ndk.mac64_bytes=400339614 -ndk.mac64_checksum=c914164b1231c574dbe40debef7048be +ndk.mac64_download=android-ndk32-r10-darwin-x86_64.tar.bz2 +ndk.mac64_bytes=411610468 +ndk.mac64_checksum=3ce1fa3dbe7a188f5d2640fd2f7ca944 -ndk.mac32_download=android-ndk-r9d-darwin-x86.tar.bz2 -ndk.mac32_bytes=393866116 -ndk.mac32_checksum=ee6544bd8093c79ea08c2e3a6ffe3573 +ndk.mac32_download=android-ndk32-r10-darwin-x86.tar.bz2 +ndk.mac32_bytes=404768263 +ndk.mac32_checksum=1824eec1f6749b6cb7bb306a3b924c33 -ndk.linux64_download=android-ndk-r9d-linux-x86_64.tar.bz2 -ndk.linux64_bytes=412879983 -ndk.linux64_checksum=c7c775ab3342965408d20fd18e71aa45 +ndk.linux64_download=android-ndk32-r10-linux-x86_64.tar.bz2 +ndk.linux64_bytes=420671390 +ndk.linux64_checksum=e3ff629d212a8106a43415862fa39baf -ndk.linux32_download=android-ndk-r9d-linux-x86.tar.bz2 -ndk.linux32_bytes=405218267 -ndk.linux32_checksum=6c1d7d99f55f0c17ecbcf81ba0eb201f +ndk.linux32_download=android-ndk32-r10-linux-x86.tar.bz2 +ndk.linux32_bytes=420078216 +ndk.linux32_checksum=8d9a5faa6e77b43bfae0f169079b21c4 -ndk.win64_download=android-ndk-r9d-windows-x86_64.zip -ndk.win64_bytes=520997454 -ndk.win64_checksum=8cd244fc799d0e6e59d65a59a8692588 +ndk.win64_download=android-ndk32-r10-windows-x86_64.zip +ndk.win64_bytes=529850429 +ndk.win64_checksum=b11f9239344f7c377ed5b627f0fb236e -ndk.win32_download=android-ndk-r9d-windows-x86.zip -ndk.win32_bytes=491440074 -ndk.win32_checksum=b16516b611841a075685a10c59d6d7a2 +ndk.win32_download=android-ndk32-r10-windows-x86.zip +ndk.win32_bytes=500135685 +ndk.win32_checksum=0a3c01147abba945cc4ef5837519ec97 -ndk.debug_info_download=android-ndk-r9d-cxx-stl-libs-with-debug-info.zip -ndk.debug_info_bytes=104947363 -ndk.debug_info_checksum=906c8d88e0f02295c3bfe6b8e98a1a35 + + +ndk.mac64_64_download=android-ndk64-r10-darwin-x86_64.tar.bz2 +ndk.mac64_64_bytes=327740247 +ndk.mac64_64_checksum=72561b27acc6192a2e81b345ea128a20 + +ndk.mac32_64_download=android-ndk64-r10-darwin-x86.tar.bz2 +ndk.mac32_64_bytes=323736411 +ndk.mac32_64_checksum=5bbaf9d8051ba5d2c0fff74cfd87c374 + +ndk.linux64_64_download=android-ndk64-r10-linux-x86_64.tar.bz2 +ndk.linux64_64_bytes=339708042 +ndk.linux64_64_checksum=737290195583268b7fbff4aa56465ab6 + +ndk.linux32_64_download=android-ndk64-r10-linux-x86.tar.bz2 +ndk.linux32_64_bytes=338544906 +ndk.linux32_64_checksum=bea5d027baeb948cbff6af840d26b80d + +ndk.win64_64_download=android-ndk64-r10-windows-x86_64.zip +ndk.win64_64_bytes=417411195 +ndk.win64_64_checksum=91879ec85539b45313a21b9526b911a8 + +ndk.win32_64_download=android-ndk64-r10-windows-x86.zip +ndk.win32_64_bytes=396751892 +ndk.win32_64_checksum=f79070ace2cde9ebf6a2e2be4a61ac7a + +ndk.debug_info_download=android-ndk-r10-cxx-stl-libs-with-debug-info.zip +ndk.debug_info_bytes=253198908 +ndk.debug_info_checksum=c2a90c43d17dbb5f0609cc8237491788 page.title=Android NDK @@ -56,129 +82,261 @@ box-shadow: -10px 10px 50px #888; This is the Android Software Development Kit License Agreement <h3>1. Introduction</h3> -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.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.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. +1.3 "Google" means Google Inc., a Delaware corporation with principal place of business at 1600 +Amphitheatre Parkway, Mountain View, CA 94043, United States. <h3>2. Accepting this License Agreement</h3> -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.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.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. +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. <h3>3. SDK License from Google</h3> -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.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.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.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.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.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.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.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. +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. <h3>4. Use of the SDK by You</h3> -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. +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. <h3>5. Your Developer Credentials</h3> -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. +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. <h3>6. Privacy and Information</h3> -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.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. +6.2 The data collected is examined in the aggregate to improve the SDK and is maintained in +accordance with Google's Privacy Policy. <h3>7. Third Party Applications</h3> -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.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.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. +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. <h3>8. Using Android APIs</h3> 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.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. +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. <h3>9. Terminating this License Agreement</h3> -9.1 This License Agreement will continue to apply until terminated by either you or Google as set out below. +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.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. +(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. +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. <h3>10. DISCLAIMER OF WARRANTIES</h3> -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.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.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. +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. <h3>11. LIMITATION OF LIABILITY</h3> -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. +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. <h3>12. Indemnification</h3> -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. +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. <h3>13. Changes to the License Agreement</h3> -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. +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. <h3>14. General Legal Terms</h3> -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. +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. <em>November 13, 2012</em> @@ -245,8 +403,8 @@ This is the Android Software Development Kit License Agreement but it always increases your app complexity. In general, you should only use the NDK if it is essential to your app—never because you simply prefer to program in C/C++.</p> - <p>Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't - allocate much memory, such as signal processing, physics simulation, and so on. When examining + <p>Typical good candidates for the NDK are CPU-intensive workloads such as game engines, + signal processing, physics simulation, and so on. When examining whether or not you should develop in native code, think about your requirements and see if the Android framework APIs provide the functionality that you need.</p> @@ -272,6 +430,182 @@ $('#Downloads').after($('#download-table')); <p> <a href="#" onclick="return toggleContent(this)"> <img src="/assets/images/triangle-opened.png" class="toggle-content-img" alt="" + >Android NDK, Revision 10</a> <em>(July 2014)</em> + </p> + <div class="toggle-content-toggleme"> + <dl> + <dt>Important changes:</dt> + <dd> + <ul> + <li>Added 3 new ABIs, all 64-bit: arm64-v8a, x86_64, mips64.</li> Note that: + <ul> + <li>GCC 4.9 is the default compiler for 64-bit ABIs. Clang is currently version 3.4. +<code>NDK_TOOLCHAIN_VERSION=clang</code> + may not work for arm64-v8a and mips64.</li> + <li>Android API level L is the first level with 64-bit support. Note that this API +level is a temporary one, and only for L-preview. An actual API level number will replace it at +L-release.</li> + <li>This release includes now includes <code>all32</code> and <code>all64</code> +settings for <code>APP_ABI</code>. + <ul> + <li><code>APP_ABI=all32</code> is equivalent to +<code>APP_ABI=armeabi,armeabi-v7a,x86,mips</code>.</li> + <li><code>APP_ABI=all64</code> is equivalent to +<code>APP_ABI=arm64-v8a,x86_64,mips64</code>.</li> + <li><code>APP_ABI=all</code> selects all ABIs.</li> + </ul> + <li>The new GNU libstdc++ in Android-L contains all <code><tr1/cmath></code> +Before defining your own math function, check <code>_GLIBCXX_USE_C99_MATH_TR1</code> to see a +function with that name already exists, in order to avoid "multiple definition" errors from the +linker.</li> + <li>The cpu-features library has been updated for the ARMv8 kernel. The existing +cpu-features library may fail to detect the presence of NEON on the ARMv8 platform. Recompile your +code with the new version.</li> + </ul> + <li>Added a new <code>platforms/android-L/</code> API directory. It includes:</li> + <ul> + <li>Updated Bionic headers, which had not changed from Android API levels 3 +(Cupcake) to 19 (KitKat). This new version, for level L, is to be synchronized with AOSP.</li> + <li>New media APIs and a native-codec sample.</li> + <li>An updated <code>Android.h</code> header for SLES/OpenSLES, enabling support for +single-precision, floating-point audio format in AudioPlayer.</li> + <li>GLES 3.1 and AEP extensions to <code>libGLESv3.so.</code></li> + <li>GLES2 and GLES3 headers updated to the latest official Khronos versions.</li> + </ul> + <li>Added GCC 4.9 compilers to the 32-/64-bit ABIs. GCC 4.9 is the default (only) compiler +for 64-bit ABIs, as previously mentioned. For 32-bit ABIs, you must explcitly enable GCC 4.9, as +GCC 4.6 is still the default.</li> + <ul> + <li>For ndk-build, enable 32-bit, GCC 4.9 building either by adding +<code>NDK_TOOLCHAIN_VERSION=4.9</code> to <code>Application.mk</code>, or exporting it as an +environment variable from the command line.</li> + <li>For a standalone toolchain, use the <code> --toolchain=</code> option in the +<code>make-standalone-toolchain.sh</code> script. For example: <code>--toolchain=arm-linux-androideabi-4.9.</code></li> + </ul> + <li>Upgraded GDB to version 7.6 in GCC 4.8/4.9 and x86*. Since GDB is still at version GDB-7.3.x in +GCC 4.6 (the default for ARM and MIPS), you must set +<code>NDK_TOOLCHAIN_VERSION=4.8</code> or <code>4.9</code> to enable ndk-gdb to select GDB 7.6.</li> + <li>Added the <code>-mssse3</code> build option to provide SSSE3 support, and made it the default for ABI x86 +(upgrading from SSE3). The image released by Google does not contain SSSE3 instructions.</li> + <li>Updated GCC 4.8 to 4.8.3.</li> + <li>Improved ARM libc++ EH support by switching from gabi++ to libc++abi. For details, see the "C++ Support" section of the documentation. + Note that:</li> + <ul> + <li>All tests except for locale now pass for Clang 3.4 and GCC 4.8. For more +information, see the "C++ Support" section of the documentation.</li> + <li>The libc++ libraries for X86 and MIPS libc++ still use gabi++.</li> + <li>GCC 4.7 and later can now use <atomic>.</li> + <li>You must add <code>-fno-strict-aliasing</code> if you use <code> <list></code>, because <code>__list_imp::_end</code>_ breaks + TBAA rules. (Issue <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61571">61571</a>.)</li> + <li>As of GCC 4.6, LIBCXX_FORCE_REBUILD:=true no longer rebuilds libc++. Rebuilding it +requires the use of a different compiler. Note that Clang 3.3 is untested.</li> + </ul> + <li>mclinker is now version 2.7, and has aarch64 Linux support.</li> + <li>Added precompiled header support for headers specified by <code>LOCAL_PCH</code>. (Issue <a href="http://b.android.com/25412">25412</a>).</li> + </dd> + <dl> + + + <dt>Important bug fixes:</dt> + <dd> + <ul> + <li>Fixed libc++ so that it now compiles <code>std::feof</code>, etc. (Issue <a +href="http://b.android.com/66668">66668</a>).</li> + <li>Fixed a Clang 3.3/3.4 atomic library call that caused crashes in some of the libc++ +tests for ABI armeabi.</li> + <li>Fixed Clang 3.4 crashes that were occurring on reading precompiled headers. (Issue <a +href="http://b.android.com/66657">66657</a>).</li> + <li>Fixed the Clang 3.3/3.4 <code>-O3</code> assert on:</li> + <code>llvm-3.2/llvm/include/llvm/MDBuilder.h:64: llvm::MDNode* +llvm::MDBuilder::createBranchWeights(llvm::ArrayRef<unsigned int>): Assertion Weights.size() >= 2 +&& "Need at least two branch weights!"</code> (Issue <a href="http://b.android.com/57381">57381</a>). + <li>Fixed the following Clang 3.3/3.4 crash:</li> + <code>Assertion failed: (!Fn && "cast failed but able to resolve overload expression!!"), function CheckCXXCStyleCast, file +Volumes/data/ndk-toolchain/src/llvm-3.3/llvm/tools/clang/lib/Sema/SemaCast.cpp, line 2018</code>. +(Issue <a href="http://b.android.com/66950">66950</a>). + </ul> + </dd> + + <dt>Other bug fixes:</dt> + <dd> + <ul> + <li>Fixed headers:</li> + <ul> + <li>Fixed 32-bit <code>ssize_t</code> to be <code>int</code> instead of <code>long +int</code>.</li> + <li>Fixed <code>WCHAR_MIN</code> and <code>WCHAR_MAX</code> so that they they take +appropriate signs according to the architecture they're running on:</li> + <ul> + <li>X86/MIPS: signed. + <li>ARM: unsigned. + <li>To force X86/MIPS to default to unsigned, use +<code>-D__WCHAR_UNSIGNED__</code>.</li> + <li>To force <code>wchar_t</code> to be 16 bits, use <code>-fshort-wchar</code>.</li> + </ul> + <li>Removed non-existent symbols from 32-bit <code>libc.so</code>, and added <code>pread64</code>, +<code>pwrite64</code>, <code>ftruncate64</code> for +Android API level 12 and higher. (Issue <a href="http://b.android.com/69319">69319</a>). For more +information, see the commit message accompanying AOSP change list + <a href="https://android-review.googlesource.com/#/c/94137">94137</a>.</li> + </ul> + <li>Fixed GCC warning about redefinition of <code>putchar</code>. Warning message reads:</li> + <code>include/stdio.h:236:5: warning: conflicts with previous declaration here +[-Wattributes] int putchar(int);</code> (Change list <a +href="https://android-review.googlesource.com/#/c/91185">91185</a>). + <li>Fixed <code>make-standalone-toolchain.sh --stl=libc++</code> so that it:</li> + <ul> + <li>Copies <code>cxxabi.h</code>. (Issue <a +href="http://b.android.com/68001">68001</a>).</li> + <li>Runs in directories other than the NDK install directory. (Issues <a +href="http://b.android.com/67690">67690</a> and <a href="http://b.android.com/68647">68647</a>).</li> + </ul> + <li>Fixed GCC/Windows to quote arguments only when necessary for spawning processes in +external programs. This change decreases the likelihood of exceeding the 32K length limit.</li> + <li>Fixed an issue that made it impossible to adjust the <code>APP_PLATFORM</code> +environment variable.</li> + <li>Fixed the implementation of <code>IsSystemLibrary()</code> in crazy_linker so that it +uses <code>strrchr()</code> + instead of <code>strchr()</code> to find the library path's true basename.</li> + <li>Fixed native-audio's inability to build in debug mode.</li> + <li>Fixed gdb's inability to print extreme floating-point numbers. (Issue <a +href="http://b.android.com/69203">69203</a>).</li> + <li>Fixed Clang 3.4 inability to compile with <code>-Wl,-shared</code> (as opposed to +<code>-shared</code>, which + had no compilation issues). The problem was that Clang added <code>-pie</code> for Android +targets if neither <code>-shared</code> nor <code>-static</code> existed. This behavior, which was +incorrect, caused the linker to complain that <code>-shared</code> and <code>-pie</code> could not +co-exist.</li> + + </ul> + </dd> + + + <dt>Other changes:</dt> + <dd> + <ul> + <li>Added <code>arm_neon.h</code> to the x86 toolchain so that it now emulates ~47% of +Neon. There is currently no support for 64-bit types. For more information, see the section on ARM +Neon intrinsics support in the x86 documentation.</li> + <li>Ported ARM/GOT_PREL optimization (present in GCC 4.6 built from the GCC google branch) to +ARM GCC 4.8/4.9. This optimization sometimes reduces instruction count when accessing global +variables. As an example, see the build.sh script in +<code>$NDK/tests/build/b14811006-GOT_PREL-optimization/</code>.</li> + <li>Added ARM version for STL gabi++, stlport, and libc++. They now have both it and Thumb +mode.</li> + <li>It is now possible to call the make-standalone-toolchain.sh script with +<code>--toolchain=x86_64-linux-android-4.9</code>, which is equivalent to +<code>--toolchain=x86_64-4.9</code>.</li> + </dd> + </ul> + </dl> + </div> +</div> + + +<div class="toggle-content closed"> + <p> + <a href="#" onclick="return toggleContent(this)"> <img + src="/assets/images/triangle-closed.png" class="toggle-content-img" alt="" >Android NDK, Revision 9d</a> <em>(March 2014)</em> </p> <div class="toggle-content-toggleme"> @@ -284,7 +618,7 @@ $('#Downloads').after($('#download-table')); still the default compiler.</li> <li>Added <code>APP_ABI=armeabi-v7a-hard</code>, with additional multilib option <code>-mfloat-abi=hard</code>. These options are for -use with ARM GCC 4.6/4.8 and clang 3.3/3.4 (which use 4.8's assembler, linker, +use with ARM GCC 4.6/4.8 and Clang 3.3/3.4 (which use 4.8's assembler, linker, and libs). When using these options, note the following changes:</li> <ul> <li> When executing the <code>ndk-build</code> script, add the @@ -322,7 +656,7 @@ to create a standalone toolchain with libc++ headers/lib.</li> </ul> For more information, see <code>CPLUSPLUS-SUPPORT.html</code>. -(Issue <a href="b.android.com/36496">36496</a>)</li> +(Issue <a href="http://b.android.com/36496">36496</a>)</li> </ul> </dd> <dl> @@ -337,7 +671,7 @@ specialization of a template with a dependent, non-type template argument. (GCC Issue <a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59052">59052</a>)</li> <li>Added more modules to prebuilt python (Issue <a -href="b.android.com/59902">59902</a>): +href="http://b.android.com/59902">59902</a>): <ul> <li>Mac OS X: <code>zlib</code>, <code>bz2</code>, <code>_curses</code>, <code>_curses_panel</code>, <code>_hashlib</code>, @@ -637,7 +971,8 @@ GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01' (<a href="http://b.android.com/55826">Issue 55826</a>)</li> <li>Fixed Clang 3.3 MIPS compiler problem where HI and LO registers are incorrectly reused.</li> - <li>Fixed issue with MIPS 4.7 ICE in {@code dbx_reg_number}. The error message is as follows: + <li>Fixed issue with MIPS 4.7 ICE in {@code dbx_reg_number}. The error message is as +follows: <pre> external/icu4c/i18n/decimfmt.cpp:1322:1: internal compiler error: in dbx_reg_number, at dwarf2out.c:10185 @@ -721,11 +1056,13 @@ LOCAL_LDFLAGS += -fopenmp <li>Modified GCC builds so that all {@code libgcc.a} files are built with <code>-funwind-tables</code> to allow the stack to be unwound past previously blocked points, such as <code>__aeabi_idiv0</code>.</li> - <li>Added Ingenic MXU support in MIPS GCC4.6/4.7/4.8 with new <code>-mmxu</code> option.</li> + <li>Added Ingenic MXU support in MIPS GCC4.6/4.7/4.8 with new <code>-mmxu</code> +option.</li> <li>Extended MIPS GCC4.6/4.7/4.8 <code>-mldc1-sdc1</code> to control ldxc1/sdxc1 too</li> <li>Added crazy linker. For more information, see {@code sources/android/crazy_linker/README.TXT}.</li> - <li>Fixed {@code bitmap-plasma} to draw to full screen rather than a 200x200 pixel area.</li> + <li>Fixed {@code bitmap-plasma} to draw to full screen rather than a 200x200 pixel +area.</li> <li>Reduced linux and darwin toolchain sizes by 25% by creating symlinks to identical files. </li> </ul> @@ -935,7 +1272,8 @@ LOCAL_LDFLAGS += -fopenmp <li>Added two flags to re-enable two optimizations in upstream Clang but disabled in NDK for better compatibility with code compiled by GCC: <ul> - <li>Added a {@code -fcxx-missing-return-semantics} flag to re-enable <em>missing return + <li>Added a {@code -fcxx-missing-return-semantics} flag to re-enable <em>missing +return semantics</em> in Clang 3.2+. Normally, all paths should terminate with a return statement for a value-returning function. If this is not the case, clang inserts an undefined instruction (or trap in debug mode) at the path without a return @@ -1079,7 +1417,8 @@ LOCAL_LDFLAGS += -fopenmp (<a href="https://android-review.googlesource.com/#/c/52134">Change 52134</a>)</li> <li>Fixed Clang 3.1 internal compiler error when using Eigen library. (<a href="http://b.android.com/41246">Issue 41246</a>)</li> - <li>Fixed Clang 3.1 internal compiler error including {@code <chrono>} in C++11 mode. + <li>Fixed Clang 3.1 internal compiler error including {@code <chrono>} in C++11 +mode. (<a href="http://b.android.com/39600">Issue 39600</a>)</li> <li>Fixed Clang 3.1 internal compiler error when generating object code for a method call to a uniform initialized {@code rvalue}. @@ -1088,7 +1427,8 @@ LOCAL_LDFLAGS += -fopenmp (<a href="https://android-review.googlesource.com/#/c/52154">Change 52154</a>)</li> <li>Fixed problem with GNU Debugger (GDB) SIGILL when debugging on Android 4.1.2. (<a href="http://b.android.com/40941">Issue 40941</a>)</li> - <li>Fixed problem where GDB cannot set {@code source:line} breakpoints when symbols contain + <li>Fixed problem where GDB cannot set {@code source:line} breakpoints when symbols +contain long, indirect file paths. (<a href="http://b.android.com/42448">Issue 42448</a>)</li> <li>Fixed GDB {@code read_program_header} for MIPS PIE executables. @@ -1182,7 +1522,8 @@ LOCAL_LDFLAGS += -fopenmp <li>Enabled MIPS floating-point {@code madd/msub/nmadd/nmsub/recip/rsqrt} instructions with 32-bit FPU.</li> <li>Enabled graphite loop optimizer in GCC 4.6 and 4.7 to allow more optimizations: - {@code -fgraphite}, {@code -fgraphite-identity}, {@code -floop-block}, {@code -floop-flatten}, + {@code -fgraphite}, {@code -fgraphite-identity}, {@code -floop-block}, {@code +-floop-flatten}, {@code -floop-interchange}, {@code -floop-strip-mine}, {@code -floop-parallelize-all}, and {@code -ftree-loop-linear}. (<a href="http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html">info</a>)</li> @@ -1379,7 +1720,9 @@ Expected in: /usr/lib/libSystem.B.dylib</pre> <li>Updated {@code make-standalone-toolchain.sh} to accept the suffix {@code -clang3.1} which is equivalent to adding {@code --llvm-version=3.1} to the GCC 4.6 toolchain.</li> <li>Updated GCC and Clang bug report URL to: - <a href="http://source.android.com/source/report-bugs.html">http://source.android.com/source/report-bugs.html</a></li> + <a +href="http://source.android.com/source/report-bugs.html">http://source.android.com/source/report-bug +s.html</a></li> <li>Added ARM ELF support to {@code llvm-objdump}.</li> <li>Suppressed <em>treating c input as c++</em> warning for Clang builds.</li> <li>Updated build so that only the 32-bit version of {@code libiberty.a} is built and @@ -1418,7 +1761,8 @@ Expected in: /usr/lib/libSystem.B.dylib</pre> <a href="http://code.google.com/p/android/issues/list">report any issues</a>.</p></li> <li>Added Gold linker {@code ld.gold} for the Windows toolchain. Gold linker is also the default for ARM and X86 on all hosts. You may override it to use the {@code ld.bfd} - linker by adding {@code LOCAL_LDFLAGS += -fuse-ld=bfd} to {@code Android.mk}, or by passing + linker by adding {@code LOCAL_LDFLAGS += -fuse-ld=bfd} to {@code Android.mk}, or by +passing {@code -fuse-ld=bfd} to the g++/clang++ command line that does the linking.</li> <li>Added checks for spaces in the NDK path to the {@code ndk-build[.cmd]} and {@code ndk-gdb} scripts, to prevent build errors that are difficult to diagnose.</li> @@ -1605,7 +1949,8 @@ Expected in: /usr/lib/libSystem.B.dylib</pre> <li>Replaced {@code link.h} for MIPS with new version supporting all platforms.</li> <li>Removed {@code linux-unistd.h}</li> <li>Move GLibc-specific macros {@code LONG_LONG_MIN}, {@code LONG_LONG_MAX} and - {@code ULONG_LONG_MAX} from {@code <pthread.h>} to {@code <limits.h>}.</li> + {@code ULONG_LONG_MAX} from {@code <pthread.h>} to {@code +<limits.h>}.</li> </ul> </li> <li>Fixed a buffer overflow in {@code ndk-stack-parser}.</li> @@ -1767,7 +2112,8 @@ info</a>).</li> <li>Fixed ARM {@code strip} command to preserve the original {@code p_align} and {@code p_flags} in {@code GNU_RELRO} section if they are valid. Without this fix, programs built with {@code -fPIE} could not be debugged. (<a -href="http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/elf.c.diff?cvsroot=src&r1=1.552&r2=1.553">more info</a>)</li> +href="http://sourceware.org/cgi-bin/cvsweb.cgi/src/bfd/elf.c.diff?cvsroot=src&r1=1.552&r2=1.553">mor +e info</a>)</li> </ul> </li> <li>Disabled {@code sincos()} optimization for compatibility with older @@ -2505,7 +2851,8 @@ LOCAL_CPP_EXTENSION := .cpp .cxx </li> - <li>You can build a standalone x86 toolchain using the <code>--toolchain=x86-4.4.3</code> + <li>You can build a standalone x86 toolchain using the +<code>--toolchain=x86-4.4.3</code> option when calling <code>make-standalone-toolchain.sh</code>. See <code>docs/STANDALONE-TOOLCHAIN.html</code> for more details. </li> @@ -2548,7 +2895,8 @@ LOCAL_CPP_EXTENSION := .cpp .cxx <li>Fixed a bug where code linked against <code>gnustl_static</code> crashed when run on platform releases older than API level 8 (Android 2.2).</li> - <li><code>ndk-gdb</code>: Fixed a bug that caused a segmentation fault when debugging Android 3.0 + <li><code>ndk-gdb</code>: Fixed a bug that caused a segmentation fault when debugging +Android 3.0 or newer devices.</li> <li><code><android/input.h></code>: Two functions that were introduced in API level @@ -2617,12 +2965,14 @@ float AMotionEvent_getHistoricalRawY(const AInputEvent* motion_event, </p> <div class="toggle-content-toggleme"> - <p>This release of the NDK does not include any new features compared to r5. The r5b release addresses the + <p>This release of the NDK does not include any new features compared to r5. The r5b release +addresses the following problems in the r5 release: </p> <ul> <li>The r5 binaries required glibc 2.11, but the r5b binaries are generated with a special - toolchain that targets glibc 2.7 or higher instead. The Linux toolchain binaries now run on Ubuntu 8.04 or higher. </li> + toolchain that targets glibc 2.7 or higher instead. The Linux toolchain binaries now run on +Ubuntu 8.04 or higher. </li> <li>Fixes a compiler bug in the arm-linux-androideabi-4.4.3 toolchain. The previous binary generated invalid thumb instruction sequences when dealing with signed chars.</li> @@ -2642,21 +2992,29 @@ float AMotionEvent_getHistoricalRawY(const AInputEvent* motion_event, with the new NDK toolchain.</li> <li>Builds in Cygwin are faster by avoiding calls to <code>cygpath -m</code> from GNU Make for every source or object file, which caused problems - with very large source trees. In case this doesn't work properly, define <code>NDK_USE_CYGPATH=1</code> in your + with very large source trees. In case this doesn't work properly, define +<code>NDK_USE_CYGPATH=1</code> in your environment to use <code>cygpath -m</code> again.</li> - <li>The Cygwin installation now notifies the user of invalid installation paths that contain spaces. Previously, an invalid path - would output an error that complained about an incorrect version of GNU Make, even if the right one was installed. + <li>The Cygwin installation now notifies the user of invalid installation paths that +contain spaces. Previously, an invalid path + would output an error that complained about an incorrect version of GNU Make, even if the +right one was installed. </ul> </li> - <li>Fixed a typo that prevented the <code>NDK_MODULE_PATH</code> environment variable from working properly when + <li>Fixed a typo that prevented the <code>NDK_MODULE_PATH</code> environment variable from +working properly when it contained multiple directories separated with a colon. </li> <li>The <code>prebuilt-common.sh</code> script contains fixes to check the compiler for 64-bit generated machine code, instead of relying on the host tag, which - allows the 32-bit toolchain to rebuild properly on Snow Leopard. The toolchain rebuild scripts now also support + allows the 32-bit toolchain to rebuild properly on Snow Leopard. The toolchain rebuild scripts +now also support using a 32-bit host toolchain.</li> - <li>A missing declaration for <code>INET_ADDRSTRLEN</code> was added to <code><netinet/in.h></code>.</li> - <li>Missing declarations for <code>IN6_IS_ADDR_MC_NODELOCAL</code> and <code>IN6_IS_ADDR_MC_GLOBAL</code> were added to <code><netinet/in6.h></code>.</li> - <li>'asm' was replaced with '__asm__' in <code><asm/byteorder.h></code> to allow compilation with <code>-std=c99</code>.</li> + <li>A missing declaration for <code>INET_ADDRSTRLEN</code> was added to +<code><netinet/in.h></code>.</li> + <li>Missing declarations for <code>IN6_IS_ADDR_MC_NODELOCAL</code> and +<code>IN6_IS_ADDR_MC_GLOBAL</code> were added to <code><netinet/in6.h></code>.</li> + <li>'asm' was replaced with '__asm__' in <code><asm/byteorder.h></code> to allow +compilation with <code>-std=c99</code>.</li> </ul> </div> </div> @@ -2673,8 +3031,10 @@ float AMotionEvent_getHistoricalRawY(const AInputEvent* motion_event, of native code. Using the APIs, developers have direct native access to events, audio, graphics and window management, assets, and storage. Developers can also implement the Android application lifecycle in native code with help from the new - {@link android.app.NativeActivity} class. For detailed information describing the changes in this - release, read the <code>CHANGES.HTML</code> document included in the downloaded NDK package. + {@link android.app.NativeActivity} class. For detailed information describing the changes +in this + release, read the <code>CHANGES.HTML</code> document included in the downloaded NDK +package. </p> <dl> <dt>General notes:</dt> @@ -2703,35 +3063,46 @@ float AMotionEvent_getHistoricalRawY(const AInputEvent* motion_event, </ul> </li> - <li>Includes a new toolchain (based on GCC 4.4.3), which generates better code, and can also now + <li>Includes a new toolchain (based on GCC 4.4.3), which generates better code, and can +also now be used as a standalone cross-compiler, for people who want to build their stuff with <code>./configure && make</code>. See - docs/STANDALONE-TOOLCHAIN.html for the details. The binaries for GCC 4.4.0 are still provided, + docs/STANDALONE-TOOLCHAIN.html for the details. The binaries for GCC 4.4.0 are still +provided, but the 4.2.1 binaries were removed.</li> - <li>Adds support for prebuilt static and shared libraries (docs/PREBUILTS.html) and module + <li>Adds support for prebuilt static and shared libraries (docs/PREBUILTS.html) and +module exports and imports to make sharing and reuse of third-party modules much easier (docs/IMPORT-MODULE.html explains why).</li> - <li>Provides a default C++ STL implementation (based on STLport) as a helper module. It can be used either - as a static or shared library (details and usage examples are in sources/android/stlport/README). Prebuilt - binaries for STLport (static or shared) and GNU libstdc++ (static only) are also provided if you choose to + <li>Provides a default C++ STL implementation (based on STLport) as a helper module. It +can be used either + as a static or shared library (details and usage examples are in +sources/android/stlport/README). Prebuilt + binaries for STLport (static or shared) and GNU libstdc++ (static only) are also +provided if you choose to compile against those libraries instead of the default C++ STL implementation. - C++ Exceptions and RTTI are not supported in the default STL implementation. For more information, see + C++ Exceptions and RTTI are not supported in the default STL implementation. For more +information, see docs/CPLUSPLUS-SUPPORT.HTML.</li> - <li>Includes improvements to the <code>cpufeatures</code> helper library that improves reporting - of the CPU type (some devices previously reported ARMv7 CPU when the device really was an ARMv6). We + <li>Includes improvements to the <code>cpufeatures</code> helper library that improves +reporting + of the CPU type (some devices previously reported ARMv7 CPU when the device really was +an ARMv6). We recommend developers that use this library to rebuild their applications then upload to Google Play to benefit from the improvements.</li> <li>Adds an EGL library that lets you create and manage OpenGL ES textures and services.</li> - <li>Adds new sample applications, <code>native-plasma</code> and <code>native-activity</code>, + <li>Adds new sample applications, <code>native-plasma</code> and +<code>native-activity</code>, to demonstrate how to write a native activity.</li> - <li>Includes many bugfixes and other small improvements; see docs/CHANGES.html for a more + <li>Includes many bugfixes and other small improvements; see docs/CHANGES.html for a +more detailed list of changes.</li> </ul> </dd> @@ -3043,7 +3414,8 @@ later)</li> </table> <p>For more information about API Level and its relationship to Android platform versions, - see <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">Android API Levels</a>.</p> + see <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">Android API +Levels</a>.</p> </li> <li>Additionally, an application using the OpenGL ES APIs should declare a @@ -3061,7 +3433,8 @@ later)</li> </pre> <p>For more information, see the <a href= - "{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code></a> + +"{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code></a> documentation.</p> </li> @@ -3104,7 +3477,8 @@ later)</li> <p>Before you get started make sure that you have downloaded the latest <a href= "{@docRoot}sdk/index.html">Android SDK</a> and upgraded your applications and environment as - needed. The NDK is compatible with older platform versions but not older versions of the SDK tools. + needed. The NDK is compatible with older platform versions but not older versions of the SDK +tools. Also, take a moment to review the <a href="#Reqs">System and Software Requirements</a> for the NDK, if you haven't already.</p> @@ -3178,7 +3552,8 @@ included with the NDK package.</p> <p>Write a native activity, which allows you to implement the lifecycle callbacks in native code. The Android SDK provides the {@link android.app.NativeActivity} class, which is a convenience class that notifies your - native code of any activity lifecycle callbacks (<code>onCreate()</code>, <code>onPause()</code>, + native code of any activity lifecycle callbacks (<code>onCreate()</code>, +<code>onPause()</code>, <code>onResume()</code>, etc). You can implement the callbacks in your native code to handle these events when they occur. Applications that use native activities must be run on Android 2.3 (API Level 9) or later.</p> @@ -3230,7 +3605,8 @@ information)</li> difference between the two instruction sets is that ARMv7-A supports hardware FPU, Thumb-2, and NEON instructions. You can target either or both of the instruction sets — ARMv5TE is the default, but switching to ARMv7-A is as easy as adding a single line to the application's - <code>Application.mk</code> file, without needing to change anything else in the file. You can also build for + <code>Application.mk</code> file, without needing to change anything else in the file. You can +also build for both architectures at the same time and have everything stored in the final <code>.apk</code>. Complete information is provided in the CPU-ARCH-ABIS.HTML in the NDK package.</p> @@ -3311,13 +3687,15 @@ information)</li> <li>CHANGES.HTML — a complete list of changes to the NDK across all releases.</li> - <li>DEVELOPMENT.HTML — describes how to modify the NDK and generate release packages for it</li> + <li>DEVELOPMENT.HTML — describes how to modify the NDK and generate release packages for +it</li> <li>HOWTO.HTML — information about common tasks associated with NDK development</li> <li>IMPORT-MODULE.HTML — describes how to share and reuse modules</li> - <li>LICENSES.HTML — information about the various open source licenses that govern the Android NDK</li> + <li>LICENSES.HTML — information about the various open source licenses that govern the +Android NDK</li> <li>NATIVE-ACTIVITY.HTML — describes how to implement native activities</li> diff --git a/docs/html/tools/sdk/tools-notes.jd b/docs/html/tools/sdk/tools-notes.jd index 14b5505..c2aaae8 100644 --- a/docs/html/tools/sdk/tools-notes.jd +++ b/docs/html/tools/sdk/tools-notes.jd @@ -28,6 +28,144 @@ href="http://tools.android.com/knownissues">http://tools.android.com/knownissues <div class="toggle-content opened"> <p><a href="#" onclick="return toggleContent(this)"> <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-content-img" + alt=""/>SDK Tools, Revision 23.0.2</a> <em>(July 2014)</em> + </p> + + <div class="toggle-content-toggleme"> + + <dl> + <dt>Dependencies:</dt> + + <dd> + <ul> + <li>Android SDK Platform-tools revision 19 or later.</li> + <li>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 + <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 23.0.2.</li> + <li>If you are developing outside Eclipse, you must have + <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li>Added ProGuard <code>.bat</code> files that were missing.</li> + <li>Added the <code>proguard-android.txt</code> file that was missing.</li> + <li>Renamed the <code>lombok-ast-0.2.2.jar</code> file to <code>lombok-ast.jar</code>, + which should allow running lint from the command line.</li> + </ul> + </dd> + </div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" + alt=""/>SDK Tools, Revision 23.0.0</a> <em>(June 2014)</em> + </p> + + <div class="toggle-content-toggleme"> + + <dl> + <dt>Dependencies:</dt> + + <dd> + <ul> + <li>Android SDK Platform-tools revision 19 or later.</li> + <li>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 + <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 23.0.0.</li> + <li>If you are developing outside Eclipse, you must have + <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li>Added the Android Wear tools and system images.</li> + </ul> + </dd> + </div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" + alt=""/>SDK Tools, Revision 22.6.4</a> <em>(June 2014)</em> + </p> + + <div class="toggle-content-toggleme"> + + <dl> + <dt>Dependencies:</dt> + + <dd> + <ul> + <li>Android SDK Platform-tools revision 18 or later.</li> + <li>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 + <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.6.3.</li> + <li>If you are developing outside Eclipse, you must have + <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li>Fixed an issue with the x86 emulator that caused Google Maps to crash. + (<a href="http://b.android.com/69385">Issue 69385</a>)</li> + <li>Fixed minor OpenGL issues.</li> + </ul> + </dd> + </div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" + alt=""/>SDK Tools, Revision 22.6.3</a> <em>(April 2014)</em> + </p> + + <div class="toggle-content-toggleme"> + + <dl> + <dt>Dependencies:</dt> + + <dd> + <ul> + <li>Android SDK Platform-tools revision 18 or later.</li> + <li>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 + <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.6.3.</li> + <li>If you are developing outside Eclipse, you must have + <a href="http://ant.apache.org/">Apache Ant</a> 1.8 or later.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li>Fixed a problem where the AVD manager allowed creating Android Wear virtual devices + with a target API Level lower than 19.</li> + <li>Fixed the description of Android Wear system images in the SDK Manager.</li> + </ul> + </dd> + + <dt>Known Issues:</dt> + <dd> + <p>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.</p> + </dd> + </div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" alt=""/>SDK Tools, Revision 22.6.2</a> <em>(March 2014)</em> </p> diff --git a/docs/html/tools/support-library/features.jd b/docs/html/tools/support-library/features.jd index 65148bf..78946ee 100644 --- a/docs/html/tools/support-library/features.jd +++ b/docs/html/tools/support-library/features.jd @@ -225,8 +225,7 @@ com.android.support:gridlayout-v7:18.0.+ <p>This library provides {@link android.support.v7.media.MediaRouter}, {@link android.support.v7.media.MediaRouteProvider}, and related media classes that -support the <a href="https://developers.google.com/cast/">Google Cast -developer preview</a>. </p> +support <a href="https://developers.google.com/cast/docs/android_sender">Google Cast</a>. </p> <p>In general, the APIs in the v7 mediarouter library provide a means of controlling the routing of media channels and streams from the current device to @@ -258,9 +257,8 @@ com.android.support:mediarouter-v7:18.0.+ <p class="caution">The v7 mediarouter library APIs introduced in Support Library r18 are subject to change in later revisions of the Support Library. At this -time, we recommend using the library only in connection with the <a -href="https://developers.google.com/cast/">Google Cast -developer preview</a>. </p> +time, we recommend using the library only in connection with <a +href="https://developers.google.com/cast/docs/android_sender">Google Cast</a>. </p> <h2 id="v8">v8 Support Library</h2> diff --git a/docs/html/tools/support-library/index.jd b/docs/html/tools/support-library/index.jd index 389238f..68eca49 100644 --- a/docs/html/tools/support-library/index.jd +++ b/docs/html/tools/support-library/index.jd @@ -58,10 +58,63 @@ page.title=Support Library <p>This section provides details about the Support Library package releases.</p> - <div class="toggle-content opened"> <p><a href="#" onclick="return toggleContent(this)"> <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-content-img" alt="" +/>Android Support Library, revision 20</a> <em>(July 2014)</em> + </p> + <div class="toggle-content-toggleme"> + <dl> + <dt>Changes for v4 support library:</dt> + <dd> + <ul> + <li>Added extended notification support for Android Wear in + {@link android.support.v4.app.NotificationCompat.WearableExtender}, which allows you + to specify wearable-specific features in your notifications.</li> + <li>Added {@link android.support.v4.app.NotificationCompat.Action.WearableExtender}, + which allows actions to be added on wearable notifications.</li> + <li>Added {@link android.support.v4.app.NotificationManagerCompat}, which allows you + to issue notifications that properly support wearable features.</li> + <li>Added {@link android.support.v4.app.RemoteInput}, which allows a handheld device + to receive voice input from a notification that appears on a wearable device.</li> + <li>Improved the handling of touch feedback in + {@link android.support.v4.widget.SwipeRefreshLayout}.</li> + </ul> + </dd> + </dl> + </div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" alt="" +/>Android Support Library, revision 19.1.0</a> <em>(March 2014)</em> + </p> + <div class="toggle-content-toggleme"> + <dl> + <dt>Changes for v4 support library:</dt> + <dd> + <ul> + <li>Added the {@link android.support.v4.widget.SwipeRefreshLayout} class, + which enables users to refresh the contents of a view with a vertical + swipe gesture.</li> + <li>Fixed accessibility issues with navigation drawers.</li> + </ul> + </dd> + + <dt>Changes for v7 appcompat library:</dt> + <dd> + <ul> + <li>Fixed background issues with the action bar.</li> + </ul> + </dd> + </dl> + </div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" alt="" />Android Support Library, revision 19.0.1</a> <em>(December 2013)</em> </p> <div class="toggle-content-toggleme"> diff --git a/docs/html/tools/testing/testing_accessibility.jd b/docs/html/tools/testing/testing_accessibility.jd index daf9b36..20948fa 100644 --- a/docs/html/tools/testing/testing_accessibility.jd +++ b/docs/html/tools/testing/testing_accessibility.jd @@ -179,7 +179,7 @@ focus navigation and audible prompts.</p> </p> <p>For more information about using TalkBack, see -<a href="http://support.google.com/nexus/bin/answer.py?hl=en&answer=2700928">Use TalkBack</a>.</p> +<a href="https://support.google.com/accessibility/android/topic/3529932">TalkBack</a>.</p> <h4 id="testing-ebt">Testing with Explore by Touch</h4> @@ -207,8 +207,7 @@ option is not available.</p> </ol> <p>For more information about using the Explore by Touch features, see -<a href="http://support.google.com/nexus/bin/answer.py?hl=en&answer=2700722">Use Explore by -Touch</a>.</p> +<a href="https://support.google.com/accessibility/android/answer/6006598">Touch Exploration</a>.</p> <h3 id="test-navigation">Testing focus navigation</h3> @@ -231,7 +230,7 @@ Touch</a>.</p> <p>Gesture navigation is an accessibility navigation mode that allows users to navigate Android devices and applications using specific - <a href="http://support.google.com/nexus/bin/answer.py?hl=en&answer=2700718">gestures</a>. This + <a href="https://support.google.com/accessibility/android/answer/6006598">gestures</a>. This navigation mode is available on Android 4.1 (API Level 16) and higher.</p> <p class="note"><strong>Note:</strong> Accessibility gestures provide a different navigation path @@ -248,8 +247,7 @@ content, keyboard and D-pad navigation only allow focus on input fields and butt </ul> <p>For more information about using Explore by Touch accessibility gestures, see -<a href="http://support.google.com/android/bin/topic.py?hl=en&topic=2492346">Accessibility -gestures</a>.</p> +<a href="https://support.google.com/accessibility/android/answer/6006598">Touch Exploration</a>.</p> <p class="note"> <strong>Note:</strong> Accessibility services other than TalkBack may map accessibility gestures diff --git a/docs/html/tools/tools_toc.cs b/docs/html/tools/tools_toc.cs index 382165c..8eb9cbf 100644 --- a/docs/html/tools/tools_toc.cs +++ b/docs/html/tools/tools_toc.cs @@ -1,50 +1,40 @@ <ul id="nav"> <li class="nav-section"> - <div class="nav-section-header empty"> - <a href="<?cs var:toroot ?>tools/index.html"><span class="en">Developer Tools</span></a> - </div> - </li> - - <li class="nav-section"> <div class="nav-section-header"><a href="<?cs var:toroot ?>sdk/index.html"><span class="en">Download</span></a></div> <ul> - <li><a href="<?cs var:toroot ?>sdk/installing/bundle.html"> - <span class="en">Setting Up the ADT Bundle</span></a></li> + <li><a href="<?cs var:toroot ?>sdk/installing/index.html"> + <span class="en">Installing the SDK</span></a></li> - <li class="nav-section"> - <div class="nav-section-header"> - <a href="<?cs var:toroot ?>sdk/installing/index.html"><span class="en">Setting Up - an Existing IDE</span></a></div> - <ul> - <li><a href="<?cs var:toroot ?>sdk/installing/installing-adt.html"> - <span class="en">Installing the Eclipse Plugin</span></a></li> - <li><a href="<?cs var:toroot ?>sdk/installing/adding-packages.html"> - <span class="en">Adding Platforms and Packages</span></a></li> - </ul> - </li> - - <li class="nav-section"> - <div class="nav-section-header"> - <a href="<?cs var:toroot ?>sdk/installing/studio.html">Android Studio</a> - </div> - <ul> - <li><a href="<?cs var:toroot ?>sdk/installing/migrate.html"> - Migrating from Eclipse</a></li> - <li><a href="<?cs var:toroot ?>sdk/installing/studio-tips.html"> - Tips and Tricks</a></li> - <li><a href="<?cs var:toroot ?>sdk/installing/studio-layout.html"> - Using the Layout Editor</a></li> - </ul> - </li> - <li><a href="<?cs var:toroot ?>sdk/exploring.html"> - <span class="en">Exploring the SDK</span></a></li> - <li><a href="<?cs var:toroot ?>tools/sdk/ndk/index.html">Download the NDK</a> - </li> + <li><a href="<?cs var:toroot ?>sdk/installing/adding-packages.html"> + <span class="en">Adding SDK Packages</span></a></li> </ul> </li> + + <li class="nav-section"> + <div class="nav-section-header"> + <a href="<?cs var:toroot ?>sdk/installing/studio.html">Android Studio</a> + </div> + <ul> + <li><a href="<?cs var:toroot ?>sdk/installing/migrate.html"> + Migrating from Eclipse</a></li> + <li><a href="<?cs var:toroot ?>sdk/installing/create-project.html"> + Creating a Project</a></li> + <li><a href="<?cs var:toroot ?>sdk/installing/studio-tips.html"> + Tips and Tricks</a></li> + <li><a href="<?cs var:toroot ?>sdk/installing/studio-androidview.html"> + Using the Android Project View</a></li> + <li><a href="<?cs var:toroot ?>sdk/installing/studio-layout.html"> + Using the Layout Editor</a></li> + <li><a href="<?cs var:toroot ?>sdk/installing/studio-build.html"> + Building Your Project with Gradle</a></li> + <li><a href="<?cs var:toroot ?>sdk/installing/studio-debug.html"> + Debugging with Android Studio</a></li> + </ul> + </li> + <li class="nav-section"> <div class="nav-section-header"> <a href="<?cs var:toroot ?>tools/workflow/index.html"><span class="en">Workflow</span></a> @@ -170,7 +160,13 @@ class="en">Support Library</span></a></div> class="en">Tools Help</span></a></div> <ul> <li><a href="<?cs var:toroot ?>tools/help/adb.html">adb</a></li> - <li><a href="<?cs var:toroot ?>tools/help/adt.html">ADT</a></li> + <li class="nav-section"> + <div class="nav-section-header"><a href="<?cs var:toroot ?>tools/help/adt.html">ADT</a></div> + <ul> + <li><a href="<?cs var:toroot ?>sdk/installing/installing-adt.html"> + <span class="en">Installing the Eclipse Plugin</span></a></li> + </ul> + </li> <li><a href="<?cs var:toroot ?>tools/help/android.html">android</a></li> <li><a href="<?cs var:toroot ?>tools/help/avd-manager.html">AVD Manager</a></li> <li><a href="<?cs var:toroot ?>tools/help/bmgr.html">bmgr</a> @@ -240,6 +236,11 @@ class="en">Platforms</span></a></li> </ul> </li> + <li class="nav-section"> + <div class="nav-section-header empty"> + <a href="<?cs var:toroot ?>tools/sdk/ndk/index.html">NDK</a> + </div> + </li> <li class="nav-section"> <div class="nav-section-header"> |