The Pair devices over Wi-Fi window pops up, as shown in figure 2. Figure 2. Popup window to pair devices using QR code or pairing code. On your device, tap Wireless debugging and pair your device:. To pair your device with a QR code, select Pair device with QR code and scan the QR code obtained from the Pair devices over Wi-Fi popup shown in figure 2. To pair your device with a pairing code, select Pair device with pairing code from the Pair devices over Wi-Fi popup. On your device, select Pair using pairing code and take note of the six-digit code provided. Once your device appears on the Pair devices over Wi-Fi window, you can select Pair and enter the six-digit code shown on your device.

To pair a different device or to forget the current device on your workstation, navigate to Wireless debugging on your device. Tap your workstation name under Paired devices and select Forget. Alternatively, to connect to your device using command line without Android Studio, follow these steps:. Find your IP address, port number, and pairing code by selecting Pair device with pairing code. Take note of the IP address, port number, and pairing code displayed on the device. On your workstation's terminal, run adb pair ipaddr:port. Use the IP address and port number from above. If you are having issues connecting to your device wirelessly, try the following troubleshooting steps to resolve the issue. Check that the workstation and device meet the prerequisites listed at the beginning of this section.

The following is a list of current known issues with wireless debugging in Android Studio and how to resolve them:. Wi-Fi is not connecting : Some Wi-Fi networks, such as corporate Wi-Fi networks, may block p2p connections and not let you connect over Wi-Fi. Try connecting with a cable or another Wi-Fi network. adb over Wi-Fi sometimes turns off automatically : This can happen if the device either switches Wi-Fi networks or disconnects from the network. To resolve, re-connect to the network. Note: The following instructions do not apply to Wear devices running Android 10 or lower. See the guide about debugging a Wear OS app for more information. adb usually communicates with the device over USB, but you can also use adb over Wi-Fi. To connect a device running Android 10 or lower, follow these initial steps over USB:.

Note: Beware that not all access points are suitable. You might need to use an access point whose firewall is configured properly to support adb. Before issuing adb commands, it is helpful to know what device instances are connected to the adb server. Generate a list of attached devices using the devices command:. In response, adb prints this status information for each device:. 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 emulators to not show up in the adb devices output even though the emulators 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 to run no 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 Command-Line startup options. If multiple devices are running, you must specify the target device when you issue the adb command. To specify the target, follow these steps: 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. apk on that device:. Note: If you issue a command without specifying a target device when multiple devices are available, adb displays an error.

If you have multiple devices available but only one is an emulator, use the -e option to send commands to the emulator. 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. Note: If you are using Android Studio, you do not need to use adb directly to install your app on the emulator or device. Instead, Android Studio handles the packaging and installation of the app for you. 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 This could be useful if you are trying to detemine what is being sent to a given port on the device.

All received data will be written to the system-logging daemon and displayed in the device logs. 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. For example, this could be the case if adb does not respond to a command. To stop the adb server, use the adb kill-server command. You can then restart the server by issuing any other adb command. Issue adb commands from a command line on your development machine or from a script using the following:. If there's only one emulator running or only one device connected, the adb command is sent to that device by default.

You can see a detailed list of all supported adb commands using the following command:. 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:. 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. With Android Platform Tools 23 and higher, adb handles arguments the same way that the ssh 1 command does. This change means that the interpretation of any command that contains shell metacharacters has also changed.

For example, adb shell setprop key ' value ' is now an error, because the single quotes ' are swallowed by the local shell, and the device sees adb shell setprop key value. To make the command work, quote twice, once for the local shell and once for the remote shell, as you do with ssh 1. For example, adb shell setprop key ' value '. 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. 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. startservice [ options ] intent Start the Service specified by intent. If not specified, then run as the current user. force-stop package Force-stop everything associated with package. kill [ options ] package Kill all processes associated with package. This command kills only processes that are safe to kill and that will not impact the user experience. If not specified, then kill all users' processes. kill-all Kill all background processes. broadcast [ options ] intent Issue a broadcast intent. If not specified, then send to all users. instrument [ options ] component Start monitoring with an Instrumentation instance. Use with [-e perf true] to generate raw output for performance measurements.

Required for test runners. If not specified, run in the current user. profile start process file Start profiler on process , write results to file. profile stop process Stop profiler on process. dumpheap [ options ] process file Dump the heap of process , write to file. If not specified, the current user is used. set-debug-app [ options ] package Set app package to debug. Options are: -w : Wait for debugger when app starts. clear-debug-app Clear the package previous set for debugging with set-debug-app. monitor [ options ] Start monitoring for crashes or ANRs. screen-compat {on off} package Control screen compatibility mode of package. display-size [reset width x height ] Override device display size. 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 by mimicking a 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. to-intent-uri intent Print the given intent specification as an intent: 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 associated file. list permission-groups Print all known permission groups. list permissions [ options ] group Print all known permissions, optionally only those in group.

Options: -g : Organize by group. list instrumentation [ options ] List all test packages. Options: -f : List the APK file for the test package. list features Print all features of the system. list libraries Print all the libraries supported by the current device. list users Print all users on the system. path package Print the path to the APK of the given package. install [ options ] path Install a package, specified by path , to the system. Options: -r : Reinstall an existing app, keeping its data. If the APK is built using a developer preview SDK, you must include the -t option with the install command if you are installing a test APK.

To use this feature, you must sign the APK, create an APK Signature Scheme v4 file , and place this file in the same directory as the APK. 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. Append the --wait option to wait until the APK is fully installed before granting access to the APK. Options: -k : Keep the data and cache directories after package removal. clear package Delete all data associated with a package. On devices running Android 6. On devices running Android 5. set-install-location location Change the default install location.

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. Print the domain verification state for the given package , or for all packages if none is specified. Include all domains, not just autoVerify ones. reset-app-links [ options ] [ package ] Reset domain verification state for the given package, or for all packages if none is specified. verify-app-links [ --re-verify ] [ package ] Broadcast a verification request for the given package , or for all packages if none is specified.

Only sends if the package has previously not recorded a response. The domain must be declared by the package as autoVerify for this to work. This command will not report a failure for domains that could not be applied. Note that the domain verification agent can override this. domains : space-separated list of domains to change, or "all" to change every domain. The domain must be declared by the package for this to work. Use the tool to control the active admin app or change a policy's status data on the device. While in a shell, the dpm syntax is:.

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. set-profile-owner [ options ] component Set component as active admin and its package as profile owner for an existing user. set-device-owner [ options ] component Set component as active admin and its package as device owner. remove-active-admin [ options ] component Disable an active admin. The app must declare android:testOnly in the manifest. This command also removes device and profile owners. clear-freeze-period-record Clear the device's record of previously set freeze periods for system OTA updates. This is useful to avoid the device 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.

png Record a video The screenrecord command is a shell utility for recording the display of devices running Android 4. The utility records screen activity to an MPEG-4 file. You can use this file to create promotional or training videos or for debugging and testing. Otherwise, the recording stops automatically at three minutes or the time limit set by --time-limit. To begin recording your device screen, run the screenrecord command to record the video. Then, run the pull command to download the video from the device to the host computer. mp4 The screenrecord utility can record at any supported resolution and bit rate you request, while retaining the aspect ratio of the device display. The utility records at the native display resolution and orientation by default, with a maximum length of three minutes. Table 4. screenrecord options. Starting in Android 7. Examine the collected profiles to understand which methods are executed frequently and which classes are used during app startup.

Content and code samples on this page are subject to the licenses described in the Content License. Platform Android Studio Google Play Jetpack Kotlin Docs Games. Android Studio. Download What's new User guide Preview. Platform Android Studio Download What's new User guide Preview Google Play Jetpack Kotlin Docs Games. Features overview Release notes. Android Developers. Downloads If you're an Android developer, you should get the latest SDK Platform-Tools from Android Studio's SDK Manager or from the sdkmanager command-line tool. But if you want just these command-line tools, use the following links: Download SDK Platform-Tools for Windows Download SDK Platform-Tools for Mac Download SDK Platform-Tools for Linux Although these links do not change, they always point to the most recent version of the tools.

Revisions Fix track-devices duplicate entry. Add receive windowing increase throughput on high-latency connections. More specific error messages in the "more than one device" failure cases. Reject unexpected reverse forward requests. Fix install-multi-package on Windows. fastboot Remove e2fsdroid as part of SDK platform-tools. Print OemCmdHandler return message on success. Fixes "install multiple" on old devices Improves the help output to include all supported compression methods. systrace Removed. Known issue: this version crashes when run without any arguments. Fix bug in adb track-devices where devices over wireless debugging wouldn't immediately receive updates.

Implement preliminary support for mDNS device discovery without a separately installed mDNS service. fastboot Don't fail when unable to get boot partition size. Derive device locked state from property instead of parsing the kernel command line. Improve incremental installation performance. fastboot Add support for compressed snapshot merges. 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. fastboot Improve console output on fastboot oem commands. 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. Implement client-side support for compression of adb {push, pull, sync} when used with an Android 11 device. Improve performance of adb push on high-latency connections. Support listening on on POSIX. Client support for WinUSB devices that publish a WinUSB descriptor required for Android 11 should no longer require a USB driver to be installed. 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. log file. Fix devices going offline on Windows. Improve adb install output and help text. fastboot Adds support for partition layout of upcoming devices. 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. adb root waits for the device to reconnect after disconnecting. 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.

fastboot Disables an error message that occurred when fastboot attempted to open the touch bar or keyboard on macOS. 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. fastboot Adds support for dynamic partitions. Updated Windows requirements The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. If you see errors mentioning missing DLLs, you may need to manually fetch and install the runtime package. Upon disconnection, adb will attempt to reconnect for up to 60 seconds before abandoning a connection.

Fix Unicode console output on Windows. Thanks to external contributor Spencer Low! Fix a file descriptor double-close that can occur, resulting in connections being closed when an adb connect happens simultaneously. Fix adb forward --list when used with more than one device connected. fastboot Increase command timeout to 30 seconds, to better support some slow bootloader commands. Sort output of adb devices by connection type and device serial. Increase the socket listen backlog to allow for more simulataneous adb commands. Improve error output for adb connect. fastboot : Improve output format, add a verbose output mode -v. Clean up help output.

Disabling unwanted applications will reduce the load on the CPU and free up RAM. Some applications are poorly optimized. Uninstall them to increase your device battery lifetime! Make screenshots, change the screen resolution and hide the icons in the status bar. And not only. ADB AppControl - a new and handy desktop program, that will allow you to easily manage applications on your android device. You can disable unwanted pre-installed system apps and bloatware, or install new ones using a modern graphical interface. The program includes many useful tools and tweaks which allow you to get the better experience with your device.

This is exactly the tool that you will use for many years - after trying ADB AppControl you will see that working with applications via adb has never been so easy. System Requirements: Windows 7, 8, 8. NET Framework 4. There is no way to remove them without root privileges. These applications will not start and run - they are not installed for the operating system. By downloading and using the "ADB AppControl" software you acknowledge that you have read and agree to the Terms of Use and Privacy Policy. You have a completely list with all installed applications and you no longer need root rights to manage them! Uninstall, disable, and install apps. Manage permissions and configure your device the way you want it.

The ADB AppControl's Debloat Wizard offers several levels of unwanted application cleanup for beginners and advanced users. This will help improve the autonomy and performance of your Android device as well as secure your personal data. Change screen resolution, hide annoying icons in the status bar, take screenshots and remotely control your device. And if you haven't already forgotten about the command line, there's a handy console for you. ADB AppControl has many features that you will love! Become a project sponsor and get access to the Extended Version with new cool features.

Bloatware cleanup, interface theme selection, app batch installation and more now and in future updates! ADB AppControl Toggle navigation Home Documentation Download Extended Version. EN RU. App Control. Disable and uninstall applications without root Multiple apps installing Full Split Support APKS Saving APK files of installed applications Permissions Manager for applications Saving and loading applications list-presets Quick search for apps on Google Play, ApkMirror, F-Droid and others. Useful tools. Displaying device information Changing the screen resolution and DPI Hiding icons in the status bar Device remotely control Virtual volume, power, camera and navigation buttons Creating screenshots of the device screen Quick reboot in recovery and bootloader.

ADB Console with favorites commands Fastboot support Logcat logs Auto permission granting for popular apps Tasker, Battery Stats, etc. Simple file upload Extended Settings And many other features are now in the future! Get automatic installer or classic zip archive Download ADB AppControl 1. Download ACBridge. apk How to work with the program? Translations Checksums Changelog By downloading and using the "ADB AppControl" software you acknowledge that you have read and agree to the Terms of Use and Privacy Policy. Forget the command line! Bloatware cleanup The ADB AppControl's Debloat Wizard offers several levels of unwanted application cleanup for beginners and advanced users. More features Change screen resolution, hide annoying icons in the status bar, take screenshots and remotely control your device.

Want even more features? Support the project!

The output should include "libusb". Force-stop everything associated with package. That is, after the device is reset, the workstation can continue to debug and issue adb commands to the device without manually registering a new key. then you're ready to start using Android Debug Bridge from the command line! The default value is 4Mbps.

Categories:

• Soft
• Music
• Files
• Games
• Movies