| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | uses-feature-element.jd | 1 page.title=<uses-feature>
11 <li><a href="#market-feature-filtering">Google Play and Feature-Based Filtering</a>
15 <li><a href="#bt-permission-handling">Special handling for Bluetooth feature</a></li>
34 <p style="padding-top:1em;">Google Play uses the <code><uses-feature></code>
36 that do not meet it's hardware and software feature requirements. </p>
40 devices meet the application's feature requirements, rather than presenting it
45 href="#market-feature-filtering">Google Play and Feature-Based Filtering</a>,
54 <pre class="stx"><uses-feature
65 <dd itemprop="description">Declares a single hardware or software feature that is used by the
68 <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>
102 …<li><code><a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature>…
|
| D | uses-permission-sdk-23-element.jd | 30 feature that requires an additional permission. If a user updates an app on a
33 update. If a new feature is minor enough, you may prefer to disable
34 the feature altogether on those devices, so the user does not have to grant
92 …<li><code><a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature>…
|
| /frameworks/base/docs/html-intl/intl/ja/training/tv/start/ |
| D | hardware.jd | 106 <uses-feature android:name="android.hardware.touchscreen"
108 <uses-feature android:name="android.hardware.faketouch"
110 <uses-feature android:name="android.hardware.telephony"
112 <uses-feature android:name="android.hardware.camera"
114 <uses-feature android:name="android.hardware.nfc"
116 <uses-feature android:name="android.hardware.location.gps"
118 <uses-feature android:name="android.hardware.microphone"
120 <uses-feature android:name="android.hardware.sensor"
137 …能の宣言については、<a href="{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code uses-feature}…
171 …feature-element.html#permissions-features">{@code uses-feature}</a>ガイドを参照してください。アプリが上記の機能のいずれかを要求す…
[all …]
|
| /frameworks/base/docs/html/training/tv/start/ |
| D | hardware.jd | 84 <th>Android feature descriptor</th>
126 not the same as the microphone hardware feature described here. The controller microphone is fully
131 See the <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html#features-reference">
139 Android apps can declare hardware feature requirements in the app manifest to ensure that they do
154 <uses-feature android:name="android.hardware.touchscreen"
156 <uses-feature android:name="android.hardware.faketouch"
158 <uses-feature android:name="android.hardware.telephony"
160 <uses-feature android:name="android.hardware.camera"
162 <uses-feature android:name="android.hardware.nfc"
164 <uses-feature android:name="android.hardware.location.gps"
[all …]
|
| /frameworks/base/libs/androidfw/tests/data/feature/ |
| D | build | 18 aapt package -M AndroidManifest.xml -S res --feature-of ../basic/bundle.apk -F bundle.apk -f && \
20 mv resources.arsc feature.arsc && \
21 xxd -i feature.arsc > feature_arsc.h
|
| /frameworks/opt/net/ims/src/java/com/android/ims/ |
| D | ImsConfig.java | 607 public void getFeatureValue(int feature, int network, in getFeatureValue() argument
610 Rlog.d(TAG, "getFeatureValue: feature = " + feature + ", network =" + network + in getFeatureValue()
614 miConfig.getFeatureValue(feature, network, listener); in getFeatureValue()
632 public void setFeatureValue(int feature, int network, int value, in setFeatureValue() argument
635 Rlog.d(TAG, "setFeatureValue: feature = " + feature + ", network =" + network + in setFeatureValue()
639 miConfig.setFeatureValue(feature, network, value, listener); in setFeatureValue()
|
| /frameworks/base/tests/FeatureSplit/feature1/src/com/android/test/split/feature/one/ |
| D | One.java | 16 package com.android.test.split.feature.one;
18 import com.android.test.split.feature.ActivityMain;
28 ((TextView) findViewById(com.android.test.split.feature.R.id.text)) in onCreate()
|
| /frameworks/base/tests/FeatureSplit/feature2/ |
| D | Android.mk | 34 LOCAL_AAPT_FLAGS := --feature-of $(featureOfApk)
35 LOCAL_AAPT_FLAGS += --feature-after $(featureAfterApk)
36 LOCAL_AAPT_FLAGS += --custom-package com.android.test.split.feature.two
|
| /frameworks/native/opengl/tools/glgen2/registry/ |
| D | reg.py | 176 def regSortCategoryKey(feature): argument
177 if (feature.elem.tag == 'feature'):
179 elif (feature.category == 'ARB' or
180 feature.category == 'KHR' or
181 feature.category == 'OES'):
188 def regSortNameKey(feature): argument
189 return feature.name
194 def regSortNumberKey(feature): argument
195 return feature.number
792 for feature in self.reg.findall('feature'):
[all …]
|
| /frameworks/base/docs/html/guide/practices/ |
| D | compatibility.jd | 36 to be successful on all these devices, it should tolerate some feature variability
48 <p>If necessary, however, you can specify your app's feature requirements and control
87 widgets), and some are dependent on the platform version. Not every device supports every feature,
109 Android defines <em>feature IDs</em> for any hardware or software feature
111 feature ID for the compass sensor is {@link
112 android.content.pm.PackageManager#FEATURE_SENSOR_COMPASS} and the feature ID for app widgets
116 given feature by declaring it with a <a href=
117 "{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code <uses-feature>}</a>
126 <uses-feature android:name="android.hardware.sensor.compass"
138 a device feature, you should set the <a href=
[all …]
|
| /frameworks/base/docs/html-intl/intl/zh-tw/google/play/ |
| D | filters.jd | 35 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a></code></l…
132 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
138 </strong>宣示說明包括 <code><uses-feature
141 …</strong>宣示說明不包括 <code><uses-feature></code> 元素。<strong>結果</strong>：除非套用其他篩選器，否則 Google Play…
143 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
145 …<code><uses-permission></code> 元素要求的許可，解譯為功能需求 (等同於 <code><uses-feature></code> 元素中宣告的…
151 <td valign="top"><p>應用程式可以使用 <code><uses-feature
162 …細資料，請參閱 <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature…
177 …<uses-feature></code> 元素中正確宣告的硬體功能需求。例如，若應用程式要求 <code>CAMERA</code> 許可，但未針對 <code>android.ha…
178 … 會視為應用程式要求基本硬體功能，即使可能並非對應於 <code><uses-feature></code> 宣告，也是如此。隨後，Google Play 會根據 <code><…
[all …]
|
| /frameworks/base/docs/html-intl/intl/zh-cn/google/play/ |
| D | filters.jd | 36 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a></code></l…
203 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
212 </strong>清单文件包括 <code><uses-feature
217 </strong>清单文件不包括 <code><uses-feature></code>
221 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
225 <code><uses-permission></code>元素请求的权限解释为与 <code><uses-feature></code> 元素所声明要求等效的功能要求。
235 <td valign="top"><p>应用可以使用<code><uses-feature
254 …更多详情，请参阅<a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature…
273 <code><uses-feature></code>
276 权限，但没有针对<code>android.hardware.camera</code>声明<code><uses-feature></code>元素，
[all …]
|
| /frameworks/base/docs/html-intl/intl/ru/google/play/ |
| D | filters.jd | 36 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a></code></l…
203 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
212 </strong>В манифесте содержится декларация <code><uses-feature
217 </strong>В манифесте не содержится элемент <code><uses-feature></code>
221 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
226 они декларировались элементами <code><uses-feature></code>. См. раздел <a href="#uses-permiss…
236 версия OpenGL-ES, используя атрибут <code><uses-feature
254 …ию, см. <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature…
274 которые, возможно, не были правильно задекларированы элементами <code><uses-feature></code>.
276 но в его манифесте не задекларирован элемент <code><uses-feature></code> для
[all …]
|
| /frameworks/base/docs/html-intl/intl/ko/google/play/ |
| D | filters.jd | 36 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a></code></l…
203 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
212 </strong>매니페스트가 <code><uses-feature
217 </strong>매니페스트가 <code><uses-feature></code> 요소를 포함하지 않습니다.
221 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
223 …Play는 <code><uses-permission></code> 요소를 통해 요청된 권한을 <code><uses-feature></code> 요소에 선언…
235 <td valign="top"><p>애플리케이션이 <code><uses-feature
254 …자세한 내용은 <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature…
272 …하지만 Google Play가 해당 요소를 읽고 <code><uses-feature></code> 요소에서 올바로 선언되지 않았을 수도 있는 하드웨어 기능 요구사항이…
275 …/code> 권한을 요청하지만 <code>android.hardware.camera</code>에 대해 <code><uses-feature></code> 요소를 선언…
[all …]
|
| /frameworks/base/docs/html-intl/intl/ja/google/play/ |
| D | filters.jd | 35 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a></code></l…
132 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
138 </strong>マニフェストに <code><uses-feature
141 …</strong>マニフェストが <code><uses-feature></code> 要素を含んでいません。<strong>結果</strong>: Google Play は、他…
143 href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><uses-feature></a>
145 … は <code><uses-permission></code> 要素から要求されたパーミッションを、<code><uses-feature></code> 要素で宣言さ…
151 <td valign="top"><p>アプリは、<code><uses-feature
162 …詳細については、<a href="{@docRoot}guide/topics/manifest/uses-feature-element.html"><code><uses-feature…
177 …feature></code> 要素で正しく宣言されていない可能性のあるハードウェア機能の要件を備えているかどうか判断します。たとえば、アプリが <code>CAMERA</code> パー…
178 …le Play は <code><uses-feature></code> 宣言に対応するものがない場合でも、基本的なハードウェア機能を必要としていると想定します。次に、Google …
[all …]
|
| /frameworks/base/telephony/java/com/android/ims/ |
| D | ImsConfigListener.aidl | 34 void onGetFeatureResponse(int feature, int network, int value, int status); in onGetFeatureResponse() argument
50 void onSetFeatureResponse(int feature, int network, int value, int status); in onSetFeatureResponse() argument
|
| /frameworks/base/docs/html/distribute/stories/games/ |
| D | glu-eternity-warriors.jd | 34 Eternity Warriors 3. They made this new feature accessible from the home
43 <li>sent push notifications to users telling them about the gifting feature.
45 <li>showed a full screen in-game screen promoting the gifting feature.</li>
69 Glu found that the gifting feature has a very high response rate and the gift
70 requests’ <b>fulfillment rate doubled</b> within 30 days of the feature’s
|
| /frameworks/base/telephony/java/com/android/ims/internal/ |
| D | IImsConfig.aidl | 81 oneway void getFeatureValue(int feature, int network, ImsConfigListener listener); in getFeatureValue() argument
94 oneway void setFeatureValue(int feature, int network, int value, ImsConfigListener listener); in setFeatureValue() argument
|
| /frameworks/base/tests/FeatureSplit/feature1/ |
| D | Android.mk | 31 LOCAL_AAPT_FLAGS := --feature-of $(featureOfApk) --custom-package com.android.test.split.feature.one
|
| /frameworks/ml/bordeaux/service/src/android/bordeaux/services/ |
| D | LocationStatsAggregator.java | 120 HashMap<String,String> feature = new HashMap<String,String>(); in getFeatureValue() local
131 feature.put(CURRENT_LOCATION, mFakeLocation); in getFeatureValue()
133 feature.put(CURRENT_LOCATION, location); in getFeatureValue()
137 return (Map) feature; in getFeatureValue()
|
| D | TimeStatsAggregator.java | 78 HashMap<String,String> feature = new HashMap<String,String>(); in getFeatureValue() local
83 feature.put(featureName, features.get(featureName)); in getFeatureValue()
87 return (Map)feature; in getFeatureValue()
|
| /frameworks/base/core/java/android/net/ |
| D | ConnectivityManager.java | 1094 public int startUsingNetworkFeature(int networkType, String feature) { in startUsingNetworkFeature() argument
1096 NetworkCapabilities netCap = networkCapabilitiesForFeature(networkType, feature); in startUsingNetworkFeature()
1099 feature); in startUsingNetworkFeature()
1149 public int stopUsingNetworkFeature(int networkType, String feature) { in stopUsingNetworkFeature() argument
1151 NetworkCapabilities netCap = networkCapabilitiesForFeature(networkType, feature); in stopUsingNetworkFeature()
1154 feature); in stopUsingNetworkFeature()
1159 Log.d(TAG, "stopUsingNetworkFeature for " + networkType + ", " + feature); in stopUsingNetworkFeature()
1164 private NetworkCapabilities networkCapabilitiesForFeature(int networkType, String feature) { in networkCapabilitiesForFeature() argument
1167 if ("enableMMS".equals(feature)) { in networkCapabilitiesForFeature()
1169 } else if ("enableSUPL".equals(feature)) { in networkCapabilitiesForFeature()
[all …]
|
| /frameworks/base/media/java/android/media/ |
| D | MediaFormat.java | 827 public boolean getFeatureEnabled(String feature) { in getFeatureEnabled() argument
828 Integer enabled = (Integer)mMap.get(KEY_FEATURE_ + feature); in getFeatureEnabled()
883 public void setFeatureEnabled(String feature, boolean enabled) { in setFeatureEnabled() argument
884 setInteger(KEY_FEATURE_ + feature, enabled ? 1 : 0); in setFeatureEnabled()
|
| /frameworks/base/media/tests/MediaFrameworkTest/src/com/android/mediaframeworktest/integration/ |
| D | CameraBinderTestUtils.java | 71 final static public boolean isFeatureAvailable(Context context, String feature) { in isFeatureAvailable() argument
75 if (f.name != null && f.name.equals(feature)) { in isFeatureAvailable()
|