| Commit message (Collapse) | Author |
|
FR49059: Accessing AOSP/Google projects Headers
Description: Vendor modules cannot refer AOSP header
paths with absolute or Global Paths instead add
corresponding header library
FR49058 : VNDK compliance
Description : VNDK is set of AOSP libraries which
are exposed to vendor (partition) for development.
Example :
error: vendor lib "/vendor/lib/libeffects.so"
depends on non-eligible lib
"/system/lib/libeffectsconfig.so".
Here , QCOM vendor-partition Library
using lib outside VNDK from system.
CRs-Fixed: 2217547
Change-Id: I51a88145fccba592080d6287ae7ff14d12c65296
|
|
Changes to fix QCameraDisplay compilation issue.
Change-Id: Iaa28e2b0acff0556d6052945e446066aa27be5b1
|
|
Issue: VTSCameraProviderV2_4Target test case is failing in setTorch
mode.
Fix: Corrected returned error -ENOSYS (OPERATION_NOT_SUPPROTED) if
torch mode is not supported by cameraid
CRs-fixed:2091737
Change-Id: I9e9bb764016227fbd6cf036c753ca5aeff8eeb7e
|
|
Issue:
Compile time HAL1 Removal as for IOT projects we are going to use only HAL3 so
removing HAL1 Camera files from compile time.
fix:
Modified the Android.mk file to remove HAL1 during compilation.In
case if HAL1 is not getting compiled muxer object is also not created
in QCamera2Factory.
CRs-Fixed: 1021955
Change-Id: I17af448d7c423c73c5f3c29e95fb42cc69ca5944
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|
|
Tag: LA.HB.1.3.2-32600-8x96.0
Signed-off-by: Davide Garberi <dade.garberi@gmail.com>
|