The folder structure added by I75165f3bf86f5f099298672977f6f5f5dc46c064
was confusing. In this commit, we are moving policies to
the common directory, which will only take effect on 855 and
newer. Then, as needed, we can backport to legacy.
Change-Id: Idc300d2a31b7851d37827e647a60a2b992ab256c
Skipping QAPE/QGPE for now. Those require learning modules from
taro, which would be a separate commit.
Change-Id: I246ff2ba848b00ea779b9b93ca0ece9b3b3a5172
Add Bluetooth HAL 1.1 service permission.
CRs-fixed: 3158165
Change-Id: I634599efbb0c20d222beab6b217c9193edc07b45
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
[1] - I forgot that now we have two different folders
Change-Id: I545984810d986aae20d0d4dddf24bbb0f882f543
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
- no reason why netflix support would just disappear with newer qssi
Signed-off-by: Omkar Chandorkar <gotenksIN@aospa.co>
Change-Id: I2c652781c1be4fcef1aaf87299f6a04d5091a1d5
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
[1] - We are sending taro definitions on the vendor.
Change-Id: I3017aaf35794506b160f42c5d2783c7160699d7f
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
[1] - Everything being used here is also cane enabled on SM8450 audio hal.
Change-Id: Iee0cb5cd7dd872f72b5b9ebe8244f9910146c990
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
For some reason, even when KERNEL_MODULES_OUT is set
it's using the no_modules script. Avoid this and set
the modules.ready prop directly if there are no modules.
This partially reverts commit 93382fa26a.
Change-Id: I237c6b31f335a71913d24a9c15f9c120ac24b1ba
Causes constant wakelocks with some networks that
don't support VoLTE, as the modem continuously tries
to register IMS.
CarrierConfig is enough to decide IMS functionality.
This reverts commit b634ff0b03.
Change-Id: I530e5d313de34c432b9819545abc0800fbbace87
Without this change, AndroidBoardCommon.mk
is inherited on all devices even if they
are non-QCOM.
This fixes the following errors:
[ 0% 768/138981] Creating /out/jake/target/product/oriole/vendor/bt_firmware
FAILED: /out/jake/target/product/oriole/vendor/bt_firmware
/bin/bash -c "(mkdir -p /out/jake/target/product/oriole/vendor/bt_firmware ) && (ln -sf /vendor/bt_firmware /out/jake/target/product/oriole/root/bt_firmware )"
ln: cannot create symbolic link from '/vendor/bt_firmware' to '/out/jake/target/product/oriole/root/bt_firmware': No such file or directory
[ 0% 769/138981] Creating /out/jake/target/product/oriole/vendor/dsp
FAILED: /out/jake/target/product/oriole/vendor/dsp
/bin/bash -c "(mkdir -p /out/jake/target/product/oriole/vendor/dsp ) && (ln -sf /vendor/dsp /out/jake/target/product/oriole/root/dsp )"
ln: cannot create symbolic link from '/vendor/dsp' to '/out/jake/target/product/oriole/root/dsp': No such file or directory
Change-Id: Id8938d36ae70c5bd3a4462bc875e390e8228cd62
This reverts commit c7dcf4fc86.
Reason for revert: Breaks existing targets with
error: kernel/msm-4.14/Android.bp:30:1: module "qti_kernel_headers" already defined
device/qcom/common/dlkm/Android.bp:1:1 <-- previous definition here
Change-Id: I857071fe582958c2ff1f68544e2acca2fc257084
* NXP NFC is becoming increasingly popular as an alternative
to NQ NFC, especially on the PN5xx platform. Add support
for disabling NQ NFC in favor of NXP NFC. Rename QTI
component to reflect this change.
Change-Id: I63dd29357943d6e5a31e479e98e6ff79df9b5124
The device under /dev/byte-cntr1 should be with permission
root diag.
Change-Id: Id5e45789995b706360742253fc93dc2304f70442
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
For now, this is for 5.10 only. 5.4 and others may upgrade
at some point. Until then, 5.4 uses media-5.4
and pre-5.4 uses media-legacy.
Change-Id: I7dccc184f81d5b1733852397c59d36ca0c3489ca
Blobs are updated to LA.VENDOR.1.0.r1-16000-WAIPIO.QSSI13.0
Configs are updated to to LA.VENDOR.1.0.r1-15600-WAIPIO.0
This does not work yet on pre-5.10 SoCs.
Those SoCs will use the perf-legacy
component until that is fixed (or indefinitely
depending on the complexity of the fix).
Note: I am aware that there are conditions in perf
that only apply to legacy and conditions in perf-legacy
that only apply to perf. We need to nail down the
supported targets before I can clean up completely.
Change-Id: I7925042da82fac6e5353c1a4b1660b3ca9e128d7
Currently, this only works on 5.4 and 5.10,
so pre-5.4 devices will stay on 5.4
binaries for the time being. This
renames components to the below:
adreno: 5.4/5.10 (LA.VENDOR.1.0.r1-16000-WAIPIO.QSSI13.0)
adreno-6xx-legacy: 4.9-4.19 (LA.UM.9.14.r1-20200-LAHAINA.QSSI13.0)
adreno-5xx: 3.18/4.4 (LA.UM.10.6.2.r1-01600-89xx.0)
Change-Id: I892e3b2e3c5c1d6d95d7c0ab4674075aa5546a3a
Maintainers should not need to manually select
the appropriate variant of a component for
their SoC. We know what does and does not
work for an SoC. Automatically select
the necessary component. This allows us
to be more flexible when new SoCs launch
and components may need to be renamed or
refactored.
Change-Id: Ibe9815ba7f70ec760c7b0cbd3771707af2e59854
Jyotiraditya Panda
Arian
Jake Weinstein
Adam Shih
Adithya R
Saikannan Chintakayala
chrisl7
Eruvaram Kumar Raja Reddy
Omkar Chandorkar
Abhay Singh Gill
Alexander Koskovich
Anay Wadhera
Robin Peng
Vishalcj17
Sarthak Garg
Yuanfang Zhang
Qi Jin
Vinoth Jayaram