Disable Camera2 API for devices with legacy hardware support

Disable Camera2 API for devices with legacy hardware support

BUG=446610
TBR=mcasas
TEST=Add log statement in function isLegacyDevice and navigate to any page in chrome that uses the camera to verify that Nexus 4 is INFO_SUPPORTED_HARDWARE_LEVEL_LEGACY and Nexus 5 is INFO_SUPPORTED_HARDWARE_LEVEL_FULL.

Committed: https://crrev.com/f62e6ae41bc9cb5c4d4ae78eda8e441a8a9ec657
Cr-Commit-Position: refs/heads/master@{#311047}

[magjed_chromium, 2015-01-12 12:39:38]

Patchset #1 (id:1) has been deleted

[magjed_chromium, 2015-01-12 13:40:54]

magjed@chromium.org changed reviewers:
+ perkj@chromium.org

[magjed_chromium, 2015-01-12 13:41:40]

perkj - Can you take a look?

[perkj_chrome, 2015-01-12 13:51:56]

lgtm but please add a TEST= and describe how to test and verify that Camera2 is
used by N5 or N6.

https://codereview.chromium.org/834423003/diff/20001/media/base/android/java/...
File media/base/android/java/src/org/chromium/media/VideoCaptureCamera2.java
(right):

https://codereview.chromium.org/834423003/diff/20001/media/base/android/java/...
media/base/android/java/src/org/chromium/media/VideoCaptureCamera2.java:279:
getCameraCharacteristics(appContext, id);
weird indentation

[magjed_chromium, 2015-01-12 14:07:31]

The CQ bit was checked by magjed@chromium.org

[commit-bot: I haz the power, 2015-01-12 14:08:08]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/834423003/20001

[commit-bot: I haz the power, 2015-01-12 15:04:18]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2015-01-12 15:05:08]

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

[magjed_chromium, 2015-01-30 11:06:24]

magjed@chromium.org changed reviewers:
+ mcasas@chromium.org

[magjed_chromium, 2015-01-30 11:07:21]

Miguel - Can you take a look at this? Maybe there is some better solution?

[mcasas, 2015-01-30 20:34:29]

On 2015/01/30 11:07:21, magjed wrote:
> Miguel - Can you take a look at this? Maybe there is some better solution?

I tried new and old APIs for http://crbug.com/448457 and elsewhere and
see that N5 and N6 work fine with the new API, while N4 and N7 don't.
Of course this applies to Android 5.0+. 

This work/no work seems to correlate 100% with the LEGACY bit,
so I think this CL is the correct way to go. We should keep an eye
on all this though. It might change.