Remove manifest entry for PASR HAL device specific manifest so this can be
moved to memory component.
Change-Id: I1c2044c76fabacede3d41dc0a53ca99cb50a9342
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
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
Additonally move xiaomi's additions to xiaomi_framework_compatibility_matrix.xml
and make them optional.
Change-Id: Ib3abddb4a9e9615fb973b9efd2e511d96998d6ce
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
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
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
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
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
