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>
* drop in-tree bootctrl and dependencies
* drop unused flags
* use usb component
* update HIDL manifests for CAF
* blob perf deps
* drop non-existent overlays and general cleanup
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
Change-Id: I7babead03416479ad6928d359b1cb68def0565cc
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
* fixes [ 2.094340] init: Do not have permissions to set 'persist.vendor.camera.privapp.list' to 'com.oneplus.camera' in property file '/vendor/build.prop'
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
Matches stock Qualcomm configuration and improves performance.
OnePlus disables this because of their framework features, which
we do not have.
Change-Id: I75a1efb3f1963041ed4a810bffad539d81dac992
Signed-off-by: Park Ju Hyung <qkrwngud825@gmail.com>
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
* fixes 'telephony.lteOnCdmaDevice' to '1,1' in property file '/system/build.prop': Property type check failed, value doesn't match expected type 'int'
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
This prop is set on stock and helps fix crash when launching app:
https://del.dog/urrimeseha.txt
Change-Id: Idcb653e0dc6a7b38579586719d0f265ae84f6a8f
Signed-off-by: Anirudh Gupta <anirudhgupta109@aosip.dev>
* Needs corresponding frameworks commit.
* Imported all vendor interfaces to the device tree. This is dirty and
should be fixed from the frameworks side first, e.g. maybe load a .jar
library for FOD, but the code of that .jar library is only present in
device tree.
Omkar Chandorkar
Satheesh Kumar Pallemoni
M Safoorah Banu
xiaowang
timocapa
LuK1337
Jake Weinstein
Hikari-no-Tenshi
dianlujitao
Yifan Hong
Jesse Chan
Anirudh Gupta
Peter Cai