Qualcomm has added another WFC preference setting `IMS Preferred`
which is not supported in AOSP. If we let carriers default to this
setting, the AOSP settings app shows that WFC is disabled and
`Unexpected WFC mode value: 10` is logged. Even though the default
mode is still working fine, the user is unable to change to this
mode again once a different mode was selected. To fix this, remove
all default WFC mode settings with value "10" and let these carriers
default to "2" (`WiFi Preferred`, the default in AOSP) instead.
Leave the `carrier_wfc_supports_ims_preferred_bool` configs in place,
such that, in case the following patches are present in the system,
the user is still able to select the `IMS Preferred` mode in settings
manually.
097dacd55ba451b1fd23a79d737742d8ff55888f#
a2beaccd8f
Additionally, enable the WFC mode settings for the affected carriers
which didn't enable them before such that the user can still prefer
cellular calls over vowifi without disabling vowifi completely.
Change-Id: Ie6b9f30da45450c43a465de1170ef11d1d4ba1ee
The framework was changed in Android R to require explicit authenticator registration.
This change allows apps to continue to use the fingerprint sensor.
Bug: 147445115
Test: Builds
Change-Id: Id3385edc784b2053c8b54ec3153728f4e6e22a45
In Android 14, prioritization of partitions is emphasized, diverging
from previous versions where priorities were respected universally.
Overlay precedence now plays a critical role, with the following
partition order dictating overlay precedence:
- system
- vendor
- odm
- oem
- product
- system_ext
When multiple overlays contend for the same resources, the order of
overlays becomes crucial. An overlay takes precedence over others if it
has configurations following its own. This prioritization, while
impactful for GSI compatibility, is essential for maintaining order and
functionality.
Change-Id: I8b7568dcc418dbbd1ccb39e2d0dc66504f19fcdd
zone1 condition(10 nits) in 120Hz
zone2 condition(15 nits, 5 Lux) in 120Hz
Bug: 243757430
Bug: 246905529
Test: Check the refresh rata at zone
Change-Id: Iee9bd842571165785c03ae761780371798fbb758
Signed-off-by: Arian <arian.kulmer@web.de>
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: I8de2a2935901cbd3eaa50ce2d8aa09f61080ba02
Merged-In: Ie633ea788dab3389a3407ec9a461b5837befca46
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
ag/16564596 will change default value to false.
Configure correct overlay configuration.
Bug: 212488775
Test: manual test & build
Change-Id: Iaf1a0a23dae69fde5995e591a757a8ef5374d5b5
Without decoupling, PowerManagerService prevents system from going to
suspend when display is in AOD.
Bug: 123205093
Change-Id: Icb53a748c40bd7ae3dc8d87316d15a47e551d653
