| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
On platforms where HFP is disabled, we were incorrectly notifying
upper layer of HFP support in local uuids. Use the build config to
determine the right set of local UUIDs
bug 7232184
Change-Id: Ica308dd879336300714e97d3441334e16471359a
|
|
|
|
|
|
|
|
|
|
| |
On a Bluetooth chip h/w error, trigger an event from the core stack to
restart the Bluetooth process. This would ensure that any state is
cleaned up and the process starts from scratch
Bug: 7001800
Change-Id: I57b0b44276585e2ae3c22ddbcc9d80bd467135b2
Signed-off-by: Iliyan Malchev <malchev@google.com>
|
|
|
|
|
|
|
| |
Look for Local BDA at ro.bdaddr_path before reading it from BT Local storage path
Bug 7228514
Change-Id: Ib6d4b5321b1146d19f671d15c34df3a85b3a89d2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Reducing media timer tick prevents a2dp fragmentation
due to MTU size limitations in many headsets. This also
provides better robustness on poor rf links. * Adjusted
bitrate to 229 kbps which represents middle quality
setting in A2DP spec (bitpool 35 @ 44.1 khz). * Use fixed
estimated nbr sbc frames per a2dp packet and adjust only
using rate adjustment logic which would keep us within
~3 ms of the ideal rate
Bug 7161154
Change-Id: Ifd84e7ab9f5ac404162269dc4ad0e3a9b024e788
|
|
|
|
|
|
|
|
| |
Root cause for the bug is RC connection establishment before A2DP connection
and play command from carkit arriving in mid of A2DP connection.
Bug: 7131791
Change-Id: I74e7c456f68c5ab5a02e827c9a1e14d770f5ec2a
|
|
|
|
|
|
|
|
| |
First release under Apache source license with updated header files
and whitespace cleanups. Also fixed file permission to remove executable
bit from source files.
Change-Id: I7155903edfc2f491c1cbbd0db108f207852caaa0
|
|
|
|
|
|
|
|
| |
This reverts commit cc914cffd521b2e6e1be804c82aea2388b843ebf
More changes in the original CL after my cherry-pick.
Change-Id: Ic144dba96aeb8a60611baac7565c9f628ab8f9eb
|
|
|
|
|
|
|
| |
Also fixed file permission to remove executable bit
from source files.
Change-Id: I6954c2d16190bc35b1b0d38386543253696b1112
|
|
|
|
|
|
| |
Root cause: the service uuid is cached in memory, it could lost in case device crash or reboot
bug 7170559
|
|
|
|
|
|
|
|
| |
During BT disable, the BTIF AV media task was not shutdown cleanly, this
could result in bad state on subsequent BT enable.
bug 7142673
Change-Id: I6177baec5804720e96adcf9aa9445cc2bb438b07
|
|
|
|
| |
Change-Id: I22120a69273e5cd2b484009421f31df97d59b410
|
|
|
|
|
|
|
|
| |
During cleanup, we were not doing a pthread_join of the thread that was
created as part of the init API. The fix was to do a join during cleanup
bug 7083069
Change-Id: I48c7b597e969d08de36365abd6bbd321001b4e0d
|
|
|
|
|
| |
Bug:7074362
Change-Id: I76afb73e51e8f6ab1da8257ea004c8d7131e6884
|
|
|
|
|
| |
Bug: 7093571
Change-Id: I328b0a24ffa827a5a7d22f90ee8d476bd151675e
|
|
|
|
|
|
|
|
|
|
| |
By default stack will attempt to auto-pair with devices that match
a certain COD. If pairing fails, pairing will be retried with manual
user pin entry. The retry was limited to HCI error code 0x05 (auth
failure). Expanded this list to handle more error conditions
bug 7092121
Change-Id: I7c11d03b87350af597062cf77a296e340a929ef9
|
|
|
|
|
|
|
|
|
| |
bonded device 2
Root case: the adapter name property set/get with wrong section & key; The end condition of the loop to load bonded device is wrong
removed the wrong return value check when loading blacklist
Change-Id: Ib02d472311cd872befd17e6d2445f649f53f02fb
|
|\
| |
| |
| | |
file" into jb-mr1-dev
|
| |
| |
| |
| |
| | |
root cause: forgot to remove the device from storage when bound is canceled
Bug 7077419
|
|/
|
|
|
|
|
| |
Set NUMLOCK state for HID keyboards without NUMLOCK key to be ON
so that the numeric keypad can be used.
Change-Id: Ib9811d55cc62ba380c0418f0ac9ff3827b9a3c8a
|
|
|
|
|
|
| |
Add strings for DM event
Change-Id: I800780c181dd51cbf9bb037690ad167a5f8bf363
|
|
|
|
|
|
|
|
|
|
| |
Filter out hid device from bluez migration.
Change-Id: I8b5eb29f37ca37e97b728f69063266a1b0a61eb8
Conflicts:
main/Android.mk
|
|
|
|
|
|
|
|
| |
Ensure that Local name string is always Null terminated
when sending it to BT stack from BTIF layer
Bug:7027639
Change-Id: I319642d6073d4178bd34ca82431c4bda16270474
|
|
|
|
|
|
|
|
|
| |
Certain carkits (e.g Audi MMI 2801)send AVRCP Pause command right after
the call if there was an active music streaming when the call was answered.
This command needs to be ignored as Phone/MediaPlayer will take care of
music Play/pause after the call based on the state of the streaming before the call
Change-Id: Iddb50089bff0f54bc3ad9665f95e64d3083c568a
|
|
|
|
|
|
|
|
|
| |
is in progress
In mid of security upgrade, sending BOND_STATUS_BONDED to java dismisses
Pairing confirmation dialog and results in security upgrade failure.
Change-Id: If2a3858c6811eaa243f1c67d055862a634ccbb45
|
|
|
|
|
|
|
|
| |
Remove attr_mask field from bta_hh_api.c and bta_hh_act.c for
BTA_HH_ADD_DEV_EVT callback as stack updates the attribute mask
to the stack callout function bta_hh_co_open()
Change-Id: I1e450a210a63359c7ae30551fd3c468f0e109fda
|
|
|
|
|
|
|
| |
The problem was due to incorrect loading of the MDL configuratoion
The issues is fixed after loading the MDL configiration in the right order
Change-Id: Id33f680e089e71a10f9dd00163f931daa277b021
|
|
|
|
|
|
| |
Included more error checking and removed unused code
Removed header file as the header file will be included in kernel
Change-Id: I3086d6520fc764b73e0e740dadaa64a9cdc11945
|
|
|
|
|
|
|
| |
These APIs are needed to allow the bluetooth chip to be put into DUT
mode so that RF/BB BQB tests can be run
Change-Id: Ie5be00da567bc94173f35b098abcaf6f6603a129
|
|
|
|
|
|
|
|
|
| |
Both when auto-pair attempts exceeded or when auto-pair was not
attempted, but authentication failure was observed, send auth fail
to upper layer
bug 6936335
Change-Id: Ieafd0c6bbc57fb36cf4c2c450556e4df7ec23a1a
|
|
|
|
|
|
|
| |
Send only length of string to Java instead of length +1 from btif for
local Bluetooth name, Remote name and Friendly name for paired devices.
Change-Id: I4e822db62eb2affaadad283c6ceb2a368e3b107c
|
|
|
|
|
|
|
| |
Set the correct pointer to properties[] array before
sending HAL callback for remote_device_properties_cb
Change-Id: I199566d5f4b5997aad6a5b2ca83b67c9b1bd108b
|
|
|
|
|
|
|
|
| |
While AV disconnection is in progress, we need to handle the RC_CLOSE
event from the stack to trigger the uinput cleanup. Otherwise we would
leaking uinput FDs.
Change-Id: I9e37eef7b1c0fa0d56e809f1bf5686235f782cb5
|
|
|
|
|
|
|
|
|
|
| |
Some carkits after send AVDTP SUSPEND right after RC PAUSE
Per the whitepaper, the device sending AVDTP SUSPEND should send
AVDTP START. However a few carkits send AVRCP PLAY without sending
AVDTP START. Added a workaround to reset the remote suspend flag
when an AVRCP PLAY is received
Change-Id: If12e55b4d905b03890c69c2137f363986482ab1a
|
|
|
|
|
|
|
|
|
|
|
| |
also added mutex protection for any a2dp control path signalling to
ensure only one outstanding request at a time
Change-Id: I06d95793a8632f6a8baec967a1d8440ecce8a65d
Conflicts:
audio_a2dp_hw/audio_a2dp_hw.c
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Conflicts:
btif/src/btif_core.c
btif/src/btif_dm.c
btif/src/btif_hh.c
btif/src/btif_sock.c
gki/ulinux/gki_ulinux.c
hci/include/bt_hci_bdroid.h
hci/src/bt_hci_bdroid.c
hci/src/btsnoop.c
hci/src/hci_h4.c
hci/src/userial.c
vendor/libvendor/src/hardware.c
vendor/libvendor/src/upio.c
|
|
|
|
|
|
|
|
| |
This translates to AUDIO_STATE_CHANGED intent with state
STATE_AUDIO_CONNECTING which is needed for AudioService/AudioManager to
suspend music
Change-Id: I1293c105aaf1486f046620d5778c680908aad362
|
|
|
|
| |
Change-Id: Iebc520d9b10ef220a83a16ff55efa46b4c5a0d27
|
|
|
|
|
|
| |
If the AG SLC is not setup within 10 seconds, disconnect the link
Change-Id: If60338e821e575bf46bb81a5f3a640b7d530eb2f
|
|
|
|
|
|
|
|
| |
UuidsChanged event will force the Settings app to fetch the bonded
devices list. Thus, bond state change event needs to be sent prior
to sending SDP data (uuids)
Change-Id: I15c420f477c89780022c28b47a3f7c1cd1b20aeb
|
|
|
|
|
|
| |
Unknow characters were added while storing adapter name to storage sonetimes
Change-Id: I081942cfb7be93cdbe0f5cd3d9fc9edef333a794
|
|
|
|
|
|
|
| |
When the local side initiates disconnection, bluedroid should send
diconnecting event, otherwise the instrumentation tests do not pass.
Change-Id: Ic21a905407814c2117c04044c2799ea17a16d33b
|
|
|
|
|
|
|
|
|
| |
For HID connection, hid and sdp connections could be attempted at the
same time. Some devices, that are short on resources, do not handle
this well, and reject our SDP L2CAP connection. SDP discovery failure
was not handled, leading to GKI exception. This has been resolved
Change-Id: Ib49d66c62a2d05a83b44b733d3c9c4259b5d4c6f
|
|
|
|
|
|
|
|
|
| |
With instrumentation tests, there were race conditions where the while
SDP was in progress after bonding, the next iteration of bonding was
triggerred. The fix was to ensure that the bonded callback is sent only
after SDP is complete
Change-Id: I07269b9188aa00eb91f8ecc089b9beb7dbff7af6
|
|
|
|
|
|
|
|
| |
When an incoming pairing request is received, store all the remote
device properties - name, cod and type. Failing which results in an
exception when upper layer tries to access remote device properties
Change-Id: I7f5d27a90319a78cefc05873e74f1b322bbce8ac
|
|
|
|
|
|
|
|
| |
Calling adapter_bonded_devices_cb on Pairing was causing a race
condition in certain scenario which resulted in bond_state_change intent
being dropped.
Change-Id: Ifa98331ad3a89d5b48b01f91a70db7fa660c7b26
|
|
|
|
|
|
|
| |
cleanup() is called. This stops the signal FDs to be leaked for every BT on/off cycle
Closed the open FDs in univ_linux.c to stop FD leaks during BT on/off cycles
Change-Id: I86af438dc1186e12aa1f18fd44bcc89343ef5489
|
|
|
|
| |
Change-Id: Ib5e1342b4fba98fa5651ed8428f5580ad54a3332
|
|
|
|
|
|
| |
reset control blocks on startup/init
Change-Id: Iddc37e60ddb712de4af39a25f3c2e5bc7b11410d
|