Re: Bluetooth device/service caching
Re: Bluetooth device/service caching
- Subject: Re: Bluetooth device/service caching
- From: Stuart Smith <email@hidden>
- Date: Mon, 09 Feb 2015 14:21:14 -0800
- Thread-topic: Bluetooth device/service caching
don't you have control over the device's address?
If mode1 and mode2 advertise different addresses, their respective
services and characteristics will be in different caches. Effectively, you
have two entirely separate servers (as far as Core Bluetooth is
concerned). CB doesn't have to know that these two servers share an
antenna, a radio, a micro-controller and firmware.
Stuart
On 2/9/15, 12:00 PM, "email@hidden"
<email@hidden> wrote:
>Date: Mon, 09 Feb 2015 15:34:58 +0000
>From: Nick Brook <email@hidden>
>To: "email@hidden Bluetooth"
> <email@hidden>
>Subject: Bluetooth device/service caching
>Message-ID: <email@hidden>
>Content-Type: text/plain; charset=utf-8
>
>Hi,
>
>We’ve built a bluetooth device that operates in two different modes.
>
>In mode 1 it advertises as a custom Bluetooth Low Energy device and our
>application connects through CoreBluetooth.
>
>When switched to mode 2 it advertises as a HID keyboard, which can be
>connected in iOS settings.
>
>We are encountering a problem where connecting via mode 1 and then
>switching to mode 2 can result in iOS connecting via both methods, as it
>is paired to the device and the App always requests a connection to known
>BTLE devices. Is there anything we can do to prevent iOS connecting via
>CoreBluetooth when the device is acting as a HID keyboard?
>
>Thanks
>Nick
>
_______________________________________________
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