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
Issue:
Camera is not launching for the first time as camera
daemon is not up.
Fix:
Increase camera daemon start timeout
Change-Id: I2dd8ae904145ad5c067b27014cdb95c28084accf
In Android O, Cameraporvider service is introduced newly and its
starting before main service which results in getnumofcameras failure.
Added re-try count to fix this issue.
Change-Id: I3a3ee1cbe6ad983d5ad7266f154b33b93d303804
Replaced LOCAL_PROPRIETARY_MODULE with LOCAL_VENDOR_MODULE to set the
output vendor path for hal binaries and libraries
Change-Id: Ib04d80eabc0e17f3863e956db5f2378e426c0687
Issue: In FLASH mode, while requesting superBuffers for 100 snapshots
cur_capture_idx is increasing to more that MAX_CAPTURE_BATCH_NUM,
so by derefrencing frameConfig.config to cur_capture_idx, stack
memory is getting corrupted.
Solution: Checking for max value of cur_capture_idx before derefrencing
frameConfig.config array to avoid writing in outOfBound index
memory.
Change-Id: Icaea62be483b3ee97304441f7c9287b73496f09d
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
