IoTGateway/BSP/Android/Gettingstarted/ADB for development APK - Revision history

Liszt.kao at 07:38, 25 January 2017

2017-01-25T07:38:35Z

2017-01-25T07:38:24Z

2017-01-25T07:38:05Z

2017-01-25T07:37:51Z

2017-01-25T07:37:34Z

2017-01-25T07:31:54Z

2017-01-25T07:31:40Z

2017-01-25T07:31:27Z

2017-01-25T07:31:14Z

2017-01-25T07:31:00Z

@@ Line 45: / Line 45: @@
 == Enable adb debugging on your device ==
-----
 To use adb with a device connected over USB, you must enable&nbsp;'''USB debugging'''&nbsp;in the device system settings, under&nbsp;'''Developer options'''.

@@ Line 31: / Line 31: @@
 == How adb works ==
-----
 When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. When the server starts, it binds to local TCP port 5037 and listens for commands sent from adb clients—all adb clients use port 5037 to communicate with the adb server.

@@ Line 61: / Line 61: @@
 == Connect to a device over Wi-Fi ==
-----
 adb is usually used over USB. However, it is also possible to use over Wi-Fi, as described here.

@@ Line 98: / Line 98: @@
 == Query for devices ==
-----
 Before issuing adb commands, it is helpful to know what emulator/device instances are connected to the adb server. You can generate a list of attached emulators/devices using the&nbsp;<code>devices</code>&nbsp;command:

@@ Line 124: / Line 124: @@
 == Send commands to a specific device ==
-----
 If multiple emulator/device instances are running, you must specify a target instance when issuing adb commands. To do so, use the&nbsp;<code>-s</code>&nbsp;option in the commands. The usage for the&nbsp;<code>-s</code>&nbsp;option is:

@@ Line 138: / Line 138: @@
 == Install an app ==
-----
 You can use adb to copy an application from your development computer and install it on an emulator/device instance. To do so, use the&nbsp;<code>install</code>command. With the command, you must specify the path to the APK file that you want to install:

@@ Line 149: / Line 149: @@
 == Set up port forwarding ==
-----
 You can use the&nbsp;<code>forward</code>&nbsp;command to set up arbitrary port forwarding — forwarding of requests on a specific host port to a different port on an emulator/device instance. Here's how you would set up forwarding of host port 6100 to emulator/device port 7100:

@@ Line 159: / Line 159: @@
 == Copy files to/from a device ==
-----
 You can use the adb commands&nbsp;<code>pull</code>&nbsp;and&nbsp;<code>push</code>&nbsp;to copy files to and from an emulator/device instance. Unlike the&nbsp;<code>install</code>&nbsp;command, which only copies an APK file to a specific location, the&nbsp;<code>pull</code>&nbsp;and&nbsp;<code>push</code>&nbsp;commands let you copy arbitrary directories and files to any location in an emulator/device instance.

@@ Line 174: / Line 174: @@
 == Stop the adb server ==
-----
 In some cases, you might need to terminate the adb server process and then restart it to resolve the problem (e.g., if adb does not respond to a command).
 To stop the adb server, use the&nbsp;<code>adb kill-server</code>&nbsp;command. You can then restart the server by issuing any other adb command.
 == adb commands reference ==

@@ Line 184: / Line 184: @@
 == adb commands reference ==
-----
 You can issue adb commands from a command line on your development machine or from a script. The usage is: