If your intention is to call another activity in order to perform some work -- do you control that activity? Start it "for result" rather than simply starting it. That way you'll get a callback (with its result) when it finishes.
I agree with Mark, you should not care about what activities outside of your control do. You should code as if they don't exist, and if there's some reason to consider the user "logged out", it should not be based on what activity is current. Is there some use case you can think of that justifies taking special action just because the user, for example, opened their messaging app to reply to the message they just received? -- 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
