Setting up an android device for development

When building a mobile application, it’s important that you always test your application on a real device before releasing it to users. This page describes how to set up your development environment and Android-powered device for testing and debugging on the device.

Setting up an android device for development

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

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.On the device, go to the home screen, press MENU, select Applications > Development, then enable USB debugging.
3. Setup your system to detect your device
   • You need to add a rules file that contains a USB configuration for each type of device you want to use for development. Each device manufacturer uses a different vendor ID. The example rules files below show how to add an entry for a single vendor ID (the Sony Ericsson vendor ID). I’m using X10 MiniPro right now, so I use this USB Vendor ID Code as an example. In order to support more devices, you will need additional lines of the same format that provide a different value for the SYSFS{idVendor} property. For other IDs, see the table of USB Vendor IDs at the bottom of this page..
     Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
     SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0fce", MODE="0666"
     Now execute:
     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 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, and it should show :
{code}[root@jfwork1 ~]# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
43423531314D38575738 device{/code}

USB Vendor IDs

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.

Note :

• Axioo Picopad using Foxconn / Hon Hai USB Vendor ID and it will show :
  {code}[root@jfwork1 ~]# adb devices
  * daemon not running. starting it now on port 5037 *
  * daemon started successfully *
  List of devices attached
  FM6120440102 device{/code}
• When developing on a device, keep in mind that you should still use the 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 platform, in different screen sizes and orientations, and more.

Done !! Good Luck and Happy debugging 🙂