libsnapshot needs to communicate to the bootloader that a merge is in
progress. This can be used to prevent factory data resets, prevent
flashing or wiping userdata/metadata, and warning when the active slot
changes.
Bug: 138861550
Test: builds
Change-Id: I577877696b5ec6920b9520d518374931ce9ddfaa
Merged-In: I577877696b5ec6920b9520d518374931ce9ddfaa
This HAL interface was setup to have multiple clients, but the interface
(and many implementations) didn't separate clients use of callbacks.
That is, one client could delete the callback of the other.
Instead, thermal@2.0 should be used.
Bug: 118792995
Test: assemble_vintf
Change-Id: I2338cf63c6f450b22894406c9426d8d2ddac1057
1.1 IRadioConfig does not exist. radio.config@1.2 is a
minor version uprev that only updates the sub interfaces,
not the top level interface.
Test: builds
Bug: 135172251
Change-Id: Ia576cea29c63850ddb531f7c972fa4ebaecd20c7
1.1 IRadioConfig does not exist. radio.config@1.2 is a
minor version uprev that only updates the sub interfaces,
not the top level interface.
Test: builds
Test: on device with target-level 4, w/o this change,
with radio config 1.1, see test failure on deprecated
radio config HAL
Test: on this device, with this change, with radio config 1.1,
deprecated radio config HAL failure goes away.
Bug: 135172251
Change-Id: Id51870a8a757af0895577a27723cff8ee3ba0fdd
compatibility_matrix.4.xml was updated for a late fix in Q, so the
current matrix also needs to be updated.
Bug: 135627722
Test: vts_treble_vintf_test
Change-Id: I0cca7c55007d42ed8e86256b7b280b075378bc40
@1.4::ISap and @1.3::ISap don't exist, so we can't declare a requirement
for them.
Bug: 135627722
Test: reproduce error with vts_treble_vintf_test and then test to see
this change fixes it.
Change-Id: I8e48fcaf56701087d5720d5133ffa9b23a4ea31e
As it turns out, the client side of this HAL was never implemented.
Ideally, we could completely remove the HAL from old compatibility
matrices and remove the HAL from current.txt. However, this would
break some old devices which include an implementation.
Bug: 130080335
Bug: 126892442
Test: build only (checks manifest)
Change-Id: I7205faa719b9566af1b4e56fda083c540d622dff
This reverts commit 373a240386.
Bug: 123249760
Test: Both of P19 & P20 build pass, basic functions work and HAL 1.4 works.
Change-Id: I69f794f25d7c87c65df749c39ed29b1e0f476b03
This was added to the PI (3) compatibility matrix but not to the
current matrix.
Bug: 126892442
Test: diff between 3 and current FCM only reflects intentional changes
Change-Id: Ib6d243d2015cb847afad63075387945a74c30f13
graphics.composer 2.3 was added in Android Q, so it is in the
compatibility matrix for target-level 4. Devices updating from P
to Q will automatically have this option applies. However, for
sanity, we try to keep the P compatibility matrix between releases.
This change should have no functional difference except minimizing
the delta in this file between P/Q branches.
Bug: 126892442
Test: diff compatibility matrix files
Test: these matrices are verified at build time
Change-Id: I8514c7b6ce4c2670ce7926fb31b09ed783d17dca
- 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
