January 2013 - Bluetooth-dev

Re: Basic question
by Matt Gillette 29 Jan '13

29 Jan '13

CBCentralManger only searches for Bluetooth LE devices(4.0). If you want to search for classic Bluetooth devices, you'll need to use the IOBluetoothDeviceInquiry class. Matt On Jan 29, 2013, at 2:56 PM, Marco Bambini <marco(a)sqlabs.com> wrote: > Hello, > I am probably missing something but I really don't understand why a simple BT code does not work. > I created a Cocoa app on MacOS X 10.8 and I linked the IOBluetooth framework. > > My very simple test class (which is CBCentralManagerDelegate and CBPeripheralDelegate) do: > > CBCentralManager *centralManager = [[CBCentralManager alloc] initWithDelegate:self queue:nil]; > [centralManager scanForPeripheralsWithServices:nil options:nil]; > > I was expecting to receive notifications about new devices in the eventDiscoveredPeripheral delegate method (and even in others methods) and I tried with a lot of different BT devices (even iPhone 5 with iOS 6.1) but nothing happens… even if devices are correctly listed using the Bluetooth preference pane utility. > > Why I do not receive anything in my delegates methods? > I am sure I am missing something about BT. > Please help. > -- > Marco Bambini > http://www.sqlabs.com > http://twitter.com/sqlabs > http://instagram.com/sqlabs > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/mgillette%40apple.com > > This email sent to mgillette(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Basic question
by Marco Bambini 29 Jan '13

29 Jan '13

Hello, I am probably missing something but I really don't understand why a simple BT code does not work. I created a Cocoa app on MacOS X 10.8 and I linked the IOBluetooth framework. My very simple test class (which is CBCentralManagerDelegate and CBPeripheralDelegate) do: CBCentralManager *centralManager = [[CBCentralManager alloc] initWithDelegate:self queue:nil]; [centralManager scanForPeripheralsWithServices:nil options:nil]; I was expecting to receive notifications about new devices in the eventDiscoveredPeripheral delegate method (and even in others methods) and I tried with a lot of different BT devices (even iPhone 5 with iOS 6.1) but nothing happens… even if devices are correctly listed using the Bluetooth preference pane utility. Why I do not receive anything in my delegates methods? I am sure I am missing something about BT. Please help. -- Marco Bambini http://www.sqlabs.com http://twitter.com/sqlabs http://instagram.com/sqlabs _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About CoreBluetooth disconnect behavior
by Jason Conn 29 Jan '13

29 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Xcode iOS 6.x Simulators Never Connect
by Amanda Shumack 29 Jan '13

29 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About CoreBluetooth disconnect behavior
by Etan Kissling 29 Jan '13

29 Jan '13

Jason, imagine an iPhone X with central-based apps A, B and C, and an iPhone Y with peripheral-based app P. All three apps on iPhone X are connected with app P. Am I correct in the assumption that P cannot distinguish the three apps on iPhone X, and that only iPhone X can evaluate which data packets from P are to forward to which A, B or C? This would explain why a peripheral cannot terminate a link (as it cannot know with how many apps it is talking), and also, why it is not possible to receive reliable connected/disconnected events on the peripheral. It would still be beneficial to have a way to leave peripheral mode altogether, disconnecting all centrals in the process. Or at least getting a callback on the first received connection and on the last ended connection. Depending on the use case, it may make sense to only perform computationally expensive tasks while a central is connected. Etan On 29.01.2013, at 18:55, Jason Conn <conn(a)apple.com> wrote: >> If my case use two iDevices, one in central and one as peripheral, how can I make sure the connection disconnected immediately? > > You can't guarantee that, and shouldn't rely on it. By it's nature, the multi-process architecture of iOS means that there may be another application running who still wants that connection up, even if you don't. > > On Jan 29, 2013, at 9:49 AM, Khaos Tian <khaos.tian(a)gmail.com> wrote: > >> Thanks for your remind :) >> >> So you suggest that the most reliable way to cause a physical disconnection immediately is to initiate it from the peripheral side. If my case use two iDevices, one in central and one as peripheral, how can I make sure the connection disconnected immediately? As what I knew there isn't possible to initiate cancel connection on CBPeripheralManager side. >> >> Best Wishes, >> Khaos Tian >> >> On Jan 30, 2013, at 1:35 AM, Jason Conn <conn(a)apple.com> wrote: >> >>> This was very much an intentional change, but one that comes with an arguably subtle caveat. As explained in the updated headerdoc: >>> >>> /*! >>> * @method cancelPeripheralConnection: >>> * >>> * @param peripheral A <code>CBPeripheral</code>. >>> * >>> * @discussion Cancels an active or pending connection to <i>peripheral</i>. This command is non-blocking, and any <code>CBPeripheral</code> >>> * commands that are still pending to <i>peripheral</i> may or may not complete. >>> * It extremely important to note that canceling a connection does not guarantee the immediate disconnection of the underlying physical >>> * link. This can be caused by a variety of different factors, including other application(s) that hold an outstanding connection to the >>> * peripheral. However, in this situation, you will still receive an immediate call to @link centralManager:didDisconnectPeripheral:error: @/link. >>> * >>> * @see centralManager:didDisconnectPeripheral:error: >>> * >>> */ >>> >>> Thus, if your use-case requires a physical disconnection of the peripheral, the only way to guarantee that happening in a timely fashion is to initiate it from the peripheral. >>> >>> On Jan 29, 2013, at 2:42 AM, Etan Kissling <kissling(a)oberon.ch> wrote: >>> >>>> Khaos, >>>> >>>> I can confirm disconnect delays of about 1-3s under the final iOS 6.1 version. >>>> Seems that it is intended and we can remove "remote disconnect" workarounds. >>>> >>>> Etan >>>> >>>> On 29.12.2012, at 14:25, Khaos Tian <khaos.tian(a)gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> On iOS 6.1 beta 4 I noticed that after I called >>>>> cancelPeripheralConnection: the connection between iDevice and >>>>> peripheral closed in about 1~2s. >>>>> >>>>> Is that Apple finally decided to remove the 30s disconnect delay in iOS 6.1? >>>>> >>>>> Best Wishes, >>>>> Khaos Tian >>>>> _______________________________________________ >>>>> Do not post admin requests to the list. They will be ignored. >>>>> Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) >>>>> Help/Unsubscribe/Update your Subscription: >>>>> https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch >>>>> >>>>> This email sent to kissling(a)oberon.ch >>>> >>>> >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/bluetooth-dev/conn%40apple.com >>>> >>>> This email sent to conn(a)apple.com >>> >> > _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About CoreBluetooth disconnect behavior
by Jason Conn 29 Jan '13

29 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About CoreBluetooth disconnect behavior
by Khaos Tian 29 Jan '13

29 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About CoreBluetooth disconnect behavior
by Jason Conn 29 Jan '13

29 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: CoreBluetooth cancelPeripheralConnection in background
by András Kövi 29 Jan '13

29 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Bluetooth LE problems with new iOS devices?
by Long LI 29 Jan '13

29 Jan '13

In iOS6.1, the problem was fixed maybe. works fine. On Fri, Jan 25, 2013 at 11:34 AM, Long LI <lilong(a)gmail.com> wrote: > I have same problem, Has anyone gotten a solution now? > >>> 1. Make a connection to the peripheral which succeeds. Attempt to >>> discover services. Instead of receiving the didDiscoverServices callback, I >>> get the didDisconnectPeripheral callback with ErrorCode=6, “The connection >>> has time out unexpectedly”. It seems to be completely random when this >>> happens. I’ve also seen cases where I am getting this disconnect at a later >>> time (after subscribing to characteristics). > > > Best regards, > Long LI > http://www.bbshare.com > Google Toolbar for Safari > Google Multi-Account Launcher for Chrome > QR Pro for iPhone > > http://www.zesty.co.jp > Control your Nikon DSLR with your iPhone > > On Wed, Nov 7, 2012 at 6:04 AM, Etan Kissling <kissling(a)oberon.ch> wrote: >> One thing that would also help is the new interval that you are trying to >> switch to. iOS accepts intervals down to 18.75 ms. However, in the iOS >> Guidelines for Bluetooth accessories, it is noted that it is not recommended >> to go below 38.75 ms. >> >> Etan >> >> >> On 06.11.2012, at 19:07, "Borna Vojdani" <bornav(a)gmail.com> wrote: >> >> Thanks for the reply Mike, >> >> I as well have been using iOS5 and iOS6 devices, and have only noticed this >> specific error on iOS6.0 and iOS6.1 beta. It may be worth looking into the >> over the air data via a capture device if one is available to you in order >> to learn more. But based on my experience, and "unexpected timeout" is a >> fatal connection time radio dropout in which no termination packet is >> broadcasted by the peripheral. >> >> I say so as I have also have experienced the error you mentioned: “The >> connection has time out unexpectedly”. I experience this error on a daily >> basis with moderate to heavy usage of the peripheral which includes >> connecting and disconnecting throughout the day. It seems to randomly >> surface and I have not discovered the root cause, at least in my case. >> >> However, after looking through the over the air data, I can concluded that, >> for my case: >> >> -During certain connection events, when the connection update request is >> replied to by the iPhone with a success message (result 0x000), something >> goes wrong in the timing/scheduling of the new rate as done by iOS/iDevice, >> and the peripheral drops the connection sans a termination packet >> immediately due to the confusion. This is why iOS seems to come back with >> "an unexpected timeout" error. The stack does not seem to be aware of any >> issues introduced, nor does is see a termination packet as one is not >> broadcasted by the peripheral due to fatal connection parameter settings. >> >> -At times, this happens repeatedly until some measures are taken to reset >> the state of the device/BT; meaning that the connection fails multiple times >> until some intervention is done. >> >> -It seems to be completely random. I have not been able to find a reliable >> method of reproduction. >> >> I'm not sure if this is the same issue you are having, as you stated a >> disconnection occurring upon service discovery. I would however note that >> the default interval set by iOS is very short, and if there are not many >> services to be discovered and configured, this can happen rather quickly. >> >> If this is happening often enough to you that is becoming a big issue, I >> would suggest temporarily disabling the update request as a method of >> diagnosis. >> >> Best Regards, >> >> Borna. >> >> On Tue, Nov 6, 2012 at 3:39 AM, Michael Mallinson >> <Michael.Mallinson(a)entrust.com> wrote: >>> >>> Hi Borna, >>> >>> >>> >>> We do update the connection speed from the peripheral side but we are >>> doing this after the iPhone subscribes to a characteristic. So this >>> shouldn’t occur until after service and characteristic discovery has >>> completed. >>> >>> >>> >>> Cheers, >>> >>> --Mike >>> >>> >>> >>> From: Borna Vojdani [mailto:bornav@gmail.com] >>> Sent: Monday, November 05, 2012 4:57 PM >>> To: Michael Mallinson >>> Cc: bluetooth-dev(a)lists.apple.com >>> Subject: Re: Bluetooth LE problems with new iOS devices? >>> >>> >>> >>> Hi Michael, >>> >>> >>> >>> With respect to issue #1, is you're peripheral expecting, or initiating a >>> "connection update parameter request" during the initial >>> connection/discovery period? >>> >>> >>> >>> Best Regards, >>> >>> >>> >>> Borna Vojdani >>> >>> On Mon, Nov 5, 2012 at 5:09 AM, Michael Mallinson >>> <Michael.Mallinson(a)entrust.com> wrote: >>> >>> Hi, >>> >>> >>> >>> I’m curious if anyone has seen any issues with the iPhone 5 and 5th gen >>> iPod Touch when used with Bluetooth LE. >>> >>> >>> >>> I’m seeing several problems with some of these devices that I wasn’t >>> seeing with the original Bluetooth LE capable devices (iPhone 4s/iPad 3). >>> My application is using bluetooth-central mode and connecting to a Bluegiga >>> BLED112 USB dongle. Currently using iOS 6.0.1 on all my test devices. >>> >>> >>> >>> 1. Make a connection to the peripheral which succeeds. Attempt to >>> discover services. Instead of receiving the didDiscoverServices callback, I >>> get the didDisconnectPeripheral callback with ErrorCode=6, “The connection >>> has time out unexpectedly”. It seems to be completely random when this >>> happens. I’ve also seen cases where I am getting this disconnect at a later >>> time (after subscribing to characteristics). >>> >>> 2. Failures while trying to subscribe to characteristics which >>> result in ErrorCode=0, “Unknown Error”. >>> >>> 3. Failures in the didDiscoverServices callback ErrorCode=0, >>> “Unknown Error”. >>> >>> >>> >>> The problems seem to be sporadic and don’t always occur. Interestingly, >>> I’ve also got one iPod Touch that hasn’t shown any signs of these problems >>> yet. I’ve been unable to reproduce these issues with the iPhone 4S/iPad 3 >>> and have only seen them with the iPhone 5 and new iPod Touch. Other than >>> the iOS device, the rest of the picture is the same. >>> >>> · Bluegiga BLED112 USB Dongle >>> >>> · Same version of the USB Dongle firmware, Windows driver and >>> Windows application. >>> >>> · iOS 6.0.1 >>> >>> · Same version of the iOS application. >>> >>> >>> >>> It is my understanding that the new iOS devices are using a new >>> WiFi/Bluetooth chip in them. I wonder if this could be contributing to the >>> problems I’m seeing? >>> >>> >>> >>> Michael Mallinson >>> >>> Software Developer >>> >>> Phone: (613) 270-2548 >>> >>> >>> >>> Entrust >>> >>> Securing Digital Identities >>> >>> & Information >>> >>> http://www.entrust.com >>> >>> >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/bluetooth-dev/bornav%40gmail.com >>> >>> This email sent to bornav(a)gmail.com >>> >>> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch >> >> This email sent to kissling(a)oberon.ch >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/bluetooth-dev/lilong%40gmail.com >> >> This email sent to lilong(a)gmail.com >> _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0