* It depends on symbol CBS_init which is removed from the latest libcrypto.
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.drm@1.3-service.widevine": cannot locate symbol "CBS_init" referenced by "/vendor/lib64/libwvhidl.so"...
Change-Id: I835f53be4970754bfffc37e8a5f5ddf0d16995ff
A dist build fails on a-only devices with retrofit dynamic partitions due to [1].
The check does not take a-only devices into account, even though they are capable of retrofit aswell.
While the PRODUCT_RETROFIT_DYNAMIC_PARTITIONS flag is used to detect and warn about misconfigurations, it does not seem to be needed for any retrofit functionality.
Hence, to avoid changes in releasetools, drop the flag.
[1]: 055b7692fb/tools/releasetools/check_partition_sizes.py (L185)
Change-Id: Ib0dfe4ee3da4c583d924d85a79d5ec37a2f9ba87
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
Since Ext4 doesn't implement "-o sync", it commits metadata at every 5 secs.
This may cause /metadata corruption.
Bug: 162883014
Change-Id: Icd38754bad1b1529d01165ea8c703c214d20bb4b
android.hardware.media.omx@1.0-service: Service not available yet
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: popoA3M <pratyayaborborah@gmail.com>
* Needed because stock does not use dynamic partitions so
there's no existing metadata that could be used
Change-Id: Icbc828389465f3d4681ca8e4c3adec782540752e
* don't include debug configs in art
* use everything filter for dexpreopt (AOSPA/android_vendor_pa@ab5061c)
* use non-debug dex2oat
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Signed-off-by: Jabiyeff <cebiyevanar@gmail.com>
* Fix for aidl power stats errors.
* New updated legacy-um sepolicy solved the android.hardware.power@1.0::IPower/default error
- Now with this we fixing both errors:
BatteryStatsService: Unable to load Power Hal or power.stats HAL
hwservicemanager: getTransport: Cannot find entry android.hardware.power.stats@1.0::IPowerStats/default in either framework or device manifest.
hwservicemanager: getTransport: Cannot find entry android.hardware.power@1.0::IPower/default in either framework or device manifest.
The HIDL interface of "android.hardware.memtrack" is no longer supported
for Android S.
Test: atest VtsHalMemtrackTargetTest pass
Bug: 186539435
Change-Id: Iaafd526fc5a601f7e8189ec764399d99c660beb0
- These seem to be long gone/not available to be source compiled?
- Anyways, these seem to have no actual function and are not needed other than to avoid logspams
unknown target 'libldacBT_dec'
unknown target 'libldacBT_bco'
Change-Id: Ia65d4e72128352132a7ad1a00c61d9596ece714a
Signed-off-by: SparXFusion <s2234nadar@gmail.com>
This ensures that the most up-to-date JSON files are shipped.
Change-Id: Ic9fae188784825ae6dc607c13b403e37290b7067
Signed-off-by: Mohammad Hasan Keramat J <ikeramat@protonmail.com>
sdm710-common: Ship cgroups.json and task_profiles.json in vendor
Google's prebuilt cgroups.json and task_profiles.json for products
launched with previous API levels only covers
ro.product.first_api_level >= 28. [1]
These devices were launched with N MR1 (API level 26), so schedtune
and task groups are completely broken. Since the system also checks
/vendor/etc for vendor profiles, make a copy of cgroups_28.json
and task_profiles_28.json and ship them to /vendor/etc. Profiles
for previous API levels are all the same anyway.
Test: boot and check /dev/stune/
[1] system/core/libprocessgroup/profiles/
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Change-Id: I33c0540ef50054fad839886f9f014cc275659e77
Signed-off-by: Mohammad Hasan Keramat J <ikeramat@protonmail.com>
* Its eating more RAM and slow down device
* Thanks for CAFEBABE find this
Signed-off-by: Jabiyeff <cebiyevanar@gmail.com>
Signed-off-by: Pranav Temkar <pranavtemkar@gmail.com>