Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For a widget it usually doesn't make sense to keep a service running all the time, you usually update the widget periodically. </p> <p>The easiest way to do this and to be battery efficient is to schedule an intent using <code>AlarmManager</code> and <a href="http://developer.android.com/reference/android/app/AlarmManager.html#setInexactRepeating%28int,%20long,%20long,%20android.app.PendingIntent%29" rel="nofollow">setAlarmInexactRepeating</a>:</p> <blockquote> <p>Schedule a repeating alarm that has inexact trigger time requirements; for example, an alarm that repeats every hour, but not necessarily at the top of every hour. These alarms are more power-efficient than the strict recurrences supplied by setRepeating(int, long, long, PendingIntent), since the system can adjust alarms' phase to cause them to fire simultaneously, avoiding waking the device from sleep more than necessary.</p> </blockquote> <p>The intent should trigger a BroadcastReceiver which in turn should trigger your service to update the widget. Using <code>IntentService</code> is usually a good choice for that.</p> <p>If you need more control over the intent scheduling, you can also set the alarms yourself in when the service is finished with updating the widget, and supply <code>RTC</code> or <code>ELAPSED_REALTIME</code> as the type of alarms. Both types won't wake up the device if it's sleeping. If the device is not sleeping (but locked) you'll effectively piggy back on other events that woke the device.</p> <p>If you really need to update as soon as the device is unlocked, the <a href="http://developer.android.com/reference/android/content/Intent.html#ACTION_USER_PRESENT" rel="nofollow">ACTION_USER_PRESENT</a> broadcast might be what you need, but I'd still recommend to implement that as an addition to scheduling a periodic update.</p>
    singulars
    1. This table or related slice is empty.
    1. PODo tasks when device wakes up
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USbotteaap
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODo tasks when device wakes up
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThe thing is, I have to have the service running. Because I have a countdowntimer in there, that updates the widget every second. I know it maybe doesn't sound good but that's just how I have to do... Shouldn't it be possible to use AlarmManager and then repeat every second? But I'm not sure if that is quite good, because it just doesn't update, it does other stuff too. But I realized that when the service stopped, the user can just resize the widget and the service will start again, exactly as it would stay on.
      singulars
      1. PO
      1. USGuiceU
    2. COHard one, it's not the best use case for a widget, a widget isn't really designed to update that fast. The service will start when a user interacts with the widget, but if you are using an IntentService it would stop when the work is done. In your case it doesn't make much sense since you'll be updating every second anyway even if the widget isn't visible. Catching ACTION_USER_PRESENT sounds like your only option, but I'm not sure if you can declare that in the manifest.
      singulars
      1. PO
      1. USbotteaap
 

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