blob: a38a437896970fc500cf1cc883f3ca2c7f0229f4 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<!--
/*
** Copyright 2015, The Android Open Source Project
**
** Licensed under the Apache License, Version 2.0 (the "License");
** you may not use this file except in compliance with the License.
** You may obtain a copy of the License at
**
** http://www.apache.org/licenses/LICENSE-2.0
**
** Unless required by applicable law or agreed to in writing, software
** distributed under the License is distributed on an "AS IS" BASIS,
** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
** See the License for the specific language governing permissions and
** limitations under the License.
*/
-->
<!-- These resources are around just to allow their values to be customized
for different hardware and product builds. Do not translate. -->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<!-- Enable multi-user. -->
<bool name="config_enableMultiUserUI">true</bool>
<!-- Maximum number of users we allow to be running at a time.
For automotive, background user will be immediately stopped upon user switching but
up to this many users can be running in garage mode.
3 = headless user 0 + two primary users or 1 primary + 1 guest -->
<integer name="config_multiuserMaxRunningUsers">3</integer>
<!-- Use delay loccking mode always for automotive -->
<bool name="config_multiuserDelayUserDataLocking">true</bool>
<!-- If true, all guest users created on the device will be ephemeral. -->
<bool name="config_guestUserEphemeral">true</bool>
<!-- Car Mode -->
<integer name="config_defaultUiModeType">3</integer>
<!-- Can't leave car mode -->
<bool name="config_lockUiMode">true</bool>
<!-- Control whether to launch Car dock home app when user presses home button or when
car dock intent is fired.
In mobile device, usually separate home app is expected in car mode, and this should be
enabled. But in environments like real car, default home app may be enough, and in that
case, this can be disabled (set to false). -->
<bool name="config_enableCarDockHomeLaunch">false</bool>
<!-- Control whether to lock day/night mode change from normal application. When it is
true, day / night mode change is only allowed to apps with MODIFY_DAY_NIGHT_MODE
permission. -->
<bool name="config_lockDayNightMode">true</bool>
<!-- Allow smart unlock immediately after boot because the user shouldn't have to enter a pin
code to unlock their car head unit. -->
<bool name="config_strongAuthRequiredOnBoot">false</bool>
<!-- Show Navigation Bar -->
<bool name="config_showNavigationBar">true</bool>
<integer name="config_jobSchedulerInactivityIdleThreshold">0</integer>
<integer name="config_jobSchedulerIdleWindowSlop">0</integer>
<!-- Automotive Bluetooth pairing option -->
<bool name="enable_pbap_pce_profile">true</bool>
<!-- Whether the device supports quick settings and its associated APIs -->
<bool name="config_quickSettingsSupported">false</bool>
<!-- Flag indicating that the entire notification header can be clicked to expand the
notification. If false, then the expand icon has to be clicked in order for the expand
to occur. -->
<bool name="config_notificationHeaderClickableForExpand">true</bool>
<!-- Night mode should be enabled. -->
<bool name="config_enableNightMode">true</bool>
<!-- The action buttons should always take the default color. -->
<bool name="config_tintNotificationActionButtons">false</bool>
<!-- Corner radius of system dialogs -->
<dimen name="config_dialogCornerRadius">16dp</dimen>
<!-- Set CarUsbHandler as the USB handling component by default -->
<string name="config_UsbDeviceConnectionHandling_component">android.car.usb.handler/android.car.usb.handler.UsbHostManagementActivity</string>
<string name="config_headlineFontFamilyMedium">sans-serif-medium</string>
<!-- Whether the system enables per-display focus. If the system has the input method for each
display, this value should be true. -->
<bool name="config_perDisplayFocusEnabled">true</bool>
<!-- True if the device supports split screen as a form of multi-window. -->
<bool name="config_supportsSplitScreenMultiWindow">false</bool>
<!-- True if the device supports system decorations on secondary displays. -->
<bool name="config_supportsSystemDecorsOnSecondaryDisplays">false</bool>
<string name="config_dataUsageSummaryComponent">com.android.car.settings/com.android.car.settings.datausage.DataWarningAndLimitActivity</string>
<!-- Controls whether system buttons use all caps for text -->
<bool name="config_buttonTextAllCaps">false</bool>
<bool name="config_automotiveHideNavBarForKeyboard">true</bool>
<!-- Turn off Wallpaper service -->
<bool name="config_enableWallpaperService">false</bool>
<!-- Whether to only install system packages on a user if they're whitelisted for that user
type. Override the default value in framework config file.
0 - disable whitelist (install all system packages; no logging)
1 - enforce (only install system packages if they are whitelisted)
2 - log (log when a non-whitelisted package is run)
4 - any package not mentioned in the whitelist file is implicitly whitelisted on all users
8 - same as 4, but just for the SYSTEM user
16 - ignore OTAs (don't install system packages during OTAs)
Common scenarios for auto:
- to enable feature (fully enforced) for a complete whitelist: 1
- to enable feature for an incomplete whitelist (so use implicit whitelist mode): 5 -->
<integer name="config_userTypePackageWhitelistMode">5</integer> <!-- 1+4 -->
<!-- Default user restrictions for system user 0. -->
<string-array translatable="false" name="config_defaultFirstUserRestrictions">
<item>"no_modify_accounts"</item>
</string-array>
</resources>