sync ag/6911752,ag/9342439
fine tune the read_ahead size for boot time
Bug: 137150088
Bug: 139640385
Bug: 143448664
Test: boot to home and boot time measurement
Change-Id: If7929c51222e325a019532ce0d16045a52778165
Signed-off-by: Kyle Lin <kylelin@google.com>
Signed-off-by: Ocean Chen <oceanchen@google.com>
RD1A.200703.001
dmesg_action_sys.boot_completed_first_timestamp_avg : 14745.3
With CL
dmesg_action_sys.boot_completed_first_timestamp_avg : 13993.7
Bug: 143857500
Bug: 161478668
Test: build and boottime test
Tested-by: Lisa Liu <liulisa@google.com>
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: Ib8f31d39501b4747f0c268d2dd87e814bcc7843b
Because the arch is similiar with SDM670, we aling the setting with
bonito.
Bug: 142552311
Test: build , munaual check the settings
Change-Id: Ie4d4cd252cbe5cdaf733a8db09117808eb0ec27c
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>
* "32-bit overflow" CAF mentioned in the function wrapper inside post-boot
script sounds very bs, since if it's 64-bit it won't be affected anyways
* We do the setup using fstab instead to allow setting up more flags such
as setting up backing device and compression streams; as such kanged from
Pixels
* zRAM size = 50% physical memory size to satisfy what CAF really wants
* Use LZ4 compression even for regular devices
Signed-off-by: Albert I <kras@raphielgang.org>
Signed-off-by: Alexander Winkowski <dereference23@outlook.com>
Change-Id: Ia6efb3d28e56fb026d9b28fc6633b2eac77dfa47
init : Command 'mkdir /firmware 0771 system system' action=early-init (/vendor/etc/init/hw/init.target.rc:31) took 0ms and failed: Not a directory on /firmware
init : Command 'mkdir /bt_firmware 0771 system system' action=early-init (/vendor/etc/init/hw/init.target.rc:32) took 0ms and failed: Not a directory on /bt_firmware
init : Command 'mkdir /dsp 0771 media media' action=early-init (/vendor/etc/init/hw/init.target.rc:33) took 0ms and failed: Not a directory on /dsp
Signed-off-by: orgesified <me@orgesified.ml>
Change-Id: I129f6fd9210076fffa1912e3dd6dcec32bd5acf6
* /data/tombstones and /data/vendor/tombstones are both created by
the system's init.rc.
* Creating /tombstones at the root isn't allowed since the root is
a ramdisk and mounted read-only.
Change-Id: I04586994280ae48f36542f56e1cace422943376b
This should be done earlier:
libprocessgroup: Failed to open /dev/cpuset/camera-daemon/tasks: No such file or directory: No such file or directory
libprocessgroup: Failed to apply CameraServiceCapacity task profile: No such file or directory
Change-Id: I9edbdad2e764667a4624b181e0426f14ed9be616
* Remove unused/duplicated parts
* Make changes to do without other scripts
Co-authored-by: Demon000 <demonsingur@gmail.com>
Change-Id: I8e758337488dc19ecb47ec1b583fba33ef05882d
