| /frameworks/base/docs/html/guide/appendix/ |
| D | market-filters.jd | 8 <ul> <li>Android Market applies filters to that let you control whether your app is shown to a
15 <ol> <li><a href="#how-filters-work">How Filters Work in Android Market</a></li>
16 <li><a href="#manifest-filters">Filtering based on Manifest File Elements</a></li>
17 <li><a href="#other-filters">Other Filters</a></li>
55 <p>Changes to the Android Market filters are independent of changes
59 <h2 id="how-filters-work">How Filters Work in Android Market</h2>
72 <p> You can use the filters described below to control whether Market shows or
74 available filters for your app — for example, you could set a
78 filters would prevent the application from being visible on any device that did
95 <h2 id="manifest-filters">Filtering based on Manifest Elements</h2>
[all …]
|
| D | glossary.jd | 135 href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
146 available intent filters in all applications and passes the Intent to the
149 href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
169 filters, services), imported libraries, and describes the various
|
| D | g-app-intents.jd | 7 href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and Intent Filters</a>.
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | category-element.jd | 13 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
14 Intent Filters</a> for details on intent filters and the role of category
|
| D | activity-alias-element.jd | 30 It can have its own set of intent filters, and they, rather than the
31 intent filters on the target activity itself, determine which intents
33 treats the alias. For example, the intent filters on the alias may
39 filters on the target activity itself set these flags.
74 The default value depends on whether the alias contains intent filters. The
75 absence of any filters means that the activity can be invoked through the alias
|
| D | action-element.jd | 17 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
18 Intent Filters</a> for details on intent filters and the role of action
|
| D | receiver-element.jd | 63 The default value depends on whether the broadcast receiver contains intent filters.
64 The absence of any filters means that it can be invoked only by Intent objects that
89 default icon for all the receiver's intent filters (see the
103 default label for all the receiver's intent filters (see the
|
| D | service-element.jd | 61 The default value depends on whether the service contains intent filters. The
62 absence of any filters means that it can be invoked only by specifying
88 default icon for all the service's intent filters (see the
102 default label for all the service's intent filters (see the
|
| D | data-element.jd | 61 Information on how intent filters work, including the rules for how Intent objects
62 are matched against filters, can be found in another document,
63 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
|
| D | uses-sdk-element.jd | 36 <p>Android Market filters the applications that are visible to users, so
38 devices. One of the ways Market filters applications is by Android
43 href="{@docRoot}guide/appendix/market-filters.html">Market Filters</a>.</p>
|
| D | uses-feature-element.jd | 22 <p style="margin-top:1em;">Android Market filters the applications that are visible to users, so
24 devices. One of the ways Market filters applications is by feature compatibility.</p>
182 <li><a href="{@docRoot}guide/appendix/market-filters.html">Android Market Filters</a></li>
191 <p>Android Market filters the applications that are visible to users, so that
193 their devices. One of the ways Market filters applications is by feature
233 supported by the device, Android Market filters the application so that it is
237 elements directly affect how Android Market filters your application, it's
257 filters the application from users on devices that do not provide that feature.
293 sets up filters for those features, just as it would do for an explicitly
322 metadata that it stores for the application and sets up filters for them.</p>
[all …]
|
| D | intent-filter-element.jd | 41 For a more detailed discussion of filters, see the separate
42 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents
|
| D | uses-permission-element.jd | 18 application requires the underlying hardware feature and filters the application
|
| D | manifest-intro.jd | 328 respond to — through <i>intent filters</i>. Since the Android system
330 intent filters are specified in the manifest as
332 elements. A component may have any number of filters, each one describing
340 filters.
344 For information on how Intent objects are tested against intent filters,
346 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents
|
| /frameworks/base/docs/html/guide/topics/intents/ |
| D | intents-filters.jd | 11 <li style="margin-left: 2em"><a href="#ifs">Intent filters</a></li>
78 <i>intent filters</i> associated with potential targets.
345 the Intent object to <i>intent filters</i>, structures associated with
349 the advertised type. If a component does not have any intent filters,
350 it can receive only explicit intents. A component with filters can
369 <h3><a name="ifs"></a>Intent filters</h3>
373 services, and broadcast receivers can have one or more intent filters.
375 the component is willing to receive. It, in effect, filters in
381 component's filters.
385 A component has separate filters for each job it can do, each face it can
[all …]
|
| /frameworks/base/core/java/android/text/ |
| D | Editable.java | 111 public void setFilters(InputFilter[] filters); in setFilters() argument
|
| D | SpannableStringBuilder.java | 1107 public void setFilters(InputFilter[] filters) { in setFilters() argument
1108 if (filters == null) { in setFilters()
1112 mFilters = filters; in setFilters()
|
| /frameworks/base/core/java/android/nfc/ |
| D | INfcAdapter.aidl | 51 in IntentFilter[] filters, in TechListParcel techLists); in enableForegroundDispatch() argument
|
| D | NfcAdapter.java | 479 IntentFilter[] filters, String[][] techLists) { in enableForegroundDispatch() argument
494 sService.enableForegroundDispatch(activity.getComponentName(), intent, filters, in enableForegroundDispatch() local
|
| /frameworks/base/docs/html/guide/topics/nfc/ |
| D | index.jd | 224 one or more of these three intent filters:
242 <p>The three intent filters are prioritized and behave in specific ways. Declare only the
243 ones that your Activity needs to handle. For more information on how to handle these filters,
263 <p>The intent dispatch system checks the intent filters of all the Activities along with the
319 to filter tags that support all of the technologies. The example below never filters a tag
340 technologies within one of the lists. The following example filters for
390 <li>Declare intent filters to handle the intents that you want to intercept. The foreground
391 dispatch system checks the specified intent filters with the intent that is received when
394 Specifying a <code>null</code> array of intent filters and for the technology filters,
580 foreground dispatching, then it can still scan tags that match the intent filters set in the
|
| /frameworks/base/docs/html/guide/practices/ |
| D | compatibility.jd | 10 href="{@docRoot}guide/appendix/market-filters.html">Market Filters</a></li>
109 <p>Android Market filters the applications that are visible to users, so
113 <p style="margin-top:1em;">One of the ways Market filters applications is by
120 <p style="margin-top:1em;">For information about other filters that you can
122 <a href="{@docRoot}guide/appendix/market-filters.html">Market
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | index.jd | 22 filters that make it much simpler to create conforming icons.</dd>
|
| D | activity_task_design.jd | 36 …<li><a href=#activity_not_reused_tip>Don't specify intent filters in an activity that won't be re-…
640 object to the <em>intent filters</em> of available activities. If more
720 title="intent filters">intent filters</a>.
819 …tip>When writing an activity that won't be re-used, don't specify intent filters — use expli…
823 to use, be sure not to add any intent filters to that activity. This
828 there's just no need for intent filters. Intent filters are
940 filters) and displays choices to share. In this case, it
|
| /frameworks/base/docs/html/resources/articles/ |
| D | can-i-use-this-intent.jd | 5 an <a href="{@docRoot}guide/topics/intents/intents-filters.html">intents</a>.
|
| /frameworks/base/docs/html/guide/topics/ |
| D | fundamentals.jd | 14 <li><a href="#ifilters">Intent filters</a></li>
334 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents
441 <h3 id="ifilters">Intent filters</h3>
448 It does so by comparing the Intent object to the <i>intent filters</i>
449 of potential targets. A component's intent filters inform Android of
453 two intent filters to the activity:
494 A component can have any number of intent filters, each one declaring a
495 different set of capabilities. If it doesn't have any filters, it can
503 object. All other filters are set up in the manifest.
507 For more on intent filters, see a separate document,
[all …]
|