diff options
author | Eino-Ville Talvala <etalvala@google.com> | 2015-04-29 17:36:58 -0700 |
---|---|---|
committer | Eino-Ville Talvala <etalvala@google.com> | 2015-04-30 15:52:21 -0700 |
commit | d48521fc2f7c34623a745728a07dad728da49254 (patch) | |
tree | 6a13d3322a6ecf2583b1227932f11220983216c5 /cmds | |
parent | f62a067a5b21c840c915d36392679346ac0abfd7 (diff) | |
download | frameworks_av-d48521fc2f7c34623a745728a07dad728da49254.zip frameworks_av-d48521fc2f7c34623a745728a07dad728da49254.tar.gz frameworks_av-d48521fc2f7c34623a745728a07dad728da49254.tar.bz2 |
Camera: API1 shim: Don't tightly apply crop region
Due to older HAL compatibility, we have been setting a tight crop region
that just bounds the current output streams. However, this did not take
into account any possible ZSL output stream, so correct application of
our stream cropping rules to ZSL results in double-crop scenarios, if
the ZSL stream aspect ratio does not match the aspect ratio of the other
output streams.
Since all current HALs follow the correct stream cropping rules (or
at least sufficiently ignore them for ZSL), simplify the cropping
substantially - now either calculate the crop region based purely
off the active array dimensions and zoom factor, or purely off
the preview stream and zoom factor. The former is used for setting
the request crop, and the latter is used for converting coordinates
for metering regions.
Bug: 20316691
Change-Id: I5a0bc2e7c09cf60fbae4220566540ca9e674d652
Diffstat (limited to 'cmds')
0 files changed, 0 insertions, 0 deletions