| /frameworks/base/docs/html/training/monitoring-device-state/ |
| manifest-receivers.jd | 1 page.title=Manipulating Broadcast Receivers On Demand
17 <li><a href="#ToggleReceivers">Toggle and Cascade State Change Receivers to Improve
32 your application manifest. Then within each of these receivers you simply reschedule your recurring
36 receivers is triggered—potentially much more frequently than required.</p>
38 <p>A better approach is to disable or enable the broadcast receivers at runtime. That way you can
39 use the receivers you declared in the manifest as passive alarms that are triggered by system events
43 <h2 id="ToggleReceivers">Toggle and Cascade State Change Receivers to Improve Efficiency </h2>
46 component defined in the manifest, including whichever broadcast receivers you wish to enable or
58 your receivers except the connectivity-change receiver. Conversely, once you are connected you can
|
| index.jd | 58 <dt><b><a href="manifest-receivers.html">Manipulating Broadcast Receivers On Demand</a></b></dt>
59 <dd>Broadcast receivers that you've declared in the manifest can be toggled at runtime to disable
61 efficiency by toggling and cascading state change receivers and delay actions until the device is in
|
| connectivity-monitoring.jd | 9 next.title=Manipulating Broadcast Receivers On Demand
10 next.link=manifest-receivers.html
89 <p>This technique requires toggling broadcast receivers you've declard in the manifest, which is
|
| /frameworks/support/v4/java/android/support/v4/content/ |
| LocalBroadcastManager.java | 71 final ArrayList<ReceiverRecord> receivers; field in class:LocalBroadcastManager.BroadcastRecord
75 receivers = _receivers;
173 ArrayList<ReceiverRecord> receivers = mActions.get(action); local
174 if (receivers != null) {
175 for (int k=0; k<receivers.size(); k++) {
176 if (receivers.get(k).receiver == receiver) {
177 receivers.remove(k);
181 if (receivers.size() <= 0) {
193 * executing while the receivers are run.
195 * @param intent The Intent to broadcast; all receivers matching thi
219 ArrayList<ReceiverRecord> receivers = null; local
[all...] |
| /frameworks/base/services/java/com/android/server/am/ |
| BroadcastRecord.java | 44 final boolean ordered; // serialize the send to receivers?
48 final List receivers; // contains BroadcastFilter and ResolveInfo field in class:BroadcastRecord
50 long dispatchTime; // when dispatch started on this set of receivers
69 // was found in our list of registered receivers).
150 final int N = receivers != null ? receivers.size() : 0;
154 Object o = receivers.get(i);
175 receivers = _receivers;
|
| ProcessRecord.java | 117 final HashSet<ReceiverList> receivers = new HashSet<ReceiverList>(); field in class:ProcessRecord
264 if (receivers.size() > 0) {
265 pw.print(prefix); pw.print("receivers="); pw.println(receivers);
|
| /external/kernel-headers/original/linux/ |
| nvhdcp.h | 24 /* maximum receivers and repeaters connected at a time */
75 // (OUT) Up to 127 receivers & repeaters
|
| /external/srtp/crypto/include/ |
| rdb.h | 68 * senders, not receivers - DO NOT use these functions on the same
|
| /external/v8/test/mjsunit/regress/ |
| regress-1062422.js | 28 // 1062422 Ensure that accessors can handle unexpected receivers.
|
| regress-1491.js | 29 // receivers.
|
| /development/apps/Development/src/com/android/development/ |
| PackageSummary.java | 167 LinearLayout receivers = (LinearLayout)findViewById(R.id.receivers); local
191 if (info.receivers != null) {
192 final int N = info.receivers.length;
194 ActivityInfo ai = info.receivers[i];
199 receivers.addView(view, lp);
202 receivers.setVisibility(View.GONE);
|
| /packages/apps/MusicFX/src/com/android/musicfx/ |
| Compatibility.java | 40 * enables or disables control panel receivers as needed to ensure that only
93 * It then enables the open/close receivers in the active control panel,
202 // The open and close receivers are likely the same, but they may not be.
219 // broadcast to newly enabled receivers, while sending "close session" to
220 // receivers that are about to be disabled. We could also consider just
|
| /frameworks/base/core/java/android/content/pm/ |
| PackageInfo.java | 99 public ActivityInfo[] receivers; field in class:PackageInfo
226 dest.writeTypedArray(receivers, parcelableFlags);
263 receivers = source.createTypedArray(ActivityInfo.CREATOR);
|
| /cts/tests/tests/content/src/android/content/pm/cts/ |
| PackageInfoTest.java | 109 checkInfoArray(expected.receivers, actual.receivers);
|
| /external/webkit/Source/WebKit2/Shared/Plugins/ |
| NPRemoteObjectMap.cpp | 193 // Gather the receivers associated with this plug-in.
200 // Now delete all the receivers.
|
| /external/chromium/third_party/libjingle/source/talk/session/phone/ |
| mediachannel.h | 173 receivers.clear();
176 std::vector<VoiceReceiverInfo> receivers; member in struct:cricket::VoiceMediaInfo
182 receivers.clear();
185 std::vector<VideoReceiverInfo> receivers; member in struct:cricket::VideoMediaInfo
453 // Send an intra frame to the receivers.
|
| /frameworks/base/docs/html/resources/articles/ |
| multitasking-android-way.jd | 53 <p>For these tasks, the application needs a way to tell Android "I would explicitly like to run at this point." There are two main facilities available to applications for this, represented by two kinds of components they can publish in their manifest: <span style="font-style:italic;">broadcast receivers</span> and <span style="font-style:italic;">services</span>.</p>
54 <h4>Broadcast Receivers</h4>
57 <p>Broadcast receivers are great for doing small pieces of work in response to an external stimulus, such as posting a notification to the user after being sent a new GPS location report. They are very lightweight, since the application's process only needs to be around while actively receiving the broadcast. Because they are active for a deterministic amount of time, fairly strong guarantees can be made about not killing their process while running. However they are not appropriate for anything of indeterminate length, such as networking.</p>
61 <p>Process management for services is different than broadcast receivers, because an unbounded number of services can ask to be running for an unknown amount of time. There may not be enough RAM to have all of the requesting services run, so as a result no strong guarantees are made about being able to keep them running.</p>
92 Application widgets are broadcast receivers that Android sends broadcasts to when it needs to interact with them. This allows app widgets to be quite lightweight, by not needing their application's process remain running.
|
| /frameworks/base/core/java/android/content/ |
| BroadcastReceiver.java | 59 * Context.sendBroadcast}) are completely asynchronous. All receivers of the
61 * more efficient, but means that receivers cannot use the result or abort
67 * to other receivers. The order receivers run in can be controlled with the
69 * android:priority} attribute of the matching intent-filter; receivers with
75 * particular, for receivers that may require the creation of a process, only
77 * In this situation, however, the non-ordered semantics hold: these receivers still
114 * <p>Receivers used with the {@link Context} APIs are by their nature a
148 * Only receivers who have been granted this permission
668 * any other broadcast receivers from receiving the broadcast. It will stil
[all...] |
| Context.java | [all...] |
| /frameworks/base/docs/html/guide/topics/manifest/ |
| receiver-element.jd | 27 subclass) as one of the application's components. Broadcast receivers enable
37 for more on dynamically created receivers.
50 application components, including broadcast receivers. The
|
| intent-filter-element.jd | 99 meaning for both activities and broadcast receivers:
108 <li><p>It controls the order in which broadcast receivers are executed to
|
| /external/libvpx/examples/includes/geshi/geshi/ |
| smalltalk.php | 139 GESHI_SEARCH => '([:(,=[.*\/+-]\s*)([a-zA-Z0-9_]+)', //message parameters, message receivers
|
| /external/v8/test/mjsunit/ |
| string-fromcharcode.js | 31 // Test various receivers and arguments passed to String.fromCharCode.
|
| /packages/apps/Launcher2/src/com/android/launcher2/ |
| LauncherApplication.java | 52 // Register intent receivers
|
| /frameworks/base/docs/html/guide/topics/ |
| fundamentals.jd | 10 services, content providers, and broadcast receivers)</li>
169 <dt><b>Broadcast receivers</b></dt>
176 receivers don't display a user interface, they may <a
217 broadcast receivers—are activated by an asynchronous message called an <em>intent</em>.
235 <p>For broadcast receivers, the intent simply defines the
335 for broadcast receivers</li>
344 receivers can be either declared in the manifest or created dynamically in code (as
357 {@link android.content.Intent} to start activities, services, and broadcast receivers. You can do so
|
