diff options
Diffstat (limited to 'docs/html/tools')
23 files changed, 1330 insertions, 201 deletions
diff --git a/docs/html/tools/debugging/systrace.jd b/docs/html/tools/debugging/systrace.jd index 287abe6..6472152 100644 --- a/docs/html/tools/debugging/systrace.jd +++ b/docs/html/tools/debugging/systrace.jd @@ -1,4 +1,5 @@ -page.title=Analyzing Display and Performance with Systrace +page.title=Analyzing Display and Performance +page.tags=systrace,speed parent.title=Debugging parent.link=index.html @jd:body @@ -12,10 +13,11 @@ parent.link=index.html <li><a href="#generate">Generating Traces</a> <ol> <li><a href="#limit-trace">Limiting trace data</a></li> - <li><a href="#config-categories">Configuring trace data categories</a></li> - <li><a href="#running">Running a trace</a></li> + <li><a href="#running-4.3">Tracing on Android 4.3 and higher</a> + <li><a href="#running-4.2">Tracing on Android 4.2 and lower</a></li> </ol> </li> + <li><a href="#app-trace">Tracing Application Code</a></li> <li><a href="#analysis">Analyzing Traces</a> <ol> <li><a href="#long-processes">Long running processes</a></li> @@ -25,13 +27,12 @@ parent.link=index.html </ol> <h2>See also</h2> <ol> - <li><a href="{@docRoot}tools/help/systrace.html">Systrace</a> - </li> + <li><a href="{@docRoot}tools/help/systrace.html">Systrace</a></li> </ol> </div> </div> -<p>After building features, eliminating bugs and cleaning up your code, you should spend some +<p>After building features, eliminating bugs, and cleaning up your code, you should spend some time looking at the performance of your application. The speed and smoothness with which your application draws pixels and performs operations has an significant impact on your users' experience.</p> @@ -42,21 +43,21 @@ parent.link=index.html threaded processes for resources, which can cause performance problems that are hard to diagnose. </p> -<p>The {@code systrace} tool allows you to collect and review code execution data for your +<p>The Systrace tool allows you to collect and review code execution data for your application and the Android system. You can use this data to diagnose execution problems and improve the performance of your application.</p> <h2 id="overview">Overview</h2> -<p>{@code systrace} helps you analyze how the execution of your application fits into the larger +<p>Systrace helps you analyze how the execution of your application fits into the larger Android environment, letting you see system and applications process execution on a common timeline. The tool allows you to generate highly detailed, interactive reports from devices running Android 4.1 and higher, such as the report in figure 1.</p> <img src="{@docRoot}images/systrace/report.png" alt="Systrace example report" id="figure1" /> <p class="img-caption"> - <strong>Figure 1.</strong> An example {@code systrace} report on 5 seconds of process execution + <strong>Figure 1.</strong> An example Systrace report on 5 seconds of process execution for a running application and related Android system processes. </p> @@ -64,16 +65,21 @@ parent.link=index.html <h2 id="generate">Generating Traces</h2> <p>In order to create a trace of your application, you must perform a few setup steps. First, you - must have a device running Android 4.1 or higher. Setup the device for + must have a device running Android 4.1 or higher. Set up the device for <a href="{@docRoot}tools/device.html#setting-up">debugging</a>, connect it to your development - system and install your application. Some types of trace information, specifically disk activity - and kernel work queues, require root access to the device, but most {@code systrace} log data - only requires that the device be enabled for developer debugging.</p> + system, and install your application. Some types of trace information, specifically disk activity + and kernel work queues, require that you have root access to the device. However, most Systrace + log data only requires that the device be enabled for developer debugging.</p> + +<p>Systrace traces can be run either from a + <a href="{@docRoot}tools/help/systrace.html#options">command line</a> or from a + <a href="{@docRoot}tools/help/systrace.html#gui">graphical user interface</a>. This guide + focuses on using the command line options.</p> <h3 id="limit-trace">Limiting trace data</h3> -<p>The {@code systrace} tool can generate a potentially huge amount of data from applications +<p>The Systrace tool can generate a potentially huge amount of data from applications and system sources. To limit the amount of data the tool collects and make the data more relevant to your analysis, use the following options:</p> @@ -81,39 +87,68 @@ parent.link=index.html <li>Limit the amount of time covered by the trace with the {@code -t, --time} option. The default length of a trace is 5 seconds.</li> <li>Limit the size of the data collected by the trace with the {@code -b, --buf-size} option.</li> - <li>Specify what types of processes are traced using the {@code --set-tags} option and the - {@code --disk}, {@code --cpu-freq}, {@code --cpu-idle}, {@code --cpu-load} options.</li> + <li>Specify what types of processes are traced. The types of processes that can be traced depends + on the version of Android you are running: + <ul> + <li>Android 4.2 and lower devices: Use the {@code --set-tags} option and the {@code --disk}, + {@code --cpu-freq}, {@code --cpu-idle}, {@code --cpu-load} options.</li> + <li>Android 4.3 and higher devices: Use the {@code --list-categories} option to see what + categories are available on your test device.</li> + </ul> + </li> </ul> -<h3 id="config-categories">Configuring trace data categories</h3> +<h3 id="running-4.3">Tracing on Android 4.3 and higher</h3> + +<p>To run a trace on Android 4.3 and higher devices:</p> + +<ol> + <li>Make sure the device is connected through a USB cable and is + <a href="{@docRoot}tools/device.html#setting-up">enabled for debugging</a>.</li> + <li>Run the trace with the options you want, for example: +<pre> +$ cd android-sdk/platform-tools/systrace +$ python systrace.py --time=10 -o mynewtrace.html sched gfx view wm +</pre> + </li> + <li>On the device, execute any user actions you want be included in the trace.</li> +</ol> + +<p>For more information on the available options for running Systrace, see the +<a href="{@docRoot}tools/help/systrace.html#options-4.3">Systrace</a> help page.</p> + -<p>To use {@code systrace} effectively, you must specify the types of processes you want to trace. +<h3 id="running-4.2">Tracing on Android 4.2 and lower</h3> + +<p>To use Systrace effectively with devices running Android 4.2 and lower, + you must configure the types of processes you want to trace before running a trace. The tool can gather the following types of process information:</p> <ul> <li>General system processes such as graphics, audio and input processes (selected using trace - <a href="{@docRoot}tools/help/systrace.html#tags">Tags</a>).</li> + <a href="{@docRoot}tools/help/systrace.html#tags">category tags</a>).</li> <li>Low level system information such as CPU, kernel and disk activity (selected using - <a href="{@docRoot}tools/help/systrace.html#options">Options</a>).</li> + <a href="{@docRoot}tools/help/systrace.html#options">options</a>).</li> </ul> -<p>To set trace tags for {@code systrace} using the command-line:</p> +<p>To set trace tags for Systrace using the command-line:</p> <ol> <li>Use the {@code --set-tags} option: <pre> -$> python systrace.py --set-tags=gfx,view,wm +$ cd android-sdk/platform-tools/systrace +$ python systrace.py --set-tags=gfx,view,wm </pre> </li> <li>Stop and restart the {@code adb} shell to enable tracing of these processes. <pre> -$> adb shell stop -$> adb shell start +$ adb shell stop +$ adb shell start </pre></li> </ol> -<p>To set trace tags for {@code systrace} using the device user interface:</p> +<p>To set trace tags for Systrace using the device user interface:</p> <ol> <li>On the device connected for tracing, navigate to: <strong>Settings > @@ -126,9 +161,6 @@ $> adb shell start selecting trace tags using this method. </p> - -<h3 id="running">Running a trace</h3> - <p>After you have configured the category tags for your trace, you can start collecting information for analysis.</p> @@ -139,21 +171,77 @@ $> adb shell start <a href="{@docRoot}tools/device.html#setting-up">enabled for debugging</a>.</li> <li>Run the trace with the low-level system trace options and limits you want, for example: <pre> -$> python systrace.py --cpu-freq --cpu-load --time=10 -o mytracefile.html +$ python systrace.py --cpu-freq --cpu-load --time=10 -o mytracefile.html </pre> </li> <li>On the device, execute any user actions you want be included in the trace.</li> </ol> +<p>For more information on the available options for running Systrace, see the +<a href="{@docRoot}tools/help/systrace.html#options-pre-4.3">Systrace</a> help page.</p> + + +<h2 id="app-trace">Tracing Application Code</h2> + +<p>The Systrace tool can trace the execution of code within your application. In Android +4.3 (API level 18) and higher, you can use the methods of the {@link android.os.Trace} class to +add instrumentation to your application code and see the results in a Systrace report.</p> + +<p>The following code example shows how to use the {@link android.os.Trace} class to track +execution of an application method, including two nested code blocks within that method.</p> + +<pre> +public void ProcessPeople() { + Trace.beginSection("ProcessPeople"); + try { + Trace.beginSection("Processing Jane"); + try { + // code for Jane task... + } finally { + Trace.endSection(); // ends "Processing Jane" + } + + Trace.beginSection("Processing John"); + try { + // code for John task... + } finally { + Trace.endSection(); // ends "Processing John" + } + } finally { + Trace.endSection(); // ends "ProcessPeople" + } +} +</pre> +<p class="note"> + <strong>Note:</strong> When you nest trace calls within each other, the + {@link android.os.Trace#endSection} method ends the most recently called + {@link android.os.Trace#beginSection} method. This means that a trace started within another + trace cannot extend beyond the end of the enclosing trace, so make sure your beginning and + ending method calls are properly matched to measure your applications processing. +</p> + +<p class="note"> + <strong>Note:</strong> Traces must begin and end on the same thread. Do not call + {@link android.os.Trace#beginSection} on one thread of execution and then attempt to end the + trace with a call to {@link android.os.Trace#endSection} on another thread. +</p> + +<p>When using application-level tracing with Systrace, you must specify the package name of your +application in the user interface or specify the {@code -a} or {@code --app=} options on the +command line. For more information, see the +<a href="{@docRoot}tools/help/systrace.html">Systrace</a> help page.</p> + +<!-- todo: add ndk coverage --> + <h2 id="analysis">Analyzing Traces</h2> -<p>After you have generated a trace using {@code systrace}, it lists the location of the output +<p>After you have generated a trace using Systrace, it lists the location of the output file and you can open the report using a web browser. How you use the trace data depends on the performance issues you are investigating. However, this section provides some general instructions on how to analyze a trace.</p> -<p>The reports generated by {@code systrace} are interactive, allowing you to zoom into and out of +<p>The reports generated by Systrace are interactive, allowing you to zoom into and out of the process execution details. Use the <em>W</em> key to zoom in, the <em>S</em> key to zoom out, the <em>A</em> key to pan left and the <em>D</em> key to pan right. Select a task in timeline using your mouse to get more information about the task. @@ -193,7 +281,7 @@ id="figure2" /> <h3 id="display-interupts">Interruptions in display execution</h3> -<p>The {@code systrace} tool is particularly useful in analyzing application display slowness, +<p>The Systrace tool is particularly useful in analyzing application display slowness, or pauses in animations, because it shows you the execution of your application across multiple system processes. With display execution, drawing screen frames with a regular rhythm is essential for good performance. Having a regular rhythm for display ensures that animations and motion are @@ -201,7 +289,7 @@ id="figure2" /> from the users perspective.</p> <p>If you are analyzing an application for this type of problem, examine the - <strong>SurfaceFlinger</strong> process in the {@code systrace} report where your application is + <strong>SurfaceFlinger</strong> process in the Systrace report where your application is also executing to look for places where it drops out of its regular rhythm.</p> <img src="{@docRoot}images/systrace/display-rhythm.png" alt="Systrace exerpt of display processing" @@ -231,9 +319,9 @@ id="figure3" /> </p> <p class="note"> - <strong>Note:</strong> When using {@code systrace} to analyze display problems, make sure + <strong>Note:</strong> When using Systrace to analyze display problems, make sure you activate the tracing tags for <strong>Graphics</strong> and <strong>Views</strong>. </p> -<p>For more information on the command line options and keyboard controls for {@code systrace}, -see the <a href="{@docRoot}tools/help/systrace.html">Systrace</a> reference page.</p>
\ No newline at end of file +<p>For more information on the command line options and keyboard controls for Systrace, +see the <a href="{@docRoot}tools/help/systrace.html">Systrace</a> help page.</p>
\ No newline at end of file diff --git a/docs/html/tools/help/adb.jd b/docs/html/tools/help/adb.jd index c25990f..c339943 100644 --- a/docs/html/tools/help/adb.jd +++ b/docs/html/tools/help/adb.jd @@ -27,6 +27,7 @@ page.tags="adb" </li> <li><a href="#logcat">Enabling logcat logging</a></li> <li><a href="#stopping">Stopping the adb server</a></li> + <li><a href="#wireless">Wireless usage</a></li> </ol> </div> @@ -1342,3 +1343,100 @@ application and sends 500 pseudo-random events to it.</p> You can then restart the server by issuing any other adb command. </p> +<h2 id="wireless">Wireless usage</h2> + +<p> +adb is usually used over USB. However, it is also possible to use over +Wi-Fi, as described here. +</p> + +<ol> + +<li> +Connect Android device and adb host computer +to a common Wi-Fi network accessible to both. +We have found that not all access points +are suitable; you may need to use an access point +whose firewall is configured properly to support adb. +</li> + +<li> +Connect the device with USB cable to host. +</li> + +<li> +Make sure adb is running in USB mode on host. +<pre> +$ adb usb +restarting in USB mode +</pre> +</li> + +<li> +Connect to the device over USB. +<pre> +$ adb devices +List of devices attached +######## device +</pre> +</li> + +<li> +Restart host adb in tcpip mode. +<pre> +$ adb tcpip 5555 +restarting in TCP mode port: 5555 +</pre> +</li> + +<li> +Find out the IP address of the Android device: +Settings -> About tablet -> Status -> IP address. +Remember the IP address, of the form <code>#.#.#.#</code>. +</li> + +<li> +Connect adb host to device: +<pre> +$ adb connect #.#.#.# +connected to #.#.#.#:5555 +</pre> +</li> + +<li> +Remove USB cable from device, and confirm you can still access device: +<pre> +$ adb devices +List of devices attached +#.#.#.#:5555 device +</pre> + +</ol> + +<p> +You're now good to go! +</p> + +<p> +If the adb connection is ever lost: +</p> + +<ol> + +<li> +Make sure that your host is still connected to the same Wi-Fi network your Android device is. +</li> + +<li> +Reconnect by executing the "adb connect" step again. +</li> + +<li> +Or if that doesn't work, reset your adb host: +<pre> +adb kill-server +</pre> +and then start over from the beginning. +</li> + +</ol> diff --git a/docs/html/tools/help/avd-manager.jd b/docs/html/tools/help/avd-manager.jd index ed90f43..20f6253 100644 --- a/docs/html/tools/help/avd-manager.jd +++ b/docs/html/tools/help/avd-manager.jd @@ -8,8 +8,11 @@ and manage Android Virtual Devices (AVDs), which are required by the <p>You can launch the AVD Manager in one of the following ways:</p> <ul> - <li>In Eclipse: select <strong>Window > AVD Manager</strong>, or click - the AVD Manager icon in the Eclipse toolbar.</li> + <li>In Eclipse: select <strong>Window > Android Virtual Device Manager</strong>, or click + the AVD Manager icon in the toolbar.</li> + + <li>In Android Studio: select <strong>Tools > Android > AVD Manager</strong>, or click + the AVD Manager icon in the toolbar.</li> <li>In other IDEs: Navigate to your SDK's <code>tools/</code> directory and execute <code>android avd</code>.</li> diff --git a/docs/html/tools/help/monitor.jd b/docs/html/tools/help/monitor.jd index e1fe772..513eb10 100644 --- a/docs/html/tools/help/monitor.jd +++ b/docs/html/tools/help/monitor.jd @@ -15,13 +15,14 @@ page.title=Device Monitor <p>Android Device Monitor is a stand-alone tool that provides a graphical user interface for several Android application debugging and analysis tools. The Monitor tool does not -require installation of a integrated development environment, such as Eclipse, and encapsulates the +require installation of an integrated development environment, such as Eclipse, and encapsulates the following tools:</p> <ul> <li><a href="{@docRoot}tools/debugging/ddms.html">DDMS</a></li> <li><a href="gltracer.html">Tracer for OpenGL ES</a></li> <li><a href="hierarchy-viewer.html">Hierarchy Viewer</a></li> + <li><a href="systrace.html">Systrace</a></li> <li><a href="traceview.html">Traceview</a></li> <li>Pixel Perfect magnification viewer</li> </ul> diff --git a/docs/html/tools/help/proguard.jd b/docs/html/tools/help/proguard.jd index 3ba7db2..aa9a0bc 100644 --- a/docs/html/tools/help/proguard.jd +++ b/docs/html/tools/help/proguard.jd @@ -25,11 +25,14 @@ parent.link=index.html <h2>See also</h2> <ol> - <li><a href="http://proguard.sourceforge.net/manual/introduction.html">ProGuard - Manual »</a></li> - - <li><a href="http://proguard.sourceforge.net/manual/retrace/introduction.html">ProGuard - ReTrace Manual »</a></li> + <li> + <a href="http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/introduction.html">ProGuard + Manual »</a> + </li> + <li> + <a href="http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/retrace/introduction.html">ProGuard + ReTrace Manual »</a> + </li> </ol> </div> </div> @@ -146,14 +149,14 @@ proguard.config=/path/to/proguard.cfg </pre> <p>There are many options and considerations when using the <code>-keep</code> option, so it is - highly recommended that you read the <a href="http://proguard.sourceforge.net/manual/introduction.html">ProGuard - Manual</a> for more information about customizing your configuration file. The <a href= - "http://proguard.sourceforge.net/manual/usage.html#keepoverview">Overview of Keep options</a> and - <a href="http://proguard.sourceforge.net/index.html#/manual/examples.html">Examples section</a> - are particularly helpful. The <a href= - "http://proguard.sourceforge.net/manual/troubleshooting.html">Troubleshooting</a> section of the - ProGuard Manual outlines other common problems you might encounter when your code gets stripped - away.</p> + highly recommended that you read the + <a href="http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/introduction.html">ProGuard + Manual</a> for more information about customizing your configuration file. The + <em>Overview of Keep options</em> and <em>Examples</em> sections are particularly helpful. + The <a href= + "http://stuff.mit.edu/afs/sipb/project/android/sdk/android-sdk-linux/tools/proguard/docs/index.html#manual/troubleshooting.html">Troubleshooting + </a> section of the ProGuard Manual outlines other common problems you might encounter + when your code gets stripped away.</p> <h2 id="decoding">Decoding Obfuscated Stack Traces</h2> @@ -192,4 +195,4 @@ proguard.config=/path/to/proguard.cfg <p>How you save the <code>mapping.txt</code> file is your decision. For example, you can rename them to include a version or build number, or you can version control them along with your source - code.</p>
\ No newline at end of file + code.</p> diff --git a/docs/html/tools/help/sdk-manager.jd b/docs/html/tools/help/sdk-manager.jd index 276206f..57271bb 100644 --- a/docs/html/tools/help/sdk-manager.jd +++ b/docs/html/tools/help/sdk-manager.jd @@ -9,6 +9,8 @@ page.title=SDK Manager <ul> <li>From Eclipse (with <a href="{@docRoot}tools/help/adt.html">ADT</a>), select <strong>Window</strong> > <strong>Android SDK Manager</strong>.</li> + <li>From Android Studio, select <strong>Tools</strong> > <strong>Android</strong> + > <strong>SDK Manager</strong>.</li> <li>On Windows, double-click the <code>SDK Manager.exe</code> file at the root of the Android SDK directory.</li> <li>On Mac or Linux, open a terminal and navigate to the <code>tools/</code> directory in the diff --git a/docs/html/tools/help/systrace.jd b/docs/html/tools/help/systrace.jd index 010cc78..d6fc05e 100644 --- a/docs/html/tools/help/systrace.jd +++ b/docs/html/tools/help/systrace.jd @@ -4,47 +4,276 @@ parent.link=index.html @jd:body -<p>The {@code systrace} tool helps analyze the performance of your application by capturing and +<p>The Systrace tool helps analyze the performance of your application by capturing and displaying execution times of your applications processes and other Android system processes. The - tool combines data from the Android kernel such as the CPU scheduler, disk activity and + tool combines data from the Android kernel such as the CPU scheduler, disk activity, and application threads to generate an HTML report that shows an overall picture of an Android device’s system processes for a given period of time.</p> -<p>The {@code systrace} tool is particularly useful in diagnosing display problems where an +<p>The Systrace tool is particularly useful in diagnosing display problems where an application is slow to draw or stutters while displaying motion or animation. For more information - on how to use {@code systrace}, see <a href="{@docRoot}tools/debugging/systrace.html">Analyzing - Display and Performance with Systrace</a>.</p> + on how to use Systrace, see <a href="{@docRoot}tools/debugging/systrace.html">Analyzing + Display and Performance</a>.</p> -<h2 id="usage">Usage</h2> -<p>In order to run {@code systrace}, the {@code adb} tool and -<a href="http://www.python.org/">Python</a> must be installed and included in your development -computer's execution path. In order to generate a trace, you must connect a device running Android -4.1 (API Level 16) or higher to your development system using a USB debugging connection.</p> +<h2 id="requirements">Requirements</h2> -<p>The syntax for running {@code systrace} is as follows.</p> +<p>In order to run Systrace, you must have Android SDK Tools 20 or later installed. You must also +have <a href="http://www.python.org/">Python</a> installed and included in your development +computer's execution path. In order to generate a trace, you must connect a device running Android +4.1 (API Level 16) or higher to your development system using a +<a href="{@docRoot}tools/device.html#setting-up">USB debugging connection</a>.</p> + +<p>The Systrace tool can be run either from one of the Android SDK's graphical user interface +tools, or from the command line. The following sections describe how to run the tool using either +of these methods.</p> + + +<h2 id="gui">User Interface</h2> + +<p>The Systrace tool can be run from the +<a href="{@docRoot}tools/help/adt.html">Android Developer Tools</a> (ADT) in Eclipse, +<a href="{@docRoot}sdk/installing/studio.html">Android Studio</a>, +or the Android <a href="{@docRoot}tools/help/monitor.html">Device Monitor</a>. + +<p>To run the Systrace user interface:</p> + +<div class="toggle-content closed"> +<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)"> + <img src="/assets/images/triangle-closed.png" class="toggle-content-img" alt="" + />Using Eclipse</a></p> + + <div class="toggle-content-toggleme"> + <ol> + <li>In Eclipse, open an Android application project.</li> + <li>Switch to the DDMS perspective, by selecting <strong>Window > Perspectives > + DDMS</strong>.</li> + <li>In the <strong>Devices</strong> tab, select the device on which to run a trace. If no + devices are listed, make sure your device is connected via USB cable and that debugging is + enabled on the device.</li> + <li>Click the Systrace icon <img src="{@docRoot}images/systrace/systrace-button.png" + style="margin:0"/> at the top of the <strong>Devices</strong> panel to configure tracing.</li> + <li>Set the tracing options and click <strong>OK</strong> to start the trace.</li> + </ol> + </div> +</div> + +<div class="toggle-content closed"> +<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)"> + <img src="/assets/images/triangle-closed.png" class="toggle-content-img" alt="" + />Using Android Studio</a></p> + + <div class="toggle-content-toggleme"> + <ol> + <li>In <a href="{@docRoot}sdk/installing/studio.html">Android Studio</a>, open an + Android application project.</li> + <li>Open the Device Monitor by selecting <strong>Tools > Android > Monitor</strong>.</li> + <li>In the <strong>Devices</strong> tab, select the device on which to run a trace. If no + devices are listed, make sure your device is connected via USB cable and that debugging is + enabled on the device.</li> + <li>Click the Systrace icon <img src="{@docRoot}images/systrace/systrace-button.png" + style="margin:0"/> at the top of the <strong>Devices</strong> panel to configure tracing.</li> + <li>Set the tracing options and click <strong>OK</strong> to start the trace.</li> + </ol> + </div> +</div> + +<div class="toggle-content closed"> +<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)"> + <img src="/assets/images/triangle-closed.png" class="toggle-content-img" alt="" + />Using Device Monitor</a></p> + + <div class="toggle-content-toggleme"> + <ol> + <li>Navigate to your SDK {@code tools/} directory.</li> + <li>Run the {@code monitor} program.</li> + <li>In the <strong>Devices</strong> tab, select the device on which to run a trace. If no + devices are listed, make sure your device is connected via USB cable and that debugging is + enabled on the device.</li> + <li>Click the Systrace icon <img src="{@docRoot}images/systrace/systrace-button.png" + style="margin:0"/> at the top of the <strong>Devices</strong> panel to configure tracing.</li> + <li>Set the tracing options and click <strong>OK</strong> to start the trace.</li> + </ol> + </div> +</div> + + + +<h2 id="options">Command Line Usage</h2> + +<p>The Systrace tool has different command line options for devices running Android 4.3 (API +level 18) and higher versus devices running Android 4.2 (API level 17) and lower. The following +sections describe the different command line options for each version.</p> + +<p>The general syntax for running Systrace from the command line is as follows.</p> <pre> -$> python systrace.py [options] +$ python systrace.py [options] [category1] [category2] ... [categoryN] </pre> -<p>Here is an example execution run that sets trace tags and generates a trace from a connected -Android device.</p> +<p>See the sections below for example Systrace sessions.</p> + + +<h3 id="options-4.3">Android 4.3 and higher options</h3> + +<p>When you use Systrace on devices running Android 4.3 and higher, you must specify at least one +trace category tag. Here is an example execution run that sets trace tags and generates a trace +from a connected device.</p> <pre> -$> cd <em>android-sdk</em>/tools/systrace -$> python systrace.py --set-tags gfx,view,wm -$> adb shell stop -$> adb shell start -$> python systrace.py --disk --time=10 -o mynewtrace.html +$ cd <em>android-sdk</em>/platform-tools/systrace +$ python systrace.py --time=10 -o mynewtrace.html sched gfx view wm </pre> +<p class="note"> + <strong>Tip:</strong> If you want to see the names of tasks in the trace output, you <em>must</em> + include the {@code sched} category in your command parameters. +</p> + +<p>The table below lists the Systrace command line options for devices running Android 4.3 +(API level 18) and higher.</p> + +<table> + <tr> + <th>Option</th> + + <th>Description</th> + </tr> + + <tr> + <td><nobr><code>-h, --help</code></nobr></td> + + <td>Show the help message.</td> + </tr> + + <tr> + <td><code>-o <<em>FILE</em>></code></td> + + <td>Write the HTML trace report to the specified file.</td> + </tr> + + <tr> + <td><code>-t N, --time=N</code></td> + + <td>Trace activity for <em>N</em> seconds. The default value is 5 seconds.</td> + </tr> + + <tr> + <td><code>-b N, --buf-size=N</code></td> + + <td>Use a trace buffer size of <em>N</em> kilobytes. This option lets you limit the total size + of the data collected during a trace.</td> + </tr> + + <tr> + <td><code>-k <<em>KFUNCS</em>><br> + --ktrace=<<em>KFUNCS</em>></code></td> + + <td>Trace the activity of specific kernel functions, specified in a comma-separated list.</td> + </tr> + + <tr> + <td><code>-l, --list-categories</code></td> + + <td>List the available tracing category tags. The available tags are: + + <ul> + <li><code>gfx</code> - Graphics</li> + <li><code>input</code> - Input</li> + <li><code>view</code> - View</li> + <li><code>webview</code> - WebView</li> + <li><code>wm</code> - Window Manager</li> + <li><code>am</code> - Activity Manager</li> + <li><code>audio</code> - Audio</li> + <li><code>video</code> - Video</li> + <li><code>camera</code> - Camera</li> + <li><code>hal</code> - Hardware Modules</li> + <li><code>res</code> - Resource Loading</li> + <li><code>dalvik</code> - Dalvik VM</li> + <li><code>rs</code> - RenderScript</li> + <li><code>sched</code> - CPU Scheduling</li> + <li><code>freq</code> - CPU Frequency</li> + <li><code>membus</code> - Memory Bus Utilization</li> + <li><code>idle</code> - CPU Idle</li> + <li><code>disk</code> - Disk input and output</li> + <li><code>load</code> - CPU Load</li> + <li><code>sync</code> - Synchronization Manager</li> + <li><code>workq</code> - Kernel Workqueues</li> + </ul> + + <p class="note"><strong>Note:</strong> Some trace categories are not supported on all + devices.</p> + + <p class="note"><strong>Tip:</strong> If you want to see the names of tasks in the trace + output, you <em>must</em> include the {@code sched} category in your command parameters.</p> + + </td> + </tr> + + <tr> + <td><code>-a <<em>APP_NAME</em>><br> + --app=<<em>APP_NAME</em>></code></td> + + <td>Enable tracing for applications, specified as a comma-separated list of + <a href="{@docRoot}guide/topics/manifest/manifest-element.html#package">package names</a>. + The apps must contain tracing instrumentation calls from the {@link android.os.Trace} class. + For more information, see <a href="{@docRoot}tools/debugging/systrace.html#app-trace">Analyzing + Display and Performance</a>. + </td> + </tr> + + + + <tr> + <td><code>--link-assets</code></td> + + <td>Link to the original CSS or JavaScript resources instead of embedding them in the HTML + trace report.</td> + </tr> + + <tr> + <td><code>--from-file=<<em>FROM_FILE</em>></code></td> + + <td>Create the interactive Systrace report from a file, instead of running a live trace.</td> + </tr> + + <tr> + <td><code>--asset-dir=<<em>ASSET_DIR</em>></code></td> + + <td>Specify a directory for the trace report assets. This option is useful for maintaining a + single set of assets for multiple Systrace reports.</td> + </tr> + + <tr> + <td style="white-space:nowrap"> + <code>-e <<em>DEVICE_SERIAL</em>><br> + --serial=<<em>DEVICE_SERIAL</em>></code></td> + <td>Conduct the trace on a specific connected device, identified by its + <a href="{@docRoot}tools/help/adb.html#devicestatus">device serial number</a>.</td> + </tr> -<h2 id="options">Options</h2> +</table> -<p>The table below lists the command line options for {@code systrace}.</p> + +<h3 id="options-pre-4.3">Android 4.2 and lower options</h3> + +<p>Using Systrace on the command line with devices running Android 4.2 and lower is typically a +two-step process. You must first set the trace tags you want to capture and then run the trace. +Here is an example execution run that sets trace tags and generates a trace from a connected +device.</p> + +<pre> +$ cd <em>android-sdk</em>/platform-tools/systrace +$ python systrace.py --set-tags gfx,view,wm +$ adb shell stop +$ adb shell start +$ python systrace.py --disk --time=10 -o mynewtrace.html +</pre> + +<p>The table below lists the Systrace command line options for devices running Android 4.2 +(API level 17) and lower.</p> <table> <tr> @@ -54,6 +283,12 @@ $> python systrace.py --disk --time=10 -o mynewtrace.html </tr> <tr> + <td><nobr><code>-h, --help</code></nobr></td> + + <td>Show the help message.</td> + </tr> + + <tr> <td><code>-o <<em>FILE</em>></code></td> <td>Write the HTML trace report to the specified file.</td> @@ -62,14 +297,14 @@ $> python systrace.py --disk --time=10 -o mynewtrace.html <tr> <td><code>-t N, --time=N</code></td> - <td>Trace activity for N seconds. Default value is 5 seconds.</td> + <td>Trace activity for <em>N</em> seconds. The default value is 5 seconds.</td> </tr> <tr> <td><code>-b N, --buf-size=N</code></td> - <td>Use a trace buffer size of N kilobytes. This option lets you limit the total size of the - data collected during a trace.</td> + <td>Use a trace buffer size of <em>N</em> kilobytes. This option lets you limit the total size + of the data collected during a trace.</td> </tr> <tr> @@ -106,6 +341,12 @@ $> python systrace.py --disk --time=10 -o mynewtrace.html </tr> <tr> + <td><nobr><code>-u, --bus-utilization</code></nobr></td> + + <td>Trace the bus utilization levels. This option requires root access on the device.</td> + </tr> + + <tr> <td><code>-w, --workqueue</code></td> <td>Trace kernel work queues. This option requires root access on the device.</td> @@ -122,13 +363,13 @@ $> python systrace.py --disk --time=10 -o mynewtrace.html <li><code>webview</code> - WebView</li> <li><code>wm</code> - Window Manager</li> <li><code>am</code> - Activity Manager</li> - <li><code>sync</code> - Sync Manager</li> + <li><code>sync</code> - Synchronization Manager</li> <li><code>audio</code> - Audio</li> <li><code>video</code> - Video</li> <li><code>camera</code> - Camera</li> </ul> <p class="note"><strong>Note:</strong> When setting trace tags from the command line, you - must stop and restart the framework ({@code $> adb shell stop; adb shell start}) for the + must stop and restart the framework ({@code $ adb shell stop; adb shell start}) for the tag tracing changes to take effect.</p> </td> </tr> @@ -140,22 +381,16 @@ $> python systrace.py --disk --time=10 -o mynewtrace.html report.</td> </tr> - <tr> - <td><nobr><code>-h, --help</code></nobr></td> - - <td>Show the help message.</td> - </tr> - </table> -<p>You can set the trace <a href="#tags">tags</a> for {@code systrace} with your device's user -interface, by navigating to <strong>Settings > Developer options > Monitoring > Enable -traces</strong>.</p> +<p>You can set the trace <a href="#tags">tags</a> for Systrace on +your Android 4.2 and lower device by navigating to <strong>Settings > Developer options > +Monitoring > Enable traces</strong>.</p> <h2 id="viewing-options">Trace Viewing Shortcuts</h2> -<p>The table below lists the keyboard shortcuts that are available while viewing a {@code systrace} +<p>The table below lists the keyboard shortcuts that are available while viewing a Systrace trace HTML report.</p> <table> diff --git a/docs/html/tools/help/uiautomator/UiSelector.jd b/docs/html/tools/help/uiautomator/UiSelector.jd index c9a1eed..6d5b4e4 100644 --- a/docs/html/tools/help/uiautomator/UiSelector.jd +++ b/docs/html/tools/help/uiautomator/UiSelector.jd @@ -472,7 +472,7 @@ hierarchy.</p> <span class="sympad"><a href="#resourceIdMatches(java.lang.String)">resourceIdMatches</a></span>(String regex)</nobr> <div class="jd-descrdiv">Set the search criteria to match the resource ID - of the widget, using a regular expression.http://blog.bettersoftwaretesting.com/</div> + of the widget, using a regular expression.</div> </td></tr> diff --git a/docs/html/tools/revisions/build-tools.jd b/docs/html/tools/revisions/build-tools.jd new file mode 100644 index 0000000..c3c83ef --- /dev/null +++ b/docs/html/tools/revisions/build-tools.jd @@ -0,0 +1,209 @@ +page.title=Build Tools +@jd:body + +<div id="qv-wrapper"> +<div id="qv"> + + <h2>See Also</h2> + <ol> + <li><a href="{@docRoot}tools/building/index.html">Building and Running</a></li> + </ol> + +</div> +</div> + +<p>Build Tools is a component of the Android SDK required for building Android + application code. The latest version of these tools is included in the + <a href="{@docRoot}sdk/index.html">SDK starter package</a> and installed in the + <code><sdk>/build-tools/</code> directory.</p> + +<p>You should always keep your Build Tools component updated by downloading the latest version + using the <a href="{@docRoot}tools/help/sdk-manager.html">Android SDK Manager</a>. By default, + the Android SDK uses the most recent downloaded version of the Build Tools. If your projects + depend on older versions of the Build Tools, the SDK Manager allows you to download and maintain + separate versions of the tools for use with those projects.</p> + +<p>To use a specific version of the Build Tools in your application project:</p> + +<div class="toggle-content closed"> +<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)"> + <img src="/assets/images/triangle-closed.png" class="toggle-content-img" alt="" + />Using Eclipse</a></p> + + <div class="toggle-content-toggleme"> + <ol> + <li>In the root folder of your application project, find the {@code project.properties} + file.</li> + <li>Open the file and specify the Build Tools version by adding a {@code buildtools} property + on a separate line: +<pre> +sdk.buildtools=17.0.0 +</pre> + </li> + </ol> + </div> +</div> + +<div class="toggle-content closed"> +<p style="margin-top:5px"><a href="#" onclick="return toggleContent(this)"> + <img src="/assets/images/triangle-closed.png" class="toggle-content-img" alt="" + />Using Android Studio</a></p> + + <div class="toggle-content-toggleme"> + <ol> + <li>In the root folder of your application project, find the {@code build.gradle} + file.</li> + <li>Open the file and specify the Build Tools version by adding a {@code buildToolsVersion} + property to the {@code android} section: +<pre> +android { + ... + buildToolsVersion "17.0.0" + ... +} +</pre> + </li> + </ol> + </div> +</div> + + +<h2 id="notes">Revisions</h2> + +<p>The sections below provide notes about releases of the Build Tools. To determine which +revisions of the Build Tools are available in your SDK, refer to the <em>Installed Packages</em> +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 19.0.3</a> <em>(March 2014)</em> + </p> + <div class="toggle-content-toggleme"> + + <p>Fixed an issue with RenderScript support.</p> + + </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.2</a> <em>(February 2014)</em> + </p> + <div class="toggle-content-toggleme"> + + <dl> + <dt>Fixed RenderScript build issues:</dt> + <dd> + <ul> + <li>Fixed a problem with RenderScript bitcode encoding. + (<a href="http://b.android.com/64775">Issue 64775</a>) + </li> + <li>Fixed a problem with RenderScript missing math symbols + (<a href="http://b.android.com/64110">Issue 64110</a>) + </li> + </ul> + </dd> + </dl> + <p></p> + + </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.1</a> <em>(December 2013)</em> + </p> + <div class="toggle-content-toggleme"> + + <dl> + <dt>Fixed miscellaneous build issues:</dt> + <dd> + <ul> + <li>Fixed support for compiling RenderScript in NDK mode with Gradle.</li> + <li>Fixed {@code BufferOverflowException} problem in the dx build. + (<a href="http://b.android.com/61710">Issue 61710</a>) + </li> + </ul> + </dd> + </dl> + <p></p> + + </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</a> <em>(October 2013)</em> + </p> + <div class="toggle-content-toggleme"> + + <p>Added support for Android 4.4 (API level 19) build targets.</p> + + </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 18.1.1</a> <em>(September 2013)</em> + </p> + <div class="toggle-content-toggleme"> + + <p>Fixed several minor build issues.</p> + + </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 18.1.0</a> <em>(September 2013)</em> + </p> + <div class="toggle-content-toggleme"> + + <p>Fixed issue with RenderScript support mode.</p> + + </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 18.0.1</a> <em>(July 2013)</em> + </p> + <div class="toggle-content-toggleme"> + + <p>Added support for Android 4.3 (API level 18) build targets.</p> + + </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 17</a> <em>(May 2013)</em> + </p> + <div class="toggle-content-toggleme"> + + <p>Initial release.</p> + + <dl> + <dt>General Notes:</dt> + <dd> + <ul> + <li>Included support for Android 4.2 (API level 17) build targets.</li> + <li>Decoupled the build-specific components of the Android SDK from the platform-tools + component, so that the build tools can be updated independently of the integrated + development environment (IDE) components.</li> + </ul> + </dd> + </dl> + + </div> +</div> diff --git a/docs/html/tools/revisions/platforms.jd b/docs/html/tools/revisions/platforms.jd index f219784..99a271f 100644 --- a/docs/html/tools/revisions/platforms.jd +++ b/docs/html/tools/revisions/platforms.jd @@ -7,14 +7,12 @@ page.title=Platforms <h2>See Also</h2> <ol> + <li><a href="{@docRoot}about/versions/kitkat.html">KitKat +Highlights and APIs</a></li> <li><a href="{@docRoot}about/versions/jelly-bean.html">Jelly Bean Highlights and APIs</a></li> <li><a href="{@docRoot}about/versions/android-4.0-highlights.html">Ice Cream Sandwich Highlights and APIs</a></li> - <li><a href="{@docRoot}about/versions/android-3.0-highlights.html">Honeycomb -Highlights and APIs</a></li> - <li><a href="{@docRoot}about/versions/android-2.3-highlights.html">Gingerbread -Highlights and APIs</a></li> </ol> </div> @@ -52,11 +50,27 @@ components will not be available for download.</p> <h2 id="4.4">Android 4.4</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 2</a> <em>(December 2013)</em> + </p> + + <div class="toggle-content-toggleme"> + + <p>Maintenance release. The system version is 4.4.2.</p> + <dl> + <dt>Dependencies:</dt> + <dd>Android SDK Platform-tools r19 or higher is required.</dd> + <dd>Android SDK Tools 22.3 or higher is recommended.</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="" />Revision 1</a> <em>(October 2013)</em> </p> @@ -72,19 +86,50 @@ class="toggle-content-img" alt="" />Revision 1</a> <em>(October 2013)</em> </div> </div> + + <h3 id="gsi-4.4">Google APIs System Image</h3> <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 3</a> <em>(February 2014)</em> + </p> + + <div class="toggle-content-toggleme"> + + <p>This release includes + <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 4.2.42, + allowing you to test your application in an emulator using the latest Google Play services.</p> + + </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="" />Revision 2</a> <em>(December 2013)</em> + </p> + + <div class="toggle-content-toggleme"> + + <p>This release includes + <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 4.0.33.</p> + + </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="" />Revision 1</a> <em>(October 2013)</em> </p> <div class="toggle-content-toggleme"> <p>Initial release. This release includes - <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 4.0.30, - allowing you to test your application in an emulator using the latest Google Play services.</p> + <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 4.0.30. + </p> </div> </div> @@ -143,8 +188,8 @@ class="toggle-content-img" alt="" />Revision 3</a> <em>(September 2013)</em> <div class="toggle-content-toggleme"> <p>Maintenance update. This release includes - <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 3.2.65, - allowing you to test your application in an emulator using the latest Google Play services.</p> + <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 3.2.65. + </p> </div> </div> @@ -158,8 +203,8 @@ class="toggle-content-img" alt="" />Revision 2</a> <em>(August 2013)</em> <div class="toggle-content-toggleme"> <p>Maintenance update. This release includes - <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 3.2.25, - allowing you to test your application in an emulator using the latest Google Play services.</p> + <a href="{@docRoot}google/play-services/index.html">Google Play services</a> version 3.2.25. + </p> </div> </div> diff --git a/docs/html/tools/samples/index.jd b/docs/html/tools/samples/index.jd deleted file mode 100644 index 76ba37a..0000000 --- a/docs/html/tools/samples/index.jd +++ /dev/null @@ -1,32 +0,0 @@ -page.title=Samples -page.tags="example","code" -@jd:body - -<p>To help you understand some fundamental Android APIs and coding practices, a variety of sample -code is available from the Android SDK Manager. Each version of the Android platform available -from the SDK Manager offers its own set of sample apps.</p> - -<p>To download the samples:</p> -<ol> - <li>Launch the Android SDK Manager. - <ul> - <li>On Windows, double-click the SDK Manager.exe file at the root of the Android SDK -directory.</li> - <li>On Mac or Linux, open a terminal to the {@code tools/} directory in the -Android SDK, then execute {@code android sdk}.</ul> - </li> - <li>Expand the list of packages for the latest Android platform.</li> - <li>Select and download <em>Samples for SDK</em>.</li> -</ol> - -<p>When the download is complete, you can find the source code for all samples at this location:</p> - -<p style="margin-left:2em"> -<code><sdk>/samples/android-<version>/</code> -</p> - -<p>The {@code <version>} number corresponds to the platform's - <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">API level</a>.</p> - -<p>You can easily create new Android projects with the downloaded samples, modify them -if you'd like, and then run them on an emulator or device.</p>
\ No newline at end of file diff --git a/docs/html/tools/sdk/eclipse-adt.jd b/docs/html/tools/sdk/eclipse-adt.jd index c584ae5..d711e44 100644 --- a/docs/html/tools/sdk/eclipse-adt.jd +++ b/docs/html/tools/sdk/eclipse-adt.jd @@ -53,10 +53,73 @@ 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 22.6.0</a> <em>(March 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</a>. + If you haven't already installed SDK Tools r22.6 into your SDK, use the + Android SDK Manager to do so.</li> + </ul> + </dd> + + <dt>General Notes:</dt> + <dd> + <ul> + <li><p>Added support for Java 7 language features like multi-catch, try-with-resources, + and the diamond operator. These features require version 19 or higher + of the Build Tools. Try-with-resources requires <code>minSdkVersion</code> + 19; the rest of the new language features require + <code>minSdkVersion</code> 8 or higher.</p> + <p>To use the new language features after installing ADT 22.6.0, ensure + that you run Eclipse on JDK 7 and change your application project settings + to use JDK 7.</p> + </li> + <li>Added new lint checks: + <ul> + <li>Security: + <ul> + <li>Look for code potentially affected by a <code>SecureRandom</code> + vulnerability.</li> + <li>Check that calls to <code>checkPermission</code> use the return + value.</li> + </ul> + </li> + <li>Check that production builds do not use mock location providers.</li> + </ul> + </li> + <li>Updated the New Project templates to include the + <a href="{@docRoot}tools/support-library/features.html#v7-appcompat"> + v7 appcompat Support Library</a>.</li> + <li>Updated the Android tools libraries to include the rendering sandbox, + improvements for converting resource XML string declarations to layout + strings, and other updates.</li> + <li>Improved the Gradle export wizard. Note that the new importer in Android + Studio is the preferred way to migrate existing projects to Gradle.</li> + <li>Fixed a deadlock during startup.</li> + <li>Fixed an issue with RenderScript support. Using RenderScript support mode + now requires version 19.0.3 of the Build Tools.</li> + </ul> + </dd> + +</dl> +</div> +</div> + +<div class="toggle-content closed"> + <p><a href="#" onclick="return toggleContent(this)"> + <img src="{@docRoot}assets/images/triangle-opened.png" class="toggle-content-img" alt=""/>ADT 22.3.0</a> <em>(October 2013)</em> </p> diff --git a/docs/html/tools/sdk/ndk/index.jd b/docs/html/tools/sdk/ndk/index.jd index 87f8a87..a22dc90 100644 --- a/docs/html/tools/sdk/ndk/index.jd +++ b/docs/html/tools/sdk/ndk/index.jd @@ -1,58 +1,34 @@ ndk=true page.template=sdk -ndk.mac64.legacy_download=android-ndk-r9b-darwin-x86_64-legacy-toolchains.tar.bz2 -ndk.mac64.legacy_bytes=122378495 -ndk.mac64.legacy_checksum=19c696a5b690b040409c68b21e9fcf46 -ndk.mac64_download=android-ndk-r9b-darwin-x86_64.tar.bz2 -ndk.mac64_bytes=354748937 -ndk.mac64_checksum=710d80b6ff807f03e585f9aacee3bf09 +ndk.mac64_download=android-ndk-r9d-darwin-x86_64.tar.bz2 +ndk.mac64_bytes=400339614 +ndk.mac64_checksum=c914164b1231c574dbe40debef7048be +ndk.mac32_download=android-ndk-r9d-darwin-x86.tar.bz2 +ndk.mac32_bytes=393866116 +ndk.mac32_checksum=ee6544bd8093c79ea08c2e3a6ffe3573 -ndk.mac32.legacy_download=android-ndk-r9b-darwin-x86-legacy-toolchains.tar.bz2 -ndk.mac32.legacy_bytes=119394536 -ndk.mac32.legacy_checksum=be0a07bcea3695f7d93cbd1b880d3f75 +ndk.linux64_download=android-ndk-r9d-linux-x86_64.tar.bz2 +ndk.linux64_bytes=412879983 +ndk.linux64_checksum=c7c775ab3342965408d20fd18e71aa45 -ndk.mac32_download=android-ndk-r9b-darwin-x86.tar.bz2 -ndk.mac32_bytes=349307548 -ndk.mac32_checksum=b5fa7aa3b9fca5a5b0c46bdd970d284b +ndk.linux32_download=android-ndk-r9d-linux-x86.tar.bz2 +ndk.linux32_bytes=405218267 +ndk.linux32_checksum=6c1d7d99f55f0c17ecbcf81ba0eb201f +ndk.win64_download=android-ndk-r9d-windows-x86_64.zip +ndk.win64_bytes=520997454 +ndk.win64_checksum=8cd244fc799d0e6e59d65a59a8692588 -ndk.linux64.legacy_download=android-ndk-r9b-linux-x86_64-legacy-toolchains.tar.bz2 -ndk.linux64.legacy_bytes=127742633 -ndk.linux64.legacy_checksum=f41017d5888a8dc210d1703dcdf1def7 +ndk.win32_download=android-ndk-r9d-windows-x86.zip +ndk.win32_bytes=491440074 +ndk.win32_checksum=b16516b611841a075685a10c59d6d7a2 -ndk.linux64_download=android-ndk-r9b-linux-x86_64.tar.bz2 -ndk.linux64_bytes=366988131 -ndk.linux64_checksum=56c0999a2683d6711591843217f943e0 - - -ndk.linux32.legacy_download=android-ndk-r9b-linux-x86-legacy-toolchains.tar.bz2 -ndk.linux32.legacy_bytes=125676842 -ndk.linux32.legacy_checksum=bfc7a1e6baf856b4348d57abffc761d2 - -ndk.linux32_download=android-ndk-r9b-linux-x86.tar.bz2 -ndk.linux32_bytes=361394055 -ndk.linux32_checksum=d7f783deaeea6b60cb515d9427c01c2e - - -ndk.win64.legacy_download=android-ndk-r9b-windows-x86_64-legacy-toolchains.zip -ndk.win64.legacy_bytes=166961852 -ndk.win64.legacy_checksum=6eee9459986e8b7f1032d62831dd775b - -ndk.win64_download=android-ndk-r9b-windows-x86_64.zip -ndk.win64_bytes=479012553 -ndk.win64_checksum=1ba6be7ebf4e9272d77031dd70f81e94 - - -ndk.win32.legacy_download=android-ndk-r9b-windows-x86-legacy-toolchains.zip -ndk.win32.legacy_bytes=152568224 -ndk.win32.legacy_checksum=00c8373b53ad9475f1bab1de4219b877 - -ndk.win32_download=android-ndk-r9b-windows-x86.zip -ndk.win32_bytes=455928388 -ndk.win32_checksum=cfb9402ea08a1554186e85ed28cb4593 +ndk.debug_info_download=android-ndk-r9d-cxx-stl-libs-with-debug-info.zip +ndk.debug_info_bytes=104947363 +ndk.debug_info_checksum=906c8d88e0f02295c3bfe6b8e98a1a35 page.title=Android NDK @@ -288,16 +264,323 @@ $('#Downloads').after($('#download-table')); contains legacy NDK toolchains for that platform, which is only required if you are not using the current, recommended toolchain for your NDK builds.</p> - - <h2 id="Revisions">Revisions</h2> <p>The following sections provide information about releases of the NDK.</p> <div class="toggle-content opened"> + <p> + <a href="#" onclick="return toggleContent(this)"> <img + src="/assets/images/triangle-opened.png" class="toggle-content-img" alt="" + >Android NDK, Revision 9d</a> <em>(March 2014)</em> + </p> + <div class="toggle-content-toggleme"> + <dl> + <dt>Important changes:</dt> + <dd> + <ul> + <li>Added support for the Clang 3.4 compiler. The +<code>NDK_TOOLCHAIN_VERSION=clang</code> option now picks Clang 3.4. GCC 4.6 is +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, +and libs). When using these options, note the following changes:</li> + <ul> + <li> When executing the <code>ndk-build</code> script, add the +following options for armeabi-v7a target: +<pre>TARGET_CFLAGS += -mhard-float -D_NDK_MATH_NO_SOFTFP=1 +TARGET_LDFLAGS += -Wl,--no-warn-mismatch -lm_hard</pre> +The built library is copied to <code>libs/armeabi-v7a</code>. For make to +behave as expected, you cannot specify both <code>armeabi-v7a</code> and +<code>armeabi-v7a-hard</code> as make targets (i.e., on the APP_ABI= line). +Doing so causes one of them to be ignored. Note that <code>APP_ABI=all</code> +is still equivalent to +<code>armeabi armeabi-v7a x86 mips</code>.</li> + <li>The <code>make-standalone-toolchain.sh</code> script copies +additional libaries under <code>/hard</code> directories. + Add the above <code>CFLAGS</code> and <code>LFLAGS</code> to your +makefile to enable GCC or Clang to link with + libraries in <code>/hard</code>.</li> + </ul> + <li>Added the yasm assembler, as well as <code>LOCAL_ASMFLAGS</code> +and <code>EXPORT_ASMFLAGS</code> flags for x86 +targets. The <code>ndk-build</code> script uses +<code>prebuilts/*/bin/yasm*</code> to build <code>LOCAL_SRC_FILES</code> that +have the <code>.asm</code> extension.</li> + <li>Updated MClinker to 2.6.0, which adds <code>-gc-sections</code> +support.</li> + <li>Added experimental libc++ support (upstream r201101). Use this new +feature by following these steps: + <ul> + <li>Add <code>APP_STL := c++_static</code> or <code>APP_STL := +c++_shared</code> in <code>Application.mk</code>. + You may rebuild from source via <code>LIBCXX_FORCE_REBUILD := +true</code></li> + <li>Execute <code>make-standalone-toolchain.sh --stl=libc++</code> +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> + </ul> + </dd> + <dl> + <dt>Important bug fixes:</dt> + <dd> + <ul> + <li>Fixed an uncaught throw from an unexpected +exception handler for GCC 4.6/4.8 ARM EABI. (GCC Issue <a +href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59392">59392</a>)</li> + <li>Fixed GCC 4.8 so that it now correctly resolves partial +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>): + <ul> + <li>Mac OS X: <code>zlib</code>, <code>bz2</code>, +<code>_curses</code>, <code>_curses_panel</code>, <code>_hashlib</code>, +<code>_ssl</code></li> + <li>Linux: <code>zlib</code>, <code>nis</code>, +<code>crypt</code>, <code>_curses</code>, and <code>_curses_panel</code></li> + </ul> + <li>Fixed the x86 and MIPS gdbserver +<code>event_getmsg_helper</code>.</li> + <li>Fixed numerous issues in the RenderScript NDK toolchain, including +issues with compatibility across older devices and C++ reflection.</li> +<br> + </ul> + </dd> + + <dt>Other bug fixes:</dt> + <dd> + <ul> + <li>Header fixes: + <ul> + <li>Fixed a missing <code>#include <sys/types.h></code> in +<code>android/asset_manager.h</code> for Android API level 13 and higher. + (Issue <a href="http://b.android.com/64988">64988</a>)</li> + <li>Fixed a missing <code>#include <stdint.h></code> in +<code>android/rect_manager.h</code> for Android API level 14 and higher.</li> + <li>Added <code>JNICALL</code> to <code>JNI_OnLoad</code> and +<code>JNI_OnUnload</code> in <code>jni.h</code>. Note that <code>JNICALL</code> + is defined as <code>__NDK_FPABI__</code> For more information, see +<code>sys/cdefs.h</code>.</li> + <li>Updated the following headers so that they can be included +without the need to +manually include their dependencies (Issue <a +href="http://b.android.com/64679">64679</a>):</li> +<pre> +android/tts.h +EGL/eglext.h +fts.h +GLES/glext.h +GLES2/gl2ext.h +OMXAL/OpenMAXSL_Android.h +SLES/OpenSLES_Android.h +sys/prctl.h +sys/utime.h +</pre> + <li>Added <code>sys/cachectl.h</code> for all architectures. MIPS +developers can now include this header instead of writing <code>#ifdef +__mips__</code>.</li> + <li></code>Fixed <code>platforms/android-18/include/android/input.h +</code> by adding <code>__NDK_FPABI__</code> to functions taking or returning +float or double values.</li> + <li>Fixed MIPS <code>struct stat</code>, which was incorrectly set +to its 64-bit counterpart for Android API level 12 and later. This wrong +setting was a +regression introduced in release r9c.</li> + <li>Defined <code>__PTHREAD_MUTEX_INIT_VALUE</code>, +<code>__PTHREAD_RECURSIVE_MUTEX_INIT_VALUE</code>, + and <code>__PTHREAD_ERRORCHECK_MUTEX_INIT_VALUE</code> for Android API +level 9 and lower.</li> + <li>Added <code>scalbln</code>, <code>scalblnf</code>, and +<code>scalblnl</code> to x86 <code>libm.so</code> for APIs 18 and later.</li> + <li>Fixed a typo in +<code>sources/android/support/include/iconv.h</code>. + (Issue <a href="http://b.android.com/63806">63806</a>)</li> + + </ul> + </li> + <li>Fixed gabi++ <code>std::unexpected()</code> to call +<code>std::terminate()</code> so that + a user-defined <code>std::terminate()</code> handler has a chance to run. +</li> + <li>Fixed gabi++ to catch <code>std::nullptr</code>.</li> + <li>Fixed samples Teapot and MoreTeapots: + <ul> + <li>Solved a problem with Tegra 2 and 3 chips by changing specular +variables to use medium precision. Values for specular power can now be less +than 1.0. </li> + <li>Changed the samples so that pressing the volume button restores +immersive mode and invalidates +<code>SYSTEM_UI_FLAG_IMMERSIVE_STICKY</code>. Screen rotation does not +trigger <code>onSystemUiVisibilityChange</code>, and so does not restore +immersive mode.</li> + </ul> + </li> + <li>Fixed the <code>ndk-build</code> script to add +<code>-rpath-link=$SYSROOT/usr/lib</code> and +<code>-rpath-link=$TARGET_OUT</code> in order to use <code>ld.bfd</code> to +link executables. (Issue <a href="http://b.android.com/64266">64266</a>)</li> + <li>Removed <code>-Bsymbolic</code> from all STL builds.</li> + <li>Fixed <code>ndk-gdb-py.cmd</code> by setting <code>SHELL</code> as +an environment variable +instead of passing it to + <code>python.exe</code>, which ignores the setting. + (Issue <a href="http://b.android.com/63054">63054</a>)</li> + <li>Fixed the <code>make-standalone-toolchain.sh</code> script so that +the <code>--stl=stlport</code> option copies the gabi++ headers instead of +symlinking them; the <code>cmd.exe</code> and MinGW shells do not understand +symlinks created by cygwin.</li> + </ul> + </dd> + + <dt>Other changes:</dt> + <dd> + <ul> + <li>Applied execution permissions to all <code>*cmd</code> scripts +previously intended for use only in the <code>cmd.exe</code> shell, in case +developers prefer to use <code>ndk-build.cmd</code> in cygwin instead of the +recommended <code>ndk-build</code> script.</li> + <li>Improved the speed of the <code>make-standalone-toolchain.sh</code> +script by moving instead of copying if the specified destination directory does +not exist.</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 9c</a> <em>(December 2013)</em> + </p> + <div class="toggle-content-toggleme"> +<p>This is a bug-fix-only release.</p> + <dl> + <dt>Important bug fixes:</dt> + <dd> + <ul> + <li>Fixed a problem with GCC 4.8 ARM, in which the stack pointer is +restored too early. This problem prevented the frame pointer from reliably +accessing a variable in the stack frame. (GCC Issue <a +href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854">58854</a>)</li> +<li>Fixed a problem with GCC 4.8 libstdc++, in which a bug in +std::nth_element was causing generation of code that produced a random +segfault. (Issue <a +href="https://code.google.com/p/android/issues/detail?id=62910">62910</a>)</li> + <li>Fixed GCC 4.8 ICE in cc1/cc1plus with +<code>-fuse-ld=mcld</code>, so that the following error no longer occurs: +<pre>cc1: internal compiler error: in common_handle_option, at +opts.c:1774</pre></li> + <li>Fixed <code>-mhard-float</code> support for +<code>__builtin</code> math functions. For ongoing information on fixes for +<code>-mhard-float</code> with STL, please follow Issue <a +href="http://b.android.com/61784">61784</a>.</li> + </ul> + </dd> + + <dt>Other bug fixes:</dt> + <dd> + <ul> + <li>Header fixes: + <ul> + <li>Changed prototype of <code>poll</code> to <code>poll(struct +pollfd *, nfds_t, int);</code> in <code>poll.h</code>.</li> + <li>Added <code>utimensat</code> to <code>libc.so</code> for Android +API levels 12 and 19. These libraries are now included for all Android API +levels 12 through 19.</li> +<li>Introduced <code>futimens</code> into <code>libc.so</code>, for Android API +level 19.</li> +<li>Added missing <code>clock_settime()</code> and +<code>clock_nanosleep()</code> to <code>time.h</code> for Android API level 8 +and higher.</li> +<li>Added <code>CLOCK_MONOTONIC_RAW, CLOCK_REALTIME_COARSE, +CLOCK_MONOTONIC_COARSE, CLOCK_BOOTTIME, CLOCK_REALTIME_ALARM,</code> and +<code>CLOCK_BOOTTIME_ALARM</code> in <code>time.h.</code></li> +<li>Removed obsolete <code>CLOCK_REALTIME_HR</code> and +<code>CLOCK_MONOTONIC_HR.</code></li> + </ul> + </li> + <li>In samples Teapot, MoreTeapots, and +<code>source/android/ndk_helper</code>: + <ul> +<li>Changed them so that they now use a hard-float abi for armeabi-v7a.</li> +<li>Updated them to use immersive mode on Android API level 19 and +higher.</li> +<li>Fixed a problem with <code>Check_ReleaseStringUTFChars</code> in +<code>/system/lib/libdvm.so</code> that was causing crashes on x86 devices.</li> + </ul> + </li> +<li>Fixed <code>ndk-build</code> fails that happen in cygwin when the NDK +package is +referenced via symlink.</li> +<li>Fixed <code>ndk-build.cmd</code> fails that happen in windows +<code>cmd.exe</code> when +<code>LOCAL_SRC_FILES</code> contains absolute paths. (Issue <a +href="https://android-review.googlesource.com/#/c/69992">69992</a>)</li> +<li>Fixed the <code>ndk-stack</code> script to proceed even when it can't parse +a frame due to inability to find a routine, filename, or line number. In any of +these cases, it prints <code>??</code>.</li> +<li>Fixed the <code>ndk-stack</code> stack for windows-x64_64 targets so that +it no longer erroneously matches a frame line with a line in the +<code>stack:</code> section that doesn't contain <code>pc</code>, +<code>eip</code>, or <code>ip</code>. For example: +<pre>I/DEBUG ( 1151): #00 5f09db68 401f01c4 +/system/lib/libc.so</pre></li> +<li>Fixed gabi++ so that it: + <ul> + <li>Does not use malloc() to allocate C++ thread-local + objects.</li> + <li>Avoids deadlocks in gabi++ in cases where libc.debug.malloc is +non-zero in userdebug/eng Android platform builds.</li> + </ul> + </ul> + </dd> + + <dt>Other changes:</dt> + <dd> + <ul> + <li>Added <code>LOCAL_EXPORT_LDFLAGS</code>.</li> +<li>Introduced the <code>NDK_PROJECT_PATH=null</code> setting for use in an +integrated build system where options are explicitly passed to +<code>ndk-build</code>. With this setting, <code>ndk-build</code> makes no +attempt to look for <code>NDK_PROJECT_PATH.</code> This setting also prevents +variables from deriving default settings from NDK_PROJECT_PATH. As a result, +the following variables must now be explicitly specified (with their default +values if such exist): <code>NDK_OUT, NDK_LIBS_OUT, APP_BUILD_SCRIPT, +NDK_DEBUG</code> (optional, default to 0), and other <code>APP_*</code>'s +contained in <code>Application.mk</code>.</li> +<li><code>APP_ABI</code> can now be enumerated in a comma-delimited list. For +example: +<pre>APP_ABI := "armeabi,armeabi-v7a"</pre></li> +<li>Provided the ability to rebuild all of STL with debugging info in an +optional, separate package called +<code>android-ndk-r9c-cxx-stl-libs-with-debugging-info.zip</code>, using the +<code>-g</code> option. This option +helps the <code>ndk-stack</code> script provide better a stack dump across STL. +This change should not affect the code/size of the final, stripped file.</li> +<li>Enhanced <code>hello-jni</code> samples to report <code>APP_ABI</code> at +compilation.</li> +<li>Used the <code>ar</code> tool in Deterministic mode (option +<code>-D</code>) to build static libraries. (Issue <a +href="http://b.android.com/60705">60705</a>)</li> + </ul> + </dd> + + </dl> + </div> +</div> + +<div class="toggle-content closed"> <p> <a href="#" onclick="return toggleContent(this)"> <img - src="{@docRoot}assets/images/triangle-opened.png" class="toggle-content-img" alt="" + src="{@docRoot}assets/images/triangle-closed.png" class="toggle-content-img" alt="" >Android NDK, Revision 9b</a> <em>(October 2013)</em> </p> <div class="toggle-content-toggleme"> @@ -313,7 +596,7 @@ $('#Downloads').after($('#download-table')); (Issues <a href="http://b.android.com/47150">47150</a>, <a href="http://b.android.com/58528">58528</a>, and <a href="http://b.android.com/38423">38423</a>)</li> - <li>Added support for API level 19, including Renderscript binding.</li> + <li>Added support for Android API level 19, including Renderscript binding.</li> <li>Added support for <code>-mhard-float</code> in the existing armeabi-v7a ABI. For more information and current restrictions on Clang, see {@code tests/device/hard-float/jni/Android.mk}.</li> @@ -2345,8 +2628,8 @@ float AMotionEvent_getHistoricalRawY(const AInputEvent* motion_event, dealing with signed chars.</li> <li>Adds missing documentation for the "gnustl_static" value for APP_STL, that allows you to link against - a static library version of GNU libstdc++. </li> - <li>The following <code>ndk-build</code> issues are fixed: + a static library version of GNU libstdc++. </li> the + <li>Fixed the following <code>ndk-build</code> issues: <ul> <li>A bug that created inconsistent dependency files when a compilation error occured on Windows. This prevented a proper build after diff --git a/docs/html/tools/sdk/preview/features.jd b/docs/html/tools/sdk/preview/features.jd index 02897cd..2bdb0f4 100644 --- a/docs/html/tools/sdk/preview/features.jd +++ b/docs/html/tools/sdk/preview/features.jd @@ -1,3 +1,4 @@ +excludeFromSuggestions=true @jd:body <script type="text/javascript"> diff --git a/docs/html/tools/sdk/preview/index.jd b/docs/html/tools/sdk/preview/index.jd index d96df93..713730e 100644 --- a/docs/html/tools/sdk/preview/index.jd +++ b/docs/html/tools/sdk/preview/index.jd @@ -1,3 +1,4 @@ sdk.redirect=true page.template=sdk +excludeFromSuggestions=true @jd:body diff --git a/docs/html/tools/sdk/preview/installing.jd b/docs/html/tools/sdk/preview/installing.jd index c40e531..d248b67 100644 --- a/docs/html/tools/sdk/preview/installing.jd +++ b/docs/html/tools/sdk/preview/installing.jd @@ -1,3 +1,4 @@ +excludeFromSuggestions=true @jd:body <script type="text/javascript"> diff --git a/docs/html/tools/sdk/preview/requirements.jd b/docs/html/tools/sdk/preview/requirements.jd index b5aed80..b62ee05 100644 --- a/docs/html/tools/sdk/preview/requirements.jd +++ b/docs/html/tools/sdk/preview/requirements.jd @@ -1,3 +1,4 @@ +excludeFromSuggestions=true @jd:body <script type="text/javascript"> diff --git a/docs/html/tools/sdk/preview/upgrading.jd b/docs/html/tools/sdk/preview/upgrading.jd index 1c53bdb..3b90696 100644 --- a/docs/html/tools/sdk/preview/upgrading.jd +++ b/docs/html/tools/sdk/preview/upgrading.jd @@ -1,3 +1,4 @@ +excludeFromSuggestions=true @jd:body <script type="text/javascript"> diff --git a/docs/html/tools/sdk/tools-notes.jd b/docs/html/tools/sdk/tools-notes.jd index c28b946..99f0b38 100644 --- a/docs/html/tools/sdk/tools-notes.jd +++ b/docs/html/tools/sdk/tools-notes.jd @@ -26,10 +26,92 @@ Tools you are using, refer to the "Installed Packages" listing in the Android SD 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=""/>SDK Tools, Revision 22.6</a> <em>(March 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.0 and later. If you haven't already, update your + <a href="{@docRoot}tools/sdk/eclipse-adt.html">ADT Plugin</a> to 22.6.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><p>The command line <code>lint</code> script (<code>tools\lint.bat</code> on + Windows platforms, <code>tools/lint</code> on other platforms) and the + <code>lint</code> target on <code>ant</code> builds fail with the following + error:</p> + <p><code>Exception in thread "main" java.lang.NoClassDefFoundError: + lombok/ast/AstVisitor</code></p> + <p>As a temporary workaround, rename the file + <code>tools\lib\lombok-ast-0.2.2.jar</code> to + <code>tools\lib\lombok-ast.jar</code>. + We will release an updated version of the tools with a fix for + this issue as soon as possible.</p> + </li> + <li>Added support for Java 7 language features like multi-catch, try-with-resources, + and the diamond operator. These features require version 19 or higher + of the Build Tools. Try-with-resources requires <code>minSdkVersion</code> + 19; the rest of the new language features require + <code>minSdkVersion</code> 8 or higher.</li> + <li>Added new lint checks: + <ul> + <li>Security: + <ul> + <li>Look for code potentially affected by a <code>SecureRandom</code> + vulnerability.</li> + <li>Check that calls to <code>checkPermission</code> use the return value.</li> + </ul> + </li> + <li>Check that production builds do not use mock location providers.</li> + <li>Look for manifest values that are overwritten by values from Gradle build + scripts.</li> + </ul> + </li> + <li>Fixed a number of minor issues in the SDK and build system.</li> + <li>Emulator: + <ul> + <li>Fixed a problem with the emulator shutting down immediately for Android 1.5 + on the Nexus One and Nexus S devices. + (<a href="http://b.android.com/64945">Issue 64945</a>)</li> + <li>Fixed a problem with port numbers longer than four digits. + (<a href="http://b.android.com/60024">Issue 60024</a>)</li> + <li>Fixed battery errors for the Nexus One and Nexus S devices. + (<a href="http://b.android.com/39959">Issue 39959</a>)</li> + <li>Fixed a problem with paths or arguments that contain + spaces on Windows platforms. + (<a href="http://b.android.com/18317">Issue 18317</a>)</li> + <li>Fixed a problem with long path values on Windows platforms. + (<a href="http://b.android.com/33336">Issue 33336</a>)</li> + <li>Fixed a problem with the {@code -snapshot-list} command line + option on 64-bit systems. + (<a href="http://b.android.com/34233">Issue 34233</a>)</li> + </ul> + </li> + <li>Fixed an issue with RenderScript support. Using RenderScript support mode + now requires version 19.0.3 of the Build Tools.</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=""/>SDK Tools, Revision 22.3</a> <em>(October 2013)</em> </p> diff --git a/docs/html/tools/support-library/index.jd b/docs/html/tools/support-library/index.jd index dba4e74..389238f 100644 --- a/docs/html/tools/support-library/index.jd +++ b/docs/html/tools/support-library/index.jd @@ -62,6 +62,49 @@ page.title=Support Library <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 19.0.1</a> <em>(December 2013)</em> + </p> + <div class="toggle-content-toggleme"> + <dl> + <dt>Changes for v4 support library:</dt> + <dd> + <ul> + <li>Improved {@link android.support.v4.print.PrintHelper} by adding asynchronous + handling of printing.</li> + <li>Fixed the {@link android.support.v4.widget.DrawerLayout} class approximation of + the {@link android.view.View#addChildrenForAccessibility addChildrenForAccessibility()} + method.</li> + <li>Fixed slide drawable mirroring in {@link + android.support.v4.app.ActionBarDrawerToggle}.</li> + <li>Fixed off-by-one issue when removing an item from a collection iterator.</li> + </ul> + </dd> + + <dt>Changes for v7 mediarouter library:</dt> + <dd> + <ul> + <li>Improved route identification by using full component name in the {@link + android.support.v7.media.MediaRouteProvider.ProviderMetadata}.</li> + <li>Updated {@link android.support.v7.app.MediaRouteChooserDialog} to hide disabled + routes.</li> + </ul> + </dd> + + <dt>Changes for v8 renderscript library:</dt> + <dd> + <ul> + <li>Added error propagation for the RenderScript thunking layer.</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</a> <em>(October 2013)</em> </p> <div class="toggle-content-toggleme"> diff --git a/docs/html/tools/support-library/setup.jd b/docs/html/tools/support-library/setup.jd index 2d2065a..2325a13 100644 --- a/docs/html/tools/support-library/setup.jd +++ b/docs/html/tools/support-library/setup.jd @@ -206,6 +206,14 @@ project</a> based on the support library code:</p> <li>In the properties window, click <strong>OK</strong>.</li> </ol> +<p class="note"> + <strong>Note:</strong> If you are using the {@code android-support-v7-mediarouter} support + library, you should note that it depends on the {@code android-support-v7-appcompat} library. + In order for the v7 mediarouter library to compile, you must import both library projects into + your development workspace. Then follow the procedure above to add the v7 appcompat project as a + library to the v7 mediarouter library project. +</p> + </div> </div> diff --git a/docs/html/tools/testing/activity_test.jd b/docs/html/tools/testing/activity_test.jd index 2d1a5bf..036407a 100644 --- a/docs/html/tools/testing/activity_test.jd +++ b/docs/html/tools/testing/activity_test.jd @@ -443,12 +443,11 @@ import com.android.example.spinner.SpinnerActivity; </p> <pre> public SpinnerActivityTest() { - super("com.android.example.spinner", SpinnerActivity.class); + super(SpinnerActivity.class); } // end of SpinnerActivityTest constructor definition </pre> <p> - This calls the superclass constructor with the Android package name (<code>com.android.example.spinner</code>)and main activity's class - (<code>SpinnerActivity.class</code>) for the application under test. Android uses this information to find the application and activity to test. + This calls the superclass constructor with the main activity's class (<code>SpinnerActivity.class</code>) for the application under test. Android uses this information to find the application and activity to test. </p> <p> You are now ready to add tests, by adding test methods to the class. diff --git a/docs/html/tools/tools_toc.cs b/docs/html/tools/tools_toc.cs index 39eecf8..a8424e6 100644 --- a/docs/html/tools/tools_toc.cs +++ b/docs/html/tools/tools_toc.cs @@ -138,7 +138,7 @@ <li><a href="<?cs var:toroot ?>tools/debugging/improving-w-lint.html"><span class="en">Improving Your Code with lint</span></a></li> <li><a href="<?cs var:toroot ?>tools/debugging/debugging-ui.html"><span class="en">Optimizing your UI</span></a></li> <li><a href="<?cs var:toroot ?>tools/debugging/debugging-tracing.html"><span class="en">Profiling with Traceview and dmtracedump</span></a></li> - <li><a href="<?cs var:toroot ?>tools/debugging/systrace.html"><span class="en">Analysing Display and Performance with Systrace</span></a></li> + <li><a href="<?cs var:toroot ?>tools/debugging/systrace.html"><span class="en">Analyzing Display and Performance</span></a></li> <li><a href="<?cs var:toroot ?>tools/debugging/debugging-memory.html">Investigating Your RAM Usage</a></li> <li><a href="<?cs var:toroot ?>tools/debugging/debugging-devtools.html"><span class="en">Using the Dev Tools App</span></a></li> </ul> @@ -225,14 +225,14 @@ class="en">MonkeyRunner</span></a></li> ?>tools/revisions/index.html"><span class="en">Revisions</span></a></div> <ul> <li><a href="<?cs var:toroot ?>tools/sdk/tools-notes.html"> - <span class="en">Tools</span> + <span class="en">SDK Tools</span> </a></li> <li><a href="<?cs var:toroot ?>tools/sdk/eclipse-adt.html"> <span class="en">ADT Plugin</span> </a></li> - <!-- - <li><a href="<?cs var:toroot ?>tools/sdk/addons.html"><span class="en">Add-ons</span></a></li> - --> + <li><a href="<?cs var:toroot ?>tools/revisions/build-tools.html"> + <span class="en">Build Tools</span> + </a></li> <li><a href="<?cs var:toroot ?>tools/revisions/platforms.html"><span class="en">Platforms</span></a></li> </ul> @@ -240,12 +240,6 @@ class="en">Platforms</span></a></li> <li class="nav-section"> - <div class="nav-section-header empty"><a href="<?cs var:toroot -?>tools/samples/index.html"><span class="en">Samples</span></a></div> - </li> - - - <li class="nav-section"> <div class="nav-section-header"> <a href="<?cs var:toroot ?>tools/adk/index.html"> <span class="en">ADK</span></a> |