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)
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: I12751f1d037ee9de477285a56bc411f9c6085752
After USB enumeration, some SD card readers do not send signals to the
device when the SD card is inserted or removed.
To support SD card hotplugging, this patch enables in-kernel
media-presence polling, which will check the SD card status every 2
seconds after a SD card reader is attached.
Bug: 186479576
Test: SD card insertion/removal and data copy (see b/301566595)
Change-Id: I29c352696cd9d31168a8eac8c58d23adb484f5d0
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
am skip reason: Merged-In I7a1fec0331c5bddabd4f9edabcfda9b137f7a452 with SHA-1 7f9f6cac0b is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2865149
Change-Id: Ib957f8b989a6b4bc06355a7a2edbdf4f6184fe81
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Icf6128476f1f669918bc20d3eecd40c89893443f with SHA-1 9278e0c263 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101-sepolicy/+/2865760
Change-Id: Id33e5a1b2f4bf66182fff901edc98d0e783a38ca
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I7a1fec0331c5bddabd4f9edabcfda9b137f7a452 with SHA-1 7f9f6cac0b is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2865149
Change-Id: Ia9d7abe61db0f878fae42ac3d54398c1565fbdf2
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Icf6128476f1f669918bc20d3eecd40c89893443f with SHA-1 9278e0c263 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101-sepolicy/+/2865760
Change-Id: I976a0db1da02934ee283984f69981bba537de3d4
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I7a1fec0331c5bddabd4f9edabcfda9b137f7a452 with SHA-1 7f9f6cac0b is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2865149
Change-Id: Ife929c160acf3251b7fd850fffcdbc979ba85351
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Icf6128476f1f669918bc20d3eecd40c89893443f with SHA-1 9278e0c263 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101-sepolicy/+/2865760
Change-Id: Iae3de3a1ce50d4a45f2a7170ced3203e0494fc26
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
