Re: BLE discover device while backgrounded
Re: BLE discover device while backgrounded
- Subject: Re: BLE discover device while backgrounded
- From: Marlon Smith <email@hidden>
- Date: Fri, 30 Nov 2012 10:54:21 -0800
Thanks for the helpful responses everyone. I was not setting a service to scan for, so I suspect that was the problem. I'll try making that change.
Mike, thanks for the reply. My eventual use case is to have the application connect to any device of a certain type, regardless of whether it has connected to that device before, so that may not work for me.
Actually taking it one step farther, I may not even need to make connections at all. I'd just like to collect advertising packet data and keep track of it.
Thanks again
Marlon
On Fri, Nov 30, 2012 at 3:54 AM, Michael Mallinson
<email@hidden> wrote:
If you know which device you want to connect to, simply issue a connection request to it while in the foreground and iOS will wake up your app when the device
comes into range and connects to it. This may be seconds, minutes or hours later. You don’t need to have an ongoing scan operation to do this.
Cheers,
Mike
Sorry, yes, Jacky is right. I was mistaken by the case when an iOS dev is sent to background, then it stops/delays (I couldn't figure out yet) sending the provided services.
Then the question is: do you set the service to scan for?
You must set a service id to scan in background.
Discover with service "nil" does not work.
--
Hi Marlon,
you should try removing service filtering from the scan options. This may solve the issue. However, as you noted, no official response from Apple has been received so far.
On 2012.11.29., at 23:55, Marlon Smith <email@hidden> wrote:
Hi everyone,
I'm using a TI BLE key fob, along with an application running on my ipod that will scan for and connect to the key fob. Everything works
fine until I start the scan and then background the application before powering up the keyfob. Even though I have set UIBackgroundModes = "bluetooth-central" in the application's info.plist, the didDiscoverPeripheral function never seems to be called when
in the background.
Reading through the documentation and the forums, I understand that it can take 55 times longer to discover a peripheral in the background.
However even after waiting much longer than that, the device never seems to be detected. If I bring the app back to the foreground, the key fob is detected instantly.
I've seen several posts outlining similar problems, but I haven't seen any solutions on this forum.
Can anyone shed some light on this?
_______________________________________________
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
_______________________________________________
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