android_frameworks_base

History

paulhu 5555c00e61 Remove NSD_ON setting

NSD_ON setting has never been set since it created. The
NsdService is the only user which read/write the setting.
However, NsdManager cts test must running with nsd service
enabled that means this setting should be enabled
always. And this setting is the hidden symbols that
NsdService can't use it after move to mainline module. Thus,
remove this useless setting.

Bug: 206702844
Test: m
Change-Id: Idb5dfc71ebfe2eacd476dd8646aad9adc4975149

2021-12-21 14:55:54 +08:00

android

Remove NSD_ON setting

2021-12-21 14:55:54 +08:00

OWNERS

Merge sc-qpr1-dev-plus-aosp-without-vendor@7810918

2021-11-18 17:00:37 +00: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.