summaryrefslogtreecommitdiffstats
path: root/docs/html/tools/help/monitor.jd
blob: e1fe7721a1360c3ac67d30443c394e3a969e8944 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
page.title=Device Monitor
@jd:body

  <div id="qv-wrapper">
    <div id="qv">
      <h2>See also</h2>

      <ol>
        <li><a href="{@docRoot}tools/debugging/debugging-memory.html"
          >Investigating Your RAM Usage</a></li>
      </ol>
    </div>
  </div>


<p>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 a integrated development environment, such as Eclipse, and encapsulates the
following tools:</p>

<ul>
  <li><a href="{@docRoot}tools/debugging/ddms.html">DDMS</a></li>
  <li><a href="gltracer.html">Tracer for OpenGL ES</a></li>
  <li><a href="hierarchy-viewer.html">Hierarchy Viewer</a></li>
  <li><a href="traceview.html">Traceview</a></li>
  <li>Pixel Perfect magnification viewer</li>
</ul>


<h2 id="usage">Usage</h2>

<p>To start Device Monitor, enter the following command from the SDK <code>tools/</code>
directory:</p>
  <pre>monitor</pre>

<p>Start an Android emulator or connect an Android device via USB cable, and connect Device
Monitor to the device by selecting it in the <strong>Devices</strong> window.</p>

<p class="note"><strong>Note:</strong> Only one debugger can be connected to your device at a time.
If you're using ADT, you may need to close the debugging tool before launching the Device Monitor
in order for the device to be fully debuggable.</p>