If you haven't already read it you should see http://developer.android.com/guide/topics/fundamentals.html#actlife
Your activity will always be "paused" when it isn't in view. Also note in the last paragraph on that page: "Because a process running a service is ranked higher than one with background activities, an activity that initiates a long-running operation might do well to start a service for that operation, rather than simply spawn a thread — particularly if the operation will likely outlast the activity." On Nov 30, 2:28 pm, DulcetTone <[email protected]> wrote: > I see no means by which my activity can pop itself off the activity > stack to return the user to the one he was using before it was > invoked. Is there one? > > My purpose is that my app has some data structures built from data > provider queries that take 5-15 seconds to assemble and I don't want a > lot of latency if it is used in a few one-shot purposes in rapid > succession. I'm more than willing to let the system ask my app to > die, but I'd like to keep warmed and ready otherwise. > > Thanks in advance. > > tone -- 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
