Age | Commit message (Collapse) | Author |
|
Replace the current raw noise model, calibrated using Android's
dng_noise_model.py script, with an improved noise model, using an
updated version of that script.
The new raw noise model has a different parameterization in terms
of ISO:
- The formula for 'S' scales with ISO. While shot noise should
be zero for a completely dark signal, we still include an offset
here to help compensate for black level variations with ISO.
- The new formula for 'O' scales with ISO^2, not ISO. This form is
required because 'O' corresponds to the *variance* due to read
noise. The new formula also treats analog and digital gain
separately. While pre-ADC read noise is affected by both types
of gain, post-ADC read noise is affected *only* by digital gain.
Bug: 16273313
Change-Id: Iec5c7854c1d529b97567235cda9a8041b0ec0914
|
|
It could cause some build breakage.
Bug: 21660414
Change-Id: I7bd7cf71e32c48f10131cf978b95dd0d8b3fc451
|
|
In case of an unrecoverable error in the backend that results in
the HAL receiving a DAEMON_DIED error notification, close the current
mct session so that the camera shuts down cleanly.
Bug: 21660414
Change-Id: I01d8cbab77775829217ae55392c78111abe8d8ce
|
|
This enumeration provides the ability to distinguish between
FAST and HIGH_QUALITY modes for Hotpixel.
Change-Id: I18078ea3f50956c0de80537c92b37821816cd133
|
|
Bug: 21664890
Change-Id: I5066777971f2c7e1886b70aa6b9480d175927664
|
|
Bug: 21662890
Change-Id: I0cf5f38d0d0f29c10ef3291afdb97286986e4809
|
|
Thumbnail dimensions in jpeg metadata needs to be swapped
if frame is rotated.
Bug: 20304829
Change-Id: I2f5c526b2b7d4568d887d5b5f522bece15d8e74b
|
|
Bug: 21864510
Change-Id: I61f5a14c74d1f1774992ebfa7b4100f54a22f681
|
|
Bug: 18643376
Change-Id: Ib7002ab8820652b7ceb4653c034b624e743b6b8c
|
|
Bug: 21436781
Change-Id: I275ec1531e22f375beeed9d75f67cf7bf402c4a3
|
|
Update static metadata and advertise
available shading.available modes and availablelensshadingmap modes.
Also add the same to availableCharacteristicsKeys.
Bug: 20087854
Change-Id: I8253275afdf3c1300245243bf1c705b24da87308
|
|
|
|
Check if mPictureChannel is NULL before
acessing the same.
Change-Id: I46cea9c3cf6f1006c1310825899bd22e598b22f5
|
|
Without this change, continuous builds of all Android projects stop at this error.
BUG: 21436781
Change-Id: I91f179b9f6a24e5c9fed14653ec36b7b642e1bd9
|
|
get_camera_info method uses HAL descriptor to determine which
version of HAL is active. Initialize HAL descriptor before
calling get_camera_info
Bug: 19809724
Change-Id: I055651baefcef05971dd184718caf15b0619ba26
|
|
Update available control modes in HAL and update
the same to upper layers.
Change-Id: I97587b100af3178aa945065656371c29de78b9b4
|
|
|
|
Previously, HAL was not advertizing HIGH_QUALITY mode for
HotPixelModes, ToneMapModes, EdgeModes, and NoiseReductionModes.
Now, HAL has been updated to properly advertise HIGH_QUALITY
for these.
Bug: 20087854
Change-Id: Iaba3102146e1dd2dc5cb22b2c13fd2996f2a7439
|
|
Change-Id: If7cfea202774727eb8235bc5e8e3077f4669a7e4
|
|
Advertised the max stall duration during reprocess
measured in number of frames
Change-Id: I8f2d7d2f8e87a09906adb9a3867bc3bb59b956bd
|
|
Earlier understanding of color space flag for video
buffer was wrong. Video encoder actually assumes the
buffer is in 601 full range, and the flag specifies
which color space the encoder converts to.
As a result, camera HAL needs to set 709 in order
for encoder to do a 601->709 conversion.
Change-Id: Ia694dd83c65d43f87b0ebab8553de4e2a482ffe0
Bug: 17785855
|
|
Update availability of AE and AWB lock feature in HAL to
advertise the same to upper layers.
Change-Id: I132ca21b3eb8257742dc1c73a5726f68e6a1cfd2
|
|
Not shutting down postprocessor during channel teardown
can cause jpeg messaging threads to linger around,
causing performance issue due to large number of abandoned
threads.
Bug: 20304243
Change-Id: Icde28a91ccc80bb29b836588abfdfca94ae97d27
|
|
|
|
When the camera is opened, a callback is triggered to reserve the
camera's flash for camera usage only. Previously, the callback
would happen even if there is no flash associated with the camera.
Now, the callback is suppressed for any camera which does not have
a flash.
Bug: 20069129
Change-Id: I816737b3b7c4976db84bbbe0e71658ababa804f7
|
|
-Fix gralloc usage flags for Opaque reprocess
-Modify support channel logic to handle front sensor
viewfinder only snapshot/zsl config
Bug: 20297264
Change-Id: I43c3619c32fefb005125c39edee2f55c6739e92d
|
|
-Picture channel's PP mask is used to avoid 2-pass reprocess
in cases where the native stream(non-zsl fallback) has already
run through PP pipeline in usecases like 4k or currently YUV ZSL.
-However this mask is irrelavant for framework reprocess input,
since the source stream could have pp connected or disconnected
based on mask.
-Even if the source stream's pp mask is non-zero there could be
some pp operations requested as part of the reprocess request
necessiating a second PP pass
-The above situation can also happen in case of API1 Bidirectional
ZSL, but works due to the fact that Native fallback and F/W ZSL streams
are tied together always with a PP mask of 0
-Such an assumption can become valid even for YUV reprocess once
online reprocess is enabled for YUV streams.
Change-Id: I3dc82a007605a3d3f520f6e9d8fe22b474ebde42
|
|
|
|
-Use ZSL stream size for overriding Picture Non ZSL
fallback stream
-Extend usage of support channel to usecases where
no PP streams present
Change-Id: I11b6d41976a8b4ec47619533f81d0bf4a7951970
|
|
Change-Id: I074337f5bc986b426f745f161da6582b25c9328b
|
|
|
|
|
|
-Modify advertised i/p stream size to match largest output
-Relax code to safegaurd against multiple ZSL candidates
Change-Id: I94d44be719f205322e640e577855799c0b06c3d0
|
|
Change-Id: I2752a11d96029566b4de19af1180d6ffcf358291
|
|
Change-Id: I7bd6db14ba29dead415b1fdef54c61742399b776
|
|
-Add support for "minimal" noise reduction mode
-Add support for effective exposure factor
Change-Id: Iccee69247186573c7268778bb3c101e00cd86722
|
|
-Add support for enabling Opaque/YUV to JPEG reprocessing
Change-Id: I66020e946f2787d2554f496c015438b11a07a2d2
|
|
This reverts commit 26aae0d7dbe6d4c8a9c189486ddbc0cacbcc7ddb.
Change-Id: If0319ca12bf5f77506888bf9b7b48612cb348d37
|
|
resource_cost of a particular camera is calculated based on
overall CPP bandwidth limit and maximum stream configuration
bandwidth requirement.
Change-Id: Ic207ffe07f51a13acff4c6f9ce7f35d683f12e81
|
|
|
|
Add flash device name into capability
Change-Id: Iabe9a557162d038a57647febf23457c7080cb3bc
|
|
Implemented new API at HAL, allowing framework to turn on flash
devices independently of the sensor. The primary logic is
implemented as a singleton named QCameraFlash, which tracks
the state of any flash devices and interfaces with the driver
to turn them on or off.
Change-Id: I4452e65401140e28aa86184800857a423c9c4b09
|
|
Detected by clang compiler.
Change-Id: I944139f07e7d1da1ea5e9477473013a5bd63c201
|
|
Incase of delayed daemon start there is possibility of
timeout, HAL should re-attempt in those cases to allow
time for daemon to start.
Change-Id: I1920fb32652e944ca599efef7801045b60c42ca8
|
|
This takes care of cases where mm-qcamera-daemon takes a long
time to launch. get_camera_info depends on mm-qcamera-daemon
being up and running to work.
In the worse case, get_camera_info will be held up by HAL for
200ms.
Bug: 10577806
Change-Id: I7068b0f60bf75c407b603f4e0a0bbb19b8f51f0c
|
|
Every output buffer by framework should
be subsequently un-mapped before it
returns to client. Both camera backend
needs to be notified and ION resources
need to be released.
Bug: 19674986
Change-Id: I0ffe789b3392c2948584f56a561fac3f086e2a6e
|
|
Change-Id: I9d2bf39a41d5c2a38de9e9e74ca856368327e424
|
|
* commit '142c136917ef12e49d5ccc862997f2a9aeebae47':
Add missing includes.
|
|
automerge: 0faef9d
* commit '0faef9defbc0cf6df073ecfe2e8f458abe2ffa5b':
Add missing includes.
|
|
Change-Id: I497ccf08d7b5428f315c9cc0dbaf3b10d2df8dc7
|