"All possible values in UTC time" - there are (2 << 63) - 1 of those,
which is almost 10 ^ 19, so I don't see how you could have tried them
all so fast :)
Even without a wake lock, your receiver's onReceive should still be
called (you do log that, right?).
RTC_WAKEUP uses wall clock time in the UTC time zone.
Make sure your code correctly computes the time value, I think that's
where the bug is. Specifically, I think you're possibly getting the
value in the wrong time zone (your own time zone, perhaps, and not UTC).
A few possible things to try:
- Log the value you feed to AlarmManager, log the value of
System.currentTimeMillis(), see what they look like relative to one another.
- Repeat the above with the hour/minute value closer to "now", so it's
easier to verify.
- Connect to your phone/emulator with "adb shell", use "dumpsys power"
to check your alarm after it's been set.
Oh, and make sure your phone/emulator's date/time are set, including the
time zone.
-- Kostya
11.03.2011 21:04, Brad Stintson пишет:
For calendar values, i tried all possible values in UTC time as well
as emulator time. Still it is not showing the notification. Is it
related to WakeLock? If yes, then how to implement it?
--
Kostya Vasilyev -- http://kmansoft.wordpress.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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
