Databases
StackOverflow2013
Postsdbo
POBackground Service getting killed in android
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBackground Service getting killed in android
    primarykey
    data
    text
    <p>We have developed an Android Application which involves a service in the background. To implement this background service we have used <code>IntentService</code>. We want the application to poll the server every <code>60 seconds</code>. So in the <code>IntentService</code>, the server is polled in a while loop. At the end of the while loop we have used <code>Thread.sleep(60000)</code> so that the next iteration starts only after 60 seconds.<bR> But in the <code>Logcat</code>, I see that sometimes it takes the application more than 5 minutes to wake up (come out of that sleep and start the next iteration). It is never <code>1 minute</code> as we want it to be.</p> <p>What is the reason for this? Should background Services be implemented in a different way?</p> <p><strong>Problem2</strong></p> <p>Android kills this background process (intent service) after sometime. Can't exactly say when. But sometimes its hours and sometimes days before the background service gets killed. I would appreciate it if you would tell me the reason for this. Because Services are not meant to be killed. They are meant to run in background as long as we want it to.</p> <p><strong>Code :</strong></p> <pre><code>@Override protected void onHandleIntent(Intent intent) { boolean temp=true; while(temp==true) { try { //connect to the server //get the data and store it in the sqlite data base } catch(Exception e) { Log.v("Exception", "in while loop : "+e.toString()); } //Sleep for 60 seconds Log.v("Sleeping", "Sleeping"); Thread.sleep(60000); Log.v("Woke up", "Woke up"); //After this a value is extracted from a table final Cursor cur=db.query("run_in_bg", null, null, null, null, null, null); cur.moveToLast(); String present_value=cur.getString(0); if(present_value==null) { //Do nothing, let the while loop continue } else if( present_value.equals("false") || present_value.equals("False") ) { //break out of the while loop db.close(); temp=false; Log.v("run_in_bg", "false"); Log.v("run_in_bg", "exiting while loop"); break; } } } </code></pre> <p>But whenever the service is killed, it happens when the the process is asleep. The last log reads - <code>Sleeping : Sleeping</code>. Why does the service gets killed?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDACrosby
    1. USAshwin
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBackground Service getting killed in android
      1. USAshwin
      1. VTBountyStart
    2. VO
      singulars
      1. POBackground Service getting killed in android
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBackground Service getting killed in android
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou should use a `Timer` instead and schedule it at a fixed rate instead of using `Thread.sleep()` in a while loop.
      singulars
      1. POBackground Service getting killed in android
      1. USMxyk
    2. CO@MikeGates : why?
      singulars
      1. POBackground Service getting killed in android
      1. USAshwin
    3. COBecause they allow you to do exactly what you're trying to do - repeat a task on a certain interval. Not necessarily an answer to your question, but a suggestion (hence why I'm posting a comment, not an answer). There's also always the chance that using `Thread.sleep()` is the reason why it's taking 5 minutes - something maybe a `Timer` may not do? I figured it'd be worth a shot.
      singulars
      1. POBackground Service getting killed in android
      1. USMxyk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload