Unable to determine UFFD GC flag for kernel version "5.4.268-qgki".
You can fix this by explicitly setting PRODUCT_ENABLE_UFFD_GC to "true"
or
"false" based on the kernel version.
1. Set PRODUCT_ENABLE_UFFD_GC to "true" if the kernel supports
userfaultfd(2)
and MREMAP_DONTUNMAP.
2. Set PRODUCT_ENABLE_UFFD_GC to "false" otherwise.
Change-Id: Ie77d9a86a7fe94e4cade1868ffea27194f724e03
Floral has issues that prevent it from working with a hermetic
partition build.
Bug: 205632228
Test: Presubmits
Change-Id: I490a29da38a6f68e7dd3650d8140cb11adaa8c7a
This got enabled by default on U, and it causes apps like
Chrome and Youtube to set the refresh rate to 30FPS when
playing some videos.
Change-Id: I649bf03d550c2b9726c7957d15ed09e455d874ec
Enable the persist.sys.fuse.passthrough.enable flag for the device
configuration to enable the FUSE passthrough feature.
This feature has been enabled on Cuttlefish, Wembley and Redbull devices for
months and no issues have been detected yet.
Bug: 168023149
Test: 'adb shell getprop | grep persist.sys.fuse.passthrough.enable',
ScopedStorageTest
Signed-off-by: Alessio Balsini <balsini@google.com>
Change-Id: I3f39b02af436f7e508bb70efc702565a667a051c
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
The vendor variants of android.hardware.drm@1.[0-4] are no longer
implicitly built since the migration to AIDL ClearKey DRM HAL.
Change-Id: I79c69e93e27f3c2f4a1c6f7acf5f013ee8f6cd03
Needed to work around a Qualcomm HAL prebuilt.
Bug: 203713560
Bug: 258322017
Bug: 254854421
Test: Forrest
Change-Id: I4eebc60f10fbea6a66127ed3e08441db32536f78
Replace certain policies for isolated_app with the newly introduced
isolated_app_all for better scalability.
Bug: 265540209
Test: m
Change-Id: I1b6866d56f15089babe368bb60335c7ed99bdd6b
The new folder structure now looks like this:
device/qcom/sepolicy_vndr
├─ legacy-um (meant for sdm845 until sm8350)
├─ sm8450
└─ sm8550
Change-Id: I4ed1a06af779909d64172da294c4a99a3ae9ba0d
Starting with Android R launched devices, debugfs cannot be mounted in
production builds. In order to avoid accidental debugfs dependencies
from creeping in during development with userdebug/eng builds, the
build flag PRODUCT_SET_DEBUGFS_RESTRICTIONS can be set by vendors to
enforce additional debugfs restrictions for userdebug/eng builds. The
same flag will be used to enable sepolicy neveallow statements to
prevent new permissions added for debugfs access.
Test: build, boot
Bug: 184381659
Change-Id: I45e6f20c886d467a215c9466f3a09965ff897d7e
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
