*Write aot_enable,[0,1] to /sys/class/sec/tsp/cmd as done before
*Also write 0 or 1 depending on display state to /sys/class/sec/tsp/input/enabled to have the screen properly turned off for DT2W
Signed-off-by: Simon1511 <simon2002.schoenmackers@gmail.com>
Change-Id: I6ba4549ae725012928dc43a5043e89c0831ff659
There's nothing really that different here when compared to the
common HAL except for the specific DT2W handling, which can simply
be supported as a power feature lib.
Change-Id: I59d039c500c672c50727aa715c256c9f55d98fa4
messages during build:
device/samsung/sm7125-common/configs/nfc/nfcee_access.xml:9: namespace error : Namespace prefix android for signature on signer is not defined
Change-Id: I1e06a53207ec7009be473a132e7d24c901c5fa56
*Build missing NFC packages
*Import init commands from stock
*Move configs to device tree and add missing ones
Change-Id: I3fd7d5641184f14dcde8aaaf493eeefa25a8b982
* 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
Willi Ye