Keymaster is now optional because KeyMint can be used instead. This
CL makes this change retroactively back to compatibility matrix v3,
per discussion with the Treble team.
Test: Replace Keymaster with KeyMint & build
Change-Id: Id26d5bac326c494e1810516582fdd56a42c04e0d
Dropping requirement of configstore on devices
launching before or at P.
Test: pass
Bug: 150981985
Change-Id: I1c08bd7b18fe6006ee1555c39072e75ec4fb3210
This reverts commit 373a240386.
Bug: 123249760
Test: Both of P19 & P20 build pass, basic functions work and HAL 1.4 works.
Change-Id: I69f794f25d7c87c65df749c39ed29b1e0f476b03
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
Adding a callback object to indicate asynchronous events back to
framework. Only a failure indication method is added currently.
Also, Uprev the hostapd interface to 1.1.
Bug: 112705137
Test: Compiles
Change-Id: Ib885001e68734caa5ff192721f618010c125e4b7
This is missing from a very old CL. IR is an optional
HAL so specifying interface / instance here doesn't break
requirements.
Test: builds
Change-Id: I6d30d33041a01d8a8a724a89e00ba4c57d820d46
Adds new EXPENSIVE_RENDERING power hint.
This adds a new library which does not affect any pre-existing
targets unless they create and add a new binary which uses this.
BUG: 110112323
Test: adb shell /data/nativetest/VtsHalPowerV1_3TargetTest/VtsHalPowerV1_3TargetTest
Change-Id: I5fb33abbbe4c4958882a106dfa400ad74013e40d
This change provides a reference implementation of the configstore HAL
v1.1.
Bug: 69691076
Test: tested on walleye-userdebug
Change-Id: I68ee224bcbda64f6fef91e8a0f95adb32d504aad
nfc@1.0 requires a conf file (libnfc-nci.conf) in order to work.
Since this file has no schema, it is a system<->vendor violation
and must be placed on the system image, however this makes the
system image non-generic.
nfc@1.1 contains this configuration in the interface, and so it
can be used entirely without creating a Treble violation.
Test: P-launching devices have nfc@1.1
Bug: 72080121
Change-Id: I7a99eb7cd5e577be0c70b4c5124f28fa471717e6
This freezes the current compatibility_matrix for
Android P.
Fixes: 68112778
Test: m (assemble_vintf checks devices)
Change-Id: Ida30b7ba7f5df7c2755bd7c737190574b9195a92
2018-04-03 11:19:40 -07:00
Renamed from compatibility_matrices/compatibility_matrix.current.xml (Browse further)
