From 0e775697fb12d3f9c577c7758a362103c2194519 Mon Sep 17 00:00:00 2001 From: Andy McFadden Date: Fri, 26 Apr 2013 11:17:57 -0700 Subject: Recommend different time source We were recommending SystemClock#uptimeMillis() from Java code, but millisecond resolution is a little coarse. We don't have an appropriate call in SystemClock, so use System.nanoTime() instead. Bug 8733179 Change-Id: Ifb85a03eabf7ff168966adcb5ed5914bbf3884b2 --- opengl/specs/EGL_ANDROID_presentation_time.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'opengl/specs/EGL_ANDROID_presentation_time.txt') diff --git a/opengl/specs/EGL_ANDROID_presentation_time.txt b/opengl/specs/EGL_ANDROID_presentation_time.txt index 03370ed..09b3938 100644 --- a/opengl/specs/EGL_ANDROID_presentation_time.txt +++ b/opengl/specs/EGL_ANDROID_presentation_time.txt @@ -107,8 +107,8 @@ Issues presentation time when an absolute time is needed be queried on Android? RESOLVED: The current clock value can be queried from the Java - SystemClock#uptimeMillis() method or from the native clock_gettime - function by passing CLOCK_MONOTONIC as the clock identifier. + System.nanoTime() method, or from the native clock_gettime function by + passing CLOCK_MONOTONIC as the clock identifier. Revision History -- cgit v1.1