* Xiaomi adds the audio_hw_socket here, but it needs
their changes in the audio HAL, hence it's useless
for us.
Change-Id: Idf38468ad709623b60b694f458e71d0565ce6fb6
This reverts commit 92b6e36b7163cf94e58c4e5b3e4c34fdb0c3d4b2.
So far it doesn't look like any GCam mod uses this.
Change-Id: I3926aef13315d329d07979cebc1e32f7ee2d25c1
This reverts commit f58073beb7855da7e3bc18ee50a0c4834ef72644.
Moved to device/qcom/sepolicy_vndr-legacy-um
Change-Id: I1f636a10ef6cd526d61557c2ca1c9589ff01ad5e
apk name and path was changed as seen here
8be4fc80c0
This causes errors in logs since pinner was trying to pin old app.
PinnerService: Could not pin file /system_ext/priv-app/SystemUI/SystemUI.apk
PinnerService: Failed to pin file = /system_ext/priv-app/SystemUI/SystemUI.apk
Change-Id: I609b29b9139d5cfaf1248c9ac001c280ae10c31c
This reverts commits 1edd945981e69ccdb2e2a41166dc51027dba7a43 and 9616ba9373631161dcb6b9240c0dcc6e27e216be.
sound_trigger doesn't work correctly with prebuilt audio HAL for
some reason.
Change-Id: Ia3a0c0881946bf8e2ab16668899d8cccf7accd0c
For some reason Xiaomi built audio HAL with "very very verbose" logging
enabled [1] and it spams really too much. Just shim the whole log function
to do nothing.
[1] https://github.com/LineageOS/android_hardware_qcom_audio/blob/c659e83702/hal/audio_hw.c#L41
Co-authored-by: Jan Engelmohr <jan.engelmohr@mailbox.tu-dresden.de>
Change-Id: Iff278c44f203dc7b81bccb2281edfc3f5687a47c
This looks very odd on most of the devices using this tree
because nothing is being patched. Just mention which image
is being flashed and only when it actually is.
Change-Id: Ib6c35e08aee0f1c102da28ca37434093a92f7045
* _ZN7android8hardware7details17gBnConstructorMapE and
_ZN7android8hardware7details17gBsConstructorMapE have been
removed in Android 13.
Signed-off-by: Lucchetto <lucchetto.tie@live.com>
Change-Id: I03ec2e4d709500cf01f8354cfba4dfa485b03293
ag/16564596 will change default value to false.
Configure correct overlay configuration.
Bug: 212488775
Test: manual test & build
Change-Id: Iaf1a0a23dae69fde5995e591a757a8ef5374d5b5
As of I3c7aed1bdb45db728d319f7d757400e44d232283 the Bluetooth stack
defaults to reasonable defaults that should work for all devices.
Change-Id: I056d63c4c8a2727e384172e964dc0000b6773504
* 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
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