Re: Bluetooth LE problems with new iOS devices?
Re: Bluetooth LE problems with new iOS devices?
- Subject: Re: Bluetooth LE problems with new iOS devices?
- From: Long LI <email@hidden>
- Date: Tue, 29 Jan 2013 23:45:35 +0900
In iOS6.1, the problem was fixed maybe.
works fine.
On Fri, Jan 25, 2013 at 11:34 AM, Long LI <email@hidden> 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 <email@hidden> 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" <email@hidden> 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
>> <email@hidden> 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:email@hidden]
>>> Sent: Monday, November 05, 2012 4:57 PM
>>> To: Michael Mallinson
>>> Cc: email@hidden
>>> 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
>>> <email@hidden> 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 (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>>
>>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>> _______________________________________________
>> 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
>>
_______________________________________________
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