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
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
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 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 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>
Migrate the usb data session event functions to the class with the
following additional functionalities;
- Support detecting gadget soft pulldown (usually done during configfs
function switch) and report usb data session correctly.
- Support reporting usb data compliance warnings to the class USB
by providing getDataComplianceWarnings call.
- Use boot_clock instead of steady_clock to measure time correctly in
the case of system suspend.
UsbDataSessionMonitor is self-contained and can be migrated to pixel usb
library after feature maturation.
Bug: 297224564
Bug: 296119135
Test: usb data session upload in device and host mode
Change-Id: Iba001933e193935d64cf5fd0a1257d02a4274fb1
(cherry picked from commit ea65ca11f6fbb6f13b89ef9ed03015f47ec1cedb)
c2.android.av1-dav1d.decoder is based on dav1d implementation.
This dav1d-based sw av1 decoder provides better decoding throughput
than the default gav1-based av1 decoder on mid-to-low-tier devices.
c2.android.av1.decoder will be deprecate eventually before that we keep
both decoders.
Bug: 309412792
Test: run cts -m CtsMediaDecoderTestCases -t android.media.decoder.cts.VideoDecoderPerfTest --module-arg CtsMediaDecoderTestCases:instrumentation-arg:codec-prefix:=c2.android.av1.decoder
Change-Id: I0d2d7e8727452d4c6dd64a45c22be5463cf21571
The license declaration can't be handled in Android.bp currently.
So keep them in Android.bp.
Bug: 310058310
Test: NA
Change-Id: I3e25fa07f6b3e1bffaf585d69e342c651b50f6ef
Report COMPLIANCE_WARNING_INPUT_POWER_LIMITED instead of
COMPLIANCE_WARNING_OTHER to flag incompatible chargers. The underlying
logic that generates the warning remains the same, what's changed is
the enum that's being used.
The purpose of the change is to have a warning type that better
represents what actually happens and free up COMPLIANCE_WARNING_OTHER
that was intended to act as a fallback reason code.
The flag enable_input_power_limited_warning controls whether to switch
to the new enum, while the flag enable_usb_data_compliance_warning
controls the new enums that are added as FlaggedApi in the framework.
Both flags need to be on to enable the change.
Bug: 308700954
Test: manual tests with local flag override
Change-Id: I6595706d1b83d533fc2d3e29086773270e045ede
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I1f546f53b63b7db94cd7443650688027c61e185b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I254534a8ec4b951fdc7a5aa8d731f84dda03e900
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: Ia2839d3e016de4ee45b4323a790ad42abb48c0d6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I5bbe3a94b51939ec0d8050ef32292ec1fb8020ab
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
