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
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,
