Blurs on android12 are extremely janky, even with EXPENSIVE_RENDERING
raising GPU frequency.
W FrameTracker: Missed SF frame:1
W FrameTracker: Missed SF frame:4
W FrameTracker: Missed SF frame:68
W FrameTracker: Missed SF frame:68
W FrameTracker: Missed SF frame:65
...
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Those commands have moved to init.rc.
Bug: 170507876
Bug: 171740453
Test: build pass
Change-Id: Ib7acc0fd83adca37e247cd9f3113c1f117e5196e
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Quoting commit afc09932f6fa07c5f6beffbcdc2bb4691e527321 in
system/sepolicy [1]:
"Devices launching with R or eariler can this by setting following
under BoardConfig.mk"
It is impractical to replace every prop definition from qcom to
vendor_property_type for old platforms like SDM845, so relax the
enforcement to avoid triggering millions of neverallows.
ref:
[1] afc09932f6
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: Ie633ea788dab3389a3407ec9a461b5837befca46
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
(nuke whole vendor configs here)
* Without CodeAurora's modifications in frameworks/av, the vendor suffixed
media codecs configs are not parsed at all. Move select vendor additions
into the main files in order to enumerate support for hardware-backed
HEVC encoder.
/dev/cpu_dma_latency accepts values in either s32 or hex format,
so convert 67 (dec) to 43 (hex).
sdm845-common comment:
I assume Google meant to set cpu dma latency to 44 in decimal
rather than hex because 44 is the lowest valid latency value for
C3 LPM state, according to qcom,latency-us in sdm845-pm.dtsi.
The pm qos request is only active when the fd is kept open, so
the dummy value of 100 does not really matter. Keep it as is.
Test: hexdump -C /dev/cpu_dma_latency
00000000 2c 00 00 00 |,...|
00000004
Test: kernel pr_err() in pm_qos_power_write() before
pm_qos_update_request()
Inspired by Artem's commit "qos: Workaround for faulty libperfmgr
config".
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Enable 64 bit compilation for DRM plugins.
This will generate DRM plugins, HALs & oemcrypto_test in 64 bit.
Change-Id: I451db39edea3446d9816fcaba77caa8d3b097afb
libdisplayconfig was replaced by libdisplayconfig.qti on R. While
we are at it, build vendor.disiplay.config@1.0.vendor as well so
that QSEECOMD is happy.
E QSEECOMD: : Init dlopen(libsecureui.so, RLTD_NOW) is failed.... dlopen failed: library "vendor.display.config@1.0.so" not found: needed by /vendor/lib64/libsecureui.so in namespace (default)
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Common config.fs/$TARGET_FS_CONFIG_GEN AID/fs configuration
file for all chipset inheriting from base.mk.
Since legacy device-specific android_filesystem_config.h and
config.fs do not co-exist, temporarily include config.fs only
if legacy file is absent. Once all legacy, device-specific
files have been deleted, config.fs can be made unconditional.
Change-Id: Ie100d0cd9db808b82d99be7139f0709390c7f3a2
* vendor_init isn't allowed to create files under system_data_file
context, leading to early init panic.
Change-Id: Ie344cc4ece2783bb7d372f64c2c23b4d5ea2cda0
