ondestroy

I've got an Android application which maintains state regarding distance traveled, time elapsed, etc. This state I can conveniently store in an object and store a reference to that object in the Bundle when Android calls onDestroy() when the user changes the screen orientation, then restore the state in onCreate(Bundle savedBundle). However, I also have some state in the Buttons and EditText objects on the screen that I want to persist through screen orientations. For example, in onStart(Bundle savedBundle) I call: _timerButton.setBackgroundColor(Color.GREEN); _pauseButton.setBackgroundColor

I am reading ListFragment source code and I see this implementation: ListAdapter mAdapter; ListView mList; View mEmptyView; TextView mStandardEmptyView; View mProgressContainer; View mListContainer; CharSequence mEmptyText; boolean mListShown; /** * Detach from list view. */ @Override public void onDestroyView() { mHandler.removeCallbacks(mRequestFocus); mList = null; mListShown = false; mEmptyView = mProgressContainer = mListContainer = null; mStandardEmptyView = null; super.onDestroyView(); } In this function, Google developers set Null to all view fields that declared in ListFragment and

I'm developing an android app using bluetooth communication (using a propetary protocol) and I need to catch the moment when the app is killed. I wanted to use the "onDestroy()" method but it isn't called every time the app is killed. I noticed that it is called when I press the back button and, only sometimes, when I kill the app from the task manager. The question is: How can I catch the moment before the app is killed? Here is the code I tried to use: @Override public void onDestroy() { sendMessage(msg); Log.d("SampleApp", "destroy"); super.onDestroy(); } @Override public void finish(){

This question already has an answer here: what exactly Activity.finish() method is doing? 12 answers Simple question: can you be sure that finish() will call onDestroy() ? I haven't found any confirmation on this. Simple question: can you be sure that finish() will call onDestroy()? First, this answer assumes that you are referring to Android's Activity class and its finish() method and onDestroy() lifecycle method. Second, it depends upon your definition of "sure": Your process could be terminated in between finish() and onDestroy() , for reasons independent of whatever is triggering the call

In my app, I use a service to communicate with our server. The Service spawns several message queue threads to deal with tasks with different priorities. This model has been used for about one year without big issues. However, recently, I found some time the onCreate of my service class are called multiple times. onDestroy is never called between two onCreate calls. Therefore, I did not get chance to kill existing threads. Once this behavior happens, the service has duplicate threads inside. The only thing I have changed is to run the service as foreground service is a user signs in the app. I

My application gets killed each time that it comes back from the screen-off-state. I fetch all the information that my app does, but I can't find out why it calls onDestroy. It's the first time I'm seeing this behavior in my applications. My main activity extends tabActivity because it contains a tabhost. I've read that it has to extend it or it will FC. I'm not sure if my issue is related to this?! Oh and it implements Observer but this should be no problem. Here are the logs: 07-21 09:57:53.247: VERBOSE/###(13180): onResume 07-21 09:57:53.267: VERBOSE/###(13180): onPause 07-21 09:57:59.967: