<robert.macaulay@gmail.com> wrote:
> Well, the < 10 ms check didn't help. dumpsys alarm just shows that it used
> to run, but nothing currently scheduled.
> I have no exceptions logged, and the reschedule is in a finally block.
What is the approximate duration between your alarms (the ones you
have been doing with set())? I'd like to take a shot at trying to
reproduce your problem.
Also, what device(s) are you testing this on?
--
Mark Murphy
CommonsWare
mmurphy@commonsware.com
http://commonsware.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment