Following the previous commit, starting with Android S most HAL
libraries are not included in VNDK anymore - they need to be explicitly
pulled in to `/vendor` for odm blobs to be allowed to access them:
linker : CANNOT LINK EXECUTABLE "/odm/bin/netmgrd": library "android.system.net.netd@1.1.so" not found: needed by main executable
Signed-off-by: Marijn Suijten <marijn.suijten@somainline.org>
Change-Id: Ide8adad466a61412a984a46d1562f8f2f6a62be3
In [1] Google removed many HIDL HAL libraries from VNDK, causing them to
only be installed to the system partition. This is inaccessible for
vendor apps and results in the usual:
linker : CANNOT LINK EXECUTABLE "/odm/bin/hw/android.hardware.keymaster@4.0-service-qti": library "android.hardware.keymaster@4.0.so" not found: needed by main executable
linker : CANNOT LINK EXECUTABLE "/odm/bin/hw/android.hardware.keymaster@4.0-service-qti": library "android.hardware.keymaster@4.1.so" not found: needed by /odm/lib64/libqtikeymaster4.so in namespace (default)
linker : CANNOT LINK EXECUTABLE "/odm/bin/hw/vendor.somc.hardware.modemswitcher@1.0-service": library "android.hardware.radio.config@1.0.so" not found: needed by /odm/lib64/libril-qc-hal-qmi.so in namespace (default)
linker : CANNOT LINK EXECUTABLE "/odm/bin/hw/qcrild": library "android.hardware.secure_element@1.1.so" not found: needed by /odm/lib64/libril-qc-hal-qmi.so in namespace (default)
linker : CANNOT LINK EXECUTABLE "/odm/bin/hw/qcrild": library "android.hardware.secure_element@1.2.so" not found: needed by /odm/lib64/libril-qc-hal-qmi.so in namespace (default)
linker : CANNOT LINK EXECUTABLE "/odm/bin/hw/qcrild": library "android.hardware.radio.deprecated@1.0.so" not found: needed by /odm/lib64/libril-qc-hal-qmi.so in namespace (default)
These libraries are listed in common-treble because they're used by ODM
apps but have no explicit vendor dependency (ie. a binary placed on
/vendor) to put them in a vendor-available space. The default is to
include system variants which is why the dependencies have to be
suffixed with `.vendor` so that they're shipped in `/vendor` and are
available for our ODM blobs even on GSIs.
[1]: d610435ac4
Signed-off-by: Marijn Suijten <marijn.suijten@somainline.org>
Change-Id: I8344b85fb4e86a913bd8d9071ce49150ed093575
The first default zram write back time is 3 hours which
is for go device to quickly save more ram. For Pixel
devices, we have more working set and could bring launch
time impact if we write back too fast. Thus, adjust the
first time write back time to 24 hours which is aligned
with periodic write back time.
Bug: 166739872
Test: boot
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: I2388dd6d75ab0a938fe0edae0563fd26e48c9908
[libfs_mgr]Warning: unknown flag: zram_loopback_path=/data/per_boot/zram_swap
[libfs_mgr]Warning: unknown flag: zram_loopback_size=512M
We don't use zram_loopback_path any longer so remove it.
We also changed zram_loopback_size with zram_backingdev_size so correct it.
Bug: 145330273
Bug: 145116439
Test: confirmed there is no warning and zram backing device was configured
Change-Id: I51be34c59203813a2f493eee6ab442c9940b75d7
Signed-off-by: Minchan Kim <minchan@google.com>
Signed-off-by: YH_Lin <yhli@google.com>
-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
* The modem version is a minimum requirement, hence it's useless to
assert on multiple modem versions.
Change-Id: I206b05365681d2292417dfbdc78b9faf11e2a295
* When setting the doze mode to HBM, disabling AOD and enabling it again
the doze mode was still set to HBM but the listpreference was reset to
LBM.
Change-Id: Ibd9682c97757335ac4df48a21c7b64f7b36dd585
Allows us to check the idle state of the display in order to use perf
hints to improve system performance.
Bug: 69270928
Bug: 69915886
Test: Booted and cat-ed the affected files
Change-Id: I8717093e9b8ed9ed35b6ca51a20225abbf71f775
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>
