It turns out berlna still needs this to initialize FP sensor
even though in the real world only one is used, so we might
as well leave this in common for berlna and xpeng
Change-Id: I094d12dc7581099c611dc1ffedf63d065af04081
From TUNDRA_RETAIL_12_S3SJS32.1-86-1-4_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC
dubai blobs aren't on a new enough CLO tag to be compatible with the display
stack CLO tag LA.UM.9.14.r1-20000.01-LAHAINA.QSSI13.0
https://review.lineageos.org/c/LineageOS/android_hardware_qcom_display/+/349384
Change-Id: If276861699519604d74ef083f122bec792ea831c
This was introduced with [1] and allows to choose target specific media
profiles without caf changes to frameworks/av. Unset media.settings.xml
so that the new property gets respected and drop copying the lahaina
config as media_profiles_vendor since we don't need a fallback anymore.
[1]: eaac82f33f#
Change-Id: I7ec306bf3dd595c09308ed26c9d3a6db8490c7f0
Drop unsupported platforms, simplify target_variant setup and drop qssi
and build codename checks.
Change-Id: I392c09587bfbf15c0bd3af84cc12d1bdb8e269d6
* ximi sm8350-common does this, and it works, so why not.
* Also cleanup some unused entries like wlan_mac and
WCNSS_mot_cfg
Change-Id: Ifaf77ece24c229fce55f93079236a03282d5a891
Signed-off-by: electimon <electimon@gmail.com>
* HAB properties are appended by the bootloader,
as well as console. RTB filter is a debug property.
Change-Id: If5347a00492c6782f17355b5221c033987475b09
Signed-off-by: electimon <electimon@gmail.com>
* CAF only does this because they use one device tree
for all 3 SoCs, vendor/qcom/lahaina. We use one -common
tree with device trees inheriting it. There is no need
to have manifest_yupik.xml.
Change-Id: I133f19725d523ce2e4acb17114b687f9e5757019
Signed-off-by: electimon <electimon@gmail.com>
This reverts commit bdbd9a4df48998b12acc836a802e5b744f00ec29.
Reason: Xiaomi Mi 11 Lite 5G NE (lisa) got A13 stock ROM so we can just
flash their bluetooth firmware partition onto ours and fix the issue
right at the source and drop the fix we have in our device tree.
Change-Id: I21f4918f8d0fc794db29b4aa2235c238c36a800e
* appears to be a typo in the tag and while we are at it define VENDOR_SECURITY_PATCH
Signed-off-by: Andrew Hexen <SyberHexen@gmail.com>
Change-Id: I36ebf0895eb87dffa9254cd87d420e25d43b11c0
Also includes these commits:
ImsConfigImpl: Remove call to syncWfcMDN()
ImsConfigImpl: Return 0 in getWfcMDN in any case
ImsServiceStub: force disable auto reject mode
Change-Id: Ib850197933c33e29697d57b97037de678c40546b
This partially reverts commit 429d082485d206e551e09cf433abdcc1b47b116e.
Oddly, the Frameworks defaults values causes peak refresh rate to fail to
work for us... so let's just partially revert and set the default peak to
60 and then users can then chose their own peak refresh value if they want.
Change-Id: Ibf2e645e3508e28e3e7c092d05db0598adafcf44
In the berlin/dubai trees we have overriding values that use the same as
the default values, so let's just revert to that.
Change-Id: Ie79456b0cf4c319b84bca0153ba2bdd91a87960e
This reverts commit 7dffcc1c5846c1284337a37ac34b33c3b14d2fa4.
Reason: We don't need this on sm73250-common as we have A12 stock ROMs
Change-Id: I772856a78a70314f4390e19b5c68da706f0d76a6
This fixes the bluetooth module crashing due to firmware that should support
BT LE as yupik is BT 5.2 but instead it fails.
Change-Id: If744eff8ceb7f665b0304fb4a506efd23926bbe1
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
