Starting March 27, 2025, we recommend using android-latest-release
instead of aosp-main
to build and contribute to AOSP. For more information, see Changes to AOSP.
Customization guidelines
Stay organized with collections
Save and categorize content based on your preferences.
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.
Customization guidelines
You can adapt or modify the base theme and structure as per the restrictions mentioned below.
The following table describes
the OEM responsibilities regarding customization.
Customization |
Description |
SHOULD |
Behaviors or interfaces that may be customized:
- Adjust overall theming and styling through a resource overlay
- Color pallette
- Sizing
- Text appearance
- Widget appearance
- Dialog appearance
- Drawables
- Enable or disable a feature gated by a config or change parameters configured by
resources
|
MAY |
Behaviors or interfaces Google recommends for an optimal user experience, but does not
enforce.
- Modify adaptive-responsive rules.
- Modify the high-level UI structure of Dialer. The Layout UI component must follow the
User Experience Restrictions.
|
Dialer belongs to a suite of system apps (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:
-
framework/base/core
All Android base styles are defined here. Specifically, all system app themes are
based on Theme.DeviceDefault
, the theme designed for use by OEMs to customize
device default appearance.
-
packages/services/Car/car_product/overlay
This folder contains overrides to Theme.DeviceDefault
which are used to produce
the AOSP look and feel of Android Automotive. OEMs might opt for excluding this overlay and
use their own
instead.
-
packages/apps/Car/libs/car-apps-common
Common colors and styles shared among AOSP provided system apps. These elements can
be customized by OEMs using overlays under
path/to/overlay/packages/apps/Car/libs/car-apps-common
.
-
packages/apps/Car/Dialer
Dialer uses its own theme, which extends from Theme.DeviceDefault
(defined in
framework/base
). The layouts, colors, styles, and other resources of Dialer can
also be customized through the use of an Overlay. Similar to libs
mentioned
above, the resource override can be located in
path/to/overlay/packages/apps/Car/Dialer
.
More documentation
For more information about AOSP theming and overlays, see
Customize the build with resource
overlays.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2024-08-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-26 UTC."],[],[],null,["# Customization guidelines\n\nThe Dialer implementation included in AOSP provides a base theme and structure you can adopt as\nis or modify.\n\nIn the table below, the descriptions of \"SHOULD\" and \"MAY\" are per the IETF standard defined\nin [Key words for use in RFCs to\nIndicate Requirement Levels (RFC 2119)](http://www.ietf.org/rfc/rfc2119.txt), the same standard used in the\n[Android 10 Compatibility Definition](/docs/compatibility/10/android-10-cdd).\n\nCustomization guidelines\n------------------------\n\nYou can adapt or modify the base theme and structure as per the restrictions mentioned below.\nThe following table describes\nthe OEM responsibilities regarding customization.\n\n| Customization | Description |\n|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **SHOULD** | Behaviors or interfaces that may be customized: - Adjust overall theming and styling through a resource overlay - Color pallette - Sizing - Text appearance - Widget appearance - Dialog appearance - Drawables - Enable or disable a feature gated by a config or change parameters configured by resources |\n| **MAY** | Behaviors or interfaces Google recommends for an optimal user experience, but does not enforce. - Modify adaptive-responsive rules. - Modify the high-level UI structure of Dialer. The Layout UI component must follow the User Experience Restrictions. |\n\nDialer belongs to a suite of system apps (including Media, Notification Center, and\nApp Launcher), all of which share common styles and assets that are defined at different levels in\nthe AOSP structure:\n\n- `framework/base/core` \n\n All Android base styles are defined here. Specifically, all system app themes are\n based on `Theme.DeviceDefault`, the theme designed for use by OEMs to customize\n device default appearance.\n\n- `packages/services/Car/car_product/overlay` \n\n This folder contains overrides to `Theme.DeviceDefault` which are used to produce\n the AOSP look and feel of Android Automotive. OEMs might opt for excluding this overlay and\n use their own\n instead.\n\n- `packages/apps/Car/libs/car-apps-common` \n\n Common colors and styles shared among AOSP provided system apps. These elements can\n be customized by OEMs using overlays under\n `path/to/overlay/packages/apps/Car/libs/car-apps-common`.\n\n- `packages/apps/Car/Dialer` \n\n Dialer uses its own theme, which extends from `Theme.DeviceDefault` (defined in\n `framework/base`). The layouts, colors, styles, and other resources of Dialer can\n also be customized through the use of an Overlay. Similar to `libs` mentioned\n above, the resource override can be located in\n `path/to/overlay/packages/apps/Car/Dialer`.\n\nMore documentation\n------------------\n\nFor more information about AOSP theming and overlays, see\n[Customize the build with resource\noverlays](/docs/setup/create/new-device#use-resource-overlays)."]]