Currently, we are only using UsageStatsProto for backup and restore purposes but to ensure it is in sync with UsageStatsProtoV2, adding the recently added LOCUS_ID event. This enables us to easily fall back to the earlier proto version if there are issues with V2. This also allows us to backup all events data if we decide to do that in the future before updating the B&R restore logic to use V2. Bug: 155935953 Test: atest UsageStatsDatabaseTest Change-Id: I792f20a0b44d13f1ed17c4dbebe5555044afa165
Conventions for the protos in this directory:
-
As in the rest of Android, use 4 spaces to indent instead of 2.
-
For protos based on Java files, use the same package as the Java file. For example,
com.android.server.thinginstead ofcom.android.server.thing.proto. -
If the proto describes the top level output of dumpsys, it should contain
Dump. This makes it easy to understand that the proto is the dumpsys output of a certain service, not the data structure of that service, e.g.WindowManagerServiceDumpProtovsWindowManagerServiceProto.- Inner messages whose containing messages have the
Protosuffix do not need to have aProtosuffix. E.g:
- Inner messages whose containing messages have the
message FooProto {
message Bar {
...
}
}
vs
message FooProto {
message BarProto {
...
}
}
-
If the proto represents the structure of an object, it should have
Protoas its suffix. Please also include the full package path of the original object as a comment to the proto message. -
Include units in the field names. For example,
screen_time_msvsscreen_time, orfile_size_bytesorfile_size_mebibytesvsfile_size. -
Leave field numbers 50,000 - 100,000 reserved for OEMs.