Hello,
Our BLE accessory is only used when an app is active. It
makes a lot of sense to put it in a lower power state when the
app moves to the background
Our app sends a message to the accessory when it is time to
switch connection parameters. The accessory then makes a
standardL2CAP Connection Parameter Update Request for a longer
connection interval.
I can see using a sniffer that iOS 5.1 immediately accepts
the connection parameter update request, and sends the
LL_Connect_Update_Req with the new interval, but the 'Instant'
it chooses to make the switch (the connEventCount) can be fairly
far in the future.
As a result, when switching back to the app, I will typically
see a delay of about 10 seconds before the accessory has
switched back to a faster connection and becomes usable. That's
too long for a user to wait, so I'm working on
disconnecting/reconnecting the accessory instead to see if
that's faster.
Does this sound about right? Are there any guidelines that
will allow these connection update transactions to happen
faster?
Thanks,
Peter Skinner
Ten One Design
201-965-0200
_______________________________________________
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