* Dropped vendor-specific range > 255
from config_screenBrightnessBacklight (stuck at bootanimation
otherwise)
* Dropped the same amount of entries from the end of
config_screenBrightnessNits (otherwise autobrightness
won't work)
Change-Id: I31956340b0ac66b6e9456df46d0b22493ede0d02
*Newer Samsung devices seem to control vibration intensity through /sys/class/timed_output/vibrator/enable instead of having a seperate node for intensity
*Therefore we need to write to the enable path instead
*Also set minimum intensity to 40 since that's the lowest value that's still noticeable
Signed-off-by: Simon1511 <simon2002.schoenmackers@gmail.com>
Change-Id: I402c5e0e77549ae8be38c43544357b1c4e847880
Samsung enables FOD in TS driver (fod_enable) at all times except
a small number of optical FOD sensor that doesn't have BiometricFeature
.FEATURE_SUPPORT_AOD. As optical type sensor support is not implemented
currently, this HAL is only used on device that has FOD always-on.
This change follows behavior of stock firmware and without toggling of
FOD enable state FOD should be more stable.
Plus it allows setInteractive and config_powerDecoupleInteractiveModeFromDisplay
to function properly with FOD. Currently setInteractive(0) happens before
a onShowFODView (which is the current point to call fod_enable) can be
triggered by the Doze, as TS driver only handles command when it is enabled,
FOD doesn't work when there is a setInteractive(0) that disables TS.
Signed-off-by: Michael Benedict <michaelbt@live.com>
Change-Id: If1ce9cab58717a9b9dcfce496da79bcf74773a33
*Use stock camera provider
*Build camera.device blobs from source to get its dependencies, then override it with stock camera.device blobs
*Added missing media_profiles_V1_0.xml for camera
Change-Id: I6d776f5fc6de343708b46ca55d8ea6f12194f153
Tethering package is APEX and we need to create a RRO to overwrite
the values for config_tether_wifi_regexs and config_tether_wifi_p2p_regexs.
BUG: 163800715
Signed-off-by: Weilun Du <wdu@google.com>
Change-Id: Ia0834f5215ff8c3b13effa591bd2f84d93419a06
Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.
Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8
Signed-off-by: Tushar Mahajan <mahajant99@gmail.com>
Tim Zimmermann