Evolution-X-Tensor/device_google_zumapro
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Disable dumpstate strict-run flag in zumapro

Browse source 
The change disables the dumpstate strict-run flag in zumapro devices, which is enabled by default. Disabling this flag increases the timeout for capturing incident report to 120 seconds, from the default 20 seconds. This is done because 20s isn't enough to capture incident report proto in some cases, especially when device is throttling.

Bug: 329683355

Test: Booted a zumapro device with the change. Then manually thermal throttled the device and captured bugreports. In some tests Incident report took more than 20s, up to 55s, and in all these cases it was succesfully captured.

Change-Id: I0b12c041c8ac864897db53f44ce51292e1ca36bb
This commit is contained in:
SaiChand Duppala 2024-03-14 14:37:26 -07:00
parent 0cf027cad7
commit aab13b2ec6
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
device.mk
View file

@ -1191,3 +1191,9 @@ PRODUCT_CHECK_DEV_TYPE_VIOLATIONS := true
# TODO(b/322518837): Remove the property override once the flag is launched. # TODO(b/322518837): Remove the property override once the flag is launched.
PRODUCT_PROPERTY_OVERRIDES += \ PRODUCT_PROPERTY_OVERRIDES += \
debug.bugle.enable_emergency_satellite_messaging=true debug.bugle.enable_emergency_satellite_messaging=true
# Allow longer timeout for incident report generation in bugreport
# Overriding in /product partition instead of /vendor intentionally,
# since it can't be overridden from /vendor.
PRODUCT_PRODUCT_PROPERTIES += \
dumpstate.strict_run=false