summaryrefslogtreecommitdiffstats
path: root/core/java/android/os
diff options
context:
space:
mode:
authorJoe Onorato <joeo@android.com>2009-07-31 17:58:55 -0700
committerJoe Onorato <joeo@android.com>2009-07-31 17:58:55 -0700
commit37296dc4edae8d1383179e956dff2ecf806ac166 (patch)
treead82c9f8dac6ea99f52b9f4413a1f8f46dead534 /core/java/android/os
parent8845ea0592e3bffc726febb66de48646b0398e70 (diff)
downloadframeworks_base-37296dc4edae8d1383179e956dff2ecf806ac166.zip
frameworks_base-37296dc4edae8d1383179e956dff2ecf806ac166.tar.gz
frameworks_base-37296dc4edae8d1383179e956dff2ecf806ac166.tar.bz2
Update docs.
Diffstat (limited to 'core/java/android/os')
-rw-r--r--core/java/android/os/SystemClock.java8
1 files changed, 7 insertions, 1 deletions
diff --git a/core/java/android/os/SystemClock.java b/core/java/android/os/SystemClock.java
index 2b57b39..2dd6749 100644
--- a/core/java/android/os/SystemClock.java
+++ b/core/java/android/os/SystemClock.java
@@ -30,7 +30,13 @@ package android.os;
* backwards or forwards unpredictably. This clock should only be used
* when correspondence with real-world dates and times is important, such
* as in a calendar or alarm clock application. Interval or elapsed
- * time measurements should use a different clock.
+ * time measurements should use a different clock. If you are using
+ * System.currentTimeMillis(), consider listening to the
+ * {@link android.content.Intent#ACTION_TIME_TICK ACTION_TIME_TICK},
+ * {@link android.content.Intent#ACTION_TIME_CHANGED ACTION_TIME_CHANGED}
+ * and {@link android.content.Intent#ACTION_TIMEZONE_CHANGED
+ * ACTION_TIMEZONE_CHANGED} {@link android.content.Intent Intent}
+ * broadcasts to find out when the time changes.
*
* <li> <p> {@link #uptimeMillis} is counted in milliseconds since the
* system was booted. This clock stops when the system enters deep