FP4: Import full fwb overlay from LineageOS

This commit is contained in:
Peter Cai 2022-11-09 18:28:38 -05:00
parent f0663e63d1
commit 2ac6e4f778
2 changed files with 530 additions and 0 deletions

View File

@ -0,0 +1,333 @@
<?xml version="1.0" encoding="utf-8"?>
<!--Copyright (c) 2012-2016, The Linux Foundation. All rights reserved
Not a Contribution.
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.
-->
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<!-- Set to true to add links to Cell Broadcast app from Settings and MMS app. -->
<bool name="config_cellBroadcastAppLinks">true</bool>
<!-- 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. -->
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,1,-1,true"</item>
<item>"mobile,0,0,0,-1,true"</item>
<item>"mobile_mms,2,0,4,60000,true"</item>
<item>"mobile_supl,3,0,2,60000,true"</item>
<item>"mobile_dun,4,0,2,60000,true"</item>
<item>"mobile_hipri,5,0,3,60000,true"</item>
<item>"mobile_fota,10,0,2,60000,true"</item>
<item>"mobile_ims,11,0,2,60000,true"</item>
<item>"mobile_cbs,12,0,2,60000,true"</item>
<item>"bluetooth,7,7,2,-1,true"</item>
<item>"mobile_emergency,15,0,5,-1,true"</item>
<item>"ethernet,9,9,9,-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>
<item>"7,1"</item>
</string-array>
<!-- Boolean indicating if current platform supports BLE peripheral mode -->
<bool name="config_bluetooth_le_peripheral_mode_supported">true</bool>
<!-- If this is true, the screen will come on when you plug/unplug usb/power/whatever. -->
<bool name="config_unplugTurnsOnScreen">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>
<!-- Is the device capable of hot swapping an UICC Card -->
<bool name="config_hotswapCapable">true</bool>
<!-- Flag indicating whether the we should enable the automatic brightness in Settings.
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:
(1-based arrays)
Point 1: (0, value[1]): lux <= 0
Point 2: (level[1], value[2]): 0 < lux <= level[1]
Point 3: (level[2], value[3]): level[2] < lux <= level[3]
...
Point N+1: (level[N], value[N+1]): level[N] < lux
The control points must be strictly increasing. Each control point
corresponds to an entry in the brightness backlight values arrays.
For example, if lux == level[1] (first element of the levels array)
then the brightness will be determined by value[2] (second element
of the brightness values array).
Spline interpolation is used to determine the auto-brightness
backlight values for lux levels between these control points.
Must be overridden in platform specific overlays -->
<integer-array name="config_autoBrightnessLevels">
<item>1</item>
<item>10</item>
<item>50</item>
<item>100</item>
<item>500</item>
<item>1000</item>
<item>3000</item>
</integer-array>
<!-- Stability requirements in milliseconds for accepting a new brightness level. This is used
for debouncing the light sensor. Different constants are used to debounce the light sensor
when adapting to brighter or darker environments. This parameter controls how quickly
brightness changes occur in response to an observed change in light level that exceeds the
hysteresis threshold. -->
<integer name="config_autoBrightnessBrighteningLightDebounce">1000</integer>
<integer name="config_autoBrightnessDarkeningLightDebounce">1000</integer>
<!-- Minimum screen brightness setting allowed by the power manager.
The user is forbidden from setting the brightness below this level. -->
<integer name="config_screenBrightnessSettingMinimum">3</integer>
<!-- Screen brightness used to dim the screen when the user activity
timeout expires. May be less than the minimum allowed brightness setting
that can be set by the user. -->
<integer name="config_screenBrightnessDim">3</integer>
<!-- Minimum allowable screen brightness to use in a very dark room.
This value sets the floor for the darkest possible auto-brightness
adjustment. It is expected to be somewhat less than the first entry in
config_autoBrightnessLcdBacklightValues so as to allow the user to have
some range of adjustment to dim the screen further than usual in very
dark rooms. The contents of the screen must still be clearly visible
in darkness (although they may not be visible in a bright room). -->
<integer name="config_screenBrightnessDark">3</integer>
<!-- Array of output values for LCD backlight corresponding to the LUX values
in the config_autoBrightnessLevels array. This array should have size one greater
than the size of the config_autoBrightnessLevels array.
The brightness values must be between 0 and 255 and be non-decreasing.
This must be overridden in platform specific overlays -->
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>10</item>
<item>20</item>
<item>40</item>
<item>70</item>
<item>110</item>
<item>160</item>
<item>200</item>
<item>255</item>
</integer-array>
<!-- MMS user agent string -->
<string name="config_mms_user_agent" translatable="false">Android-Mms/2.0</string>
<!-- MMS user agent prolfile url -->
<string name="config_mms_user_agent_profile_url" translatable="false">https://techsupport.fairphone.com/uap/fp4_UAP.xml</string>
<!-- 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>
<!-- 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>
<!-- Flag specifying whether WFC over IMS is available on device -->
<bool name="config_device_wfc_ims_available">true</bool>
<!-- Flag specifying whether VoLTE & VT 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>
<!-- 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>"5gnr: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>"hspap: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:4094,87380,524288,4096,16384,262144"</item>
</string-array>
<!-- 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>
<!-- Whether the Unprocessed audio source supports the required frequency range and level -->
<bool name="config_supportAudioSourceUnprocessed">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>
<!-- Boolean indicating if current platform supports HFP inband ringing -->
<bool name="config_bluetooth_hfp_inband_ringing_support">true</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()
to put the display into a low power state and allow the application processor
to be suspended. When the dream ends, the system will go to sleep as usual.
Specify the component name or an empty string if none.
Note that doze dreams are not subject to the same start conditions as ordinary dreams.
Doze dreams will run whenever the power manager is in a dozing state. -->
<string name="config_dozeComponent">com.android.systemui/com.android.systemui.doze.DozeService</string>
<!-- If true, the doze component is not started until after the screen has been
turned off and the screen off animation has been performed. -->
<bool name="config_dozeAfterScreenOff">true</bool>
<!-- Screen brightness used to dim the screen while dozing in a very low power state.
May be less than the minimum allowed brightness setting
that can be set by the user. -->
<integer name="config_screenBrightnessDoze">17</integer>
<!-- Boolean indicating whether the HWC setColorTransform function can be performed efficiently
in hardware. -->
<bool name="config_setColorTransformAccelerated">true</bool>
<!-- An array of arrays of side fingerprint sensor properties relative to each display.
Note: this value is temporary and is expected to be queried directly
from the HAL in the future. -->
<array name="config_sfps_sensor_props" translatable="false">
<item>@array/config_sfps_sensor_props_0</item>
</array>
<array name="config_sfps_sensor_props_0" translatable="false">
<item>local:4630947175487691137</item> <!--item>displayId</item-->
<item>1080</item> <!--item>sensorLocationX</item-->
<item>940</item> <!--item>sensorLocationY</item-->
<item>200</item> <!--item>sensorRadius</item-->
</array>
<!-- Indicates whether device has a power button fingerprint sensor. -->
<bool name="config_is_powerbutton_fps" translatable="false">true</bool>
<!-- 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> <!-- ID0:Fingerprint:Strong -->
</string-array>
<!-- An array of device capabilities defined by GSMA SGP.22 v2.0.
The first item is the capability name that the device supports. The second item is the
major version. The minor and revision versions are default to 0s.
The device capabilities and their definition in the spec are:
gsm : gsmSupportedRelease
utran : utranSupportedRelease
cdma1x : cdma2000onexSupportedRelease
hrpd : cdma2000hrpdSupportedRelease
ehrpd : cdma2000ehrpdSupportedRelease
eutran : eutranSupportedRelease
nfc : contactlessSupportedRelease
crl : rspCrlSupportedVersion
-->
<array name="config_telephonyEuiccDeviceCapabilities">
<item>gsm,9</item>
<item>utran,10</item>
<item>eutran,15</item>
</array>
<!-- Average Current for bluetooth controller when idle. 0 by default-->
<integer translatable="false" name="config_bluetooth_idle_cur_ma">3</integer>
<!-- Average Current for bluetooth controller when receiving. 0 by default-->
<integer translatable="false" name="config_bluetooth_rx_cur_ma">20</integer>
<!-- Average Current for bluetooth controller when transmitting. 0 by default-->
<integer translatable="false" name="config_bluetooth_tx_cur_ma">33</integer>
<!-- Operating volatage for bluetooth controller. 0 by default-->
<integer translatable="false" name="config_bluetooth_operating_voltage_mv">3700</integer>
<!-- set to false if we need to show user confirmation
when alpha identifier is not provided by the UICC -->
<bool name="config_stkNoAlphaUsrCnf">false</bool>
<!-- The bounding path of the cutout region of the main built-in display.
Must either be empty if there is no cutout region, or a string that is parsable by
{@link android.util.PathParser}.
The path is assumed to be specified in display coordinates with pixel units and in
the display's native orientation, with the origin of the coordinate system at the
center top of the display. Optionally, you can append either `@left` or `@right` to the
end of the path string, in order to change the path origin to either the top left,
or top right of the display.
To facilitate writing device-independent emulation overlays, the marker `@dp` can be
appended after the path string to interpret coordinates in dp instead of px units.
Note that a physical cutout should be configured in pixels for the best results.
Example for a 10px x 10px square top-center cutout:
<string ...>M -5,0 L -5,10 L 5,10 L 5,0 Z</string>
Example for a 10dp x 10dp square top-center cutout:
<string ...>M -5,0 L -5,10 L 5,10 L 5,0 Z @dp</string>
@see https://www.w3.org/TR/SVG/paths.html#PathData
-->
<string name="config_mainBuiltInDisplayCutout">M -145 0 L -145 82 L 145 82 L 145 0 Z</string>
<!-- Whether the display cutout region of the main built-in display should be forced to
black in software (to avoid aliasing or emulate a cutout that is not physically existent).
-->
<bool name="config_fillMainBuiltInDisplayCutout">false</bool>
<!-- Vibrator pattern for feedback about a long screen/key press -->
<integer-array name="config_longPressVibePattern">
<item>0</item>
<item>15</item>
</integer-array>
<!-- Vibrator pattern for feedback about touching a virtual key -->
<integer-array name="config_virtualKeyVibePattern">
<item>0</item>
<item>15</item>
</integer-array>
<!-- Vibrator pattern for a very short but reliable vibration for soft keyboard tap -->
<integer-array name="config_keyboardTapVibePattern">
<item>0</item>
<item>15</item>
</integer-array>
<!-- Vibrator pattern for feedback about booting with safe mode enabled -->
<integer-array name="config_safeModeEnabledVibePattern">
<item>0</item>
<item>0</item>
<item>94</item>
</integer-array>
<!-- Vibrator pattern for feedback about hitting a scroll barrier -->
<integer-array name="config_scrollBarrierVibePattern">
<item>0</item>
<item>15</item>
<item>30</item>
<item>15</item>
</integer-array>
</resources>

View File

@ -0,0 +1,197 @@
<?xml version="1.0" encoding="utf-8"?>
<device name="Android">
<item name="none">0
</item>
<item name="screen.on">108
</item>
<item name="screen.full">430
</item>
<array name="cpu.clusters.cores">
<value>6
</value>
<value>2
</value>
</array>
<array name="cpu.core_speeds.cluster0">
<value>614400
</value>
<value>864000
</value>
<value>1075200
</value>
<value>1363200
</value>
<value>1516800
</value>
<value>1651200
</value>
<value>1804800
</value>
</array>
<array name="cpu.core_power.cluster0">
<value>8
</value>
<value>13
</value>
<value>17
</value>
<value>22
</value>
<value>28
</value>
<value>33
</value>
<value>37
</value>
</array>
<array name="cpu.core_speeds.cluster1">
<value>652800
</value>
<value>806400
</value>
<value>940800
</value>
<value>1094400
</value>
<value>1152000
</value>
<value>1401600
</value>
<value>1478400
</value>
<value>1728000
</value>
<value>1766400
</value>
<value>1900800
</value>
<value>1996800
</value>
<value>2092800
</value>
<value>2188800
</value>
<value>2208000
</value>
<value>2342400
</value>
<value>2400000
</value>
<value>2611200
</value>
<value>2707200
</value>
</array>
<array name="cpu.core_power.cluster1">
<value>18
</value>
<value>32
</value>
<value>33
</value>
<value>48
</value>
<value>48
</value>
<value>76
</value>
<value>78
</value>
<value>110
</value>
<value>120
</value>
<value>153
</value>
<value>169
</value>
<value>189
</value>
<value>219
</value>
<value>210
</value>
<value>254
</value>
<value>265
</value>
<value>335
</value>
<value>369
</value>
</array>
<item name="cpu.active">8.5
</item>
<item name="cpu.idle">0.1
</item>
<item name="cpu.suspend">0
</item>
<item name="battery.capacity">3300
</item>
<item name="wifi.on">0.1
</item>
<item name="wifi.active">156
</item>
<item name="wifi.scan">1
</item>
<item name="dsp.audio">26
</item>
<item name="dsp.video">66
</item>
<item name="camera.flashlight">620
</item>
<item name="camera.avg">410
</item>
<item name="gps.on">5
</item>
<item name="radio.active">171
</item>
<item name="radio.scanning">6
</item>
<array name="radio.on">
<value>88
</value>
<value>8
</value>
</array>
<item name="modem.controller.idle">6
</item>
<item name="modem.controller.rx">221
</item>
<item name="modem.controller.tx">203
</item>
<item name="modem.controller.voltage">3700
</item>
<array name="memory.bandwidths">
<value>16.5
</value>
</array>
<item name="wifi.controller.idle">1
</item>
<item name="wifi.controller.rx">127
</item>
<item name="wifi.controller.tx">168
</item>
<array name="wifi.controller.tx_levels">1
</array>
<item name="wifi.controller.voltage">3700
</item>
<array name="wifi.batchedscan">
<value>.0001
</value>
<value>.001
</value>
<value>.01
</value>
<value>.1
</value>
<value>1
</value>
</array>
<item name="bluetooth.active">93
</item>
<item name="bluetooth.on">0.65
</item>
<item name="bluetooth.controller.voltage">700
</item>
</device>