vibrator: Add a threshold to filter out some short vibration cases
Some app will use short vibration to implement haptics effect and those cases will feel a delay from the motion awareness mechanism. We add this patch to filter out those cases since those behaviors beyond the motion awareness mechanism scope. Bug: 162346934 Test: UT test Signed-off-by: chasewu <chasewu@google.com> Change-Id: Iee8d5993f040126243d90330f03b897970c70c1b
This commit is contained in:
parent
3070ff7642
commit
214cb227e2
|
@ -75,6 +75,7 @@ static struct timespec sGetTime;
|
|||
#define SENSOR_DATA_NUM 20
|
||||
// Set sensing period to 2s
|
||||
#define SENSING_PERIOD 2000000000
|
||||
#define VIBRATION_MOTION_TIME_THRESHOLD 100
|
||||
#define ARRAY_SIZE(a) (sizeof(a) / sizeof((a)[0]))
|
||||
|
||||
int GSensorCallback(__attribute__((unused)) int fd, __attribute__((unused)) int events,
|
||||
|
@ -500,7 +501,9 @@ ndk::ScopedAStatus Vibrator::on(int32_t timeoutMs,
|
|||
if (temperature > TEMP_UPPER_BOUND) {
|
||||
mSteadyConfig->odClamp = &mSteadyTargetOdClamp[0];
|
||||
mSteadyConfig->olLraPeriod = mSteadyOlLraPeriod;
|
||||
if (!motionAwareness()) {
|
||||
// TODO: b/162346934 This a compromise way to bypass the motion
|
||||
// awareness delay
|
||||
if ((timeoutMs > VIBRATION_MOTION_TIME_THRESHOLD) && (!motionAwareness())) {
|
||||
return on(timeoutMs, RTP_MODE, mSteadyConfig, 2);
|
||||
}
|
||||
} else if (temperature < TEMP_LOWER_BOUND) {
|
||||
|
|
Loading…
Reference in New Issue