Hi Steve,
We have encountered two bugs that result in a crippled BT stack:
1. After several connect/disconnects, the BT stack gets corrupted so we can scan but not perform deeper service queries or connections to BT peripherals. In this state, neither our app, the TI sample app, or the LightBlue app can access peripherals. This ones's isolated to 7.0, is known about by Apple, requires a reboot to reset the BT antenna, and is fixed in 7.1 beta.
2. In this case, we place our app in the background for 15+ mins then return to foreground and connect. After repeating this 5-10 times, the BT stack gets corrupted and we can only reset by rebooting the phone. Our BT sniffer trace shows iOS dropping the connection at discover services each time. We're testing further but can easily repeat this in 6.1, 7.0, and 7.1.
On Dec 11, 2013, at 3:16 PM, William Henderson < email@hidden> wrote: Wow, if you’ve got it down that fine you should file the bug (with that sample code for running the automated test)! Do you have a stack trace for the BT crash?
Our app also runs in peripheral mode.
William On December 11, 2013 at 3:13:42 PM, Steve Jabs (email@hidden) wrote:
William,
We've noticed it when running as the only app on our
device.
In our scenario we are the Peripheral. We set up an automated
test to connect to us, transfer some data, disconnect and restart
that process every 30 seconds. We can successfully crash the
Bluetooth on the device (iPod running iOS 7) every few hours.
Requires a restart of the device to reload Bluetooth.
Anyone else experiencing this?
Thanks,
Steve Jablonski
On Wednesday, December 11, 2013, William Henderson wrote:
Steve, have you noticed that this happens more (always?) when
multiple apps are using BTLE? I’ve only been able to reproduce
locally with multiple BTLE apps installed, and we noticed a big
up-tick in bug reports when the Apple Store app shipped their
BTLE/iBeacon feature...
--
William
On December 11, 2013 at 3:02:57 PM, Steve
Jabs (email@hidden) wrote:
Noticed the same. Currently have an item in my
current sprint to report a bug. However, I unfortunately have no
been able to retrieve any sort of a crash report around
this.
Anyone else have any ideas?
Thanks,
--
Steve Jablonski
p. (814) 720-9067
e. 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
|