diff --git a/docs/html/guide/developing/device.jd b/docs/html/guide/developing/device.jd index 2c42e78cddd6a..9dea053ab43f7 100644 --- a/docs/html/guide/developing/device.jd +++ b/docs/html/guide/developing/device.jd @@ -7,11 +7,12 @@ page.title=Developing on a Device
  1. Available Devices
      -
    1. T-Mobile G1
      2. +
    2. Consumer devices
    3. Android Dev Phone 1
  2. Setting up a Device for Development
    3. +
  3. Installing the WinUsb Driver
@@ -23,20 +24,24 @@ developing and debugging.

Available Devices

-

While developers can use regular -consumer devices purchased at retail to test and use their apps, some developers -may choose not to use a retail device, preferring an unlocked or no-contract -device. Here are some options for obtaining devices capable of testing your applications.

+

Here are some options for obtaining devices capable of testing your applications.

-

T-Mobile G1

+

Consumer devices

-

The T-Mobile G1 device makes an excellent development device. You can write -applications in the SDK and install them on the G1, then run them as users -would, using the same hardware, system, and network.

+

It's likely that one of your local mobile carriers offers an Android-powered device. +Any Android-powered device (even one bought from your mobile carrier) is a perfectly good +device for running and testing your own Android applications. +You can write applications using the Android SDK and then install them +directly onto the device for testing.

+ +

Check with the service providers in your area to determine which Android-powered +devices are available.

+ +

Be aware that consumer devices are not designed to allow system image updates by the +user. If you're interested in manually updating the device with custom system images, then +you'll need a developer device such as the Android Dev Phone 1.

-

For more information about obtaining a G1, visit the T-Mobile G1 site.

Android Dev Phone 1

@@ -60,6 +65,7 @@ href="http://www.t-mobileg1.com">T-Mobile G1 site.

+

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 @@ -67,7 +73,7 @@ applications. You can use any SIM in the device and can flash custom Android builds that will work with the unlocked bootloader. Unlike the bootloader on retail devices, the bootloader on the Android Dev Phone 1 does not enforce signed system images. The Android Dev Phone 1 should also appeal to developers -who live outside of T-Mobile geographies.

+who live in geographies where local mobile carriers do not currently offer Android-powered devices.

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. @@ -82,25 +88,30 @@ 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.

-

Note that Android Dev Phone 1 devices are not intended for +

Android Dev Phone 1 devices are not intended for 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.

+

Note that your Android Dev Phone 1 will not receive automated +over-the-air (OTA) updates for the system image. System updates must be flashed manually. +See the HTC site for a guide to Flashing +your Android Dev Phone with a Factory System Image.

+

For full device specs and more information about obtaining an Android Dev Phone 1 device, see the Android Market site.

+

Setting up a Device for Development

-

With a T-mobile G1 or Android Dev Phone 1, you can develop and debug your Android applications just as you +

With an Android-powered device, you can develop and debug your Android applications just as you would on the emulator. There are just a few things to do before you can start.

  1. Declare your application as "debuggable" in your Android Manifest.

    In Eclipse, you can do this from the Application tab when viewing the Manifest (on the right side, set Debuggable to true). Otherwise, in the AndroidManifest.xml - file, add android:debuggable="true" to the <application> element.

  2. Turn on "USB Debugging" on your device. @@ -110,30 +121,8 @@ would on the emulator. There are just a few things to do before you can start.
  3. Setup your system to detect your device.