diff --git a/docs/html/guide/developing/device.jd b/docs/html/guide/developing/device.jd index 5443529d51d24..cfb9a36bcd600 100644 --- a/docs/html/guide/developing/device.jd +++ b/docs/html/guide/developing/device.jd @@ -41,7 +41,8 @@ Dev Phone, see the Android MarketNote: When developing on a device, keep in mind that you should still use the Android emulator to test your application +href="{@docRoot}guide/developing/devices/emulator.html">Android emulator to test your +application on configurations that are not equivalent to those of your real device. Although the emulator does not allow you to test every device feature (such as the accelerometer), it does allow you to verify that your application functions properly on different versions of the Android @@ -56,14 +57,22 @@ would on the emulator. Before you can start, there are just a few things to do:<
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.
AndroidManifest.xml
+ file, add android:debuggable="true" to the <application>
+element.
+ On +the device, go to Settings > Applications and enable + +Unknown sources.
+On the device, go to the home screen, press MENU, select Applications > Development, - then enable USB debugging.
+On the device, go to Settings > Applications > Development + and enable USB debugging.
SYSFS{idVendor} property. For other IDs, see the table of USB Vendor IDs, below.
- /etc/udev/rules.d/51-android.rules.
- For Gusty/Hardy, edit the file to read:
- SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4",
- MODE="0666"
udev
+rules file that contains a USB configuration for each type of device
+you want to use for development. In the rules file, each device manufacturer
+is identified by a unique vendor ID, as specified by the
+ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on
+Ubuntu Linux:
- For Dapper, edit the file to read:
- SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4",
- MODE="0666"
/etc/udev/rules.d/51-android.rules.
+ Use this format to add each vendor to the file:
+ SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4",
+MODE="0666", GROUP="plugdev"
+
+
+ In this example, the vendor ID is for HTC. The MODE
+assignment specifies read/write permissions, and GROUP defines
+which Unix group owns the device node.
Note: The rule syntax
+may vary slightly depending on your environment. Consult the udev
+documentation for your system as needed. For an overview of rule syntax, see
+this guide to writing udev
+rules.
chmod a+r /etc/udev/rules.d/51-android.rules
+ chmod a+r /etc/udev/rules.d/51-android.rules
You can verify that your device is connected by executing adb devices from your
-SDK {@code platform-tools/} directory. If connected, you'll see the device name listed as a
-"device."
You can verify that your device is connected by executing adb
+devices from your SDK {@code platform-tools/} directory. If connected,
+you'll see the device name listed as a "device."
If using Eclipse, run or debug as usual. You will be presented -with a Device Chooser dialog that lists the available emulator(s) and connected device(s). -Select the device upon which you want to install and run the application.
- -If using the Android Debug Bridge (adb),
-you can issue commands with the -d flag to target your
-connected device.
If using Eclipse, run or debug your application as usual. You will be +presented with a Device Chooser dialog that lists the available +emulator(s) and connected device(s). Select the device upon which you want to +install and run the application.
+If using the Android
+Debug Bridge (adb), you can issue commands with the -d flag to
+target your connected device.
This table provides a reference to the vendor IDs needed in order to add
-USB device support on Linux. The USB Vendor ID is the value given to the
-SYSFS{idVendor} property in the rules file, as described in step 3, above.
This table provides a reference to the vendor IDs needed in order to add USB
+device support on Linux. The USB Vendor ID is the value given to the
+ATTR{idVendor} property in the rules file, as described
+above.
| Company | USB Vendor ID |
|---|---|
| Acer | -0502 | 0502 |
+
+
| ASUS | +0b05 |
+
| Dell | -413c | 413c |
+
| Foxconn | -0489 | 0489 |
+
| Garmin-Asus | -091E | 091E |
+
18d1 | 18d1 |
+
| HTC | -0bb4 | 0bb4 |
+
| Huawei | -12d1 | 12d1 |
+
| K-Touch | -24e3 | 24e3 |
+
+
| KT Tech | +2116 |
+
| Kyocera | -0482 | 0482 |
+
| Lenevo | -17EF | 17EF |
+
| LG | -1004 | 1004 |
+
| Motorola | -22b8 | 22b8 |
+
+
| NEC | +0409 |
+
| Nook | +2080 |
+
| Nvidia | -0955 | 0955 |
+
+
| OTGV | +2257 |
+
| Pantech | -10A9 | 10A9 |
+
+
| Pegatron | +0x1D4D |
+
| Philips | +0471 |
+
| PMC-Sierra | +04da |
+
| Qualcomm | +05c6 |
+
| SK Telesys | +1f53 |
+
| Pegatron | 0x1D4D |
| Samsung | -04e8 | 04e8 |
+
| Sharp | -04dd | 04dd |
+
| Sony Ericsson | -0fce | 0fce |
+
+
| Toshiba | +0930 |
+
| ZTE | -19D2 | 19D2 |
+