Android Device Monitor was deprecated in Android Studio 3.1 and removed from Android Studio 3.2. The features that you could use through the Android Device Monitor have been replaced by new features. The table below helps you decide which features you should use instead of these deprecated and removed features.
|Android Device Monitor component||What you should use|
|Dalvik Debug Monitor Server (DDMS)||
This tool is deprecated. Instead, use Android Profiler in Android Studio 3.0 and higher to profile your app's CPU, memory, and network usage.
If you want to perform other debugging tasks, such as sending commands
to a connected device to set up port-forwarding, transfer files, or
take screenshots, then use the
Android Debug Bridge (
This tool is deprecated. To inspect
If you need to inspect native system processes and address UI
jank caused by dropped frames, use
|Tracer for OpenGL ES||Use the Android GPU Inspector.|
If you want to inspect your app's view hierarchy at runtime, use Layout Inspector.
If you want to profile the rendering speed of your app's layout, use Window.OnFrameMetricsAvailableListener as described in this blog post.
|Pixel Perfect||Use Layout Inspector.|
|Network Traffic tool||
If you need to view how and when your app transfers data over a network, use the Network Profiler.
Start Android Device Monitor
To start the standalone Device Monitor application in Android Studio 3.1 and
lower, enter the following on the command line in the
You can then link the tool to a connected device by selecting the device from the Devices pane. If you have trouble viewing panes or windows, select Window > Reset Perspective from the menu bar.
Note: Each device can be attached to only one debugger process at a time. So, for example, if you are using Android Studio to debug your app on a device, you need to disconnect the Android Studio debugger from the device before you attach a debugger process from the Android Device Monitor.