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. 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. That said, Auslogics Driver Updater will locate the latest manufacturer-recommended drivers that are compatible with your system.
Please, assure yourself in the compatibility of the selected driver with your current OS just to guarantee its correct and efficient work. Get the ADB driver file. Open Google Chrome. Open Settings on your Android device. 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.
Click "Have Disk" 7. Browse to the folder where you extracted the driver and click Ok. Usually targeted at developers, the ADB Android Debug Bridge driver basically allows advanced users to connect any Android mobile phone to a computer and find workarounds for various application problems or even modify the operating system.
Even though this driver is developed for users with a richer ADB command background, it can also be used by regular mobile phone owners, but at their own risk. We recommend that average users make use of this tool wisely, after they have read the step-by-step instructions. Third Party Applications 7. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources.
You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources either in whole or in part unless you have been specifically given permission to do so by the relevant owners.
In that case, the License Agreement does not affect your legal relationship with these third parties. Using Android APIs 8. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data either in whole or in part unless allowed by the relevant Terms of Service.
Terminating this License Agreement 9. Indemnification Changes to the License Agreement When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available. General Legal Terms The remaining provisions of the License Agreement will continue to be valid and enforceable.
Other than this, no other person or company shall be third party beneficiaries to the License Agreement. Neither you nor Google shall be permitted to delegate their responsibilities or obligations under the License Agreement without the prior written approval of the other party.
0コメント