am: 7888554b

Change-Id: Ibe7719c8be0dbf5f215e8b32374d8cb4fe4e7869

am: 3c8cd0cd

Change-Id: Ida3e5c78a1e143a242b47183b1f176a3ebbbd8fd

am: 75e4a422

Change-Id: I1d0b87ac34613f739e24d3a8ff13798778b89117

Bug: 30188076
Test: make checkbuild
Change-Id: I02fe530f6bc3f632c4179d2d1bf8ce40970e4b25

am: 329b994e

Change-Id: I7d9b69b050e776a9cc62a23ebe51b4c2420b265c

am: 4d0a75dc

Change-Id: I27ca922115b308935d6f6482c34099496cdfd9a0

am: eafda485

Change-Id: I8cc071d266f405dd4987c4cc13523e96a2936bd7

Bug: 30188076
Test: make checkbuild
Change-Id: I126c6f8c86455bf63a9dce5e3a535abbaa7c0c73

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