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. Then, from the directory of this ADB binary, open the command prompt. This can be done by clicking the 'Open command prompt here' option and holding Shift and Right-Click in the folder.
See 'PowerShell,' instead of 'prompt command,' for some Windows 10 users. Connect your smartphone or tablet using USB cable to your computer. Before issuing adb commands, it is helpful to know what device instances are connected to the adb server.
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. You agree that Google may stop permanently or temporarily providing the SDK or any features within the SDK to you or to users generally at Google's sole discretion, without prior notice to you. Use of the SDK by You 4. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users.
If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so. Your Developer Credentials 5.
Privacy and Information 6. Before any of this information is collected, the SDK will notify you and seek your consent. If you withhold consent, the information will not be collected. 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.
0コメント