Common Criteria mode puts device into a state where certain funtionalities are tuned or turned on to meet the higher security requirement from Common Criteria certification. Device Owner can use the new device policy API to toggle Common Criteria mode. Bug: 137937540 Test: atest FrameworksServicesTests:DevicePolicyManagerTest Test: atest SettingsProviderTest Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testCommonCriteriaMode Test: atest com.android.cts.devicepolicy.OrgOwnedProfileOwnerTest#testCommonCriteriaMode Change-Id: If07c053437e980ed3317d3838cc74e5bfd44efce
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.