-
Improvement
-
Resolution: Won't Fix
-
Major
-
None
-
None
-
None
Due to there being quite a bit of pieces of AGL that require the current agl-service-bluetooth we need to have two PROVIDERS which one is the new bluetooth service and the other the legacy one.
NOTE: Will need force push privileges initially to push the current history, or copying over agl-service-bluetooth to agl-service-bluetooth-legacy will be fine
Middleware changes should make this transparent to most applications via libqtappfw and a reporting of the version API
Owner: Matt Ranostay
Maintainers: Matt Ranostay, Scott Murray