Jake,
The 30 minute minimum intervals only applies to updates specified in the
widget's XML file (updateTimeMillis).
You can have alarm-driven (or other event driven) updates as often as
you like, so it's only a question of judgement with respect to battery life.
Android 2.x includes analog clocks that update once a minute, so it
can't be that bad.
Avoiding updates when the screen is off is pretty easy - just use alarm
options without the _WAKEUP (i.e. ELAPSED_REALTIME or RTC). If such
alarm goes of while the phone is asleep, it will be delivered when the
phone wakes up.
-- Kostya
24.06.2010 19:36, Jake Colman пишет:
But in the second example, would it be appropriate to update every
minute? But Android 2.2 only allows an update every 30 minutes. Do you
set an alarm to trigger even minute or would that also drain the
battery? Do you trigger an update only when the screen is turned on?
Can that even be detected?
--
Kostya Vasilev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
NEW! Try asking and tagging your question on Stack Overflow at
http://stackoverflow.com/questions/tagged/android
To unsubscribe from this group, send email to
android-beginners+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
