Lists

Open Menu Close Menu

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

Re: Bluetooth-dev Digest, Vol 12, Issue 120

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

Re: Bluetooth-dev Digest, Vol 12, Issue 120

Subject: Re: Bluetooth-dev Digest, Vol 12, Issue 120
From: Matthew Chung <email@hidden>
Date: Sat, 05 Dec 2015 13:15:57 -0800

Hi Richard,

Thanks for writing. Perhaps I am misunderstanding the cases in which restoration works. In sandy chapman's answer, he crossed out the part about scanning for peripherials. Given that, I assumed (incorrectly?) that caching the peripheral is not necessary, and that restoration would work in the case where a central, that was scanning without having discovered a peripheral, was killed.

I actually have been able to reproduce the restore case sandy described, but from his wording, I thought caching of the peripheral 'might' not be a necessary step.

Anyways, if you have any thoughts, it would be appreciated.

On Sat, Dec 5, 2015 at 12:00 PM, <email@hidden> wrote:

Send Bluetooth-dev mailing list submissions to
email@hidden

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.apple.com/mailman/listinfo/bluetooth-dev
or, via email, send a message with subject or body 'help' to
email@hidden

You can reach the person managing the list at
email@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bluetooth-dev digest..."

Today's Topics:

1. Re: ble restoration question (Richard Grundy)

----------------------------------------------------------------------

Message: 1
Date: Fri, 04 Dec 2015 16:04:48 -0500
From: Richard Grundy <email@hidden>
To: email@hidden
Subject: Re: ble restoration question
Message-ID:
<CABUOPwia=b8_wqna6-q06Un1xK14TUBNxcHddAJe1pJgPmou=email@hidden>
Content-Type: text/plain; charset="utf-8"

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 <http://trackhack.org/> and learn to
build awesome end-to-end solutions with our products.

<http://flomio.com>
*Richard Grundy | Chief Executive | * +1.954.553.6227 * | **
email@hidden
<email@hidden>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.apple.com/mailman/private/bluetooth-dev/attachments/20151204/62ade282/attachment.html>

------------------------------

_______________________________________________
Bluetooth-dev mailing list
email@hidden
https://lists.apple.com/mailman/listinfo/bluetooth-dev

End of Bluetooth-dev Digest, Vol 12, Issue 120
**********************************************

--

Matt Chung

VersaMe

email@hidden

310-210-0956

Pre-Order Now!

 _______________________________________________
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: Re: ble restoration question
Next by Date: Re: CBPeripheral object / identifier not unique for iOS device
Previous by thread: Re: ble restoration question
Next by thread: Re: CBPeripheral object / identifier not unique for iOS device
Index(es):
- Date
- Thread