Dear All,

I've developed an app  that registers a receiver in the onResume()
constructor.

This receiver need not to be deallocated as it processes intent even when
my app is not running on the foreground.

For that reason, the receiver is not deregistered by onPause().

Now, when the app goes in background mode, I get a warning that the
receiver has leaked and, since the 4.1 update, the receiver seems to be
deallocated from memory (was not the case before).

Question: is there a way to ensure that receiver are programmatically
registered at run-time are not deallocated when an app goes in background?

Thanks,

Thank you Mark - this was never very clear in any of the books I've bought
regarding Android programming or on Android website unfortunately.

My next question is as follows:

I've listed a receiver in the manifest as suggested pointing to the
following definition:

public class TESTWAKEUP extends BroadcastReceiver {

@Override
public void onReceive(Context context, Intent intent) {
           Intent rerun=new Intent(context,MyApp.class);
           rerun.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
           rerun.putExtra("fromstaticreceiver", "parameter");
           context.startActivity(rerun);
        }
  }
   }

Now, for some reason, when my activity is brought back to the foreground by
the about receiver (which is triggered by a Service), it does not seem that
the extra parameter is ever receiver:

@Override
public void onCreate(Bundle savedInstanceState) //this is for MyApp
{
Intent argv=getIntent();
Bundle bundle = argv.getExtras();
String fromstaticreceiver=null;
if (bundle != null)
fromstaticreceiver = bundle.getString("fromstaticreceiver");
                Log.d("here:", "fromstaticreceiver=" + fromstaticreceiver);
//always shows null for fromstaticreceiver

My question is:does getIntent() represent the argument of the intent that
originally started the activity or does it reflect intent in the system
that are forcing an activity to come to the foreground?

Many thanks for any feedback on this front.

Rdgs,

On Wed, Aug 15, 2012 at 9:43 AM, Mark Murphy <mmur...@commonsware.com>wrote:

Books and documentation cannot possibly cover the infinite variations
of applications and the ways that they are assembled.

I would phrase it as the one that originally created the activity.

No. I think that you will be called with onNewIntent() in this case,
instead of onCreate(), and the Intent supplied to onNewIntent() will
be the one used by your startActivity() from the BroadcastReceiver. I
have not tried this in conjunction with a BroadcastReceiver and
FLAG_ACTIVITY_NEW_TASK -- at least not recently -- and so I am not
100% certain about onNewIntent() for your scenario.

--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training in NYC: http://marakana.com/training/android/