* move to as many components as we reasonably can
* drop all duplicate configs and properties
* add missing oneplus usb additions
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
* use standard sensor type
* ignore non-wakeup sensor variant
* ignore events that do not properly match a pickup
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
* AOSP already mounts TraceFS in system init, so mounting it twice
causes SEPolicy denials. See the comments in this change.
https://android-review.googlesource.com/c/platform/system/sepolicy/+/1294195
Change-Id: Ic5d9ac2dbd36e404a93a8d48aa0ea933fd7fa701
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
We are going to enforce that each property has an explicit owner, such
as system, vendor, or product. This attaches vendor_property_type to
properties defined under vendor sepolicy directories.
Change-Id: Iedbbcc5086c09f549e91e73ece7311563c378347
* ELF prebuilts were banned in PRODUCT_COPY_FILES starting
May 11th. See b/156534160 for long-term fix which should
override this change.
Change-Id: Icd25b40ca4e4285319775046a1b70de30572be07
We are restoring the old behavior of BOARD_PLAT_*_SEPOLICY_DIR that
extends system sepolicy. To that end, we use another make variable to
specify product sepolicy.
Bug: 119305624
Test: m selinux_policy
Change-Id: I67636b7aaff2bd5ae5309981f9fa2f8ce51edf6f
* Fixes retry/close buttons not working on error
open/close camera alert.
Change-Id: I3fccb76e038e7da7a7e39a8df371c7ee48f54ed3
Signed-off-by: DarkJoker360 <simoespo159@gmail.com>
libgf_ud_hal.so looks for vendor.boot.verifiedbootstate to be set to the phones true state
in our case, for an unlocked phone, it must be orange
(green = locked with factory rom, orange = unlocked no checking, yellow = locked with user key)
Change it to look for vendor.boot.fingerprintbstate which we set to orange without having to mess with anything safetynet related.
Add a device check since only 7T Series actually checks for it
Co-authored-by: Matt Filetto <matt.filetto@gmail.com>
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
Change-Id: I35dec00b50c2f45334127ff251d5475100a6f3f2
There are several VMTs inside that library that are prone to change
on CAF merges.
So far, last LA.QSSI.11.0.r1-12300-qssi.0 merge already modified
ConfigInterface VMT in a way that's not backwards compatible thus
it'd be better if we provided a prebuilt library instead.
Change-Id: I25fe58e6721b8d0e67882f576cfaf288c9992fc9
Added below two changes to enable the AAC frame control
when property persist.vendor.bt.a2dp.hal.implementation
has nbeen enabled.
- Send bitrate value to MM on basis of MTU and sample rate.
CRs-Fixed: 2402346
Change-Id: I6c964311dfa5db335d3b9dd21c60d1f9dcc61ebe
- A2dpSrc: Calculate bitrate with exact peer MTU value.
CRs-Fixed: 2466969
Change-Id: I95e93cb29d1add0b2bca8f99827849519311a0b1
CRs-Fixed: 2474400
Change-Id: I8eea975fac290c117d9781c1455e81e9404f6bd6
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
- Enable/Disable TWS plus feature support using persist
property - "persist.vendor.btstack.enable.twsplus"
- TWS plus feature is supported only if property is set to
"True" else feature is not supported.By default property
is set to False.
CRs-Fixed: 2344895
Change-Id: I855f448146424b7b647ca599f3d830073ec7c409
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
High power consumption issues were reported for some HS/CK/Speaker
in close range(1 meter) on hastings platform as they may not have
perfect RSSI golden range logic for power control and always request
SOC to increase TX power to max power level. Newer hastings SOC support
LPA power control to avoid unnecessary higher power consumption.
The change enable this soc feature according to value of property.
And disable it for special remote devices which have been added in BL
when new ACL link is created.
If feature is enabled, controllable power level for remote is L0-L9,
BT controller increase it to L10 or L11 according to RSSI and NAK rate.
Otherwise controllable power level for remote is from 0 to max power
level signified in NVM, most likely L11 for hastings.
CRs-Fixed: 2597191
Change-Id: I354bb34a84aa7a55537e3a595daac54c46d90603
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>