Hi, If I follow the lifecycle docs correctly, an Activity won't get notified if it's force killed for memory? Example: In my app, I create a maps driving intent. I can see in the log output say something like:
I/ActivityManager( 76): Low Memory: No more background processes When the user returns back to my app (via the back button), it's in an inconsistent state - it's expecting some data I store in a global singleton to be around, which is no longer present. So I guess that my Activity was killed. But was does onDestroy() get called, so we have a chance to clean up? Or do we just have to write safeguards in onCreate () to check for a force-kill as mentioned in this post?: http://groups.google.com/group/android-developers/browse_thread/thread/1b342cd8f940d98c/0958bfede0b2b87a?lnk=gst&q=kill+low+memory#0958bfede0b2b87a Thanks -- 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
