broadcastreceiver

I have braodcastreceiver, that broadcast receiver shall schedule an alarm. Usually I would do AlarmManager am = (AlarmManager) getSystemService(ALARM_SERVICE); am.set(AlarmManager.RTC, time, myPendingIntent); The problem is that getSystemService is not available in a Broadcast receiver only in an Activty. How would I do it here? Thanks, A. AndyAndroid, getSystemService() is part of the Context . You will need to save the Context you receive in your onReceive() method like so... private Context mContext; @Override public void onReceive(Context c, Intent i) { mContext = c; } Then..where you call

I have a small application which can be used to set reminders for future events. The app uses an AlarmManager to set the time for when the user should be reminded. When the alarm goes off, a BroadcastReceiver registers this and in turn starts a service to notify the user via a toast and a notification in the status bar. In order to display the correct information in the notification and toast, some extra information is passed along with the intent. The first time a reminder is registered, the info received by the BroadcastReceiver and passed on to the service is correct. But for each following

In onResume() I do: registerReceiver(timeTickReceiver, new IntentFilter(Intent.ACTION_TIME_TICK)); and in onPause(): unregisterReceiver(timeTickReceiver); I see "java.lang.IllegalArgumentException: Receiver not registered" reports in Android Developer Console (there are only 2 reports and my app has thousands of users). The exception is triggered by unregisterReceiver(). What can be happening? I don't feel very confident to just surround it with try-catch. We've seen this error when doing a long press on a particular screen, and then immediately doing two orientation changes (e.g. turning the

Consider a simple tool using a BroadcastReceiver to achieve a simple goal. Because this should not be used by other applications, it defines a permission with a protectionLevel of signature or signatureOrSystem : <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="any.test"> <permission android:name="any.test.PERMISSION" android:protectionLevel="signatureOrSystem" /> <application android:label="AnyTest"> <receiver android:name=".Receiver" android:exported="true" android:permission="any.test.PERMISSION" /> </application> </manifest> Now I'd like to test this by sending

I am getting warning of deprecated declaration of Broadcast Receiver. <!-- NETWORK RECEIVER... --> <receiver android:name=".utils.NetworkUtils" > <intent-filter> <action android:name="android.net.conn.CONNECTIVITY_CHANGE" /> </intent-filter> </receiver> WARNING: Declaring a broadcastreceiver for android.net.conn.CONNECTIVITY_CHANGE is deprecated for apps targeting N and higher. In general, apps should not rely on this broadcast and instead use JobScheduler or GCMNetworkManager. Is there any other way to use it without deprecated methods? I had the same problem, i did something like that. It

I want to detect screen off and on event for that i have created BroadcastReceiver, It only works fine when app is running and when i remove the app from task manager then it does not works. Activity: @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); try{ BroadcastReceiver myrcver = new BootReceiver(); IntentFilter screenStateFilter = new IntentFilter(); screenStateFilter.addAction(Intent.ACTION_SCREEN_ON); screenStateFilter.addAction(Intent.ACTION_SCREEN_OFF); registerReceiver(myrcver, screenStateFilter);

Does anyone have any documentation on this "TooManyMessages" error . After I call the GoogleCloudMessaging send method I am getting an intent from com.google.android.c2dm.intent.RECEIVE with the following key/value pairs in the extras bundle. Send error: Bundle[{error=TooManyMessages, message_type=send_error, google.message_id=1, android.support.content.wakelockid=1} This means that too many messages were stored in the GCM server for a single device without being delivered (which might happen if your device was offline while many messages were sent by your server). Once the number of such