AutoConnect with ble_app_proximity & Master Control Panel/ToolBox

RE: AutoConnect with ble_app_proximity & Master Control Panel/ToolBox

Hung Bui — Thu, 21 Jan 2016 09:40:09 GMT

Well, no the nRF51 can't do Bluetooth classic, they are 2 different protocols. nRF51 is not compatible with BT Classic central. Most phones are Bluetooth Smart Ready, which mean they supports both Classic and BTLE.

Regarding your watch, I would need to know how does it connects to the phone, could be using an app or a service running in background ? I suspect there is a chance that the app do scanning and connect continuously (instead of using auto connect).

RE: AutoConnect with ble_app_proximity & Master Control Panel/ToolBox

TechGeek — Thu, 21 Jan 2016 08:15:13 GMT

Yes, the device starting to advertise right after disconnection. No issues with it.

As for Bluetooth Classic, isn't it the nRF51822 can be in Bluetooth classic mode as well? Even if not, wouldn't it be "compatible" with BT Classic mode central roles? BTW, my watch uses BT LE.

RE: AutoConnect with ble_app_proximity & Master Control Panel/ToolBox

Hung Bui — Thu, 21 Jan 2016 08:06:42 GMT

Hi TechGeek,

The headphones most likely using Bluetooth classic which mean different protocol. I'm not sure about the watch.

I don't think the firmware can do anything here unless you change the address when start advertising again. I assume that your device start advertising right after it get disconnected ?

RE: AutoConnect with ble_app_proximity & Master Control Panel/ToolBox

TechGeek — Wed, 20 Jan 2016 20:49:52 GMT

Thanks Hung.

While I will try to test with other Android, preferably on a Samsung, my concern is about the behavior consistency (or lack there of). The issue is that, with OnePlus, all my other BT devices like headphones, speakers and my watch is working perfectly fine with respect to AutoConnect. Only Nordic device is having trouble with the autoconnection. So, I am wondering if this is specific to nRF51822 or could I be doing something in the firmware to get this capability....

RE: AutoConnect with ble_app_proximity & Master Control Panel/ToolBox

Hung Bui — Wed, 20 Jan 2016 10:12:33 GMT

Hi Techgeek,

We haven't tested with One Plus, but not all the Android phones support Autoconnect. We had some experience with old Nexus phones that didn't support Autoconnect. Samsung's phones seems to be more stable and autoconnect worked fine. You can have a test.

On Windows10, I am not sure autoconnect is supported.

RE: AutoConnect with ble_app_proximity & Master Control Panel/ToolBox

TechGeek — Wed, 20 Jan 2016 03:45:43 GMT

On Android, I tested with a One Plus phone device and on Windows 10, I tested with multiple tablets and PCs.

When I use "Connect using autoconnect" in MCP (in the drop down menu), once I get out of range, the phone gets disconnected (which is as expected) and getting back in to the range, does not auto-connect. I also tried Bluetooth OFF(and later ON), Airplane mode (ON and later OFF) experiments within the range. All of them resulted in same behavior- phone doesn't auto-connect.

RE: AutoConnect with ble_app_proximity & Master Control Panel/ToolBox

Hung Bui — Tue, 19 Jan 2016 09:42:22 GMT

Hi TechGeek,

Could you let me know which Android device (s) you tested ?

When you enable AutoConnect in MCP (in the dropdown menu), what happened when you get out of range and get back in ?