Connect to phone in background

RE: Connect to phone in background

Vaibhav Aggarwal — Fri, 12 May 2017 02:40:54 GMT

These are mine, but only because I don't need high throughput. You will have to adjust according to your usecase. I am working on iOS 10, but it should work for most of them.

#define MIN_CONN_INTERVAL_MS   150
#define MAX_CONN_INTERVAL_MS   200
#define SLAVE_LATENCY		   4
#define CONN_SUP_TIMEOUT_MS    6000

RE: Connect to phone in background

Julian — Fri, 12 May 2017 02:15:09 GMT

Same issue with me and I am using the apple specs. Vaibhav, which iOS version are you using? Could you share your GAP parameters? Thank you

RE: Connect to phone in background

Vaibhav Aggarwal — Thu, 11 May 2017 16:37:39 GMT

Yes, the issue was with tweaking my GAP parameters. Make sure they are within the range specified by Apple. Look at section 3.6 here

RE: Connect to phone in background

hagar — Thu, 11 May 2017 12:26:03 GMT

@Vaibhav Aggarwal Did you manage to solve this? I am having the same problem here and any help would be really appreciated. Thanks!

RE: Connect to phone in background

Hung Bui — Thu, 08 Sep 2016 13:27:15 GMT

You can test the sniffer like this:

You put your app in background mode
You turn on your device, let it advertise
The app won't connect to your device as you described as the issue. You can use the sniffer to follow the device
Check if there is any connection request when the app is in background
Wake the app up to foreground and see if how it's connected.

Which type of address do you have ? Please take a screenshot of the normal device and your device.

Please be noted that, besides advertising, the nRF5 can't do anything else to interact with the phone unless the phone connect to it.

RE: Connect to phone in background

Vaibhav Aggarwal — Thu, 08 Sep 2016 08:28:06 GMT

@Hung Bui I have a sniffer and there is a difference in "randomized tx address" bit in the ADV_IND packet header. Do you know how to set this? Other than that, the adv packet is essentially the same, and my peripheral can communicate with the app only when the app is in the foreground, so it probably isn't an issue with advertisement since other peripherals wouldn't advertise differently since they wouldn't know when to connect to mobile app in the background or foreground. It's sort of hard to use a sniffer to catch packets when connecting in the background since the moment I turn on the device it immediately connects to the app before I can configure the sniffer. Is there a way around this issue? Thanks for the help!

RE: Connect to phone in background

Hung Bui — Thu, 08 Sep 2016 07:33:16 GMT

@Vaibhav: You may need to have a look at the sniffer trace to figure out why it connects to other devices but not yours.

We need to check if the app/phone actually connect to the nRF5 or not. If it doesn't then it could be that the flag or something are different from what other device advertise to the phone doesn't send connect request.

RE: Connect to phone in background

Vaibhav Aggarwal — Wed, 07 Sep 2016 20:34:03 GMT

I'm attempting to get my peripheral to work with an app that already exists and I don't have control over. Other peripheral devices can connect with it in the background but my nRF52 peripheral can't and needs the app to come into the foreground. This is on iOS. Is there some sort of setting or callback for the nRF52 to handle background connection or something? Thanks!

RE: Connect to phone in background

Hung Bui — Wed, 07 Sep 2016 13:08:01 GMT

@Vaiblhav: Are you talking about iOS or Android ? On Android you can create a background service, like this

For iOS you may want to have a look at this.