By removing 1.0 from current.xml, health@1.0 is officially
considered "deprecated" but not "removed". It is still
supported for upgrading devices.
On upgrading devices, fwk/storaged->healthd->1.0 HAL still
exist, so this entry is kept on 26/27/legacy.xml.
On launch devices, device is required to have health 2.0 HAL,
hence the only code path is fwk/storaged->2.0 HAL. healthd
and 1.0 HAL is not used.
Test: builds (assemble_vintf passes)
Bug: 65990106
Change-Id: I4deb80074fe8e5a399e01e86bffcc69c272e748b
... on "current" compat mat level. They are kept optional
on upgrading devices.
Test: builds (assemble_vintf passes)
Bug: 63702641
Change-Id: Iafe64c4ffa7df8aa7f80a1b6cf599d56e7854f33
framework & storaged talks to health@2.0 HAL prior to healthd.
If the vendor service for health@2.0 is missing, framework / storaged
falls back and talks to healthd. Hence health@2.0 HAL is optional.
A follow-up change is needed to require launch devices to launch
with health@2.0 (i.e. current.xml says optional=false).
Bug: 62229583
Test: builds (assemble_vintf passes)
Change-Id: I49caca2b683e928f25e6f3cac2e2a8396b50f46a
This is a requirement on android phones and tv but
not on watches. Owner will handle putting that requirement
in place, but removing requirement from this file
specifically only in order to have O-MR1 interfaces
frozen.
Bug: 63603463
Test: m system_compatibility_matrix.xml compatibility_matrix.xml manifest.xml system_manifest.xml -j
Change-Id: Iefdc231c2928dfdb8e04a5de8a08ab9b23bae73d
Note, only new HALs for various shipping API levels
are added. No required HALs are added.
Test: (sanity) boot device w/o 'internal problem' error
Bug: 63603463
Change-Id: Ia400bdaf5d167ce8637ecdf940c5ccd629c8a09a
They are injected via assemble_vintf by the build system
at build time. See build/make/target/board/Android.mk.
Test: m system_compatibility_matrix.xml, and manually
inspect $OUT/system/compatibility_matrix.xml; it contains
<kernel> versions.
Bug: 64124223
Change-Id: Ibf82efa0805233dedb6badce7e5a4ff62a9ff769
Merged-In: Ibf82efa0805233dedb6badce7e5a4ff62a9ff769
Configstore was up-revisioned from 1.0 to 1.1. However no new
APIs were added to 1.1. Therefore configstore in mr1 will be down
revisioned to 1.0.
Bug: 64999074
Test: lshal | grep configsotre
Test: "cat proc/<configstore pid>/status | grep Seccomp " return:
Seccomp: 2
Change-Id: Ia2614439cd620fbe5fbd427571ab55a15089cc47
Keyed on MATRIX_LEVEL_OVERRIDE, FULL_TREBLE, SHIPPING_API_LEVEL,
and SDK_VERSION.
Bug: 62136051
Test: m system_compatibility_matrix.xml -j; \
grep -e"gatekeeper" -B1 $OUT/system/compatibility_matrix.xml; \
grep -e"oemlock" -B1 $OUT/system/compatibility_matrix.xml
bullhead: gatekeeper is optional, no oemlock (legacy.xml)
marlin without COMP_LEVEL_OVERRIDE: gatekeeper is not optional,
no oemlock (26.xml)
marlin with COMP_LEVEL_OVERRIDE: gatekeeper is not optional,
oemlock exists (current.xml)
new devices with COMP_LEVEL_OVERRIDE: same as above.
Change-Id: I2ccfa9b0132bf98cc2da8f0500bea992b5fa83d0
