Today, the dark boot follows the Dark Theme mode in Settings. Now
the UI team decide to always use dark boot after the device is
provisioned. So users will see fewer disturbances when a scheduled
update is taken at night
Bug: 181339788
Test: flash a Pixel -> boot -> dark theme is set;
boot again -> observe dark boot
Change-Id: Id4989e4e78471bcefc2730ba7d9adc36f5ac9c75
We have switch misc_writer to use more specific flags to set the dark mode.
Modify the caller as well.
Bug: 131775112
Test: set dark mode, check device boots with dark mode
Change-Id: Icbf3377e514f79b9b4bcf5c5a2dff9b0c8324df5
Bug: 113028175
Bug: 134157796
Test: Build and flash walleye with the matching bootloader change.
Check serial log regarding the start of vendor.darkboot and
vendor.darkboot_clear services when toggling dark theme in
Settings. Also read the value via `dd bs=1 skip=14408
if=/dev/block/sdd1 count=32 | xxd` to confirm the change.
Test: Trigger a factory reset via Settings. Check the value in /misc
after the reset.
Change-Id: Ie8504cec4358576890cc395de8df1679fa52fa01
With a request size fix, 2MB-sized readahead would not be a way to gain
boottime.
taimen - PVT - Hynix 128GB - boot_complete timestamp (avg of 100 loop)
Base [1] : 10.943
New [2] : 10.7495
taimen - PVT - Hynix 128GB - boot_complete timestamp + fastboot -w (avg of 100 loop)
Base [1] : 32.5857
New [2] : 31.7474
[1] w/o this CL, revert commit 7c37954411e9 ("mm: readahead back to 128KB")
[2] w/ this CL, keep commit 7c37954411e9 ("mm: readahead back to 128KB")
Bug: 122246531
Bug: 120757803
Change-Id: I2c3236b0b0cd4f2a8610a1af64de694f8a4d7997
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
The deadline IO scheduler results in lower latency SD, and pulls in
latency outliers (especially when the flash starts getting fragmented).
Switch to deadline post boot.
Test: various workloads, both synthetic (fio) as well as actual
workloads (app launch, ioshark).
Bug: 63630139
Change-Id: I94b90ac09e921fdf01564bd4c6e1a1b809f3f8ec
Signed-off-by: Mohan Srinivasan <srmohan@google.com>
Walleye requres /sys/class/uio/uio1/device/rtel/rtel in userdebug build,
and GSI will change the device to userdebug. So, we need to switch rtel
with the build type in boot time, even the device is in user build.
Bug: 65229896
Test: Boot (aosp_)walleye-(user|userdebug) with/without GSI to home screen
Change-Id: I8fa74c02a0a48feeef87d8e9caa702e4a44aedf7
Bootloader set androidboot.revision on kernel command line and we set
ro.boot.hardware.revision to a numerical string accordingly.
Bug: 64375827
Change-Id: Ib814f765b53155721d86035405fbc6490fb5a2c3
Signed-off-by: Thierry Strudel <tstrudel@google.com>
Tested 1/2x, 1x, 2x, and 4x the current readahead buffer and noop and
cfq I/O schedulers for /dev/block/sda, which contains /data. The most
consistent performance boost was seen across all UFS vendors and storage
sizes using cfq and a readahead buffer of 1024.
Bug: 38000161
Test: Compared 1P app launch times using app-launcher for schedulers
(noop, cfq) and readahead buffer sizes (128,512,1024,2048)
Change-Id: Ifcc9145d6f7a77ba4b3844b7892291eb348d9e1c
With noop scheduler, I see dramatic jank with an irritant i/o thread;
going back to cfq, which doesn't have nearly the same negative impact
on UX.
Bug: 62375787
Test: boot, scroll a lot
Change-Id: I3c1ad17f432b25b5359f813e070fd1266dac1f87
Disable kernel module loading after boot on user builds.
Bug: 38204366
Test: boot walleye, confirm kernel module does not load after boot
Change-Id: I40217ff37c1b1bcf00155e5bec74b92a020481f7
