| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
This timer(BTA_DISABLE_DELAY) if set to a value greater than zero shall delay the
chip/transport shutdown. The BTA_DISABLE_DELAY can be fine-tuned per
platform.
bug 7212447
Change-Id: Ib0346af42f6b596e9fbb281203058872bceffbd9
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
for immediate role switch
Initiating immediate role switch with certain remote devices has caused issues due to role
switch colliding with link encryption setup and causing encryption (and in turn the link) to fail .
These device Firmware versions are stored in a blacklist and role switch with these devices
are delayed to avoid the collision with link encryption setup
Bug 6992300
Change-Id: I71c7d94bc4cf03f2383b6c1956bba8697f6c2a8b
|
|
|
|
|
|
|
|
|
|
| |
Crash is seen while attempting to memcpy more data than what is
actually available. Root cause is that the stack callbacks where
sending arguments which are union members and not the union
structure. This resulted in a crash during memcpy
bug 7016761
Change-Id: I55ad3c885d1634e44833152ed0808b09e437a657
|
|
|
|
|
|
|
| |
Fix for a potential race condition where unpair was failing is music was
streaming. The issue was due to the unpair callback not being invoked
Change-Id: I5dff05abd238b4af3301495be05cbaa970d275d6
|
|
|
|
|
|
|
| |
1. Per the spec, if both sides are using "No Bonding" for auth requirements, then the key could be considered a session key. Updated the pairing logic to handle this
2. If incoming JustWorks pairing is initiated, prompt the user for consent if the peer's io capabilities reflects DisplayOnly or NoInputNoOutput
Change-Id: If592c96203e7a4b25af3d87056d534131b606e58
|
|
|
|
|
|
| |
BT_PROPERTY_UUIDS of the remote device
Change-Id: I1facd9238cf847915df4c01b33c77b2fdaa168cb
|
|
|
|
| |
Change-Id: I77b751d14afb8fbe450d5176454a33dc6884f51d
|
|
|
|
|
|
|
| |
and stack. Added support for suspend and a dedicated HAL callback
notifying framework on audiopath events. Cleanup.
Change-Id: I3b738611bc8e1d84794f7207413fd9e7dd1fc668
|
|
|
|
|
|
| |
time even when no ACL connections were present
Change-Id: Ib37c43d3cbc484d3f2973478ff2b1eee51de5150
|
|
|
|
| |
Change-Id: I88ec6084c140fa257154a98e23e075900e84cc8c
|
|
|
|
| |
Change-Id: Ib28372748df21d36d371d308975758f60df7aa28
|
|
|
|
| |
Change-Id: I86e8d033789269905102cf05d8b66961ae79b9a2
|
|
|