Lines Matching full:feature
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
90 widgets), and some are dependent on the platform version. Not every device supports every feature,
114 Android defines <em>feature IDs</em> for any hardware or software feature
116 feature ID for the compass sensor is {@link
117 android.content.pm.PackageManager#FEATURE_SENSOR_COMPASS} and the feature ID for app widgets
121 given feature by declaring it with a <a href=
122 "{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code <uses-feature>}</a>
131 <uses-feature android:name="android.hardware.sensor.compass"
143 a device feature, you should set the <a href=
144 "{@docRoot}guide/topics/manifest/uses-feature-element.html#required">{@code required}</a>
146 for the device feature at runtime. If the app feature is not available on the current device,
147 gracefully degrade the corresponding app feature. For example, you can query whether
148 a feature is available by calling
154 // This device does not have a compass, turn off the compass feature
166 availability of a device feature. For example, if your app requests permission to access to {@link
168 android.content.pm.PackageManager#FEATURE_BLUETOOTH} device feature. You can disable filtering based
169 on this feature and make your app available to devices without Bluetooth by setting the <a href=
170 "{@docRoot}guide/topics/manifest/uses-feature-element.html#required">{@code required}</a> attribute
172 "{@docRoot}guide/topics/manifest/uses-feature-element.html">{@code <uses-feature>}</a> tag.
174 "{@docRoot}guide/topics/manifest/uses-feature-element.html#permissions">Permissions that Imply
175 Feature Requirements</a>.</p>
