Use estimated vsync period on Android

ui/android/java/src/org/chromium/ui/base/WindowAndroid.java

Index: ui/android/java/src/org/chromium/ui/base/WindowAndroid.java
diff --git a/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java b/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java
index 6d3f3a6d1538a90ed7137b6f992c74610cfc56d8..ed0fb07a60b325d4107a4bf0f9dbce6ecafa367c 100644
--- a/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java
+++ b/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java
@@ -51,6 +51,10 @@ public class WindowAndroid {
         @Override
         public void onVSync(VSyncMonitor monitor, long vsyncTimeMicros) {
             if (mNativeWindowAndroid != 0) {
+                if (monitor.isVSyncSignalAvailable()) {
+                    nativeUpdateVSyncPeriod(mNativeWindowAndroid,

[Sami, 2014/09/30 16:04:14]

Instead of adding a new JNI call, please merge this with nativeOnVSync.

[jmanko, 2014/10/01 09:36:51]

Acknowledged.

+                                            mVSyncMonitor.getVSyncPeriodInMicroseconds());
+                }
                 nativeOnVSync(mNativeWindowAndroid, vsyncTimeMicros);
             }
         }
@@ -289,6 +293,7 @@ public class WindowAndroid {
 
     private native long nativeInit(long vsyncPeriod);
     private native void nativeOnVSync(long nativeWindowAndroid, long vsyncTimeMicros);
+    private native void nativeUpdateVSyncPeriod(long nativeWindowAndroid, long vsyncPeriod);
     private native void nativeDestroy(long nativeWindowAndroid);
 
 }