Yea, I am basically using the activity as my application. Might need to refactor the whole damn thing, create a real Application, Service, and then activities...
Maybe as a short-term hack I can just do nothing in my own activity (I already have an exit button). On Monday, March 19, 2012 9:39:41 AM UTC-4, 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
