diff options
Diffstat (limited to 'docs/html/guide/developing')
| -rw-r--r-- | docs/html/guide/developing/debug-tasks.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/developing/device.jd | 42 | ||||
| -rw-r--r-- | docs/html/guide/developing/eclipse-adt.jd | 60 | ||||
| -rw-r--r-- | docs/html/guide/developing/instrumentation/index.jd | 54 | ||||
| -rw-r--r-- | docs/html/guide/developing/instrumentation/inst-framework.jd | 139 | ||||
| -rw-r--r-- | docs/html/guide/developing/instrumentation/inst-testing.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/developing/other-ide.jd | 49 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/adb.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/adt.jd | 2 | ||||
| -rw-r--r-- | docs/html/guide/developing/tools/adt_download.jd | 65 |
10 files changed, 128 insertions, 289 deletions
diff --git a/docs/html/guide/developing/debug-tasks.jd b/docs/html/guide/developing/debug-tasks.jd index a604df2..6b7c27a 100644 --- a/docs/html/guide/developing/debug-tasks.jd +++ b/docs/html/guide/developing/debug-tasks.jd @@ -53,7 +53,7 @@ D/ActivityManager( 763): Stopping: HistoryRecord{409dbb20 com.android.home.AllAp graphical reader called Traceview. See the linked topic for more information. </li> </ul> <ul> - <li><a href="#developingwitheclipse"><strong>Eclipse plugin</strong></a> - The ADT Plugin + <li><a href="{@docRoot}guide/developing/eclipse-adt.html"><strong>Eclipse plugin</strong></a> - The ADT Plugin for Eclipse integrates a number of these tools (ADB, DDMS, logcat output, and other functionality). See the linked topic for more information. </li> <li><strong>Debug and Test Device Settings</strong> - Android exposes several settings diff --git a/docs/html/guide/developing/device.jd b/docs/html/guide/developing/device.jd index b723797..034f707 100644 --- a/docs/html/guide/developing/device.jd +++ b/docs/html/guide/developing/device.jd @@ -7,8 +7,8 @@ page.title=Developing on a Device <ol> <li><a href="#devices">Available Devices</a> <ol> - <li><a href="g1">T-Mobile G1</a></li> - <li><a href="dev-phone-1">Android Dev Phone 1</a></li> + <li><a href="#g1">T-Mobile G1</a></li> + <li><a href="#dev-phone-1">Android Dev Phone 1</a></li> </ol> </li> <li><a href="#setting-up">Setting up a Device for Development</a></li> @@ -41,8 +41,9 @@ href="http://www.t-mobileg1.com">T-Mobile G1 site</a>. </p> <h3 id="dev-phone-1">Android Dev Phone 1</h3> +<div class="sidebox-wrapper"> <div class="sidebox"> -<p>Selected specs for Android Dev Phone 1: </p> +<p>Selected specs for Android Dev Phone 1:</p> <ul> <li>Touch screen</li> <li>Trackball</li> @@ -58,7 +59,7 @@ href="http://www.t-mobileg1.com">T-Mobile G1 site</a>. </p> <li>Includes 1GB MicroSD card (can be replaced with up to 16GB card)</li> </ul> </div> - +</div> <p>The Android Dev Phone 1 is a SIM-unlocked and hardware-unlocked device that is designed for advanced developers. The device ships with a system image that is fully compatible with Android 1.0, so you can rely on it when developing your @@ -71,19 +72,19 @@ who live outside of T-Mobile geographies. </p> <p>To purchase an Android Dev Phone 1 device, you must first register as an Android developer on the Android Market site, if you haven't done so already. Once you've logged into your developer account on Android Market, you can -purchase the device by clicking the "Purchase" link. To accommodate demand, +purchase the device by following the link to "Development phones." To accommodate demand, there is a limit of 1 device per developer account, for now.</p> <p>The device currently costs $399 (USD) (including free shipping in the US), -and will be available for purchase in 18 international markets, including the +and is available for purchase in 18 international markets, including the US, UK, Germany, Japan, India, Canada, France, Taiwan, Spain, Australia, Singapore, Switzerland, Netherlands, Austria, Sweden, Finland, Poland, and Hungary. We will continue to expand this program into new geographies over time. Check this page for updated information.</p> <p>Note that Android Dev Phone 1 devices are <em>not</em> intended for -non-developer end users. Since the devices can be configured with system -software not provided by or supported by Google or any other company, end users +non-developer end-users. Because the device can be configured with system +software not provided by or supported by Google or any other company, end-users operate these devices at their own risk.</p> <p>For full device specs and more information about obtaining an Android Dev @@ -109,17 +110,28 @@ would on the emulator. There are just a few things to do before you can start.</ </li> <li>Setup your system to detect your device. <ul> - <li>If you're developing on Windows (32-bit only), you need to install the USB driver for adb: + <li>If you're developing on 32-bit Windows, you need to install the 32-bit USB driver for adb. + The USB driver is included in the SDK package. To install it, follow these steps:</p> <ol> - <li>Download the driver ZIP file - (<a href="http://dl.google.com/android/android_usb_windows.zip">android_usb_windows.zip</a>) - and unzip it.</li> - <li>Connect your Android device via USB. When the <em>Found New Hardware Wizard</em> appears, you'll be asked if you'd like Windows Update to search for software, select <em>No, not this time</em> and click <b>Next</b>.</li> + <li>Connect your Android device via USB. When the <em>Found New Hardware Wizard</em> appears, + you'll be asked if you'd like Windows Update to search for software. Select <em>No, not this + time</em> and click <b>Next</b>.</li> <li>Select <em>Install from a list or specified location</em> and click <b>Next</b>.</li> - <li>Select <em>Search for the best driver in these locations</em>. Browse and select the unzipped file.</li> - <li>Click <b>Finish</b>. You're all set.</li> + <li>Select <em>Search for the best driver in these locations</em>. Browse to the <code>usb_driver/x86</code> in the SDK package (<code><sdk>\usb_driver\x86</code>).</li> + <li>Click <b>Finish</b>. The system should install the driver files as necessary. Your machine may require a reboot.</li> + </ol> + </li> + <li>If you're developing on 64-bit Windows Vista, you need to install the 64-bit USB driver for adb. + The USB driver is included in the SDK package. To install it, follow these steps:</p> + <ol> + <li>Connect your Android device via USB. When the <em>Found New Hardware Wizard</em> appears, + you'll be asked if you'd like Windows Update to search for software. Select <em>No, not this + time</em> and click <b>Next</b>.</li> + <li>Select <em>Install from a list or specified location</em> and click <b>Next</b>.</li> + <li>Select <em>Search for the best driver in these locations</em>. Browse to the <code>usb_driver/amd64</code> in the SDK package (<code><sdk>\usb_driver\amd64</code>).</li> + <li>Click <b>Finish</b>. The system should install the driver files as necessary. Your machine may require a reboot.</li> </ol> </li> <li>If you're developing on Mac OS X, it just works. Skip this step.</li> diff --git a/docs/html/guide/developing/eclipse-adt.jd b/docs/html/guide/developing/eclipse-adt.jd index 7177395..8c482ee 100644 --- a/docs/html/guide/developing/eclipse-adt.jd +++ b/docs/html/guide/developing/eclipse-adt.jd @@ -1,17 +1,28 @@ page.title=In Eclipse, with ADT @jd:body -<p>To begin developing Android applications in the Eclipse IDE with ADT, you first create an Android +<p>The Android Development Tools (ADT) plugin for Eclipse adds powerful extensions to the Eclipse integrated development environment. It allows you to create and debug Android applications easier and faster. If you use Eclipse, the ADT plugin gives you an incredible boost in developing Android applications:</p> + +<ul> + <li>It gives you access to other Android development tools from inside the Eclipse IDE. For example, ADT lets you access the many capabilities of the DDMS tool: take screenshots, manage port-forwarding, set breakpoints, and view thread and process informationd irectly from Eclipse.</li> + <li>It provides a New Project Wizard, which helps you quickly create and set up all of the basic files you'll need for a new Android application.</li> + <li>It automates and simplifies the process of building your Android application.</li> + <li>It provides an Android code editor that helps you write valid XML for your Android manifest and resource files.</li> +</ul> + +<p>To begin developing Android applications in the Eclipse IDE with ADT, you first need to download the Eclipse IDE and then download and install the ADT plugin. To do so, follow the steps given in <a href="{@docRoot}sdk/1.1_r1/installing.html#installingplugin">Installing the ADT Plugin</a>, in the installation documentation included with your SDK package. </p> + +<p>Once you've installed the ADT plugin, you begin by creating an Android project and then set up a launch configuration. After that, you can write, run, and debug your application. </p> <p>The sections below provide instructions assuming that you have installed the ADT plugin in your Eclipse environment. If you haven't installed the ADT plugin, you should do that -before using the instructions below. For complete information, see the installation documentation included in your SDK package. </p> +before using the instructions below. </p> <a name="creatingaproject" id="creatingaproject"></a> -<h3>Creating an Android Project</h3> +<h2>Creating an Android Project</h2> <p>The ADT plugin provides a New Project Wizard that you can use to quickly create an Eclipse project for new or existing code. To create the project, follow these steps:</p> @@ -49,7 +60,7 @@ Eclipse project for new or existing code. To create the project, follow these st <a name="launchconfig" id="launchconfig"></a> -<h3>Creating a Launch Configuration </h3> +<h2>Creating a Launch Configuration </h2> <p>Before you can run and debug your application in Eclipse, you must create a launch configuration for it. A launch configuration specifies the project to launch, the Activity to start, the emulator options to use, and so on. </p> @@ -78,9 +89,45 @@ Eclipse project for new or existing code. To create the project, follow these st </ol> + +<h2 id="sign_in_adt">Setting Up Application Signing</h2> + +<p>As you begin developing Android applications, you should understand that all +Android applications must be digitally signed before the system will install +them on the emulator or an actual device. </p> + +<p>The ADT plugin helps you get started quickly by signing your .apk files with +a debug key, prior to installing them on the emulator. This means that you can +compile your application and install it on the emulator without having to +generate your own private key. However, please note that if you intend to +publish your application, you <em>must</em> sign the application with your own +private key, rather than the debug key generated by the SDK tools. </p> + +<p>To sign your applications, the ADT plugin requires the Keytool utility +included in the JDK. To set up your development environment for +signing, you need to make sure that Keytool is available on your +machine that the ADT plugin knows how to find it. </p> + +<p>In most cases, you can tell the SDK build tools how to find Keytool by making +sure that your JAVA_HOME environment variable is set and that it references a +suitable JDK. Alternatively, you can add the JDK version of Keytool to your +PATH variable.</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 PATH, it +might be pointing to a symlink at /usr/bin/keytool. In this case, check the +symlink target to make sure that it points to the keytool in the JDK.</p> + +<p>In all cases, please read and understand <a +href="{@docRoot}guide/publishing/app-signing.html">Signing Your +Applications</a>, which provides an overview of application signing on Android +and what it means to you as an Android application developer. </p> + + <a name="installingrunningdebugging" id="installingrunningdebugging"></a> -<h3>Running and Debugging an Application</h3> +<h2>Running and Debugging an Application</h2> <p>Once you've set up the project and launch configuration for your application, you can run or debug it as described below.</p> @@ -98,7 +145,8 @@ From the Eclipse main menu, select <strong>Run</strong> > <strong>Run</strong </ul> - <h2 id="tips">Eclipse Tips </h2> + +<h2 id="tips">Eclipse Tips </h2> <h3>Executing arbitrary Java expressions in Eclipse<a name="arbitraryexpressions" id="arbitraryexpressions"></a></h3> <p>You can execute arbitrary code when paused at a breakpoint in Eclipse. For example, when in a function with a String argument called "zip", you can get diff --git a/docs/html/guide/developing/instrumentation/index.jd b/docs/html/guide/developing/instrumentation/index.jd deleted file mode 100644 index 7ebd72e..0000000 --- a/docs/html/guide/developing/instrumentation/index.jd +++ /dev/null @@ -1,54 +0,0 @@ -page.title=Instrumentation -@jd:body - -<dl> - <dt><a href="inst-framework.html">Instrumentation Framework</a></dt> - <dt><a href="inst-testing.html">Instrumentation Testing</a></dt> -</dl> - -<!-- -<p>Android provides an instrumentation framework that lets you create a bundle of instrumentation tests and attach them to your application. When you run the instrumentation from the command line, the Android system d - - through an <code><instrumentation></code> element in its manifest file. You write your instrumentation tests in a subclass of {@link android.app.Instrumentation}, from which you have access to a variety of methods for managing the state of the application, from within the application's process. For example, you can write instrumentation to -<ul> -<li>Instantiate the process's Application object -<li>Instantiate an Activity and change it's lifecycle state -<li>Send keypad events to the currently focused window -<li>Execute a menu item -<li>Take a performance snapshot, and -<li>Attach an - -When running with instrumentation turned on, the system instantiates class will be instantiated for you before any of the application code, allowing you to monitor all of the interaction the system has with the application. An Instrumentation implementation is described to the system through an AndroidManifest.xml's <instrumentation> tag. - - -<ul> - <li> - <a href="hierarchy.html">IntroducHierarchy of Screen Elements</a> - </li> - <li> - <a href="layout.html">Common Layout Objects</a> - </li> - <li> - <a href="ui-xml.html">Declaring a UI in XML</a> - </li> - <li> - <a href="binding.html">Binding to Data with AdapterView</a> - </li> - <li> - <a href="ui-events.html">Handling UI Events</a> - </li> - <li> - <a href="themes.html">Applying Styles and Themes to Your Application</a> - </li> - <li> - <a href="custom-views.html">Building Custom Views</a> - </li> - <li> - <a href="glossary.html">UI Elements and Concepts Glossary</a> - </li> - <li> - <a href="{@docRoot}guide/tutorials/views/index.html">Hello Views</a> - </li> - -</ul> --->
\ No newline at end of file diff --git a/docs/html/guide/developing/instrumentation/inst-framework.jd b/docs/html/guide/developing/instrumentation/inst-framework.jd deleted file mode 100644 index 17eea61..0000000 --- a/docs/html/guide/developing/instrumentation/inst-framework.jd +++ /dev/null @@ -1,139 +0,0 @@ -page.title=Instrumentation Framework -@jd:body - -<p>This document describes how to use the Android Instrumentation Framework to write test cases. You should have a working knowledge of the following:</p> -<ul> - <li> Android Application Framework </li> - <li> Using <code>adb</code>, <code>am</code> and various logging functionality </li> - <li> A brief understanding of the application of interest, that is, he names of the classes which handle the intents etc. </li> - <li> Junit testing. </li> -</ul> -<p> Each Android application runs in its own process. Instrumentation kills the application process and restarts the process with Instrumentation. Instrumentation gives a handle to the application context used to poke around the application to validate test assertions, allowing you to write test cases to test applications at a much lower level than UI screen shot tests. Note that Instrumentation cannot catch UI bugs. </p> - -<p>This document covers these topics:</p> - -<ul> -<li><a href="#androidInstrumentationFrameworkamCommand">Understanding the am Command</a></li> -<li><a href="#androidInstrumentationFrameworkWritingRunning">Writing and Running Test Cases</a></li> -<li><a href="#androidInstrumentationFrameworkTestCase">Exploring a Test Case</a></li> -<li><a href="#androidInstrumentationFrameworkTroubleshooting">Troubleshooting</a></li> -</ul> - -<a name="androidInstrumentationFrameworkamCommand"></a><h2>Understanding the am Command</h2> - -<p><code>am</code> is used to start and instrument activities using the adb shell command, as shown in the snippet below:</p> -<pre class="prettify"> -> adb shell am -usage: am [start|instrument] - am start [-a <ACTION>] [-d <DATA_URI>] [-t <MIME_TYPE>] - [-c <CATEGORY> [-c <CATEGORY>] ...] - [-e <EXTRA_KEY> <EXTRA_VALUE> [-e <EXTRA_KEY> <EXTRA_VALUE> ...] - [-n <COMPONENT>] [-D] [<URI>] - am instrument [-e <ARG_NAME> <ARG_VALUE>] [-p <PROF_FILE>] - [-w] <COMPONENT> -For example, to start the Contacts application you can use -> adb shell am start -n com.google.android.contacts/.ContactsActivity -</pre> - - -<a name="androidInstrumentationFrameworkWritingRunning"></a><h2>Writing and Running Test Cases</h2> - -<p>Each instrumentation test case is similar to an Android application with the distinction that it starts another application. For example, have a look in the <code>tests/Contacts</code> directory. </p> -<ul> - <li> There should be a Makefile and an Android Manifest file. </li> - <li> Tests are located in <code>tests/Contacts/src/com/google/android/contactstests</code>. </li> - <li> The Instrumentation Test Runner is located at <code>tests/Contacts/src/com/google/android/contactstests/functional/ContactsInstrumentationTestRunner.java</code>.</li> -</ul> -<p>Suppose you have a makefile with <code>Contactstests</code> as the target. </p> -<ul> - <li> <code>make Contactstests</code>: Compiles the test cases. </li> - <li> <code>adb install Contactstests.apk</code>: Installs the apk on the device. </li> - <li> Use the adb shell <code>am</code> command to run them. </li> -</ul> -<p> For options and other details, please see <a href="inst-testing.html">Instrumentation Testing</a>.</p> - - -<a name="androidInstrumentationFrameworkTestCase"></a><h2>Exploring a Test Case</h2> - -<p> The test case described in this section adds and tests a new Contact. Note that you can send intents, register broadcast receivers, etc. </p> -<p><code>Instrumentation.java</code> has helper functions that send key events and string, for example: </p> -<ul> - <li><code>getInstrumentation()</code>: Returns the handle to the instrumentation </li> - <li><code>sendCharacterSync</code>: Sends a character. </li> - <li><code>sendStringSync</code>: Sends a string to an input box. </li> - <li><code>sendKeyDownUpSync</code>: Sends a specific keyevent. </li> - <li><code>sendTrackballEventSync</code>: Send a trackball event.</li> -</ul> -<p> You can find the test case below at <code>device/tests/Contacts.</code></p> -<pre class="prettify"> -private void addNewContact(String name, int star, int phoneType, String number, String label, - String email, int emailType){ - ContentValues values = new ContentValues(); - Uri phoneUri = null; - Uri emailUri = null; - - values.put(Contacts.People.NAME, name); - values.put(Contacts.People.STARRED, star); - - //Add Phone Numbers - Uri uri = mActivity.getContentResolver().insert(Contacts.People.CONTENT_URI, values); - phoneUri = Uri.withAppendedPath(uri, Contacts.People.Phones.CONTENT_DIRECTORY); - - values.clear(); - values.put(Contacts.Phones.TYPE, phoneType); - values.put(Contacts.Phones.NUMBER, number); - values.put(Contacts.Phones.LABEL, label); - mActivity.getContentResolver().insert(phoneUri, values); - - //Add Email - emailUri = Uri.withAppendedPath(uri, ContactMethods.CONTENT_DIRECTORY); - - values.clear(); - values.put(ContactMethods.KIND, Contacts.KIND_EMAIL); - values.put(ContactMethods.DATA, email); - values.put(ContactMethods.LABEL, ""); - values.put(ContactMethods.TYPE, emailType); - mActivity.getContentResolver().insert(emailUri, values); -} - - - public void testAddSaveSingleContact(){ - int previousCount = mActivity.getListView().getCount(); - String message; - - addNewContact(INPUT_NAME_1 + "1", "5435754532", "1" + INPUT_EMAIL_1, CONFIRM_OPTION); - - message = "Added 1 to initial length=" + previousCount + ", but resulted with a count=" + - mActivity.getListView().getCount(); - assertEquals(message, ++previousCount, mActivity.getListView().getCount()); - - // Check Content; Name; Num; Starred - assertEquals(INPUT_NAME_1 + "1", getTextFromView(0, android.R.id.text1)); - assertEquals("5435754532", getTextFromView(0, android.R.id.text2)); - - //Check email is saved - //cursor = returnEmailCursorAtId("1"); - Uri uri = Uri.parse("content://contacts/people/1"); - uri = Uri.withAppendedPath(uri, ContactMethods.CONTENT_DIRECTORY); - Cursor cursor = mActivity.getContentResolver().query(uri, CONTACTS_COLUMNS, null, null, null); - assertTrue("returnEmailCursorAtId: Moving cursor to first row has failed", cursor.first()); - - int dataIndex = cursor.getColumnIndexOrThrow("data"); - assertEquals("1" + INPUT_EMAIL_1, cursor.getString(dataIndex)); - cursor.deactivate(); -} - </pre> - - -<a name="androidInstrumentationFrameworkTroubleshooting"></a><h2>Troubleshooting</h2> - -<p>If you run your test cases and nothing appears to happen, have a look at <code>adb logcat</code>. The following is a common problem:</p> -<pre class="prettify"> -I/dalvikvm( 688): threadid=11: attached from native, name=Binder Thread #1 -I/dalvikvm( 688): threadid=13: attached from native, name=Binder Thread #2 -W/ActivityManager( 469): Unable to find instrumentation info for: ComponentInfo{com.google.android.browser_instrumentation/com.google.android.browser_instrumentation.BrowserWebkitLayoutInstrumentation} -D/AndroidRuntime( 688): Shutting down VM -E/AndroidRuntime( 688): ERROR: thread attach failed -</pre> -<p>It's possible that the instrumentation apk isn't installed on your device or that the package name is incorrect in the Manifest file. </p> - diff --git a/docs/html/guide/developing/instrumentation/inst-testing.jd b/docs/html/guide/developing/instrumentation/inst-testing.jd index 6f69344..2dc4daa 100644 --- a/docs/html/guide/developing/instrumentation/inst-testing.jd +++ b/docs/html/guide/developing/instrumentation/inst-testing.jd @@ -142,8 +142,6 @@ public class FrameworkInstrumentationTestRunner extends InstrumentationTestRunne <p> Next, in an appropriate <code>AndroidManifest.xml</code>, define the instrumentation for the derived class with the appropriate <code>android:targetPackage</code> set. For example, the snippet below defines the instrumentation runner for the framework tests.</p> <pre> -<uses-permission android:name="android.permission.RUN_INSTRUMENTATION" /> - <instrumentation android:name="android.tests.FrameworkInstrumentationTestRunner" android:targetPackage="com.google.android.frameworktest" android:label="framework instrumentation test runner" /> diff --git a/docs/html/guide/developing/other-ide.jd b/docs/html/guide/developing/other-ide.jd index 78871c5..7bcb509 100644 --- a/docs/html/guide/developing/other-ide.jd +++ b/docs/html/guide/developing/other-ide.jd @@ -2,9 +2,9 @@ page.title=In Other IDEs @jd:body <p>The recommended way to develop an Android application is to use - <a href="#developingwitheclipse">Eclipse - with the ADT plugin</a>. This plugin provides editing, building, - and debugging functionality integrated right into the IDE. </p> + <a href="{@docRoot}guide/developing/eclipse-adt.html">Eclipse with the Android + Development Tools (ADT) plugin</a>, provided in the SDK. The ADT plugin + provides editing, building,and debugging functionality integrated right into the IDE. </p> <p>However, if you'd rather develop your application in another IDE, such as IntelliJ, or use Eclipse without the ADT plugin, you can do that instead. The SDK @@ -82,6 +82,45 @@ activity_name: ActivityName latest version of the application for you to deploy.</li> </ol> +<h2 id="sign_in_other">Setting Up Application Signing</h2> + +<p>As you begin developing Android applications, you should understand that all +Android applications must be digitally signed before the system will install +them on the emulator or an actual device. </p> + +<p>The Android build tools help you get started quickly by signing your .apk +files with a debug key, prior to installing them on the emulator. This means +that you can compile your application and install it on the emulator without +having to generate your own private key. However, please note that if you intend +to publish your application, you <em>must</em> sign the application with your +own private key, rather than the debug key generated by the SDK tools. </p> + +<p>To sign your applications, the ADT plugin requires the Keytool utility +included in the JDK. To set up your development environment for +signing, all you need to do is make sure that Keytool is available on your +machine that the build tools know how to find it. </p> + +<p>In most cases, you can tell the SDK build tools how to find Keytool by making +sure that +your JAVA_HOME environment variable is set and that it references a suitable +JDK. Alternatively, +you can add the JDK version of Keytool to your PATH variable.</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 PATH, it might be pointing to a symlink at +/usr/bin/keytool. +In this case, check the symlink target to make sure that it points to the +keytool in the JDK.</p> + +<p>In all cases, please read and understand <a +href="{@docRoot}guide/publishing/app-signing.html">Signing Your +Applications</a>, which provides an overview of application signing on Android +and what it means to you as an Android application developer. </p> + + <h2>Running an Android Application</h2> <p>To run a compiled application, you will upload the .apk file to the <code>/data/app/ </code>directory @@ -122,7 +161,7 @@ activity_name: ActivityName can be used without DDMS, such as displaying CPU usage or screen refresh rate on the emulator.</li> <li><strong>Configure your IDE to attach to port 8700 for debugging.</strong> We - include information on <a href="#eclipse">how to set up Eclipse to debug - your project</a>. </li> + include information on <a href="{@docRoot}guide/developing/debug-tasks.html#ide-debug-port"> + how to set up Eclipse to debug your project</a>. </li> </ol> diff --git a/docs/html/guide/developing/tools/adb.jd b/docs/html/guide/developing/tools/adb.jd index 50fb024..b111047 100644 --- a/docs/html/guide/developing/tools/adb.jd +++ b/docs/html/guide/developing/tools/adb.jd @@ -104,7 +104,7 @@ Emulator 2, adb: 5557 ... <pre>adb [-d|-e|-s <serialNumber>] <command> </pre> -<p>When you issue a command, the program invokes an adb client. The client is not specifically associated with any emulator instance, so if multiple emulators/devices are running, you need to use the <code>-d</code> option to specify the target instance to which the command should be directed. For more information about using this option, see <a href"#directingcommands">Directing Commands to a Specific Emulator/Device Instance</a>. </p> +<p>When you issue a command, the program invokes an adb client. The client is not specifically associated with any emulator instance, so if multiple emulators/devices are running, you need to use the <code>-d</code> option to specify the target instance to which the command should be directed. For more information about using this option, see <a href="#directingcommands">Directing Commands to a Specific Emulator/Device Instance</a>. </p> <a name="devicestatus"></a> diff --git a/docs/html/guide/developing/tools/adt.jd b/docs/html/guide/developing/tools/adt.jd index c3bd255..f28b24c 100644 --- a/docs/html/guide/developing/tools/adt.jd +++ b/docs/html/guide/developing/tools/adt.jd @@ -90,7 +90,7 @@ If you are having trouble downloading the ADT plugin after following the steps a If you are still unable to use Eclipse to download the ADT plugin, follow these steps to download and install the plugin from your computer: </p> <ol> -<li><a href="adt_download.html">Download the ADT zip file</a> (do not unpack it). +<li><a href="{@docRoot}sdk/adt_download.html">Download the ADT zip file</a> (do not unpack it). <li>Follow steps 1 and 2 in the default install instructions (above). <li>In Eclipse 3.3, click <strong>New Archive Site...</strong>. <br/> In Eclipse 3.4, click <strong>Add Site...</strong>, then <strong>Archive...</strong> diff --git a/docs/html/guide/developing/tools/adt_download.jd b/docs/html/guide/developing/tools/adt_download.jd deleted file mode 100644 index f03cc46..0000000 --- a/docs/html/guide/developing/tools/adt_download.jd +++ /dev/null @@ -1,65 +0,0 @@ -page.title=Download the ADT Plugin Zip File -@jd:body - -<p> -If you are unable to download the ADT plugin through <a -href="{@docRoot}guide/developing/tools/adt.html#installingplugin">setting up a remote -update site</a> in Eclipse, you can download the ADT zip file and install it -from your computer (archived site) instead. -</p> -<p> -If you go with this method, in order to update the plugin, you will need to -download the latest version from this page, uninstall the old version from -Eclipse, then install the new version. For more details on the procedure, -see Troubleshooting ADT Installation in the -<a href="{@docRoot}guide/developing/tools/adt.html#troubleshooting"> installation -page</a>. -</p> -<p> -<table> - <tr> - <th>Version</th> - <th>File</th> - <th>Date</th> - <th>Compatible SDK Versions</th> - <th>Notes</th> - </tr> - - <tr> - <td style="background-color:#ffcccc;">0.8.0</td> - <td style="background-color:#ffcccc;"><a href="http://dl-ssl.google.com/android/ADT-0.8.0.zip">ADT-0.8.0.zip</a></td> - <td style="background-color:#ffcccc;">23 September 2008</td> - <td style="background-color:#ffcccc;">Android 1.0 SDK, Release 1</td> - <td style="background-color:#ffcccc;">Required for users of Android 1.0 SDK, Release 1. </td> - </tr> - <tr> - <td>0.7.1</td> - <td><a href="http://dl-ssl.google.com/android/ADT-0.7.1.zip">ADT-0.7.1.zip</a></td> - <td>18 Aug 2008</td> - <td>Android 0.9 SDK beta</td> - <td>Required for users of Android 0.9 SDK beta. As of this version, <b>Eclipse 3.2 is no longer supported.</b> - Please upgrade to Eclipse Ganymede (3.4) or Europa (3.3) if you are still using 3.2. </td> - </tr> - <tr> - <td>0.4.0</td> - <td><a href="http://dl-ssl.google.com/android/ADT-0.4.0.zip">ADT-0.4.0.zip</a></td> - <td>12 Feb 2008</td> - <td>m5-rc14</td> - <td>Required if you are using the M5 SDK. See the SDK Release Notes for details on changes and enhancements in this version.</td> - </tr> - <tr> - <td>0.3.3</td> - <td><a href="http://dl-ssl.google.com/android/ADT-0.3.3.zip">ADT-0.3.3.zip</a></td> - <td>14 Dec 2007</td> - <td>m3-rc37</td> - <td>Some significant enhancements (see SDK Release Notes).</td> - </tr> - <tr> - <td>0.3.1</td> - <td><a href="http://dl-ssl.google.com/android/ADT-0.3.1.zip">ADT-0.3.1.zip</a></td> - <td>21 Nov 2007</td> - <td>m3-rc20, m3-rc22</td> - <td>Initial Release.</td> - </tr> -</table> -</p> |