Supporting AVF implies that device supports updatable APEX
AVF (Microdroid specifically) doesn't work on device with flattened APEXes. While there are already requirements that new devices should support non-flattened APEXes, during device bring up it is possible to end up in a state of (flattened APEX + AVF supported). This patch fixes such scenarios by inheriting the updateable_apex.mk from the product_packages.mk used to enable AVF. Bug: 274898309 Test: m Change-Id: Ia8d589f573381e0eda9db032e4ad82e48b331c1b
This commit is contained in:
parent
092a1f3fd7
commit
3a747a655c
|
@ -19,6 +19,9 @@
|
|||
# To include the APEX in your build, insert this in your device.mk:
|
||||
# $(call inherit-product, packages/modules/Virtualization/apex/product_packages.mk)
|
||||
|
||||
# If devices supports AVF it implies that it uses non-flattened APEXes.
|
||||
$(call inherit-product, $(SRC_TARGET_DIR)/product/updatable_apex.mk)
|
||||
|
||||
PRODUCT_PACKAGES += \
|
||||
com.android.compos \
|
||||
|
||||
|
|
Loading…
Reference in New Issue