views:

979

answers:

2

I've got an Android application which needs to be woken up sporadically throughout the day.

To do this, I'm using the AlarmManager to set up a PendingIntent and have this trigger a BroadcastReceiver. This BroadcastReceiver then starts an Activity to bring the UI to the foreground.

All of the above seems to work, in that the Activity launches itself correctly; but I'd like the BroadcastReceiver to notify the Activity that it was started by the alarm (as opposed to being started by the user). To do this I'm trying, from the onReceive() method of the BroadcastReceiver to set a variable in the extras bundle of the intent, thus:

    Intent i = new Intent(context, MyActivity.class);
    i.putExtra(wakeupKey, true);
    i.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
    context.startActivity(i);

In the onResume() method of my Activity, I then look for the existence of this boolean variable:

protected void onResume() {
    super.onResume();

    String wakeupKey = "blah";      
    if (getIntent()!=null && getIntent().getExtras()!=null)
        Log.d("app", "onResume at " + System.currentTimeMillis() + ":" + getIntent().getExtras().getBoolean(wakeupKey));
    else
        Log.d("app", "onResume at " + System.currentTimeMillis() + ": null");
}

The getIntent().getExtras() call in onResume() always returns null - I don't seem to be able to pass any extras through at all in this bundle.

If I use the same method to bind extras to the PendingIntent which triggers the BroadcastReceiver however, the extras come through just fine.

Can anyone tell me what's different about passing a bundle from a BroadcastReceiver to an Activity, as opposed to passing the bundle from an Activity to a BroadcastReceiver? I fear I may be doing something very very obvious wrong here...

A: 

Instead of getIntent().getExtras().getBoolean(wakeupKey) it is more conventional to write getIntent().getBooleanExtra(wakeupKey, defaultValue). I can't be sure if this is related to your problem, but there is some stuff to do with creating a bundle inside getExtras() that I'm not sure about, so it might be worth a go anyway.

Jim Blackler
Thanks Jim. Just tried making that change, but the value is always false (and I'm only ever setting it to true).
Tom Hume
A: 

This BroadcastReceiver then starts an Activity to bring the UI to the foreground.

This may be the crux of your problem here. Try overriding onNewIntent() and seeing if the Intent passed to it has your extra. If so, that's because of the way you set up the activity in the manifest (e.g., you're using singleTop) and the fact that, in this specific case, the activity already existed.

You might also consider getting rid of i.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK); and see if that changes matters.

The upshot is that what you're doing -- putting the extra in the Intent for startActivity() -- should work just fine. In fact, you can see examples of that here. This suggests it's something funky about the activity (e.g., singleTop) or the way you're invoking the activity (e.g., FLAG_ACTIVITY_NEW_TASK).

EDIT:

Since my first shots didn't work, and given your "curiouser" comment above...

This feels a bit like a PendingIntent -- with those, unless you take steps, you will not be able to update extras.

On a whim, try adding a second <intent-filter> to your activity in the manifest, just on some unique action string, and try starting your activity from your receiver using that. Or, just toss some action string into your Intent that the receiver is using for startActivity(), without messing with the manifest.

CommonsWare
Nope, onNewIntent() doesn't get it either...The FLAG_ACTIVITY_NEW_TASK is there because without it I get a RuntimeException:E/AndroidRuntime( 274): java.lang.RuntimeException: Unable to start receiver com.futureplatforms.twitchr.BirdArrivesAlarmReceiver: android.util.AndroidRuntimeException: Calling startActivity() from outside of an Activity context requires the FLAG_ACTIVITY_NEW_TASK flag. Is this really what you want?
Tom Hume
I edited my earlier answer with other things you can try -- commenting here in case you don't get notified on an answer edit...
CommonsWare
OK, retried again. onNewIntent() does get it now - I changed the activity launchmode to singleTask, and it's working exactly as I had hoped. I then overrode newIntent and set a variable which the activity could pick up on elsewhere to determine it had been woken by an alarm.Thankyou!
Tom Hume