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]
Oneplus 5,5t were launched with Nougat (API level 25), 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>
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Change-Id: If8c09fa1868f60a451ced9e094e5796e46545fc0
* Fix for hidl power stats errors.
- 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.
* There is zero reason to ever build without blobs. We've even seen
this situation with official builds from our servers. It's always
better for a build to fail than it is for it to produce something
that has no chance at working.
Change-Id: I4968795670c91f691e9ecdc0e4af62e16ba3a93a
* This seems to be wholly dead for legacy functionfs. Pour one out,
she led a great, yet short-lived, life.
This reverts commit 53fd5b0828.
This reverts commit 8b07abf736.
Change-Id: I494769c2106638d8e442f43dfedf399e7f90aa9e
Use the default software implementation of gatekeeper.
Change-Id: Id696752ad78047155cad6a5dafe7ca1b4fe86345
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
* libsec-ril*.so files need strdup8to16, which is is dropped in the API
30 library, but can be found in the API 29 prebuilt.
Change-Id: Iaa54b061048a00f832d18396a82212905af0fd7e
* libwvdrmengine.so needs _ZN6google8protobuf8internal13empty_string_E
which is dropped in the API 30 library, but can be found in the
API 29 prebuilt
Change-Id: I39e3251d53b14f3325282b12e6a6bf741ebcf63a
* Apparently this is now required on all non full treble devices since
google added a sleep(1) in libhidl...
Change-Id: I6d8492dd7c56bfdb2ca00f3477634a46fa55b1c0
* SE policies are imported and modified from
https://github.com/sonyxperiadev/device-sony-sepolicy.
Modifications are needed because qcom legacy policy
contains conflicting labels and rules.
Change-Id: Id04a824dea69976f6fc9d48bef77859cc82971ed
* Even though camera.device@3.4-external-impl still will look for the
file, this is seemingly no longer required in Q due to changes
elsewhere in the stack.
This reverts commit cf207232cb.
Change-Id: Ibd19f4d7abeafb7f4d8af1ca6226d6065058538c
* This config needs to be modified for legacy devices. As
there is no easy way to split it, import it into device
tree and bind mount it instead.
* Head at android-10.0.0_r2
(3ac371484399da6efbd0c835aa461d3326263ab1).
Change-Id: I8d5003d7cd3a471c569844aede4b5ea4c68ae36b
* We already set props via system.prop, so let's not mix
and match between that and PRODUCT_PROPERTY_OVERRIDES.
Change-Id: I92c6863b8393640e2239decd7f089ee890b3c7f7
* This fixes the following error on camera-in-mediaserver devices:
E CameraService_proxy: Calling UID: 1013 doesn't match expected camera service UID!
Change-Id: I185e34e8983b286436bfc0fe36cfdf260ef78170
* The external camera provider occupies our camera v4l2 nodes,
potentially crashing the kernel driver and blocking the camera HAL.
Unfortunately, there's no easy way to just disable it, so let's just
tell it to ignore the internal video devices.
Change-Id: I00c67de1b94a1f7eca1bf458d1d0e4de3507aa81
Signed-off-by: Daniel Jarai <jaraidaniel@gmail.com>
