It should belong to the default /misc implementation of boot control
1.1. Right now, the library as well as the bootloader_message_ab
are only used by cuttlefish. So move it over to reduce the confusion
in libbootloader_message.
Bug: 131775112
Test: build
Change-Id: I599678bf90d19718de811b9e34d82cf8fe1571a4
(cherry picked from commit c971ea8d5d)
Sync fences can be invalid if the buffer is already ready. If the
fence is invalid, we do not need to wait.
Test: VtsHalGraphicsMapperV4_0
Bug: 150213134
Change-Id: I8326d5f8b358c466ee9a686fd299daed1d4b4aa8
RAW12 and RAW16 buffers need a PlaneLayoutComponentType. Add a RAW
type so vendors don't have to add private RAW types.
Test: VtsHalGraphicsMapperV4_0
Bug: 149869426
Change-Id: Idf1fa609e3a1506c3c87af22d4c548cf1218fad1
std::optional defaults to containing std::nullopt_t. Using "->" or
"." on an std::optional object that does not contain a value is
undefined. Clang seems to ignore the whole line.
SetSmpte2086 and SetCta861_3 both incorrectly instantiate their
std::optional types. The std::optional types contain std::nullopt_t
when they are passed into encode. When mapper decodes the fields,
they are empty.
Update std::optionals to be instantiated correctly.
Bug: 149931805
Test: VtsHalGraphicsMapperV4_0
Change-Id: I046242f8261a5378228231b89b2eedec242667cb
The parameter order of a couple checks is wrong.
For example:
EXPECT_GT(val1, val2) is EXPECT_TRUE(val1 > val2)
so EXPECT_GT(0, X) can never be true.
Update the tests to be correct.
Test: VtsHalGraphicsMapperV4_0
Bug: 149739702
Change-Id: I21070a912b6014acc5feb63b6b19912b45fe8f5f
The callback is targeted for events related to an output stream.
Currently, there is one callback event defined, which is codec
format changed event.
Bug: 133526565
Test: manual
Test: atest VtsHalAudioV6_0TargetTest
Change-Id: I73a4914c1ffc30e1c88b8fedd61a031e24a069f6
Test: no regression with offloaded Play Music
Bug: 133526565
Merged-In: Ie655a96503be5a4ad1660d4b2183b01e514452fd
Change-Id: Ie655a96503be5a4ad1660d4b2183b01e514452fd
(cherry picked from commit c91b679ac1)
Bad merge conflict resolution when removing IRadioConfig 1.3
Bug: 149522248
Test: mm cf_x86_phone-userdebug
Change-Id: I055b94a2bf275d9ed5ecff6f271e8204e6ee7c0b
There were some questions on how the new IRadio 1.5 setRadioPower
command should be implemented based on vendor feedback. This CL
clarifies this behavior.
Test: manual
Bug: 143683674
Bug: 147496715
Merged-In: If08741f0ea156a5c2656a47e46f7e1f98bf54ec4
Change-Id: If08741f0ea156a5c2656a47e46f7e1f98bf54ec4
(cherry picked from commit 0eac27ccf3)
am skip reason: Change-Id Ib71ce43e9168d82fd9ee0564db813c5a3538c459 with SHA-1 09c8b5ba59 is in history
Change-Id: I53f6db496bf54998202fa61e2ca35c900608ad11
Add a test that starts the dialog with some Confirmation strings that
need to be supported to provide portability guarantees.
Bug: 149954317
Test: VtsHalConfirmationUIV1_0TargetTest
Change-Id: Ie6961848d41b7d23d13b85702330682c755a9bbc
Pixel has been dumping some non-sensitive information in bug reports
using IDumpstateDevice for a long time, and requiring nothing to be
dumped on user builds by default suddenly changes behavior.
To account for this use case, we instead change the meaning of the
toggle to control *verbose* logging, specifically anything with privacy,
storage, or battery impact.
VTS tests are updated appropriately.
Bug: 143183758
Bug: 143184495
Test: atest VtsHalDumpstateV1_1TargetTest
Change-Id: Ib71ce43e9168d82fd9ee0564db813c5a3538c459
Merged-In: Ib71ce43e9168d82fd9ee0564db813c5a3538c459
(cherry picked from commit 09c8b5ba59)
Playback rate parameters allow changing the playback speed
of audio streams optionally preserving the pitch (this is
often referred to as "timestretch"). HALs can apply these
parameters when decoding of streams is done in hardware.
Bug: 133526565
Test: atest VtsHalAudioV6_0TargetTest
Change-Id: Ie78cd924bd034b57bf5b6a74affd62641ffc0aba
