This page (revision-58) was last changed on 23-Apr-2022 17:06 by HarryMetske

This page was created on 23-Apr-2022 17:05 by Harry Metske

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
58 23-Apr-2022 17:06 29 KB HarryMetske to previous
57 23-Apr-2022 17:05 29 KB HarryMetske to previous | to last
56 23-Apr-2022 17:05 28 KB HarryMetske to previous | to last
55 23-Apr-2022 17:05 26 KB Harry Metske to previous | to last
54 23-Apr-2022 17:05 26 KB Harry Metske to previous | to last
53 23-Apr-2022 17:05 24 KB Harry Metske to previous | to last
52 23-Apr-2022 17:05 24 KB 10.0.0.138 to previous | to last
51 23-Apr-2022 17:05 23 KB 10.0.0.138 to previous | to last
50 23-Apr-2022 17:05 23 KB 10.0.0.138 to previous | to last
49 23-Apr-2022 17:05 22 KB 10.0.0.138 to previous | to last
48 23-Apr-2022 17:05 22 KB 10.0.0.138 to previous | to last
47 23-Apr-2022 17:05 22 KB 10.0.0.138 to previous | to last
46 23-Apr-2022 17:05 20 KB 10.0.0.138 to previous | to last
45 23-Apr-2022 17:05 20 KB 10.0.0.138 to previous | to last
44 23-Apr-2022 17:05 20 KB HarryMetske to previous | to last
43 23-Apr-2022 17:05 19 KB HarryMetske to previous | to last
42 23-Apr-2022 17:05 19 KB Harry Metske to previous | to last
41 23-Apr-2022 17:05 19 KB Harry Metske to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 325 changed one line
* __Ordered__ - sequential processing in priority order
* __Ordered__ - sequential processing in priority order ( ''sendOrderedBroadcasts()'')
At line 338 added 17 lines
When an intent is delivered to the onReceive(), two parms are passed:
* the context in which the receiver is running
* the intent
The process receiving the intent has high priority during onReceive() processing and runs on the main thread, so make it quick. If you have long running work, let it handle by a Service.
Receiver is not considered valid after onReceive() returns. Android might terminate the BroadcastReceiver .
BroadcastReceivers can't wait for asynchronous callbacks, because they then migth already be gone. So no ShowDialogs and not startActivityForResult().
BroadcastReceivers can abort the broadcast, making the Intent unavailable to receivers lower in the prio. (''abortBroadcast()'')
BroadcastReceivers can ''setResultData()'' to the broadcast, so each receiver can see what the previous receiver has done with the result.
With sticky intents, intents can "overwrite" older intents they match.
When a BroadcastReceiver registers itself, all Android cached sticky intents will be delivered to the broadcastreceiver, and one matching sticky intent is returned to the caller.