Re-enable the adaptive haptics feature for latest qpr in order to align
with other similar devices.
Bug: 198239103
Test: adb shell dumpsys android.hardware.vibrator.IVibrator/default
Change-Id: Ie2964f4971f209ad4d18a05007e1847bad68ff25
Signed-off-by: Chris Paulo <chrispaulo@google.com>
Update pointers used in protobuf interface for configuring the detector.
When AoC has an SSR, it causes CapoDetector to go down by null pointer
dereference.
Bug: 261349596
Test: Verified 10x forced AoC SSR
Change-Id: Ifd7fcbbff4639f552c6708b5b171f0b3c9164c03
Signed-off-by: Chris Paulo <chrispaulo@google.com>
the file node was removed so also remove these
dummy setting
Bug: 260806701
Change-Id: I23044f7f32cf4b2b2cc93205ec5751525f05ee7f
Signed-off-by: Chungkai Mei <chungkai@google.com>
Some 3rd party app may use one or three microhpne(s)
to do the camera recording.
Add these two configurations to UC_AUDIO_RECORD to sync
the audio and video of the recoreded video.
Bug: 260824124
Test: Reporter verified
Change-Id: Iaaf160070a26926a3cf6e18a184750d154abef6d
Disable the adaptive haptics feature temporarily for qpr2 release
Bug: 260247920
Test: Verified feature disabled on device
Change-Id: If9929744ac798f69cf8ee73529f16badcfcb302a
Signed-off-by: Chris Paulo <chrispaulo@google.com>
Add capability for vibrator HAL to detect whether the device is face-up
and adjust/scale haptic alerts to avoid loud and startling buzzing when
there is no case on the device
Bug: 198239103
Test: Verified tests and functionality
Change-Id: I93875c3c1e6128d275cb8007f8e8870a7842938a
Signed-off-by: Chris Paulo <chrispaulo@google.com>
Moved L26 portion of vibrator hal from hardware/google/pixel to
device/google
Bug: 198239103
Test: None
Change-Id: I0d3b5c068168ede0cae1e7a99cc8497185b48ec3
Signed-off-by: Chris Paulo <chrispaulo@google.com>
When exiting camera app, camera daemon is still busy in background,
which may affect the launch animation of launcher. So, limit the cpuset
of camera daemon to little cores for 1 second when there is app launch
hint to improve it. This only happens when camera is running. Also
bypass this behavior when video recording is active.
Bug: 240889279
Test: camera daemon cpuset changed as expected
Change-Id: I1d35bacf3d907a3e7ca9f18c213c941b55768500
Camera hints was canceled at activityStop and applied the rule for
a while after LAUNCH hint, exten the LAUNCH HINT to fix it.
Bug: 255927500
Test: build and launch/exit camera
Change-Id: I48d9c50c36bc974088a55ca70aa87f53ac9d8647
extend this to prevent alsa trigger stop playback
and causing pop
Bug: 238056484
Signed-off-by: vincenttew <vincenttew@google.com>
Change-Id: I1c4bf46a51893717b8d184a0919073eafcdc1e50
INTERACTION is removed but some actions still use it.
Bug: 246738037
Test: pts-tradefed run commandAndExit pts -m PtsPerformanceTestCases -t
com.google.android.perf.pts.PowerHintJsonVerifyTest
Change-Id: Iaecddf37361eeda9697dd6324a4de9cc33511f5c
Since those feature was enabled in android T,
disabling these features as android S version.
Bug: 241353178
Test: check the value after device boot up
Test: update PtsHapticsTestCases and run it
Signed-off-by: Chase Wu <chasewu@google.com>
Change-Id: I1b363136147beff334fba0ca1e065729dcfb57e4
Merged-In: I1b363136147beff334fba0ca1e065729dcfb57e4
With systemui now changed its cpuset in early stage, we no longer
need RestrictedCpuset hint as workaround.
Bug: 242775562
Test: build pass
Change-Id: I44477860126809487bb960eb1a0b037734357975
