http://groups.google.com/group/android-developers/browse_thread/thread/fa2848e31636af70/8d967c32df91a7d1?lnk=gst&q=keeping+a+service+alive
On Jan 30, 3:09 pm, brs <bernhard.r.su...@gmail.com> wrote: > I have an app loosely based on the LocalService example from the SDK > with a controller activity and a long-running, stateful service which > is doing stuff on a periodic handler. The service is also a bit of a > memory hog. > > It seems that the service is sometimes killed by the activity-manager > and immediately restarted. I don't see any stack trace, so I assume it > is not the application crashing but the system doing that, presumably > to claim resources. Is that what is going on here? > > Is there a way to tell the system that this process is kind of > important, even though it has no foreground activity and should only > be killed as a last resort? > > Bernhard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
