September 2012 - Bluetooth-dev

IOBluetoothHandsFreeDevice has failed during initialization
by 김영태 16 Sep '12

16 Sep '12

_______________________________________________ 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

CoreBluetooth: peripheral hardware won't connect anymore at some point (iOS 6 beta 4)
by Florian Schulz 12 Sep '12

12 Sep '12

Hi, we are developing an app that communicates with peripheral hardware (TI CC2540). On iOS 6 we ran into the following problem: Usually the peripheral connects without any issues, but at some point the peripheral won't connect anymore on iOS 6 (beta 4). After connectPeripheral: is called on the centralManager, no didConnect: or didFailToConnect: callback comes in and the advertisement continues. In the air-trace it looks like there is no connection attempt by the iOS device. If this has happened once, the peripheral won't connect anymore. Restarting the peripheral or the app doesn't help. Turning Bluetooth on and off in the Settings app doesn't help either. What did make the peripheral connect again was changing the Bluetooth address on the peripheral. Rebooting the iOS device seemed to solve the situation as well. The problem is hard to reproduce - usually the peripheral connects but at some yet undefined point it stops working. On iOS 5.1.1 the problem doesn't seem to occur at all. I've double checked that the peripheral is retained properly and that the peripheral instance doesn't change between the initial discovery and the following discoveries. The delegates are set correctly as well. Can anybody point me at where to further investigate this issue? Could it be firmware related? Could it be cause by messed up connection parameters? My guess is that it's somehow related to caching in OS 6 (the peripheral is not paired btw), or maybe something like a connection that isn't closed properly on the iOS side. Any help would be highly appreciated. Best regards, Florian _______________________________________________ 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 Low Energy on ios6. CBPeripheralManager
by Borna Vojdani 12 Sep '12

12 Sep '12

_______________________________________________ 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

Long Characterisic Write
by Thomas Rosenstein 12 Sep '12

12 Sep '12

_______________________________________________ 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

Bluetooth Low Energy on ios6. CBPeripheralManager
by ramprakash.thinakaran＠wipro.com 12 Sep '12

12 Sep '12

_______________________________________________ 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: Is encrypted link supported in CoreBluetooth?
by Joakim Linde 10 Sep '12

10 Sep '12

Hi Jimmy, See comments below. Thanks, Joakim On Sep 10, 2012, at 2:21 PM, Jimmy Adler wrote: > Hi Joakim, > > thanks for the reply. > > If I try to read one of the protected Characteristics on the sensor, the pairing is initiated, indicated by a UIAlertView that asks if it is ok to pair the device. > > How do I know from the application that the link has been encrypted, is there a way to tell the outcome of the pairing? This is transparent to the app. > > Currently the pairing does not make any difference for me, I still cannot read the protected Characteristics. I did however notice that the UIAlertView that asks about paring states that > "The sensor would like to pair with your iPhone" > Is this the correct behavior? Sound like it. > > As I understood it, the sensor was not allowed to do pairing, it should be the other way around, right? The iPhone pairing with the sensor? The iPhone initiates pairing based on the error code from the Peripheral. > > Br, > > Jimmy > > On Sep 10, 2012, at 7:25 PM, Joakim Linde wrote: > >> >> Hi Jimmy, >> >> The Peripheral may indicate to an iOS Central that an encrypted link is needed by responding with the error code Insufficient Authentication on a characteristic read or write from the Central. The iOS Central will then initiate pairing and encrypt the link. >> >> Thanks, >> Joakim >> >> On Sep 10, 2012, at 5:43 AM, Jimmy Adler wrote: >> >>> The device I am communicating with requires an encrypted link to be setup in order for the device to allow access to most of its services, a Characteristic needs to be fed with a passkey in order for access to be granted and this has to be done over an encrypted link. >>> >>> How do I initiate such an encrypted link after connecting to the device using CoreBluetooth? >>> >>> I would assume it to be a function attached to CBPeripheral or CBCentralManager, but I cannot find any such functions there, unless it is an option of some sort that I have missed. >>> >>> Is it possible at all? >>> >>> Br, >>> >>> Jimmy Adler >> > _______________________________________________ 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: Is encrypted link supported in CoreBluetooth?
by Jimmy Adler 10 Sep '12

10 Sep '12

Hi Joakim, thanks for the reply. If I try to read one of the protected Characteristics on the sensor, the pairing is initiated, indicated by a UIAlertView that asks if it is ok to pair the device. How do I know from the application that the link has been encrypted, is there a way to tell the outcome of the pairing? Currently the pairing does not make any difference for me, I still cannot read the protected Characteristics. I did however notice that the UIAlertView that asks about paring states that "The sensor would like to pair with your iPhone" Is this the correct behavior? As I understood it, the sensor was not allowed to do pairing, it should be the other way around, right? The iPhone pairing with the sensor? Br, Jimmy On Sep 10, 2012, at 7:25 PM, Joakim Linde wrote: > > Hi Jimmy, > > The Peripheral may indicate to an iOS Central that an encrypted link is needed by responding with the error code Insufficient Authentication on a characteristic read or write from the Central. The iOS Central will then initiate pairing and encrypt the link. > > Thanks, > Joakim > > On Sep 10, 2012, at 5:43 AM, Jimmy Adler wrote: > >> The device I am communicating with requires an encrypted link to be setup in order for the device to allow access to most of its services, a Characteristic needs to be fed with a passkey in order for access to be granted and this has to be done over an encrypted link. >> >> How do I initiate such an encrypted link after connecting to the device using CoreBluetooth? >> >> I would assume it to be a function attached to CBPeripheral or CBCentralManager, but I cannot find any such functions there, unless it is an option of some sort that I have missed. >> >> Is it possible at all? >> >> Br, >> >> Jimmy Adler > _______________________________________________ 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: Is encrypted link supported in CoreBluetooth?
by Joakim Linde 10 Sep '12

10 Sep '12

Hi Jimmy, The Peripheral may indicate to an iOS Central that an encrypted link is needed by responding with the error code Insufficient Authentication on a characteristic read or write from the Central. The iOS Central will then initiate pairing and encrypt the link. Thanks, Joakim On Sep 10, 2012, at 5:43 AM, Jimmy Adler wrote: > The device I am communicating with requires an encrypted link to be setup in order for the device to allow access to most of its services, a Characteristic needs to be fed with a passkey in order for access to be granted and this has to be done over an encrypted link. > > How do I initiate such an encrypted link after connecting to the device using CoreBluetooth? > > I would assume it to be a function attached to CBPeripheral or CBCentralManager, but I cannot find any such functions there, unless it is an option of some sort that I have missed. > > Is it possible at all? > > Br, > > Jimmy Adler _______________________________________________ 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

Is encrypted link supported in CoreBluetooth?
by Jimmy Adler 10 Sep '12

10 Sep '12

The device I am communicating with requires an encrypted link to be setup in order for the device to allow access to most of its services, a Characteristic needs to be fed with a passkey in order for access to be granted and this has to be done over an encrypted link. How do I initiate such an encrypted link after connecting to the device using CoreBluetooth? I would assume it to be a function attached to CBPeripheral or CBCentralManager, but I cannot find any such functions there, unless it is an option of some sort that I have missed. Is it possible at all? Br, Jimmy Adler _______________________________________________ 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: writeValue:forCharacteristic:type: always fails when using 128-Bit UUIDs on iOS 6 beta 4
by Florian Schulz 06 Sep '12

06 Sep '12

Etan, thank you so much for reply, the problem really lied within our GATT-database - the permissions weren't set correctly. On iOS 5, CoreBluetooth ignores that error. Your answer saved us from a lot of trouble. Best regards, Florian Am 05.09.2012 um 14:02 schrieb Etan Kissling <kissling(a)oberon.ch>: > Florian, > > I have tested 128-bit UUIDs on iOS 6 Beta 4 and did not encounter such problems. > In my case, a CSR 1000 chip was used as peripheral, and a new iPad as well as an > iPhone 4S were used as centrals. I am using both 128-bit and 16-bit UUIDs for > primary services and characteristics. I am also using only short characteristics with > less than or equal 20 bytes of payload. > > What you could do is to use the TI packet sniffer software to get an air trace. > CoreBluetooth does not expose valuable information in the error-objects. > Therefore, the air trace could provide you with further information on what > could go wrong in your case. > > Could it be that your GATT-database is malformed? > And do BLE tools from the AppStore also encounter errors when writing to your > characteristics? > > Etan > > > On 05.09.2012, at 13:51, Florian Schulz <florianschulz(a)me.com> > wrote: > >> Hi, >> >> We are developing accessory hardware implementing the peripheral role - our app acts as the central. We are using the TI CC2540 chip for BLE on our hardware. >> >> Recently we discovered a major issue regarding iOS 6. On iOS 6 beta 4 writing values using writeValue:forCharacteristic:type: always fails, when we don't use standard profile UUIDs. We are using 128-Bit UUIDs for either our custom services and characteristics. We also tried using a 128-Bit UUID just for the service, and 16-Bit UUIDs for the characteristics with no success. The didWriteValueForCharacteristic: callback is fired immediately after starting the write request. An error object is passed to that callback, saying that the operation couldn't be completed: >> peripheral:didWriteValueForCharacteristic:error: Code: 0 Domain: >> CBErrorDomain Description: Unknown error. >> >> The write has no effect. On iOS 5.1.1 writing values using 128-Bit UUIDs works fine. We don't know exactly if the error only exists since iOS 6 beta 4, or if it was present on previous iOS 6 builds as well. >> >> This is a critical issue for us, since we are about to start mass production of our hardware. >> >> Is this behavior caused by a change in iOS 6 that will find its way to the final release, or is this a beta issue? >> >> Best Regards, >> Florian >> _______________________________________________ >> 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/etan.kissling%40obero… >> >> This email sent to etan.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/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0