While Google found that fingerprint HAL is insensitive to
increased CPU throughput, we have not found that to be the
case. Allowing more CPUs makes fingerprint unlock up to
2x faster in some tests.
SM8250 device with fingerprint on display:
- Before: 3128ms
- After: 944ms
SDM845 device with fingerprint on the power button:
- Before: 1146ms
- After: 688ms
This reverts commit d0fdb4431d26e4f257b8867f67ffd9b4a9818d9e.
Change-Id: Ia51ceb43ac940dfdae733919fbd685156d082568
Signed-off-by: pix106 <sbordenave@gmail.com>
writepid command usage to join a cgroup has been deprecated in favor
of a more flexible approach using task_profiles. This way cgroup path
is not hardcoded and cgroup changes can be easily made. Replace
writepid with task_profiles command to migrate between cgroups.
Bug: 191283136
Test: build and boot
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: If0a64b9f335ad13f65522361b125cab951002a2c
Signed-off-by: pix106 <sbordenave@gmail.com>
The fingerprint HAL is insensitive to increased CPU throughput, but it also
has a tendency to spin while waiting for FP hardware. Limit FPC to the
system-background cpuset in order to avoid increased power consumption
when accidentally touching the fingerprint sensor.
bug 76115243
Test: fingerprint in system-background cpuset
Change-Id: Iaffe6f63bd76b7a1c4acaf0cae980840af515961
Signed-off-by: Manish4586 <manish.n.manish45@gmail.com>
