StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8713795
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
14
CommunityOwnedDate
CreationDate
2012-01-03T14:30:29.760
FavoriteCount
0
LastActivityDate
2015-02-02T11:07:57.773
LastEditDate
2015-02-02T11:07:57.773
LastEditorUserId
985296
OwnerUserId
985296
ParentId
8713361
PostTypeId
2
Score
59
ViewCount
0
LastEditorDisplayName
text
Body
Note: This post has been updated to include the <code>JobScheduler</code> API of the Android Lollipop release. The following is still a viable way, but can be considered deprecated if you're targeting Android Lollipop and beyond. See the second half for the <code>JobScheduler</code> alternative. One way to do recurrent tasks is this: <ul> <li>Create a class <code>AlarmReceiver</code> <pre><code>public class AlarmReceiver extends BroadcastReceiver { @Override public void onReceive(Context context, Intent intent) { Intent myService = new Intent(context, YourService.class); context.startService(myService); } } </code></pre> with <code>YourService</code> being your service ;-)</li> </ul> If you require a wake lock for your Task, it is advisable to extend from <a href="https://developer.android.com/reference/android/support/v4/content/WakefulBroadcastReceiver.html"><code>WakefulBroadcastReceiver</code></a>. Don't forget to add the <code>WAKE_LOCK</code> permission in your Manifest in this case! <ul> <li>Create a Pending Intent</li> </ul> To start your recurrent polling, execute this code in your activity: <pre><code>Intent myAlarm = new Intent(getApplicationContext(), AlarmReceiver.class); //myAlarm.putExtra("project_id", project_id); //Put Extra if needed PendingIntent recurringAlarm = PendingIntent.getBroadcast(getApplicationContext(), 0, myAlarm, PendingIntent.FLAG_CANCEL_CURRENT); AlarmManager alarms = (AlarmManager) this.getSystemService(Context.ALARM_SERVICE); Calendar updateTime = Calendar.getInstance(); //updateTime.setWhatever(0); //set time to start first occurence of alarm alarms.setInexactRepeating(AlarmManager.RTC_WAKEUP, updateTime.getTimeInMillis(), AlarmManager.INTERVAL_DAY, recurringAlarm); //you can modify the interval of course </code></pre> This code sets up an <code>alarm</code> and a canceable <code>pendingIntent</code>. The <code>alarmManager</code> gets the job to repeat the <code>recurringAlarm</code> every day (third argument), but inexact so the CPU does wake up approximately after the interval but not exactly (It lets the OS choose the optimal time, which reduces battery drain). The first time the alarm (and thus the service) is started will be the time you choose to be <code>updateTime</code>. <ul> <li>last but not least: here is how to kill the recurring alarm <pre><code>Intent myAlarm = new Intent(getApplicationContext(), AlarmReceiver.class); //myAlarm.putExtra("project_id",project_id); //put the SAME extras PendingIntent recurringAlarm = PendingIntent.getBroadcast(getApplicationContext(), 0, myAlarm, PendingIntent.FLAG_CANCEL_CURRENT); AlarmManager alarms = (AlarmManager) getApplicationContext().getSystemService(Context.ALARM_SERVICE); alarms.cancel(recurringAlarm); </code></pre></li> </ul> This code creates a copy of your (probably) existing alarm and tells the <code>alarmManager</code> to cancel all alarms of that kind. <ul> <li>of course there is also something to do in the <code>Manifest</code>:</li> </ul> include these two lines <pre><code> < receiver android:name=".AlarmReceiver"></receiver> < service android:name=".YourService"></service> </code></pre> inside the <code>< application></code>-tag. Without it, the system does not accept the start of recurrent alarm of a service. <hr> Starting with the Android Lollipop release, there's a new way of solving this task elegantly. This also makes it easier to only perform an action if certain criteria such as network state are met. <pre><code>// wrap your stuff in a componentName ComponentName mServiceComponent = new ComponentName(context, MyJobService.class); // set up conditions for the job JobInfo task = JobInfo.Builder(mJobId, mServiceComponent) .setPeriodic(mIntervalMillis) .setRequiresCharging(true) // default is "false" .setRequiredNetworkCapabilities(JobInfo.NetworkType.UNMETERED) // Parameter may be "ANY", "NONE" (=default) or "UNMETERED" .build(); // inform the system of the job JobScheduler jobScheduler = (JobScheduler) context.getSystemService(Context.JOB_SCHEDULER_SERVICE); jobScheduler.schedule(task); </code></pre> You may also provide a deadline with <code>setOverrideDeadline(maxExecutionDelayMillis)</code>. To get rid of such a task, just call <code>jobScheduler.cancel(mJobId);</code> or <code>jobScheduler.cancelAll();</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POKeep a Service running even when phone is asleep?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USstefan
UserOwnerUserId
1. USstefan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POKeep a Service running even when phone is asleep?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.