Hi Nicolas,
Thanks for the feedback. I've double checked the logs and I don't see
anything about TasKiller when the process has died.
In the meantime I've read the following thread about developers
complaining about Task killers applications (not yours especially).
http://groups.google.com/group/android-developers/browse_thread/thread/3f87972d1f99ee81/e28b5180bb404a79
(Our users complain that widget updates stop too)
So, I've uninstalled TaskKiller, run GoogleMaps to generate a process
kill from Android. Here are the logs just after GoogleMaps starting:
[...]
11-27 19:25:47.494: INFO/ActivityManager(74): Process abc (pid 3509)
has died.
[...]
11-27 19:26:00.044: INFO/ActivityManager(74): Start proc abc for
service abc/.xyz.RefreshService: pid=3603 uid=10033 gids={3003, 1015}
[...]
11-27 19:26:00.424: INFO/abc.xyz.RefreshService(3603): RefreshService
started (abc.xyz.refreshserv...@431f1d38)
[...]
It seems to work now. The only difference is that the following trace
does not appear:
"Scheduling restart of crashed service abc/.xyz.RefreshService in
5000ms".
Could it be a bug in your application ? or in the Android API you're
using to monitor running processes ?
It may prevent a service from restart. Is there any test I can do to
make sure ?
Thanks again.
On Nov 27, 7:25 pm, Nicolas Thibaut <[email protected]> wrote:
> Hi, Taskiller use ActivityManager to "kill" process (there is no kill
> but uninstall process).
>
> If I kill taskiller itselfs, the log are:
>
> 11-27 19:16:58.952 I/ActivityManager( 75): Displayed activity
> com.tni.TasKiller/.TasKiller: 2023 ms (total 2023 ms)
> 11-27 19:16:59.032 I/ActivityManager( 75): Process
> com.android.settings (pid 4361) has died.
> 11-27 19:17:05.212 D/dalvikvm( 2816): GC freed 2448 objects / 115688
> bytes in 175ms
> 11-27 19:17:12.842 D/ActivityManager( 75): Uninstalling process
> com.tni.TasKiller
> 11-27 19:17:12.842 D/ActivityManager( 75): Force removing process
> ProcessRecord{43678608 4341:com.tni.TasKiller/10030}
> (com.tni.TasKiller/10030)
>
> If your service die without this log, Taskiller is not guilty !
> And if your service is killed by taskiller : the user HOPE it will
> NEVER restart.
>
> On Nov 27, 7:01 pm, Derek <[email protected]> wrote:
>
> > Hi Diane,
>
> > We've have exactly the same problem. We have TasKiller v2.2 installed
> > but we DO NOT use it to kill our app.
> > However, our service (running every one minute thanks to AlarmManager)
> > never restarts after process has died.
> > Here are the log extracted today on my HTC device under 1.6:
> > [...]
> > 11-27 18:14:00.463: INFO/abc.RefreshService(1482): Alarm planned in
> > 60000 milliseconds at 1259342100000 (abc.refreshserv...@431e8178 -
> > PendingIntent{431f71f8: android.os.binderpr...@431f71b0})
> > 11-27 18:14:00.463: INFO/abc.RefreshService(1482): RefreshService
> > stopping (abc.refreshserv...@431e8178)
> > 11-27 18:14:00.463: INFO/ActivityManager(74): Stopping service:
> > abc/.xyz.RefreshService
> > [...]
> > 11-27 18:15:07.629: INFO/ActivityManager(74): Process abc (pid 1482)
> > has died.
> > 11-27 18:15:07.679: WARN/ActivityManager(74): Scheduling restart of
> > crashed service abc/.xyz.RefreshService in 5000ms
> > [...]
> > 11-27 18:19:26.131: INFO/ActivityManager(74): Start proc abc for
> > service abc/.xyz.RefreshService: pid=1536 uid=10033 gids={3003, 1015}
> > 11-27 18:19:26.241: INFO/dalvikvm(1536): Debugger thread not active,
> > ignoring DDM send (t=0x41504e4d l=38)
> > [...]
>
> > Do you mean that the problem could come from TaskKiller application ?
> > Once problem has occurred I still can see our app in TasKiller as
> > Italic/grayed (which means that a service is running in background) or
> > yellow.
>
> > Thanks.
>
> > On Nov 22, 8:53 pm, Dianne Hackborn <[email protected]> wrote:
>
> > > 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
