frameworks_base

Files

Yan Zhu 39b0e9a02b Add flag info to displays dump output proto

FLAG_PRIVATE information is needed for cts on physical private display

Bug: 133794475
Test: -Build and flash (make -j framework; aae flash 1s)
- Add "Log.d(TAG, display.toString())" in code to print out detailed
information about display. (Note: Display class is imported from
android.server.wm.WindowManagerState.Display)
- Check "mFlags=.." is printed

Change-Id: I6481dff51b140d3a9320e1e92b06fff531ba34e9

2019-09-05 14:05:28 +00:00

android

Add flag info to displays dump output proto

2019-09-05 14:05:28 +00:00

Android.bp

…

OWNERS

Merge "Add graphicsstats.proto owner"

2019-08-02 10:48:47 -07:00

README.md

…

README.md

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.thing instead of com.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. WindowManagerServiceDumpProto vs WindowManagerServiceProto.
- Inner messages whose containing messages have the Proto suffix do not need to have a Proto suffix. E.g:

message FooProto {
    message Bar {
        ...
    }
}

vs

message FooProto {
    message BarProto {
        ...
    }
}

If the proto represents the structure of an object, it should have Proto as 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_ms vs screen_time, or file_size_bytes or file_size_mebibytes vs file_size.
Leave field numbers 50,000 - 100,000 reserved for OEMs.