lifecycle

I'm using a singleTop Activity to receive intents from a search-dialog via onNewIntent() . What I noticed is that onPause() is called before onNewIntent() , and then afterwards it calls onResume() . Visually: search dialog initiated search intent fired to activity onPause() onNewIntent() onResume() The problem is that I have listeners registered in onResume() that get removed in onPause() , but they are needed inside of the onNewIntent() call. Is there a standard way to make those listeners available? Rodja onNewIntent() is meant as entry point for singleTop activities which already run

I have an activity and I call the finish() method and the activity is not cleared from memory. After calling finish() , I see that the method onDestroy() is executed successfully (and I clear all my variables and stuff in there). Should it be cleared from memory or its how android works? As I understand the LifeCycle of the Activity is finished. And if it keeps the app in memory so it runs faster the 2nd time the user uses it, what kind of objects can I leave in memory to reuse? If I understand correctly, I am suppose to clear everything on onDestroy. Android keeps processes around in case the

I'm trying to wrap my head around scopes in Dagger 2, specifically the lifecycle of scoped graphs. How do you create a component that will be cleaned up when you leave the scope. In the case of an Android application, using Dagger 1.x you generally have a root scope at the application level which you'd extend to create a child scope at the activity level. public class MyActivity { private ObjectGraph mGraph; public void onCreate() { mGraph = ((MyApp) getApplicationContext()) .getObjectGraph() .plus(new ActivityModule()) .inject(this); } public void onDestroy() { mGraph = null; } } The child

I am trying to automatically capture and log Android lifecycle events using ActivityLifecycleCallbacks, however documentation on this matter is scarce, to say the least: public void registerActivityLifecycleCallbacks (Application.ActivityLifecycleCallbacks callback) I don't want to have to extend the Activity class or override the existing lifecycle methods (onCreate, onResume, etc...) I'm looking to have a separate class listening for these events and acting accordingly. Does anyone have any experience in this, or have links to good solid documentation or tutorials on how this works?

The android app I am working on overrides the Application class to store lightweight state (username, gps location, etc) in static vars. Most of this state is set in OnCreate of the launch activity (username retrieved from prefs, location listener runs). Is it safe to rely on the launch activity to initialize the Application class? Are there any cases where the Application class might be re-created without the Launch activity also being created? The question comes up because I ran into a null pointer exception accessing a variable in the Application class on resuming the app after the phone