diff --git a/docs/html/tools/debugging/ddms.jd b/docs/html/tools/debugging/ddms.jd index 28ad11e14f56f..becbdb1fe7325 100644 --- a/docs/html/tools/debugging/ddms.jd +++ b/docs/html/tools/debugging/ddms.jd @@ -22,28 +22,23 @@ parent.link=index.html
  • Using LogCat
  • Emulating phone operations and location
    • - + -

    Android ships with a debugging tool called the Dalvik Debug Monitor Server (DDMS), which +

    Android Studio includes a debugging tool called the Dalvik Debug Monitor Server (DDMS), which provides port-forwarding services, screen capture on the device, thread and heap information on the device, logcat, process, and radio state information, incoming call and SMS spoofing, location data spoofing, and more. This page provides a modest discussion of DDMS features; it is not an exhaustive exploration of all the features and capabilities.

    - +

    Running DDMS

    -

    DDMS is integrated into Eclipse and is also shipped in the tools/ directory of the - SDK. DDMS works with both the emulator and a connected device. If both are connected and running simultaneously, - DDMS defaults to the emulator.

    - - +

    DDMS is integrated into Android Studio. To use it, launch the + Android Device Monitor, and click the + DDMS menu button. DDMS works with both the emulator and a + connected device. If both are connected and running simultaneously, DDMS defaults to the emulator.

    How DDMS Interacts with a Debugger

    @@ -70,7 +65,7 @@ parent.link=index.html all the VMs on a device. The traffic that is forwarded is determined by the currently selected process in the DDMS Devices view.

    -

    The following screenshot shows a typical DDMS screen in Eclipse. If you are starting DDMS from +

    The following screenshot shows a typical DDMS screen. If you are starting DDMS from the command line, the screen is slightly different, but much of the functionality is identical. Notice that the highlighted process, com.android.email, that is running in the emulator has the debugging port 8700 assigned to it as well as 8606. This signifies that DDMS is currently @@ -78,10 +73,10 @@ parent.link=index.html -

    Figure 1. - Screenshot of DDMS

    +

    Figure 1. + Screenshot of DDMS

    -

    If you are not using Eclipse and ADT, read If you are using the command line, read Configuring your IDE to attach to the debugging port, for more information on attaching your debugger.

    @@ -97,11 +92,11 @@ parent.link=index.html

    Using DDMS

    The following sections describe how to use DDMS and the various tabs and panes that are part of the - DDMS GUI. The Eclipse version and the command line version have minor UI differences, but the - same functionality. For information on running DDMS, see the previous section in this document, + DDMS GUI. The Android Studio version and the command line version have minor UI differences, but + the same functionality. For information on running DDMS, see the previous section in this document, Running DDMS. - - + +

    Viewing heap usage for a process

    DDMS allows you to view how much heap memory a process is using. This information is useful in @@ -129,7 +124,7 @@ parent.link=index.html objects are being allocated when you perform certain actions in your application. This information is valuable for assessing memory usage that can affect application performance.

    - +

    To track memory allocation of objects:

    1. In the Devices tab, select the process that you want to enable allocation tracking @@ -155,7 +150,7 @@ parent.link=index.html

      DDMS provides a File Explorer tab that allows you to view, copy, and delete files on the device. This feature is useful in examining files that are created by your application or if you want to transfer files to and from the device.

      - +

      To work with an emulator or device's file system:

      1. In the Devices tab, select the emulator that you want to view the file system for.
        2. @@ -166,7 +161,7 @@ parent.link=index.html
      2. To copy a file to the device, click the Push file button on the File Explorer tab.
      - + @@ -189,7 +184,7 @@ parent.link=index.html where profiling data is collected, use the {@link android.os.Debug#startMethodTracing()} and {@link android.os.Debug#stopMethodTracing()} methods. For more information about generating trace logs, see Profiling and Debugging UIs.

      - +

      Before you start method profiling in DDMS, be aware of the following restrictions:

      - +

      To start method profiling:

      1. On the Devices tab, select the process that you want to enable method profiling for.
        2. @@ -218,7 +213,7 @@ parent.link=index.html

      Using the Network Traffic tool

      - +

      In Android 4.0, the DDMS (Dalvik Debug Monitor Server) includes a Detailed Network Usage tab that makes it possible to track when your application is making network requests. Using this tool, you can monitor how and when your app @@ -274,7 +269,7 @@ to clear the tag.

      Socket tagging is supported in Android 4.0, but real-time stats will only be displayed on devices running Android 4.0.3 or higher.

      - +

      Using LogCat

      LogCat is integrated into DDMS, and outputs the messages that you print out using the {@link android.util.Log} @@ -296,7 +291,7 @@ displayed on devices running Android 4.0.3 or higher.

    2. Error
      3. - +

      You can also setup your own custom filter to specify more details such as filtering messages with the log tags or with the process id that generated the log message. The add filter, edit filter, and delete filter buttons let you manage your custom filters.

      @@ -351,7 +346,7 @@ displayed on devices running Android 4.0.3 or higher.

    3. KML - Keyhole Markup Language file
      4. - + For more information about providing mock location data, see Location Strategies. diff --git a/docs/html/tools/debugging/debugging-tracing.jd b/docs/html/tools/debugging/debugging-tracing.jd index fa5b4e1254bce..829c82a19fc7f 100644 --- a/docs/html/tools/debugging/debugging-tracing.jd +++ b/docs/html/tools/debugging/debugging-tracing.jd @@ -177,12 +177,15 @@ adb pull /sdcard/calc.trace /tmp

      Viewing Trace Files in Traceview

      -

      To run Traceview and view the trace files, enter traceview - <trace-base-name>. For example, to run Traceview on the example files copied in the - previous section, use:

      - 
      -traceview /tmp/calc
-
      +

      To run Traceview and view the trace files:

      +

      Note: If you are trying to view the trace logs of an application that is built with ProGuard enabled (release mode build), some method and member names might be obfuscated. diff --git a/docs/html/tools/help/monitor.jd b/docs/html/tools/help/monitor.jd index 513eb10b8b060..5f7b5ce9a19b0 100644 --- a/docs/html/tools/help/monitor.jd +++ b/docs/html/tools/help/monitor.jd @@ -15,8 +15,8 @@ page.title=Device Monitor

      Android Device Monitor is a stand-alone tool that provides a graphical user interface for several Android application debugging and analysis tools. The Monitor tool does not -require installation of an integrated development environment, such as Eclipse, and encapsulates the -following tools:

      +require installation of an integrated development environment, such as Android Studio, and +encapsulates the following tools:

    +

    To start the Traceview tool:

    -

    For more information on how to use Traceview, see -Profiling with Traceview and dmtracedump +

    + + +

    For more information on how to use Traceview, see +Profiling with Traceview and +dmtracedump.

    +

    Note: Running traceview from the command line +has been deprecated.

    + +