Hello Szymon, On 9 February 2016 at 09:03, Szymon Janc <ext.szymon.janc@xxxxxxxxx> wrote: > Hi Barry, > > On Tuesday 09 of February 2016 08:00:52 Barry Byford wrote: > > <snip> > >> >>According to my phone the code on the Raspberry Pi is advertising with >> >>only the 'LE General Discoverable Mode' flag set. The 'BR/EDR not >> >>Supported' is not set. >> >>I've looked at the DBus API documentation again and it is not obvious >> >>that I can change this setting on the advertisement. Am I missing >> >>something? >> >> >> > Have you tried setting ControllerMode = le in bluez¹s main.conf? If set, >> > bluetoothd will explicitly enable le and disable br/edr in the kernel via >> > the management interface, and that should set advertising flags >> > appropriately. There does not appear to be a DBus API, probably because >> > this is more of a static setting. >> >> Thanks for the suggestion. I've added that setting to the >> /etc/bluetooth/main.conf and when the Raspberry Pi advertises it now >> has the 'BR/EDR Not supported' flag set. >> Now when I try to connect from my phone it fails with the same error >> message on my phone although in the hcidump and bluetoothd logs >> nothing appears when the phone tries to connect. >> >> Thanks again for the suggestion. > > If this is Android phone with 4.0 BT (no 4.1/4.2 features) then you need to > unpair the device and toggle phone BT off/on. Otherwise Bluedroid stack cache > info that your device is dual mode and tries to connect over BR/EDR. > Good suggestion! The modification to main.conf and resetting the phone has allowed me to access the services on my phone the raspberry pi is advertising. Thanks for your help. Regards, Barry -- 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
