Options: -g : Organize by group. Options: -f : List the APK file for the test package. Options: -r : Reinstall an existing app, keeping its data. This feature is only supported on certain devices. This option forces adb to use the feature or fail if it is not supported with verbose information on why it failed. Options: -k : Keep the data and cache directories around after package removal. On devices running Android 6. On devices running Android 5.
Location values: 0 : Auto: Let system decide the best location. Note: This is only intended for debugging; using this can cause apps to break and other undesireable behavior. To help you develop and test your device management or other enterprise apps, you can issue commands to the device policy manager dpm tool. Use the tool to control the active admin app or change a policy's status data on the device.
You can also issue a device policy manager command directly from adb without entering a remote shell:. You can also pass --user current to select the current user. The app must declare android:testOnly in the manifest. This command also removes device and profile owners. This is useful to avoid the device's scheduling restrictions when developing apps that manage freeze-periods. See Manage system updates. Supported on devices running Android 9. This command is rate-limited.
The screencap command is a shell utility for taking a screenshot of a device display. The utility records screen activity to an MPEG-4 file. You can use this file to create promotional or training videos or for debugging and testing. 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. The utility records at the native display resolution and orientation by default, with a maximum length of three minutes.
Table 5. Starting in Android 7. You might want to examine the collected profiles to understand which methods are determined to be frequently executed and which classes are used during app startup. If you test your app across multiple test devices, it may be useful to reset your device between tests, for example, to remove user data and reset the test environment. You can perform a factory reset of a test device running Android 10 API level 29 or higher using the testharness adb shell command, as shown below.
When restoring the device using testharness , the device automatically backs up the RSA key that allows debugging through the current workstation in a persistent location. 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. Additionally, to help make it easier and more secure to keep testing your app, using the testharness to restore a device also changes the following device settings:.
If you app needs to detect and adapt to the default settings of the testharness command, you can use the ActivityManager. It includes commands such as. You can also execute SQLite commands from the command line, as shown below. For more information, see the sqlite3 command line documentation. Content and code samples on this page are subject to the licenses described in the Content License.
Android Studio. Download What's new User guide Preview. Meet Android Studio. Manage your project. Write your app. Build and run your app. Run apps on the emulator. Run apps on a hardware device. Configure your build. Optimize your build speed. Debug your app. Test your app. Profile your app. Android Studio profilers. Profile CPU activity. Benchmark your app.
Measure performance. Publish your app. Command line tools. Android Developers. It is a client-server program that includes three components: A client , which sends commands. The client runs on your development machine. You can invoke a client from a command-line terminal by issuing an adb command. A daemon adbd , which runs commands on a device.
The daemon runs as a background process on each device. A server , which manages communication between the client and the daemon. The server runs as a background process on your development machine.
How adb works When you start an adb client, the client first checks whether there is an adb server process already running. For example: Emulator 1, console: Emulator 1, adb: Emulator 2, console: Emulator 2, adb: and so on Enable adb debugging on your device To use adb with a device connected over USB, you must enable USB debugging in the device system settings, under Developer options.
On some devices, the Developer options screen might be located or named differently. To connect to your device, follow these steps: Figure 1. Wireless ADB pairing dialog. Figure 2. Wireless adb IP and port number. Start an Activity specified by intent. Start the Service specified by intent. Force stop everything associated with package the app's package name. Kill all processes associated with package the app's package name. Issue a broadcast intent. Start monitoring with an Instrumentation instance.
Start profiler on process , write results to file. Dump the heap of process , write to file. Set app package to debug. Clear the package previous set for debugging with set-debug-app. Start monitoring for crashes or ANRs. Control screen compatibility mode of package. Override device display size. Example: am display-size x Override device display density. Example: am display-density Print the given intent specification as a URI.
Print the given intent specification as an intent: URI. Prints all packages, optionally only those whose package name contains the text in filter. Prints all known permissions, optionally only those in group.
List all test packages. Print the path to the APK of the given package. Installs a package specified by path to the system. Removes a package from the system. Grant a permission to an app.
Revoke a permission from an app. Changes the default install location. Returns the current install location. Return values: 0 [auto] : Lets system decide the best location 1 [internal] : Installs on internal device storage 2 [external] : Installs on external media.
Sets component as active admin. Sets component as active admin and its package as profile owner for an existing user. Sets component as active admin and its package as device owner. Disables an active admin. Clears the device's record of previously-set freeze periods for system OTA updates. Forces the system to make any existing network logs ready for retrieval by a DPC.
It is important that you get the right set of ADB drivers for your device. These drivers are very fickle, so it is always best to use the manufacturer built drivers for maximum compatibility.
Here we have a list of known ADB drivers for each manufacturer. While this extensive list should be able to provide the drivers you need for your device, there may be cases where you might have to go looking for your drivers manually. You can go search for it through your favorite search engine like Google to find the drivers.
If you are having troubles connecting even with the drivers installed, try restarting or reinstalling, then restarting your PC. Once you install KIES, you already have the drivers necessary for your device. Other devices like ZTE smartphones will have their download for the drivers only. They can be installed just like any other program, and then you can connect the device to your PC. Then again, other smartphones, especially those that use the basic, unadulterated version of Android, will have their drivers preinstalled if you install the Android SDK.
0コメント