November 2012 - Bluetooth-dev

Re: Making a peripheral app
by Kelvin Kakugawa 04 Nov '12

04 Nov '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Making a peripheral app
by Rick Mann 04 Nov '12

04 Nov '12

Hi. I'm looking at the docs, and I don't see a proper Core Bluetooth programming guide, just the reference docs. In any case, is there a place to look if I want to make a peripheral device? It strikes me that it might be easier to simulate my BTLE device as an app on an iPhone, to allow getting started on the iOS app that will talk to it. That way, I don't have to wait as long for the hardware to be ready. >From the CoreBluetooth 101 presentation, I know I can make a peripheral/server in iOS 6. The CBPeripheral class seems to exist for representing an external device connected. Then again, these reference docs don't provide very much info. Anywhere else I should look? Thanks! -- Rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: cancelPeripheralConnection misbehavior?
by Andras Kovi 03 Nov '12

03 Nov '12

Hi Etan, yes, I know, this is the ordinary way of handling things. I understand that the client app should hold the reference as long as it may encounter it. But the framework helps itself and calls the didDisconnect with the correct peripheral, it is just creates a new object for it. I know this is not going to change any time soon, it's just annoying to deal with. Additionally, I have not seen it documented anywhere. A bigger problem is that the didDisconnect is not called every time the cancel is called. It depends on whether there is a connection pending for the peripheral (connecting/disconnecting), and this state is not visible in the CBPeripheral structure. So, this is another state the app has to take care of while the framework handles it as well. I feel this could be simplified by exposing this "connectionPending" property together with the isConnected. Thanks, Andras On 2012.11.03., at 20:38, Etan Kissling <kissling(a)oberon.ch> wrote: > Try setting the peripheral reference to nil after receiving the diddisconnect callback instead of when you cancel connection. > > On 03.11.2012, at 15:15, "Andras Kovi" <allprog(a)gmail.com> wrote: > >> I observed that after I cancel a peripheral connection and set the peripheral reference to nil, the peripheral object is collected by ARC and a warning is shown that the peripheral was still in use (disconnecting if it was connected earlier). >> >> So I have two questions: >> 1. Can I turn this warning off? If I cancel a peripheral connection, I don't care what happens to the peripheral object later. >> >> 2. If I have to be aware of the connecting and disconnecting states, then why isn't there a flag on CBPeripheral that shows it? Every application will have to reimplement this anyway. >> >> Thanks, >> Andras >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch >> >> This email sent to kissling(a)oberon.ch _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: cancelPeripheralConnection misbehavior?
by Etan Kissling 03 Nov '12

03 Nov '12

Try setting the peripheral reference to nil after receiving the diddisconnect callback instead of when you cancel connection. On 03.11.2012, at 15:15, "Andras Kovi" <allprog(a)gmail.com> wrote: > I observed that after I cancel a peripheral connection and set the peripheral reference to nil, the peripheral object is collected by ARC and a warning is shown that the peripheral was still in use (disconnecting if it was connected earlier). > > So I have two questions: > 1. Can I turn this warning off? If I cancel a peripheral connection, I don't care what happens to the peripheral object later. > > 2. If I have to be aware of the connecting and disconnecting states, then why isn't there a flag on CBPeripheral that shows it? Every application will have to reimplement this anyway. > > Thanks, > Andras > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch > > This email sent to kissling(a)oberon.ch _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: terminating a connection from a peripheral
by Andras Kovi 03 Nov '12

03 Nov '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

cancelPeripheralConnection misbehavior?
by Andras Kovi 03 Nov '12

03 Nov '12

I observed that after I cancel a peripheral connection and set the peripheral reference to nil, the peripheral object is collected by ARC and a warning is shown that the peripheral was still in use (disconnecting if it was connected earlier). So I have two questions: 1. Can I turn this warning off? If I cancel a peripheral connection, I don't care what happens to the peripheral object later. 2. If I have to be aware of the connecting and disconnecting states, then why isn't there a flag on CBPeripheral that shows it? Every application will have to reimplement this anyway. Thanks, Andras _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Refreshing local name of an already discovered Peripheral
by Sandro Baechler 03 Nov '12

03 Nov '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

terminating a connection from a peripheral
by Bob Frankel 02 Nov '12

02 Nov '12

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: bluetooth-central/bluetooth-peripheral apps terminated from suspended state – workaround?
by Jason Conn 02 Nov '12

02 Nov '12

We're aware of this issue and are trying to come up with a solution. Currently, there is no workaround. On Nov 2, 2012, at 8:52 AM, Tammo Freese <tammo(a)tammofreese.de> wrote: > Hi, > > I am experimenting with one app acting as a bluetooth-peripheral, and another one (for testing the peripheral) as bluetooth-central. > > Both run fine in background (central: scanning, peripheral: advertising). More precisely, the apps seem to be suspended in background after a few seconds, but iOS continues advertising/scanning, as I can connect both apps in the background. > > However, the problem I experience with both applications is that they are terminated from the suspended state when memory runs low, advertising and scanning stop. > > Is there any way to work around that so that the apps continue to advertise/scan? > > Thank you, > Tammo > > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/conn%40apple.com > > This email sent to conn(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

bluetooth-central/bluetooth-peripheral apps terminated from suspended state – workaround?
by Tammo Freese 02 Nov '12

02 Nov '12

Hi, I am experimenting with one app acting as a bluetooth-peripheral, and another one (for testing the peripheral) as bluetooth-central. Both run fine in background (central: scanning, peripheral: advertising). More precisely, the apps seem to be suspended in background after a few seconds, but iOS continues advertising/scanning, as I can connect both apps in the background. However, the problem I experience with both applications is that they are terminated from the suspended state when memory runs low, advertising and scanning stop. Is there any way to work around that so that the apps continue to advertise/scan? Thank you, Tammo _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0