Because the arch is similiar with SDM670, we aling the setting with
bonito.
Bug: 142552311
Test: build , munaual check the settings
Change-Id: Ica44125c8ed71a85cfd6bde77c9107bceed7b094
Bug: 36367381
Test: Boot and check stune configuration effect on sysfs
Change-Id: I838c31d164684a5d88550c92284b65bb50f2ed56
Signed-off-by: Andres Oportus <andresoportus@google.com>
Signed-off-by: Arian <arian.kulmer@web.de>
-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
Add support to set "ro.netflix.bsp_rev" property at run time
depending on the target. This is needed when 2 or targets are
binary compatible, but have different Netflix proprty for
device whitelisting.
Change-Id: Ieccd17128f1b73c819a3f33816eb8c402cfa17e2
Set drm_vblank_offdelay parameter to -1, to make DRM
issue the vblank disable immediately with out delay.
By defailt the DRM framework has a delay of 5 secs
timeout before issuing the vblank disable.
Change-Id: Idc1dfe6a6994f2ac2d3c60ae8fd5a4e883b675d9
* /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: I6c3a287056a2264d9e9ffe4557ecca8c6e03c0bb
Decrease the log level to '3', which would only log KERN_ERR
and lower, onto the console. This is to avoid false-positives
in the test cases that may emit excessive logs, ultimately
leading to a watchdog bark.
Change-Id: I7967272de8e425e93035cd937982bfb3aee19597
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>
If we set 2048KB ra value in the beginning of the
boot process, services initialized at this time would
keep 2048KB ra value even though we adjust the ra value
to 128KB after boot completion.
This may cause memory pressure.
Bug: 174700194
Signed-off-by: Randall Huang <huangrandall@google.com>
Change-Id: I97ee0ee9511eaada011f2634afd68d68cdca4570
Previously we found that the effect of using sched_boost is very
similar to skipping EAS. Since sched_boost is not used because of
CONFIG_SCHED_WALT not enabled, we can boost performance this way.
Bug: 119932121
Test: launch time and app launch time are better than EAS
Change-Id: Idf8026c258b6c36417c9be9b5c87f7b4bfa3f50d
* By default, AOSP uses the 'US' country code for wifi.
* When a SIM is present, Android can check the correct country
(using information from the SIM itself) and it can set the correct
country code.
* However, if no SIM is present or if the phone is in airplane mode,
Android will just use 'US' as country code and it will disable access to
a lot of frequencies.
To bypass this issue, set the default country code to '00': this
is the "world regulatory domain" and it contains generic settings.
When a SIM is inserted, Android will overwrite the default setting with
the correct country code.
Copy from Google:
12b500667e/init.hardware.rc (524)
Change-Id: If7537357f282c51549f754cd385bc1ab9a9a109c
Signed-off-by: Roberto Sartori <roberto.sartori.android@gmail.com>
Signed-off-by: dogpoopy <dogpoopy.dev@proton.me>
Signed-off-by: bagaskara815 <bagaskara815@gmail.com>
