34,333
edits
Changes
no edit summary
Whilst much can be achieved by testing applications using an Android Virtual Device (AVD), there is no substitute for performing real world application testing on a physical Android deviceand there are a number is features of Android that are only available on physical Android devices.
Communication with both AVD instances and connected Android devices is handled by the Android Debug Bridge (ADB). In this chapter we will work through the steps to configure the adb environment to enable application testing on a physical Android device with Mac OS X, Windows and Linux based systems.
</pre>
== Enabling ADB on Android 4.2 4 based Devices ==
Before ADB can connect to an Android device, that device must first be configured to allow the connection. On phone and tablet devices running Android 4.2 4 or later, the steps to achieve this are as follows:
1. Open the Settings app on the device and select the About tablet or About phone option.
2. On the About screen, scroll down to the Build number field (Figure 5 -1) and tap on it seven times until a message appears indicating that developer mode has been enabled.
[[Image:android_about_screen.png|The Build Number on the About screen of an Android 4.2 4 device]]
Figure 5-1
Right-click on the device name and select Update Driver Software from the menu. Once the device drivers have been uninstalled, disconnect the device from the computer. Select the option to Browse my computer for driver software and in the next dialog, keep the Include subfolder option selected and click on the Browse… button. Navigate to the location into which the USB drivers were installed (in the case of the Google USB driver, this will be <sdk path>\sdk\extras\google\usb_driver) and click on OK to select the driver folder followed by Next to initiate the installation.
During the installation, a Windows Security prompt will appear seeking permission to install the driver as illustrated in Figure 5-6. When this dialog appears, click on the Install button to proceed.
</pre>
If the device is listed as offlineor unauthorized, go to the device display and check for the dialog shown in Figure 5-9 seeking permission to Allow USB debugging.
