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. This option forces adb to use the feature or fail if it is not supported with verbose information on why it failed.
Options: -k : Keep the data and cache directories around after package removal. On devices running Android 6. On devices running Android 5. Location values: 0 : Auto: Let system decide the best location.
Note: This is only intended for debugging; using this can cause apps to break and other undesireable behavior. To help you develop and test your device management or other enterprise apps, you can issue commands to the device policy manager dpm tool. Use the tool to control the active admin app or change a policy's status data on the device. You can also issue a device policy manager command directly from adb without entering a remote shell:. You can also pass --user current to select the current user.
The app must declare android:testOnly in the manifest. This command also removes device and profile owners. This is useful to avoid the device's scheduling restrictions when developing apps that manage freeze-periods. See Manage system updates. Supported on devices running Android 9. This command is rate-limited. The screencap command is a shell utility for taking a screenshot of a device display. The utility records screen activity to an MPEG-4 file.
It does not provide debug services. If you previously performed this step for another Android device, and you can debug over USB with that Android device, you do not need to install this USB driver a second time.
You can go directly to the next section and verify that USB debugging is enabled on your Android device. You must be a member of the Administrator group or be logged in as Administrator on your Windows development system to perform the operations described below. You can try the Chrome desktop browser test described on this page to see if your device is being recognized for debug.
If you see none of the above options you may have to select Show All Devices at the top of the list and then click the Next button to get a complete list of device drivers installed on your system. Just download the latest driver from the above links and extract downloaded zip files on your computer.
After extraction, double click on. To download the proper driver by the version or Device ID. The driver package includes ADB as well as the Fastboot drivers. The Intel Android. USB Driver package enables you to connect your Windows. The feature allows them to side-load apps that they cannot acquire from the Google Play Store. In this article, we are going to teach you how to install Android Debug Bridge for Windows Make sure you read through the article to get bonus tips that will enhance your user experience!
You will see the detailed instructions below. Make sure you follow them carefully to be able to set up the ADB correctly. Benchmark your app. Measure performance. Publish your app. Command line tools. Android Developers. Click the SDK Tools tab. Download the Google USB driver Before downloading, you must agree to the following terms and conditions. Introduction 1. Accepting this License Agreement 2. If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity.
SDK License from Google 3. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose.
Google reserves all rights not expressly granted to you. Except to the extent required by applicable third party licenses, you may not copy except for backup purposes , modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK.
0コメント