On Oct 23, 1:54 pm, Mark Murphy <[email protected]> wrote: > Set your own alarm using AlarmManager to supplement or replace > updatePeriodMillis in the next edition of your app. You don't need to > use it; it is there mostly as a convenience AFAICT.
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. 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. String --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
