Lines Matching refs:feature

20 href="{@docRoot}guide/topics/manifest/uses-feature-element.html">&lt;uses-feature&gt;</a></code></l…
64 corresponding hardware or feature. But that’s not a problem: we also designed
80 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code>&lt;uses-feature&gt;</code><…
114 feature compatibility. To do this, Google Play checks the
115 <code>&lt;uses-feature&gt;</code> elements in each application's manifest, to
116 establish the app's feature needs. Google Play then shows or hides the application to
129 Wallpapers. However, not every device will support every feature. For instance,
133 <p>To manage this, Android defines <em>feature IDs</em>. Every capability has a
134 corresponding feature ID defined by the Android platform. For instance, the
135 feature ID for compass is <code>“android.hardware.sensor.compass”</code>, 
136 while the feature
140 feature is supported at runtime. As Android adds support for new features in
141 future versions, new feature IDs will be added as well.</p>
144 by listing their feature IDs in <code>&lt;uses-feature&gt;</code> elements in
194 introduces a new feature or changes how existing features are handled, what
213 devices, such as set-top boxes. Android 2.2 included a new feature ID for the
216 assumed to require the microphone feature by default. If your app can use a