The Dialer implementation included in AOSP provides a base theme and structure you can adopt as is or modify.
In the table below, the descriptions of “SHOULD” and “MAY” are per the IETF standard defined in Key words for use in RFCs to Indicate Requirement Levels (RFC 2119), the same standard used in the Android 10 Compatibility Definition.
The Dialer implementation included in AOSP provides a base theme and structure that can be adopted as is, or modified according to the following restrictions. The following table describes OEM responsibilities regarding customization.
Behaviors or interfaces that may be customized:
Behaviors or interfaces Google recommends for an optimal user experience, but does not enforce.
Dialer belongs to a suite of system applications (including Media, Notification Center, and App Launcher), all of which share common styles and assets that are defined at different levels in the AOSP structure:
All Android base styles are defined here. Specifically, all system application themes are based on
Theme.DeviceDefault, the theme designed for use by OEMs to customize device default appearance.
This folder contains overrides to
Theme.DeviceDefaultwhich are used to produce the AOSP look and feel of Android Automotive. OEMs might opt for excluding this overlay and use their own instead.
Common colors and styles shared among AOSP provided system applications. These elements can be customized by OEMs using overlays under
Dialer uses its own theme, which extends from
framework/base). The layouts, colors, styles and other resources of Dialer can also be customized through the use of an overlay. Similar to
car_libmentioned above, the resource override can be located in
For more information about AOSP theming and overlays, see Customizing the build with resource overlays.