Issue:
Diplay freeze observed sometimes, if there is any
suspend/resume of the device.
The issue found to be with differences in the timesources
used by display and camera for timestamp calculation.
Fix:
Measure the clock offset between BOOTTIME and MONOTONIC.
The clock domain source for ISP is BOOTTIME and
for display, it is MONOTONIC.
The offset is used to convert from clock domain of
camera to display.
Added following set prop to switch between camera time sources.
persist.camera.time.monotonic <value>
Default value is 1.
value 0 indicates Boot time from camera.
value 1 indicates Monotonic time from camera.
Change-Id: I733aa17e89ccaa7f5ea6d2eae5e1cd6428c81a85
CRs-Fixed: 1005906
Camera launch is failing due to QCameraDisplay crash.
Disabling temporarily for AOSP upgrade to avoid the crash.
This will be reverted once proper fix is found.
Change-Id: I6ed87edcfbb07410899dcde13341b7ddd404960e
Issue: Release_recording() can be called with any Imemory pointer
sent earlier. HAL cannot use this pointer to recognize video frame
to match before release this buffer to kernel.
Fix: Buffer identity is introduced to every video buffer and released
buffer can be found by comparing identity.
CRs-Fixed: 1026840
Change-Id: I287d1276fbf2241a2fc6d470e887a91e1daeca4d
Incase framework updates camera native_handle pointer, we need
to use cached native_handle to update for every timestamp
callback. This change is excecuted only if media extension flag
is enabled for the target.
Issue:
Use case introduced in video to overwrites camera native handle
pointer.
Fix:
Change is to cache camera native handle and restore when video
release camera buffer.
Change-Id: I0bdc01b3f2b51d7bba66320cc8ef1ab019136d4e
