String wrote: > I'm already using alarms to drive my widget updates. Problem is, > alarms are unreliable, especially with the proliferation of task > killer apps which abuse the API (see > http://groups.google.com/group/android-developers/browse_thread/thread/3f87972d1f99ee81). > People have these running in the background, then I get complaints > that my clock has stopped. So I've been using updatePeriodMillis as a > backup, checking that my widget update alarm is still running every so > often.
It would appear that the app widget framework uses AlarmManager for updatePeriodMillis, based upon my interpretation of the AppWidgetService.java code. > My concern is also for other widget developers; this was not a well > publicized change in Donut, and there's probably some head-scratching > about a feature that used to work fine in Cupcake but doesn't now. > Hopefully less after threads like this, though. Indubitably! -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Development Wiki: http://wiki.andmob.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
