Remove burst mode from VSyncMonitor.

Remove burst mode from VSyncMonitor.

Extra vsyncs after each rendering cause 1% more power consumption.
Modify VSyncMonitorTest to follow the rule 1 request == 1 vsync.

BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=282154

[egor.starkov, 2014-07-07 10:59:33]

This patchset was reviewed here https://codereview.chromium.org/346813002/

[Sami, 2014-07-07 14:35:06]

lgtm with a nit.

https://codereview.chromium.org/377483002/diff/1/ui/android/java/src/org/chro...
File ui/android/java/src/org/chromium/ui/VSyncMonitor.java (right):

https://codereview.chromium.org/377483002/diff/1/ui/android/java/src/org/chro...
ui/android/java/src/org/chromium/ui/VSyncMonitor.java:138: * Stop reporting
vsync events. Note that at most one pending vsync event can still be delivered
Does this comment need updating? Do we need this function at all anymore?

[egor.starkov, 2014-07-07 15:08:59]

https://codereview.chromium.org/377483002/diff/1/ui/android/java/src/org/chro...
File ui/android/java/src/org/chromium/ui/VSyncMonitor.java (right):

https://codereview.chromium.org/377483002/diff/1/ui/android/java/src/org/chro...
ui/android/java/src/org/chromium/ui/VSyncMonitor.java:138: * Stop reporting
vsync events. Note that at most one pending vsync event can still be delivered
On 2014/07/07 14:35:06, Sami wrote:
> Does this comment need updating? Do we need this function at all anymore?

I left it here because was afraid to ruin some dependency code, that i don't
know about.

[Sami, 2014-07-07 15:21:02]

On 2014/07/07 at 15:08:59, egor.starkov wrote:
> I left it here because was afraid to ruin some dependency code, that i don't
know about.

Could you try removing it and seeing what breaks (e.g., do a "git cl try") and
updating those call sites in this patch too? I'd prefer not leaving dead code
lying around.

[egor.starkov, 2014-07-07 16:03:10]

Removed empty method "stop()" in VSyncMonitor and tests.

[Sami, 2014-07-07 16:20:29]

Thanks! lgtm.

[egor.starkov, 2014-07-08 07:19:45]

The CQ bit was checked by egor.starkov@samsung.com

[commit-bot: I haz the power, 2014-07-08 07:21:00]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/egor.starkov@samsung.com/377483002/20001

[commit-bot: I haz the power, 2014-07-08 11:16:04]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_dbg_triggered_tests on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg_triggered...)
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-07-08 11:19:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-08 11:19:13]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)

[egor.starkov, 2014-07-09 10:56:42]

Adding OWNERS for review and LGTMing.

[Yaron, 2014-07-09 20:53:00]

lgtm

[egor.starkov, 2014-07-09 22:41:40]

The CQ bit was checked by egor.starkov@samsung.com

[commit-bot: I haz the power, 2014-07-09 22:43:29]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/egor.starkov@samsung.com/377483002/20001

[commit-bot: I haz the power, 2014-07-09 22:49:33]

Change committed as 282154

[egor.starkov, 2014-07-10 10:45:29]

On 2014/07/09 20:53:00, Yaron wrote:
> lgtm

Thanks, Yaron!