Closed
Bug 1236841
Opened 8 years ago
Closed 8 years ago
Support Lollipop CAF implementation for Bluetooth headers
Categories
(Firefox OS Graveyard :: Bluetooth, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: _AtilA_, Assigned: _AtilA_)
References
Details
Attachments
(1 file)
No description provided.
Assignee | ||
Updated•8 years ago
|
Summary: [BluetoothdSupport Lollipop CAF implementation for → Support Lollipop CAF implementation for Bluetooth headers
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → jgomez
Assignee | ||
Comment 1•8 years ago
|
||
Because CAF is using another API for Bluetooth, we need a way for Lollipop devices to distinguish between CAF based devices (mostly Qualcomm devices), AOSP devices, or any other AOSP-like fork. So, we are going to add a flag in device configuration scripts to solve the problem, and modify Bleutoothd to support CAF headers depending on this flag.
Comment 2•8 years ago
|
||
Some CAF code uses Q_BLUETOOTH in the C preprocessor. We should define it in bluetoothd's Android.mk if the device flag is present.
Assignee | ||
Comment 3•8 years ago
|
||
Attachment #8704184 -
Flags: review?(tzimmermann)
Comment 4•8 years ago
|
||
Comment on attachment 8704184 [details] [review] PR for supporting Bluetooth CAF headers Thanks for this fix. I left a comment in the pull request.
Attachment #8704184 -
Flags: review?(tzimmermann) → review+
Assignee | ||
Comment 5•8 years ago
|
||
Fixed! https://github.com/mozilla-b2g/platform_system_bluetoothd/commit/bb356d6505f914347690c8143dbd03af427dd07e
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•