am 181bb3aa: am 921c8a5d: am 4e483ed3: Merge "docs: misc bug fixes. including...

element as a child of <code>&lt;manifest&gt;</code>, as follows: </p>

<p style="margin-left:2em;"><code>&lt;uses-permission

android:name="com.android.vending.CHECK_LICENSE"&gt;</code></p>

android:name="com.android.vending.CHECK_LICENSE" /&gt;</code></p>

<p>For example, here's how the LVL sample application declares the permission:

</p>

system, add and track the sources that are in the working location rather

than those in default location in the SDK. </p>

<p>Moving the library sources is important is because, when you later update the

<p>Moving the library sources is important because when you later update the

Licensing package, the SDK installs the new files to the same location as

the older files. Moving your working library files to a safe location ensures

that your work won't be inadvertently overwritten should you download a new

defines a few helper methods, most notably {@code asInterface()}, which takes an {@link

android.os.IBinder} (usually the one passed to a client's {@link

android.content.ServiceConnection#onServiceConnected onServiceConnected()} callback method) and

returns an instance of the stub interface. See the section <a href="#calling">Calling an IPC

returns an instance of the stub interface. See the section <a href="#Calling">Calling an IPC

Method</a> for more details on how to make this cast.</p>

<p>To implement the interface generated from the {@code .aidl}, extend the generated {@link

// Specify arguments in placeholder order.

String[] selelectionArgs = { String.valueOf(rowId) };

// Issue SQL statement.

db.delete(table_name, mySelection, selectionArgs);

db.delete(table_name, selection, selectionArgs);

</pre>

  <dd>The <a href="{@docRoot}guide/topics/manifest/manifest-intro.html">manifest file</a> describes

the fundamental characteristics of the app and defines each of

its components. You'll learn about various declarations in this file as you read more training

classes.</dd>

classes.

  <p>One of the most important elements your manifest should include is the <a

href="{@docRoot}guide/topics/manifest/uses-sdk-element.html">{@code &lt;uses-sdk>}</a>

element. This declares your app's compatibility with different Android versions using the <a

href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#min">{@code android:minSdkVersion}</a>

and <a

href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#target">{@code android:targetSdkVersion}</a>

attributes. For your first app, it should look like this:</p>

<pre>

<manifest xmlns:android="http://schemas.android.com/apk/res/android" ... >

    <uses-sdk android:minSdkVersion="8" android:targetSdkVersion="17" />

    ...

</manifest>

</pre>

<p>You should always set the <a

href="{@docRoot}guide/topics/manifest/uses-sdk-element.html#target">{@code android:targetSdkVersion}</a>

as high as possible and test your app on the corresponding platform version. For more information,

read <a href="{@docRoot}training/basics/supporting-devices/platforms.html">Supporting Different

Platform Versions</a>.</p>

  </dd>

  <dt><code>src/</code></dt>

  <dd>Directory for your app's main source files. By default, it includes an {@link

android.app.Activity} class that runs when your app is launched using the app icon.</dd>