android_device_xiaomi_sdm66.../rro_overlay/SDM660WifiOverlay/Android.bp

runtime_resource_overlay {
    name: "SDM660WifiOverlay",
    resource_dirs: ["res"],
    vendor: true
}
sdm660-common: Add WifiOverlay Bug: 148617260 Test: Device boots up and connects to wifi networks. Change-Id: Iec27a6d947a232a42451ef095dc73d1a52327db5 2020-04-24 17:33:28 -04:00			`runtime_resource_overlay {`
sdm660-common: rro_overlay: rename all overlays to avoid conflicts 2024-01-14 10:37:26 -05:00			`name: "SDM660WifiOverlay",`
sdm660-common: rro_overlays: Install WifiOverlay into vendor We don't have a dedicated product partition which will leave WiFi broken on vanilla AOSP GSI. Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com> Change-Id: I3107da263fd29f0bc40f495ad84fdf4db0d3c814 Signed-off-by: pix106 <sbordenave@gmail.com> 2020-11-14 02:12:12 -05:00			`resource_dirs: ["res"],`
sdm660-common: overlay: Move rro packages to vendor partition In Android 14, prioritization of partitions is emphasized, diverging from previous versions where priorities were respected universally. Overlay precedence now plays a critical role, with the following partition order dictating overlay precedence: - system - vendor - odm - oem - product - system_ext When multiple overlays contend for the same resources, the order of overlays becomes crucial. An overlay takes precedence over others if it has configurations following its own. This prioritization, while impactful for GSI compatibility, is essential for maintaining order and functionality. * (pix106) Only WifiOverlay packages did not have vendor explicitely defined Change-Id: I8b7568dcc418dbbd1ccb39e2d0dc66504f19fcdd 2024-02-27 02:49:41 -05:00			`vendor: true`
sdm660-common: Add WifiOverlay Bug: 148617260 Test: Device boots up and connects to wifi networks. Change-Id: Iec27a6d947a232a42451ef095dc73d1a52327db5 2020-04-24 17:33:28 -04:00			`}`