* These were moved to sysprops in Android 13 [1] and while
frameworks reads the values directly from power_profile.xml
Bluetooth app reads from the properties.
[1] 976d33062b%5E%21/#F0
Change-Id: I5bff67a15c537e8a47a19f30776fca6bf2c9fbe5
System properties set with the "=" operator cannot be overriden. This
device is used elsewhere in the system and some of the properties need
to be overridden. The "?=" operator will use the assigned value if no
other values are assigned elsewhere, allowing for overrides.
Bug: 230638462
Test: adb shell getprop | grep bluetooth
Merged-In: Ie29700e8b87f6f3fc2da741411dfbe94fa56ca36
Change-Id: Ie29700e8b87f6f3fc2da741411dfbe94fa56ca36
The class of device is a string with a list of uint8t values:
90,2,12
The meaning is as follows:
{Service Field, Major class, Minor class}
Service Field: 0x5A -> 90
Bit 17: Networking
Bit 19: Capturing
Bit 20: Object Transfer
Bit 22: Telephony
MAJOR_CLASS: 0x02 -> 2 (Phone)
MINOR_CLASS: 0x0C -> 12 (Smart Phone)
Bug: 217452259
Test: make -j; -- check that bluetooth.device.class_of_device is
correct
Merged-In: I75a6fb83a6149f58372b7aa46ccc190fd4451ab0
Change-Id: I75a6fb83a6149f58372b7aa46ccc190fd4451ab0
Those keys will be embedded into VtsSecurityAvb on host side
instead, to verify the GSI image used on the device.
Bug: 149806769
Test: build and checks those keys are removed from
$OUT/recovery/root/first_stage_ramdisk/avb/
Change-Id: I8a002ba6f1421fb460056ccae6572050bdb0ce3c
This fixes GSI image overriding the default value
Bug: 153852350
Test: Manually verified after flashing the GSI image
Change-Id: I78b415862c420c23121ec03d6953814cd628ea9a
Add some librart which will load during camera launch to reduce camera
launch time in I/O busy case.
Bug: 165825997
Test: Camera_checklist, dumpsys pinner
Change-Id: I48b5503ad674dc19cda940c44878291171fa4536
* ro.vendor.audio.sdk.ssr: False is default
vendor.audio.enable.mirrorlink: Unused in AOSP
vendor.audio.safx.pbe.enabled: False is default
Change-Id: If30194f5bcd4f69edf7ac43fe3725db4fe9b3da1
* Lahaina is supposed to be a supported target, but
some CTS tests fail. Oplus also disables these in
OOS.
Change-Id: I5921e0f4ecb2140a5610059bdd16cc6e99d7d725
* Currently, cancelEvents in MTP will cancel the requests one by
one, and it will check each response to confirm success or
failure. However, if kernel usb controller driver got the
cancel request, the driver will handle all requests in the same
endpoint so that the second io_cancel in cancelEvents will be
useless causing the cancelEvents to return error and fail the
transfer.
* Fix this by setting sys.usb.mtp.batchcancel for the targets
using MTP over FFS.
Change-Id: Icea9a2815c79ff710ee887d02e4c99dfe5ad6361
* Used by system_ext/lib64/liboplusstagefright.so
and Oplus' surfaceflinger, neither of which we
have.
Change-Id: Id04538d5c7ed3424fbb8aab9031aa929c7e2fe01
