Hi Serge, On Mon, Aug 1, 2016 at 3:34 PM, Serge van den Boom <serge@xxxxxxxxxx> wrote: > Hi, > > When a new profile is registered, or an adapter is make discoverable, > the device class of the adapter is reset to the value set in > /etc/bluetooth/main.conf. > > The test case below (to be run as root) demonstrates the issue. For this > demonstration, there should be no 'Class = ...' setting in > /etc/bluetooth/main.conf. This is a classical problem of using hci* tools along with bluetoothd, they both are trying to control the same thing and then you got a conflict, it shall be one or the other but not both. If you are curious to look at the bluetoothd source code you will see that the we derive the class of the device from the registered services so there is no point in doing anything with hcitool. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
