android-lifecycle

Sorry for my incomprehension, but I am new in the android development. I have an application with activity A and activity B in it, and I go from activity A to activity B. When I left activity A, the onSaveInstanceState method was called, but when I went back to activity A (from activity B in the same application), the bundle in the onCreate method was null. What can I do, to save the activity A's previous state? I only want to store the data for the application lifetime. Can someone help me with this? Here is my code for Activity A: @Override protected void onCreate(Bundle savedInstanceState)

I appreciate the numerous postings regarding AsyncTask on a rotation change. I have the following problem when using the compatability lib and trying to dismiss a DialogFragment in onPostExecute . I have a fragment which fires of an AsyncTask which displays a progress DialogFragment , then in onPostExecute dismisses the dialog and then potentially throws up another DialogFragment . If when the progress dialog is being displayed I put the application into the background I get the following for my fragment: 1) onPause 2) onSaveInstanceState 3) onPostExecute in which I try to dismiss and invoke a

I know that a fragment's view hierarchy has to be inflated in onCreateView, but what other functionality can be in onCreateView vs. what should wait for onActivityCreated? My current implementation uses separate activities for everything, and a typical activity does most of its work in its onCreate method, including inflating the view, setting the content view, initializing the various widgets with data, setting up listeners, etc. So can this probably all be moved into onCreateView, or should some functions be put into an onActivityCreated method instead? If your view is static, then moving

When I run my app on the debugger, I get the main thread and 3 binder threads. On a button click I call Activity.finish() , which looks like it ends the activity as the UI closes and goes back to the home screen. However, in the debugger, it still shows the main thread and 3 binder threads as " (running) ". I am baffled to why this is happening. Even more so, it is causing my app to call Activity.onResume() when I run it again after exiting the app. I currently override these methods in the Activity, but I call the appropriate super functions in each one: onDestroy() onPause() onResume()

Imagine this scenario: I have a Fragment in a Pager . I try to switch to other apps, so that the Activity owning my pager (and my fragment) will be stopped and temporarily destroyed, eventually. So, when I come back to my Activity, the Fragment 's callbacks onCreate , oncreateview and so forth are called. But none of the Fragment's onDestroy callbacks were called before! It seems that after "onStop" the fragment is destroyed at once. Is it a normal behavior? Is it maybe because the Activity is destroyed without a call to its onDestroy ? invertigo Take a look at this question: Why implement

I created an application which creates and stores files to sdcard. Is there a way to bind the folder with application in order to delete all files when the user runs uninstall on android device? Prashast There's no way for your application to know that it is being uninstalled (without modifying the kernel). All files created in the data/data/your.app.package is deleted automatically upon application uninstall. I don't think anything is cleared from the sdcard. You can do a quick test and find that out. Another approach could be to have another application that checks whether this application