1edcb1863b
With the QPR2 merge, the AOSP implementation doesn't allow toggling linked & unlinked volumes as a setting; it has to be set by config or overlay. Since we like customization, enable separated volumes Also needed crdroidandroid/android_frameworks_base@922f964 Signed-off-by: AmolAmrit <amol.amrit03@outlook.com>
163 lines
9.0 KiB
XML
163 lines
9.0 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
Copyright (C) 2022 The Linux Foundation
|
|
SPDX-License-Identifier: BSD-3-Clause
|
|
-->
|
|
<resources>
|
|
|
|
<!-- Control whether the always on display mode is available. This should only be enabled on
|
|
devices where the display has been tuned to be power efficient in DOZE and/or DOZE_SUSPEND
|
|
states. -->
|
|
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool>
|
|
|
|
<!-- Whether a software navigation bar should be shown. NOTE: in the future this may be
|
|
autodetected from the Configuration. -->
|
|
<bool name="config_showNavigationBar">true</bool>
|
|
|
|
<!-- When true use the linux /dev/input/event subsystem to detect the switch changes
|
|
on the headphone/microphone jack. When false use the older uevent framework. -->
|
|
<bool name="config_useDevInputEventForAudioJack">true</bool>
|
|
|
|
<!-- Telephony qualified networks service package name to bind to by default. -->
|
|
<string name="config_qualified_networks_service_package" translatable="false">vendor.qti.iwlan</string>
|
|
|
|
<!-- IWLAN data service package name to bind to by default. If none is specified in an overlay, an
|
|
empty string is passed in -->
|
|
<string name="config_wlan_data_service_package" translatable="false">vendor.qti.iwlan</string>
|
|
|
|
<!-- IWLAN network service package name to bind to by default. If none is specified in an overlay, an
|
|
empty string is passed in -->
|
|
<string name="config_wlan_network_service_package" translatable="false">vendor.qti.iwlan</string>
|
|
|
|
<!-- Default files to pin via Pinner Service -->
|
|
<string-array name="config_defaultPinnerServiceFiles">
|
|
<item>/system/framework/arm64/boot-framework.oat</item>
|
|
<item>/system/framework/arm/boot-framework.oat</item>
|
|
<item>/apex/com.android.art/javalib/arm64/boot-core-libart.oat</item>
|
|
<item>/apex/com.android.art/javalib/arm/boot-core-libart.oat</item>
|
|
<item>/apex/com.android.art/javalib/arm64/boot-okhttp.oat</item>
|
|
<item>/apex/com.android.art/javalib/arm/boot-okhttp.oat</item>
|
|
<item>/apex/com.android.art/javalib/arm64/boot.vdex</item>
|
|
<item>/apex/com.android.art/javalib/arm/boot.vdex</item>
|
|
<item>/apex/com.android.art/javalib/arm64/boot-core-libart.vdex</item>
|
|
<item>/apex/com.android.art/javalib/arm/boot-core-libart.vdex</item>
|
|
<item>/apex/com.android.art/javalib/arm64/boot-core-libart.art</item>
|
|
<item>/apex/com.android.art/javalib/arm/boot-core-libart.art</item>
|
|
<item>/system/framework/framework-res.apk</item>
|
|
<item>/system/lib64/libhwui.so</item>
|
|
<item>/system/lib/libhwui.so</item>
|
|
<item>/system/framework/boot-framework.vdex</item>
|
|
<item>/system/framework/oat/arm64/services.vdex</item>
|
|
<item>/system/framework/oat/arm64/services.odex</item>
|
|
<item>/apex/com.android.art/javalib/arm64/boot.oat</item>
|
|
<item>/apex/com.android.art/javalib/arm/boot.oat</item>
|
|
<item>/system/framework/telephony-common.jar</item>
|
|
<item>/system/framework/arm64/boot-telephony-common.art</item>
|
|
<item>/system/lib64/libsurfaceflinger.so</item>
|
|
<item>/apex/com.android.art/javalib/core-oj.jar</item>
|
|
<item>/apex/com.android.art/javalib/core-libart.jar</item>
|
|
</string-array>
|
|
|
|
<!-- List of biometric sensors on the device, in decreasing strength. Consumed by AuthService
|
|
when registering authenticators with BiometricService. Format must be ID:Modality:Strength,
|
|
where: IDs are unique per device, Modality as defined in BiometricAuthenticator.java,
|
|
and Strength as defined in Authenticators.java -->
|
|
<string-array name="config_biometric_sensors" translatable="false" >
|
|
<item>0:2:15</item>
|
|
</string-array>
|
|
|
|
<!-- Whether the device enable the standalone (SA) mode of 5G NR.-->
|
|
<bool name="config_telephony5gStandalone">true</bool>
|
|
|
|
<!-- Whether the device enable the non-standalone (NSA) mode of 5G NR.-->
|
|
<bool name="config_telephony5gNonStandalone">true</bool>
|
|
|
|
<!-- The default journal mode to use use when Write-Ahead Logging is not active.
|
|
Choices are: OFF, DELETE, TRUNCATE, PERSIST and MEMORY.
|
|
PERSIST may improve performance by reducing how often journal blocks are
|
|
reallocated (compared to truncation) resulting in better data block locality
|
|
and less churn of the storage media.
|
|
The PERSIST mode results in data persisting in the journal beyond the life of
|
|
a transaction, so it interacts poorly with SECURE_DELETE. -->
|
|
<string name="db_default_journal_mode" translatable="false">MEMORY</string>
|
|
|
|
<!-- The database synchronization mode when using the default journal mode.
|
|
FULL is safest and preserves durability at the cost of extra fsyncs.
|
|
NORMAL also preserves durability in non-WAL modes and uses checksums to ensure
|
|
integrity although there is a small chance that an error might go unnoticed.
|
|
Choices are: FULL, NORMAL, OFF. -->
|
|
<string name="db_default_sync_mode" translatable="false">OFF</string>
|
|
|
|
<!-- The database synchronization mode when using Write-Ahead Logging.
|
|
From https://www.sqlite.org/pragma.html#pragma_synchronous:
|
|
WAL mode is safe from corruption with synchronous=NORMAL, and probably DELETE mode is safe
|
|
too on modern filesystems. WAL mode is always consistent with synchronous=NORMAL, but WAL
|
|
mode does lose durability. A transaction committed in WAL mode with
|
|
synchronous=NORMAL might roll back following a power loss or system crash.
|
|
Transactions are durable across application crashes regardless of the synchronous setting
|
|
or journal mode. The synchronous=NORMAL setting is a good choice for most applications
|
|
running in WAL mode.
|
|
Choices are: FULL, NORMAL, OFF. -->
|
|
<string name="db_wal_sync_mode" translatable="false">OFF</string>
|
|
|
|
<!-- Whether device has physical tri state switch -->
|
|
<bool name="config_hasAlertSlider">true</bool>
|
|
|
|
<!-- The location of the devices physical tri state switch
|
|
0: Left side
|
|
1: Right side -->
|
|
<integer name="config_alertSliderLocation">1</integer>
|
|
|
|
<!-- Whether doze feature is enabled by default in settings -->
|
|
<bool name="config_doze_enabled_by_default">true</bool>
|
|
|
|
<!-- Power Management: Specifies whether to decouple the auto-suspend state of the
|
|
device from the display on/off state.
|
|
When false, autosuspend_disable() will be called before the display is turned on
|
|
and autosuspend_enable() will be called after the display is turned off.
|
|
This mode provides best compatibility for devices using legacy power management
|
|
features such as early suspend / late resume.
|
|
When true, autosuspend_display() and autosuspend_enable() will be called
|
|
independently of whether the display is being turned on or off. This mode
|
|
enables the power manager to suspend the application processor while the
|
|
display is on.
|
|
This resource should be set to "true" when a doze component has been specified
|
|
to maximize power savings but not all devices support it.
|
|
Refer to autosuspend.h for details.
|
|
-->
|
|
<bool name="config_powerDecoupleAutoSuspendModeFromDisplay">true</bool>
|
|
|
|
<!-- Power Management: Specifies whether to decouple the interactive state of the
|
|
device from the display on/off state.
|
|
When false, setInteractive(..., true) will be called before the display is turned on
|
|
and setInteractive(..., false) will be called after the display is turned off.
|
|
This mode provides best compatibility for devices that expect the interactive
|
|
state to be tied to the display state.
|
|
When true, setInteractive(...) will be called independently of whether the display
|
|
is being turned on or off. This mode enables the power manager to reduce
|
|
clocks and disable the touch controller while the display is on.
|
|
This resource should be set to "true" when a doze component has been specified
|
|
to maximize power savings but not all devices support it.
|
|
Refer to power.h for details.
|
|
-->
|
|
<bool name="config_powerDecoupleInteractiveModeFromDisplay">true</bool>
|
|
|
|
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
|
|
<bool name="config_unplugTurnsOnScreen">true</bool>
|
|
|
|
<!-- Whether device supports sensor based doze customizations -->
|
|
<bool name="config_dozePulsePickup">true</bool>
|
|
<bool name="config_dozePulseTilt">true</bool>
|
|
<bool name="config_dozePulseProximity">true</bool>
|
|
<bool name="config_deviceHaveWakeUpProximity">true</bool>
|
|
|
|
<!-- The maximum range of gamma adjustment possible using the screen
|
|
auto-brightness adjustment setting. -->
|
|
<fraction name="config_autoBrightnessAdjustmentMaxGamma">150%</fraction>
|
|
|
|
<!-- Flag indicating whether notification and ringtone volumes
|
|
are controlled together (aliasing is true) or not. -->
|
|
<bool name="config_alias_ring_notif_stream_types">false</bool>
|
|
|
|
</resources>
|