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 6105843
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T14:00:55+00:00 2026-05-23T14:00:55+00:00

I notice that applications like Skype use a service which basically runs 24×7, without

  • 0

I notice that applications like Skype use a service which basically runs 24×7, without getting killed at all. You cannot even manually kill it using task killers ( you can kill them by going to running services and kill service ). How is this implemented?

I find that in Android 2.3, my service gets killed after running for sometime. onDestroy() is never called even if I start the service with START_STICKY. However this works fine on my 2.1 device, that is the service doesnt get killed.

Thanks

  • 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-05-23T14:00:56+00:00Added an answer on May 23, 2026 at 2:00 pm

    How is this implemented?

    Based on the Skype screenshots that show a Notification icon, then they are most likely using startForeground().

    I find that in Android 2.3, my service gets killed after running for sometime.

    That is perfectly normal.

    First, most Android applications do not really need a service that “basically runs 24×7”. Users do not like such services, which is why task killers and the Running Services screen and the auto-kill logic in the OS exist. The only reason a service should be running “24×7” is if is delivering value every microsecond. VOIP clients, like Skype, will deliver value every microsecond, as they are waiting for incoming phone calls. Most Android applications do not meet this criterion.

    If your service is running constantly, but for a user-controlled period (e.g., a music player), startForeground() is a fine solution.

    Otherwise, I would rather that you find a way to eliminate the service that “basically runs 24×7”, switching to a user-controllable polling system using AlarmManager, so your service is generally not in memory except when it is delivering value.

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

Sidebar

Related Questions

I have noticed that applications like GPS Status get a fix pretty quickly. When
When thinking about iPhone/iPad applications security, I can notice that there is: Widely available
What is the best approach to implement tabs that look like web applications on
I'm designing a hosted software-as-a-service application that's like a highly specialized version of 37Signal's
I notice that (too) many applications on my Android phone require full internet access.
In a lot of examples, I notice that that they are created like this:
I notice many applications like firefox allow me to watch part of a video
As a two-monitor user at work, I've noticed that applications behave differently with regards
I've noticed that a handful of WCF applications choose to break their objects apart;
i've noticed that plenty of games / applications (very common on mobile builds) pack

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.