Hi all,
I'm working on fixing bluetooth related bugs for the M14.4 IVI release.
To do so, I found few limitations/constraints in bluetooth-frwk, I'd
like to change:
- bt-service daemon automatically enables bluetooth.
--> I would like to keep bluetooth state as it is and align
accordingly vconf bt status key.
- in each bluetooth CAPI call, bt adapter state is checked. Currently
CAPI directly checks the status over Bluez property.
--> I would like to make this check in bt-service. By this way,
bt-service can be launched by dbus activation (when checking bt state at
bt init phase for instance).
The main goal here is to clean up tizen bluetooth crosswalk extension
intialization in fixing IVI bluetooth bugs.
In addition it will unify initialization phase in case of NTB or
bluetooth-frwk component.
Does someone see a problem with this approach ?
Thanks and regards,
Corentin
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
