These are no longer used by EventHub, and should not be carried forward.
Bug: 116601048
Test: presubmit only
Merged-In: I35129484d9945dcd4d291e0f2fac894e07c53c04
Change-Id: I35129484d9945dcd4d291e0f2fac894e07c53c04
The include path was needed because libnbaio_mono was missing
an include export for libaudioutils headers.
Test: make
Change-Id: I6d6aa2826ed259b682e8a417557fb6fdfb3caea6
am: 3f9c4488b0 -s ours
am skip reason: change_id I4391e73874e502da5000b1746436fb61bb2fe869 with SHA1 5b78d41954 is in history
Change-Id: I73f2efbafa48435e0e3bea31a96732af4e317632
am: 3e4de69cbf -s ours
am skip reason: change_id I4391e73874e502da5000b1746436fb61bb2fe869 with SHA1 5b78d41954 is in history
Change-Id: I0df6d6ff6a4f8f5662cf6ce511e0460c53326ec6
Force mono pipe shutdown when all input stream clients are closed
so that a pending write is not stuck waiting for available buffer.
Bug: 119057550
Test: abort search on BLE remote
Merged-In: I4391e73874e502da5000b1746436fb61bb2fe869
Change-Id: I4391e73874e502da5000b1746436fb61bb2fe869
This change removes libBionicGtestMain from the dependency of
camera.v4l2_test target.
Bug: 134488555
Change-Id: Ia719f770b03fa1679bb9467f58806e64b05eb469
Signed-off-by: Changyeon Jo <changyeon@google.com>
Since rework of presentationTimestamp in AudioFlinger, it is expecting
to drain correctly before stopping an output.
When a MIX RECORDER is set,
1/ Dynamic Policy Mix is registered
2/ Extraction Sink Port is made available
3/ Player is started on this sink
4/ Extraction source port is connected upon start Output
4/ Capture may be launched on the source to be rerouted
5/ All Capture are stopped, player is stopped
6/ Extraction source port shall be disconnected on stopOutput
Step 6 does not happen as the track is never set as drained.
Upon capture stop, rxSink MonoPipe is put in shutdown state. Any further
write will discard the buffer. However, frames written shall be
incremented of these frame discarded to be able to set the track as
drained.
This CL fixes this issue.
Test: AudioPolicyEmulatorTests --gtest_filter=RecordInjectionSourceMatch/DynamicPolicyMixRecordInjectionTest.RecordingInjection/*
Bug: 130356101
Change-Id: I861c4867991da8bcc1090be56d64e69646d58dc2
Signed-off-by: François Gaffie <francois.gaffie@renault.com>
Brightness is already a per display capability, we don't need this API.
BUG: 130313275
Test: build
Change-Id: If1ddf2a6224c9aa86f250178fc5cae3b01334b57
This was added in KM4, but didn't make it into this header.
Additionally, KM_TAG_UNLOCKED_DEVICE_REQUIRED was squatting on
KM_TRUSTED_CONFIRMATION_REQUIRED's number.
See hardware/interfaces/keymaster/4.0/types.hal for correct numbering.
Bug: 128851722
Test: Keymaster VTS 4.0 + Trusty
Change-Id: I89117ffe91602884edb8dd19ffd22e659f40fb1c
Extend "CAMERA3_MSG_ERROR_RESULT" comments and describe
how Hal must notify about physical device result failures
and logical device result failures.
Bug: 128835627
Test: Successful build
Change-Id: I935fba5a5676a0fe9440f43b281fc9eeb50578ea
