onDestroy() generally doesn't get called to free up resourced; most usually processes are killed to accomplish this.
The platform tries to keep the process hosting the home app running, so that pressing home won't take a long time to return to the launcher. Of course under enough memory stress it will get killed. On Tue, Apr 24, 2012 at 2:41 PM, Josh <[email protected]> wrote: > let me rephrase this... > > I have built a default launcher app that is specifically for the > Samsung Galaxy Tab 10.1. I have launched many apps in order to have > android call onDestroy() on my launcher app but I have not been > successful in doing this. > > Does anyone know if Android ever calls onDestroy() on the default > launcher in order to free up resources? > > On Apr 24, 10:28 am, Josh <[email protected]> wrote: > > Does Android ever stop the defaultlauncherin order to free up > > resources? > > -- > 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 > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
