You can generate a list of attached devices using the devices command. The following example shows the devices command and its output. There are three devices running. The first two lines in the list are emulators, and the third line is a hardware device that is attached to the computer. The adb devices command has a corner-case command sequence that causes running emulator s to not show up in the adb devices output even though the emulator s are visible on your desktop. This happens when all of the following conditions are true:.
One way to avoid this situation is to let the emulator choose its own ports, and don't run more than 16 emulators at once. Another way is to always start the adb server before you use the emulator command, as explained in the following examples.
Example 1: In the following command sequence, the adb devices command starts the adb server, but the list of devices does not appear. Stop the adb server and enter the following commands in the order shown. For the avd name, provide a valid avd name from your system. To get a list of avd names, type emulator -list-avds.
Example 2: In the following command sequence, adb devices displays the list of devices because the adb server was started first. To see the emulator in the adb devices output, stop the adb server, and then start it again after using the emulator command and before using the adb devices command, as follows:.
For more information about emulator command-line options, see Using Command Line Parameters. If multiple devices are running, you must specify the target device when you issue the adb command.
To specify the target, use the devices command to get the serial number of the target. Once you have the serial number, use the -s option with the adb commands to specify the serial number. In the following example, the list of attached devices is obtained, and then the serial number of one of the devices is used to install the helloWorld. Note: If you issue a command without specifying a target device when multiple devices are available, adb generates an error.
If you have multiple devices available, but only one is an emulator, use the -e option to send commands to the emulator. Likewise, if there are multiple devices but only one hardware device attached, use the -d option to send commands to the hardware device. You can use adb to install an APK on an emulator or connected device with the install command:. You must use the -t option with the install command when you install a test APK.
For more information, see -t. Instead, Android Studio handles the packaging and installation of the app for you. You can use the forward command to set up arbitrary port forwarding, which forwards requests on a specific host port to a different port on a device. The following example sets up forwarding of host port to device port Use the pull and push commands to copy files to and from an device.
Unlike the install command, which only copies an APK file to a specific location, the pull and push commands let you copy arbitrary directories and files to any location in a device.
In some cases, you might need to terminate the adb server process and then restart it to resolve the problem e. To stop the adb server, use the adb kill-server command. You can then restart the server by issuing any other adb command. You can issue adb commands from a command line on your development machine or from a script. The usage is:. If there's only one emulator running or only one device connected, the adb command is sent to that device by default.
You can use the shell command to issue device commands through adb, or to start an interactive shell. To issue a single command use the shell command like this:.
To start an interactive shell on a device use the shell command like this:. Note: With Android Platform-Tools 23 and higher, adb handles arguments the same way that the ssh 1 command does. But, this change means that the interpretation of any command that contains shell metacharacters has also changed.
For example, the adb shell setprop foo 'a b' command is now an error because the single quotes ' are swallowed by the local shell, and the device sees adb shell setprop foo a b. To make the command work, quote twice, once for the local shell and once for the remote shell, the same as you do with ssh 1.
For example, adb shell setprop foo "'a b'". Android provides most of the usual Unix command-line tools. For a list of available tools, use the following command:.
Help is available for most of the commands via the --help argument. Many of the shell commands are provided by toybox. General help applicable to all toybox commands is available via toybox --help. See also Logcat Command-Line Tool which is useful for monitoring the system log. Within an adb shell, you can issue commands with the activity manager am tool to perform various system actions, such as start an activity, force-stop a process, broadcast an intent, modify the device screen properties, and more.
While in a shell, the syntax is:. You can also issue an activity manager command directly from adb without entering a remote shell. See the Specification for intent arguments.
Options are: -D : Enable debugging. Prior to each repeat, the top activity will be finished. This command kills only processes that are safe to kill and that will not impact the user experience. Use with [-e perf true] to generate raw output for performance measurements. Required for test runners. Options are: -w : Wait for debugger when app starts. This command is helpful for testing your app across different screen sizes by mimicking a small screen resolution using a device with a large screen, and vice versa.
Example: am display-size x display-density dpi Override device display density. This command is helpful for testing your app across different screen densities on high-density screen environment using a low density screen, and vice versa. Example: am display-density to-uri intent Print the given intent specification as a URI. Specification for intent arguments For activity manager commands that take an intent argument, you can specify the intent with the following options:.
Within an adb shell, you can issue commands with the package manager pm tool to perform actions and queries on app packages installed on the device. You can also issue a package manager command directly from adb without entering a remote shell. Options: -f : See their associated file. Options: -g : Organize by group. Options: -f : List the APK file for the test package.
Options: -r : Reinstall an existing app, keeping its data. This feature is only supported on certain devices. Download What's new User guide Preview. Features overview Release notes. Android Developers.
Revisions Fix bug in adb track-devices where devices over wireless debugging wouldn't immediately receive updates. Derive device locked state from property instead of parsing the kernel command line. Improve incremental installation performance.
Fix adb push --sync with multiple inputs. Improve performance of incremental apk installation. Improve error handling for incremental apk installation. Fix adb install-multi-package. Fix some more crashes related to adb wireless pairing.
Improve some error messages. Fix fastboot flashall on older devices such as Nexus 7. Fix crash when using adb -H. Fix hang in adb logcat when run before a device is connected. Improve performance of adb install-multi on Android 10 or newer devices. Update support for wireless pairing. Add support for incremental APK installation. Improve performance of adb push on high-latency connections.
Fix hang when using adb install on something that isn't actually a file. Add --fastdeploy option to adb install , for incremental updates to APKs while developing. This also fixes a related bug in the Android Studio Profilers that causes an AdbCommandRejectedException , which you can see in the idea. Fix devices going offline on Windows. Improve adb install output and help text. On Linux, when connecting to a newer adb server, instead of killing the server and starting an older one, adb attempts to launch the newer version transparently.
Previously, adb root; adb wait-for-device could mistakenly return immediately if adb wait-for-device started before adb noticed that the device had disconnected. Fixes authentication—when the private key used for authentication does not match the public key—by calculating the public key from the private key, instead of assuming that they match.
Updated Windows requirements The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. Scroll down, then tap About Phone or About.
Enable the Developer options by tapping the Build number seven times. Remember to set the toggle at the top to On. Enable USB Debugging. Plug your Android device into your computer. This should bring up Device Manager. Look for your Android device. Right-click it, then select Properties from the options. If the driver is not installed properly, you will see a yellow warning icon beside your Android device. Go to the Driver tab, then click Update Driver. A new window will pop up. Search for the ADB driver file you previously downloaded by clicking Browse.
Select the box beside Include Subfolders, then click Next. Device Manager will automatically install the ADB driver. Special offer.
0コメント