|
|
|
|
@ -18,25 +18,81 @@ |
|
|
|
|
--> |
|
|
|
|
|
|
|
|
|
<resources> |
|
|
|
|
<bool name="config_automatic_brightness_available">true</bool> |
|
|
|
|
<bool name="config_supportsScreenOffUdfps">true</bool> |
|
|
|
|
<bool name="config_haveHigherAspectRatioScreen">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> |
|
|
|
|
<bool name="config_bluetooth_hfp_inband_ringing_support">true</bool> |
|
|
|
|
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool> |
|
|
|
|
<bool name="config_carrier_volte_available">false</bool> |
|
|
|
|
<bool name="config_device_volte_available">false</bool> |
|
|
|
|
|
|
|
|
|
<!-- Flag specifying whether VoLTE should be available for carrier: independent of |
|
|
|
|
carrier provisioning. If false: hard disabled. If true: then depends on carrier |
|
|
|
|
provisioning, availability etc --> |
|
|
|
|
<bool name="config_carrier_volte_available">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Flag specifying whether VoLTE is available on device --> |
|
|
|
|
<bool name="config_device_volte_available">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Flag specifying whether VT is available on device --> |
|
|
|
|
<bool name="config_device_vt_available">true</bool> |
|
|
|
|
<bool name="config_device_wfc_ims_available">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Flag specifying whether WFC over IMS is available on device --> |
|
|
|
|
<bool name="config_device_wfc_ims_available">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Whether UI for multi user should be shown --> |
|
|
|
|
<bool name="config_enableMultiUserUI">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Maximum number of supported users --> |
|
|
|
|
<integer name="config_multiuserMaximumUsers">4</integer> |
|
|
|
|
|
|
|
|
|
<!-- Is the device capable of hot swapping an UICC Card --> |
|
|
|
|
<bool name="config_hotswapCapable">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Flag indicating if the speed up audio on mt call code should be executed --> |
|
|
|
|
<bool name="config_speed_up_audio_on_mt_calls">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Config determines whether to update phone object when voice registration |
|
|
|
|
state changes. Voice radio tech change will always trigger an update of |
|
|
|
|
phone object irrespective of this config --> |
|
|
|
|
<bool name="config_switch_phone_on_voice_reg_state_change">false</bool> |
|
|
|
|
|
|
|
|
|
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. --> |
|
|
|
|
<bool name="config_unplugTurnsOnScreen">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Set to true if the wifi display supports compositing content stored |
|
|
|
|
in gralloc protected buffers. For this to be true, there must exist |
|
|
|
|
a protected hardware path for surface flinger to composite and send |
|
|
|
|
protected buffers to the wifi display video encoder. |
|
|
|
|
|
|
|
|
|
If this flag is false, we advise applications not to use protected |
|
|
|
|
buffers (if possible) when presenting content to a wifi display because |
|
|
|
|
the content may be blanked. |
|
|
|
|
|
|
|
|
|
This flag controls whether the {@link Display#FLAG_SUPPORTS_PROTECTED_BUFFERS} |
|
|
|
|
flag is set for wifi displays. |
|
|
|
|
--> |
|
|
|
|
<bool name="config_wifiDisplaySupportsProtectedBuffers">true</bool> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!-- Whether WiFi display is supported by this device. |
|
|
|
|
There are many prerequisites for this feature to work correctly. |
|
|
|
|
Here are a few of them: |
|
|
|
|
* The WiFi radio must support WiFi P2P. |
|
|
|
|
* The WiFi radio must support concurrent connections to the WiFi display and |
|
|
|
|
to an access point. |
|
|
|
|
* The Audio Flinger audio_policy.conf file must specify a rule for the "r_submix" |
|
|
|
|
remote submix module. This module is used to record and stream system |
|
|
|
|
audio output to the WiFi display encoder in the media server. |
|
|
|
|
* The remote submix module "audio.r_submix.default" must be installed on the device. |
|
|
|
|
* The device must be provisioned with HDCP keys (for protected content). |
|
|
|
|
--> |
|
|
|
|
<bool name="config_enableWifiDisplay">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Boolean indicating if restoring network selection should be skipped --> |
|
|
|
|
<!-- The restoring is handled by modem if it is true--> |
|
|
|
|
<bool translatable="false" name="skip_restoring_network_selection">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Configure mobile tcp buffer sizes in the form: |
|
|
|
|
rat-name:rmem_min,rmem_def,rmem_max,wmem_min,wmem_def,wmem_max |
|
|
|
|
If no value is found for the rat-name in use, the system default will be applied. |
|
|
|
|
--> |
|
|
|
|
<string-array name="config_mobile_tcp_buffers"> |
|
|
|
|
<item>lte:2097152,4194304,8388608,524288,1572864,2097152</item> |
|
|
|
|
<item>lte_ca:2097152,4194304,8388608,4096,1048576,2097152</item> |
|
|
|
|
@ -49,6 +105,20 @@ |
|
|
|
|
<item>gprs:4092,8760,11680,4096,8760,11680</item> |
|
|
|
|
<item>evdo:4094,87380,524288,4096,16384,262144</item> |
|
|
|
|
</string-array> |
|
|
|
|
|
|
|
|
|
<!-- This string array should be overridden by the device to present a list of network |
|
|
|
|
attributes. This is used by the connectivity manager to decide which networks can coexist |
|
|
|
|
based on the hardware --> |
|
|
|
|
<!-- An Array of "[Connection name],[ConnectivityManager.TYPE_xxxx], |
|
|
|
|
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] --> |
|
|
|
|
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay |
|
|
|
|
before automatically restore the default connection. Set -1 if the connection |
|
|
|
|
does not require auto-restore. --> |
|
|
|
|
<!-- the 6th element indicates boot-time dependency-met value. --> |
|
|
|
|
<!-- 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 |
|
|
|
|
is available at all is controlled by the flag: config_moble_data_capable. --> |
|
|
|
|
<string-array translatable="false" name="networkAttributes"> |
|
|
|
|
<item>wifi,1,1,1,-1,true</item> |
|
|
|
|
<item>mobile,0,0,0,-1,true</item> |
|
|
|
|
@ -72,6 +142,12 @@ |
|
|
|
|
<item>mobile_foc,30,0,2,-1,true</item> |
|
|
|
|
<item>mobile_rcs,31,0,2,-1,true</item> |
|
|
|
|
</string-array> |
|
|
|
|
|
|
|
|
|
<!-- This string array should be overridden by the device to present a list of radio |
|
|
|
|
attributes. This is used by the connectivity manager to decide which networks can coexist |
|
|
|
|
based on the hardware --> |
|
|
|
|
<!-- An Array of "[ConnectivityManager connectionType], |
|
|
|
|
[# simultaneous connection types]" --> |
|
|
|
|
<string-array translatable="false" name="radioAttributes"> |
|
|
|
|
<item>1,1</item> |
|
|
|
|
<item>0,1</item> |
|
|
|
|
@ -80,6 +156,10 @@ |
|
|
|
|
|
|
|
|
|
<!-- Whether the new Auto Selection Network UI should be shown --> |
|
|
|
|
<bool name="config_enableNewAutoSelectNetworkUI">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Flag indicating whether we should enable the automatic brightness. |
|
|
|
|
Software implementation will be used if config_hardware_auto_brightness_available is not set --> |
|
|
|
|
<bool name="config_automatic_brightness_available">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Array of light sensor lux values to define our levels for auto backlight brightness support. |
|
|
|
|
The N entries of this array define N + 1 control points as follows: |
|
|
|
|
@ -1196,9 +1276,6 @@ |
|
|
|
|
DOZE_SUSPEND states. --> |
|
|
|
|
<bool name="config_dozeAlwaysOnDisplayAvailable">true</bool> |
|
|
|
|
|
|
|
|
|
<!-- Whether the display blanks itself when transition from a doze to a non-doze state --> |
|
|
|
|
<bool name="config_displayBlanksAfterDoze">false</bool> |
|
|
|
|
|
|
|
|
|
<!-- ComponentName of a dream to show whenever the system would otherwise have |
|
|
|
|
gone to sleep. When the PowerManager is asked to go to sleep, it will instead |
|
|
|
|
try to start this dream if possible. The dream should typically call startDozing() |
|
|
|
|
|
Ruchit
10 months ago
committed by