This property was removed and is not being used anymore. So
modem_svc will not need to read it.
Bug: 316816342
Change-Id: I9fe6002e34f7dd5fea0371d41d417c778c3d0905
Signed-off-by: Mahesh Kallelil <kallelil@google.com>
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
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: I08a9ce89155324b0ac749bde4a9d205585a57320
Signed-off-by: wenchangliu <wenchangliu@google.com>
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
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: Ibd7816b717d2fbcb038a7c0ff703b7fab7d2a46c
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
am skip reason: Merged-In I484f4446b915cad1347dd065f2539cc12c75beec with SHA-1 e8cf7e19a1 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201/+/2863573
Change-Id: I5e8c5e70ff6b013d65d04ca84a1b6c92bd646bc2
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I8ee515e5ae5498296342d1f432ba9fa5716f221d with SHA-1 3dbfb9e35f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201-sepolicy/+/2866361
Change-Id: I2dfdcd71b09693fc3e9f6de7f3c376b94ee43846
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I484f4446b915cad1347dd065f2539cc12c75beec with SHA-1 e8cf7e19a1 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201/+/2863573
Change-Id: I2b868ab3e8999174c3415cb28f2ad7a72f0729b6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I8ee515e5ae5498296342d1f432ba9fa5716f221d with SHA-1 3dbfb9e35f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201-sepolicy/+/2866361
Change-Id: If5980ad15bebe1ae2b83e8ea8971044658c1cbd8
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I484f4446b915cad1347dd065f2539cc12c75beec with SHA-1 e8cf7e19a1 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201/+/2863573
Change-Id: I0a0102fc588322a247feaa366a600807de6f8aac
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I8ee515e5ae5498296342d1f432ba9fa5716f221d with SHA-1 3dbfb9e35f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs201-sepolicy/+/2866361
Change-Id: Iee7d406102b238debd416fed74724025a032c946
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
