Age | Commit message (Collapse) | Author |
|
|
|
Change-Id: I38176d1aa568e0583eda7b2a0fbe4393d32725f8
|
|
Change-Id: I30ed2047edf93e528c020b4d571c55fa99c4e57b
|
|
Added more information to analysis. Also added rule for Interrupts
Change-Id: I090ec531d170693a3a96047a02c3b057cfb80bb4
|
|
Change-Id: I5f6bbf8ee41311ef7dfb3d60fd76c7d902c187f8
|
|
Change-Id: Ib513af70611367dd0ddce5b21ae7df56a2371b4d
|
|
Parse the activity service section and retrieve location usage clients
Change-Id: I71fb6331be713b3b8653834feea05c88deab68b6
|
|
|
|
Change-Id: Ifd2c923750dc6f2b5f8104aa3993277648fcf7b9
|
|
At present the only way to get a new LogcatItem is to reinstantiate the
LogcatParser; adding clear() will allow each parser to easily produce
multiple LogcatItems during its lifetime.
Change-Id: I0025d8509d75936d9bb29b94f278b788f4a2ab91
|
|
|
|
Bug: 26140048
Change-Id: I9b7e46ee9fb5eb34de56ff4832ec942947b5b2cc
|
|
Change-Id: Ic878cf94ecc5fd16ba12a81409dbb2ea09097563
|
|
Bug: 25597146
Change-Id: If8617d180fc37eb756e89bb24d7a2e12d9be9533
|
|
Change-Id: Ie36b3192e49aa3570185da5eab78157e85e27e41
|
|
I think inspect bug was expecting a stack to be present so just set it as
unkown.
Bug: 24304795
Change-Id: Ia91246f2769889e7bb11bd2b8b972d8a92afc0ef
|
|
|
|
qtaguid includes network usage per uid, but it does not contain actual
package names. Therefore, we have to also collect package UIDs.
Change-Id: I6bbc9e0a266c15328f51bb3d7c915f242669fb43
|
|
|
|
Change-Id: I1daa01a9d1312c7356667ca80909487b9ce5df5c
|
|
|
|
Change-Id: I2fc18f621b0cfba50339b561315a1996325604f6
|
|
In one of the recent devices, surfaceflinger dumpsys contains lines
that match the no_op regex and hence the remaining dumpsys items are
not processed. Hence batterystats parser is returning null.
Affecting string: "------ DrmDisplayCompositor Layer: plane=21 disabled"
Change-Id: Idc3489bed8ebfa0ab08cae8eaceebe264243d9e5
|
|
In some bugreports kernel wakelock section is missing. This prevents
parsing of partial wakelock as well. So this fix is to separate kernel
and partial wakelock parsing
Change-Id: I196dcd9438976cb5d3fcd3b0a81839903aebac15
|
|
Native crashes used to always start with "*** *** ... ***" but not anymore.
The next line is always "Build fingerprint: ..." so start with that.
Bug: 21642733
Change-Id: I0e1b7c6a70f646ea27f7da62f141d14b6c75dd58
|
|
Change-Id: I5000e4352ded2eaa004bc486242c241bcdf4dada
|
|
Change-Id: Ib73fe8215bf5b9cf8cd6dd58c54eb481c38cc483
|
|
Native crashes sometimes appear in logcat with F DEBUG as the level and tag.
Refactor the crash tag mechanism to allow for 2 signatures for native
crashes but keep it private (for now) since there isn't a public need to
add more (like there is for Java crashes).
Bug: 20917511
Change-Id: Ieae63d45553ac8cf92977d69028783b7367c2162
|
|
|
|
Initial version of the battery drain investigator. It parses the bugreport
for power specific sections and returns the analysis in JSON format
Change-Id: I56c1e010666892b1296272942cc5edcc5072c731
|
|
BUG: 19963847
Change-Id: I9e380ecba32313e1f423b5af192acf0010487730
|
|
Change-Id: I5508f0c24cfff566db167e8e7dba772a8b17950f
|
|
Change-Id: I949bf99eae6ae4c45140ab90659b7fc9b20f703e
|
|
Change-Id: I01e9fcb3a1a52471add6cde81e0db6fc68583375
|
|
Change-Id: Idcc68cd6e02781647f8ca8e2aa8bee19f5991977
|
|
Change-Id: Ic16907e7e98ee1a9be9b0a75b9cccffee6c75441
|
|
Bug: 17674945
Change-Id: Iabe3b791395e28caeaed8a54f5e7aa532d3966e5
|
|
|
|
Ignore entries with values greater than a long instead of crashing.
Change-Id: I62410d4083169143049229afd47236a0984b3c42
|
|
Bug: 17252597
Change-Id: I87e359535c7aea42f6e669a5e83eb0b1abdd4930
|
|
Also, bring kernel log parser in line with APR and only record first
kernel reset.
Bug: 14829888
Change-Id: Ice5db062b3fc8ece774afc8e284f1a276aa52d43
|
|
Change-Id: I4e14fb4dc3414b6a78d1b5456403699980abb8a8
|
|
Bug: 14445952
Change-Id: I52ef8fc3f9b78e4aba24f6c3f0fc166eafb06780
|
|
Change-Id: I9ff2677f75bb2b77e07c3a9e391235c3f7004eec
|
|
Change-Id: Ibd1f4d81b94b3ddb11726b70dbb26603cfdcfbc7
|
|
A recent change mean that all native crashes were printed with the same PID
and TID which broke how we parsed. Now look for the start of the native crash
as well as changes in PID/TID.
Bug: 13098304
Change-Id: Ia691000b99328e0dbd1514a379a9e6528189430a
|
|
Bug: 12903905
Change-Id: I0a7551f4ad7bc000f006e4adf82140427b1265bc
|
|
Bug: 12995243
Change-Id: I25636ccbac15cfd3fd788c4557a7b71f14e29b8c
|
|
Change-Id: I283bf137b382e440216665188e4444a4fe48e782
|
|
|