Start PowerUsageMonitor unconditionally from UMA bit.

Start PowerUsageMonitor unconditionally from UMA bit.

As PowerUsageMonitor is only reporting UMA data and nothing else, then PowerUsageMonitor can be started without checking UMA bit. The existing metrics service will take care of not uploading the data if The UMA bit is off.

Currently the check is there so that PowerUsageMonitor is not uselessly working in cases when the data will not be uploaded anyway. However in general we prefer to avoid such checks because enabling UMA shouldn't give users 'slower' Chrome.

BUG=600398
Committed: https://crrev.com/2d74e1b7211331a5ae569190e5ab7725f47afd0f
Cr-Commit-Position: refs/heads/master@{#385183}

[gayane -on leave until 09-2017, 2016-04-04 16:04:30]

Description was changed from

==========
Start PowerUsageMonitor unconditionally from UMA bit.

BUG=
==========

to

==========
Start PowerUsageMonitor unconditionally from UMA bit.

BUG=600398
==========

[gayane -on leave until 09-2017, 2016-04-04 16:05:34]

gayane@chromium.org changed reviewers:
+ sullivan@chromium.org

[gayane -on leave until 09-2017, 2016-04-04 16:05:34]

As discussed by email I am removing the check for UMA bit. Please have a look.

[sullivan, 2016-04-04 17:59:58]

lgtm

[gayane -on leave until 09-2017, 2016-04-04 18:12:23]

gayane@chromium.org changed reviewers:
+ sky@chromium.org

[gayane -on leave until 09-2017, 2016-04-04 18:12:24]

+sky for owners review.

[sky, 2016-04-04 20:51:10]

Can you elaborate on why we are doing this? The bug doesn't clarify why either.

[gayane -on leave until 09-2017, 2016-04-04 21:06:34]

Description was changed from

==========
Start PowerUsageMonitor unconditionally from UMA bit.

BUG=600398
==========

to

==========
Start PowerUsageMonitor unconditionally from UMA bit.

As PowerUsageMonitor is only reporting UMA data and nothing else, then
PowerUsageMonitor can be started without checking UMA bit. The existing metrics
service will take care of not uploading the data if The UMA bit is off.

Currently the check is there so that PowerUsageMonitor is not uselessly working
in cases when the data will not be uploaded anyway. However in general we prefer
to avoid such checks because enabling UMA shouldn't give users 'slower' Chrome. 

BUG=600398
==========

[gayane -on leave until 09-2017, 2016-04-04 21:07:32]

On 2016/04/04 20:51:10, sky wrote:
> Can you elaborate on why we are doing this? The bug doesn't clarify why
either.

I have updated the CL description and the bug as well.

[sky, 2016-04-04 22:47:12]

LGTM

[gayane -on leave until 09-2017, 2016-04-05 14:27:25]

The CQ bit was checked by gayane@chromium.org

[commit-bot: I haz the power, 2016-04-05 14:27:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1855223003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1855223003/1

[commit-bot: I haz the power, 2016-04-05 16:13:10]

Description was changed from

==========
Start PowerUsageMonitor unconditionally from UMA bit.

As PowerUsageMonitor is only reporting UMA data and nothing else, then
PowerUsageMonitor can be started without checking UMA bit. The existing metrics
service will take care of not uploading the data if The UMA bit is off.

Currently the check is there so that PowerUsageMonitor is not uselessly working
in cases when the data will not be uploaded anyway. However in general we prefer
to avoid such checks because enabling UMA shouldn't give users 'slower' Chrome. 

BUG=600398
==========

to

==========
Start PowerUsageMonitor unconditionally from UMA bit.

As PowerUsageMonitor is only reporting UMA data and nothing else, then
PowerUsageMonitor can be started without checking UMA bit. The existing metrics
service will take care of not uploading the data if The UMA bit is off.

Currently the check is there so that PowerUsageMonitor is not uselessly working
in cases when the data will not be uploaded anyway. However in general we prefer
to avoid such checks because enabling UMA shouldn't give users 'slower' Chrome. 

BUG=600398
==========

[commit-bot: I haz the power, 2016-04-05 16:13:10]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-05 16:14:11]

Description was changed from

==========
Start PowerUsageMonitor unconditionally from UMA bit.

As PowerUsageMonitor is only reporting UMA data and nothing else, then
PowerUsageMonitor can be started without checking UMA bit. The existing metrics
service will take care of not uploading the data if The UMA bit is off.

Currently the check is there so that PowerUsageMonitor is not uselessly working
in cases when the data will not be uploaded anyway. However in general we prefer
to avoid such checks because enabling UMA shouldn't give users 'slower' Chrome. 

BUG=600398
==========

to

==========
Start PowerUsageMonitor unconditionally from UMA bit.

As PowerUsageMonitor is only reporting UMA data and nothing else, then
PowerUsageMonitor can be started without checking UMA bit. The existing metrics
service will take care of not uploading the data if The UMA bit is off.

Currently the check is there so that PowerUsageMonitor is not uselessly working
in cases when the data will not be uploaded anyway. However in general we prefer
to avoid such checks because enabling UMA shouldn't give users 'slower' Chrome.

BUG=600398

Committed: https://crrev.com/2d74e1b7211331a5ae569190e5ab7725f47afd0f
Cr-Commit-Position: refs/heads/master@{#385183}
==========

[commit-bot: I haz the power, 2016-04-05 16:14:12]

Patchset 1 (id:??) landed as
https://crrev.com/2d74e1b7211331a5ae569190e5ab7725f47afd0f
Cr-Commit-Position: refs/heads/master@{#385183}