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
* Limits security exposure from shims
* As a bonus, we no longer need noatsecure
to make LD_SHIM_LIBS persist through services
Change-Id: I877192422062f3e59c81a7130ad1a2b4be5d1647
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
* Update build fingerprint as latest MIUI9 Global Stable
Change-Id: I0af7a2bfe53b725a45f5a6c029f9bc125a7c4ec7
Signed-off-by: Shubham Das <dasshubham762@gmail.com>
