Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As it quotes in the post you linked: "A broadcast receiver is a component that responds to system-wide broadcast announcements. Many broadcasts originate from the system."</p> <p>Therefore, they are useful in "catching" system broadcasts, e.g., when the device has booted up, when the battery level changes, when your Wi-Fi has been turned on, etc. </p> <p>Personally, I've used a BroadcastReceiver to start my app whenever the device receives a text message. In my case, this is preferred, as my app does not need to be running when the text message is received. Upon receipt, the system will broadcast an intent with an SMS_RECEIVED action. My BroadcastReceiver component, registered to accept this particular type ofbroadcast, will be notified and can then react as needed. In my case, it launches an Activity to notify the user of the text message and choose a particular reply text message.</p> <p>This is just a specific example. There are many other broadcasts that the system transmits and your Receiver can get. Check this <a href="http://developer.android.com/reference/android/content/Intent.html" rel="nofollow noreferrer">link</a> and this <a href="https://stackoverflow.com/questions/4031740/where-is-the-all-android-broadcast-intent-list/15178266#15178266">post</a> for more examples.</p> <p><strong>Clarification:</strong></p> <p>A LocalBroadcastManager is preferable in instances when you want rather simple way to communicate between app components without an intent being broadcast system-wide. Knowing this, you would want to go this route when the info you're passing is to be used only by your app. A LocalBroadcastManager is more efficient, generally simpler than using an IBinder interface, and can ensure that information isn't leaving your app.</p> <p>For an example, suppose you have a Service that runs in the background to track and log some constantly changing data; let's say your battery level. The Service can run on its own without user interaction, saving the battery level to the disk as it changes. When you start your activity to view said data, it would use LocalBroadcastManager to register a receiver to accept the info the Service is sending, and update the Activity's UI in real time to reflect this. Since no other app needs the info from your Service, it's better to do this than broadcasting an intent to which any other app could have access.</p> <p>To sum up, using a LocalBroadcastManager is:</p> <ol> <li>More efficient.</li> <li>More secure.</li> <li>Simpler.</li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POWhen to use BroadcastReceiver for non-cross-application communication?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USMike M.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhen to use BroadcastReceiver for non-cross-application communication?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for your response; I believe you addressed the question I asked, but I now think what I asked was not what I wanted an answer to. I've updated my question to clarify my intent. Can you take a look?
      singulars
      1. PO
      1. USMack
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload