I see the thread has progressed quite a bit from this original question, but I still feel the need to answer this original question clearly: you should certainly not "override the onDestroy". If it gets called the need for you to release resources is genuine, you should just do it.
Others have already mentioned using Service, this is certainly going to play a major part in your final solution, however you decide to factor your business logic between the Service and the Activity (or Activities). Providing a place in the background for things to go on for a long time even when the Activity goes away is the major purpose of having a Service. On Monday, March 19, 2012 6:39:41 AM UTC-7, RedBullet wrote: > > My application is a GPS nav type app. Needs to be running when I am doing > a route. > > It appears that the system can decide to kill my process (I see onDestroy) > get called for example. > > So, what's the right policy here, should I over-ride the onDestroy and > just have it do nothing, but provide a way to manually kill the activity? > -- 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
