The new framework implementation derives capture buffer loss
notification from other information, and treats HAL notify() with
ERROR_BUFFER as no-op.
Test: Build
Bug: 155353799
Change-Id: Ia7ea52ee2750c7404b657467e1cfda4c05e6cc78
- Add documentation about giving hints to camera HAL about concurrent
operation before configuring sessions
- Limitations on ZOOM_RATIO_RANGE during concurrent operation.
Bug: 151891611
Test: builds
Change-Id: I79d0bd8be1ed9aa29a1ba080d01833f16eff580c
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
Clarify behaviour of the following ops in the case when inputs would
cause an output to have an empty shape:
* MEAN
* ARGMIN/ARGMAX
* STRIDED_SLICE
Bug: 155508675
Bug: 155660285
Bug: 155508675
Bug: 155238914
Test: VtsHalNeuralnetworksV1_3TargetTest
Change-Id: I92d1c3866a462a99b4eed7782b72f62bb6a076c6
Merged-In: I92d1c3866a462a99b4eed7782b72f62bb6a076c6
(cherry picked from commit d4bba83f6a)
Add a clarification on the behaviour of REDUCE_* ops when all dimensions
of an input tensor are reduced.
Bug: 155508675
Test: VtsHalNeuralnetworksV1_3TargetTest
Change-Id: I3a67225c3af80af40a11362ca5d0f55350cbfa05
Merged-In: I3a67225c3af80af40a11362ca5d0f55350cbfa05
(cherry picked from commit eec7d86b44)
Existing definition was inconsistent, so update it to be consistent
and match what implementations have actually done.
Test: Builds
Bug: 150331548
Change-Id: I5dfbe7c802bf4ac98f0c5556d5ac3af5d79cff7a
Clarify behaviour of the following ops in the case when inputs would
cause an output to have an empty shape:
* MEAN
* ARGMIN/ARGMAX
* STRIDED_SLICE
Bug: 155508675
Bug: 155660285
Bug: 155508675
Bug: 155238914
Test: VtsHalNeuralnetworksV1_3TargetTest
Change-Id: I92d1c3866a462a99b4eed7782b72f62bb6a076c6
Add a clarification on the behaviour of REDUCE_* ops when all dimensions
of an input tensor are reduced.
Bug: 155508675
Test: VtsHalNeuralnetworksV1_3TargetTest
Change-Id: I3a67225c3af80af40a11362ca5d0f55350cbfa05
This was caught by R process, but due to a bug in hidl-gen, not
enforced.
Bug: 155593324
Test: build checks hash
Merged-In: Ied59b4ba94c8b6bb9e3ead869d8341cffa86f1e8
Change-Id: I2bf135bb10ad052bcfe4d8f2035ed8368d5ea9ac
Update comments only for IStreamOutEventCallback::onCodecFormatChanged
Test: compiles, this is a comment change only.
Bug: 150175043
Change-Id: I1895c737997fbf3cb509b4078b545658d11df198
Also removed the hash check on Vehicle HAL files, as they're still being
worked on.
Test: m
Bug: 15249991
Change-Id: I214ebc9b5bbd71e5db1a1332296ceb4e426c50cf
Since it was a big problem for little gain, we are reverting back to the
old practice of waiting to freeze interfaces for release.
vts_treble_vintf_*_test no longer checks hashes in non-release branches.
Bug: 144366823
Test: N/A
Change-Id: I147025ffed053bc583055fbc4f39d9823e793c22
AudioFocusChange is expected to have negative values, but was originally
defined to be an unsigned int.
Bug: 153090512
Test: make -j
Change-Id: I27cd8134f9fe19fbefc788e5c2498947dc52967e
The way I planned for this to work doesn't work. We'll revisit in
Keymaster5. For now, removing IOperation and beginOp.
Test: Build & boot
Merged-In: I017d17079380cc3bacc6f05b2486e1b6e6c3f675
Change-Id: I017d17079380cc3bacc6f05b2486e1b6e6c3f675
This change introduces a new API to import frame capture buffers
allocated by the clients.
Bug: 152493110
Test: m -j and run /system/bin/evs_app --test --extmem
Change-Id: I679c61719e4d0e3a7d0c41110afe66e0a4ccb305
Adding these now, with a note that AIDL interfaces should be preserved,
to avoid some merge conflicts.
Bug: 147496715
Test: N/A
Change-Id: I67f6c5d583b853516c7203edb77f3c5fa841863b
(cherry picked from commit e6c11c9407)
Merged-In: I67f6c5d583b853516c7203edb77f3c5fa841863b
Adding these now, with a note that AIDL interfaces should be preserved,
to avoid some merge conflicts.
Bug: 147496715
Test: N/A
Change-Id: I67f6c5d583b853516c7203edb77f3c5fa841863b
The way I planned for this to work doesn't work. We'll revisit in
Keymaster5. For now, removing IOperation and beginOp.
Bug: 152536287
Test: Build & boot
Change-Id: I017d17079380cc3bacc6f05b2486e1b6e6c3f675
This reverts commit 7b8a5c99d6.
Reason for revert: this interface is untested in R.
Bug: 151331855
Change-Id: I6e0f8096a1c9c02936d7f3fcc247566f80b37648
It does not exist.
Fixes: 151954406
Test: aosp-changes-report no longer shows identity as being incorrectly
added
Change-Id: I878f8719175188c718d249251d051ff616def891
- Rename recieverInterSignalBiasNs into interSignalBiasNs, which refers
to the sum of receiver ISB and satellite ISB.
Bug: 150724332
Test: atest VtsHalGnssV2_1TargetTest
Change-Id: Ifae15cb482bc12e793a481fec7847c817ef3c34d
Bug: 148102466
Test: compilation for both cuttlefish and sargo
Merged-In: I8a8e734011909b038c0d735c2bfde7ea773b71e6
Change-Id: I8a8e734011909b038c0d735c2bfde7ea773b71e6
(cherry picked from commit 24c3416b4f)
Add CellIdentity to getBarringInfoResponse to make
the req/resp method match the existing indication.
The CellIdentity is used to prevent races where
barring is attributed to the wrong cell based on the
timing of separate polled or unsolicited inputs to
the framework.
Because the CellIdentity is already in IRadioIndication
the information to provide CID with BarringInfo is already
present and available. This just makes the unsol and the
polled APIs match.
Matching indication is IRadioIndication@1.5::barringInfoChanged
Bug: 148992393
Test: make && VtsHalRadioV1_5TargetTest
Merged-In: I74e6ab9ca9e0dd49846af774fd73773ff3737df7
Change-Id: I74e6ab9ca9e0dd49846af774fd73773ff3737df7
(cherry picked from commit 6894f89fd8)
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: 143683647
Change-Id: If08741f0ea156a5c2656a47e46f7e1f98bf54ec4
Merged-In: If08741f0ea156a5c2656a47e46f7e1f98bf54ec4
Prior to this CL, the NNAPI QoS deadline is a strict deadline: a task
with a deadline must either complete or abort by the deadline. To
avoid as much overhead as possible, it is requested for Android R to
have a relaxed deadline, where the task *may* be aborted after the
deadline has passed or when the task is estimated to take too long.
Because the deadline is now relaxed, the querying method
IDevice::supportsDeadlines can be removed.
Bug: 149766387
Test: mma
Test: VtsHalNeuralnetworksV1_3TargetTest
Change-Id: Ib9937b5bb95646c2fd82e1aa17f2b0b639e2c420
Merged-In: Ib9937b5bb95646c2fd82e1aa17f2b0b639e2c420
(cherry picked from commit 9b9a804fe4)
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)
This reverts commit b071f8ae53.
Reason for revert: Change will not be supported by vendor, so HAL for RadioConfig is no longer necessary.
Change-Id: I33bf652c6aa2f8516ee6ec1c462a1a575d2a5d27
Merged-In: I2eb83fd2356134ef45a782d99174fdd65f8c5a13
This reverts commit e1d1b0b92c.
Reason for revert: Change not supported by vendor
Change-Id: I5e2cdf0797124e0a1d272ca4b0525d2425954c3f
Merged-In: I9b268f41614149b5cd55caf3d730b25bb1f885e9
This reverts commit f0cfc3ef60.
Reason for revert: Change not supported by vendor
Change-Id: Ie148208a890834b0cd05b0ae4d6190e1a0b5dede
Merged-In: Ief5c5325f51a9bb3921bd2eb6e0ea8c9e7111581
Add to IRadio, IRadioResponse, and VTS
Test: make cf_x86_phone-userdebug && mm
Bug: 149112073
Change-Id: I330d5be6bf531c93439f8f1d55718f71ec46c1c3
Merged-In: I330d5be6bf531c93439f8f1d55718f71ec46c1c3
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