The sysfs paths in the rc file differ across kernel versions or build
targets. Given that the path is static in the newer kernels (6.1+),
modify the paths for newer kernels in the original rc file and create
another rc file for older kernels (i.e kernel 5.10). Put the correct rc
file to the vendor partition based on kernel versions.
Bug: 317946158
Change-Id: Ie313664ee14c837bc9f33113e9341f6e06192401
Signed-off-by: Kyle Tso <kyletso@google.com>
The paths of sysfs nodes are different on multiple build targets and are
also different between the old kernel (5.10) and newer kernel (6.1).
Since usb HAL code is shared by those targets and different kernel
versions, Runtime search the correct paths.
Bug: 317946158
Change-Id: I676455145232fd71db1578bb7a9801fed7bb327f
Signed-off-by: Kyle Tso <kyletso@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: Id05d31e3c058d3bfe961d90e37a0c6992d823605
`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: I7fb10e4013da59f42cff47da6d104deed9b4bb71
assign system_dlkm.modules.blocklist to BOARD_SYSTEM_KERNEL_MODULES_BLOCKLIST_FILE
located from kernel prebuilts folder
Bug: 267429528
Bug: 322457552
Change-Id: I912f1a8e0df12e4614c74b870921ca0b47b8383e
Signed-off-by: Robin Peng <robinpeng@google.com>
- BOARD_SYSTEM_KERNEL_MODULES_LOAD is for GKI modules
- BOARD_VENDOR_KERNEL_RAMDISK_KERNEL_MODULES_LOAD should not contains GKI modules
Bug: 267429528
Bug: 322457552
Change-Id: Ib5da01f861a34edec07e2a958f153c876e5cef10
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: If4912322095ec112507c2e7f37e5bc1506d8c17a
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: Ic7c64f942985596d9a5d919dfd3ca2127de881d0
Signed-off-by: Mahesh Kallelil <kallelil@google.com>
4217a458ba
Reverting to comply with the Allocator VTS for 24Q1, do not merge to main.
Bug: 310046460
Test: VtsHalGraphicsAllocatorAidl_TargetTest
Change-Id: I322cdf9452a80e5da87f1808b324ac2e499fe9cd
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: I1f947d2eb75bd4d75d9db1d39b0b083d32f8032f
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
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
The versions were originally not specified in the device manifest and
compatibility matrices. This is changed here to fix the broken vts
tests.
Bug: 310109332
Test: atest vts_treble_vintf_vendor_test -- --abi arm64-v8a
Change-Id: Ib2baeda6a3c81c701e6f813b6c88f561b158e674
