That's what the task killers do.  Don't use them if you don't want this to
happen.  You can't get around this.  The API they are using is intended for
the user to explicitly stop everything about an app.

On Sat, Nov 21, 2009 at 6:53 PM, shahzad ahmad <[email protected]>wrote:

> Hi,
>     I'm just investing how crashed services are restarted. I've developed a
> simple service and use a taskkiller from market place to kill the
> application. Following are the logs after application is killed
>
> "Uninstalling the process test.sys"
> "Force removing process ProcessRecord{432d6ad0 252:test.sys/10041}
> (test.sys/10041)"
> "Scheduling restart of crashed service test.sys/.testservice in 5000ms"
> "Sending signal. PID: 252 SIG: 9"
>
> But the service is never started. Can anybody tell why service is not
> starting? Do i need to put any flag in manifest file for service restart to
> work?
>
> Regards,
> shaz
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<android-developers%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
[email protected]

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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to