On Sat, Aug 27, 2011 at 1:43 PM, kypriakos <[email protected]> wrote: > > Aha ... With "eventually" you mean that if Android does not need > RAM the process could be around for a while (or until the phone > is rebooted)?
Yes. How long will depend on what's all going on. I would expect it to be gone within an hour or so, given various services that will wake up periodically to do a bit of polling. Quite possibly it will be gone much more quickly. > Is finish() synchronous and it occurs immediately? No, and no. finish() will happen very quickly, but it is not synchronous (i.e., a blocking call) and therefore cannot be construed strictly as "immediately". > I am wondering if it is possible to exit the activity but > subsequently > ask Android to terminate it immediately ... If by "it", you mean "the process", please do not do this. Please let Android terminate it when it is ready to. Whatever problem you are trying to solve can be solved better some other way. > On a different note - how far back do your books go? Did you cover > 1.6 and 2.1? Yes. 1.5, even. Mostly, I cover "Android" and try to point out when various new-ish features were added to the OS. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 3.1 Programming Books: http://commonsware.com/books -- 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
