- 06 Oct, 2014 3 commits
-
-
Andre Eisenbach authored
-
Satya Calloji authored
The latest discovered address is not used when reconnecting to devices using resolvable private addresses, if RPA resolution offloadin is not supported in the controller. This patch also address the exception case where BT off is memseting all control value while the IRK list is still being cleaned up. Bug: 17187661 Change-Id: Ifeb5b8297e7eadb0e34ec1afbd41f46bdd836cf3 Author: Chaojing Sun <cjsun@broadcom.com>
-
Mattias Agren authored
* Ensure all a2dp audiopath threads are configured to high priority when actively streaming. * For now set bt hc worker thread always to URGENT_AUDIO until new thread api can adjust thread priority dynamically. Bug: 17520043 Change-Id: I10e314085329278bcfcc4e8bc5ce899b03d22e2b
-
- 25 Sep, 2014 1 commit
-
-
Matthew Xie authored
-
- 24 Sep, 2014 1 commit
-
-
Priti Aghera authored
When BT is turning off btm_ble_vendor control block is cleaned up. So irk_entry which points to the first element of irk_list is NULL Included a null check for irk_entry to prevent stack crash. Bug 17399097 Change-Id: Ib129f7dd06f9db61cc54257aa4a563fe2c9f41f2
-
- 23 Sep, 2014 2 commits
-
-
Matthew Xie authored
-
Nitin Arora authored
This adds logic to remove the device from whitelist when user unpairs or disconnects device. Bug: 17318494 Change-Id: I43c06dd16c665f9ce2e71a0e031c4f0f11a4012e
-
- 19 Sep, 2014 1 commit
-
-
Satya Calloji authored
Read the controller features before local name read Bug 17505545 Change-Id: I7995a8c714ebec6e1751af5371edfd29c74b12ea
-
- 18 Sep, 2014 2 commits
-
-
Zhenye Zhu authored
peer stuck in receiving bug 17525124 Change-Id:Ic67e9c0aab7e64afc9679733e6c3de10a28078d7
-
Chris Manton authored
The userial read loop uses one global flag to condition the serial port read and a second global file descriptor variable that may change from another thread underneath it. Check the validity of the serial port file descriptor by making a copy immediately before the read and only proceeding if it's a valid fd. bug: 17552690 Change-Id: Iaaf1b8476fdee462ddc178d2a31ef8f55cb33e52
-
- 17 Sep, 2014 5 commits
-
-
Andre Eisenbach authored
-
Andre Eisenbach authored
Currently a stack restart or device reboot will overwrite existing snoop logs when the stack restarts. This patch adds a new configuration file parameter "BtSnoopSaveLog" that, if enabled, will cause an existing snoop log to be renamed to "<snoop_file_name>.last" before a new snoop log is created. This will allow for easier debugging of crashes that involve a reboot or stack restart. Change-Id: I4f56204d31a6bf2e96058938e8616eb6dee7360b
-
Matthew Xie authored
-
Matthew Xie authored
When the LE pairing is initiated over NFC, skipping device scan, there is no device type or address type info. We set the default as le and public. bug 17497942 Change-Id: I3dcbb9029ead6ea0f7c48e62f46c8a055f1bc293
-
Andre Eisenbach authored
This removes a hack to set LE IO capabilities and reuses the existing constant defined in bt_target.h. Change-Id: I3c97629bd092ac78bd673afc29458775b2bce836
-
- 14 Sep, 2014 1 commit
-
-
Priti Aghera authored
Host can not initiate new connection when exceed controller capability and connection then drop back to lower than the max. Controller will not generate connection complete event when initaite LE ll connection request failed, and host is dead loop waiting for the connection complete then can not recover. Included a connection complete callback with failure status when controller capability is exceeded. bug 17326529 Change-Id: I9b863578dc868456e092f1d060e50d2c9fdcb441
-
- 12 Sep, 2014 3 commits
-
-
Prerepa Viswanadham authored
To avoid premature connection notification to app, always wait for LE read remote feature complete with success before the connection event is sent to application. This patch also deprecates the BTA_SKIP_BLE_READ_REMOTE_FEAT flag. Since the remote feature request is now serialized and start encryption won't be called until the connection is up, this flag is no longer necessary and interferes with the new behaviour. This is an extension of previous CL Bug: 17326529 Change-Id: Icfd4c5dfdd9f89d1318ef429e132eb005abb1f64
-
Wei Wang authored
-
Wei Wang authored
-
- 11 Sep, 2014 2 commits
-
-
Andre Eisenbach authored
When re-connecting to HID devices, the first reconnection immediately after a reboot incorrectly uses the static, public Bluetooth address of the phone/tablet as the own address. This patch fixes the Bluetooth initialization sequence to make sure privacy is enabled before any Bluetooth services are started. Bug: 16952502 Change-Id: I43e595ddc7e347fab972b059382b512fb03e9459
-
Satya Calloji authored
Fixed the 128-bit UUID handling during setting up of adv data/scan response Bug:16799331 Change-Id: I81e4ab0a80a5c1b7abf012dccc29eead54229b21
-
- 10 Sep, 2014 2 commits
-
-
Andre Eisenbach authored
-
Andre Eisenbach authored
Merge "SMP doesn't detect the event of local processing taking more than SMP timeout (30 sec)" into lmp-dev
-
- 09 Sep, 2014 8 commits
-
-
Mudumba Ananth authored
LE link transmit quota should be calculated based on the total LE buffer available and number of LE link that shares the buffer. Currently it's been calculated based on the ACL buffer number and total physical links(BR and LE), that cause the LE link transmit quota not being done right. Modify the link transmit quota allocation, and keep track of LE link seperately, also keep track of round robin scheme for LE links solving the problem. Bug: 16560957 Change-Id: I70f91827b96f2c10421e91311ea34cc81a5ef4b8
-
Andre Eisenbach authored
-
Andre Eisenbach authored
-
Priti Aghera authored
SMP pairing failure if remote send security request before master side receive LE link connection callback. The racing condition will cause master side bonding failure upon ignoring remote security request and flush out all SMP information. Retain SMP information when a locally initiated pairing is in process solves the problem. Bug: 17412687 Change-Id: Ia2256160c866413f93c6f49e5db82b4c6489d9d2
-
Mudumba Ananth authored
Bug: 16560957 Change-Id: I1113f367187a30e01fa3d5d2a5ccb0243580e06b
-
Mudumba Ananth authored
Bug: 16560957 Change-Id: I91fd2cc90435d0b899474b555b4a4ab00306c156
-
Andre Eisenbach authored
-
Andre Eisenbach authored
If the local device does not support RPA offloading, background connections to a resolvable random address will not work. Added callback to indicate to the application writer that the requested operation is not supported. Bug: 16831527 Change-Id: I083d66b16704e997f52a40ea4daced3056b50ad5
-
- 08 Sep, 2014 4 commits
-
-
Satya Calloji authored
Handled the case of no manufacturer data in filter configuration Bug:17324059 Change-Id: I87c2c44644f808bd88f4d8681ff53e2d92815658
-
Priti Aghera authored
Remove the link key if encryption fails due to missing key or authentication error. When a remote device loses the bond, all HOGP services cached should be discarded and all client configuration descriptors needs to be re-enabled. This will ensure successful re-connection. Bug: 15022622 Change-Id: Ie1730830c0cbbc294e2cd579d7dca69d16cf8218
-
Priti Aghera authored
ACL link up notifaction was not sent after LE read remote features was successful. Thus, total ACL link up count was not updated. Included a link up notification after LE read remote features is successfull. Bug: 17410697 Change-Id: I41fc640e76fa99354cb63d9b0b3031582178c057
-
Matthew Xie authored
Bug: 17401266 Change-Id: I5f36e13b3ccb327f191db33123fff98858f07c5f
-
- 05 Sep, 2014 1 commit
-
-
Priti Aghera authored
To avoid premature connection notification to app, always wait for LE read remote feature complete with success before the connection event is sent to application. bug 17326529 Change-Id: Id731bf02e8d5d5a68db12e0478b8eb74723eb95d
-
- 04 Sep, 2014 4 commits
-
-
Priti Aghera authored
Send Set_Random_Address when privacy is enabled. If Set_Random_Address is not sent to controller, Connection request will be sent with host address as all 0's Bug: 17386986 Change-Id: I59877e52bf76a56696800ff0e75487c633adde3c
-
Fred Quintana authored
-
Andre Eisenbach authored
-
Andre Eisenbach authored
A previous changed introduced an error in the timer tick calculation when removing a timer. This could lead to timers expiring sooner than expected. Bug: 17390240 Change-Id: Id3291aaf492a7178782e6f804dad71387c3c9382
-