You should catch the back key, and do what behavior you want when it is pressed.
Do not do this kind of stuff in onStop(). It is only going to cause you pain. For example, the the user receives a phone call when in your app, the in call activity will be displayed, you will be stopped. When they press home, you will be stopped. When they use the status bar to switch to another app via its notification, you will be stopped. On Tue, Apr 27, 2010 at 12:45 AM, Xiongzh <[email protected]> wrote: > But it's totally transparent to the customer, isn't it? > The activity should be in the very top of the Android stacks. So it > would be bring up again quickly. > > On Apr 27, 3:28 pm, patbenatar <[email protected]> wrote: > > > > Restarting the Activity in onStop sounds incredibly intrusive for your > > user experience. > > > > -Nick > > > > -- > 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]<android-developers%[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
