Has the issue of connection problem after repeated connection/disconnect been fixed?
Has the issue of connection problem after repeated connection/disconnect been fixed?
- Subject: Has the issue of connection problem after repeated connection/disconnect been fixed?
- From: H E R C R O M <email@hidden>
- Date: Sat, 28 Sep 2013 11:21:27 +0800
Hi all,
For a long time I have been seeing this issue coming up from time to time. And I believe there are other people seeing the same issues. Bug reported but no true resolution, so I want to bring this up here and see if I get some attention.
The issue was first seen on iOS6, that after repeated connect/disconnect, sometimes iOS just either doesn't proceed service discovery after connection. So BLE device receives connection request and done, but discoverServices: simply gets no callback "didDiscoverServices:" and hence subsequent access of BLE service/characteristic can not be done. Rebooting BLE device doesn't help, restarting the app doesn't help, turning off then on Bluetooth switch doesn't help. The only way to recover is to reboot iOS device.
And from iOS7 beta 6 or GM I noticed a different issue. Again, after repeated connect/disconnect, when iOS sends connect request to BLE device and the device responds ACK, and then subsequent data packets sent from BLE device to iOS got "NACK"ed. At iOS side I see "connection timeout" error. And it still needs rebooting iOS to resolve.
This is quite annoying as the users usually blame poor stability of the BLE devices after being frustrated on trying to get the devices connected. But so far, the only cure is to reboot the iOS device, and I failed to find any workaround to avoid it in application design.
Hercrom
_______________________________________________
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