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
* The following things are left in devices, because they're device specific
- voip compress properties
- HVDCP properties
- audio configs
- power profile
- rounded corner configuration
- partition configuration
- FOD
- camera motor
- NFC
- board-info
- fstab
- ipa and graphics firmware
- shipping and manifest target level
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Co-authored-by: Arian <arian.kulmer@web.de>
Change-Id: I8bef29041f8f239361b999fc8ab1a43cc2ebb86b
Add owners for new lcd brightness and max_brightness node
/sys/class/backlight/panel0-backlight/brightness
/sys/class/backlight/panel0-backlight/max_brightness
Change-Id: I939ed22dc880a3536d95b397dbc7bed9288bc5df
Change ownership of UFS RPMB bsg node so that TZ RPMB service
can open this node without root permissions.
Change-Id: I285e2ae26094677d91ad8486457af86e7aaabbb9
Disabling UFS clock scaling during boot time helps in reducing
IO delays, which helps in reducing the total boot time.
This change will disable UFS clock scaling during early-init and
enable it back after boot completion.
Change-Id: Ib3490a8155610aea399ac2f63aa4a71bee299c6e
Mount of tracefs in /sys/kernel/debug/tracing will fail when DEBUG_FS
is disabled. So, mount tracefs in /sys/kernel/tracing to still use all the
tracing abilities when CONFIG_DEBUG_FS is disabled
Change-Id: Ib37332c3f1108d7c4798717f0f009c891db72850
This changes removes tftp and rmt storage service definitions
from main .rc file as these services are defined in respective
local .rc files.
Change-Id: Ibbd1fda31b7fd950590d6a15b7aca3bb08d84f4b
move sensors specific boot up commands from global init.qcom.rc to component
specific rc files , which are part of individual component projects.
Change-Id: Ib0410cd0af8d77573bd320063982b504b1b1d1d5
add wakelock group and BLOCK_SuSPEND capabilities to vendor.sensors
to acess wake-lock sysfs nodes
Change-Id: I193836d097f15f5bfbe1645909ae70f3f870f972
Make charger binary run as system instead of root. Since it
needs to handle input key events, add input as a supplemental
group in addition to system and graphics.
Change-Id: Id1dc46f335087147b7d8cf674664c26f0b511de1
Two fstabs are needed to support different data unit
number (dun) size for ufs and emmc hardwares. This
needs different encryption flag in fstab to address
the difference in dun size.
Change-Id: Ifb0e9132fc91e3281401ac49ad70c695a22c9df5
* Enabling the services allows them to start at their proper stage (class main)
* Enable them on boot to ensure they are enabled before class main starts
Change-Id: I71c3fcb72b38d247d304fda2fa6b2cc76baa0db2
* These modules are disabled by default and started by
init.class_main.sh which we do not ship. Start them from init.qcom.rc
on post-fs-data instead, just like qcrild.
Change-Id: Ifa907b5e33d8d3d08e64baaabfb8e3e450925e96
