- ELF prebuilts were banned in PRODUCT_COPY_FILES starting May 11.
- Adding BUILD_BROKEN_ELF_PREBUILT_PRODUCT_COPY_FILES := true to
BoardConfig.mk temoporarily.
- See b/156534160 for long-term fix which should override this change.
Test: Build
Bug: 156534160
Change-Id: I7d80798d3b2d3818bc835fcede21de2e7ab04735
* sRGB on Natural and Boosted
Unmanaged on Saturated
P3 on Automatic
* Set color mode to Natural by default
* Adjust display composition color spaces
Change-Id: If73eafa82395e80acf84445fcab2f1ce25a33e23
Signed-off-by: aswin7469 <aswinas@pixysos.com>
* ConNectivity SubSystem daemon from OnePlus Nord CE (ebba)
does not load bdwlan data for OnePlus Nord (avicii) properly
therefore, decommonize the daemon from the common inheritance.
Signed-off-by: Daniel Jacob Chittoor <djchittoor47@gmail.com>
These props are used by cnss-daemon in order to load
proper bdwlan firmware. Apparently these should be
set automatically via some QMI/RIL binary but I don't
really care enough to figure out as to how that works.
Change-Id: I06effa06321e9e00994ce7918c14bbc929d3d1cd
* Ultra low latency playback is currently broken. Crackling audio
can be well noticed while playing WhatsApp audio messages or even
during some games.
* This patch routes all audio that normally used audio-ull-playback
paths to low-latency-playback paths instead, thus meaning we're
switching from ULL to LL mode.
Change-Id: I7d672f1ff10b984c8096c9c4ca83475e730fd16f
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
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.
Co-authored-by: Matt Filetto <matt.filetto@gmail.com>
It allows users to switch between audio output devices by tapping the music
note icon on the notification of a music app
Change-Id: I71cdc10d21c53345666d372f71ade982c4a37277
OnePlus pocket sensor is broken on Android 11 custom ROMs.
Blinking dot can be seen on screen, but this is better than nothing.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Change-Id: Ie6e8c8d025316a9e482ff840c857b64ff58377e7
* This is only available on Nexus/Pixel devices. Already implemented
in LiveDisplay for devices that have the proper profile in the
QDCM calibration file or provide the commands via sysfs node.
Change-Id: I1dbeafdef930bcfeb2b950b3adce293307abff85
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>
There seems to be a race condition somewhere that prevents
it to be properly labelled, so move to genfs.
Change-Id: Ie2d1deeb19a871eb0b9f5120a92432fda658d725
The list of folders for genfscon was generated using following script:
for f in `adb shell "find /sys/devices -name wakeup -type d"`; do
adb shell "ls -Z '$f' | grep -qv u:object_r:sysfs:s0 || echo '$f'"
done
While list for regular file_contexts was just a simple grep "wakeup[0-9]".
Change-Id: I66abd501ce53b84e7268948d01d7b6c6c42cfbd1
