892172 - [B2G][User Story] Create framework to enable partners/developers to add new BT Profiles on BLE

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Bluetooth, defect)

Description

[Sandip Kamat]

As a developer (or a partner), I would like to add an additional Bluetooth profile to FxOS based product software. This is a request to create that enabler framework.

Comment 1

[Kai-Chih Hu [:khu]]

Can we have someone to own this user story bug? Thanks.

Comment 3

[Eric Chou [:ericchou] [:echou]]

Hand over to Ben, the owner of API refinement.

Go for it, Ben!

Comment 4

[Ben Tian (inactive)]

As more and more applications require BLE profiles to communicate with peripheral devices, we decide to support GATT client API first to enable partners/developers to add new BT profiles on BLE. The GATT client API will be based on refined WebBluetooth API (bug 1005848).

Change bug title and dependency accordingly.

Comment 5

[Olof Wickström]

Will this bug solve the following issue?

Mozilla has declared that 1.2 supports AVRCP 1.3. "Users can control media playing and get playing status via Bluetooth. (bug 892164) (bug 892165)"
This is not true from a user and third party app developer perspective if AVRCP does not work with any media player.

Tagged as blocking-b2g:2.1? as our investigation indicates that the AVRCP API are limited to certified apps.

Comment 6

[Eric Chou [:ericchou] [:echou]]

Hi Olof,

(In reply to Olof Wickström from comment #5)
> Will this bug solve the following issue?
> 
> Mozilla has declared that 1.2 supports AVRCP 1.3. "Users can control media
> playing and get playing status via Bluetooth. (bug 892164) (bug 892165)"
> This is not true from a user and third party app developer perspective if
> AVRCP does not work with any media player.
> 

When we declared we 'support' a Bluetooth profile, we didn't actually mean that any related API would be exposed to 3rd party apps. In fact, we haven't exposed any Bluetooth API (including on/off, search, pair, HFP functions) for non-certified apps until now. To me it's just a misunderstanding of how we define the term 'support', so I hope my explanation makes it more clear.

Moreover, I know that you want to know if there is any chance to have AVRCP API for 3rd party apps so that you set blocking-b2g flag to 2.1. However it would be a long process for exposing a set of privileged API since every little detail should have been reviewed. 

If you have any comments about how we should modify our Wiki page (https://wiki.mozilla.org/B2G/Bluetooth#Supported_Bluetooth_Profiles) to not confuse other people, please feel free to revise by yourself or tell us how to modify.

Comment 7

[Dietrich Ayala (:dietrich)]

Triage reviewed - this is a new feature, which does not block releases per the criteria at https://wiki.mozilla.org/B2G/Triage#Blocker_Triage_Guidelines. Clearing nom.

Comment 8

[Aaron Wu]

[Blocking Requested - why for this release]:Nominate this in 3.0

Comment 9

[Aaron Wu]

marked as 2.5+

Comment 10

[Ben Tian (inactive)]

Resolve this bug since all dependent bugs are resolved.