We are interested in tuning these as well.
Label them under u:object_r:proc_dirty:s0.
Change-Id: I21868ea3952ace1e33c593515c56e5fe7aea1353
Signed-off-by: Juhyung Park <qkrwngud825@gmail.com>
- Fix --no-tags argument.
- Remove --no-clone-bundle. Qualcomm no longer recommends
this since migrating from CAF to CLO.
- Remove handling of separate CLO remotes since
we now just have one: clo-la.
Change-Id: Ib9026a5850f658903e6e9717ecec347fc1cdd17f
Device prefix must be _ not -, otherwise
the build system thinks aospa is the target.
In file included from build/make/core/config.mk:356:
In file included from build/make/core/envsetup.mk:354:
vendor/aospa/products/AndroidProducts.mk:54: error: COMMON_LUNCH_CHOICES contains products(s) not defined in this file: aospa.
Change-Id: I08c537f3a5edfeea700acee03ea50b6f00866750
- By default LLVM Support is set to true unless GCC flag is set to true.
Change-Id: I5eb8b2d29c1c818ab6011abe809494b0b80707f0
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
[rdxzv: Rebrand to AOSPA and move to blueprint]
Change-Id: I362c75a9a9456bb4d7ffe12072b1b2ef1ea49dac
Change-Id: I9a29203af8721ec105a40849f0814ef109abc08e
If the device only have 60 and 120 Hz in the config group, 60 Hz won't be
used when watching a 24 fps video and instead 120 Hz will be used because
it is perfectly divisible by 24.
This is a publicly documented AOSP behavior [1], but it simply does not
make any practical sense and trades off significant amount of power for a
very-hard-to-notice jitter-free experience.
Set debug.sf.frame_rate_multiple_threshold to 60 by default to limit this
behavior to 60 or lower fps.
[1] https://source.android.com/devices/graphics/multiple-refresh-rate
Change-Id: I66353abc46ad16e63b2c9188794469ad71f2192e
Signed-off-by: Juhyung Park <qkrwngud825@gmail.com>
Co-authored-by: Christian Oder <myself5@carbonrom.org>
Co-authored-by: SpiritCroc <spiritcroc@gmail.com>
Change-Id: I0a4a3510c8e0c4603fa334a3db4165c8b1e927dc
Label sysfs node as vendor_sysfs_dc_dim in device tree
Signed-off-by: rituj <ritujbeniwal@gmail.com>
Change-Id: Ic50a616037dc744943ca1a7c04c506827ef50526
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
* Users reported that CLO lmkd is too aggresive compared to aosp, so for now use what's the best.
Change-Id: I36134aefaa9a4200b757ac1861b11af2379f2ad6
Signed-off-by: Jprimero15 <jprimero155@gmail.com>
* Recently we switched to LA.VENDOR.13.2.0.r1(KAILUA.QSSI14.0) tag on vendor and for mi439 devices, it broke wifi,hotspot and usb so for now revert to working tag which is LA.VENDOR.1.0.r1 (WAIPIO.QSSI13.0) until we get a proper fix.
Change-Id: I75a3da89b121550f34d3496c46b01c9bf994a45b
Signed-off-by: Jprimero15 <jprimero155@gmail.com>
[1] - There are some changes between 9.15 and 9.16. So we'll use something specific to bengal.
Change-Id: Ie0950dcd0f0dc2655ecb7663520bbd996b218af6
Signed-off-by: chrisl7 <wandersonrodriguesf1@gmail.com>
KERNEL_OBJ directory was just a symlink to this directory.
Hence, on installclean, KERNEL_OBJ was getting wiped while
kernel directory was still there in out. On running the build,
this symlink gets recreated. Since it matches the previous
condition of the directory, the build doesn't consider
rebuilding the kernel.
• This commit does address the issue at [1].
Reference:
[1] https://gerrit.aospa.co/c/AOSPA/android_build_soong/+/26101
Change-Id: Idbd998de19f2a634cc9d9c93ccb921bb00d41718
* update kernel path while we're at it
and fix some typos
Change-Id: Ib7da277cfa5f132be72161471a88843e2e008399
Signed-off-by: BladeRunner-A2C <prisoner56898@protonmail.com>