Regarding this: http://developer.android.com/guide/topics/fundamentals/activities.html
Why does the doc say this, "For example, if your activity has a thread running in the background to download data from the network, it might create that thread in onCreate() and then stop the thread in onDestroy()." - onDestroy() is not guaranteed to be called, so if you create a Thread in onCreate(), the thread may never be stopped. And, why does the doc say this, " For example, you can register a BroadcastReceiver in onStart() to monitor changes that impact your UI, and unregister it in onStop() when the user can no longer see what you are displaying. The system might call onStart() and onStop() multiple times during the entire lifetime of the activity, as the activity alternates between being visible and hidden to the user." - onStop() is not guaranteed to be called if the activity is killed by Android, so your broadcast receiver would never be unregistered. Wouldn't the developer need to perform all of these functions in onResume/onPause() instead? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
