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
Removing command to load ipa fw from post-fs, where FW mount
is not guaranteed.
Change-Id: I426bcfd2d9e0fb9f09a360374fe05b653676cf4b
CRs-Fixed: 2819603
QMCS partition is not a read only partition, and risks the danger
of causing unnecessary disk churn when QMCS files are read.
Update QMCS partition to be mounted with the noatime option.
Change-Id: Icf7e565d0e1c990131ad090c2f466bea419b4ad4
move spunvm partition out of fstab and mount in init.target.rc
only for lahaina as shima doesn't have spunvm partition.
Change-Id: I2b19c7cf84f23c0f73103fff2a2a7ae5a7dd186a
CRs-Fixed: 2801834
Properties that cannot be set from vendor are removed from
vendor.prop, other properties are removed from system.prop.
Change-Id: I1e15db5e11121ded15b768bd559b161fbf0ecea7
