debugfs not accessible in user builds. Hence dumping through
sysfs.
Bug: 200313640
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
Change-Id: I5e42d1cd9b53c0989dbbb35bf580271d15cd8db3
dumpstate availible to dump data with below 2 permission:
-r--r--r-- 1 root root
-r--r----- 1 system system
but /d/regmap permission is -r-------- 1 root root
1. we cannot change root to system with chown if the file node is root
2. we cannot change to read with chmod if the file node is root
3. try change permission in vendor_init causes sepolicy build fail with
message rule neverallow
Base on above results, we added new file node in kernel with available
permission to dump needed data and dump it.
Bug: 194941806
Test: adb bugreport
Change-Id: Ieeb1adfb0351ceb33bf817cbef3663d41cdb8645
Signed-off-by: Ted Lin <tedlin@google.com>
dumpstate availible to dump data with below 2 permission:
-r--r--r-- 1 root root
-r--r----- 1 system system
but /d/regmap permission is -r-------- 1 root root
1. we cannot change root to system with chown if the file node is root
2. we cannot change to read with chmod if the file node is root
3. try change permission in vendor_init causes sepolicy build fail with
message rule neverallow
Base on above results, we added new file node in kernel with available
permission to dump needed data and dump it.
Bug: 194941806
Test: adb bugreport
Change-Id: Ieeb1adfb0351ceb33bf817cbef3663d41cdb8645
Signed-off-by: Ted Lin <tedlin@google.com>
MPMM/PPM readings, OFFSRC and PWRONSRC will be printed out.
Bug: 195455000
Test: Local Test and confirm its printed.
------ Instruction ... ------
enable_mitigation=1
mpmm_settings=0x1a
offsrc=0x0
ppm_settings=0x0
pwronsrc=0x4
Signed-off-by: George Lee <geolee@google.com>
Change-Id: I1f3e10edc416966f0eba18e0ba94fb56a487eaee
These are small, usually <1MB. Attaching more CPA traces gives us some
buffer to ensure that the relevant trace is actually included in the bug
report. Previously if the user opens one or two more camera sessions
after they observe the performance issue, the trace will be missing.
Bug: 191169822
Test: Build
Change-Id: I4c10217c39991e80f25a7fd90eee9e8b8c5b6cdb
This also change the sequence of run_rawcap_read_all
and run_self_rawcap_read_all to last. Because these
two commands need to run selftest first to read data,
this will make ambient update to make other raw data with
differen baseline.
Bug: 195111369
Test: check touch data in bugreport.
Signed-off-by: Super Liu <supercjliu@google.com>
Change-Id: I4693b099fbc98d80fbe166525773e3ab803c98d8
Dump state2power table in cooling_device
Bug: 189488358
Test: local test and state2power table can be dumped.
Change-Id: Ifb9a8e41158c5452b2f6e856d30ac97011460298
Signed-off-by: David Chao <davidchao@google.com>
Bug: 194157915
Test: bugreport works normally for touch.
Signed-off-by: Super Liu <supercjliu@google.com>
Change-Id: Ice27991a4cac9cca875b55241126bc6f88fb62b6
* Latest is determined by alphabetical order
* To find the .cpa file, unzip the bug report and run `tar -xvf dumpstate_board.bin`
* The .cpa file can then be found under the `camera/` directory
* This can be disabled with the prop `vendor.camera.debug.camera_performance_analyzer.attach_to_bugreport`
Bug: 191169822
Test: `adb bugreport`, unzip, `tar -xvf dumpstate_board.bin`, find expected .cpa file
Change-Id: Ie05e8d446588cebea46492b267491065161915a1
In b/183180525, vendor mentioned they won't provide
fw symbol table (logstrs.bin) in terms of their internal
concern. Hence, remove wifi fw symbol table from dumpstate.
Bug: 191429306
Test: build pass, device can connect to AP.
Change-Id: I54a012f619f113a2567a93707731b5c4802b1da8
Bug: 174189876
Test: check bugreport for #19 data.
Signed-off-by: Super Liu <supercjliu@google.com>
Change-Id: I288d8079528f99834a1867ab973535d4e7b383b6
Dumpstate will only collect always-on modem logs,
should only stop modem logging when it is always-on
Bug: 189441741
Change-Id: Icc4e1940aab774d56e51e966248985dda539890c
Only dump the latest dump files so that bugreport
size won't be increased by too much.
Test: build and capture bugreport
Bug: 178737594
Change-Id: I699ee76997c9107dad13419688f3c6c04551313b
Use bugreport flag to keep waking up the touch driver instead of
force active flag to prevent the kernel driver from blocking CPU
enter the suspend mode.
Bug: 183466375
Test: touch driver won't block system suspend.
Signed-off-by: davidycchen <davidycchen@google.com>
Change-Id: I586173485bd41deac891b7edb366b51a99977434
This is a manual porting from ag/10344396.
Replace the usage of "persist.vendor.verbose_logging_enabled" since we are not using
this property for Whitechapel.
Use the default property "persist.dumpstate.verbose_logging.enabled" instead.
Test: atest VtsHalDumpstateV1_1TargetTest pass
Bug: 186539439
Change-Id: I3f0d35647c0748d360b12d3be078d514f99d23d5
Need setting information for debugging
Bug: 186872139
Signed-off-by: Jenny Ho <hsiufangho@google.com>
Change-Id: Iaf7345a4f38a67c4134f5cb23050b5f5e6ba7fdd
This collects the output of "usf_reg_edit save -" and adds it to the
bugreport. It is only done on userbuilds for PROTO* and EVT* devices.
Bug: 187081112
Test: Run "adb bugreport <zip>" and verify it contains the output
from "usf_reg_edit save -".
Change-Id: Ie68b56a3bb211840f33bdb5afbc31b0759641c8e
Bug: 183467815
Test: 1. Enable tcpdump_logger always-on function
2. Dump bugreport
3. Pull dumpstate_board.bin and chagne it to zip
4. Unzip dumpstate_board.zip and check if tcpdump files
are there.
Change-Id: If5fc2fe8ff4bfc0beb91ff973cc3d8137fd7cc47
