From 2f6d8829524dfca3a77e9a57c3b9c3862209877d Mon Sep 17 00:00:00 2001 From: Philip Milne Date: Fri, 21 Sep 2012 14:21:27 -0700 Subject: Fix for bug: #7173350. elapsedRealtimeNano() -> elapsedRealtimeNanos() Change-Id: I71c24ea10093ece07a0780e97bc641ff548c1a44 --- core/java/android/os/SystemClock.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'core') diff --git a/core/java/android/os/SystemClock.java b/core/java/android/os/SystemClock.java index a54c25b..c9adf45 100644 --- a/core/java/android/os/SystemClock.java +++ b/core/java/android/os/SystemClock.java @@ -50,7 +50,7 @@ package android.os; * interval does not span device sleep. Most methods that accept a * timestamp value currently expect the {@link #uptimeMillis} clock. * - *

  • {@link #elapsedRealtime} and {@link #elapsedRealtimeNano} + *

  • {@link #elapsedRealtime} and {@link #elapsedRealtimeNanos} * return the time since the system was booted, and include deep sleep. * This clock is guaranteed to be monotonic, and continues to tick even * when the CPU is in power saving modes, so is the recommend basis @@ -157,7 +157,7 @@ public final class SystemClock { * * @return elapsed nanoseconds since boot. */ - public static native long elapsedRealtimeNano(); + public static native long elapsedRealtimeNanos(); /** * Returns milliseconds running in the current thread. -- cgit v1.1