Evolution-x-devices/device_google_walleye
2
0
Fork 0
mirror of https://github.com/Evolution-X-Devices/device_google_walleye synced 2026-02-01 07:33:36 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
d0010076bceb130e6b44ca69b0624ea4eff7df3b
device_google_walleye/init-common.rc

76 lines
2.8 KiB
Plaintext
Raw Normal View History

Revert "Boottime: remove all block-related tunes including readahead size" This reverts commit 08e352d88b0ad3f6e3e085ccdd25314b0287b16f. Reason for revert: boottime regression found by b/126431810 Change-Id: Ie9b9f05bfff86518fe59fdd06d1a33f423567184
2019-03-11 23:18:27 +00:00
on late-fs
# boot time fs tune
write /sys/block/sda/queue/iostats 0
write /sys/block/sda/queue/scheduler cfq
write /sys/block/sda/queue/iosched/slice_idle 0
write /sys/block/sda/queue/read_ahead_kb 2048
write /sys/block/sda/queue/nr_requests 256
write /sys/block/dm-0/queue/read_ahead_kb 2048
write /sys/block/dm-1/queue/read_ahead_kb 2048
on property:sys.boot_completed=1
# end boot time fs tune
write /sys/block/sda/queue/read_ahead_kb 128
write /sys/block/sda/queue/nr_requests 128
write /sys/block/sda/queue/iostats 1
write /sys/block/dm-0/queue/read_ahead_kb 128
write /sys/block/dm-1/queue/read_ahead_kb 128
disable kernel module loading after boot 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
2017-05-10 16:28:53 -07:00
on property:sys.boot_completed=1 && property:ro.build.type=user
write /proc/sys/kernel/modules_disabled 1
init-common.rc: set ro.boot.hardware.revision 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>
2017-08-09 22:04:19 -07:00
on init && property:ro.boot.revision=EVM
setprop ro.boot.hardware.revision 0.5
on init && property:ro.boot.revision=EVT0
setprop ro.boot.hardware.revision 0.6
on init && property:ro.boot.revision=EVT1
setprop ro.boot.hardware.revision 0.7
on init && property:ro.boot.revision=EVT2
setprop ro.boot.hardware.revision 0.8
on init && property:ro.boot.revision=DVT
setprop ro.boot.hardware.revision 1.0
on init && property:ro.boot.revision=MP0 # PVT
setprop ro.boot.hardware.revision 1.0
on init && property:ro.boot.revision=MP1
setprop ro.boot.hardware.revision 1.0
Fix walleye to boot with GSI 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
2017-09-19 12:11:14 +08:00
on boot && property:ro.build.type=userdebug
write /sys/class/uio/uio1/device/rtel/rtel 1
init-common: map sys.retaildemo.enabled to persist.vendor.charge.* Bug: 73647497 Change-Id: Id317f390da648b935819e25342725a4663ee5841 Signed-off-by: Thierry Strudel <tstrudel@google.com>
2018-03-26 17:27:30 -07:00
init-common.rc: map sys.retaildemo to persist.vendor.charge.*.level Bug: 75293289 Change-Id: I0cfc3538fb7f377d578e4bf8fdc6e338a3d0a097 Signed-off-by: Thierry Strudel <tstrudel@google.com>
2018-04-03 16:20:04 -07:00
on property:persist.vendor.charge.stop.level=* && property:sys.all.modules.ready=1
init-common: map sys.retaildemo.enabled to persist.vendor.charge.* Bug: 73647497 Change-Id: Id317f390da648b935819e25342725a4663ee5841 Signed-off-by: Thierry Strudel <tstrudel@google.com>
2018-03-26 17:27:30 -07:00
write /sys/module/htc_battery/parameters/charge_stop_level ${persist.vendor.charge.stop.level}
init-common.rc: map sys.retaildemo to persist.vendor.charge.*.level Bug: 75293289 Change-Id: I0cfc3538fb7f377d578e4bf8fdc6e338a3d0a097 Signed-off-by: Thierry Strudel <tstrudel@google.com>
2018-04-03 16:20:04 -07:00
on property:persist.vendor.charge.start.level=* && property:sys.all.modules.ready=1
init-common: map sys.retaildemo.enabled to persist.vendor.charge.* Bug: 73647497 Change-Id: Id317f390da648b935819e25342725a4663ee5841 Signed-off-by: Thierry Strudel <tstrudel@google.com>
2018-03-26 17:27:30 -07:00
write /sys/module/htc_battery/parameters/charge_start_level ${persist.vendor.charge.start.level}
Dark boot on dark theme. 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
2019-06-03 15:30:17 -07:00
# Write the dark theme magic (`theme-dark`, or 0x7468656d652d6461726b in hex string) to /misc
# partition. Offset 12360 (0x3048) in vendor space is effectively offset 14408 (0x3848) in /misc
# partition.
service vendor.darkboot /vendor/bin/misc_writer --vendor-space-offset 12360 --hex-string 0x7468656d652d6461726b
disabled
oneshot
# Clear the 10-byte dark theme magic in /misc partition. Offset 0 in vendor space is effectively
# offset 2048 in /misc partition.
service vendor.darkboot_clear /vendor/bin/misc_writer --vendor-space-offset 12360 --hex-string 0x00000000000000000000
disabled
oneshot
# Set the dark boot flag on dark mode (UiModeManager.MODE_NIGHT_YES == 2).
on property:persist.sys.theme=2
start vendor.darkboot
# Clear the dark theme flag on light mode (UiModeManager.MODE_NIGHT_NO == 1) or auto mode
# (UiModeManager.MODE_NIGHT_AUTO == 0).
on property:persist.sys.theme=1
start vendor.darkboot_clear
on property:persist.sys.theme=0
start vendor.darkboot_clear
Reference in New Issue Copy Permalink