- We don't use EXT4 for /system anymore hence let's mount it appropriately.
Change-Id: Ida90e4be8e36ca5778a4ca7d483ca3586b1f95e3
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
- EROFS offers much more compressed partition sizes compared to the likes of ext4 albeit being read-only.
- We have switched to EROFS for /system, /system_ext, /product, /odm and /vendor.
- This patch was inspired by [1].
[1]: 2b52a00408
Change-Id: I438f6b88ede93fe7e5d581439ba630b5c5440a48
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
Signed-off-by: donjohanliebert <donjohanliebert@gmail.com>
No longer needed now init listens for property changes on a
separate thread.
Bug: 186580823
Test: Cuttlefish boots successfully
Change-Id: Ief3a546d2154231d18957c2f703bd128966d7288
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
writepid command usage to join a cgroup has been deprecated in favor
of a more flexible approach using task_profiles. This way cgroup path
is not hardcoded and cgroup changes can be easily made. Replace
writepid with task_profiles command to migrate between cgroups.
Bug: 191283136
Test: build and boot
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: Ibb56d2379c42e5ed4b2f15c1b04d5fb163b48678
For easy transition from SchedTune to UtilClamp, direct access to these
cgroups should be abstracted by using task profiles. Replace writepid
commands with new task_profiles command.
Bug: 155419956
Test: change .rc file and confirm task profile is applied
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: Ide373c283359cf4b73af4cb0813d8c0306942595
The health AIDL HAL service provides functionalities of charger,
therefore system charger at /system/bin/charger is deprecated.
On top of that, QTI health AIDL HAL service enables suspend by
default, the equivalent of setting ro.charger.enable_suspend
for legacy charger.
Change-Id: I59c23e7974cea1174b0161f31a535fa3afa1e5c9
Default to false if the property is not set.
Device init scripts will need to be adapted to restart
loc_launcher service when property change is detected.
Change-Id: Icbda789cd2a9a3391f437af2c07fc5127f2f09ab
This reverts commit a13246a7fc.
This causes dac_override denials, set no_sehash_xattr on persist
in fstab instead to fix the issue.
Change-Id: I75f824d5b2beca5f7c3835045a7f568736e148f0
* Manually setting the doze status before entering the low-power mode
makes the doze mode not to be set correctly on sweet.
* The doze status is automatically set when entering the low-power mode
This reverts commit 10f101e143.
Change-Id: I4dfee2ffb351b9bc426268e437a26f9eaefec319
Kernels >4.7 will create a comp stream for each online CPU
and ignore /sys/block/max_compression_streams. This has been
backported to many 4.4 kernels as well.
Any device running a kernel with the upstream commit can safely remove
the parameter.
Upstream commit: 43209ea2d1
Change-Id: Ibb29b54a31f0fb5bd941d7709d15d571dd77ebf5
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
Increase the log level to '4', which would only log KERN_ERR
and lower, onto the console.Earlier it was incorrectly reduced
to 3 which would only log KERN_CRIT and lower.
Fixes: 06b604b6bef40abdb4b507fc13debb2146a922e1("Decrease the console log level")
Change-Id: Ic87d037450dd49138c3208e1b9f844469550364b
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
The restorecon_recursive directive in init is only applied if the
file_contexts file changed between builds, but not necessarily if any
file or folder inside /mnt/vendor/persist/ has changed.
The restorecon code checks whether an xattr named
"security.sehash" contains a string that matches the current
combined hashes of the SELinux context files and skips restoring labels
if there is a match, see
https://android.googlesource.com/platform/external/selinux/+/refs/tags/android-9.0.0_r35/libselinux/src/android/android_platform.c#1546
Force wiping that xattr so that restorecon always runs since it's not
very expensive (there are currently only about 50 files on /persist).
The restorecon is needed to fix issues such as wrong stock labels on
/mnt/vendor/persist/sensors/:
sensors_persist_file -> persist_sensors_file
Change-Id: Ic0cd848836ee550499d9236f56ed6e939e35f01e
[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
