| /frameworks/support/v4/java/android/support/v4/content/ |
| D | LocalBroadcastManager.java | 136 ArrayList<IntentFilter> filters = mReceivers.get(receiver); in registerReceiver() local
137 if (filters == null) { in registerReceiver()
138 filters = new ArrayList<IntentFilter>(1); in registerReceiver()
139 mReceivers.put(receiver, filters); in registerReceiver()
141 filters.add(filter); in registerReceiver()
165 ArrayList<IntentFilter> filters = mReceivers.remove(receiver); in unregisterReceiver() local
166 if (filters == null) { in unregisterReceiver()
169 for (int i=0; i<filters.size(); i++) { in unregisterReceiver()
170 IntentFilter filter = filters.get(i); in unregisterReceiver()
|
| /frameworks/base/docs/html/guide/appendix/ |
| D | market-filters.jd | 9 <li>Android Market applies filters that control which Android-powered devices can access your
17 <li><a href="#how-filters-work">How Filters Work in Android Market</a></li>
18 <li><a href="#manifest-filters">Filtering based on Manifest Elements</a>
20 <li><a href="#advanced-filters">Advanced manifest filters</a></li>
23 <li><a href="#other-filters">Other Filters</a></li>
70 <p>Changes to the Android Market filters are independent of changes to the Android platform itself.
72 filters applications.</p>
75 <h2 id="how-filters-work">How Filters Work in Android Market</h2>
95 <p>You can use any combination of the available filters for your app. For example, you can set a
98 only. Android Market's filters will thus prevent the application from being available on any device
[all …]
|
| D | glossary.jd | 134 href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
145 available intent filters in all applications and passes the Intent to the
148 href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
168 filters, services), imported libraries, and describes the various
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | activity-alias-element.jd | 32 It can have its own set of intent filters, and they, rather than the
33 intent filters on the target activity itself, determine which intents
35 treats the alias. For example, the intent filters on the alias may
41 filters on the target activity itself set these flags.
76 The default value depends on whether the alias contains intent filters. The
77 absence of any filters means that the activity can be invoked through the alias
|
| D | category-element.jd | 15 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
16 Intent Filters</a> for details on intent filters and the role of category
|
| D | action-element.jd | 19 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
20 Intent Filters</a> for details on intent filters and the role of action
|
| D | supports-gl-texture-element.jd | 25 <p style="margin-top:1em;">Android Market filters applications according
144 <li><a href="{@docRoot}guide/appendix/market-filters.html">Android Market Filters</a></li>
150 <p>Android Market filters the applications that are visible to users, so that
152 their devices. One of the ways Market filters applications is by texture
182 formats is supported by the device, Android Market filters the application so
|
| D | uses-library-element.jd | 47 Android Market filters applications based on the libraries installed on the
49 <a href="{@docRoot}guide/appendix/market-filters.html">Market Filters</a>.
|
| D | compatible-screens-element.jd | 57 <p>Also see the <a href="{@docRoot}guide/appendix/market-filters.html">Market Filters</a>
58 document for more information about how Android Market filters applications using this and
141 <dd><a href="{@docRoot}guide/appendix/market-filters.html">Market Filters</a></dd>
|
| D | receiver-element.jd | 65 The default value depends on whether the broadcast receiver contains intent filters.
66 The absence of any filters means that it can be invoked only by Intent objects that
91 default icon for all the receiver's intent filters (see the
105 default label for all the receiver's intent filters (see the
|
| D | service-element.jd | 63 The default value depends on whether the service contains intent filters. The
64 absence of any filters means that it can be invoked only by specifying
90 default icon for all the service's intent filters (see the
104 default label for all the service's intent filters (see the
|
| D | uses-sdk-element.jd | 38 <p>Android Market filters the applications that are visible to users, so
40 devices. One of the ways Market filters applications is by Android
45 href="{@docRoot}guide/appendix/market-filters.html">Market Filters</a>.</p>
|
| D | data-element.jd | 63 Information on how intent filters work, including the rules for how Intent objects
64 are matched against filters, can be found in another document,
65 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents and
|
| D | intent-filter-element.jd | 43 For a more detailed discussion of filters, see the separate
44 <a href="{@docRoot}guide/topics/intents/intents-filters.html">Intents
|
| D | uses-feature-element.jd | 50 <p style="margin-top:1em;">Android Market filters the applications that are visible to users, so
52 devices. One of the ways Market filters applications is by feature compatibility.</p>
210 <li><a href="{@docRoot}guide/appendix/market-filters.html">Android Market Filters</a></li>
219 <p>Android Market filters the applications that are visible to users, so that
221 their devices. One of the ways Market filters applications is by feature
261 supported by the device, Android Market filters the application so that it is
265 elements directly affect how Android Market filters your application, it's
285 filters the application from users on devices that do not provide that feature.
321 sets up filters for those features, just as it would do for an explicitly
350 metadata that it stores for the application and sets up filters for them.</p>
[all …]
|
| /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/nfc/ |
| D | INfcAdapter.aidl | 45 in IntentFilter[] filters, in TechListParcel techLists); in setForegroundDispatch() argument
|
| D | NfcAdapter.java | 646 IntentFilter[] filters, String[][] techLists) { in enableForegroundDispatch() argument
661 sService.setForegroundDispatch(intent, filters, parcel); in enableForegroundDispatch()
|
| /frameworks/base/core/java/android/text/ |
| D | Editable.java | 111 public void setFilters(InputFilter[] filters); in setFilters() argument
|
| /frameworks/base/docs/html/guide/topics/nfc/ |
| D | advanced-nfc.jd | 239 <li>Declare intent filters to handle the intents that you want to intercept. The foreground
240 dispatch system checks the specified intent filters with the intent that is received when
243 Specifying a <code>null</code> array of intent filters and technology filters, specifies
|
| D | nfc.jd | 245 filters for the intent. If more than one application can handle the intent, the Activity Chooser
282 android.nfc.NfcAdapter#ACTION_TAG_DISCOVERED}) until an application filters for the
362 following example filters for {@link android.nfc.NfcAdapter#ACTION_NDEF_DISCOVERED}
372 <p>The following example filters for a URI in the form of
387 <p>If your activity filters for the {@link android.nfc.NfcAdapter#ACTION_TECH_DISCOVERED} intent,
669 href="filtering-intents">use intent filters</a>.
678 <li>If the Activity that filters for the intent does not match the
694 intent filters as normal. This is useful if your application is interested in other tags
770 dispatching</a>, then it can still scan tags that match the intent filters set in the foreground
916 <p>Even though AARs guarantee an application is started or downloaded, intent filters are
|
| /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/market/publishing/ |
| D | multiple-apks.jd | 12 <li>Different APKs are distributed to different devices based on filters declared in the
28 <li><a href="#SupportedFilters">Supported filters</a></li>
48 <li><a href="{@docRoot}guide/appendix/market-filters.html">Market Filters</a></li>
192 <h3 id="SupportedFilters">Supported filters</h3>
195 href="{@docRoot}guide/appendix/market-filters.html">Android Market filters</a> that are specified by
197 APKs only when each APK uses filters to support a variation of the following
289 href="{@docRoot}guide/appendix/market-filters.html">Android Market filters</a>—but are not
292 multiple APKs if the above listed filters are the same for each APK (but the APKs differ based on
315 the <a href="#MarketFiltersSupported">supported Market filters</a> (listed above).</p>
333 supported API levels (no other <a href="#SupportedMarketFilters">supported market filters</a>
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | index.jd | 22 filters that make it much simpler to create conforming icons.</dd>
|
| /frameworks/base/docs/html/resources/articles/ |
| D | can-i-use-this-intent.jd | 7 an <a href="{@docRoot}guide/topics/intents/intents-filters.html">intents</a>.
|