3 ms·

After you press the 'Back' try holding the 'Home' button down for a second. You should still see the application in the list that comes up. Further, after you

by haseman 17y ago

After you press the 'Back' try holding the 'Home' button down for a second. You should still see the application in the list that comes up. Further, after you receive 'onDestroy()' your activity isn't actually unloaded. It just 'could' be unloaded at some point in the future. Good developers will null all their pointers so the GC can clean up....and we're all good developers right?

metachris 17y ago
If you hold the home button and see a list of apps -- that's the history. Not related to currently running apps. Furthermore, have a look at the Activity lifecycle: http://developer.android.com/guide/topics/fundamentals.html#actlife http://developer.android.com/guide/topics/fundamentals.html#... If your app receives the onDestroy() event, there is no way it will ever recover to a running state.
- deleted 17y ago
  [deleted]
- haseman 17y ago
  In my experience, getting an onDestroy() call doesn't mean your process is about to be terminated/unloaded (this may be different in newer versions?)
- deleted 17y ago
  [deleted]