- configstore@1.2 no longer exists
- configstore@1.1 is being deprecated in favor of properties
Bug: 122461092
Bug: 124531214
Test: manual
Change-Id: Ia1411ca5db897b3d9f67a4450cf10f878ddc64b9
Sometimes, the camera service needs to notify a camera HAL that the
overall device physical state has changed, so that the HAL can
properly remap how it handles logical multicamera devices or similar.
Test: Builds, new VTS tests pass
Bug: 121379978
Change-Id: I0982fdecaf53a0529289d63c08c5a31264ee7ec7
Before:
1.0-1.1 is optional, but an implementation of 1.2 is required.
After:
1.0-1.2 can be used.
Bug: N/A
Test: N/A
Change-Id: I631c253ee44f858e3c1912106cb42682eb044c05
This reverts commit 1b066c8d1d.
Reason for revert: <This CL isn't related to public API which triggered previous revert>
Change-Id: If1fa2a244e5f4ee7f978cda79421172da02220f1
Add sendSessionEvent to notify hal what happened on a session.
Add onSessionEvent to listen notification from hal for a session
Test: manual
Bug: 122472761
Change-Id: I98434325915e7bee57e63bdeeedba9ed5578e493
Fix the compatibility matrix with range of versions
Bug: 122994344
Test: verified manually
Change-Id: Ic5ebb7261d2fe8f379d46ebcc0c47efe8dbd3c59
Merged-In: Ic5ebb7261d2fe8f379d46ebcc0c47efe8dbd3c59
DEVICE_PRODUCT_COMPATIBILITY_MATRIX_FILE is installed on
/product/etc/vintf. It is considered as a replacement of
DEVICE_FRAMEWORK_COMPATIBILITY_MATRIX_FILE, so only one
of them may be defined. At build time, things like
SEPolicy versions etc. will be written to
/product/etc/vintf/compatibility_matrix.device.xml, just
like the /system one.
Also, split framework_compatibitity_matrix.xml to
system_compatibility_matrix.xml and product_compatibility_matrix.xml.
The latter two corresponds to matrices installed to respective
partitions only.
Test: build with DEVICE_PRODUCT_COMPATIBILITY_MATRIX_FILE defined
Test: boot (sanity)
Bug: 120600021
Change-Id: I81f9a8f5028cbb88c45f44df04bccb8ccb483972
Supports reporting and userspace control of USB contamination presence.
Bug: 117330206
Bug: 77606903
Bug: 119642987
Test: USB HAL V1.2 HIDL tests.
Change-Id: I70219641cdd48d59d217334dbd6d4ed8a8ce4927
V2_2 has the same functionality as V2_1 except it adds one new
api, getModelState.
Note: V2_1 will be removed in a subsequent cl.
Test: built android and tested using SoundTriggerTestApp
Bug: 70206501
Change-Id: Ia1567bfc988482195b89b8d6a0901d51e870bfbf
Generalized Bluetooth Audio HAL interface.
It is similar to the original android.hardware.bluetooth.a2dp@1.0
interface with the following modifications:
* The session type can be one of the following:
- A2DP Software Encoding Datapath
- A2DP Hardware Encoding Datapath
- Hearing Aid Software Encoding Datapath
* For Hardware Offload Datapath (A2DP), the HAL interface is used only
for the control path
* For Software Encoding Datapath (A2DP or Hearing Aid), the HAL
interface is used for both the control and data paths
* Added Delay Report support: IBluetoothAudioHost.getPresentationPosition()
that was missing in the original android.hardware.bluetooth.a2dp@1.0
HAL interface.
* Removed "oneway" calls to avoid potential reordering of HAL calls:
b/111244402
* Updated SBC-specific codec configuration
* Added AAC-specific and LDAC-specific codec configuration
* Reorganized the original CodecConfiguration into two sections:
- PcmDataConfiguration: Audio PCM data configuration
- EncodedDataConfiguration: Encoded audio data codec configuration.
It is used only if the HAL is responsible for encoding the PCM audio
data.
* Added new HAL IBluetoothAudioProvidersFactory.
It is used to open an audio provider for an audio session as specified by
the session type and the codec configuration as negotiated with the
remote device.
Bug: 111519504
Test: manual
Change-Id: I2ee4cf50b177baee077cf0b5143dbeadda57c8fb
Merged-In: I2ee4cf50b177baee077cf0b5143dbeadda57c8fb
(cherry picked from commit fcc0732db4)
Increase IAllocator and IMapper to 3.0. This patch does not add
any new features.
Bug: 120493579
Test: vts
Change-Id: I84d9887f94d91eca1cc5d845bb11ac1d8affbf62
Generalized Bluetooth Audio HAL interface.
It is similar to the original android.hardware.bluetooth.a2dp@1.0
interface with the following modifications:
* The session type can be one of the following:
- A2DP Software Encoding Datapath
- A2DP Hardware Encoding Datapath
- Hearing Aid Software Encoding Datapath
* For Hardware Offload Datapath (A2DP), the HAL interface is used only
for the control path
* For Software Encoding Datapath (A2DP or Hearing Aid), the HAL
interface is used for both the control and data paths
* Added Delay Report support: IBluetoothAudioHost.getPresentationPosition()
that was missing in the original android.hardware.bluetooth.a2dp@1.0
HAL interface.
* Removed "oneway" calls to avoid potential reordering of HAL calls:
b/111244402
* Updated SBC-specific codec configuration
* Added AAC-specific and LDAC-specific codec configuration
* Reorganized the original CodecConfiguration into two sections:
- PcmDataConfiguration: Audio PCM data configuration
- EncodedDataConfiguration: Encoded audio data codec configuration.
It is used only if the HAL is responsible for encoding the PCM audio
data.
* Added new HAL IBluetoothAudioProvidersFactory.
It is used to open an audio provider for an audio session as specified by
the session type and the codec configuration as negotiated with the
remote device.
Bug: 111519504
Test: manual
Change-Id: I2ee4cf50b177baee077cf0b5143dbeadda57c8fb
In order to continue providing the best Telephony
experience possible, Android devices that ship
with Q should implement the IRadio 1.4 HAL.
Likewise, new devices should ship with IRadioConfig
version 1.2.
Bug: 112764647
Test: compilation; boots with Pixel 2
Change-Id: I7ce1a7e81dc54d6e4e13b4bdaad8228465bf1570
The new HAL will be responsible for processing touch video frames that
are received from InputClassifier stage.
After processing, the HAL will generate a classification of the current
gesture. This classification will later be provided to the app via
the MotionEvent.getClassification() public API.
The eventual goal is to classify each event stream as a force touch
or not a force touch.
An example implementation of the HAL is presented here. This code was
used for local testing on blueline, and should not be actually installed
or used in any way other than for reference.
Bug: 62940136
Test: observed "detected deep press" logs when pressing with large
finger area on the touchscreen
Change-Id: Id6ac4337435e4ac07877da11ca184b6dd4d64780
* changes:
power/stats: Add VTS test cases for power.stats HAL
power/stats: Add VTS testcases
power/stats: Add default implementation
power/stats: Update HIDL to include power stats API
power/stats: Update HIDL to use synchronous FMQ
power.stats: Add power.stats HIDL interface
Bug: 122271863
Test: Verified Sensors 1.0 is used if DCM requests Sensors 1.0
Test: Verified Sensors 2.0 is used if DCM requests Sensors 2.0
Change-Id: I3d5d21f0c1a75440e777ddb9a9afe4b0efbdda12
Add API for enabling/disabling external control of vibrator.
Bug: 117835666
Test: Sanity Check Via 'cmd vibrator'
Change-Id: I5342ca9feba1811efcb5483668858db3f70ad686
Signed-off-by: Harpreet "Eli" Sangha <eliptus@google.com>
