On Wed, Jun 16, 2010 at 9:23 PM, Robert Macaulay <[email protected]> wrote: > This works, I see my app run over and over. I see my app being killed, and > respawned via alarmReceiver. This all works great, but it randomly ceases. > No exceptions in the log. I luckily have the log showing the last running of > the service. The service runs, exits cleanly, and never runs again. I > originally thought it could be that my msTillNext was negative, but the docs > say that if the time is in the past, it will run immediately.
You may want to test that anyway. For example, make sure that msTillNext is at least, say, 10, rather than smaller or negative. It wouldn't be the first time that the docs were wrong, and it shouldn't have any material impact on your actual app functionality. > It is a moto droid, running 2.1. Any suggestions? I'm about to write an > alarm watchdog alarm to reschedule. or use setRepeating and store something > in the DB to notice the dupes. You could try adb shell dumpsys. Redirect the output to a file, then look for the line starting with: DUMP OF SERVICE alarm: You may see signs of your alarms in there. See if you can determine any patterns of what the dump looks like when the next alarm will succeed versus when it will fail. -- Mark Murphy CommonsWare [email protected] 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 [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
