Great Tip, Dianne. Also very helpful for my other issue with notifications
(adb shell dumpsys notification).
On Sun, Feb 15, 2009 at 11:30 PM, Dianne Hackborn hack...@android.comwrote:
You can't expand the size of the log. You can however use adb shell
dumpsys alarm to see the current state
On Feb 15, 6:29 am, Mariano Kamp mariano.k...@gmail.com wrote:
This question is a bit strange, but does anybody know about a common
gotcha when using the AlarmManager? And not knowing it sometimes leads
to the AlarmManger forgetting alarms?
I have a repeating task that runs once an hour.
Nope, not until somebody broke into my house and rebooted it during my sleep
;-)
The other problem in finding the source of my issue is, that I can't go back
very long in the Android log files. My logfile tells me that the alarms
weren't fired, but the logfile doesn't contain any more information
You can't expand the size of the log. You can however use adb shell
dumpsys alarm to see the current state of the alarm manager, which might
help.
On Sun, Feb 15, 2009 at 9:18 AM, Mariano Kamp mariano.k...@gmail.comwrote:
Nope, not until somebody broke into my house and rebooted it during my
The documentation states that alarms are not persisted across reboots,
so that's something that has to be dealt with by your app. But here's
the gotcha that I can't find documented anywhere...
It seems that uninstalling the app also clears all set alarms for the
package being uninstalled. This
5 matches
Mail list logo
