To support end-to-end DRM content playback with SG List feature,
android.hardware.drm@1.0-service needs to have access permission
to /dev/qce to map & unmap ION buffer virtual address with HW Crypto
Engine. So, set /dev/qce device permission 0660 and let it be
accessible by user "system" and group "drmrpc".
Change-Id: If9c0ed70acc2bb063344692374f51441fe84eff6
Based on "dispatchNetworkManual" introduced by
Adrian Ulrich (adrian-bl-yuga) and which was used
till Android O RIL stack.
[HenningJW]: Apply for automatic network selection too
Change-Id: I85433f2a4f94690c1dd2a742f0b1c39aba360cd6
* For search, the number of strings returned for
RIL_REQUEST_QUERY_AVAILABLE_NETWORKS should be defined in the system
prop ro.ril.telephony.mqanelements
Change-Id: Ie5bb8ba80c5ac93b7502da3b1bb3d2b4404ecd5e
* Perf/Thermal blobs from angler - OPM6.171019.030
* Thermal HAL from angler base + hima modified configs.
* Modified thermal sensor numbers for kitakami platform.
* From https://github.com/AICP/device_htc_hima
Issue:
When camera open fails, param heap buffer which was allocated
in a deferred thread will not be cleaned up properly because
of improper flag check in parameters deinit().
Fix:
Since param heap buffer is allocated asynchronously, move the
initialization flag check after deallocating param heap.
CRs-Fixed: 1070448
Change-Id: I026f307c5b7501d3607c64c6b36d41eddaf0349a
On high RAM targets, due to more anonymous memory availability,
we can improve headroom by increasing ZRAM swap size,
especially under memory pressure, and during background app compact.
Also ZRAM swap size is logical and is used when needed and
shouldn't cause other side effects.
Change-Id: I11949b8bdf16e9b4b8abb1bd633ffa1a1c0b1ad6
* Enable B-services aging propagation and delay service restart
for devices with 2GB or less memory.
Change-Id: I81a09cc8425602bfc586875b7d36a4f56a226908
* aviraxp:
Note, the CAF fix seems incorrect in QCameraStateMachine as
fall-through is intended and the signal won't be sent, so
change the break to fallthrough. Also add a missing break.
Change-Id: Ia8cb92afc246bfb7ae7a9f2eac90fcdc518e426e
Issue:
Flashlight in system tray is not working with HAL1 on
devices with module version >= 2.4.
Its due to framework looks for ANDROID_FLASH_INFO_AVAILABLE
property which is not set in the HAL1 camera info.
Fix:
Populate the required camera static characteristics
regardless of HAL version.
CRs-Fixed: 993695
Change-Id: I5d3b95b3b3f4ab72ae3b67c87a8a2d257260a5de
Add .reserveFlashForCamera() and releaseFlashFromCamera() in
openCamera and closeCamera respectively
CRs-fixed: 939604
Change-Id: I49162b31df6b62f1e87269b018c238d1e1eedf5e
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
When the camera is opened, a callback is triggered to reserve the
camera's flash for camera usage only. Previously, the callback
would happen even if there is no flash associated with the camera.
Now, the callback is suppressed for any camera which does not have
a flash.
Bug: 20069129
Change-Id: I816737b3b7c4976db84bbbe0e71658ababa804f7
resource_cost of a particular camera is calculated
based on overall CPP bandwidth limit and maximum stream
configuration bandwidth requirement.
[aviraxp: Trim down to dummy support for camera API 2.4.]
Change-Id: Ic207ffe07f51a13acff4c6f9ce7f35d683f12e81
Implemented new API at HAL, allowing framework
to turn on flash devices independently of the sensor.
The primary logic is implemented as a singleton named QCameraFlash,
which tracks the state of any flash devices and interfaces
with the driver to turn them on or off.
Change-Id: I4452e65401140e28aa86184800857a423c9c4b09
If camera daemon crashes, it could take up to 10 seconds for it
to restarts. This time seems to increase in latest OS upgrade.
Increasing the retry count makes it less likely to fail get_camera_info.
Test: Hardcode hasPendingBuffers in HAL destructor to force restart
Bug: 67576800
Change-Id: Ifd697e7fed4944a255e1efea3b96c75345b253c1
Device open may fail when cameraserver and mm-qcamera-daemon are
killed at the same time.
Bug: 27869821
Change-Id: I03e006246c2df68b7ef176afd269fabb280b2534
Incase of delayed daemon start there is a possibility of
timeout, HAL should re-attempt in those cases to allow
time for daemon to start.
Change-Id: I1920fb32652e944ca599efef7801045b60c42ca8
This takes care of cases where mm-qcamera-daemon takes a long
time to launch. get_camera_info depends on mm-qcamera-daemon
being up and running to work. In the worse case,
get_camera_info will be held up by HAL for 200ms.
Bug: 10577806
Change-Id: I7068b0f60bf75c407b603f4e0a0bbb19b8f51f0c
* This fixes the following error on camera-in-mediaserver devices:
E CameraService_proxy: Calling UID: 1013 doesn't match expected camera service UID!
Change-Id: I185e34e8983b286436bfc0fe36cfdf260ef78170
