2.5s is too short especially for fling, since we don't have
boostFramework to hint onFling() event, and prefling event on
perfd only last for 80ms which not usable at all, so the only
thing we can do is keep the boost duration for longer time.
Signed-off-by: debdeep199x <debdeep199x@gmail.com>
Currently, we're not using CAF's BoostFramework due to having a pure
AOSP based source, thus qcom perf hinting are not correctly applied.
This extension will handle the first app launch hinting through
device-specific mode override, utilizing existing libqti-perfd hinting.
So any further configuration should be happens inside app launch (V1)
config inside perfboostsconfig.xml
Signed-off-by: debdeep199x <debdeep199x@gmail.com>
handling
Currently, we're not using CAF's BoostFramework due to having a pure
AOSP based source, thus qcom perf hinting are not correctly applied.
This extension will handle the vertical fling through device-specific
boost override, utilizing existing libqti-perfd hinting.
So any further configuration should be happens inside vertical scroll
config inside perfboostsconfig.xml
Signed-off-by: debdeep199x <debdeep199x@gmail.com>
