Now that the dependency commits for gerrit topic 13-camera-privapp are merged,
we can now enable super slow motion in MotCamera4
Change-Id: I020fa669311129af7f9874ce8677798628731fb8
Build fingerprint and description taken from getprop of stock ROM
[ro.build.description]: [dubai_g-user 12 S1RD32.55-106 0cdff5-e7305 release-keys]
[ro.build.fingerprint]: [motorola/dubai_g/dubai:12/S1RD32.55-106/0cdff5-e7305:user/release-keys]
Also drop duplicated cvp blobs from sm7325-common
Change-Id: I79c471d12ca4c9edbfa39e40a8191d79701e101e
The values extracted from Stock ROM are quite dim on average and the minimum brightness is low,
So let's remove the three minimum light sensor values on config_autoBrightnessLevels and the
bottom four values and then add another value near max on config_autoBrightnessDisplayValuesNits
to help increase the minimum brightness and also bump up the values for the other automatic
brightness values.
While we're at it, we shall also raise the values for DarkeningLightDebounce and
BrighteningDebounce overlays so that it takes a lot longer before our device decides to actually
lower the brightness to prevent super jarring brightness changes.
Change-Id: Iacafa69d1e27b5201d98a832305c9afc5f228dd3
Also remove duplicate cvp blobs which are in sm7325-common tree and Update
MotCamera4 and disable Video HDR and Night Vision. We can also leave the
required libs in the apk now that we are on lineage-20.
Change-Id: I39bd9e5daacdc525091b9391aa3a968ce10e0144
In the berlin/dubai trees we have overriding values that use the same as
the default values, so let's just revert to that.
Change-Id: I5e4ee2d89fb6c9e058db4395e50d7891c69f85d3
This reverts commit ca971befd9.
Reason: There's already a sort-blobs-list.py in the extract tools repo
https: //github.com/LineageOS/android_tools_extract-utils
Change-Id: I433157f6fc6d7775ed0931fb4079e76918a32348
While we're at it, remove the duplicated camera sensormodule section that
is already included in the camera sensor section.
Change-Id: I9c78b3e2268c627494eb70a2d862b88161e56b36
Signed-off-by: sb6596 <shubhamprince111@gmail.com>
Co-authored-by: Marc Bourgoin <themard85@gmail.com>
While Google found that fingerprint HAL is insensitive to
increased CPU throughput, we have not found that to be the
case. Allowing more CPUs makes fingerprint unlock up to
2x faster in some tests.
SM8250 device with fingerprint on display:
- Before: 3128ms
- After: 944ms
SDM845 device with fingerprint on the power button:
- Before: 1146ms
- After: 688ms
Change-Id: I43d6096bd0ee8c6c30a81104858e42725689d696
Ran the reorder-libs.py from the previous commit
Change-Id: I7e8f5a778cdcf13b46607bfc3206995e7abf1e28
(cherry picked from commit 65cfa2cc888de0f8ef857f74d03317257860d3b8)
As of I3c7aed1bdb45db728d319f7d757400e44d232283 the Bluetooth stack
defaults to reasonable defaults that should work for all devices.
Change-Id: I056d63c4c8a2727e384172e964dc0000b6773504
