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: Ic79a83f58c3b0ca09dd530f28e93da234ae4463a
Bug: 113028175
Bug: 134430124
Test: Build and flash taimen with the matching bootloader change. Toggle
dark mode in Settings. Check serial log regarding the start of
vendor.theme_{set,clear} services. Also read the value via `dd bs=1
skip=2048 if=/dev/block/sda5 count=32 | xxd` to confirm the change.
Test: Trigger a factory reset via Settings. Check the value in /misc
after the reset.
Change-Id: I3ae9ac41d689a4d0a9d5e0275de92c35dda068b7
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: I40baa222c92330757303ee9c2fd0e3f075dfac78
Signed-off-by: Mohan Srinivasan <srmohan@google.com>
To prevent property name collisions between properties of system and
vendor, 'vendor.' prefix must be added to a vendor HAL service name.
You can see the details in http://go/treble-sysprop-compatibility.
Test: succeeded building and tested on a taimen device.
Bug: 36796459
Change-Id: I1292f57b7ad27d0f96726f2073a5720b78281834
Taimen's vendor is on sde, this will make sure we have same tuning as walleye
Bug: 38000161
Test: check readahead
Change-Id: Ia2eaffa050804ee4e209e6263c91a8b9d67d736d
This reverts commit efce5fb8a0.
Reason for revert: moving this logic under wahoo init script
Bug: 64065874
Change-Id: I531d22c92456ebe4a95408407285867a54afeda5
This reverts commit 8d0e6dca79.
Change-Id: I5777501d14ed2d551dba5bb314cdfcd5476b785d
reason: restore the folder if /persist/sensors is missing
Test: flash on a phone without /persist/sensors folder
Test: reboot and verify sensor regsitry is created
Test: and sensors are available to sensor service
Bug: 64065874
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.
Note: testing was done on Walleye, not Taimen
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: I7551a4110ad025ec7975dd39301f048f0942f585
Bug : 62663757
- Change low persistence(LP) mode brightness from 255 to 159
- If panel version is 2-1, Set LP mode brightness to 255
Change-Id: Ie3754ac9ab11347e4f4edf91a607a17fc6b776fc
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: I6a544075a7ae71830e8ea9cb6a594dd062941f35
Directly using 'insmod' operation to init process is not permitted.
Therefore modified to use init.insmod.sh
Bug: 37914698
Test: booted device, touch works
Change-Id: I57ba8a86a6c508a66a805bacaf014640c6b49254
FPC IRQ conflicts with Touch SPI of LunchBox LCD. So fpc is disabled
in kernel on rev-0 only.
Stop the fps_hal service to avoid being continually re-loaded.
Test: built and verified on a device
Bug: 36076258
Change-Id: If77591bac111514470759d0e72fdc65b21c58f2b
