Apple

On 08.07.2013, at 19:03, Stefan Damm <email@hidden>

wrote:

I've talked to our hardware developer and it seems that I misunderstood him a little bit. The problem is that we are not able to request a vendor specific UUID (128bit) from BT SIG because they did not introduce a way to do this.

There are a lot of devices out there that hijack 16bit standard UUIDs (e.g. Heart Rate, Blood Pressure) to get around this. Is this something Apple would allow or tolerate?

Stefan

Runtastische Grüße · Runtastic regards

Stefan Damm
Head of iOS Development

runtastic GmbH
Pluskaufstraße 7 · Business Center
4061 Pasching / Linz (Austria)
Tel. +43(0)650.9133838
Fax. +43(0)7229.23327
email@hidden
www.runtastic.com

Sent with Sparrow

On Monday, 08. July 2013 at 18:55, Etan Kissling wrote:

MFi is not required for BLE accessories.

The custom services somehow "guarantee" that your peripheral won't interfere with other apps.

With classic BT, there's the problem that many peripherals use the SPP profile for different purposes,

with no clean way to distinguish between them. Therefore, MFi is necessary there.

On 08.07.2013, at 18:42, Stefan Damm <email@hidden>

wrote:

Hi,

we are creating our own custom service for a BLE hardware we want to use in our iOS app. Does anybody know if we need to apply for the MFI program when we use a custom UUID?

I know that usually there is no need to apply for MFI if you connect BLE hardware with the pre defined services like Heart Rate or Blood Pressure. But does this also apply for custom services?

Thanks in advance

Stefan Damm

_______________________________________________

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

References:
	>MFI for Bluetooth Low Energy Custom Services (From: Stefan Damm <email@hidden>)
	>Re: MFI for Bluetooth Low Energy Custom Services (From: Etan Kissling <email@hidden>)
	>Re: MFI for Bluetooth Low Energy Custom Services (From: Stefan Damm <email@hidden>)