While this is a relatively straightforward process, the steps involved differ depending on whether the development system is running Windows, Mac OS X or Linux. All that remains is to configure the development system to detect the device when it is attached. Swipe downward from the top of the screen to display the notifications panel (Figure 6 3) and note that the device is currently connected for debugging.Īt this point, the device is now configured to accept debugging connections from adb on the development system. Purchase the fully updated Android Studio Electric Eel Edition of this publication in eBook ($29.99) or Print ($49.99) formatĪndroid Studio Electric Eel Essentials - Java Edition Print and eBook (PDF) editions contain 88 chapters and over 800 pagesĤ. You are reading a sample chapter from the Android Studio 1.x / Android 6 Edition book. The following command output indicates the presence of an AVD on the system but no physical devices: $ adb devices For example, a listing of currently active virtual or physical devices may be obtained using the devices command-line argument.
Similarly, Android Studio also has a built-in client.Ī variety of tasks may be performed using the adb command-line tool.
For example, a client is provided in the form of a command-line tool named adb located in the Android SDK platform-tools sub-directory. The ADB client can take a variety of forms. The ADB consists of a client, a server process running in the background on the development system and a daemon background process running in either AVDs or real Android devices such as phones and tablets. The primary purpose of the ADB is to facilitate interaction between a development system, in this case Android Studio, and both AVD emulators and physical Android devices for the purposes of running and debugging applications. An Overview of the Android Debug Bridge (ADB)
0 kommentar(er)
