Updating composePwleV2 VTS test to verify cases where the PWLE V2 capability is not supported.
Bug: 347034419
Flag: TEST_ONLY
Test: vts-tradefed run vts -m VtsHalVibratorTargetTest
Change-Id: I73de882f6595e858cea922b5378e5e7da4719140
There are changes in common audio libraries that force the sounddose
implementation to be bumped if any of the other audio implementations
are bumped.
Since we want to deprecate the sounddose interface and remove it from
FCMs > 202404, we need to retroactively allow the new sounddose version.
The other audio interfaces don't need this treatment because the newer
versions are added to the newer FCMs and we allow older devices to
implement them.
Test: m
Bug: 361383071
Change-Id: I195053bb6c5b6cb01584398eafc86f8fbcdd1148
refreshPropertyConfigs was not previously used in dumpresult proto
resulting in failing tests that require the argument.
Flag: EXEMPT test
Bug: 357135536
Test: atest android.car.apitest.CarPropertyManagerTest
Change-Id: I9c6dd3053aa54f37786edc3810a9342f5efb39cd
Stub output stream is like a /dev/null audio device, however
for synchronous transfers it must block for the duration of
the audio chunk being transferred. Implement more accurate
accounting for the blocking time using the same approach as
employed by the remote submix stream implementation.
Bug: 356719263
Test: atest CtsNativeMediaAAudioTestCases
on aosp_cf_x86_64_auto target
Change-Id: I137aed397246bcf2b5ef6789aa4d2d27ead64467
When supporting the audio AIDL HAL, we do not use the ISoundDoseFactory
anymore. Removing it from the compatibility matrix.
Flag: EXEMPT bugfix
Test: trivial
Bug: 356641174
Change-Id: I241c4b93ea6aa4e5499bc9e924d6df4f4bd464a7
Updating IVibrator.aidl to introduce APIs for PWLE V2 support. The updated interface now enables retrieval of minimum and maximum PWLE durations, maximum composition size, and facilitates the composition of PWLE effects using points.
Bug: 347034419
Flag: EXEMPT HAL interface change
Test: vts-tradefed run vts -m VtsHalVibratorTargetTest
Change-Id: Id0a93e4f8678622bdb698cddc2b39f46e0283fdd
Some devices require this for VTS
Bug: 329526845
Test: builds
Test: VtsHalGraphicsComposer3_TargetTest
Change-Id: I94d9611c9ec64be867ade6933a07ae9e97b459a1
It was noted that calling 'ABinderProcess_startThreadPool'
results in the audio HAL service having more Binder pool
threads than without it. This is preferred to having
just one thread via 'ABinderProcess_joinThreadPool'
as in the latter case clients may seemingly be blocked
instead of being served by a newly spawned thread from
the pool.
Bug: 357669241
Test: atest VtsHalAudioCoreTargetTest
Change-Id: Ia8ed52b3c5a95cea12d063a0e75ac908af9260f8
Add support for haptic scale factors introduced to the HapticScale
parcelable defined at HapticGenerator.aidl. These fields are used by the
platform to scale the haptic channel data before it's sent to the vibrator
motor.
The fields have a default negative value which will be interpreted as
undefined by the scale function and ignored. The VibratorScale enum will
still be supported by the platform when the scale factors are undefined.
Fix: 356406324
Fix: 356406686
Flag: EXEMPT HAL interface change
Test: VtsHalHapticGeneratorTargetTest
Change-Id: I9da0f6f2573722089efadb78ff96fc265bdad164
In our project we integrate vehicle properties definition and reused some of the existing message types (`VehiclePropConfig` and `VehicleAreaConfig`), so we need to depend on a Rust target of the protos.
Bug: 346786677
Test: m
Change-Id: If99f1763e38a9f8bb0ac4dd9ba5e1bee22cc54a7
Move the cleanup of the stream worker thread from '~StreamCommonImpl'
up to concrete stream implementations. This is because when
the worker thread is stopping, it calls 'DriverInterface::shutdown'
method of the stream. At the time when '~StreamCommonImpl' is
running, the concrete stream class has already been destroyed.
The cleanup actually only happens in the case when the client
did not close the stream properly via 'IStreamCommon.close', or
when the stream creation has failed in the middle.
Bug: 355804294
Test: atest VtsHalAudioCoreTargetTest
Change-Id: Ie86f682af202976ed48d24338b2dffcfd20d9a76
Update VendorEffect.aidl to support 2 continuous float scale parameters,
one that reflects the user intensity settings for that effect and a
second that is forwarded from the vendor vibrator controller service for
that vibration usage.
This allows vendors to apply the 2-tier scaling function to the
vibrations, one reflecting the user settings and a second reflecting the
vendor parameter sent to the platform based on the device current
state.
Bug: 345409060
Test: VtsHalVibratorTargetTest
Flag: EXEMPT HAL interface changes
Change-Id: Ic88f90fd0ff1eae8797a7fe7d84d5b11f6c2f6bf
