| afa6e1abbedaad8fe854b0f43999b8aeb801af91 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of e8c3d75b to master
Change-Id: I78ef69c4d54a36243620ae14296d3507e3339567
|
| 93912473fde12ab5ab4b1be8774bbf43d47c7ddc |
|
26-Jun-2014 |
Mike Lockwood <lockwood@google.com> |
Merge some missing pieces of AVRCP controller support from klp-wireless-dev
Change-Id: I1dc99496a6ed0e7d13cab9d7c95972d32ad88769
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| e8c3d75b75493911ebf0f99c83676359657178f7 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: BTIF and APPL.
Change-Id: I5b1214642bbb4b9aecc0fd2c899a6ec2c9793286
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 4ad470e33021be4246ae539e1bcb7a346dbb4405 |
|
03-Jun-2014 |
Mike Lockwood <lockwood@google.com> |
Move AVRCP controller support to separate HAL interface
Change-Id: Ib7dcd7b90f85cf3b25148e2929d8921c6db37aa2
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 3a1ca50d0def4078a0db82bcdeecfe408ca4af64 |
|
03-Jun-2014 |
Mike Lockwood <lockwood@google.com> |
Move AVRCP controller support to separate HAL interface
Change-Id: Ib7dcd7b90f85cf3b25148e2929d8921c6db37aa2
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 44c6f8d6c7cb3929a5b49e5d0ef8c471798f552f |
|
07-Feb-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
[2/4] Add Support for AVRCP Controller Feature
- Provide support for AVRCP Controller CAT 1 and CAT 2
Passthrough commands.
Change-Id: Ia3ca08c1139d9a98b86919b51d7480e0245c35f3
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 68c53ded6523113ddcc1932fa5bcb7d378b12209 |
|
13-Feb-2014 |
Nitin Srivastava <nitinsr@codeaurora.org> |
Bluetooth: Clear Notification array on AVRCP disconnect
DUT does not clear previous AVRCP notification registration
on AVCTP disconnect hence DUT sends response even when remote
device hasn't registered.
Changes made to clear notification array and while sending
notification respose check if event is registered.
Change-Id: I610f8ae6381a63236378f179bb2a619ec0c6549e
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| ad0b6c784a5684812f828b68fd8b5f952c62a443 |
|
13-Feb-2014 |
Nitin Srivastava <nitinsr@codeaurora.org> |
Bluetooth: Clear Notification array on AVRCP disconnect
DUT does not clear previous AVRCP notification registration
on AVCTP disconnect hence DUT sends response even when remote
device hasn't registered.
Changes made to clear notification array and while sending
notification respose check if event is registered.
Change-Id: I610f8ae6381a63236378f179bb2a619ec0c6549e
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 73e68297292dd901a170bcf6434ed0a10f1ec450 |
|
07-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
flounder64: bluetooth: Adjust volume level on BT HS and DUT side
MW600 Bluetooth address is "58:17:0c:e8:b0:7a". It is not included in
AVRCP profile white list. So it can't support absolute volume. We need
to whitelist it by device name "MW600" instead device address method.
Signed-off-by: Thomas.TT_Lin <Thomas.TT_Lin@htc.com>
Change-Id: I41b27fbab13dcf9d0005e8d5ae25ffb95eb546d4
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| d2ccbbb73c7851d2fa28dc212d2fffc0ad4e5d50 |
|
13-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Remove executable bit on source files.
Change-Id: Id456478aea626f57fed3479346e8fb4dbd0fafa6
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| c9fbcde6d2077ee03dc497824cd98e4d782f7cea |
|
07-Apr-2014 |
Thomas.TT_Lin <Thomas.TT_Lin@htc.com> |
flounder64: bluetooth: Adjust volume level on BT HS and DUT side
MW600 Bluetooth address is "58:17:0c:e8:b0:7a". It is not included in
AVRCP profile white list. So it can't support absolute volume. We need
to whitelist it by device name "MW600" instead device address method.
Signed-off-by: Thomas.TT_Lin <Thomas.TT_Lin@htc.com>
Change-Id: I41b27fbab13dcf9d0005e8d5ae25ffb95eb546d4
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 5cd8bff2dd0337cb52bf48f312e3d2d55a8882fb |
|
01-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Major warnings cleanup
Mostly fixing unused parameter warnings.
A few other warnings also fixed like possible use of
unitialized variables (no real issue found, just compiler couldn't
follow the path), signed vs unsigned warning.
Also fixed some typos, indent issues, removal of dead code, etc.
Change-Id: I95eb887aefc4d559d7921f71a0af5f3bfb01ac01
Signed-off-by: Mike J. Chen <mjchen@google.com>
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 7850a939f3c33a0bada9b9e2cd335189614a5ef9 |
|
06-Nov-2013 |
Matthew Xie <mattx@google.com> |
whitelist well tested devices for absolute volume feature
We are blacklisting all the devices that are not in whitelist
instead of blacklisting known bad devices.
bug 11124170
Change-Id: I044970df611d2a800d7698d4a63331644ab107ce
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| a7ae4a15e954fe143326d4f869f8dac8e76ee8ce |
|
24-Oct-2013 |
Matthew Xie <mattx@google.com> |
Blacklist Devices that donot handle absolute volume well
Use vendor prefix address, include hbs730 headset, passat carkit
bug 11124170
Change-Id: I80f634366ce332c55581d7b1e36641e5ce3ad346
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 247c68fe6eee3660cbdcf4509195fe735ae25573 |
|
01-Aug-2013 |
Satya Calloji <satyac@broadcom.com> |
Add support for AbsoluteVolume
Add support for AbsoluteVolume in BTIF
bug 9595622
Change-Id: I11b707f6ab50d31bd11e879b0ebe5ad5bac54ad9
Conflicts:
btif/src/btif_rc.c
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 98497a520010fc996a8ce490665cac6c1439dd2d |
|
25-Jun-2013 |
John Du <johnldu@google.com> |
Add support for ff/rew
Change-Id: I017a7ddc9f7255d84ad8bf3284fefc1b7040900f
(cherry picked from commit 342bdf540d8c183d14ec5fb436b73cd979df3a8f)
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| b88fc6cb5636c4af17077502fe3313ffb32d93ee |
|
02-Apr-2013 |
Ravi Nagarajan <nravi@broadcom.com> |
Add support for PLAY_POS_CHANGED
Enable PLAY_POS_CHANGED support in get capabilities
Change-Id: I8f41209fe5be5345826136f14434488524e7b1bb
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 841e5b5092bcdbc1acffd6cf7255ec423fe15fdb |
|
22-Mar-2013 |
Ravi Nagarajan <nravi@broadcom.com> |
Reject element attribute request if count is 0xff
Updates from review. BTRC_MAX_ELEM_ATTR_SIZE set back to 7 and handled
invalid attribute count (oxff) in BTIF
Change-Id: Id2610c7882c4bc8aca04491d81b9b2c35f0682d0
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 081d6e548bed5a91c0ba9abda518c06a1b0ba7f5 |
|
30-Mar-2013 |
Zhihai Xu <zhihaixu@google.com> |
need send reject response to unsupported Avrcp 1.3 command
Without this change, some carkit will stuch waiting for response and crash.
Change-Id: I710f69077e400830a9cedd540bef5d51dc468272
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 9adddf4965e9ddb01e339b934c343fcbd842a977 |
|
06-Mar-2013 |
Ravi Nagarajan <nravi@broadcom.com> |
Initial version of Stack for AVRCP 1.3
BTIF and stack changes for supporting AVRCP 1.3
Change-Id: Id02eb7b6a385683cedc41c62b6f829f5d7620bd4
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|
| 5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/external/bluetooth/bluedroid/btif/src/btif_rc.c
|