According to the the book <Bluetooth Low Energy: The Developer's Handbook> (page 273) written by Robin Heydon (the co-chair of the BLE spec group):

"The BR/EDR Not Supported flag (Bit2) bit is used to notify a peer device before making a connection that it cannot make a connection by using Bluetooth classic; instead, it must use Bluetooth low energy. This is important because a dual mode device cannot make a connection to another dual-mode device by using Bluetooth low energy. Therefore, a dual-mode device must check this bit to determine how it should initiate a connection to the device".

So the Bit2 actually tells the other dual mode device (BlackBerry phone) that the watch only accept BLE connection. So our setting is correct. Otherwise if Bit2 is set to "0", it means the watch is dual mode and supports both BR and BLE connection, BlackBerry would always initiate a BR connection instead of BLE connection.

The Bit3/4 means:

"The Simultaneous LE and BR/EDR to Same Device Capable flag bits are used to determine if the peer device can initiate a connection over Bluetooth low energy if a Bluetooth classic connection already exists to that device."

So these bits don't matter here as setting up simultaneous BLE and BR connections is not the case here.

Re: Bluetooth 4.0 (BLE) compatibility between Z10 and MetaWatch

Thanks, so unless I've misunderstood, the issue is perhaps about the semantics/intention of the phrase "not supported" regarding Bluetooth Classic. MetaWatch does support it but in this use case it's not available for connection and BLE should be used. Is that a reasonable summary?

Leave it with me and I'll discuss with our development team further.

--------------------------------------------------------------------------------------------Feel free to press the like button on the right side if you liked my attempts to help :-)And please mark posts as solved if you think I found the solution or set you on its path. Thanks!Follow me on Twitter: @mdwrim

Re: Bluetooth 4.0 (BLE) compatibility between Z10 and MetaWatch

the original tests performed with MetaWatch were from last year and with MetaWatch firmware version 1.5.1. I just upgraded to the latest firmware, version 1.5.3 and now get the correct and expected results. I used a sniffer to capture advertising packets and the content captured at 1.5.1 is different to 1.5.3. 1.5.1 used the FLAGS field incorrectly with reference to the Bluetooth Core Specification and this caused the anomoly whereby BlackBerry 10 listed the device twice in its Bluetooth Settings page (once for a BR/EDR interface and once for a BLE interface). Now, with the 1.5.3 firmware on the MetaWatch, advertising packet FLAGS are correct and the device appears only once, as a BR/EDR device. Here are the packet details from the two firmware versions fyi:

So it seems that with the latest MetaWatch firmware, BlackBerry 10 and MetaWatch play nicely and I hope the above explains why this was not the case with older firmware.

Regards

Martin

--------------------------------------------------------------------------------------------Feel free to press the like button on the right side if you liked my attempts to help :-)And please mark posts as solved if you think I found the solution or set you on its path. Thanks!Follow me on Twitter: @mdwrim

It's writable and notifiable. MWM shall use it to send messages (as notifications) to the watch. So one Client Configuration Characteristic descriptor is also needed for the watch to register the notifications.” "

--------------------------------------------------------------------------------------------Feel free to press the like button on the right side if you liked my attempts to help :-)And please mark posts as solved if you think I found the solution or set you on its path. Thanks!Follow me on Twitter: @mdwrim