due to some miatoll devices not having a11 fw which leads to them being L3, this should load a11 blobs for a11 devices (currently only curtana) while the default is a10 blobs, temporary
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 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>
move sensors specific boot up commands from global init.qcom.rc to component
specific rc files , which are part of individual component projects.
Change-Id: Ib0410cd0af8d77573bd320063982b504b1b1d1d5
Remove context hub HAL service from common init rc file to
target specific
Change-Id: If32c8c15ad5e9ab4103db21580955bff6bfe92ef
Signed-off-by: Jeya R <jeyr@codeaurora.org>
This patch removed the old writeout policy tune which was never touched since
2009. In the meantime, most of Android devices are equipped with over 4GB DRAM
and very fast flash storages like UFS, which becomes more like desktop or
servers in 2009. So, it'd be worth to go back to use the default kernel configs.
Bug: 136483670
Bug: 137190999
Bug: 152936751
Test: check value output
Change-Id: I1ebbf9f1f27a921103db51e96a50aadd6ec0dde8
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Signed-off-by: Martin Liu <liumartin@google.com>
Build process errors out without this.
Traceback (most recent call last):
File "build/make/tools/releasetools/ota_from_target_files", line 2455, in <module>
main(sys.argv[1:])
File "build/make/tools/releasetools/ota_from_target_files", line 2429, in main
output_file=args[1])
File "build/make/tools/releasetools/ota_from_target_files", line 1103, in WriteFullOTAPackage
common.CheckSize(boot_img.data, "boot.img", target_info)
File "/home/aicp-dev/rom/lineage-17.1/build/make/tools/releasetools/common.py", line 1190, in CheckSize
p = info_dict["fstab"][mount_point]
KeyError: '/boot'
Change-Id: I30a396ea62e6e48420c0dd41533c156e90032929
