Add new mechanism for stopping FP HIDL after several times init fail.
This prevents the case of FP HIDL keeping trying to do init process and
raising CPU usage when sensor totally dead.
After limited times init retry fail (default 10 times), FP HIDL will
be stopped.
init-fingerprint-sh is for stopping fps_hal after init retry fail
serval times.
It keeps running until max init retry or fps_hal running successfully.
vendor.fps_hal restarts until max init retry times fail.
Test: build pass and FP functionaily are good.
Test: init process will be stopped after limited times retry fail
Bug: 111710758
Change-Id: I8a19bdd351e5d712f8e23c6a0849acb1771e61e5
Signed-off-by: emilchung <emilchung@google.com>
This reverts commit 1000b4e9fa.
Reason for revert: Broke build of partner-q-fs-release-generic-fs/mini_arm64-userdebug, which apparently has the device/google/wahoo project but not the hardware/google/pixel project.
Bug: 118339706
Change-Id: Ie6331a07b39267a8543fa0eacc0c7cd872d67119
Added a new flag to specify the IWLAN operation mode. Also
allowed this system properties for vendor native service to
access.
Test: Manual
Bug: 73659459
Change-Id: I5b64c6c437a3dc11a361121e2652a3f30f357105
The HAL API includes a "debug" interface that can be invoked from the
command line to get debug output for a particular HAL. While the
existing PowerHAL implementation includes support for the "debug"
interface, it only includes data for the performance hinting side of the
HAL. To facilitate device troubleshooting (not just of the HAL itself,
but of power drain), this change expands that implementation to also
include the output from calls to getPlatformLowPowerStats() and
getSubsystemLowPowerStats().
On existing in-market devices where this support is present, the command
lshal debug android.hardware.power@1.3::IPower/default
will produce the "debug" output.
The code for dumping the PowerHAL stats data is generic across
device-specific PowerHAL implementations, so it is all pushed up into a
new library (see topic CLs) that will eventually host additional
PowerHAL implementation code.
Bug: 116750864
Test: Ran code on an active P17 device.
Test: Added temporary test code (triggered by appending " test" to the
command above) to cover all base cases of data being present absent
(test code is included in first uploaded patchset on the corresponding
crosshatch CL).
Change-Id: Id97534a2a9fe05bbca614c763c907daea37e9723
Input configuration files should be in /vendor, not in /system, since
these are device-specific
Bug: 112880217
Test: dumpsys input and observe that the files are placed into /vendor
Change-Id: I6212dbe2eb75115baa02d4db3c9e1b82569d0bd3
- turn on config and add effect library for Waves effect
Bug: 111283341
Test: build pass and manual audio test on product/aosp
Change-Id: Idba8eb83a88e3aa4f254b5ab4beddaa6a4477cd8
Signed-off-by: Jasmine Cha <chajasmine@google.com>
* changes:
Modify ramoops sepolicy due to some ramoops file paths are changed to vendor partition
Change the file path of ramoops shell script and remove ramoops runcom
Put the inir.ramoops.sh to /vendor/bin/
The ramoops run commands are recorded in init.ramoops.rc individually
Bug: 113147446
Test: Build pass and test on walleye and taimen
can generate ramoops successfully.
Change-Id: I370cdfc36d7031a7f695abc2045ff756066d1902
Signed-off-by: Chungjui Fan <chungjuifan@google.com>
Add property to disable usb overheat mitigation that prevent device
offline during thermal testing in chamber.
Bug: 111762741
Test: Run thermal test in chamber
Change-Id: I23a760c8e31979b38ae89cd6750ae107605d5c3b
Setting PRODUCT_COMPATIBLE_PROPERTY_OVERRIDE to true blocks
System-only-OTA from OMR1 devices because it does not allow some
propertis set by the OMR1 vendor partition.
Only if we include the VNDK snapshot v27 to wahoo devices, remove
PRODUCT_COMPATIBLE_PROPERTY_OVERRIDE from wahoo as well as ag/3694012
for rild.
Bug: 74505580
Test: Check if Bluetooth could be turned on in P-OMR1 walleye device.
Change-Id: I5113988b10f0cdde394ed2fc31ebc9d1ea811e1c
Wahoo devices don't have keymaster4 hardware, just a software
implementation that was used for testing.
Bug: 77307896
Test: Check that the KM4 binary and RC are no longer on the device
Change-Id: I607937921c09bf24bb971bb7ef089aab2346debd
