Shipping >= API Level 30: no vndservicemanager.
Make this device configuration instead. Vendor implementations can choose to use this, but it's not required. Bug: 148807371 Test: TH will test CF boots Change-Id: Ic144b1aa36e35295fccd9fa7f7f911587bf39bee
This commit is contained in:
parent
7decc032c2
commit
2bf4726f18
|
@ -67,11 +67,11 @@ PRODUCT_PACKAGES += \
|
||||||
selinux_policy_nonsystem \
|
selinux_policy_nonsystem \
|
||||||
shell_and_utilities_vendor \
|
shell_and_utilities_vendor \
|
||||||
vndservice \
|
vndservice \
|
||||||
vndservicemanager \
|
|
||||||
|
|
||||||
# Base module when shipping api level is less than or equal to 29
|
# Base module when shipping api level is less than or equal to 29
|
||||||
PRODUCT_PACKAGES_SHIPPING_API_LEVEL_29 += \
|
PRODUCT_PACKAGES_SHIPPING_API_LEVEL_29 += \
|
||||||
android.hardware.configstore@1.1-service \
|
android.hardware.configstore@1.1-service \
|
||||||
|
vndservicemanager \
|
||||||
|
|
||||||
# VINTF data for vendor image
|
# VINTF data for vendor image
|
||||||
PRODUCT_PACKAGES += \
|
PRODUCT_PACKAGES += \
|
||||||
|
|
Loading…
Reference in New Issue