Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: ble restoration question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ble restoration question

Subject: Re: ble restoration question
From: Richard Grundy <email@hidden>
Date: Fri, 04 Dec 2015 16:04:48 -0500

Matt, something seems amiss with the steps to your proposed user experience. The original SO answer (by sandy chapman) expects that the central has actually discovered the peripheral in question before the BT connection is severed. In your case you suggest that the central is discovering peripherals, querying for services, etc but are you waiting to make sure this happens with your target peripheral before severing the connection?

It seems trivial but since querying for services takes longer than just discovering peripherals, you could easily be killing the central well before your target peripheral has been discovered and cached which means that the willRestoreState delegate will never get called upon advertising from that target peripheral.

my 2 cents.

Message: 1
Date: Thu, 03 Dec 2015 19:32:53 -0800
From: Matthew Chung <email@hidden>
To: email@hidden
Subject: ble restoration question
Message-ID:
<email@hidden>
Content-Type: text/plain; charset="utf-8"

I'm not able to get restoration working as I would like, and if anyone has
any suggestions, I would much appreciate it.

What I've done is I have gone through the first answer on this page
http://stackoverflow.com/questions/22412376/corebluetooth-state-preservation-issue-willrestorestate-not-called-in-ios-7-1
(by sandy chapman)
and have worked through the restoration steps except I have 2 ios 9
devices, one running a central and one a peripheral . Then I

1. have my central discover the peripheral, caching the peripheral
2. kill the app running the peripheral
3. tell the central to connect to the peripheral
4. kill my central using a SIGKILL button
5. relaunch my peripheral and advertise
6. see my NSLog("wahoo") that is in the willRestoreState delegate callback
write to the device log

I'd really like to get this working where the steps are closer to (assuming
central and peripheral have talked to each other before)

1. have my central scan for specific services
2. SIGKILL the central
3. relaunch my peripheral and advertise
4. see my NSLog("wahoo") in willRestoreState write to the device log

and according to the stackoverflow posting above, It seems like it should
work this way, since he says it works with just scanning. I've spent more
time on this than I'd like to admit, so any suggestions are appreciated.

--
*Matt Chung*
VersaMe <http://versame.com/>
email@hidden <email@hidden>
3 <720-273-9832>10-210-0956
*Pre-Order Now! <http://www.versame.com/>*

--

PS: Hang with us at TrackHack.org and learn to build awesome end-to-end solutions with our products.

Richard Grundy | Chief Executive | +1.954.553.6227 | 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

Prev by Date: ble restoration question
Next by Date: Re: Bluetooth-dev Digest, Vol 12, Issue 120
Previous by thread: ble restoration question
Next by thread: Re: Bluetooth-dev Digest, Vol 12, Issue 120
Index(es):
- Date
- Thread