81 lines
3.4 KiB
Plaintext
81 lines
3.4 KiB
Plaintext
page.title=<uses-permission>
|
|
@jd:body
|
|
|
|
<dl class="xml">
|
|
|
|
<div class="sidebox-wrapper">
|
|
<img id="rule" src="{@docRoot}assets/images/grad-rule-qv.png">
|
|
<div id="qv-sub-rule">
|
|
<img src="{@docRoot}assets/images/icon_market.jpg" style="float:left;margin:0;padding:0;">
|
|
<p style="color:#669999;"><code style="color:#669999;"><uses-permission></code> and filtering on Android Market. </p>
|
|
|
|
<p style="margin-top:1em;">In some cases, the permissions that you request
|
|
through <code><uses-permission></code> can affect how
|
|
your application is filtered by Android Market.</p>
|
|
|
|
<p style="margin-top:1em;">If you request a hardware-related permission —
|
|
<code>CAMERA</code>, for example — Android Market assumes that your
|
|
application requires the underlying hardware feature and filters the application
|
|
from devices that do not offer it.</p>
|
|
|
|
<p style="margin-top:1em;">To control filtering, always explicitly declare
|
|
hardware features in <code><uses-feature></code> elements, rather than
|
|
relying on Android Market to "discover" the requirements in
|
|
<code><uses-permission></code> elements. Then, if you want to disable
|
|
filtering for a particular feature, you can add a
|
|
<code>android:required="false"</code> attribute to the
|
|
<code><uses-feature></code> declaration.</p>
|
|
|
|
<p style="margin-top:1em;" class="caution">For a list of permissions that imply
|
|
hardware features, see the documentation for the <a
|
|
href="{@docRoot}guide/topics/manifest/uses-feature-element.html#permissions-features">
|
|
<code><uses-feature></code></a> element.</p>
|
|
</div>
|
|
</div>
|
|
|
|
|
|
<dt>syntax:</dt>
|
|
<dd><pre class="stx"><uses-permission android:<a href="#nm">name</a>="<i>string</i>" /></pre></dd>
|
|
|
|
<dt>contained in:</dt>
|
|
<dd><code><a href="{@docRoot}guide/topics/manifest/manifest-element.html"><manifest></a></code></dd>
|
|
|
|
<dt>description:</dt>
|
|
<dd>Requests a permission that the application must be granted in
|
|
order for it to operate correctly. Permissions are granted by the user when the
|
|
application is installed, not while it's running.
|
|
|
|
<p>
|
|
For more information on permissions, see the
|
|
<a href="{@docRoot}guide/topics/manifest/manifest-intro.html#perms">Permissions</a></code>
|
|
section in the introduction and the separate
|
|
<a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> document.
|
|
A list of permissions defined by the base platform can be found at
|
|
{@link android.Manifest.permission android.Manifest.permission}.
|
|
|
|
<dt>attributes:</dt>
|
|
<dd><dl class="attr">
|
|
<dt><a name="nm"></a>{@code android:name}</dt>
|
|
<dd>The name of the permission. It can be a permission defined by the
|
|
application with the <code><a href="{@docRoot}guide/topics/manifest/permission-element.html"><permission></a></code>
|
|
element, a permission defined by another application, or one of the
|
|
standard system permissions, such as "{@code android.permission.CAMERA}"
|
|
or "{@code android.permission.READ_CONTACTS}". As these examples show,
|
|
a permission name typically includes the package name as a prefix.</dd>
|
|
|
|
</dl></dd>
|
|
|
|
<!-- ##api level indication## -->
|
|
<dt>introduced in:</dt>
|
|
<dd>API Level 1</dd>
|
|
|
|
<dt>see also:</dt>
|
|
<dd>
|
|
<ul>
|
|
<li><code><a href="{@docRoot}guide/topics/manifest/permission-element.html"><permission></a></code></li>
|
|
<li><code><a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a></code></li>
|
|
</ul>
|
|
</dd>
|
|
|
|
</dl>
|