See here:
http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle
onPause is guaranteed to be called, but onStop/onDestroy is not.
If Android needs memory after your activity has been paused, it may kill
your process. This happens without invoking any callbacks.
-- Kostya
07.10.2010 18:51, sdphil пишет:
it should at least call onStop -- because the activity is no longer
visible.
On Oct 7, 7:10 am, Prakash Iyer<thei...@gmail.com> wrote:
It is not required that an onPause is always followed by onStop - in fact if
you press the home key that's what I have seen as the default behavior. This
way if the user goes back to your app, thru the home key press or from
launchpad, the onResume will be called and it will all be much faster than
doing an onCreate which would otherwise have been required.
On Thu, Oct 7, 2010 at 10:06 AM, sdphil<phil.pellouch...@gmail.com> wrote:
I am seeing an issue where when I hit the "back" button, I get the
onPause call, but it isn't followed by onStop and onDestroy.
On most phones, I see this, but on one particular phone (Droid-X), I
don't....
Any ideas?
tia.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com>
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
Kostya Vasilyev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
