| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / / / / / / / / / / / / /
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
On BT OFF, PowerManager callback has to be disabled to avoid handling
events that are triggered as part of the BT OFF sequence. This was
causing a dead lock in the BTU thread not exitting when AV is
disconnected as part of BT OFF sequence
bug 7142673
Change-Id: I29554e47514210a5002c06b078a30b3e7cd03710
|
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | |
| | | | | | | | | | | | | | |
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
|
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
Change-Id: I6f9459197724cbb2824f4160f7f366bfe7631556
Signed-off-by: Iliyan Malchev <malchev@google.com>
|
|\ \ \ \ \ \ \ \ \ \ \ \ \ |
|
| |/ / / / / / / / / / / /
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
Change-Id: Ib1f39b66b3422164f64fcbbf271636244b6cb1a3
|
|/ / / / / / / / / / / /
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
Stack supports AT+BIA, which is mandatory for HFP 1.6 support.
WBS is optional, hence does not impact the HFP version. Update
HFP version in SDP to be 1.6
bug 7127626
Change-Id: I7dcd6edc3299b267a737d281c1663a2db2ef591a
|
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
Remove obsolete get_supported_devices() function.
Change-Id: I4e2e6daa2222b9c7b6c685d8ac0763dc5f8cdaa9
|
|/ / / / / / / / / / /
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Bug 7009277
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Bug:7074362
Change-Id: I76afb73e51e8f6ab1da8257ea004c8d7131e6884
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Bug: 7093571
Change-Id: I328b0a24ffa827a5a7d22f90ee8d476bd151675e
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
A few GKI buffer macro definitions were overlapping between bt_target
and gki_target. GKI buffer definitions should only be present in
gki_target.h.
Change-Id: I0930960efe114ad479a894785b3ecf3e94195caf
|
|/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
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
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Use layer specific data to display the log tags for stack logs
bug 7070825
Change-Id: I39b9a5c7c719a08bd5355c1648effc7828eceb57
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Fix two bugs in adev_get_parameters():
- the str_parms struct was not destroyed causing a memory leak.
- get_parameters() should return an empty string, not NULL.
Change-Id: Icdf2803afe82fa4be7950b4659f850b772381f17
|
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Prints the error code of hardware failure for the BR/EDR Controller
Change-Id: I8c5172d9485ef0d71668969789fdacd720a2067f
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
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
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
BTM, BTU, and BTA modules were preset with hardcoded trace level
(BT_TRACE_LEVEL_DEBUG) during early development days. Since the trace levels
have been made configurable in /etc/bluetooth/bt_stack.conf at run-time,
removing those hardcoded settings.
So, the compile-time default trace level BT_TRACE_LEVEL_WARNING (set in
bt_trace.h) will be used if the bt_stack.conf is missing, or if the
TraceConf=false is given in the bt_stack.conf.
Change-Id: I76d905adbfda3c40f714398da86ebec90a1a8a40
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: Id9df79ff6c0f5e6a981ecb9defd82e057c643bf5
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Set thread names for easier debugging
Change-Id: I1beeaae24a7782ab97be22db57060c773721bc46
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Configured the trace level to not report logs which are marked DEBUG or
VERBOSE.
Change-Id: I3112128d20140b28523edf439a1b6bd0c255d835
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rather than using a text file and generating each buildcfg.h file
per device bdroid_buildcfg.h which supplies device specific values
and then bt_target.h will supply common values.
Change-Id: I12cb5408729c3e076562a292204f07a0c4b52628
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are some devices that do not respond to SDP request while they are
in the midst of initiating an AV connection. In such cases, it is valid
to ignore the SDP failure and initiate the AV open.
bug 6996250
Change-Id: I16149fee9b6ee6130cf45396246948716898b167
|
|/ /
| |
| |
| |
| |
| | |
Included more error checking and removed unused code
Removed header file as the header file will be included in kernel
Change-Id: I3086d6520fc764b73e0e740dadaa64a9cdc11945
|
| |
| |
| |
| | |
Change-Id: Ic596804bf6a25e4f039860348298f296edc9cd8f
|
|/
|
|
|
|
| |
Revise BT Vendor Lib interface and add support of HCI multi-channel transport.
Change-Id: I5a7a7b64798bb30be60ed29bd564bc499bd5b5bc
|
|
|
|
|
|
|
|
| |
Avoid duplicate notifications for service, signal, roam and battery
charge
bug 6983415
Change-Id: If68ea7315de4f964e7fb83a6a628c8d2c29a333d
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
1. Move UART port configuration into vendor lib to respect the fact that each
vendor might have different UART port settings for its own chipsets.
2. Detail bt_vendor_lib.h header file with usage instructions.
Change-Id: I10dc44afd9b3cc1985769166a717089728281296
|
|
|
|
|
|
| |
- fix PDK mini builds
Change-Id: Ic5cd4975210f70d028938b1f306ea38de27191a4
|
|
|
|
|
|
| |
This is a copy of broid_generic.txt for now.
Change-Id: Ia48bdbde2e7c2ca45cd57927182253c75cfbb252
|
|
|
|
| |
Change-Id: I95563503209c9166ef5998a02683d700ed8eef5f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original baud rate change was done through closing the existing UART port
then reopening UART port at new baud rate. It was reported that this approach
would cause trouble on some platforms which spits out false start-bit signal
on UART bus during port close and open process.
Revise the way of doing baud rate change to use terminal I/O (termios) control
functions.
Change-Id: I18ab5a234576147dd9185eafd1e57d3b4e3fa2bd
Conflicts:
hci/src/userial.c
|
|
|
|
|
|
|
|
|
|
|
|
| |
From time to time, we had seen some GKI_exception error messages showing up
in adb log during turning BT off. Those were triggered by a HCI event which
arrived after BTU task had been terminated. The early termination of BTU task
had also become a contributing factor to the BT-OFF hung issue.
Revise the termination sequence between BTU and HCI/Vendor tasks to address
the issues.
Change-Id: I094104943275b3b1fb95aef514936e28394615eb
|
|
|
|
|
|
| |
Define max L2CAP channels to be 16 and combine MAX_L2CAP_LINKS and MAX_BD_CONNECTION into one definition
Change-Id: Ib5cb95f5829400b2182beb3c8409142a20b8fb95
|