docs: InfoPros, Project 01, Batch 02

    <dt id="adb">adb</dt>

    <dd>Android Debug Bridge, a command-line debugging application included with the

        SDK. It provides tools to browse the device, copy tools on the device, and

        forward ports for debugging. If you are developing in Eclipse using the

		ADT Plugin, adb is integrated into your development environment. See 

        forward ports for debugging. If you are developing in Android Studio, 

        adb is integrated into your development environment. See 

		<a href="{@docRoot}tools/help/adb.html">Android Debug Bridge</a>

		for more information. </dd>

    <dt id="ddms">DDMS</dt>

    <dd>Dalvik Debug Monitor Service, a GUI debugging application included

    with the SDK. It provides screen capture, log dump, and process

    examination capabilities. If you are developing in Eclipse using the ADT

    Plugin, DDMS is integrated into your development environment. See <a

    examination capabilities. If you are developing in Android Studio, 

    DDMS is integrated into your development environment. See <a

    href="{@docRoot}tools/debugging/ddms.html">Using DDMS</a> to learn more about the program.</dd>

    <dt id="dialog">Dialog</dt> <dd> A floating window that acts as a lightweight

you're using the emulator, since the emulator uses your desktop computer's

network connection. That's almost guaranteed to be much faster than a cell

network, so you'll want to change the settings on the emulator that simulate

slower network speeds. You can do this in Eclipse, in the "Emulator Settings"

tab of your launch configuration or via a <a

slower network speeds. You can do this in Android Studio via the AVD Manager, 

or via a <a

href="{@docRoot}tools/help/emulator.html#netspeed">command-line 

option</a> when starting the emulator.</p>

<ol>

<li>On your device, connect to wireless (<strong>Settings > Wireless & networks

> Wi-Fi > Wi-Fi settings</strong>)</li>

> Wi-Fi > Wi-Fi settings</strong>).</li>

<li>Set up your mobile device for testing, as described in <a

href="{@docRoot}tools/device.html">Developing on a Device</a>.</li>

<li>Run your application on your mobile device, as described in <a

href="{@docRoot}tools/device.html">Developing on a Device</a>.</li>

<li>If you are using Eclipse, you can view the application log output in Eclipse

using LogCat (<strong>Window > Show View > Other > Android >

LogCat</strong>).</li>

<li>If you are using Android Studio, you can view the application log output by

opening the Event Log console (<strong>View > Tool Windows > Event Log</strong>). 

<li>Ensure your application is configured to launch Logcat automatically when it runs: 

<ol TYPE=a>

<li>Select <strong>Run > Edit Configurations</strong>.

<li>Select the <strong>Miscellaneous</strong> tab in the <strong>Run/Debug Configurations</strong> window.

<li>Under <strong>Logcat</strong>, select <strong>Show logcat automatically</strong> then

select <strong>OK</strong>.</li></ol>

</ol>

<ol>

<li>First, build and export your application as an unsigned <code>.apk</code>.

If you are developing in Eclipse with ADT, right-click the project and select

<strong>Android Tools</strong> &gt; <strong>Export Unsigned Application

Package</strong>. Select a destination filename and path and click

<strong>OK</strong>. </li>

If you are developing in Android Studio, build your application with Gradle:

<ol TYPE=a>

<li>Open the project and select <strong>Run > Edit Configurations</strong>.

<li>Select the plus sign near the top-left corner of the <strong>Run/Debug

Configurations</strong> window.

<li>Select <strong>Gradle.</strong>

<li>Enter <code>Unsigned APK</code> in <strong>Name</strong>.

<li>Choose your module from the <strong>Gradle project</strong> section.

<li>Enter <code>assemble</code> in <strong>Tasks</strong>.

<li>Select <strong>OK</strong> to complete the new configuration.

<li>Make sure the <strong>Unsigned APK</strong> run configuration is selected

in the toolbar and select <strong>Run > Run 'Unsigned APK'</strong>.</li>

</ol>

You can find your unsigned <code>.apk</code> in the

<code>&lt;<em>ProjectName</em>&gt;/app/build/outputs/apk/</code> directory.

<li>Next, locate the <code>aapt</code> tool, if it is not already in your PATH.

If you are using SDK Tools r8 or higher, you can find <code>aapt</code> in the

<code>&lt;<em>SDK</em>&gt;/platform-tools/</code> directory.

       <td rowspan="6">Camera</td>

       <td><code>android.hardware.camera</code></td>

       <td>The application uses the device's back-facing (main) camera.</td>

       <td>Devices with only a front-facing camera do not list this feature, so the 

           <code>android.hardware.camera.any</code> feature should be

           used instead if a camera facing any direction is acceptable for the

       <td>Devices with only a front-facing camera do not list this feature, so

           the <code>android.hardware.camera.any</code> feature should be used

           instead if a camera facing any direction is acceptable for the

           application.</td>

    </tr>

<tr>

    A contract class also helps developers because it usually has mnemonic names for its constants,

    so developers are less likely to use incorrect values for column names or URIs. Since it's a

    class, it can contain Javadoc documentation. Integrated development environments such as

    Eclipse can auto-complete constant names from the contract class and display Javadoc for the

    constants.

    Android Studio can auto-complete constant names from the contract class and display Javadoc for 

    the constants.

</p>

<p>

    Developers can't access the contract class's class file from your application, but they can