frameworks_base

Files

Arc Wang 036f404d88 Add action metrics for Wi-Fi provision features

// ACTION: Share a Wi-Fi network by generating a QR code
  ACTION_SETTINGS_SHARE_WIFI_QR_CODE

  // ACTION: Connect to a Wi-Fi network by scanning a QR code
  ACTION_SETTINGS_ENROLL_WIFI_QR_CODE

  // ACTION: Share Wi-Fi hotspot by generating a QR code
  ACTION_SETTINGS_SHARE_WIFI_HOTSPOT_QR_CODE

Bug: 130521826
Test: manual
Change-Id: I99e55b53c49830347e48f688aa38afc3912e71b1

2019-04-23 11:26:45 +08:00

android

Add action metrics for Wi-Fi provision features

2019-04-23 11:26:45 +08:00

Android.bp

Atom: Add more Bluetooth atoms

2019-01-28 17:30:05 -08:00

OWNERS

Merge "Add zhfan as owner of settings_enums.proto."

2018-11-07 19:46:22 +00:00

README.md

Refactoring GlobalSettingsProto to avoid method limit.

2018-03-23 18:03:43 -07:00

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.