xiaomi-sm8450/android_device_xiaomi_sm8450-common
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sm8450-common: overlay: Update Frameworks overlay from LA.VENDOR.1.0.r1-15600-WAIPIO.0

Browse Source 
Change-Id: I7a13a9139477c45228966d845087902f503e3fd2
This commit is contained in:
Arian
2024-01-25 16:57:57 +01:00
parent e97facd2db
commit b3cc9df3a3
3 changed files with 53 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
overlay/FrameworksResCommon_Sys/res/values/bools.xml
View File

@@ -4,6 +4,8 @@
SPDX-License-Identifier: Apache-2.0
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<bool name="config_bluetooth_hfp_inband_ringing_support">true</bool>
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
<bool name="config_dozeAfterScreenOff">true</bool>
<bool name="config_wifi_background_scan_support">true</bool>
<bool name="config_wifi_batched_scan_supported">true</bool>

17
overlay/FrameworksResCommon_Sys/res/values/config.xml
View File

@@ -4,9 +4,6 @@
SPDX-License-Identifier: Apache-2.0
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<bool name="config_bluetooth_hfp_inband_ringing_support">true</bool>
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
<!-- NOTE: The telephony module is no longer reading the configuration below for available
APN types. The set of APN types and relevant settings are specified within the telephony
module and are non-configurable. Whether or not data connectivity over a cellular network
@@ -290,6 +287,14 @@
phone object irrespective of this config -->
<bool name="config_switch_phone_on_voice_reg_state_change">false</bool>
<!--The default "usage setting" indicating that the device is either a voice-centric
device (1) or a data-centric device (2). A voice-centric device will require that any cellular
service that it uses provides access to voice capability, and a data-centric device will
likewise require that the network provides access to data services. These settings are
sent to the cellular modem and control the behavior in accordance with 3gpp TS 24.301 sec 4.3
(and equivalent functionality in other generations of cellular).-->
<integer name="config_default_cellular_usage_setting">-1</integer>
<!-- Whether the Unprocessed audio source supports the required frequency range and level -->
<bool name="config_supportAudioSourceUnprocessed">true</bool>
@@ -309,6 +314,12 @@
non-zero. -->
<integer name="config_defaultPeakRefreshRate">240</integer>
<!-- 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>
<!-- Whether to select voice/data/sms preference without user confirmation -->
<bool name="config_voice_data_sms_auto_fallback">true</bool>
</resources>

37
overlay/FrameworksResCommon_Sys/res/values/config_telephony.xml
View File

@@ -4,6 +4,36 @@
SPDX-License-Identifier: Apache-2.0
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<!-- Configure tcp buffer sizes per network type in the form:
network-type:rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max
The network-type must be a valid DataConfigNetworkType value. If no value is found for the
network-type in use, config_tcp_buffers will be used instead.
-->
<string-array name="config_network_type_tcp_buffers">
<item>NR_SA_MMWAVE:2097152,6291456,16777216,512000,2097152,8388608</item>
<item>NR_SA:2097152,6291456,16777216,512000,2097152,8388608</item>
<item>NR_NSA_MMWAVE:2097152,6291456,16777216,512000,2097152,8388608</item>
<item>NR_NSA:2097152,6291456,16777216,512000,2097152,8388608</item>
<item>LTE:2097152,4194304,8388608,262144,524288,1048576</item>
<item>LTE_CA:4096,6291456,12582912,4096,1048576,2097152</item>
<item>UMTS:4094,87380,1220608,4096,16384,1220608</item>
<item>HSPA:4094,87380,1220608,4096,16384,1220608</item>
<item>HSUPA:4094,87380,1220608,4096,16384,1220608</item>
<item>HSDPA:4094,87380,1220608,4096,16384,1220608</item>
<item>HSPA+:4094,87380,1220608,4096,16384,1220608</item>
<item>EDGE:4093,26280,35040,4096,16384,35040</item>
<item>GPRS:4092,8760,11680,4096,8760,11680</item>
<item>EvDo_0:4094,87380,524288,4096,16384,262144</item>
<item>EvDo_A:4094,87380,524288,4096,16384,262144</item>
<item>EvDo_B:4094,87380,524288,4096,16384,262144</item>
</string-array>
<!-- Whether to adopt the predefined handover policies for IWLAN.
{@see CarrierConfigManager#KEY_IWLAN_HANDOVER_POLICY_STRING_ARRAY}
-->
<bool name="config_enable_iwlan_handover_policy">false</bool>
<!-- 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>
@@ -14,4 +44,11 @@
<!-- Telephony qualified networks service package name to bind to by default. -->
<string name="config_qualified_networks_service_package" translatable="false">vendor.qti.iwlan</string>
<!-- Whether enhanced IWLAN handover check is enabled. If enabled, telephony frameworks
will not perform handover if the target transport is out of service, or VoPS not
supported. The network will be torn down on the source transport, and will be
re-established on the target transport when condition is allowed for bringing up a
new network. -->
<bool name="config_enhanced_iwlan_handover_check">false</bool>
</resources>