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: In accordance to treble rules libcamera_client.so cannot be
used or included. For HAL1 needed support for values of
Cameraparameters for HAL1 QCameraParameters
Solution: Included Cameraparameters.h and .cpp files to this location
as well.
Change-Id: If04d8a342d1552d2f0ba665b08b312e98bf8b9f5
1. fix HAL1 memory callback cookie for Treble change
2. remove checking for VANILLA_HAL definition for O upgrade now
for initial bring up, until the removal of the TARGET_USE_AOSP
flag in devie mkfile.
Change-Id: Iedf5a97e9890bc7216a3008373ddef5005836a01
Issue:
Android camera framework expects camera HAL modules
to release video duped FD's. Framework can trigger this event
after stopRecording() call.
Fix:
Change to avoid state machine check to release video FD's.
CRs-Fixed: 1077211
Change-Id: I6dcc31b335679e4885f56ae1e4e02ee33d193b08
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
Batch mode video processing was broken on latest builds. Batch mode
enabled and verified with media extension now.
CRs-Fixed: 1013704
Change-Id: Ifb34a9c201f39591ab5d6a8aa70125ca7cad3f4f
Issue:
Type of refreshrate is different in different android versions
and if same camera code is used across the versions then
dereferencing the hardcoded int pointer to float resulting a zero.
Fix:
Update Max fps as per the type of(MetaData_t->refreshrate)
Change-Id: Ifced28cdc56252151be4f41e3e652be41af510a0
CRs-Fixed: 1018231
In video metadata mode, framework allocates native handle
resource and needs to be freed in release recording.
This change is to free framework resources in case of media
extension use cases.
Change-Id: I1bac10740130d506d71ec1275dd7d75f66c263c8
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
