Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7936073
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 3, 20262026-06-03T22:06:03+00:00 2026-06-03T22:06:03+00:00

When I use an app such as Go Power Master to forcibly kill Services

  • 0

When I use an app such as “Go Power Master” to forcibly kill Services running on my Android phone, not all Services restart with the same delay. Why is this and how do I reduce the time taken for my Service to restart?

The Facebook Service is a perfect example. Below is its LogCat output while it was killed 3 times in succession. Notice the restart times in bold: 14992ms, 5000ms, 14963ms.

My Service is not treated so well. Below is its LogCat output while it was killed 3 times in succession. Notice the much larger restart times in bold: 23358ms, 93432ms, 373728ms.

The complete source code for this project is on GitHub.
https://github.com/ccoffey/NUIMWiFi

Facebook LogCat

05-10 14:09:33.381: I/ActivityManager(192): Killing proc 7280:com.facebook.katana/10077: kill background
05-10 14:09:33.381: W/ActivityManager(192): Scheduling restart of crashed service com.facebook.katana/.service.MediaUploadService in 14992ms
05-10 14:09:48.412: I/ActivityManager(192): Start proc com.facebook.katana for service com.facebook.katana/.service.MediaUploadService: pid=7847 uid=10077 gids={3003, 1006, 1015}
05-10 14:09:48.568: I/ActivityThread(7847): Pub com.facebook.katana.provider.LoggingProvider: com.facebook.katana.provider.LoggingProvider
05-10 14:09:48.592: I/ActivityThread(7847): Pub com.facebook.katana.provider.KeyValueProvider: com.facebook.katana.provider.KeyValueProvider
05-10 14:09:48.592: I/ActivityThread(7847): Pub com.facebook.katana.provider.CacheProvider: com.facebook.katana.provider.CacheProvider
05-10 14:09:48.592: I/ActivityThread(7847): Pub com.facebook.katana.provider.MailboxProvider: com.facebook.katana.provider.MailboxProvider
05-10 14:09:48.599: I/ActivityThread(7847): Pub com.facebook.katana.provider.UserStatusesProvider: com.facebook.katana.provider.UserStatusesProvider
05-10 14:09:48.599: I/ActivityThread(7847): Pub com.facebook.katana.provider.EventsProvider: com.facebook.katana.provider.EventsProvider
05-10 14:09:48.607: I/ActivityThread(7847): Pub com.facebook.katana.provider.NotificationsProvider: com.facebook.katana.provider.NotificationsProvider
05-10 14:09:48.607: I/ActivityThread(7847): Pub com.facebook.katana.provider.UserValuesProvider: com.facebook.katana.provider.UserValuesProvider
05-10 14:09:48.607: I/ActivityThread(7847): Pub com.facebook.katana.provider.PagesProvider: com.facebook.katana.provider.PagesProvider
05-10 14:09:48.607: I/ActivityThread(7847): Pub com.facebook.katana.provider.MobileEventLogProvider: com.facebook.katana.provider.MobileEventLogProvider
05-10 14:09:48.607: I/ActivityThread(7847): Pub com.facebook.katana.provider.PushNotificationsProvider: com.facebook.katana.provider.PushNotificationsProvider
05-10 14:09:48.615: I/ActivityThread(7847): Pub com.facebook.katana.provider.PhotosProvider: com.facebook.katana.provider.PhotosProvider
05-10 14:09:48.615: I/ActivityThread(7847): Pub com.facebook.katana.provider.ConnectionsProvider: com.facebook.katana.provider.ConnectionsProvider
05-10 14:09:48.623: I/ActivityThread(7847): Pub com.facebook.orca.notify.FbandroidMessagesForegroundProvider: com.facebook.orca.notify.FbandroidMessagesForegroundProvider
05-10 14:09:48.639: D/ACRA(7847): ACRA is enabled for com.facebook.katana, intializing…
05-10 14:09:48.654: D/ACRA(7847): Looking for error files in /data/data/com.facebook.katana/app_acra-reports
05-10 14:09:48.701: W/nalizableReferenceQueue(7847): at com.facebook.orca.inject.binder.AnnotatedBindingBuilderImpl.a(AnnotatedBindingBuilderImpl.java:22)
05-10 14:09:48.701: W/nalizableReferenceQueue(7847): at com.facebook.orca.app.FbBaseModule.a(FbBaseModule.java:73)
05-10 14:09:48.701: W/nalizableReferenceQueue(7847): at com.facebook.orca.inject.AbstractModule.a(AbstractModule.java:19)
05-10 14:09:48.701: W/nalizableReferenceQueue(7847): at com.facebook.orca.inject.FbInjectorImpl.a(FbInjectorImpl.java:61)
05-10 14:09:48.701: W/nalizableReferenceQueue(7847): at com.facebook.orca.inject.FbInjectorImpl.(FbInjectorImpl.java:41)
05-10 14:09:48.701: W/nalizableReferenceQueue(7847): at com.facebook.orca.inject.FbInjector.a(FbInjector.java:40)
05-10 14:09:48.701: W/nalizableReferenceQueue(7847): at com.facebook.katana.FacebookApplication.onCreate(FacebookApplication.java:75)
05-10 14:09:48.928: I/SqliteDatabaseCpp(7847): sqlite returned: error code = 21, msg = misuse at line 105099 of [8609a15dfa], db=/data/data/com.facebook.katana/databases/prefs_db
05-10 14:09:53.810: I/ActivityManager(192): Killing proc 7847:com.facebook.katana/10077: kill background
05-10 14:09:53.810: W/ActivityManager(192): Scheduling restart of crashed service com.facebook.katana/.service.MediaUploadService in 5000ms
05-10 14:09:58.842: I/ActivityManager(192): Start proc com.facebook.katana for service com.facebook.katana/.service.MediaUploadService: pid=7890 uid=10077 gids={3003, 1006, 1015}
05-10 14:09:59.053: I/ActivityThread(7890): Pub com.facebook.katana.provider.LoggingProvider: com.facebook.katana.provider.LoggingProvider
05-10 14:09:59.060: I/ActivityThread(7890): Pub com.facebook.katana.provider.KeyValueProvider: com.facebook.katana.provider.KeyValueProvider
05-10 14:09:59.060: I/ActivityThread(7890): Pub com.facebook.katana.provider.CacheProvider: com.facebook.katana.provider.CacheProvider
05-10 14:09:59.076: I/ActivityThread(7890): Pub com.facebook.katana.provider.MailboxProvider: com.facebook.katana.provider.MailboxProvider
05-10 14:09:59.076: I/ActivityThread(7890): Pub com.facebook.katana.provider.UserStatusesProvider: com.facebook.katana.provider.UserStatusesProvider
05-10 14:09:59.076: I/ActivityThread(7890): Pub com.facebook.katana.provider.EventsProvider: com.facebook.katana.provider.EventsProvider
05-10 14:09:59.076: I/ActivityThread(7890): Pub com.facebook.katana.provider.NotificationsProvider: com.facebook.katana.provider.NotificationsProvider
05-10 14:09:59.076: I/ActivityThread(7890): Pub com.facebook.katana.provider.UserValuesProvider: com.facebook.katana.provider.UserValuesProvider
05-10 14:09:59.076: I/ActivityThread(7890): Pub com.facebook.katana.provider.PagesProvider: com.facebook.katana.provider.PagesProvider
05-10 14:09:59.084: I/ActivityThread(7890): Pub com.facebook.katana.provider.MobileEventLogProvider: com.facebook.katana.provider.MobileEventLogProvider
05-10 14:09:59.084: I/ActivityThread(7890): Pub com.facebook.katana.provider.PushNotificationsProvider: com.facebook.katana.provider.PushNotificationsProvider
05-10 14:09:59.084: I/ActivityThread(7890): Pub com.facebook.katana.provider.PhotosProvider: com.facebook.katana.provider.PhotosProvider
05-10 14:09:59.084: I/ActivityThread(7890): Pub com.facebook.katana.provider.ConnectionsProvider: com.facebook.katana.provider.ConnectionsProvider
05-10 14:09:59.092: I/ActivityThread(7890): Pub com.facebook.orca.notify.FbandroidMessagesForegroundProvider: com.facebook.orca.notify.FbandroidMessagesForegroundProvider
05-10 14:09:59.154: D/ACRA(7890): ACRA is enabled for com.facebook.katana, intializing…
05-10 14:09:59.185: D/ACRA(7890): Looking for error files in /data/data/com.facebook.katana/app_acra-reports
05-10 14:09:59.232: W/nalizableReferenceQueue(7890): at com.facebook.orca.inject.binder.AnnotatedBindingBuilderImpl.a(AnnotatedBindingBuilderImpl.java:22)
05-10 14:09:59.232: W/nalizableReferenceQueue(7890): at com.facebook.orca.app.FbBaseModule.a(FbBaseModule.java:73)
05-10 14:09:59.232: W/nalizableReferenceQueue(7890): at com.facebook.orca.inject.AbstractModule.a(AbstractModule.java:19)
05-10 14:09:59.232: W/nalizableReferenceQueue(7890): at com.facebook.orca.inject.FbInjectorImpl.a(FbInjectorImpl.java:61)
05-10 14:09:59.232: W/nalizableReferenceQueue(7890): at com.facebook.orca.inject.FbInjectorImpl.(FbInjectorImpl.java:41)
05-10 14:09:59.232: W/nalizableReferenceQueue(7890): at com.facebook.orca.inject.FbInjector.a(FbInjector.java:40)
05-10 14:09:59.232: W/nalizableReferenceQueue(7890): at com.facebook.katana.FacebookApplication.onCreate(FacebookApplication.java:75)
05-10 14:10:44.826: I/ActivityManager(192): Killing proc 7890:com.facebook.katana/10077: kill background
05-10 14:10:44.826: W/ActivityManager(192): Scheduling restart of crashed service com.facebook.katana/.service.MediaUploadService in 14963ms

MyService LogCat

I/ActivityManager( 192): Killing proc 8556:ie.cathalcoffey.android/10033: kill background
I/ActivityManager( 192): Killing proc 8606:ie.cathalcoffey.android:remote/10033: kill background
W/ActivityManager( 192): Scheduling restart of crashed service ie.cathalcoffey.android/.MyService in 23358ms
I/ActivityManager( 192): Start proc ie.cathalcoffey.android:remote for service ie.cathalcoffey.android/.MyService: pid=8726 uid=10033 gids={3003}
I/ActivityManager( 192): Killing proc 8726:ie.cathalcoffey.android:remote/10033: kill background
W/ActivityManager( 192): Scheduling restart of crashed service ie.cathalcoffey.android/.MyService in 93432ms
I/ActivityManager( 192): Start proc ie.cathalcoffey.android:remote for service ie.cathalcoffey.android/.MyService: pid=9063 uid=10033 gids={3003}
I/ActivityManager( 192): Killing proc 9063:ie.cathalcoffey.android:remote/10033: kill background
W/ActivityManager( 192): Scheduling restart of crashed service ie.cathalcoffey.android/.MyService in 373728ms

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-03T22:06:04+00:00Added an answer on June 3, 2026 at 10:06 pm

    The solution to this problem seems to be the following. Cause the OS to believe that it has killed a Service that was doing work. It then appears to restart that Service with a smaller delay.

    I have now edited my Service to start an AsyncTask which simply loops forever and calls Thread.sleep(100)

    Now when I forcibly kill my Service, I see very similar restart times that I do for the Facebook Service: 5000ms, 24713ms, 14997ms, 54912ms, 14988ms.

    Please prove me wrong or right but as it stands this seems to solve my problem.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

In my web app I use several asmx (Web Services) from the same provider,
In my app I use a static database to store all counties and census
I have published a test app with such manifest <?xml version=1.0 encoding=utf-8?> <manifest xmlns:android=http://schemas.android.com/apk/res/android
I have created a WCF service which does not use the app.config to configure
I'm developing an android app for 2.2 ver. My app must hav such structure:
I need to write an app in such a way that it should not
if your app use this solution , do do you plan port the app
Tried following the instructions here: How to use Google app engine with my own
The Salesforce.com API seems to assume that you will always use the app as
During the use of my app, the user should be able to start, stop,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.