Apple

Le 19 nov. 2013 à 16:30, András Kövi <email@hidden> a écrit :

I've been testing a very similar setup where the peripheral is sleeping and wakes on a trigger. Then it starts advertising with 20ms interval. The advertisement theoretically wouldn't even be a requirement, only discoverability as the iOS side is hanging on the connectPeripheral call. With this setup the iOS device connects in 4-10 seconds reliably. I haven't had a single case yet when it failed when Core Bluetooth was operational.

I added this info just to confirm that your use case should work and there may be some other issues behind the long connection times.

2013/11/19 Etan Kissling <email@hidden>

Could it be that you are scanning at the same time, when it is slow?

Or maybe a different app that is scanning?

Do WiFi / 3G toggles change the probabilities of a slow connection?

Any other apps open with big memory consumption?

On 19.11.2013, at 14:26, Alpwise iOS Dev <email@hidden> wrote:

Hello,

In fact, my app first connect in foreground, and with this code:

-(void)centralManager:(CBCentralManager *)central didDisconnectPeripheral:(CBPeripheral *)peripheral error:(NSError *)error

{

[central connectPeripheral:peripheral options:nil];



/*

   *

   ...

   */

}

the app always try to reconnect (the connect request never timed out, even in background).

I have a fast connection 60% of the time but (very) slow in the other 40%.

Sam

Le 19 nov. 2013 à 13:49, David Chu <email@hidden> a écrit :

Hey Sam,

Can you show how you are using -connectPeripheral:options to reconnect in the background?

Dave

On Nov 19, 2013, at 5:44 PM, Alpwise iOS Dev <email@hidden> wrote:

I don't use the scan in background, i directly send a connect request to the peripheral (Once discovered for the first time, i save the identifier).

Thanks,

Sam

Le 18 nov. 2013 à 18:34, Darren Jones <email@hidden> a écrit :

I believe this is expected behaviour when backgrounded to conserve battery. I think the docs say something along the lines of "scanning can take considerably longer"

Sent from my iPhone

On 18 Nov 2013, at 17:26, Alpwise iOS Dev <email@hidden> wrote:

Hi,

I develop an application (the phone is central) that try to connect to a remote device in background.
When my peripheral starts advertising, most of the time, the app (in background) can connect in 1 second.
But sometimes, it takes up to 60 seconds.

Does someone have the same issues?

I use an iPhone 4S with iOS 7.0 .

Thanks,

Sam
_______________________________________________
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

References:
	>Background Connection Latency (From: Alpwise iOS Dev <email@hidden>)
	>Re: Background Connection Latency (From: Darren Jones <email@hidden>)
	>Re: Background Connection Latency (From: Alpwise iOS Dev <email@hidden>)
	>Re: Background Connection Latency (From: David Chu <email@hidden>)
	>Re: Background Connection Latency (From: Alpwise iOS Dev <email@hidden>)
	>Re: Background Connection Latency (From: Etan Kissling <email@hidden>)
	>Re: Background Connection Latency (From: András Kövi <email@hidden>)