`Liboemservice_proxy` was originally included as a part of the build
target for DMD, which meant that the binder aidl declaration had to be
done on all devices that used DMD (all Lassen devices), even if they
didn't use the service. `Liboemservice_proxy` has now been decoupled
from DMD so it only needs to be included on our target devices now. This
CL removes the outdated service definitions.
Test: Build gs101 and ensure it still builds.
Bug: 321867236
Change-Id: Iefd8a4e563c41ffc5221810e3fb042dbe4a3e733
Need to disable stripping the vendor_dlkm modules to retain the GKI
modules' signature. Fortunately, the kernel build strips the modules for
us.
Bug: 290274601
Bug: 322457552
Change-Id: I4c8ff2196d062dc65a1f707a738f78bc8bfda704
Signed-off-by: Robin Peng <robinpeng@google.com>
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: I73a3db45cb58a228ac68408468923101d79322b8
Setting the owner of /dev/logbuffer_cpif as system to allow the
dump_modem script to read the logs as part of bugreport
Test: Tested bugreport on device
Bug: 305600375
Change-Id: I20c1a843edadbc4ed2da51af3e242957b5849d6b
Signed-off-by: Mahesh Kallelil <kallelil@google.com>
0a894f5d0d
Reverting to comply with the Allocator VTS for 24Q1, do not merge to main.
Bug: 310046460
Test: VtsHalGraphicsAllocatorAidl_TargetTest
Change-Id: I57a9dc98122f312ad98dacbab343d7eb98700cec
The cpif logbuffer did not have the right context and was
missing as part of the bugreport.
Test: Tested bugreport on device
Bug: 305600375
Change-Id: I2101037d0044e706969f2582e29f923ae029458b
Signed-off-by: Mahesh Kallelil <kallelil@google.com>
Dump flag value in the construtor for easier debugging. Feature flags
are not expected to change in runtime, dumping the value once should
be enough.
Bug: 296119135
Test: manual test
Change-Id: Ie5aca2dff23e59704fb306833cde0e592b9f430d
(cherry picked from commit 9164eae7cdee032381d8bf045fbbed33f62b00bf)
- Include mediacodec_samsung setting from gs-common
- Enable Codec2 HIDL 1.2 from BoardConfig and update
manifest hidl version for samsung.hardware.media.c2
Bug: 318793681
Test: run cts -m CtsMediaDecoderTestCases
Test: run cts -m CtsMediaPlayerTestCases
Test: run vts -m vts_treble_vintf_vendor_test
Change-Id: I5679bee76ca0ff7f430797ed261069e0f7fc3937
remove mediacodec_samsung sepolicy in legacy path since we will include it from gs-common.
Bug: 318793681
Test: build pass, camera record, youtube
Change-Id: Idc0e19348d1e113e95305279aebbbaf82c79d730
The state count requirement is very specific to the case where the
signal integrity is the culprit of flaky connection. However,
there could be other cases such as bad receptacles causing data pins
to disconnect randomly.
Remove the state count requirement to cover more cases.
Bug: 296119135
Test: manually trigger the warnings
Change-Id: Ic2ae376ad6062d9930614381503f44e4a5ac760f
(cherry picked from commit 5e14ba01be9acc31d3df0f506b4287eea0bf9583)
Support flagging enum failure and flaky connection in device mode,
flagging enum failure and missing data lines in host mode.
No warning would be flagged until 5 secs after the data session
starts to give ample time for the connection to stabilize, a timer
is added to support it.
Bug: 296119135
Test: manually trigger the warnings
Change-Id: I25f08657e328913946add192b5ecb9ee50c3a1a8
(cherry picked from commit 42020dc4585442bd7ca88f183ba29a18834af197)