This avoids flooding the log, when using the device.
I android.hardware.power-service-qti: Power setBoost: 0, duration: 351
I android.hardware.power-service-qti: Power setBoost: 1, duration: 0
I android.hardware.power-service-qti: Power setBoost: 0, duration: 0
I android.hardware.power-service-qti: Power setBoost: 0, duration: 0
I android.hardware.power-service-qti: Power setBoost: 1, duration: 0
I android.hardware.power-service-qti: Power setBoost: 0, duration: 0
I android.hardware.power-service-qti: Power setBoost: 0, duration: 0
I android.hardware.power-service-qti: Power setBoost: 0, duration: 1119
I android.hardware.power-service-qti: Power setBoost: 1, duration: 0
I android.hardware.power-service-qti: Power setBoost: 0, duration: 0
I android.hardware.power-service-qti: Power setBoost: 0, duration: 0
I android.hardware.power-service-qti: Power setBoost: 1, duration: 0
I android.hardware.power-service-qti: Power setBoost: 0, duration: 1492
I android.hardware.power-service-qti: Power setBoost: 1, duration: 0
Change-Id: I4e3c9ba79412875947593ea49739c3c30eabc429
* Using AOSP interface .clang-format
* Clean Android.mk while we are at it
Change-Id: I630f72e3dffb676ca1930e72945e897f62103ada
Signed-off-by: Arian <arian.kulmer@web.de>
Detect the support status of EXPENSIVE_RENDERING mode based on the
vendor property, which can be configured per target.
Change-Id: I39ed53f5df506bb8b7a714138d35e5b29bcfa4a5
CRs-Fixed: 3364809
When background_blur is enabled, the rendering can be expensive
and many janks will occur. So, need to support the mode in power
module and pass it to perf-hal to handle.
Change-Id: I5bab53e72134d76201d9fc28b9bdae4185790deb
CRs-Fixed: 3278491
Moving from the default implementation to a binderized service with no
wrapping.
Now using 1.2 implementation of the IPower interface.
Change-Id: Ibefd916544f51545e6889684a051b2ecc5867fe2