On Tue, 2013-12-10 at 17:09 +0800, Guoqiang Liu wrote:
> From: Zhang zhengguang <[email protected]>
>
> Root cause:
> When ConnMan tries to enable bluetooth technology, firstly
> it will send RFkill unblock event to kernel, then call dbus method
> to enable bluetooth device. When bluez receives the RFkill event,
> it will power on the device immediately, and sends PropertyChanged
> message to ConnMan. In ConnMan, the device powered state is updated in
> device enable dbus reply callback function, but ConnMan receives
> PropertyChanged message before device enable dbus reply, and in current
> ConnMan bluetooth plugin for Bluez 5.x, when handling PropertyChanged
> message, it finds the adapter state(enabled) is different with the device
> state ConnMan stores(disabled), it will disable the bluetooth device.
>
> Solution:
> In ConnMan bluetooth plugin for Bluez 5.x, When ConnMan finds the adapter
> state is different with the device state ConnMan stores, update device
> state in ConnMan to the adapter state.
Applied, thanks!
Patrik
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
