On Thu, Mar 11, 2010 at 1:59 PM, Achanta <krishna.acha...@gmail.com> wrote:
> Yes I considered using singleton pattern but again I still face with > the issue where onDestroy will be called after onCreate when it should > not happen and I need to keep track of that case also. So I would just > go with AsynkTask but take care that my app is not eating up the > battery. > As I said, it is not true that this "should not happen." In fact it can and will happen. The system bug here just makes it (a lot) more likely to happen. And for anyone wondering, the singleTask or singleInstance launch modes do not impact this, that is not what they are for. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
