15c9ef4cc3
The priority order for overlays is PRODUCT > DEVICE > LOCAL Having PRODUCT here was overriding all of the DEVICE_ specifics mentioned in device repositories, which was not the intent. vendor/cm is present as a set of sane defaults, but for the most part these overlays are intended to be overridable by the device if needed. The logic is that PRODUCT_PACKAGE_OVERLAYS should be used by a particular product while DEVICE_PACKAGE_OVERLAYS is used by several products that share common device configs. Yeah, the naming is counterintiuitive, but that's the implementation in build/core/package_internal.mk Partially addresses CYNGNOS-2229 Change-Id: Icfbc92593e37f3c00c3d26dd09e08d09267621ed |
||
|---|---|---|
| .. | ||
| permissions | ||
| cm_audio.mk | ||
| common_full_phone.mk | ||
| common_full_tablet_wifionly.mk | ||
| common_full_tv.mk | ||
| common_full.mk | ||
| common_mini_phone.mk | ||
| common_mini_tablet_wifionly.mk | ||
| common_mini_tv.mk | ||
| common.mk | ||
| nfc_enhanced.mk | ||
| telephony.mk | ||
| themes_common.mk | ||