It will select "fast input" or "quad mic" as a compatible profile if
the parameter from recording app can't match the profile of
usb_surround_sound completely although connecting usb device.

Remove the usb device from the supported devices list of "fast input"
and "quad mic" for exact match.

Change-Id: Ie99886552082e99ac19193907b271131a2502d33

Add support for new LC3 format AUDIO_FORMAT_LC3
added for BLE support.

Change-Id: Ifd80fee833e05901544e2952781a460815661fb6

Remove dynamic attributes from APS config since it
is not supported.

Change-Id: I5ad81b67e7b6bb33e245a2620622f1e2e2a76506

Change-Id: Ia37b752c369d8b0dc48aba33898ce7e245f4de2d

Change-Id: I44004a3c1377d91e887f66905df5f8c61b0d5639

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.

https://android.googlesource.com/platform/frameworks/base/+/c78a463e875d91eae2cf256042fd99d130217c38

Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581

Change-Id: I7c0a9ad622a0c42966d84024c22cd03e033fd09b

Change-Id: Ibec129b39c0c7987f71f72107171cb53647572ab

Change-Id: I8770fb6c27637dfa934af45a3993c4447dcd2430

Additonally move xiaomi's additions to xiaomi_framework_compatibility_matrix.xml
and make them optional.

Change-Id: Ib3abddb4a9e9615fb973b9efd2e511d96998d6ce

Change-Id: I89d960aa3055628f3feb9881a8b6b7138262f89e

This is a pre-public tag which matches stock.
https://source.codeaurora.org/quic/la/platform/vendor/qcom/lahaina/plain/manifest_lahaina.xml?h=LA.UM.9.14.r1-12600-LAHAINA.0&id=2100bf201f102dcf517f7436dc5f6e802ab386ac

Change-Id: I4ebe1dc949c0e1188d18e04bae77ed62bdc51fc0

Change-Id: Ie1a43451abdcf02038e58959e1818a5275ae37c8

Change-Id: Ib1f92e29fd0830b6f13c2f899e6aa358e1997b4c

Change-Id: I41480402e01d1a32ee1d8562e73c8e97a9380aae

Squashed in this commit:
Author: Yifan Hong <elsk@google.com>
Date:   Mon Jul 15 16:43:26 2019 -0700

    sm8350-common: Replace BOARD_CHARGER_ENABLE_SUSPEND with ro.charger.enable_suspend

    Test: charger mode
    Bug: 124118169
    Change-Id: I3825d08e38d677bd7154879609857de302348b6f

Change-Id: I27a642dbadfba1575ff2d8e96dc385fc19c0eaff

This reverts commit 4372eed4.

Change-Id: Icd049f2e874d7044e7a156eac7d3f1d4e16460f1

The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:

  - We could easily end up with 160 MiB of camera app files pinned,
    which is a tall order with the 8 GiB of usable RAM that we have
  - The data that gets pinned may not even be the most critical data for
    launching the camera

Let's disable pinning of the camera app to save RAM.

Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24

These are not pinned on stock.

This reverts commit 98c9d2a9.

Change-Id: I69b906fbc0ae18c4d5832fc642beaae38ff6d392

Change-Id: I0ab13fb86b352680439198058b615f29f76f0165

* Activates some options on Settings>accessibility>vibration

Change-Id: I00e20f0d607736c04d5c2a0bd9c513c7f5fd8b41

Enable Adaptive color mode setting.

Bug: 143513730
Test: Boot test and measure the adaptive color value

Change-Id: I969ec6c3cb1d092a33c0e3a028ff38ad7115dfe2

This fixes deep sleep on AOD. The values are from stock,
note that xiaomi did not use RRO for these values, hence
the values are changed in framework-res.apk directly.

Change-Id: I9c4ea935e7a7df4bd85e1884f91ab25805fe8959

Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.

Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8

Change-Id: I37db0f8662f771885cf6e75027e23c62a51f7257

Change-Id: Ia57acd244608848f70fdcc30d5694c919db60671

Change-Id: I274cd7c5e5e47b2e86dbc733b37960e1a5993e7a

* This isn't needed anymore.

Change-Id: Ib77e5212099d82bbc07aea6044eb35109faff5cb

There is already a fallback to the model name and using that
is perfectly fine.

Change-Id: I7900cc449cd36d327d35f0597eea6427dd710458

Specifying avb=<vbmeta-partition> is only necessary for first entry of
partition groups that use same vbmeta partition. The following entry can have
<vbmeta-parititon> part omitted.

Test: None
Link: https://source.android.com/devices/architecture/kernel/mounting-partitions-early#fstab-entries


Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I5a42fd3de72c400acfae56d6a1e1b85c22a79537

Change-Id: I47c9b034600c9b31a17de2808030af38f69e10e0

Change-Id: I62629d99e0ace3e5cfa0bdef925e919ddd2ebe12

Add AID_VENDOR_FASTRPC group, so that fastrpc clients can be in
this group to get extra privileges on the remote subsystem, like
higher thread priority.

Change-Id: Icb8e418cfe66d696cad9d608d30f4b3f2a02bef8

Change-Id: I0ca98738e4964d23614df797b1faaebe0058a451

The copyright header has been modified by caf while the initial lahaina
tree whose fstab we use.
Specifically from https://source.codeaurora.org/quic/la/platform/vendor/qcom/lahaina/tree/fstab.qcom?h=LA.UM.9.14.r1-18900-LAHAINA.QSSI12.0&id=b403cbb26431c57a8590f94307f12443a55e29e2

Change-Id: I1dd07a729feeded6478e095573070fde532f2f02

Remove start console

Change-Id: I1041fa446499cd82bcbf6d5b86cb25a9a88fa90c
CRs-Fixed: 2977860

Disabling UFS clkgate and ah8 during boot time helps in reducing
IO delays, which helps in reducing the total boot time. This change
will disable UFS clkgate and ah8 during early-init and then enable
it back after boot completion.

Change-Id: I6a10cd57a30fe3bdc4fba72a0d84cdfa3b1fd513

Two fstabs are needed to support different data unit number (dun)
size for ufs and emmc hardwares. This needs different encryption
flag in fstab to address the difference in dun size.

[ArianK16a: don't add the emmc fstab since all our devices are ufs]

Test: Verified bootup, vts_kernel_encryption, fscryptctl.

Change-Id: Iff03422d39c789c544bdd86faef070ae46eb4e0e