Disabling UFS clock scaling during boot time helps in reducing
IO delays, which helps in reducing the total boot time.
This change will disable UFS clock scaling during early-init and
enable it back after boot completion.
Change-Id: Ib3490a8155610aea399ac2f63aa4a71bee299c6e
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
-Switch to LZ4 for better overall performance
-Set max_comp_streams to num of cores since upstream also moves this to
percpu.
-Set page-cluster to 0 as the incremental cost of reading 1 page at a
time is negligible for zram
Bug: 38249616
Test: boot and run zram-perf showing better performance
Change-Id: I0b92b246d773db85aa03d033b2cecee54347cbd1
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Also includes:
commit 82dcb788c9c2ee5d50e75e050550cc841262d3df
Author: Kuba Wojciechowski <nullbytepl@gmail.com>
Date: Mon Jun 15 21:01:20 2020 +0200
ginkgo: rootdir: Move boot animation early start to late-init
* "on init" is triggered in offline charge mode too causing
boot animation to launch in that mode.
* Ref: https://github.com/aosp-mirror/platform_system_core/blob/150687b/init/init.cpp#L854-L866
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Set lmkd.reinit property to 1. This will trigger
reinit of lmkd service after boot complete.
CRs-Fixed: 2692843
Change-Id: Ib946b01ca1dc013f0148ca702e4d550cde32b6c2
We have plenty of space left at /system
Change-Id: I39d552259b66ec329c56cd4f4a7fc46fb2c07457
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
This patch enables zram-writeback job. It will run idle marking
at 60m since the device is boot. After that, it will do first
writeback after 3hour to sweep initiallized cold pages out.
After that, it periodically write out every 24hour.
Bug: 117682284
Bug: 127185055
Test: confirm with manual testing
Change-Id: I6857c79ca3ce6a3619f4b7e200d7f17a8decd659
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Support has landed in WebView, so time to turn it on in framework!
Bug: 111461797
Test: manual
Change-Id: I064cf3512928637895932b3405adaec74b1ceed2
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
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
Signed-off-by: Tushar Mahajan <mahajant99@gmail.com>
* We used to have an init extension, which breaks treble
and since P it requires custom SELinux rules to allow
init reading /proc/sys/kernel/boot_reason
* Remove the init extension and set the property like
QCOM does through init.qcom.early_boot.sh
* Update the property with vendor prefix while we are at it
Change-Id: I238f754a17c9a548c6c90503bfa4b21763d1b4c4
Signed-off-by: Sonal Singh <sonal.singh.19993@gmail.com>
* This enables Deep Sleep mode, additionally to QPower
* With this configuration, QPower manages the new Deep sleep mode
-> Leads to amazing power savings
Change-Id: I32dbaee6406fbe01594176ba14c9f3f0c6d16714
PA Notes:
- Not merged to master, but merged to internal master.
- Original commit removes libsurfaceflinger but I do not
because we have enough memory.
Test: Builds as expected after this change, and flashes successfully.
Bug: 176197656
Signed-off-by: Sonal Singh <sonal.singh.19993@gmail.com>
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 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 precious RAM on this
device.
Signed-off-by: Sonal Singh <sonal.singh.19993@gmail.com>
Xiaomi has built this device with TARGET_HAS_WIDE_COLOR_DISPLAY=true (possibly because it is the default in caf), but
the hardware doesn't properly support DISPLAY_P3 profilem causing weird yellowish tint in some scenarios. Force
disable the feature to fix it.
Signed-off-by: Kuba Wojciechowski <nullbytepl@gmail.com>
This change yields considerable SQLite performance gains. It
should be generally safe as this device has irremovable battery.
Some OEMs have been doing this for years.
Signed-off-by: Jesse Chan <jc@lineageos.org>
Change-Id: Ic775c3fa735a32653d8e7f4c15cac26c6ebc262c
This will OFF kernel page table isolation.
Notes from Kuba Wojciechowski <nullbytepl@gmail.com> in 86bb20a832:
As per qualcomm - "SM8150/SM8250/SM8350/SM7250/SM7150/SM6150 - KPTI Not required".
It can also help increase performance by a lot in some scenarios.
Change-Id: Idd36c359d4955701e9ee3ee27a58177a8d622c86
Signed-off-by: Rahul Shahare <rshaha@codeaurora.org>
To make VOIP work properly the following has to be set:
AUDIO_FEATURE_ENABLED_COMPRESS_VOIP := false in BoardConfig.mk
vendor.audio.feature.compr_voip.enable=true in vendor.prop
I have no idea why this is but setting either one of them differently results in the mic not working as it should.
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
