• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

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 9, Issue 255
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bluetooth-dev Digest, Vol 9, Issue 255


  • Subject: Re: Bluetooth-dev Digest, Vol 9, Issue 255
  • From: Frederic Visticot <email@hidden>
  • Date: Thu, 06 Dec 2012 17:03:39 +0100

4. The Bluetooth Smart "Alert Notification Profile" is a perfect fit for BLE-based notification accessories, but using this requires that you have access to the data in the first place, which we do not.

Is there any Apple documentation regarding Alert Notification Profile ?
Is iPhone4S or later able to send this kind of "alert notification" when incoming call or incoming SMS?

Sorry but I'm quite lost with all difference BLE / Classic bluetooth :)

-Fred


On Tue, Nov 20, 2012 at 5: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: iOS6 access to SMS, email,    and call notifications using
      Bluetooth Smart / BLE (Alexander Traud)
   2. RE: iOS6 access to SMS, email,    and call notifications using
      Bluetooth Smart / BLE (Mark Davis)
   3. RE: iOS6 access to SMS, email,    and call notifications using
      Bluetooth Smart / BLE (ming huang)
   4. RE: iOS6 access to SMS, email,    and call notifications using
      Bluetooth Smart / BLE (Mark Davis)


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

Message: 1
Date: Tue, 20 Nov 2012 11:12:44 +0100
From: Alexander Traud <email@hidden>
To: Apple Bluetooth <email@hidden>
Subject: Re: iOS6 access to SMS, email, and call notifications using
        Bluetooth Smart / BLE
Message-ID: <CCD1162C.D3F4%email@hidden>
Content-Type: text/plain; charset=ISO-8859-1

Good summary!

> iOS6 supports the MAP profile over classical Bluetooth only and NOT
> Bluetooth Smart / Low Energy. MAP allows access to push notifications in
> general (incoming calls I¹m not sure about).

Calls are handled with the Hands-Free Profile (HFP). After (!) connecting
via SCO, you are able to use AT commands for call handling, call-lists and
caller-name display. When you need more detailed phonebook and call-lists,
you go for the Phone-Book-Access Profile (PBAP).

The current state of Bluetooth profiles in iOS 6:
<http://support.apple.com/kb/HT3647>
  HFP offers HD-Voice aka Wide-Band Speech (WBS; with mSBC codec)
  MAP offers MMS and SMS (no E-Mail access)
 PBAP offers Mobile Phone-Book (ME) not SIM

Earlier firmwares like the last iOS (version 3.1.3) for the original iPhone
included IrMC Level 2 for accessing the phone book, as well. Back then and
today the functionality of IrMC can be done in PBAP.

All these services are not Bluetooth Low-Energy (BLE) but classic profiles.
Links to specifications and other implementations, are on my website:
<http://www.traud.de/gsm/MAP.htm>
Hope too it helps someone.





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

Message: 2
Date: Tue, 20 Nov 2012 08:40:29 -0500
From: Mark Davis <email@hidden>
To: Jeff Rowberg <email@hidden>,    "email@hidden"
        <email@hidden>
Subject: RE: iOS6 access to SMS, email, and call notifications using
        Bluetooth Smart / BLE
Message-ID:
        <email@hidden>
Content-Type: text/plain; charset="utf-8"

Jeff;

I believe point 5 would be a bit more accurate stated this way:

5. As with other iOS-Supported Bluetooth profiles, a MFi license is not needed for using MAP...

And I'd add this point:
6. MAP is only available on iPhone 4 and later devices, running iOS 6

Regards,

Mark

From: bluetooth-dev-bounces+markd=email@hidden [mailto:bluetooth-dev-bounces+markd=email@hidden] On Behalf Of Jeff Rowberg
Sent: Monday, November 19, 2012 3:36 PM
To: email@hidden
Subject: Re: iOS6 access to SMS, email, and call notifications using Bluetooth Smart / BLE

Hey again everyone,

Thanks for the feedback on the topic of accessing calls, emails, and texts in Bluetooth applications. That info plus a lot more searching has given me a pretty solid answer. Here's a compilation of all relevant information I have found so far. The summary is this:
1. Accessing SMS, MMS, and emails through an iOS API directly is impossible, even in iOS6. This would break the "app sandboxing" rule Apple strictly enforces. Private APIs exist, but they're...well...private.

2. The ONLY exception to the above point is if your device is jailbroken, in which case it's completely open. This is not a good requirement for a retail accessory though, obviously.

3. iOS6 supports the MAP profile over classical Bluetooth only and NOT Bluetooth Smart / Low Energy. MAP allows access to push notifications in general (incoming calls I'm not sure about).

4. The Bluetooth Smart "Alert Notification Profile" is a perfect fit for BLE-based notification accessories, but using this requires that you have access to the data in the first place, which we do not.

5. MAP by itself works without requiring membership in MFI or any extra hardware, which is good, but it requires classic Bluetooth, which is a battery hog compared to BLE.
So, in short, for a feature-complete alert accessory TODAY (2012-11-19), you have to use Bluetooth classic and MAP. BLE won't work for everything, though it will work for anything you can get to through a public API. Hopefully iOS will add support soon for permission-based read-only access to call metadata and incoming messages. This is trivial in Android if the user grants permission when installing the app. iOS feels sorely lacking by comparison, especially with the exploding BLE market.

Now for the links, for reference:

Message Access Profile specification from Bluetooth SIG (Bluetooth classic only, no BLE support, also appears only to support SMS, MMS, + email, no calls)
https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=215400
Using Message Access Profile in various MAP-enabled cars, including iOS settings necessary
https://discussions.apple.com/thread/4343154?start=0&tstart=0
https://discussions.apple.com/thread/4315172?start=0&tstart=0
http://www.toyotanation.com/forum/310-7th-generation-2012/424034-iphone-4s-ios-6-bluetooth-map-profile.html

Alert Notification Profile info from Bluetooth SIG, perfect profile for this use case (as long as info is available)
http://developer.bluetooth.org/gatt/profiles/Pages/ProfileViewer.aspx?u=org.bluetooth.profile.alert_notification.xml
http://developer.bluetooth.org/gatt/services/Pages/ServiceViewer.aspx?u=org.bluetooth.service.alert_notification.xml
http://developer.bluetooth.org/gatt/characteristics/Pages/CharacteristicViewer.aspx?u=org.bluetooth.characteristic.new_alert.xml
https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=242286

Pebble forum discussion of iOS6 MAP support announcement, appears all push notifications are supported (not sure if this includes calls)
http://forums.getpebble.com/topics/560

Pebble forum discussion of lack of API support (two pages, especially page 2 is useful)
http://forums.getpebble.com/topics/517

Detecting call state from another app (only semi-possible if app is in foreground)
http://stackoverflow.com/questions/3319805/detecting-call-state-in-ios4

Detect foreground app about to become inactive, e.g. for incoming call:
http://developer.apple.com/library/ios/#documentation/uikit/reference/UIApplicationDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIApplicationDelegate/applicationWillResignActive<http://developer.apple.com/library/ios/#documentation/uikit/reference/UIApplicationDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIApplicationDelegate/applicationWillResignActive>:

Direct SMS access not possible in iOS:
http://www.tersus.com/?Id=6291

Direct SMS access not possible in iOS if not jailbroken:
http://stackoverflow.com/questions/10060834/interrupt-calls-smss-on-iphone-ios-5

Jailbroken device SMS interception info:
http://stackoverflow.com/questions/8680764/ios-jailbreak-how-do-intercept-sms-text-messages?rq=1

Jailbroken device SMS content reading info:
http://stackoverflow.com/questions/10681995/how-to-get-the-message-when-receiving-the-kctmessagereceivednotification-notif/11026338#11026338

Hope this helps some people.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.apple.com/mailman/private/bluetooth-dev/attachments/20121120/e4809fcc/attachment.html>

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

Message: 3
Date: Tue, 20 Nov 2012 15:17:11 +0000
From: ming huang <email@hidden>
To: email@hidden, email@hidden,
        email@hidden
Subject: RE: iOS6 access to SMS, email, and call notifications using
        Bluetooth Smart / BLE
Message-ID: <email@hidden>
Content-Type: text/plain; charset="windows-1252"


Hi,Now I got confused about the point 5:- Mark clearly stated that if you are a iOS 6 developer and not a MFi licensee, you can use MAP.- Previous emails by other people stated, but not specifically said, that if you are not a MFi licensee, then you cannot use MAP.
Would you please confirm which of my two understandings is correct?
ThanksMing

From: email@hidden
To: email@hidden; email@hidden
Date: Tue, 20 Nov 2012 08:40:29 -0500
Subject: RE: iOS6 access to SMS, email, and call notifications using Bluetooth Smart / BLE

Jeff; I believe point 5 would be a bit more accurate stated this way: 5. As with other iOS-Supported Bluetooth profiles, a MFi license is not needed for using MAP…  And I’d add this point:6. MAP is only available on iPhone 4 and later devices, running iOS 6 Regards, Mark From: bluetooth-dev-bounces+markd=email@hidden [mailto:bluetooth-dev-bounces+markd=email@hidden] On Behalf Of Jeff Rowberg
Sent: Monday, November 19, 2012 3:36 PM
To: email@hidden
Subject: Re: iOS6 access to SMS, email, and call notifications using Bluetooth Smart / BLE Hey again everyone, Thanks for the feedback on the topic of accessing calls, emails, and texts in Bluetooth applications. That info plus a lot more searching has given me a pretty solid answer. Here’s a compilation of all relevant information I have found so far. The summary is this:1. Accessing SMS, MMS, and emails through an iOS API directly is impossible, even in iOS6. This would break the “app sandboxing” rule Apple strictly enforces. Private APIs exist, but they’re…well…private. 2. The ONLY exception to the above point is if your device is jailbroken, in which case it’s completely open. This is not a good requirement for a retail accessory though, obviously. 3. iOS6 supports the MAP profile over classical Bluetooth only and NOT Bluetooth Smart / Low Energy. MAP allows access to push notifications in general (incoming calls I’m not sure about). 4. The Bluetooth Smart “Alert Notification Profile” is a perfect fit for BLE-based notification accessories, but using this requires that you have access to the data in the first place, which we do not. 5. MAP by itself works without requiring membership in MFI or any extra hardware, which is good, but it requires classic Bluetooth, which is a battery hog compared to BLE.So, in short, for a feature-complete alert accessory TODAY (2012-11-19), you have to use Bluetooth classic and MAP. BLE won’t work for everything, though it will work for anything you can get to through a public API. Hopefully iOS will add support soon for permission-based read-only access to call metadata and incoming messages. This is trivial in Android if the user grants permission when installing the app. iOS feels sorely lacking by comparison, especially with the exploding BLE market.
Now for the links, for reference:
Message Access Profile specification from Bluetooth SIG (Bluetooth classic only, no BLE support, also appears only to support SMS, MMS, + email, no calls)
https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=215400Using Message Access Profile in various MAP-enabled cars, including iOS settings necessary
https://discussions.apple.com/thread/4343154?start=0&tstart=0
https://discussions.apple.com/thread/4315172?start=0&tstart=0
http://www.toyotanation.com/forum/310-7th-generation-2012/424034-iphone-4s-ios-6-bluetooth-map-profile.html
Alert Notification Profile info from Bluetooth SIG, perfect profile for this use case (as long as info is available)
http://developer.bluetooth.org/gatt/profiles/Pages/ProfileViewer.aspx?u=org.bluetooth.profile.alert_notification.xml
http://developer.bluetooth.org/gatt/services/Pages/ServiceViewer.aspx?u=org.bluetooth.service.alert_notification.xml
http://developer.bluetooth.org/gatt/characteristics/Pages/CharacteristicViewer.aspx?u=org.bluetooth.characteristic.new_alert.xml
https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=242286
Pebble forum discussion of iOS6 MAP support announcement, appears all push notifications are supported (not sure if this includes calls)
http://forums.getpebble.com/topics/560
Pebble forum discussion of lack of API support (two pages, especially page 2 is useful)http://forums.getpebble.com/topics/517
Detecting call state from another app (only semi-possible if app is in foreground)http://stackoverflow.com/questions/3319805/detecting-call-state-in-ios4 Detect foreground app about to become inactive, e.g. for incoming call:http://developer.apple.com/library/ios/#documentation/uikit/reference/UIApplicationDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/UIApplicationDelegate/applicationWillResignActive: Direct SMS access not possible in iOS:
http://www.tersus.com/?Id=6291 Direct SMS access not possible in iOS if not jailbroken:http://stackoverflow.com/questions/10060834/interrupt-calls-smss-on-iphone-ios-5 Jailbroken device SMS interception info:http://stackoverflow.com/questions/8680764/ios-jailbreak-how-do-intercept-sms-text-messages?rq=1 Jailbroken device SMS content reading info:http://stackoverflow.com/questions/10681995/how-to-get-the-message-when-receiving-the-kctmessagereceivednotification-notif/11026338#11026338 Hope this helps some people.
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.apple.com/mailman/private/bluetooth-dev/attachments/20121120/a95b80c5/attachment.html>

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

Message: 4
Date: Tue, 20 Nov 2012 10:59:44 -0500
From: Mark Davis <email@hidden>
To: "email@hidden" <email@hidden>
Subject: RE: iOS6 access to SMS, email, and call notifications using
        Bluetooth Smart / BLE
Message-ID:
        <email@hidden>
Content-Type: text/plain; charset="utf-8"

Ming;

The key is the "iOS: Supported Bluetooth profiles", identified on http://support.apple.com/kb/HT3647.

These Bluetooth profiles are available to all  iOS developers, without any requirement for a MFi license.

These are "Bluetooth v2.1+EDR" profiles (what Jeff is calling "classic Bluetooth")... not Bluetooth LE.

Bluetooth devices that implement these "iOS-supported" profiles can communicate with relevant iOS facilities on an iOS device. This allows communications between the Bluetooth device and built-in apps included with the iOS operating system.  However, these "classic Bluetooth" profiles don't allow allow any direct communication between the Bluetooth device and user-developed apps.

With CoreBluetooth, Apple has provided a mechanism for iOS apps to communicate directly with Bluetooth LE devices, but this is independent of the "Bluetooth v2.1+EDR" ("classic Bluetooth") functionality.

If you want to develop a Bluetooth accessory that requires performance or features that can't be accomplished with Bluetooth LE, and that must communicate directly with a user-developed iOS app, then the accessory must be developed and manufactured under a MFi license agreement.

Regards,

Mark

From: ming huang [mailto:email@hidden]
Sent: Tuesday, November 20, 2012 10:17 AM
To: Mark Davis; email@hidden; email@hidden
Subject: RE: iOS6 access to SMS, email, and call notifications using Bluetooth Smart / BLE

Hi,
Now I got confused about the point 5:
- Mark clearly stated that if you are a iOS 6 developer and not a MFi licensee, you can use MAP.
- Previous emails by other people stated, but not specifically said, that if you are not a MFi licensee, then you cannot use MAP.

Would you please confirm which of my two understandings is correct?

Thanks
Ming

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.apple.com/mailman/private/bluetooth-dev/attachments/20121120/c1837db5/attachment.html>

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

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

End of Bluetooth-dev Digest, Vol 9, Issue 255
*********************************************

 _______________________________________________
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

  • Follow-Ups:
    • RE: Bluetooth-dev Digest, Vol 9, Issue 255
      • From: Mark Davis <email@hidden>
  • Prev by Date: Re: A program supports HFP on iPad
  • Next by Date: Re: Default connection interval
  • Previous by thread: Re: A program supports HFP on iPad
  • Next by thread: RE: Bluetooth-dev Digest, Vol 9, Issue 255
  • Index(es):
    • Date
    • Thread