The ngfd droid backend uses the Android headers (version specifically) to figure out which Android API to use.
These headers existed as part of the libhybris dependency, but a change of machine would not always trigger a sysroot update because there's no hard dependency on the android-headers package.
This fixes the issue where sometimes the vibrator would not work for some watches.
The ngfd droid backend uses the Android headers (version specifically) to figure out which Android API to use. These headers existed as part of the libhybris dependency, but a change of machine would not always trigger a sysroot update because there's no hard dependency on the android-headers package.
This fixes the issue where sometimes the vibrator would not work for some watches.
This issue was reported by @dodoradio, https://github.com/AsteroidOS/meta-smartwatch/issues/90 and https://github.com/AsteroidOS/meta-smartwatch/issues/91.