| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | uses-feature-element.jd | 1 page.title=<uses-feature>
12 <li><a href="#market-feature-filtering">Google Play and Feature-Based Filtering</a>
16 <li><a href="#bt-permission-handling">Special handling for Bluetooth feature</a></li>
35 <p style="padding-top:1em;">Google Play uses the <code><uses-feature></code>
37 that do not meet it's hardware and software feature requirements. </p>
41 devices meet the application's feature requirements, rather than presenting it
46 href="#market-feature-filtering">Google Play and Feature-Based Filtering</a>,
55 <pre class="stx"><uses-feature
66 <dd>Declares a single hardware or software feature that is used by the
69 <p>The purpose of a <code><uses-feature></code> declaration is to inform
[all …]
|
| D | uses-permission-element.jd | 19 application requires the underlying hardware feature and filters the application
23 hardware features in <code><uses-feature></code> elements, rather than
26 filtering for a particular feature, you can add a
28 <code><uses-feature></code> declaration.</p>
32 href="{@docRoot}guide/topics/manifest/uses-feature-element.html#permissions-features">
33 <code><uses-feature></code></a> element.</p>
76 …<li><code><a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature>…
|
| /frameworks/base/docs/html/guide/practices/ |
| D | compatibility.jd | 20 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></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><uses-feature></code><…
114 feature compatibility. To do this, Google Play checks the
115 <code><uses-feature></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>,
[all …]
|
| /frameworks/base/docs/html/training/tv/ |
| D | unsupported-features-tv.jd | 39 <th>Android feature descriptor</th>
91 <uses-feature android:name="android.hardware.touchscreen" android:required="false"/>
130 To check if a feature is available at runtime, call
133 feature you want to check. For example, to check for touchscreen, use
142 // Check if android.hardware.telephony feature is available.
145 // Check if android.hardware.touchscreen feature is available.
|
| /frameworks/base/core/java/android/net/ |
| D | ConnectivityManager.java | 505 public int startUsingNetworkFeature(int networkType, String feature) { in startUsingNetworkFeature() argument
507 return mService.startUsingNetworkFeature(networkType, feature, in startUsingNetworkFeature()
527 public int stopUsingNetworkFeature(int networkType, String feature) { in stopUsingNetworkFeature() argument
529 return mService.stopUsingNetworkFeature(networkType, feature); in stopUsingNetworkFeature()
|
| D | IConnectivityManager.aidl | 61 int startUsingNetworkFeature(int networkType, in String feature, in startUsingNetworkFeature() argument
64 int stopUsingNetworkFeature(int networkType, in String feature); in stopUsingNetworkFeature() argument
|
| D | EthernetDataTracker.java | 310 public int startUsingNetworkFeature(String feature, int callingPid, int callingUid) { in startUsingNetworkFeature() argument
327 public int stopUsingNetworkFeature(String feature, int callingPid, int callingUid) { in stopUsingNetworkFeature() argument
|
| /frameworks/base/services/java/com/android/server/ |
| D | ConnectivityService.java | 1016 FeatureUser(int type, String feature, IBinder binder) { in FeatureUser() argument
1019 mFeature = feature; in FeatureUser()
1058 public boolean isSameUser(int pid, int uid, int networkType, String feature) { in isSameUser() argument
1060 TextUtils.equals(mFeature, feature)) { in isSameUser()
1073 public int startUsingNetworkFeature(int networkType, String feature, in startUsingNetworkFeature() argument
1080 log("startUsingNetworkFeature for net " + networkType + ": " + feature + ", uid=" in startUsingNetworkFeature()
1090 FeatureUser f = new FeatureUser(networkType, feature, binder); in startUsingNetworkFeature()
1093 int usedNetworkType = convertFeatureToNetworkType(networkType, feature); in startUsingNetworkFeature()
1122 if (!TextUtils.equals(feature,Phone.FEATURE_ENABLE_DUN_ALWAYS)) { in startUsingNetworkFeature()
1184 feature); in startUsingNetworkFeature()
[all …]
|
| /frameworks/wilhelm/tests/sandbox/ |
| D | engine.c | 87 options[0].feature = 0x12345; in main()
105 options[0].feature = SL_ENGINEOPTION_THREADSAFE; in main()
107 options[1].feature = SL_ENGINEOPTION_LOSSOFCONTROL; in main()
|
| /frameworks/base/docs/html/google/play/ |
| D | filters.jd | 37 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a></code></l…
206 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
215 </strong>The manifest includes <code><uses-feature
220 </strong>The manifest does not include a <code><uses-feature></code>
224 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
228 <code><uses-permission></code> elements as feature requirements equivalent
229 to those declared in <code><uses-feature></code> elements. See <a
240 OpenGL-ES version using the <code><uses-feature
259 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code><…
279 elements to determine whether the application has hardware feature requirements
[all …]
|
| /frameworks/base/docs/html/distribute/googleplay/quality/ |
| D | tablet.jd | 14 <li><a href="#offer-full-feature-set">7. Offer the app's full feature set</a></li>
35 you focus on key aspects of quality, feature set, and UI that can have a
359 <h2 id="offer-full-feature-set">7. Offer the app's full feature set to tablet users</h2>
380 <li>If you will omit a feature or capability from your tablet UI, make sure
382 to a replacement feature (also see the section below on hardware features).</li>
399 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature></code><…
412 href="{@docRoot}guide/topics/manifest/uses-feature-element.html#permissions">imply
413 feature requirements</a> that might not be appropriate for tablets, except when
414 accompanied by a corresponding <code><uses-feature></code> element
428 <li><strong><a href="{@docRoot}guide/topics/manifest/uses-feature-element.html#permissions">Permiss…
[all …]
|
| /frameworks/wilhelm/src/ |
| D | entry.c | 63 switch (option->feature) { in liCreateEngine()
72 option->feature, option->data); in liCreateEngine()
|
| /frameworks/compile/libbcc/lib/Renderscript/runtime/ |
| D | build_bc_lib.mk | 22 bc_clang_cc1_cflags := -target-feature +long64
|
| /frameworks/base/docs/html/guide/topics/media/ |
| D | camera.jd | 34 <li><a href="#check-feature">Checking feature availability</a></li>
65 questions about how your app intends to use this hardware feature.</p>
76 <a href="#intents">Using Existing Camera Apps</a>. For developing a customized camera feature, check
129 <uses-feature android:name="android.hardware.camera" />
132 <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html#hw-features">Features
136 specify. For more information about using feature-based filtering with Google Play, see <a
137 href="{@docRoot}guide/topics/manifest/uses-feature-element.html#market-feature-filtering">Google
139 <p>If your application <em>can use</em> a camera or camera feature for proper operation, but does
143 <uses-feature android:name="android.hardware.camera" android:required="false" />
1102 camera parameters object, follow the links in the feature list below to the API reference
[all …]
|
| /frameworks/base/core/java/android/bluetooth/ |
| D | BluetoothTetheringDataTracker.java | 180 public int startUsingNetworkFeature(String feature, int callingPid, int callingUid) { in startUsingNetworkFeature() argument
197 public int stopUsingNetworkFeature(String feature, int callingPid, int callingUid) { in stopUsingNetworkFeature() argument
|
| /frameworks/base/docs/html/training/ |
| D | index.jd | 3 …Each class explains the steps required to solve a problem or implement a feature using code snippe…
|
| /frameworks/base/docs/html/training/basics/firstapp/ |
| D | creating-project.jd | 78 that allows your app to provide its core feature set. If any feature of your app is possible
79 only on newer versions of Android and it's not critical to the app's core feature set, you
80 can enable the feature only when running on the versions that support it (as
|
| /frameworks/base/docs/html/guide/topics/connectivity/ |
| D | sip.jd | 126 feature is supported only on Android 2.3 (API level 9) and higher versions of
155 <li><code><uses-feature android:name="android.hardware.sip.voip"
159 not offer SIP support. Other <code><uses-feature></code> declarations
162 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-
163 feature></a> element.</li>
185 …<uses-feature android:name="android.hardware.sip.voip" android:required="true&qu…
186 …<uses-feature android:name="android.hardware.wifi" android:required="true" …
187 …<uses-feature android:name="android.hardware.microphone" android:required="true&…
|
| /frameworks/base/docs/html/training/camera/ |
| D | videobasics.jd | 55 {@code <uses-feature>} tag in the manifest file:</p>
59 <uses-feature android:name="android.hardware.camera" />
|
| /frameworks/base/docs/html/guide/topics/connectivity/usb/ |
| D | index.jd | 44 "{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a> element. See
|
| /frameworks/base/docs/html/training/multiple-apks/ |
| D | texture.jd | 280 uses-feature:'android.hardware.telephony'
281 uses-feature:'android.hardware.touchscreen'
290 supports-screens and compatible-screens, and that you don’t have unintended "uses-feature" values
293 <p>Why? By adding the required permission SEND_SMS, the feature requirement of android.hardware.te…
297 <uses-feature android:name="android.hardware.telephony" android:required="false" />
301 <uses-feature android:name="android.hardware.touchscreen" android:required="false" />
|
| D | api.jd | 361 uses-feature:'android.hardware.telephony'
362 uses-feature:'android.hardware.touchscreen'
371 supports-screens and compatible-screens, and that you don’t have unintended "uses-feature" values
374 <p>Why? By adding the required permission SEND_SMS, the feature requirement of android.hardware.te…
378 <uses-feature android:name="android.hardware.telephony" android:required="false" />
382 <uses-feature android:name="android.hardware.touchscreen" android:required="false" />
|
| D | screensize.jd | 335 uses-feature:'android.hardware.telephony'
336 uses-feature:'android.hardware.touchscreen'
345 supports-screens and compatible-screens, and that you don’t have unintended "uses-feature" values
348 <p>Why? By adding the required permission SEND_SMS, the feature requirement of android.hardware.te…
353 <uses-feature android:name="android.hardware.telephony" android:required="false" />
357 <uses-feature android:name="android.hardware.touchscreen" android:required="false" />
|
| /frameworks/base/docs/html/tools/testing/ |
| D | testing_accessibility.jd | 156 the Explore by Touch system feature. The TalkBack accessibility service comes preinstalled on most
159 Play</a>. The Explore by Touch system feature is available on devices running Android 4.0 and later.
186 <p>The <em>Explore by Touch</em> system feature is available on devices running Android 4.0 and
188 around the interface of an application and hear the contents of the screen spoken. This feature
243 <li>Enable both TalkBack and the Explore by Touch feature as described in the
|
| /frameworks/base/docs/html/guide/topics/text/ |
| D | index.jd | 15 <p>A new feature available in Android 4.0 is voice typing: the difference for users is that
|