| 9b1613de0aa905ca37e66a344d209d520a6f81f5 |
18-Apr-2017 |
Makoto Onuki <omakoto@google.com> |
Add missing services to incident_report
Bug 37306229
Test: Manual test with "incident_report battery diskstats package"
Change-Id: I10c6e4514581aeef77e2609acc031ef38edb12f2
ncident.proto
|
| 958d0a503699840f8f4b85cafa62f3793c89ac73 |
07-Feb-2017 |
Netta P <nettap@google.com> |
Protobufferize PowerManager dumpsys
Bug: 34230125
Test: cts-tradefed run cts-dev -m CtsIncidentHostTestCase -t com.android.server.cts.PowerIncidentTest
Change-Id: Ib71563cfc9ca95c297111430d8bbe2ce88d7a41d
ooper.proto
essage.proto
essagequeue.proto
orksource.proto
|
| df1742ed47da1e9b61afeae16fa448d5302a8aa0 |
20-Jan-2017 |
John Reck <jreck@google.com> |
Overhaul GraphicsStatsService
* LRU cache of recently-used is dead, replaced
disk storage
* ASHMEM size is read from native by the system service,
no longer requires keeping a sizeof() in sync with a
constant in Java
* Supports dumping in proto format by passing --proto
* Rotates logs on a daily basis
* Keeps a history of the most recent 3 days
Bug: 33705836
Test: Manual. Verified log rotating works by setting it up to
rotate every minute instead of day. Confirmed /data/system/graphicsstats
only has the most recent 3 entries after several minutes
Change-Id: Ib84bafb26c58701cc86f123236de4fff01aaa4aa
ncident.proto
|
| c9842c16274cbfaf60ad116b0f8bee913b82de7c |
07-Feb-2017 |
Julia Reynolds <juliacr@google.com> |
Dump notification records to proto
Bug: 34227881
Test: cts
Change-Id: I1b55d37ee73a17330f4039a50bdf05e9ce1be24d
ncident.proto
|
| 86882f4587031e48ef1bb60f5f3d8a9a5281c7ee |
26-Jan-2017 |
Mario Bertschler <bmario@google.com> |
App Widget Service with dump in protobuf format
Test: This protobuf format is validated as a CTS test
Bug: 33088921
Change-Id: I9d2a983052ade06cd3a13857b7e7f9e3d9bc275e
ncident.proto
|
| d72c39709d2f0a850dc32544324bfe4729ce81c6 |
28-Dec-2016 |
Eugene Susla <eugenesusla@google.com> |
Add ability to dump settings as proto buf
Test: Extracted the result via proto bug and as text and compared,
ran new CTS Setting incident test
Change-Id: Icf7b54b9c5c0a613dfd413ad575001c7b637ca01
ncident.proto
|
| da65a52f87ca1a31c9e01e99756e38d37d7e7202 |
13-Jan-2017 |
Makoto Onuki <omakoto@google.com> |
Support protofied dumpsys for NetStats
Bug 34228873
Test: manual tests with "incident_report netstats"
Change-Id: I359b364c64d9798fd4229018a905658d5d46ea5c
ncident.proto
|
| 7669012623a18855913c84ec0690066fbfd823ea |
20-Dec-2016 |
Joe Onorato <joeo@google.com> |
Clean up file names for protos
Test: cts-tradefed run singleCommand cts -d --module CtsIncidentHostTestCases
Change-Id: Iea2fc81768082e8e01afa8df86e113665020e7f6
ncident.proto
ncident_proto.proto
|
| 1754d744a7a34731ffc07af1bc3dbfcb06864ab0 |
22-Nov-2016 |
Joe Onorato <joeo@google.com> |
First checkin of incident reporting.
There are a few major pieces here:
incidentd
---------
This daemon (started by init) runs and accepts incoming requests to take
incident reports. When prompted, it calls into various system services
and fills in an IncidentProto data structure, and then writes the report
into dropbox.
The next steps for incidentd:
- Security review of SELinux policies. These will be a subset of
the dumpstate permissions. Until this is done, incidentd is
not started at boot time.
incident
--------
This shell command calls into incidentd, and can initiate an incident
report and either capture the output or leave for dropbox.
incident_report
---------------
This host side tool can call adb shell with the correct parameters
and also format the incident report as text. This formatting code
was left of the device on purpose. Right now it's pretty small, but
as the number of fields increases, the metadata and code to do the
formatting will start to grow.
The incident_report command also contains a workaround to let it
work before incidentd is turned on by default. Right now, it is
implemented to call adb shell dumpsys <service> --proto directly,
whereas in the future it will go through the full incidentd flow.
incident_section_gen
--------------------
A build-time tool that generates a stripped down set of information
about the fields that are available.
libincident
-----------
This library contains the code to connect to incidentd, and the
meta proto definitions that are used by the framework protos.
The basics are here now, but they are not fully fleshed out yet.
The privacy.proto file contains annotations that can go in the
proto file that we will later use to filter which fields are
uploaded, and which are used by local sources. For example, a
device in a test lab is safe to upload much much more information
than a real user. These will share the same mechanism, but the
user's output will be filtered according to these annotations.
frameworks/core/proto
---------------------
These .proto files contain the definitions of the system's
output. There is one master android.os.IncidentProto file that
is the top level of an incident report, but some other services
(notification, fingerprint, batterystats, etc) will have others
that are used directly by the logging mechanism.
Other files which are shared by several of the services also go
here, such as ComponentName, Locale, Configuration, etc. There
will be many more.
There is also a first iplementation of a dump method handling
--proto in the fingerprint service.
IncidentManager
---------------
The java API to trigger an incident report.
Test: Not written yet
Change-Id: I59568b115ac7fcf73af70c946c95752bf33ae67f
ncident_proto.proto
|