Android Broadcast reciever

In Android, a broadcast receiver is an Android component which allows you to register for system or application events. All registered receivers for an event are notified by the Android run time once this event happens.
For example, applications can register for the ACTION_POWER_CONNECTED system event which is fired once the Android system has completed the boot process.
A receiver can be registered via the AndroidManifest.xml file.
Alternatively to this static registration, you can also register a receiver dynamically via theContext.registerReceiver() method.
The implementing class for a receiver extends the BroadcastReceiver class.
If the event for which the broadcast receiver has registered happens, the onReceive() method of the receiver is called by the Android system.

Comments

Post a Comment

Popular posts from this blog

Android intent/filters

Image
An Android  Intent  is an abstract description of an operation to be performed. It can be used with  startActivity  to launch an Activity,  broadcastIntent  to send it to any interested BroadcastReceiver components, and  startService(Intent)  or  bindService(Intent, ServiceConnection, int)  to communicate with a background Service. The intent itself, an Intent object, is a passive data structure holding an abstract description of an operation to be performed. For example, let's assume that you have an Activity that needs to launch an email client and sends an email using your Android device. For this purpose, your Activity would send an ACTION_SEND along with appropriate  chooser , to the Android Intent Resolver. The specified chooser gives the proper interface for the user to pick how to send your email data. Intent email = new Intent ( Intent . ACTION_SEND , Uri . parse ( "mailto:" )); email . putExtra ( Intent . EXTRA...
Read more

Android Content Provider(Easy explaination with diagram)

Image
A content provider component supplies data from one application to others on request. Such requests are handled by the methods of the ContentResolver class. A content provider can use different ways to store its data and the data can be stored in a database, in files, or even over a network. Content providers let you centralize content in one place and have many different applications access it as needed. A content provider behaves very much like a database where you can query it, edit its content, as well as add or delete content using insert(), update(), delete(), and query() methods. In most cases this data is stored in an  SQlite  database. A content provider is implemented as a subclass of  ContentProvider  class and must implement a standard set of APIs that enable other applications to perform transactions. Create Content Provider This involves number of simple steps to create your own content provider. First of all you need to create a Content P...
Read more