config_satellite_nb_iot_inactivity_timeout_millis
extend to 15-min as per POR mentioned in b/323211209#comment7
config_datagram_wait_for_connected_state_timeout_millis
extend to 15-min to improve sending at intermittent cellular scan
Bug: 323211209
Bug: 323301557
Test: make
Change-Id: Icf3a2ca4b62d65db7812e32669befeffa08f556a
We need to set sysprops debug.sf.hwc_hotplug_error_via_neg_vsync and
debug.sf.hwc_hdcp_via_neg_vsync on zumapro devices so SurfaceFlinger
would properly handle specially-crafted onVsync calls with negative
parameter values that HWC makes to pass hotplug error info and HDCP
status info.
Bug: 324953626
Test: tested DisplayPort error propagation
Change-Id: Ice36756154a9091419a41019dc51b187205e9187
DisplayPort kernel driver passes error code/status to hardware composer
via the dp_hotplug_error_code sysfs file. When HWC receives/consumes
the error, it will write "0" into that file to reset the error code. So
this file must be readable and writable by the HWC code running with
"system" user/group permissions.
Bug: 324953626
Test: checked that SYSFS dp_hotplug_error_code has correct permissions
Change-Id: Idb7d44f8e9f22fc61e8df432aa72281daddb15ef
Make the EdgeTPU targets defined in <soc>/proprietary visible by product packages included in edgetpu.mk.
Bug: 323601370
Tested:
No functionality change. Edgetpu services still work.
Change-Id: Ia8846b929b21e9fbcfd1f091779c57d4fed3da0b
Enable dynamic color mode to reduce the power overhead of color space
conversion when GPU composition exists.
Bug: 315787778
Test: check "dumpsys SurfaceFlinger" and state of display color service
when playing SDR/HDR video
Change-Id: Ie9e87091385ab5247141bf956fbaba3275cc6811
i2c paths for 5.15 and 6.1 kernels are statically assigned,
so delete variations that do not exist from init rc file.
Depending on the device either i2c bus 6 or 11 are used, so
create permissions for both in separate init rc files.
Put the correct rc file to the vendor partition based on
target product.
Test: Manual test on device. Confirm that file reads related to
file path error do not trigger error.
Bug: 318820040
Change-Id: I4cb67bcbba99ef32a5ddfb2487b92ee196563b90
Signed-off-by: RD Babiera <rdbabiera@google.com>
The paths of sysfs nodes are different across kernel versions
and i2c bus assignement. Runtime search the correct ones.
Test: Manual test on device. Confirm that file reads related to
file path error do not trigger error.
Bug: 318820040
Change-Id: I1217fcea012865cebe12c935917f12903003fd5b
(ported from commit 0b768c8fbe1e59a4b9efa7b5f7b6a017a81d46fb)
Signed-off-by: RD Babiera <rdbabiera@google.com>
1. Update media_codecs_performance_c2.xml from zuma
2. fine tune value for c2.exynos.vp9.encoder 3840x2160
Bug: 321187030
Test: run cts -m CtsVideoTestCases
Change-Id: I4b943f5c134e26f352cc5e14d837ba50347baa32
SE policies are already there. Probably policies were copied properly
from the previous project but device files were not.
Bug: 321899122
Test: `adb shell dumpsys meminfo surfaceflinger` shows data for graphics
Change-Id: I72deafef9e2b6c49360f73ef4c71642dddd2e2f8
It is useful to know the PCIe LTSSM state residencies in various
scenarios. The pcie binary that provides this is availaable in factory
builds. This change also makes it available for eng and userdebug builds.
Bug: 322357593
Change-Id: I5a8513063f232124a82f81ecc2a5e2e6d84d7459
Signed-off-by: Sajid Dalvi <sdalvi@google.com>
This is already the default, so no need to set via sysprop. Moving
forward, we will set this using flags, unless a particular category
of device needs to override the flag.
Bug: 293371537
Test: NA
Change-Id: I6b149c2ee198a28a306540f4670edaa560533f48
c2.android.av1-dav1d.decoder performance has been improved with CL
"C2SoftDav1dDec: Fix performance issues in frame parallel multi-threading"
More detail in b/315828433
Bug: 315828433
Test: run cts -m CtsMediaDecoderTestCases -a arm64-v8a -t android.media.decoder.cts.VideoDecoderPerfTest --module-arg CtsMediaDecoderTestCases:instrumentation-arg:codec-prefix:=c2.android.av1-dav1d.decoder
Change-Id: Ie2aaccc9f89127b2d9e11e7ddb71455f6d75b50c
Previously, `Liboemservice_proxy` was included as a part of DMD, and so
didn't need to be included on its own. However, since these two have
been decoupled, we need to explicitly include the build target here for
it to execute on device.
Test: Build and check logs to ensure service starts up on boot
Bug: 321867236
Change-Id: I9a03a5f7dffc91e4760472a79d510e23eacca564
