{
	"id": "c3e4e1e6-17cc-496a-8d6c-14c8cdc87b86",
	"created_at": "2026-04-06T00:16:24.111076Z",
	"updated_at": "2026-04-10T13:12:45.875248Z",
	"deleted_at": null,
	"sha1_hash": "261dde8dcf4a1047d0e9203f7b4732d8c7851b89",
	"title": "Android Debug Bridge (adb)",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 788546,
	"plain_text": "Android Debug Bridge (adb)\r\nArchived: 2026-04-05 23:48:27 UTC\r\nAndroid Debug Bridge ( adb ) is a versatile command-line tool that lets you communicate with a device. The\r\nadb command facilitates a variety of device actions, such as installing and debugging apps. adb provides\r\naccess to a Unix shell that you can use to run a variety of commands on a device. It is a client-server program that\r\nincludes three components:\r\nA client, which sends commands. The client runs on your development machine. You can invoke a client\r\nfrom a command-line terminal by issuing an adb command.\r\nA daemon (adbd), which runs commands on a device. The daemon runs as a background process on each\r\ndevice.\r\nA server, which manages communication between the client and the daemon. The server runs as a\r\nbackground process on your development machine.\r\nadb is included in the Android SDK Platform Tools package. Download this package with the SDK Manager,\r\nwhich installs it at android_sdk/platform-tools/ . If you want the standalone Android SDK Platform Tools\r\npackage, download it here.\r\nFor information on connecting a device for use over adb , including how to use the Connection Assistant to\r\ntroubleshoot common problems, see Run apps on a hardware device.\r\nHow adb works\r\nWhen you start an adb client, the client first checks whether there is an adb server process already running. If\r\nthere isn't, it starts the server process. When the server starts, it binds to local TCP port 5037 and listens for\r\ncommands sent from adb clients.\r\nNote: All adb clients use port 5037 to communicate with the adb server.\r\nThe server then sets up connections to all running devices. It locates emulators by scanning odd-numbered ports in\r\nthe range 5555 to 5585, which is the range used by the first 16 emulators. Where the server finds an adb daemon\r\n(adbd), it sets up a connection to that port.\r\nEach emulator uses a pair of sequential ports — an even-numbered port for console connections and an odd-numbered port for adb connections. For example:\r\nEmulator 1, console: 5554\r\nEmulator 1, adb : 5555\r\nEmulator 2, console: 5556\r\nEmulator 2, adb : 5557\r\nand so on.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 1 of 31\n\nAs shown, the emulator connected to adb on port 5555 is the same as the emulator whose console listens on port\r\n5554.\r\nOnce the server has set up connections to all devices, you can use adb commands to access those devices.\r\nBecause the server manages connections to devices and handles commands from multiple adb clients, you can\r\ncontrol any device from any client or from a script.\r\nEnable adb debugging on your device\r\nTo use adb with a device connected over USB, you must enable USB debugging in the device system settings,\r\nunder Developer options. On Android 4.2 (API level 17) and higher, the Developer options screen is hidden by\r\ndefault. To make it visible, enable Developer options.\r\nYou can now connect your device with USB. You can verify that your device is connected by executing adb\r\ndevices from the android_sdk/platform-tools/ directory. If connected, you'll see the device name listed as a\r\n\"device.\"\r\nNote: When you connect a device running Android 4.2.2 (API level 17) or higher, the system shows a dialog\r\nasking whether to accept an RSA key that allows debugging through this computer. This security mechanism\r\nprotects user devices because it ensures that USB debugging and other adb commands cannot be executed unless\r\nyou're able to unlock the device and acknowledge the dialog.\r\nFor more information about connecting to a device over USB, read Run apps on a hardware device.\r\nConnect to a device over Wi-Fi\r\nNote: The instructions below do not apply to Wear devices running Android 11 (API level 30). See the guide to\r\ndebugging a Wear OS app for more information.\r\nAndroid 11 (API level 30) and higher support deploying and debugging your app wirelessly from your\r\nworkstation using Android Debug Bridge (adb). For example, you can deploy your debuggable app to multiple\r\nremote devices without ever needing to physically connect your device via USB. This eliminates the need to deal\r\nwith common USB connection issues, such as driver installation.\r\nBefore you begin using wireless debugging, do the following:\r\nEnsure that your workstation and device are connected to the same wireless network.\r\nEnsure that your device is running Android 11 (API level 30) or higher for phone or Android 13 (API level\r\n33) or higher for TV and WearOS. For more information, see Check \u0026 update your Android version.\r\nIf using the IDE, ensure that you have the latest version of Android Studio installed. You can download it\r\nhere.\r\nOn your workstation, update to the latest version of the SDK Platform Tools.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 2 of 31\n\nTo use wireless debugging, you must pair your device to your workstation using a QR code or a pairing code.\r\nYour workstation and device must be connected to the same wireless network. To connect to your device, follow\r\nthese steps:\r\n1. Enable developer options on your device.\r\n2. Open Android Studio and select Pair Devices Using Wi-Fi from the run configurations menu.\r\nFigure 1. Run configurations menu.\r\nThe Pair devices over Wi-Fi window pops up, as shown in figure 2.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 3 of 31\n\nFigure 2. Popup window to pair devices using QR code or pairing code.\r\n3. On your device, tap Wireless debugging and pair your device:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 4 of 31\n\nFigure 3. Screenshot of the Wireless debugging setting on a Google Pixel phone.\r\n1. To pair your device with a QR code, select Pair device with QR code and scan the QR code\r\nobtained from the Pair devices over Wi-Fi popup shown in figure 2.\r\n2. To pair your device with a pairing code, select Pair device with pairing code from the Pair\r\ndevices 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\r\nselect Pair and enter the six-digit code shown on your device.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 5 of 31\n\nFigure 4. Example of six-digit code entry.\r\n4. After your device is paired, you can attempt to deploy your app to your device.\r\nTo pair a different device or to forget the current device on your workstation, navigate to Wireless\r\ndebugging on your device. Tap your workstation name under Paired devices and select Forget.\r\n5. If you want to quickly turn on and off wireless debugging, you can utilize the Quick settings developer tiles\r\nfor Wireless debugging, found in Developer Options \u003e Quick settings developer tiles.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 6 of 31\n\nFigure 5. The Quick settings developer tiles setting lets you quickly turn wireless\r\ndebugging on and off.\r\nWi-Fi connection using command line\r\nAlternatively, to connect to your device using command line without Android Studio, follow these steps:\r\n1. Enable developer options on your device, as described earlier.\r\n2. Enable Wireless debugging on your device, as described earlier.\r\n3. On your workstation, open a terminal window and navigate to android_sdk/platform-tools .\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 7 of 31\n\n4. Find your IP address, port number, and pairing code by selecting Pair device with pairing code. Take note\r\nof the IP address, port number, and pairing code displayed on the device.\r\n5. On your workstation's terminal, run adb pair ipaddr:port . Use the IP address and port number from\r\nabove.\r\n6. When prompted, enter the pairing code, as shown below.\r\nFigure 6. A message indicates that your device has been successfully paired.\r\nResolve wireless connection issues\r\nIf you are having issues connecting to your device wirelessly, try the following troubleshooting steps to resolve\r\nthe issue.\r\nCheck whether your workstation and device meet the prerequisites\r\nCheck that the workstation and device meet the prerequisites listed at the beginning of this section.\r\nCheck for other known issues\r\nThe following is a list of current known issues with wireless debugging (with adb or Android Studio) and how to\r\nresolve them:\r\nWi-Fi is not connecting: Secure Wi-Fi networks, such as corporate Wi-Fi networks, may block p2p\r\nconnections and not let you connect over Wi-Fi. Try connecting with a cable or another (non-corp) Wi-Fi\r\nnetwork. Wireless connection using adb connect ip:port over tcp/ip (following an initial USB\r\nconnection) is another option, in case resorting to a non-corp network is an option.\r\nadb over Wi-Fi sometimes turns off automatically: This can happen if the device either switches Wi-Fi\r\nnetworks or disconnects from the network. To resolve, re-connect to the network.\r\nDevice not connecting after pairing successfully: adb relies on mDNS to discover and automatically\r\nconnect to paired devices. If your network or device configuration does not support mDNS or has disabled\r\nit, then you need to manually connect to the device using adb connect ip:port .\r\nConnect wirelessly with a device after an initial USB connection (only option\r\navailable on Android 10 and lower)\r\nNote: This workflow is applicable also to Android 11 (and higher), the caveat being that it also involves an\r\n*initial* connection over physical USB.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 8 of 31\n\nNote: The following instructions do not apply to Wear devices running Android 10 (API level 29) or lower. See\r\nthe guide about debugging a Wear OS app for more information.\r\nadb usually communicates with the device over USB, but you can also use adb over Wi-Fi. To connect a\r\ndevice running Android 10 (API level 29) or lower, follow these initial steps over USB:\r\n1. Connect your Android device and adb host computer to a common Wi-Fi network.\r\nNote: Beware that not all access points are suitable. You might need to use an access point whose firewall\r\nis configured properly to support adb .\r\n2. Connect the device to the host computer with a USB cable.\r\n3. Set the target device to listen for a TCP/IP connection on port 5555:\r\nadb tcpip 5555\r\n4. Disconnect the USB cable from the target device.\r\n5. Find the IP address of the Android device. For example, on a Nexus device, you can find the IP address at\r\nSettings \u003e About tablet (or About phone) \u003e Status \u003e IP address.\r\n6. Connect to the device by its IP address:\r\nadb connect device_ip_address:5555\r\n7. Confirm that your host computer is connected to the target device:\r\n$ adb devices\r\nList of devices attached\r\ndevice_ip_address:5555 device\r\nYour device is now connected to adb .\r\nIf the adb connection to your device is lost:\r\nMake sure that your host is still connected to the same Wi-Fi network as your Android device.\r\nReconnect by executing the adb connect step again.\r\nIf that doesn't work, reset your adb host:\r\nadb kill-server\r\nThen start over from the beginning.\r\nQuery for devices\r\nBefore issuing adb commands, it is helpful to know what device instances are connected to the adb server.\r\nGenerate a list of attached devices using the devices command:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 9 of 31\n\nadb devices -l\r\n \r\nIn response, adb prints this status information for each device:\r\nSerial number: adb creates a string to uniquely identify the device by its port number. Here's an example\r\nserial number: emulator-5554\r\nState: The connection state of the device can be one of the following:\r\noffline : The device is not connected to adb or is not responding.\r\ndevice : The device is connected to the adb server. Note that this state does not imply that the\r\nAndroid system is fully booted and operational, because the device connects to adb while the\r\nsystem is still booting. After boot-up, this is the normal operational state of a device.\r\nno device : There is no device connected.\r\nDescription: If you include the -l option, the devices command tells you what the device is. This\r\ninformation is helpful when you have multiple devices connected so that you can tell them apart.\r\nThe following example shows the devices command and its output. There are three devices running. The first\r\ntwo lines in the list are emulators, and the third line is a hardware device that is attached to the computer.\r\n$ adb devices\r\nList of devices attached\r\nemulator-5556 device product:sdk_google_phone_x86_64 model:Android_SDK_built_for_x86_64 device:generi\r\nemulator-5554 device product:sdk_google_phone_x86 model:Android_SDK_built_for_x86 device:generic_x86\r\n0a388e93 device usb:1-1 product:razor model:Nexus_7 device:flo\r\nEmulator not listed\r\nThe adb devices command has a corner-case command sequence that causes running emulators to not show up\r\nin the adb devices output even though the emulators are visible on your desktop. This happens when all of the\r\nfollowing conditions are true:\r\nThe adb server is not running.\r\nYou use the emulator command with the -port or -ports option with an odd-numbered port value\r\nbetween 5554 and 5584.\r\nThe odd-numbered port you chose is not busy, so the port connection can be made at the specified port\r\nnumber — or, if it is busy, the emulator switches to another port that meets the requirements in 2.\r\nYou start the adb server after you start the emulator.\r\nOne way to avoid this situation is to let the emulator choose its own ports and to run no more than 16 emulators at\r\nonce. Another way is to always start the adb server before you use the emulator command, as explained in the\r\nfollowing examples.\r\nExample 1: In the following command sequence, the adb devices command starts the adb server, but the list\r\nof devices does not appear.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 10 of 31\n\nStop the adb server and enter the following commands in the order shown. For the AVD name, provide a valid\r\nAVD name from your system. To get a list of AVD names, type emulator -list-avds . The emulator command\r\nis in the android_sdk/tools directory.\r\n$ adb kill-server\r\n$ emulator -avd Nexus_6_API_25 -port 5555\r\n$ adb devices\r\nList of devices attached\r\n* daemon not running. starting it now on port 5037 *\r\n* daemon started successfully *\r\nExample 2: In the following command sequence, adb devices displays the list of devices because the adb\r\nserver was started first.\r\nTo see the emulator in the adb devices output, stop the adb server, and then start it again after using the\r\nemulator command and before using the adb devices command, as follows:\r\n$ adb kill-server\r\n$ emulator -avd Nexus_6_API_25 -port 5557\r\n$ adb start-server\r\n$ adb devices\r\nList of devices attached\r\nemulator-5557 device\r\nFor more information about emulator command-line options, see Command-Line startup options.\r\nSend commands to a specific device\r\nIf multiple devices are running, you must specify the target device when you issue the adb command. To specify\r\nthe target, follow these steps:\r\n1. Use the devices command to get the serial number of the target.\r\n2. Once you have the serial number, use the -s option with the adb commands to specify the serial\r\nnumber.\r\n1. If you're going to issue a lot of adb commands, you can set the $ANDROID_SERIAL environment\r\nvariable to contain the serial number instead.\r\n2. If you use both -s and $ANDROID_SERIAL , -s overrides $ANDROID_SERIAL .\r\nIn the following example, the list of attached devices is obtained, and then the serial number of one of the devices\r\nis used to install the helloWorld.apk on that device:\r\n$ adb devices\r\nList of devices attached\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 11 of 31\n\nemulator-5554 device\r\nemulator-5555 device\r\n0.0.0.0:6520 device\r\n# To install on emulator-5555\r\n$ adb -s emulator-5555 install helloWorld.apk\r\n# To install on 0.0.0.0:6520\r\n$ adb -s 0.0.0.0:6520 install helloWorld.apk\r\nNote: If you issue a command without specifying a target device when multiple devices are available, adb\r\ndisplays an error \"adb: more than one device/emulator\".\r\nIf you have multiple devices available but only one is an emulator, use the -e option to send commands to the\r\nemulator. If there are multiple devices but only one hardware device attached, use the -d option to send\r\ncommands to the hardware device.\r\nInstall an app\r\nYou can use adb to install an APK on an emulator or connected device with the install command:\r\nadb install path_to_apk\r\nYou must use the -t option with the install command when you install a test APK. For more information,\r\nsee -t .\r\nTo install multiple APKs use install-multiple . This is useful if you download all the APKs for a specific\r\ndevice for your app from the Play Console and want to install them on an emulator or physical device.\r\nFor more information about how to create an APK file that you can install on an emulator/device instance, see\r\nBuild and run your app.\r\nNote: If you are using Android Studio, you do not need to use adb directly to install your app on the emulator or\r\ndevice. Instead, Android Studio handles the packaging and installation of the app for you.\r\nSet up port forwarding\r\nUse the forward command to set up arbitrary port forwarding, which forwards requests on a specific host port to\r\na different port on a device. The following example sets up forwarding of host port 6100 to device port 7100:\r\nadb forward tcp:6100 tcp:7100\r\nThe following example sets up forwarding of host port 6100 to local:logd:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 12 of 31\n\nadb forward tcp:6100 local:logd\r\nThis could be useful if you are trying to detemine what is being sent to a given port on the device. All received\r\ndata will be written to the system-logging daemon and displayed in the device logs.\r\nCopy files to and from a device\r\nUse the pull and push commands to copy files to and from a device. Unlike the install command, which\r\nonly copies an APK file to a specific location, the pull and push commands let you copy arbitrary directories\r\nand files to any location in a device.\r\nTo copy a file or directory and its sub-directories from the device, do the following:\r\nadb pull remote local\r\nTo copy a file or directory and its sub-directories to the device, do the following:\r\nadb push local remote\r\nReplace local and remote with the paths to the target files/directory on your development machine (local) and\r\non the device (remote). For example:\r\nadb push myfile.txt /sdcard/myfile.txt\r\nStop the adb server\r\nIn some cases, you might need to terminate the adb server process and then restart it to resolve the problem. For\r\nexample, this could be the case if adb does not respond to a command.\r\nTo stop the adb server, use the adb kill-server command. You can then restart the server by issuing any other\r\nadb command.\r\nIssue adb commands\r\nIssue adb commands from a command line on your development machine or from a script using the following:\r\nadb [-d | -e | -s serial_number] command\r\nIf there's only one emulator running or only one device connected, the adb command is sent to that device by\r\ndefault. If multiple emulators are running and/or multiple devices are attached, you need to use the -d , -e , or\r\n-s option to specify the target device to which the command should be directed.\r\nYou can see a detailed list of all supported adb commands using the following command:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 13 of 31\n\nadb --help\r\nIssue shell commands\r\nYou can use the shell command to issue device commands through adb or to start an interactive shell. To\r\nissue a single command, use the shell command like this:\r\nadb [-d |-e | -s serial_number] shell shell_command\r\nTo start an interactive shell on a device, use the shell command like this:\r\nadb [-d | -e | -s serial_number] shell\r\nTo exit an interactive shell, press Control+D or type exit .\r\nAndroid provides most of the usual Unix command-line tools. For a list of available tools, use the following\r\ncommand:\r\nadb shell ls /system/bin\r\nHelp is available for most of the commands via the --help argument. Many of the shell commands are provided\r\nby toybox. General help applicable to all toybox commands is available via toybox --help .\r\nWith Android Platform Tools 23 and higher, adb handles arguments the same way that the ssh(1) command\r\ndoes. This change has fixed a lot of problems with command injection and makes it possible to safely execute\r\ncommands that contain shell metacharacters, such as adb install Let\\'sGo.apk . This change means that the\r\ninterpretation of any command that contains shell metacharacters has also changed.\r\nFor example, adb shell setprop key 'two words' is now an error, because the quotes are swallowed by the\r\nlocal shell, and the device sees adb shell setprop key two words . To make the command work, quote twice,\r\nonce for the local shell and once for the remote shell, as you do with ssh(1) . For example, adb shell setprop\r\nkey \"'two words'\" works because the local shell takes the outer level of quoting and the device still sees the\r\ninner level of quoting: setprop key 'two words' . Escaping is also an option, but quoting twice is usually easier.\r\nSee also Logcat command-line tool, which is useful for monitoring the system log.\r\nCall activity manager\r\nWithin an adb shell, you can issue commands with the activity manager ( am ) tool to perform various system\r\nactions, such as start an activity, force-stop a process, broadcast an intent, modify the device screen properties, and\r\nmore.\r\nWhile in a shell, the am syntax is:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 14 of 31\n\nam command\r\nYou can also issue an activity manager command directly from adb without entering a remote shell. For\r\nexample:\r\nadb shell am start -a android.intent.action.VIEW\r\nTable 1. Available activity manager commands\r\nCommand Description\r\nstart [options]\r\nintent\r\nStart an Activity specified by intent .\r\nSee the Specification for intent arguments.\r\nOptions are:\r\n-D : Enable debugging.\r\n-W : Wait for launch to complete.\r\n--start-profiler file : Start profiler and send results to file .\r\n-P file : Like --start-profiler , but profiling stops when the app goes\r\nidle.\r\n-R count : Repeat the activity launch count times. Prior to each repeat,\r\nthe top activity will be finished.\r\n-S : Force stop the target app before starting the activity.\r\n--opengl-trace : Enable tracing of OpenGL functions.\r\n--user user_id | current : Specify which user to run as; if not specified,\r\nthen run as the current user.\r\nstartservice\r\n[options] intent\r\nStart the Service specified by intent .\r\nSee the Specification for intent arguments.\r\nOptions are:\r\n--user user_id | current : Specify which user to run as. If not specified,\r\nthen run as the current user.\r\nforce-stop\r\npackage\r\nForce-stop everything associated with package .\r\nkill [options]\r\npackage\r\nKill all processes associated with package . This command kills only processes that\r\nare safe to kill and that will not impact the user experience.\r\nOptions are:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 15 of 31\n\n--user user_id | all | current : Specify which user's processes to kill. If\r\nnot specified, then kill all users' processes.\r\nkill-all Kill all background processes.\r\nbroadcast\r\n[options] intent\r\nIssue a broadcast intent.\r\nSee the Specification for intent arguments.\r\nOptions are:\r\n[--user user_id | all | current] : Specify which user to send to. If not\r\nspecified, then send to all users.\r\ninstrument\r\n[options]\r\ncomponent\r\nStart monitoring with an Instrumentation instance. Typically the target\r\ncomponent is the form test_package/runner_class .\r\nOptions are:\r\n-r : Print raw results (otherwise decode report_key_streamresult ). Use\r\nwith [-e perf true] to generate raw output for performance\r\nmeasurements.\r\n-e name value : Set argument name to value . For test runners a common\r\nform is -e testrunner_flag value[,value...] .\r\n-p file : Write profiling data to file .\r\n-w : Wait for instrumentation to finish before returning. Required for test\r\nrunners.\r\n--no-window-animation : Turn off window animations while running.\r\n--user user_id | current : Specify which user instrumentation runs in. If\r\nnot specified, run in the current user.\r\nprofile start\r\nprocess file\r\nStart profiler on process , write results to file .\r\nprofile stop\r\nprocess\r\nStop profiler on process .\r\ndumpheap [options]\r\nprocess file\r\nDump the heap of process , write to file .\r\nOptions are:\r\n--user [user_id | current] : When supplying a process name, specify the\r\nuser of the process to dump. If not specified, the current user is used.\r\n-b [| png | jpg | webp] : Dump bitmaps from graphics memory (API\r\nlevel 35 and above). Optionally specify the format to dump in (PNG by\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 16 of 31\n\ndefault).\r\n-n : Dump native heap instead of managed heap.\r\ndumpbitmaps\r\n[options] [-p\r\nprocess]\r\nDump bitmap information from process (API level 36 and above).\r\nOptions are:\r\n-d|--dump [format] : dump bitmap contents in the specified format ,\r\nwhich can be one of png , jpg , or webp , default to png if none is\r\nspecified. A zip file dumpbitmaps-\u003ctime\u003e.zip will be created with the\r\nbitmaps.\r\n-p process : dump bitmaps from process , multiple -p process can be\r\nspecified.\r\nIf no process is specified, bitmaps from all processes will be dumped.\r\nset-debug-app\r\n[options] package\r\nSet app package to debug.\r\nOptions are:\r\n-w : Wait for debugger when app starts.\r\n--persistent : Retain this value.\r\nclear-debug-app Clear the package previous set for debugging with set-debug-app .\r\nmonitor [options]\r\nStart monitoring for crashes or ANRs.\r\nOptions are:\r\n--gdb : Start gdbserv on the given port at crash/ANR.\r\nscreen-compat {on\r\n| off} package\r\nControl screen compatibility mode of package .\r\ndisplay-size\r\n[reset |\r\nwidthxheight]\r\nOverride device display size. This command is helpful for testing your app across\r\ndifferent screen sizes by mimicking a small screen resolution using a device with a\r\nlarge screen, and vice versa.\r\nExample:\r\nam display-size 1280x800\r\ndisplay-density\r\ndpi\r\nOverride device display density. This command is helpful for testing your app across\r\ndifferent screen densities by mimicking a high-density screen environment using a\r\nlow-density screen, and vice versa.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 17 of 31\n\nExample:\r\nam display-density 480\r\nto-uri intent\r\nPrint the given intent specification as a URI.\r\nSee the Specification for intent arguments.\r\nto-intent-uri\r\nintent\r\nPrint the given intent specification as an intent: URI.\r\nSee the Specification for intent arguments.\r\nSpecification for intent arguments\r\nFor activity manager commands that take an intent argument, you can specify the intent with the following\r\noptions:\r\nShow all\r\n-a action\r\nSpecify the intent action, such as android.intent.action.VIEW . You can declare this only once.\r\n-d data_uri\r\nSpecify the intent data URI, such as content://contacts/people/1 . You can declare this only once.\r\n-t mime_type\r\nSpecify the intent MIME type, such as image/png . You can declare this only once.\r\n-c category\r\nSpecify an intent category, such as android.intent.category.APP_CONTACTS .\r\n-n component\r\nSpecify the component name with package name prefix to create an explicit intent, such as\r\ncom.example.app/.ExampleActivity .\r\n-f flags\r\nAdd flags to the intent, as supported by setFlags() .\r\n--esn extra_key\r\nAdd a null extra. This option is not supported for URI intents.\r\n-e | --es extra_key extra_string_value\r\nAdd string data as a key-value pair.\r\n--ez extra_key extra_boolean_value\r\nAdd boolean data as a key-value pair.\r\n--ei extra_key extra_int_value\r\nAdd integer data as a key-value pair.\r\n--el extra_key extra_long_value\r\nAdd long data as a key-value pair.\r\n--ef extra_key extra_float_value\r\nAdd float data as a key-value pair.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 18 of 31\n\n--eu extra_key extra_uri_value\r\nAdd URI data as a key-value pair.\r\n--ecn extra_key extra_component_name_value\r\nAdd a component name, which is converted and passed as a ComponentName object.\r\n--eia extra_key extra_int_value[,extra_int_value...]\r\nAdd an array of integers.\r\n--ela extra_key extra_long_value[,extra_long_value...]\r\nAdd an array of longs.\r\n--efa extra_key extra_float_value[,extra_float_value...]\r\nAdd an array of floats.\r\n--grant-read-uri-permission\r\nInclude the flag FLAG_GRANT_READ_URI_PERMISSION .\r\n--grant-write-uri-permission\r\nInclude the flag FLAG_GRANT_WRITE_URI_PERMISSION .\r\n--debug-log-resolution\r\nInclude the flag FLAG_DEBUG_LOG_RESOLUTION .\r\n--exclude-stopped-packages\r\nInclude the flag FLAG_EXCLUDE_STOPPED_PACKAGES .\r\n--include-stopped-packages\r\nInclude the flag FLAG_INCLUDE_STOPPED_PACKAGES .\r\n--activity-brought-to-front\r\nInclude the flag FLAG_ACTIVITY_BROUGHT_TO_FRONT .\r\n--activity-clear-top\r\nInclude the flag FLAG_ACTIVITY_CLEAR_TOP .\r\n--activity-clear-when-task-reset\r\nInclude the flag FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET .\r\n--activity-exclude-from-recents\r\nInclude the flag FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS .\r\n--activity-launched-from-history\r\nInclude the flag FLAG_ACTIVITY_LAUNCHED_FROM_HISTORY .\r\n--activity-multiple-task\r\nInclude the flag FLAG_ACTIVITY_MULTIPLE_TASK .\r\n--activity-no-animation\r\nInclude the flag FLAG_ACTIVITY_NO_ANIMATION .\r\n--activity-no-history\r\nInclude the flag FLAG_ACTIVITY_NO_HISTORY .\r\n--activity-no-user-action\r\nInclude the flag FLAG_ACTIVITY_NO_USER_ACTION .\r\n--activity-previous-is-top\r\nInclude the flag FLAG_ACTIVITY_PREVIOUS_IS_TOP .\r\n--activity-reorder-to-front\r\nInclude the flag FLAG_ACTIVITY_REORDER_TO_FRONT .\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 19 of 31\n\n--activity-reset-task-if-needed\r\nInclude the flag FLAG_ACTIVITY_RESET_TASK_IF_NEEDED .\r\n--activity-single-top\r\nInclude the flag FLAG_ACTIVITY_SINGLE_TOP .\r\n--activity-clear-task\r\nInclude the flag FLAG_ACTIVITY_CLEAR_TASK .\r\n--activity-task-on-home\r\nInclude the flag FLAG_ACTIVITY_TASK_ON_HOME .\r\n--receiver-registered-only\r\nInclude the flag FLAG_RECEIVER_REGISTERED_ONLY .\r\n--receiver-replace-pending\r\nInclude the flag FLAG_RECEIVER_REPLACE_PENDING .\r\n--selector\r\nRequires the use of -d and -t options to set the intent data and type.\r\nURI component package\r\nYou can directly specify a URI, package name, and component name when not qualified by one of the\r\npreceding options. When an argument is unqualified, the tool assumes the argument is a URI if it contains a\r\n\":\" (colon). The tools assumes the argument is a component name if it contains a \"/\" (forward-slash);\r\notherwise it assumes the argument is a package name.\r\nCall package manager ( pm )\r\nWithin an adb shell, you can issue commands with the package manager ( pm ) tool to perform actions and\r\nqueries on app packages installed on the device.\r\nWhile in a shell, the pm syntax is:\r\npm command\r\nYou can also issue a package manager command directly from adb without entering a remote shell. For example:\r\nadb shell pm uninstall com.example.MyApp\r\nTable 2. Available package manager commands\r\nCommand Description\r\nlist packages [options]\r\nfilter\r\nPrint all packages, optionally only those whose package name contains the\r\ntext in filter .\r\nOptions:\r\n-f : See associated file.\r\n-d : Filter to only show disabled packages.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 20 of 31\n\n-e : Filter to only show enabled packages.\r\n-s : Filter to only show system packages.\r\n-3 : Filter to only show third-party packages.\r\n-i : See the installer for the packages.\r\n-u : Include uninstalled packages.\r\n--user user_id : The user space to query.\r\nlist permission-groups Print all known permission groups.\r\nlist permissions\r\n[options] group\r\nPrint all known permissions, optionally only those in group .\r\nOptions:\r\n-g : Organize by group.\r\n-f : Print all information.\r\n-s : Short summary.\r\n-d : Only list dangerous permissions.\r\n-u : List only the permissions users will see.\r\nlist instrumentation\r\n[options]\r\nList all test packages.\r\nOptions:\r\n-f : List the APK file for the test package.\r\ntarget_package : List test packages for only this app.\r\nlist features Print all features of the system.\r\nlist libraries Print all the libraries supported by the current device.\r\nlist users Print all users on the system.\r\npath package Print the path to the APK of the given package .\r\ninstall [options] path Install a package, specified by path , to the system.\r\nOptions:\r\n-r : Reinstall an existing app, keeping its data.\r\n-t : Allow test APKs to be installed. Gradle generates a test APK\r\nwhen you have only run or debugged your app or have used the\r\nAndroid Studio Build \u003e Build APK command. If the APK is built\r\nusing a developer preview SDK, you must include the -t option\r\nwith the install command if you are installing a test APK.\r\n-i installer_package_name : Specify the installer package name.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 21 of 31\n\n--user user_id : Specify the user to install the package for. By\r\ndefault, the package is installed for all users existing on the device.\r\n--install-location location : Set the install location using one of\r\nthe following values:\r\n0 : Use the default install location.\r\n1 : Install on internal device storage.\r\n2 : Install on external media.\r\n-f : Install package on the internal system memory.\r\n-d : Allow version code downgrade.\r\n-g : Grant all permissions listed in the app manifest.\r\n--fastdeploy : Quickly update an installed package by only\r\nupdating the parts of the APK that changed.\r\n--incremental : Installs enough of the APK to launch the app while\r\nstreaming the remaining data in the background. To use this feature,\r\nyou must sign the APK, create an APK Signature Scheme v4 file, and\r\nplace this file in the same directory as the APK. This feature is only\r\nsupported on certain devices. This option forces adb to use the\r\nfeature or fail if it is not supported, with verbose information on why\r\nit failed. Append the --wait option to wait until the APK is fully\r\ninstalled before granting access to the APK.\r\n--no-incremental prevents adb from using this feature.\r\nuninstall [options]\r\npackage\r\nRemoves a package from the system.\r\nOptions:\r\n-k : Keep the data and cache directories after package removal.\r\n--user user_id : Specifies the user for whom the package is\r\nremoved. By default, the package is removed for all users on the\r\ndevice.\r\n--versionCode version_code : Only uninstalls if the app has the\r\ngiven version code.\r\nclear package Delete all data associated with a package.\r\nenable\r\npackage_or_component\r\nEnable the given package or component (written as \"package/class\").\r\ndisable\r\npackage_or_component\r\nDisable the given package or component (written as \"package/class\").\r\ndisable-user [options]\r\npackage_or_component\r\nOptions:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 22 of 31\n\n--user user_id : The user to disable.\r\ngrant package_name\r\npermission\r\nGrant a permission to an app. On devices running Android 6.0 (API level 23)\r\nand higher, the permission can be any permission declared in the app\r\nmanifest. On devices running Android 5.1 (API level 22) and lower, must be\r\nan optional permission defined by the app.\r\nrevoke package_name\r\npermission\r\nRevoke a permission from an app. On devices running Android 6.0 (API\r\nlevel 23) and higher, the permission can be any permission declared in the\r\napp manifest. On devices running Android 5.1 (API level 22) and lower,\r\nmust be an optional permission defined by the app.\r\nset-install-location\r\nlocation\r\nChange the default install location. Location values:\r\n0 : Auto: Let system decide the best location.\r\n1 : Internal: Install on internal device storage.\r\n2 : External: Install on external media.\r\nNote: This is only intended for debugging. Using this can cause apps to\r\nbreak and other undesireable behavior.\r\nget-install-location\r\nReturns the current install location. Return values:\r\n0 [auto] : Let system decide the best location\r\n1 [internal] : Install on internal device storage\r\n2 [external] : Install on external media\r\nset-permission-enforced\r\npermission [true | false]\r\nSpecify whether the given permission should be enforced.\r\ntrim-caches\r\ndesired_free_space\r\nTrim cache files to reach the given free space.\r\ncreate-user user_name\r\nCreate a new user with the given user_name , printing the new user\r\nidentifier of the user.\r\nremove-user user_id\r\nRemove the user with the given user_id , deleting all data associated with\r\nthat user\r\nget-max-users Print the maximum number of users supported by the device.\r\nget-app-links [options]\r\n[package]\r\nPrint the domain verification state for the given package, or for all packages\r\nif none is specified. State codes are defined as follows:\r\nnone : nothing has been recorded for this domain\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 23 of 31\n\nverified : the domain has been successfully verified\r\napproved : force-approved, usually through shell\r\ndenied : force-denied, usually through shell\r\nmigrated : preserved verification from a legacy response\r\nrestored : preserved verification from a user data restore\r\nlegacy_failure : rejected by a legacy verifier, unknown reason\r\nsystem_configured : automatically approved by the device config\r\n\u003e= 1024 : custom error code, which is specific to the device verifier\r\nOptions are:\r\n--user user_id : include user selections. Include all domains, not\r\njust autoVerify ones.\r\nreset-app-links [options]\r\n[package]\r\nReset domain verification state for the given package, or for all packages if\r\nnone is specified.\r\npackage : the package to reset, or \"all\" to reset all packages\r\nOptions are:\r\n--user user_id : include user selections. Include all domains, not\r\njust autoVerify ones.\r\nverify-app-links [--re-verify] [package]\r\nBroadcast a verification request for the given package, or for all packages if\r\nnone is specified. Only sends if the package has previously not recorded a\r\nresponse.\r\n--re-verify : send even if the package has recorded a response\r\nset-app-links [--package\r\npackage] state domains\r\nManually set the state of a domain for a package. The domain must be\r\ndeclared by the package as autoVerify for this to work. This command will\r\nnot report a failure for domains that could not be applied.\r\n--package package : the package to set, or \"all\" to set all packages\r\nstate : the code to set the domains to. Valid values are:\r\nSTATE_NO_RESPONSE (0) : reset as if no response was ever\r\nrecorded.\r\nSTATE_SUCCESS (1) : treat domain as successfully verified by\r\ndomain verification agent. Note that the domain verification\r\nagent can override this.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 24 of 31\n\nSTATE_APPROVED (2) : treat domain as always approved,\r\npreventing the domain verification agent from changing it.\r\nSTATE_DENIED (3) : treat domain as always denied,\r\npreventing the domain verification agent from changing it.\r\ndomains : space-separated list of domains to change, or \"all\" to\r\nchange every domain.\r\nset-app-links-user-selection --user user_id\r\n[--package package]\r\nenabled domains\r\nManually set the state of a host user selection for a package. The domain\r\nmust be declared by the package for this to work. This command will not\r\nreport a failure for domains that could not be applied.\r\n--user user_id : the user to change selections for\r\n--package package : the package to set\r\nenabled : whether to approve the domain\r\ndomains : space-separated list of domains to change, or \"all\" to\r\nchange every domain\r\nset-app-links-allowed --\r\nuser user_id [--package\r\npackage] allowed\r\nToggle the auto-verified link-handling setting for a package.\r\n--user user_id : the user to change selections for\r\n--package package : the package to set, or \"all\" to set all packages;\r\npackages will be reset if no package is specified\r\nallowed : true to allow the package to open auto-verified links, false\r\nto disable\r\nget-app-link-owners --\r\nuser user_id [--package\r\npackage] domains\r\nPrint the owners for a specific domain for a given user in low- to high-priority order.\r\n--user user_id : the user to query for\r\n--package package : optionally also print for all web domains\r\ndeclared by a package, or \"all\" to print all packages\r\ndomains : space-separated list of domains to query for\r\nCall device policy manager ( dpm )\r\nTo help you develop and test your device management apps, issue commands to the device policy manager ( dpm )\r\ntool. Use the tool to control the active admin app or change a policy's status data on the device.\r\nWhile in a shell, the dpm syntax is:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 25 of 31\n\ndpm command\r\nYou can also issue a device policy manager command directly from adb without entering a remote shell:\r\nadb shell dpm command\r\nTable 3. Available device policy manager commands\r\nCommand Description\r\nset-active-admin\r\n[options]\r\ncomponent\r\nSets component as active admin.\r\nOptions are:\r\n--user user_id : Specify the target user. You can also pass --user\r\ncurrent to select the current user.\r\nset-profile-owner\r\n[options]\r\ncomponent\r\nSet component as active admin and its package as profile owner for an existing user.\r\nOptions are:\r\n--user user_id : Specify the target user. You can also pass --user\r\ncurrent to select the current user.\r\n--name name : Specify the human-readable organization name.\r\nset-device-owner\r\n[options]\r\ncomponent\r\nSet component as active admin and its package as device owner.\r\nOptions are:\r\n--user user_id : Specify the target user. You can also pass --user\r\ncurrent to select the current user.\r\n--name name : Specify the human-readable organization name.\r\nremove-active-admin [options]\r\ncomponent\r\nDisable an active admin. The app must declare android:testOnly in the manifest.\r\nThis command also removes device and profile owners.\r\nOptions are:\r\n--user user_id : Specify the target user. You can also pass --user\r\ncurrent to select the current user.\r\nclear-freeze-period-recordClear the device's record of previously set freeze periods for system OTA updates.\r\nThis is useful to avoid the device scheduling restrictions when developing apps that\r\nmanage freeze periods. See Manage system updates.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 26 of 31\n\nSupported on devices running Android 9.0 (API level 28) and higher.\r\nforce-network-logs\r\nForce the system to make any existing network logs ready for retrieval by a DPC. If\r\nthere are connection or DNS logs available, the DPC receives the\r\nonNetworkLogsAvailable() callback. See Network activity logging.\r\nThis command is rate-limited. Supported on devices running Android 9.0 (API level\r\n28) and higher.\r\nforce-security-logs\r\nForce the system to make any existing security logs available to the DPC. If there are\r\nlogs available, the DPC receives the onSecurityLogsAvailable() callback. See Log\r\nenterprise device activity.\r\nThis command is rate-limited. Supported on devices running Android 9.0 (API level\r\n28) and higher.\r\nTake a screenshot\r\nThe screencap command is a shell utility for taking a screenshot of a device display.\r\nWhile in a shell, the screencap syntax is:\r\nscreencap filename\r\nTo use screencap from the command line, enter the following:\r\nadb shell screencap /sdcard/screen.png\r\nHere's an example screenshot session, using the adb shell to capture the screenshot and the pull command to\r\ndownload the file from the device:\r\n$ adb shell\r\nshell@ $ screencap /sdcard/screen.png\r\nshell@ $ exit\r\n$ adb pull /sdcard/screen.png\r\nAlternatively, if you omit the filename, screencap writes the image to standard output. When combined with the\r\n-p option to specify PNG format, you can stream the device screenshot directly to a file on your local machine.\r\nHere's an example of capturing a screenshot and saving it locally in a single command:\r\n# use 'exec-out' instead of 'shell' to get raw data\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 27 of 31\n\n$ adb exec-out screencap -p \u003e screen.png\r\nRecord a video\r\nThe screenrecord command is a shell utility for recording the display of devices running Android 4.4 (API level\r\n19) and higher. The utility records screen activity to an MPEG-4 file. You can use this file to create promotional or\r\ntraining videos or for debugging and testing.\r\nIn a shell, use the following syntax:\r\nscreenrecord [options] filename\r\nTo use screenrecord from the command line, enter the following:\r\nadb shell screenrecord /sdcard/demo.mp4\r\nStop the screen recording by pressing Control+C. Otherwise, the recording stops automatically at three minutes or\r\nthe time limit set by --time-limit .\r\nTo begin recording your device screen, run the screenrecord command to record the video. Then, run the pull\r\ncommand to download the video from the device to the host computer. Here's an example recording session:\r\n$ adb shell\r\nshell@ $ screenrecord --verbose /sdcard/demo.mp4\r\n(press Control + C to stop)\r\nshell@ $ exit\r\n$ adb pull /sdcard/demo.mp4\r\nThe screenrecord utility can record at any supported resolution and bit rate you request, while retaining the\r\naspect ratio of the device display. The utility records at the native display resolution and orientation by default,\r\nwith a maximum length of three minutes.\r\nLimitations of the screenrecord utility:\r\nAudio is not recorded with the video file.\r\nVideo recording is not available for devices running Wear OS.\r\nSome devices might not be able to record at their native display resolution. If you encounter problems with\r\nscreen recording, try using a lower screen resolution.\r\nRotation of the screen during recording is not supported. If the screen does rotate during recording, some of\r\nthe screen is cut off in the recording.\r\nTable 4. screenrecord options\r\nOptions Description\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 28 of 31\n\n--help Display command syntax and options\r\n--size\r\nwidthxheight\r\nSet the video size: 1280x720 . The default value is the device's native display resolution\r\n(if supported), 1280x720 if not. For best results, use a size supported by your device's\r\nAdvanced Video Coding (AVC) encoder.\r\n--bit-rate\r\nrate\r\nSet the video bit rate for the video, in megabits per second. The default value is 20Mbps.\r\nYou can increase the bit rate to improve video quality, but doing so results in larger movie\r\nfiles. The following example sets the recording bit rate to 6Mbps:\r\nscreenrecord --bit-rate 6000000 /sdcard/demo.mp4\r\n--time-limit\r\ntime\r\nSet the maximum recording time, in seconds. The default and maximum value is 180 (3\r\nminutes).\r\n--rotate Rotate the output 90 degrees. This feature is experimental.\r\n--verbose\r\nDisplay log information on the command-line screen. If you do not set this option, the\r\nutility does not display any information while running.\r\nRead ART profiles for apps\r\nStarting in Android 7.0 (API level 24), the Android Runtime (ART) collects execution profiles for installed apps,\r\nwhich are used to optimize app performance. Examine the collected profiles to understand which methods are\r\nexecuted frequently and which classes are used during app startup.\r\nNote: It is only possible to retrieve the execution profile filename if you have root access to the file system, for\r\nexample, on an emulator.\r\nTo produce a text form of the profile information, use the following command:\r\nadb shell cmd package dump-profiles package\r\nTo retrieve the file produced, use:\r\nadb pull /data/misc/profman/package.prof.txt\r\nReset test devices\r\nIf you test your app across multiple test devices, it may be useful to reset your device between tests, for example,\r\nto remove user data and reset the test environment. You can perform a factory reset of a test device running\r\nAndroid 10 (API level 29) or higher using the testharness adb shell command, as shown:\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 29 of 31\n\nadb shell cmd testharness enable\r\nWhen restoring the device using testharness , the device automatically backs up the RSA key that allows\r\ndebugging through the current workstation in a persistent location. That is, after the device is reset, the\r\nworkstation can continue to debug and issue adb commands to the device without manually registering a new\r\nkey.\r\nAdditionally, to help make it easier and more secure to keep testing your app, using the testharness to restore a\r\ndevice also changes the following device settings:\r\nThe device sets up certain system settings so that initial device setup wizards do not appear. That is, the\r\ndevice enters a state from which you can quickly install, debug, and test your app.\r\nSettings:\r\nDisables lock screen.\r\nDisables emergency alerts.\r\nDisables auto-sync for accounts.\r\nDisables automatic system updates.\r\nOther:\r\nDisables preinstalled security apps.\r\nIf your app needs to detect and adapt to the default settings of the testharness command, use the\r\nActivityManager.isRunningInUserTestHarness() .\r\nsqlite\r\nsqlite3 starts the sqlite command-line program for examining SQLite databases. It includes commands such\r\nas .dump to print the contents of a table and .schema to print the SQL CREATE statement for an existing table.\r\nYou can also execute SQLite commands from the command line, as shown:\r\n$ adb -s emulator-5554 shell\r\n$ sqlite3 /data/data/com.example.app/databases/rssitems.db\r\nSQLite version 3.3.12\r\nEnter \".help\" for instructions\r\nNote: It is only possible to access a SQLite database if you have root access to the file system, for example, on an\r\nemulator.\r\nFor more information, see the sqlite3 command line documentation.\r\nadb USB backends\r\nThe adb server can interact with the USB stack through two backends. It can either use the native backend of the\r\nOS (Windows, Linux, or macOS) or it can use the libusb backend. Some features, such as attach , detach ,\r\nand USB speed detection, are only available when using libusb backend.\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 30 of 31\n\nYou can choose a backend by using the ADB_LIBUSB environment variable. If it isn't set, adb uses its default\r\nbackend. The default behavior varies among OS. Starting with ADB v34, the liubusb backend is used by default\r\non all OS except Windows, where the native backend is used by default. If ADB_LIBUSB is set, it determines\r\nwhether the native backend or libusb is used. See the adb manual page for more information about adb\r\nenvironment variables.\r\nadb mDNS backends\r\nADB can use the multicast DNS protocol to automatically connect the server and devices. The ADB server ships\r\nwith two backends, Bonjour (Apple's mdnsResponder) and Openscreen.\r\nThe Bonjour backend needs a daemon to be running on the host machine. On macOS Apple's built-in daemon is\r\nalways running, but on Windows and Linux, the user must make sure the mdnsd daemon is up and running. If the\r\ncommand adb mdns check returns an error, it is likely that ADB is using the Bonjour backend but there is no\r\nBonjour daemon running.\r\nThe Openscreen backend does not need a daemon to be running on the machine. Support for the Openscreen\r\nbackend on macOS starts at ADB v35. Windows and Linux are supported as of ADB v34.\r\nBy default ADB uses the Bonjour backend. This behavior can be changed using the environment variable\r\nADB_MDNS_OPENSCREEN (set to 1 or 0 ). See the ADB manual page for further details.\r\nadb Burst Mode (starting with ADB 36.0.0)\r\nBurst Mode is an experimental feature that lets ADB to keep on sending packets to a device even before the device\r\nhas responded to the previous packet. This greatly increases the throughput of ADB when transferring large files\r\nand also reduces latency while debugging.\r\nBurst Mode is disabled by default. To enable the feature, do one of the following:\r\nSet the environment variable ADB_BURST_MODE to 1 .\r\nIn Android Studio, go to the debugger settings at File (or Android Studio on macOS) \u003e Settings \u003e Build,\r\nExecution, Deployment \u003e Debugger and set ADB Server Burst Mode to Enabled.\r\nSource: https://developer.android.com/studio/command-line/adb\r\nhttps://developer.android.com/studio/command-line/adb\r\nPage 31 of 31",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://developer.android.com/studio/command-line/adb"
	],
	"report_names": [
		"adb"
	],
	"threat_actors": [],
	"ts_created_at": 1775434584,
	"ts_updated_at": 1775826765,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/261dde8dcf4a1047d0e9203f7b4732d8c7851b89.pdf",
		"text": "https://archive.orkl.eu/261dde8dcf4a1047d0e9203f7b4732d8c7851b89.txt",
		"img": "https://archive.orkl.eu/261dde8dcf4a1047d0e9203f7b4732d8c7851b89.jpg"
	}
}