Most layers used by the build system are at priority 7.
Having the same layer priority for the meta-smartwatch introduces deterministic issue where sometimes the wrong file may be installed.
Recipes may prepend or append files.
For example brcm-patchram-plus and bluez are often adjusted to install a different service or config file.
In the case of brcm-patchram-plus sometimes the patchram.service file from meta-asteroid is installed leading to non-functional Bluetooth on many devices, this has been solved previously by removing the file from meta-asteroid.
In the case of bluez a main.conf file is proved by meta-asteroid that disables classic Bluetooth mode to improve battery life.
This doesn't work on some platforms, where dual mode needs to be enabled. Installing the wrong file again leads to non-functional Bluetooth.
Other issues may also arise from using the same priority. Giving the platform layers a higher priority should solve these issues.
Most layers used by the build system are at priority 7. Having the same layer priority for the
meta-smartwatchintroduces deterministic issue where sometimes the wrong file may be installed.Recipes may prepend or append files. For example
brcm-patchram-plusandbluezare often adjusted to install a different service or config file. In the case ofbrcm-patchram-plussometimes thepatchram.servicefile frommeta-asteroidis installed leading to non-functional Bluetooth on many devices, this has been solved previously by removing the file frommeta-asteroid. In the case ofbluezamain.conffile is proved bymeta-asteroidthat disables classic Bluetooth mode to improve battery life. This doesn't work on some platforms, where dual mode needs to be enabled. Installing the wrong file again leads to non-functional Bluetooth. Other issues may also arise from using the same priority. Giving the platform layers a higher priority should solve these issues.