I realized this right after I posted, by running a bunch of other apps while my app was still running. It seems like 'setPersistent' on the activity should most likely prevent this. Any ideas?
Thanks again. On Jan 23, 8:36 am, Torgny <torgny.bj...@gmail.com> wrote: > Your application background process might get killed if you run > another application that takes up a lot of memory, for instance the > browser with several windows. As far as I understand it, the > application in the foreground takes priority as far as memory and > processing power goes over services and threads. > > On Jan 23, 9:15 am, g1bb <corymgibb...@gmail.com> wrote: > > > > > Hello, > > > I've created an app that functions as a countdown timer via a thread, > > a wakelock, and a handler back to my activity. My question is, what > > will cause my thread to die, or app to not be running in memory > > anymore? I've had this happen once, and can't seem to recreate it > > again. > > > Thanks in advance!- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
