Not really. If you are building your own device, you can make new
persistent processes like the existing phone process (look at its manifest
to see how it is set up), but unless you have a lot of memory this is
strongly discouraged because of the resources it uses. In a stock platform
build, that is the only application process that has any kind of
persistence.
On Mon, Apr 20, 2009 at 2:42 PM, va vandra.w...@gmail.com wrote:
The android manifest entry android:persistent and the setPersistent()
api allows Activities be marked as persistent, so that they do not
get killed by the low memory killer. Does the framework provide any
mechanism to mark a Service as persistent, so that LMK does not affect
it?
Thanks,
V
--
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-framework group.
To post to this group, send email to android-framework@googlegroups.com
To unsubscribe from this group, send email to
android-framework+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-framework?hl=en
-~--~~~~--~~--~--~---
