| Hi Kaelin,
I have noticed new behavior in iOS 6 that may be related. Sending a cancelPeripheralConnection does disconnect the CBPeripheral from the application. However, the system maintains a radio connection to the peripheral hardware in the background for about 46 seconds afterwards (although the time can vary).
I had assumed this is an intentional behavior meant to reduce the number of connect/disconnect cycles as a peripheral is shared between applications. On the other hand, it is causing some trouble for us because the peripheral does not begin advertising as expected, and this may result in user confusion (it certainly confused me for a while).
If you're testing with 6, maybe try 5 once to see if the problem goes away.
On Jul 25, 2012, at 4:05 PM, Kaelin Colclasure < email@hidden> wrote: It does seem to be an issue with the board. If I wait long enough, it will eventually revert back to advertising. Thanks for the replies confirming I was on the right track.
-- Kaelin
On Jul 25, 2012, at 11:54 AM, James Collins wrote: Woops, should have read your message more carefully. Anyway, the device that I am testing with, the polar heart monitor disconnects when the cancelPerpheralConnection is issued so maybe the problem is with your test board.
Jim
_____________________________ Jim Collins
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|