dfb3b2f2595dc16fe7f576a4b0c2f5e73db0327f |
06-Feb-2015 |
Andre Eisenbach <eisenbach@google.com> |
Add flag indicating encrypted connections to btif_dm_get_connection_state() Add a check to btif_dm_get_connection_state() to see if the currently active connection is encrypted. Bug: 19186961 Change-Id: I27bcc6e296d272ffd17c0bbe97631ffa4df57ccd
tif_dm.c
|
893637614568b8ac7dc996c2e9bdbde481fbdc08 |
26-Jan-2015 |
Andre Eisenbach <eisenbach@google.com> |
Change pairing_cb to assume temporary pairing by default When pairing takes place, the pairing_cb.is_temp flag indicates whether a pairing is temporary or permanent. Link keys are not stored for temporary pairings. Since this is a "positive" flag, resetting the pairing_cb control block (ex. memset to 0), it will assume persistent pairing by default. Under certain circumstances, this can lead to a link key being stored for temporarily secured connection. This patch reverses the flag to be a "negative" flag. Renamed to "persistent_bond", the default 0 meaning is now used to indicate a temporary bond. If the lag is not properly set now, it will default to a temporary bond and will not save the link key erronously. Bug: 18345373 Change-Id: I6e821595877ff30d64dc6e33602ac049cab3dd1e
tif_dm.c
|
26e80aad86fae4e468a330d64ee02291f3a1980e |
07-Jan-2015 |
Andre Eisenbach <eisenbach@google.com> |
Relax max PCM frames per tick a bit Also made the value overwrite-able in bt_target.h. Bug: 18913091 Change-Id: I64bbe453b35fdce6f127b3c23c0552b14d4ac49b
tif_media_task.c
|
2cfcf51ea3447f2b5cf95dbe7515d230de1e7df7 |
17-Dec-2014 |
Tobias Melin <tobias.melin@sonymobile.com> |
Added check if the device address is random A check if the device address is random is needed since in a public device address the two most significatant bits can also be equal to 01 (see Bluetooth specification Core_v4.1.pdf, page 2021 and page 2500). Bug: 18784040 Change-Id: I4f967a426ebb825731461e202c0741ae0540ef6a
tif_gatt_client.c
|
e608a529718bb64accdf9f18cb196a9a3c45c90e |
04-Dec-2014 |
Wei Wang <weiwa@google.com> |
Merge "Remove unnecessary check of multiple advertise instance count." into lmp-mr1-dev
|
8a75ab5b918c4e65e1b8fe55ec193b047ddfcb06 |
03-Dec-2014 |
Matthew Xie <mattx@google.com> |
Merge "PAN TAP fd is not monitored in all cases" into lmp-mr1-dev
|
e79be3d6ca41ed6349012c73a3374aca3714a053 |
26-Nov-2014 |
Andre Eisenbach <eisenbach@google.com> |
Add server-side callback for change in MTU (2/4) When a client requests to update the LE transport MTU, the server currently does not get notified and can therefor not properly size notifications appropriate to the current MTU. Bug: 18388114 Change-Id: Ice355f8919d4f69876574df1d90ce7d31f42bc4f
tif_gatt_server.c
|
ffaf9c5358decc3102252e76cc00da5c910bb065 |
26-Nov-2014 |
Wei Wang <weiwa@google.com> |
Remove unnecessary check of multiple advertise instance count. Bug:18539121 Change-Id: I841e4323ed4995bd9f8117681a759f52995d071f
tif_gatt_multi_adv_util.c
|
285f7c6527244c749aafdc1edec39787e12bd871 |
26-Nov-2014 |
Zhenye Zhu <zhenye@broadcom.com> |
PAN TAP fd is not monitored in all cases Bug: 18271987 Change-Id: I348f3851a955b5277e7cdf0102583eaaef2ef0f3
tif_pan.c
|
c113e4db5218901b7ef4b09b1f08727da70971e1 |
24-Nov-2014 |
Matthew Xie <mattx@google.com> |
Merge "Enforce Authentication for incoming HID connection" into lmp-mr1-dev
|
3770c47387d3dfc6d2e2d32f4409a82119e726e3 |
20-Oct-2014 |
Satya Calloji <satyac@broadcom.com> |
Clean up SetADV and ScanResp data memory leak. Bug:18045480 Change-Id: Ic433f4aa26bd08e84c53c447be9d5278e16ebd55
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
d79fb192585822a76b833403dfc61468d225d0b3 |
12-Nov-2014 |
Priti Aghera <paghera@broadcom.com> |
Enforce Authentication for incoming HID connection Enforce Authentication in addition to encryption for all incoming HID connections. Bug 17887668 Change-Id: Ib0d6cd6d8e793823c541a1b4468dcce89f297181 (cherry picked from commit 6d6502909c1dd1766db1fea2cb638866e137a7bf)
tif_hh.c
|
86f97eda524568f2d264186844450db5e56dac36 |
10-Nov-2014 |
Matthew Xie <mattx@google.com> |
Use the device type from saved properties instead of assuming default DUMO device can do both BLE and BREDR operations. It was wrong to assign BLE or BREDR type to it. Bug: 18275230 Change-Id: I8d6c17e5157ba29a1af459629de9e2d6f6dc5e99
tif_config.c
tif_dm.c
tif_gatt_client.c
tif_gatt_server.c
tif_gatt_util.c
tif_sock_util.c
tif_util.c
|
c5916e97384f07ec5a2e061e6af24f70107c74a2 |
08-Nov-2014 |
Andre Eisenbach <eisenbach@google.com> |
Remove overflow rate limiting when reading A2DP frames A2DP now supports adjusting the number of A2DP frames sent per timer tick to adjust for timer drift and missed media task ticks. When the signal to the headset/speakers becomes interrupted, the number of packets to be read can queue up and rate limiting will not allow for the queue to be cleared. The overflow mechanism introduced in commit 4aebca4 will cause the media task to stop sending packets completely, which can underflow the jutter buffer on the remote device and lead to audio drop-outs. This patch removes the overflow mechanism and also adds code do discard audio frames that could not be sent to the remote device (weak signal etc) to allow the device to stay in sync and not build up audio delays. Also added additional debug logging and changed the UIPC flush mechanism to address an issue where reading byte by byte causes an endless flush loop if remote UIPC producer writes data faster than the flush loop consumes it. Bug: 18326405 Change-Id: I9a424984806bb2a464877399804b3355b2c439c3
tif_media_task.c
|
16451571a5461ab3be535d25cbb62ab03b6b6157 |
06-Nov-2014 |
Satya Calloji <satyac@broadcom.com> |
am b407515f: Fix "no instances found for adv" when stop BLE scanning. * commit 'b407515ffa145b1a2cab01467da03c92aeb0e8eb': Fix "no instances found for adv" when stop BLE scanning.
|
b407515ffa145b1a2cab01467da03c92aeb0e8eb |
10-Oct-2014 |
Satya Calloji <satyac@broadcom.com> |
Fix "no instances found for adv" when stop BLE scanning. Bug:17703806 Change-Id: I103d3637ad38d33b4370850a300b0d72bdaeb562
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
3e0dc7324e7b0127f9d15609bab395100a22098d |
24-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Make local privacy configurable Bug: 17753401 Change-Id: I288ea8b6194d91d18485d0f3f1bbf997f97a26dd
tif_dm.c
|
f89382760380cc3a2dd5d56366344eed2c00e561 |
22-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
am 5e808468: LE: Do not remove bond on encryption failure * commit '5e808468e0667a6a2a8a1e6de80efbc4f42fa0f0': LE: Do not remove bond on encryption failure
|
5e808468e0667a6a2a8a1e6de80efbc4f42fa0f0 |
21-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Do not remove bond on encryption failure If the encryption fails during the re-connection process with a previously paired LE device, the pairing is removed. Thus, a single connection failure could lead to the device be unpaired. This patch prevents unpairing when encryption fails. Additionally, the IRK is restored from NV ram to fix reconnection to dual-mode devices. Bug: 18072300 Change-Id: I077a16d0715fdaa07b95b1c664c18bd839754896
tif_dm.c
tif_gatt_util.c
tif_storage.c
|
b94c47a5407b29bf3bcb8d3c5f94773d9697ce50 |
21-Oct-2014 |
Chaojing Sun <cjsun@broadcom.com> |
am 433fe016: Cache HOGP HID report map * commit '433fe016392c7ae003033530f1b3994f2ddad313': Cache HOGP HID report map
|
f4d88b93db3796b3c0915d8068ea14e60913f377 |
21-Oct-2014 |
Prem Kumar <premk@google.com> |
am 25249f76: Merge "Retry pairing if the device did not respond (page timeout)" into lmp-dev * commit '25249f7663d75244b5a2abcac08e301d584fcd8d': Retry pairing if the device did not respond (page timeout)
|
6b5262a6943444848a377aa882f8be91449211d1 |
21-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
am 01d102b3: A2DP: Lowering maximum PCM frame limit to avoid audio breaks * commit '01d102b3b187ab0d24050c1e12f96e6ee1ce50be': A2DP: Lowering maximum PCM frame limit to avoid audio breaks
|
433fe016392c7ae003033530f1b3994f2ddad313 |
17-Oct-2014 |
Chaojing Sun <cjsun@broadcom.com> |
Cache HOGP HID report map HID reports from a bonded device can be missed when Bluetooth is restarted HOGP report discovery is still active. Caching the report information and loading it back when the stack resets will ensure incoming HID reports can be processed immediately. Bug: 17999991 Change-Id: I4608935f8749537d6b05625b894445a21f844ee0
tif_hh.c
|
25249f7663d75244b5a2abcac08e301d584fcd8d |
18-Oct-2014 |
Prem Kumar <premk@google.com> |
Merge "Retry pairing if the device did not respond (page timeout)" into lmp-dev
|
01d102b3b187ab0d24050c1e12f96e6ee1ce50be |
17-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
A2DP: Lowering maximum PCM frame limit to avoid audio breaks Some car kits (notably Renesas car kits used in Nissan/Infiniti models) will throttle incoming A2DP frames if too many frames are sent at once. This patch lowers the maximum number of frames sent per tick to not overwhelm the remote device. Bug: 17880920 Change-Id: I7bfbba625405c96159d1c94eebd8dc498f100daa
tif_media_task.c
|
31a640079c9a7b9a2bf014f06f6c371afb66cc63 |
14-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
Retry pairing if the device did not respond (page timeout) Implements a "blacklist" identifying troublesome remote devices which may require multiple pairing attempts to succeed. Change-Id: I11b6b7da7230e37fbd5ec4c07cd38b30dc12b40e
tif_dm.c
|
494b3bf7403723560709949f8c2d337d6d63310a |
14-Oct-2014 |
Wei Wang <weiwa@google.com> |
Merge "Add support of advertising through standard instance.(4/4)" into lmp-sprout-dev
|
f061e74b81863771b174d1717a6165034dbad8e5 |
09-Oct-2014 |
Mattias Agren <magren@broadcom.com> |
Added missing A2DP priority on java alarm service Running GKI timer engine via JAVA alarm service was causing severe timer preemption at times which affects A2DP media task timer. This in turn was stressing the compensation logic towards UIPC resulting in very bursty reads of up to 40 UIPC frames at a time. This led to instabilities on the UIPC pipe and trickled upwards in audio framework. Inclusion of java alarm thread in A2DP high priority thread list results in a much smoother data flow for entire A2DP data path and improved audio quality. Bug: 17520043 Change-Id: I7cea6ec64aa5b973b5fff767389a8827e681619e
tif_media_task.c
|
cafed88eb2caeaece08da1110625f4567a16ddd1 |
27-Sep-2014 |
Satya Calloji <satyac@broadcom.com> |
Add support of advertising through standard instance.(4/4) Handled the case of standard ADV when Multi ADV is not supported by controller Bug:17641092 Change-Id: I129a7faaf027985c63197e7298dbd2507905d29f
tif_gatt_multi_adv_util.c
|
d5aa24750c2202ce944560c2c27ead0214e8350d |
24-Sep-2014 |
Satya Calloji <satyac@broadcom.com> |
LE: Peer device's latest RPA is not being applied 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>
tif_core.c
|
303d4ac5ff7758ab2cdde4040cb8db6cf37552f5 |
17-Sep-2014 |
Matthew Xie <mattx@google.com> |
Merge "For pairing over le transport, set default device type and address type" into lmp-dev
|
64c5479fc050c537ef6d39625de2032c77fc5676 |
16-Sep-2014 |
Matthew Xie <mattx@google.com> |
For pairing over le transport, set default device type and address type 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
tif_dm.c
|
976990f872bb0873fedbb74649d0bf704bb70d05 |
13-Sep-2014 |
Wei Wang <weiwa@google.com> |
Merge "Fix issues with manufacturer ID prefix scan filter." into lmp-dev
|
1a5f8105337cd41efad09d4ec8812311e8adaaec |
13-Sep-2014 |
Wei Wang <weiwa@google.com> |
Merge "Fix ADV data exceeding max adv packet length" into lmp-dev
|
a015a8348b9e09caf5261689f4c288a4d2ff6acd |
11-Sep-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Use random address when initiating background connections 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
tif_dm.c
|
7ddf2d88501a2dd17045fb2f126ec99dcac9b5d9 |
06-Sep-2014 |
Satya Calloji <satyac@broadcom.com> |
Fix ADV data exceeding max adv packet length Fixed the 128-bit UUID handling during setting up of adv data/scan response Bug:16799331 Change-Id: I81e4ab0a80a5c1b7abf012dccc29eead54229b21
tif_gatt_multi_adv_util.c
|
f5140468dc83dafcd75ffe607e1a56c514b9a8a4 |
09-Sep-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "LE: Disable background connections if RPA offloading is not supported" into lmp-dev
|
a1e649b2566040d1f9e620753f18ca1fc088c64f |
18-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Disable background connections if RPA offloading is not supported 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
tif_gatt_client.c
|
6cbb113e7863888f62c49b4b7a89f12a04fe07f4 |
03-Sep-2014 |
Satya Calloji <satyac@broadcom.com> |
Fix issues with manufacturer ID prefix scan filter. Handled the case of no manufacturer data in filter configuration Bug:17324059 Change-Id: I87c2c44644f808bd88f4d8681ff53e2d92815658
tif_gatt_client.c
|
5e02098d563a7a8ff62ab71413d9878b88b7d484 |
04-Sep-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "Limit the time PAN can occupy the BTU stack thread" into lmp-dev
|
ae13ec986e188d66eaad3c69bb916ea18c142fef |
03-Sep-2014 |
Andre Eisenbach <eisenbach@google.com> |
Avoid race condition in SBC encoder initialization In the A2DP media task, btif_a2dp_encoder_update() relies on the fact that btif_a2dp_encoder_init() is called beforehand. Otherwise division by zero errors will occur. Since _init() called after the audio stream is opened, and _update() is called in resonse the the audio stream being opened, a race condition could ensue where _update() was called before open. This patch changes the A2DP stream start sequence to ensure the SBC encoder is initialized before the updated parameters are calculated. Bug: 17339248 Change-Id: I6ed36a7fff0e4aa672a8866727030681eb4b3dfc
tif_av.c
tif_media_task.c
|
95ca3c43eae763465bbd7bddc927279f17b16106 |
26-Aug-2014 |
Zhenye Zhu <zhenye@broadcom.com> |
Limit the time PAN can occupy the BTU stack thread Also make sure tap read/write are non-blocking and PAN does not use the complete shared buffer pool to avoid GKI buffer overruns. Bug: 16374840 Change-Id: I6f96d1c8d2804d253d33fe37ff87275e03e55ddd
tif_pan.c
|
ec2777e6a3e8516deff362e5cc732811d0afb1c8 |
03-Sep-2014 |
Matthew Xie <mattx@google.com> |
Clean up fd when failed to add monitor thread Bug: 10773872 Change-Id: I7f5b5f976ee7fa522e02b9ee4369b8f152b15cfb
tif_sock_rfc.c
|
e9ff1332e0c74c01be43cbff6daff48a271bcf03 |
29-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "Add LE device to inquiry DB before pairing" into lmp-dev
|
3baff79dcd63bc33b17f475939d0e282526d9995 |
29-Aug-2014 |
lungtsai_lin <lungtsai_lin@htc.com> |
Add LE device to inquiry DB before pairing There is no remote device type info wgeb OOB pairing LE devices. Add device type according to transport. Bug: 17156993 Change-Id: I29182ca13f801f8a7f2c3a95969d6ae23312dd7e
tif_dm.c
|
adb7bb50469db992969295792a7ba3b73f9e24b3 |
13-Aug-2014 |
Satya Calloji <satyac@broadcom.com> |
GKI_exception on running longer batch scans Fixed GKI memory leak in btif_gatt_client.c file besides few needed logic improvements which will help in preventing leaks on exception conditions Bug:16829603 Change-Id: Id39267fbedeb7435cdc2c3a9eda25d4b3cd82c2f
tif_gatt_client.c
|
eebf155a282baedbeb2579cde4e7fafc58d991ab |
25-Aug-2014 |
Matthew Xie <mattx@google.com> |
Merge "MAP: SDP corruption" into lmp-dev
|
54e24af853a77a057995ee4f234bae4d490b32e5 |
18-Aug-2014 |
Casper Bonde <c.bonde@samsung.com> |
MAP: SDP corruption Terminate strings before parsing to values. Might be related to: bug: 16877287 Change-Id: I0c46861229a90f37e266bd06bcba9ac78e3fc155 Signed-off-by: Casper Bonde <c.bonde@samsung.com>
tif_sock_sdp.c
|
962f1d1f9dc22d939bea4e9fb34a67028ff185fd |
17-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Remove general/limited discoverability bits for non-connectable adv According to the Bluetooth spec, section 9.1.1.2, "A device in the broadcast mode shall not set the ‘LE General Discoverable Mode’ flag or the ‘LE Limited Discoverable Mode’ flag in the Flags AD Type. This patch masks out the specific bits for non-connectable advertisements. Bug: 16924631 Change-Id: Ia2c0011fb31de3e4166a8bd2c2732e50aad3a610
tif_gatt_multi_adv_util.c
|
3e278d3f114907775626a3826c69e52a2278fe07 |
13-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "LE: Fix limited advertising not stopping after timeout" into lmp-dev
|
cf32e8d4e0cabac8432a3c6c6d8ece27d6067770 |
13-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Fix limited advertising not stopping after timeout When starting to advertise with a given timeout, the alarm did not fire and thus not stop the advertising. This patch switchs from the new alarm system to use BTU timers. Also fixes a bug in the oneshot timer handling where adding a new timer with a short timeout value would not actually restart the timer to pull in the deadline. Bug: 16988160 Change-Id: Ia556562675636be440ddca7682ac7d092bc0b48b
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
d437d1192a7812987b2f9caf197839086a105f13 |
13-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "A2DP: Protect against division-by-zero error in bitpool calculation" into lmp-dev
|
a391bf1d4f4250e27b6f157a1a8d2493c36934dc |
09-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
A2DP: Protect against division-by-zero error in bitpool calculation If the encoder parameters have not been configured correctly before the SBC encoder is initialized, a division-by-zero can occur resulting in a SIGFPE. Bug: 16902125 Change-Id: Ie4c6715b6b374a2d62fcfa0a1a99d40c689d0e2a
tif_media_task.c
|
169cd7a221a79474d36e5c1697e862c1d640c064 |
08-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Additional rebase fixes Change-Id: I0bb6c9f96987a7e8b8d91473681f5e208d3b844f
tif_gatt_multi_adv_util.c
|
1097ff0b2c493e1541ca989681267dfa6a61ed6b |
08-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Fix Bluedroid rebase error Change-Id: I80a2f3767acaee6095389bb9579aad4241d7c42f
tif_gatt_multi_adv_util.c
|
9dd5a9c11f2022fa9709f0c34f04560c21105152 |
08-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Add limited advertising duration capability (2/3) Change-Id: Id2ebc353f1bcd94978c5c8dc55a235c92ebc7658
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
16fe0822ccd3eb6f66d3afd9965d25a0a0cb4c30 |
07-Aug-2014 |
Prerepa Viswanadham <dham@google.com> |
Use run time parameters to control LE features Use values read from controller to enable and control LE features such as multi advertising, RPA offload, maximum irk size etc bug 15393216 Change-Id: I193e2b9a0dc61b86f667e986803571440e390160
tif_core.c
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
c331807e3c3a0e15180a11325e1635ae5268aa39 |
27-Mar-2014 |
Matthew Xie <mattx@google.com> |
BT MAP: added support for email sharing over BT - added more dynamic SDP record name setting for MAP in order to support multiple mas instances with different name strings. Change-Id: I7a78da3ba9707a08d1f6a6245c27fc3f1b86d244
tif_sock_sdp.c
|
62a54c5b374c1eb9d3664da2717f82fdeea8bb7e |
05-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "Add transport parameter to createBond() function (2/4)" into lmp-dev
|
b0daa5d79d4e2950701fb9a5f76a306e1da42de0 |
05-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Add transport parameter to createBond() function (2/4) Change-Id: I8176b932da705f8d0a230abd56bc5faa00005eb6
luetooth.c
tif_dm.c
|
f877e4c6990a05c6a609980efa4fc575aa7eb51e |
04-Aug-2014 |
Wei Wang <weiwa@google.com> |
Merge "LE batchscan consolidated reports" into lmp-dev
|
f1dba910daa5f0ce9ca89f840bb7e6269f07af1d |
16-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
LE batchscan consolidated reports Provide consolidated batchscan reports Change-Id: Ie3da240c38b014fe29d4394438f3858fd4e731fa
tif_gatt_client.c
|
372a9f7d53682a853f4c5f5fc7d2c36c044f2513 |
05-Aug-2014 |
Matthew Xie <mattx@google.com> |
Merge "Blacklist Apple HID devices to skip SDP" into lmp-dev
|
c0edf9f2038d23a3ba0cd424e187cb0d8fa201e8 |
26-Jun-2014 |
Priti Aghera <paghera@broadcom.com> |
Blacklist Apple HID devices to skip SDP Remote initiated HID connection fails as Apple devices goes out of resource. During incoming connection SDP is performed after authentication is successful. Apple device is out of resources and thus sends No resources available error for SDP request. In order to avoid this situation a apple HID devices are blacklisted to skip SDP after authentication in case of incoming connections. bug 15566403 Change-Id: Ic7fdfd2543c90e81341b4d5b7bef9c1d1c11b928
tif_dm.c
|
694988f6aadc9ff9611c595a9863661c85da2e0f |
01-Aug-2014 |
Zhenye Zhu <zhenye@broadcom.com> |
Fixed wrong return condition when all RFCOMM data was sent succesfully Bug: 16566991 Change-Id: I4e0d2487b71e2d8ad8e571e88d2623db2852bb1e
tif_sock_rfc.c
|
3489ca9d44bbf0d3f00b1f5cd9675694774d48a8 |
31-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
ADV data override issue Setting scan response overrides advertiseData Bug 16577710 Change-Id: I5ca28568495c8e487648a5f36d945e4443cba639
tif_gatt_multi_adv_util.c
|
d773c2cfd3675aaec431a42b79b26b24e0555ed9 |
30-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
Incorrect data type in local LE features bt_local_le_features_t of wrong size b/16653133 Change-Id: I81da7f8c6b9151b8def8d4e3c655cf746d0e3db9
tif_core.c
tif_dm.c
|
4a7ad9be81cc2b515502f2c1fb1b7ec7e3104146 |
30-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
Tx power is 0 in ADV packet b/15412969 Tx power is always 0 in advertising packet Change-Id: I7eb1f16b5fb1ab4ed669ba6a72f9603885cebc99
tif_gatt_multi_adv_util.c
|
efaddcb2cec21bfcdcadfa86720d3ca720a4253d |
29-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
Bug 16498557 Inconsistent energy reporting Fix for inconsistent energy reporting Change-Id: Iddd77354624a631ca8db52f12086d3afa5751d36
tif_dm.c
|
e85eb5a7c3ea7eaca09cbb33920435d809b4dd3d |
03-Oct-2013 |
Nitin Shivpure <nshivpur@codeaurora.org> |
Bluetooth: Cleaning up pan_conn DB, if connection is not successful. - do not merge A case where DUT is paired with remoteDeviceA & remoteDeviceB. remoteDeviceA is not pagable(turned off or some other reason). DUT(PANU) try to connect remoteDeviceA(NAP). But connection is unsuccessful, Because remoteDeviceA is not pagable, In this scenario btpan_conn Database is not cleaning up at btif layer. Later remoteDeviceB(PANU) connect to DUT(NAP) & connection is succesful, When remoteDeviceB disconnect existing connection. As database still has remoteDeviceA BD address at Btif layer. remoteDeviceA BD address is passed instead of remoteDeviceB BD address from Btif to UI. So remoteDeviceB still shows connected on UI. Cleaning up pan_conn database for particular pan connection at BTIF layer, whichever connection is not successful will solve this issue. Change-Id: I31dfe3ef46295e74bbfb57563e4fd4fc7155f006
tif_pan.c
|
76f645ea6f5cd22e464dcbdb1e73ecb50c5ea87c |
29-Aug-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Update security for HID Devices to Encrypt on BT On. - do not merge This patch updates HID Devices security mask to BTA_SEC_ENCRYPT from BTA_SEC_NONE. Without this change it was observed that on BT Reset, authentication and encryption were not initiated by DUT for incoming HID Control L2CAP Connection Request from remote HID Keyboard device. Change-Id: I484fbae1294fde386bd7959467214f9968e381e9
tif_hh.c
|
6e2d9db5148176d88d7f48c3b2ad5b27c57ca14d |
09-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
Settings app does not show BLE devices Settings does not show all BLE devices when scan filter is set Change-Id: I669ef3b87a9a21dfce26c1e22b5d984a5ea6f75c
tif_dm.c
tif_gatt_client.c
|
81b03192d4284acc7c9903f5b183927797dceca4 |
24-Jul-2014 |
Prerepa Viswanadham <dham@google.com> |
Fix build for non BLE supported targets(nakasi and manta) Change-Id: I0de46e1dfce3a51367bc0e2640e91cdefc8a21c6
tif_dm.c
|
e5ba8841cd39e17c05aeb4ab65b5b761d41577da |
04-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
LE energy info feature Stack and BT-IF changes for LE energy feature Change-Id: I671e63aaead210c6352b45a5e20ad5e4bbbb77b7
luetooth.c
tif_core.c
tif_dm.c
tif_util.c
|
25067c0afc4d3ed95181b91801d3d638d9aa3f8f |
22-Jul-2014 |
Andre Eisenbach <eisenbach@google.com> |
Fix integer overflow in GKI timer calculation Fix an integer overflow in the GKI timer elapsed time calculation that would cause Bluetooth Stereo Audio (A2DP) playback to stop suddenly after a period of INT32_MAX microseconds (about 35 minutes) of continuous uptime of the phone/tablet. Bug: 16412377 Change-Id: I28cd3155a23444e41b26b3f3b8424cc2a3c5bf91
tif_media_task.c
|
5e17049abe2158303a9423439f324d1a24d68b87 |
19-Jul-2014 |
Elliott Hughes <enh@google.com> |
Fix implicit declaration of function 'prctl' in bluedroid. (cherry picked from commit d356ffbf6f6095489c73266e6e591b1167cfa5e6) Change-Id: Icc160c758c126e48fd6490cd14211a8685e4cdba
tif_hl.c
|
1ef4ba488d259f6523b6e650fb80820d3a363302 |
19-Jul-2014 |
Matthew Xie <mattx@google.com> |
Merge "Bluetooth: fix the HOGP device(iBUFFALO BSMBB09DS) pair and reconnect problem." into lmp-dev
|
52a2cd609897c04bb6440e14ef2ec8871143d028 |
17-Jul-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Add connection parameter update request API (2/4) Change-Id: I131bfa7fb0a8cc970e1ac3e26e9d86ed2bee80a7
tif_gatt_client.c
|
2772dac59971dd9c135cfac73a1ba77a912324f4 |
17-Jul-2014 |
Thomas.TT_Lin <Thomas.TT_Lin@htc.com> |
Bluetooth: fix the HOGP device(iBUFFALO BSMBB09DS) pair and reconnect problem. in bta_hh_le.c (fix reconnect issue) Since new LE security flags are import, (BTM_SEC_LE_AUTHENTICATED, BTM_SEC_LE_ENCRYPTED, BTM_SEC_LE_NAME_KNOWN, BTM_SEC_LE_LINK_KEY_KNOWN, BTM_SEC_LE_LINK_KEY_AUTHED), we have to use new BTM_GetSecurityFlagsByTransport() function with LE transport to get right sec_flag, or will cause cannot correctly add to white list and cause reconnect fail. in btif_dm.c (fix HOGP mouse pair issue) the HOGP mouse will become abnormal if we update connection parameter too many times. Therefore the is_hid case is not suitable for HOGP mouse, it will trigger call to L2CA_EnableUpdateBleConnParams() several times due to service discovery and bonded state. L2CA_EnableUpdateBleConnParams() update connection cause mouse abnormal. The change will make the flow: complete bonding procedure first, then do service discovery, connect to mouse. in gap_ble.c (fix HOGP device pair issue) After pairing status is bonded, host start to create ATT layer to get some information from HOGP device. If host send "disconnect" command during period. Device will stop to feedback anything. Suggest to delete it. in smp_act.c (fix HOGP device pair issue) update connection parameter too many times may cause mouse abnormal, so remove this code since this will be called again after service discovery. Suggest to delete it. Change-Id: I4b722343c2b08d33530bc6b928bc9ffe89fd09e9 Signed-off-by: Thomas.TT_Lin <Thomas.TT_Lin@htc.com>
tif_dm.c
|
288f5cf88113e9fd107e914e41e01b9618195872 |
12-Jul-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "Calculate A2DP frames to send based on elapsed time"
|
f13db8a534adf5281ee915c4b73b3141957ed17b |
12-Jul-2014 |
Andre Eisenbach <eisenbach@google.com> |
Calculate A2DP frames to send based on elapsed time This patch is aimed at improving A2DP audio quality by sending the correct number of frames based on the actual time elapes between "ticks" in order to account for timer drift. Change-Id: If5b7cde90f5eb10b926ad247f51cff0eb60bbff7
tif_media_task.c
|
a3c936eae6fd686658dd84d546326908904029c8 |
11-Jul-2014 |
Priti Aghera <paghera@broadcom.com> |
am 156c52bb: Send correct status for SMP AUTH failure * commit '156c52bb003a14147db99d8a151edc08f591bd34': Send correct status for SMP AUTH failure
|
8cbb1f60fa29b736e8ea42a361fdb59195b84cb9 |
12-Jul-2014 |
Mike J. Chen <mjchen@google.com> |
Merge "Fix deadlock and non-working socket msg throttling"
|
335aa36bca8532874c23c1afe5bfc2aff7fc01a5 |
01-Jul-2014 |
Mike J. Chen <mjchen@google.com> |
Fix deadlock and non-working socket msg throttling Two major bugs in btif_config.c. One is that due to improper locking order, a deadlock could occur (symptom is generally out of GKI buffers because BTIF thread stops processing it's mailbox because it is blocked sending a msg to the socket thread, which in turn is blocked because BTIF is holding the lock it needs to do the config save that BTIF requested in the first place). The other is also lock related. The mechanism to throttle socket messages based on whether there was one already in flight wasn't working because there wasn't locking when that variable was being used. The compiler would be free to cache it in a register on SMP machines, so it would never look like there as a value in flight. This would cause a bunch of messages to be queued up, and then the way the handling worked in cfg_cmd_callback(), every cmd would cause a 3 second sleep, even if there was nothing to do. Modified the loop to check if there was nothing to do before sleeping. I was running into both bugs when repeatedly pairing and unpairing a BLE device. The deadlock would hit first, causing out of GKI buffers. Once I fixed the deadlock, I would still run out of GKI buffers because the socket thread wasn't working fast enough to clear the backlog of socket messages it had received. Also optimized some string termination code which was using a memset of the full buffer before and then copying over every entry except the last. Now we do the copy and just set the last buffer entry to null. Change-Id: Ic06ef0b8e15d8f1fe669fb88439851ffbad560de Signed-off-by: Mike J. Chen <mjchen@google.com>
tif_config.c
|
156c52bb003a14147db99d8a151edc08f591bd34 |
09-Jul-2014 |
Priti Aghera <paghera@broadcom.com> |
Send correct status for SMP AUTH failure Send correct corresponding status for SMP AUTH failure to JAVA layer. This will enable BluetoothEventManager to display correct error message for bond state changed callback. Bug 15677623 Change-Id: I6a8742926bac862f960890417b5d68c23b33e010
tif_dm.c
|
0317a401142e927be82a0259f54cfa10a686e0fe |
09-Jul-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "Prevent A2DP bit pool calculation endless loops."
|
4e3593a9a1c596904a844286fbe704e969e7230e |
08-Jul-2014 |
Andre Eisenbach <eisenbach@google.com> |
Prevent A2DP bit pool calculation endless loops. This prevents log spam and endless loops in the A2DP bit pool calculation. Protecting against the endless loop with prevent battery draining issues and phone unresponsiveness. This patch addresses the symptom. A separate patch will be submitted once root cause is determined to address the problem. Change-Id: I045b724c1c1638551b9333249f39eee109fa9ba1
tif_media_task.c
|
6718c6d9fcfe373a679a529aca003d32062f81dc |
02-Jul-2014 |
lungtsai_lin <lungtsai_lin@htc.com> |
Bluetooth: Rename BTA_AVK_INCLUDED flag to BTA_AV_SINK_INCLUDED (bt_target.h) Now OEM could enable/disable A2DP SINK role Change-Id: I62cf17b0397a86c5f886a2c1ca724ca77a7f9bd4 Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
tif_media_task.c
|
85b4ee5df4208fd06e836f40d7a19a84545f4e93 |
05-Jul-2014 |
Matthew Xie <mattx@google.com> |
Merge "DO NOT MERGE: Send to local UUID for AV connection" into klp-wireless-dev
|
7bc6e981a647ea7c246d2d37b425ee187218eeb3 |
02-Jul-2014 |
Ravi Nagarajan <nravi@broadcom.com> |
DO NOT MERGE: Send to local UUID for AV connection BTA expects local UUID to be passed into BTA_AvOpen. The value of source/sink was reversed in the btif layer thus causing connection failure bug 15837817 Change-Id: If159ac0491afcb75659336c98caba3cefe71ee7b
tif_av.c
|
a92c04f2dbd7f88853d6380d66c1f4d200674f97 |
01-Jul-2014 |
Matthew Xie <mattx@google.com> |
DO NOT MERGE Fix compilation issue This patch fixes broken compilation on KWD branch Change-Id: I9a1da11e33e938910dc556ed3e015bd3456e21ef
tif_hl.c
|
e3eecc1515a278520665bbf87a91837a5bebec46 |
02-Jul-2014 |
Sharvil Nanavati <sharvil@google.com> |
Fix build: change macro call from _DEBUG0 to _DEBUG. Change-Id: Iacbf4c33a7b690e2065471b85a6a4d82dd4a7fca
tif_hl.c
|
6ac369a8381a61fef594cd64c4ee89c7919cf00d |
02-Jul-2014 |
Matthew Xie <mattx@google.com> |
am 23ae7c52: Merge "Added code to reuse the signal fds and avoid fd close" into klp-wireless-dev * commit '23ae7c526b529cf1c76c4a4cc8a341545493404d': Added code to reuse the signal fds and avoid fd close
|
5ded33915f458e2de4a3a459b7b893ac9b57dd32 |
02-Jul-2014 |
git-zhenye.broadcom.com <zhenye@broadcom.com> |
am 359895ef: Fixed deadlock issue for concurrent multiple rfcomm connections. * commit '359895efb36a7e4f65fbcc9a28221b6ede44aadd': Fixed deadlock issue for concurrent multiple rfcomm connections.
|
6397cfb5b415d2622f81a27c646a441b108ee13f |
02-Jul-2014 |
Mike Lockwood <lockwood@google.com> |
Fix problem with A2DP initialization due to merge error btif_av_init() would fail when called a second time due to erroneous nulling of btif_av_cb.sm_handle Bug: 16014877 Change-Id: I7e6b213759e93372ac8ecaadc2b81452572f3f7d
tif_av.c
|
23ae7c526b529cf1c76c4a4cc8a341545493404d |
02-Jul-2014 |
Matthew Xie <mattx@google.com> |
Merge "Added code to reuse the signal fds and avoid fd close" into klp-wireless-dev
|
bf0ce82611b5133d61a0e544ec5bf53b567edfe7 |
20-Jun-2014 |
git-zhenye.broadcom.com <zhenye@broadcom.com> |
Added code to reuse the signal fds and avoid fd close Bug 15436535 Change-Id: Ica5b1915dd94699eb19c57b6904154493b0cc08c
tif_hl.c
|
359895efb36a7e4f65fbcc9a28221b6ede44aadd |
13-Jun-2014 |
git-zhenye.broadcom.com <zhenye@broadcom.com> |
Fixed deadlock issue for concurrent multiple rfcomm connections. Bug 15469934 Change-Id: I77a3dc97c92f0ccd5764220e8e0bf5c0689d7b12
tif_sock_rfc.c
|
2dc999935d4c69ae31ea93d9014165965dd373d6 |
17-Apr-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Support MAP Client role on Bluedroid. Implementation changes from BTA and BTIF layer to support MCE role on Bluedroid stack. Change-Id: I8547b0f28338e83edabae969121872ca23fdcb36
luetooth.c
tif_core.c
tif_dm.c
tif_mce.c
|
7ae3f9eebc4e930d51e6b61f845ffd0f9a8cb9f8 |
15-Jun-2014 |
Satya Calloji <satyac@broadcom.com> |
LE Onfound and Onlost feature BTIF and stack layer changes for onfound/onlost feature DO NOT MERGE Change-Id: Id52cdd5855ca8c0ff276b42613b51c4cd3882bfc
tif_gatt_client.c
|
5e177043e3dfcd70676761a40425179d16c4a7ce |
05-Jun-2014 |
Satya Calloji <satyac@broadcom.com> |
LE ADV Filter changes BTIF and stack layer changes for ADV filter feature DO NOT MERGE Change-Id: I865e57c41802751e172248547b8510598261ec94
tif_core.c
tif_gatt_client.c
|
b9b1f4e7a5cc96c57873a991f4ea3c3c08934c26 |
11-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE batch scan feature BTIF and stack changes for batch scan feature DO NOT MERGE Change-Id: I4dd2d551435e9f1f0e43906bd695294e97ed4bba
tif_gatt_client.c
|
ff7f41e67b7c3fb3f35a082d7123196f78e685ff |
01-Jul-2014 |
Matthew Xie <mattx@google.com> |
am 66432dcf: Add WBS support on Bluedroid (2/6) * commit '66432dcffe211e317d35978283a04a96d5620bdf': Add WBS support on Bluedroid (2/6)
|
66432dcffe211e317d35978283a04a96d5620bdf |
27-Apr-2014 |
Matthew Xie <mattx@google.com> |
Add WBS support on Bluedroid (2/6) Bug 13764086 Change-Id: I12bf302f7dd19efb497ad49d4d1d638a7a926049
tif_hf.c
tif_util.c
|
1acb61ce065053f91a0f8d43e8328c9eeec4b5ed |
15-Jun-2014 |
Satya Calloji <satyac@broadcom.com> |
LE Onfound and Onlost feature BTIF and stack layer changes for onfound/onlost feature Change-Id: Id52cdd5855ca8c0ff276b42613b51c4cd3882bfc
tif_gatt_client.c
|
1a9247a1229aa65b3d1dce16426177bc5828e54d |
05-Jun-2014 |
Satya Calloji <satyac@broadcom.com> |
LE ADV Filter changes BTIF and stack layer changes for ADV filter feature Change-Id: I865e57c41802751e172248547b8510598261ec94
tif_core.c
tif_gatt_client.c
|
c4e2596a112a0dd63ac681b1226548c0f95e828c |
11-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE batch scan feature BTIF and stack changes for batch scan feature Change-Id: I4dd2d551435e9f1f0e43906bd695294e97ed4bba
tif_gatt_client.c
|
63084199d86b31721e7265a1b72e218b019ece5b |
29-Jun-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
am e146869f: GAP: Remove device info from storage on Pairing Cancel * commit 'e146869fec903400e601d2ac7b0a59bd05934f0e': GAP: Remove device info from storage on Pairing Cancel
|
84b98f6d0c9dcd5ba148f58daedd4ec450f4c91c |
29-Jun-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
am b4801441: GAP:Add authentication failed error code in auth_compl_evt. * commit 'b4801441a5b7a093bc78f2143a8ed28605c51dc6': GAP:Add authentication failed error code in auth_compl_evt.
|
40ea618b79ee366fbe5fe267effa492e2c4bd5b6 |
29-Jun-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
am aef7a671: [2/2] Bluetooth: Security: Handle authentication rejected error status * commit 'aef7a6716e72e9304af36469500ee53c97350c21': [2/2] Bluetooth: Security: Handle authentication rejected error status
|
5eb938bacd3a214d55b34ef99448e36c1ecc8e67 |
29-Jun-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
am 59a88ec2: Bluetooth: Handle missing key event * commit '59a88ec207ead601c7ba5e767fd1373c7f2df70b': Bluetooth: Handle missing key event
|
4dbb90f07682b1d348ddf22189fce8e9e96b66ad |
29-Jun-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
am 831423ea: Bluetooth: Fix to avoid NULL pointer dereferences * commit '831423ea1879244e746f39d7696ad4a66681f306': Bluetooth: Fix to avoid NULL pointer dereferences
|
e146869fec903400e601d2ac7b0a59bd05934f0e |
14-Nov-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Remove device info from storage on Pairing Cancel Remove paired device information for SSP devices from the BT-IF layer storage on pairing cancel. Change-Id: I4660e3659866bd66339350b5cdb92bf3ad3cc850
tif_dm.c
|
b4801441a5b7a093bc78f2143a8ed28605c51dc6 |
07-Jan-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP:Add authentication failed error code in auth_compl_evt. There is an unhandle failed HCI error code when pairing with symbian OS phone nokia n95 which will cause no prompt when auth failed. Change-Id: I3a37c7732d1bf71c090bb968380d8c5f0af2ff79
tif_dm.c
|
aef7a6716e72e9304af36469500ee53c97350c21 |
31-Jul-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
[2/2] Bluetooth: Security: Handle authentication rejected error status Handle error codes in authentication complete event with failures like reject pairing , unspecified error. Change-Id: I392b7531a8625efbf91bf80f7f617a6954229892
tif_dm.c
|
59a88ec207ead601c7ba5e767fd1373c7f2df70b |
19-Mar-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Handle missing key event This change handles HCI_ERR_KEY_MISSING event coming to the stack when user doesn't enter any key and timeout happens. Change-Id: If530e8acce3f105e4f1e2841bf350ee5330f389e
tif_dm.c
|
831423ea1879244e746f39d7696ad4a66681f306 |
07-Jan-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Fix to avoid NULL pointer dereferences This fix for avoiding NULL pointer dereferences: - Added check for state checking in btm_remove_acl function to avoid sending disconnect command if already in Disconnecting state. - Added NULL check for 'pin_code' in btif_dm_pin_reply function - Null check before accessing in BD interface layer configuration node variables. - Add NULL check before accessing p_bd_addr variable to avoid null pointer exception while referring to invalid memory. Change-Id: Ib7ed45b6a1692785a45224d739a564f767e5b10f
tif_config.c
tif_dm.c
|
afa6e1abbedaad8fe854b0f43999b8aeb801af91 |
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of e8c3d75b to master Change-Id: I78ef69c4d54a36243620ae14296d3507e3339567
|
d5ebf6b695a5b40563b5fddca97c0591e39557f1 |
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
handle link key check in non_ble case Change-Id: Ibbdf3c4fbff9e53f8e2a85db9d6de62cd2925c60
tif_storage.c
|
1b5fda660a24f4c2884f94691f7537f40f67685c |
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
am f219040f: Merge "Reload Hid info only for bonded device" into klp-wireless-dev * commit 'f219040fb458fe4bb19d55d39c28d4535865a908': Reload Hid info only for bonded device
|
8e50f047de2999e89b6a19ec9bf513017fcde3f9 |
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of 6449e497 to master Change-Id: I01ef7ea6c4ce49c9d775b355fb5b082b25ffbc39
|
13594e6e4fbfb8a8458c3f25f5336d3996283c24 |
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
am bf611504: Merge "Save remote device name immediately" into klp-wireless-dev * commit 'bf611504d460adb10cc8c31f731504750104a1f3': Save remote device name immediately
|
249f600c1518c015f5cb45720cb022a203ba744e |
18-Jun-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Add is_connected() function (2/3) Change-Id: I73c4ea7f13982bf9c208996f9c749d2dfbe698be
luetooth.c
tif_dm.c
|
493a98a8de29a35808db28470736819af5fd22d2 |
28-Mar-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Add notification sent and congestion callbacks (2/4) This change introduces two new callbacks for applications to better handle LE notification flow control and transport congestion. The notification callback is invoked when the remote platform confirms an indication or when a local notification has been passed to the controller. No new notifications should be sent until a callback is received. Congestion callbacks are triggered when a GATT operation cannot be sent to the local Bluetooth controller. Repeatedly calling writeCharacteristic() for example will eventually trigger a congestion callback. Applications cannot send additional data until a further callback is received, indicating that the congestion has cleared up. Also fixes a memory leak issue that can trigger GKI exception for certain GATT operations. Change-Id: I7112bdfc1fedec2e390bd0ea52655d238683917f
tif_gatt_client.c
tif_gatt_server.c
tif_gatt_test.c
|
9536abefc8761390566030f570f3ff034639a81d |
27-Jun-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "LE: Add notification sent and congestion callbacks (2/4)"
|
93912473fde12ab5ab4b1be8774bbf43d47c7ddc |
26-Jun-2014 |
Mike Lockwood <lockwood@google.com> |
Merge some missing pieces of AVRCP controller support from klp-wireless-dev Change-Id: I1dc99496a6ed0e7d13cab9d7c95972d32ad88769
tif_rc.c
|
aa859a9af3767b5ee62ec882f83a922234a39cda |
26-Jun-2014 |
Mike J. Chen <mjchen@google.com> |
Merge "Change btif_gatt_client to use BTIF_TRACE_XXX macros instead of raw ALOGX"
|
bcbf9cd0727f6903f9cf6c165453539fc55b6072 |
26-Jun-2014 |
Mike J. Chen <mjchen@google.com> |
Change btif_gatt_client to use BTIF_TRACE_XXX macros instead of raw ALOGX This allows the trace flags in bt_trace.h to control whether these logs are enabled or not, to be consistent with rest of bluedroid. Change-Id: Ia4abeac42da181fd748a668d3ec5a9624ae8c19d Signed-off-by: Mike J. Chen <mjchen@google.com>
tif_gatt_client.c
|
17b04bd498405f2bb109a85562ebbdcb6bb06e95 |
28-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add notification sent and congestion callbacks (2/4) This change introduces two new callbacks for applications to better handle LE notification flow control and transport congestion. The notification callback is invoked when the remote platform confirms an indication or when a local notification has been passed to the controller. No new notifications should be sent until a callback is received. Congestion callbacks are triggered when a GATT operation cannot be sent to the local Bluetooth controller. Repeatedly calling writeCharacteristic() for example will eventually trigger a congestion callback. Applications cannot send additional data until a further callback is received, indicating that the congestion has cleared up. Also fixes a memory leak issue that can trigger GKI exception for certain GATT operations. Change-Id: Ib470c15ca1f577573a632e9afe4cb9e86680fd8c
tif_gatt_client.c
tif_gatt_server.c
tif_gatt_test.c
|
3c36809a32db64eccd21df7415477810c98d9e3f |
22-Jun-2014 |
Matthew Xie <mattx@google.com> |
Merge "switch a2dp sync and source to the correct uuids"
|
d6151e9811a35ac965bfb96ad77c427d9a4f1325 |
22-Jun-2014 |
Matthew Xie <mattx@google.com> |
switch a2dp sync and source to the correct uuids bug 15687722 Change-Id: I09e5fdc7bf7c1bb0ff3c87dc43b228e3761cfa36
tif_av.c
|
40a1994ae3043eb31d2d7993294ca9faaeafffb9 |
21-Jun-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "LE: Add is_connected() function (2/3)"
|
5c0b052090a57b3926669c23349b0f0db68853f8 |
18-Jun-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Add is_connected() function (2/3) Change-Id: I73c4ea7f13982bf9c208996f9c749d2dfbe698be
luetooth.c
tif_dm.c
|
93f6651217c7cf1eda0c46de1ecd718b397edbae |
19-Jun-2014 |
Sharvil Nanavati <sharvil@google.com> |
Fix build, replace logging macro. Change-Id: Ib1189b887d57253940fa38e8af24ea03462c403e
tif_storage.c
|
e8c3d75b75493911ebf0f99c83676359657178f7 |
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: BTIF and APPL. Change-Id: I5b1214642bbb4b9aecc0fd2c899a6ec2c9793286
tif_av.c
tif_core.c
tif_dm.c
tif_gatt_client.c
tif_gatt_multi_adv_util.c
tif_gatt_server.c
tif_gatt_util.c
tif_hf.c
tif_hf_client.c
tif_hh.c
tif_hl.c
tif_media_task.c
tif_pan.c
tif_rc.c
tif_sm.c
tif_sock.c
tif_sock_rfc.c
tif_sock_sdp.c
tif_sock_thread.c
tif_sock_util.c
tif_storage.c
|
f281b43fbf6832b80651e0dbf300294ba9808f20 |
15-May-2014 |
Priti Aghera <paghera@broadcom.com> |
Reload Hid info only for bonded device Check if the device is bonded before loadind HID device information after BT reset. If the HID info exists in NVRAM for unbonded device, the device will not be able to repair. bug 14837902 Change-Id: I5e6d5e8c5344ca8ae18f102e40867745d3f460ab
tif_storage.c
|
533cc76a012444993eb5e566238f71fc9f24ba0d |
19-Jun-2014 |
Matthew Xie <mattx@google.com> |
am 27232899: am 283aa16d: Merge "Bluedroid: Avoid multicast address for tun-tap interface" * commit '2723289960c3eca333aa25369bde59cf8d36dcf4': Bluedroid: Avoid multicast address for tun-tap interface
|
2723289960c3eca333aa25369bde59cf8d36dcf4 |
19-Jun-2014 |
Matthew Xie <mattx@google.com> |
am 283aa16d: Merge "Bluedroid: Avoid multicast address for tun-tap interface" * commit '283aa16d5f16bc10b5491661b5729c5f25635731': Bluedroid: Avoid multicast address for tun-tap interface
|
01364c729dd8f94be9959300188c94324960e0df |
08-Apr-2014 |
Loic Poulain <loic.poulain@intel.com> |
Bluedroid: Avoid multicast address for tun-tap interface Linux Kernel disallows to set an ethernet multicast address as ethernet device address. The IEEE has specified that the most significant bit of the most significant byte of a mac address is used for multicast. If its a 1, that means multicast, 0 means unicast. Bluedroid uses the BD address to set the tun-tap intf mac address. This BD address can be randomly auto generated, possibly with the multicast bit. To avoid any address issue, this patch masks this bit before setting the ethernet mac address. Change-Id: Ifff4ec7237ae6cbef3b8d4c23096c5df65e1431c Signed-off-by: Loic Poulain <loic.poulain@intel.com> Reviewed-on: https://android.intel.com/184768 Reviewed-by: Zhang, Jianxun <jianxun.zhang@intel.com> Tested-by: Zhang, Jianxun <jianxun.zhang@intel.com>
tif_pan.c
|
c4262059511336139735f410dd8d3ff303576057 |
18-Jun-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "LE: Add ability to pass address type to GATT test command"
|
4ad470e33021be4246ae539e1bcb7a346dbb4405 |
03-Jun-2014 |
Mike Lockwood <lockwood@google.com> |
Move AVRCP controller support to separate HAL interface Change-Id: Ib7dcd7b90f85cf3b25148e2929d8921c6db37aa2
luetooth.c
tif_av.c
tif_rc.c
|
3e8a242fcbeebea2857fa964ca48624d8433333e |
23-May-2014 |
Mike Lockwood <lockwood@google.com> |
More work on A2DP Sink: Output audio data through A2DP audio HAL rather than playing directly to native AudioTrack API. Add separate HAL interface for A2DP sink Change-Id: I6c6cb6088c350e104b4a7354f328b29c7178e295
luetooth.c
luetoothTrack.cpp
tif_av.c
tif_core.c
tif_media_task.c
|
ce24765fe7620c34e8d88ed4f826c8a6917582b2 |
20-Mar-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
SBC Decoder for A2DP SINK Change-Id: Ic8d1dd81d1788324ec140fe0d1379dfff33deb54
tif_media_task.c
|
f7dd9f5779680da37dc89e5df2b26d436487818c |
24-Oct-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Add A2DP Sink Support Change-Id: I9affefdd2d00597545e49c593ef3bddb110d4c9c
luetoothTrack.cpp
tif_av.c
tif_hf.c
tif_hf_client.c
tif_media_task.c
tif_profile_queue.c
|
41d4a266ceca77bb09ab1bf5c04c30d15f3ded3a |
19-Aug-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Add support for HFP Client role. Implementation changes in BTA and BTIF layer to support HFP Client role. Change-Id: I9f939c18e8f989a50f298d0b313c5a0959c030a7
luetooth.c
tif_dm.c
tif_hf_client.c
tif_storage.c
tif_util.c
|
1628d79747b33b5b655ef813ee133fbc322a5991 |
04-Jun-2014 |
Sharvil Nanavati <sharvil@google.com> |
Parse auto_pair_devlist.conf file with the generic config parser. Change-Id: Idfd1aca2417d74725a8f9ac67b1ca946a33bf14d
tif_storage.c
|
10aecea0649e523ad9e94b5d0256e72729ec5875 |
29-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Implement GKI timers based on wake alarms and wake locks. Before this change, bluedroid was unable to acquire wake locks because the Bluetooth process didn't have permissions to write to /sys/power/wake_*. We are now making wake locks accessible to bluedroid through a HAL callout back into Java code. The previous design did not use wake alarms. Bluedroid would attempt to hold a wake lock until all pending timers expired, which is awful if a timer is scheduled seconds or minutes from now. There is a 15min timer in bluedroid now so holding a wake lock for the entire duration of pending alarms is unacceptable (power cost). The new implementation uses a hybrid approach: if the next deadline is < 3s away, we take a wake lock. If it is further than 3s away, we set a wake alarm and release the wake lock. As a result of this change, we have also eliminated a thread whose sole purpose was to wake up every 10ms and update timers. Change-Id: I46cd4edfcad2f5dce23c4003a14a617e7bf00541
luetooth.c
|
2a00176ae263607dd2de9408fd804d4c4028b511 |
11-Jun-2014 |
Prerepa Viswanadham <dham@google.com> |
Fix build for aosp_manta Change-Id: Ic1e2363e7fb7d23dcaef8e989cae37606f2af664
tif_core.c
|
8d41691e6b16ba945711e8c3846df1ec70fdb724 |
31-May-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Support for reading LE specific controller features Support for reading LE specific controller features via get adapter properties API Change-Id: Ia0b813be45fb826ce27d1d7a31ca41650d7286dd
tif_core.c
tif_dm.c
|
da271ee4a0afcf5516208dc8df18a4da41a47124 |
31-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Whitelist IPv6 packets so they can be sent over PAN. Change-Id: I68e96bc34af1dfded2761c9bc780c089076d15e0
tif_pan.c
|
1a3006f317b1b493dde1b80c4debbcf1bf5f6727 |
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Eliminate dead code (helped by compiler warnings). I've removed all functions that the compiler decided were unused. Change-Id: I0cbddf874ebd1586abe29b80e8d6390680679542
tif_config.c
tif_dm.c
tif_hh.c
tif_hl.c
tif_media_task.c
tif_sock_rfc.c
tif_storage.c
|
847ea13e09f3fc1d2a46a8b75109ef89243ace31 |
26-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Update RFCOMM socket code to use list data structure. Change-Id: I70402d8bfaa36b36d3d4b8f3cec98371691e86c9
tif_sock_rfc.c
|
fe10dd40a0b5b553467fff293a6addc56e4eae90 |
26-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Update btif_profile_queue to use the list data structure. The profile queue maintains a list of pending connect operations for each profile. If a connect is followed by a disconnect before the queued connect is dispatched, the disconnect will have no effect and the connect will proceed. This code clearly needs to be re-thought; it may be a good idea to abandon the connect queue entirely in the long-run. Change-Id: Ic0e85654abcf7a47f65953edb301eb9524394950
tif_profile_queue.c
|
e7c4f99f1ca3da0ac46aa7425a37b383177c699f |
05-Sep-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: On Suspend ignore media task timer event On Recieving Suspend confirmation from remote device, Media task timer reload and tx_timer is made false, hence media task will not be stopped at that instant. Media task timer expires causing buffer to be allocated. Changes done to ensure buffer is allocated only if tx_timer is true. Change-Id: I971a82cccc64ba033475ad532b096862968de942
tif_media_task.c
|
b804e2114b4e9c2d2481d62538f4d450d7b67128 |
11-Jun-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Add ability to pass address type to GATT test command Currently the GATT test command to connect a remote device assumes a public Bluetooth device address. This patch adds the ability to pass in the address type via the test command interface. Change-Id: Ia50792738796b97d1d02d6f33cb0586c82dcd477
tif_gatt_test.c
|
80fcd9447bc862b321f5bd5c507c2f5839e01c24 |
11-Jun-2014 |
Matthew Xie <mattx@google.com> |
am 8b8050ad: am 197a801b: Merge "Bluedroid: Fix UUID unsigned/signed comparison" * commit '8b8050ad5f2f4fd64766c99378fa0866d89230c6': Bluedroid: Fix UUID unsigned/signed comparison
|
0c4ec0dae97523cadc9207e98c4a1edff7e2e7cf |
11-Jun-2014 |
Prerepa Viswanadham <dham@google.com> |
Fix build for aosp_manta Change-Id: Ic1e2363e7fb7d23dcaef8e989cae37606f2af664
tif_core.c
|
8b8050ad5f2f4fd64766c99378fa0866d89230c6 |
11-Jun-2014 |
Matthew Xie <mattx@google.com> |
am 197a801b: Merge "Bluedroid: Fix UUID unsigned/signed comparison" * commit '197a801bb5f12675d025bf1b7d2cac40924abe77': Bluedroid: Fix UUID unsigned/signed comparison
|
3a1ca50d0def4078a0db82bcdeecfe408ca4af64 |
03-Jun-2014 |
Mike Lockwood <lockwood@google.com> |
Move AVRCP controller support to separate HAL interface Change-Id: Ib7dcd7b90f85cf3b25148e2929d8921c6db37aa2
luetooth.c
tif_av.c
tif_rc.c
|
309243751678f395e6f7323e45433e5476dc17ef |
23-May-2014 |
Mike Lockwood <lockwood@google.com> |
More work on A2DP Sink: Output audio data through A2DP audio HAL rather than playing directly to native AudioTrack API. Add separate HAL interface for A2DP sink Change-Id: I6c6cb6088c350e104b4a7354f328b29c7178e295
luetooth.c
luetoothTrack.cpp
tif_av.c
tif_core.c
tif_media_task.c
|
8e08ad12eae66877f9725ca2d66fc69fe6762340 |
20-Mar-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
SBC Decoder for A2DP SINK Change-Id: Ic8d1dd81d1788324ec140fe0d1379dfff33deb54
tif_media_task.c
|
cc35559160745c60b42ae182002a59337d844d09 |
24-Oct-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Add A2DP Sink Support Change-Id: I9affefdd2d00597545e49c593ef3bddb110d4c9c
luetoothTrack.cpp
tif_av.c
tif_hf.c
tif_hf_client.c
tif_media_task.c
tif_profile_queue.c
|
6449e497dfe4d500810c3e7b4d7d056027c33a0e |
06-Jun-2014 |
Sharvil Nanavati <sharvil@google.com> |
Eliminate more dead code in GKI. Change-Id: I4c0000445535e5300b83a18f5f6ca45f1ef797da
tif_media_task.c
|
197a801bb5f12675d025bf1b7d2cac40924abe77 |
11-Jun-2014 |
Matthew Xie <mattx@google.com> |
Merge "Bluedroid: Fix UUID unsigned/signed comparison"
|
479a9a3750e243b40663ddbd1ac44d4fc1c3ec4e |
04-Jun-2014 |
Sharvil Nanavati <sharvil@google.com> |
Parse auto_pair_devlist.conf file with the generic config parser. Change-Id: Idfd1aca2417d74725a8f9ac67b1ca946a33bf14d
tif_storage.c
|
9bce2266bae83dfeb57319076dee569324a6d0a8 |
29-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Implement GKI timers based on wake alarms and wake locks. Before this change, bluedroid was unable to acquire wake locks because the Bluetooth process didn't have permissions to write to /sys/power/wake_*. We are now making wake locks accessible to bluedroid through a HAL callout back into Java code. The previous design did not use wake alarms. Bluedroid would attempt to hold a wake lock until all pending timers expired, which is awful if a timer is scheduled seconds or minutes from now. There is a 15min timer in bluedroid now so holding a wake lock for the entire duration of pending alarms is unacceptable (power cost). The new implementation uses a hybrid approach: if the next deadline is < 3s away, we take a wake lock. If it is further than 3s away, we set a wake alarm and release the wake lock. As a result of this change, we have also eliminated a thread whose sole purpose was to wake up every 10ms and update timers. Change-Id: I46cd4edfcad2f5dce23c4003a14a617e7bf00541
luetooth.c
|
bf611504d460adb10cc8c31f731504750104a1f3 |
05-Jun-2014 |
Matthew Xie <mattx@google.com> |
Merge "Save remote device name immediately" into klp-wireless-dev
|
ed999f5e92ef9e718f4e6a5d6e68caf1001961c8 |
05-Jun-2014 |
Matthew Xie <mattx@google.com> |
Save remote device name immediately bug 7381249 Change-Id: Ief1910c608116ebc28f5dc3e5804be65797ec53c
tif_storage.c
|
9546abf9fc4400853803ee220482ae63e63f0d9d |
31-May-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Support for reading LE specific controller features Support for reading LE specific controller features via get adapter properties API Change-Id: Ia0b813be45fb826ce27d1d7a31ca41650d7286dd
tif_core.c
tif_dm.c
|
f1d9b90f44336264a7dfee8708f208cd7b7fd541 |
31-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Whitelist IPv6 packets so they can be sent over PAN. Change-Id: I68e96bc34af1dfded2761c9bc780c089076d15e0
tif_pan.c
|
477057cc54dde60732f9a97232f0042c2c64f3a8 |
24-May-2014 |
Matthew Xie <mattx@google.com> |
Revert "add wakelock control callback" This reverts commit cd7896c5c4bffa5a6f9a414177ea0038d6172964.
luetooth.c
|
8075fbd743d5eb3937a11156abf2c9a4f051434c |
23-May-2014 |
Dmitry Grinberg <dmitrygr@google.com> |
am 262685fe: am cd7896c5: add wakelock control callback * commit '262685fe26c0ccc7e196def7db1d7447c51efdbb': add wakelock control callback
|
262685fe26c0ccc7e196def7db1d7447c51efdbb |
23-May-2014 |
Dmitry Grinberg <dmitrygr@google.com> |
am cd7896c5: add wakelock control callback * commit 'cd7896c5c4bffa5a6f9a414177ea0038d6172964': add wakelock control callback
|
cd7896c5c4bffa5a6f9a414177ea0038d6172964 |
22-May-2014 |
Dmitry Grinberg <dmitrygr@google.com> |
add wakelock control callback Change-Id: Iffa8f33767a037fceb4757cdff07f25f30acf453
luetooth.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
tif_av.c
tif_rc.c
|
bf0e4b26d8f0748ff4f9522a2ac7001bfb9ca5cc |
20-May-2014 |
Wei Wang <weiwa@google.com> |
Fix build issue for devices without BLE features. Change-Id: I6499663d253c791cc739ed76b839eb3aefe6613a
tif_dm.c
tif_gatt_multi_adv_util.c
|
2a647f406c94a3a85e984c23428260dddea3f4ee |
20-May-2014 |
Wei Wang <weiwa@google.com> |
Add bt_target.h header Change-Id: I6b584e3e610d20348bf410f434164b8a5e738f04
tif_gatt_multi_adv_util.c
|
29fa7d710857881b6c61cff949d42922b70e8df2 |
20-May-2014 |
Wei Wang <weiwa@google.com> |
Fix build issue for devices without BLE features. Change-Id: I6499663d253c791cc739ed76b839eb3aefe6613a Conflicts: btif/src/btif_dm.c btif/src/btif_gatt_multi_adv_util.c Conflicts: btif/src/btif_dm.c btif/src/btif_gatt_multi_adv_util.c
tif_dm.c
tif_gatt_multi_adv_util.c
|
ed534e330bf63c72e778fc8daae09ddd63c395b2 |
20-May-2014 |
Wei Wang <weiwa@google.com> |
Revert "Revert "LE: Add RRA offloading and vendor specific PCF commands"" This reverts commit 146bb736bc1cdfd679bbafcf3f33c7af612096b9. Change-Id: Ie4e6b4d7118a622d04c46623add1073906366edf
tif_dm.c
|
a6ce7751d84218c193eb90d390aef23217b1737e |
20-May-2014 |
Wei Wang <weiwa@google.com> |
Revert "Revert "LE Multi ADV feature"" This reverts commit ea85048a8e86b1e1b6b725649f6bb0834ba17301. Change-Id: I9a9305db4fabff07b4309a38f65361dca3f5f37c
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
ea85048a8e86b1e1b6b725649f6bb0834ba17301 |
20-May-2014 |
Wei Wang <weiwa@google.com> |
Revert "LE Multi ADV feature" This reverts commit 87776cf5e201b18646cbc16f11a7110d5ffe510c. Change-Id: I5b544a5c965999096b665b1bd2edb021e3054be8
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
146bb736bc1cdfd679bbafcf3f33c7af612096b9 |
20-May-2014 |
Wei Wang <weiwa@google.com> |
Revert "LE: Add RRA offloading and vendor specific PCF commands" This reverts commit 15fa3be8ecd576b9ef88e20cf9a6f4bd765cbc6b. Change-Id: Iaa484508ac664d4cb6c94758c2984d53263a902a
tif_dm.c
|
15fa3be8ecd576b9ef88e20cf9a6f4bd765cbc6b |
12-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE: Add RRA offloading and vendor specific PCF commands Change-Id: Iadca8e73ceaadcd0429421ea70f1b76644e88c42
tif_dm.c
|
87776cf5e201b18646cbc16f11a7110d5ffe510c |
01-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE Multi ADV feature BTIF and stack changes for LE multi ADV feature Change-Id: I5e009ff8cbac5fc6f92ca943c61c4faf98e4e2ce
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
0943c10ed5713a08659f08e39e13de4894aaba61 |
12-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE: Add RRA offloading and vendor specific PCF commands Change-Id: Iadca8e73ceaadcd0429421ea70f1b76644e88c42
tif_dm.c
|
ffb3960bb05f9acb0717d213612403487e9ad433 |
01-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE Multi ADV feature BTIF and stack changes for LE multi ADV feature Change-Id: I5e009ff8cbac5fc6f92ca943c61c4faf98e4e2ce
tif_gatt_client.c
tif_gatt_multi_adv_util.c
|
bfa5cf78dc26b971236190c6fb42353a8d30a649 |
15-May-2014 |
Mike Lockwood <lockwood@google.com> |
Merge "[2/4] Bluetooth: Add support for HFP Client role." into klp-wireless-dev
|
4a1a92a5f945ecbadc8a8c95ba18cca2c396c26a |
15-May-2014 |
Mike Lockwood <lockwood@google.com> |
Merge "Submitted on behalf of 3rd party copied from external/bluetooth/bluedroid" into klp-wireless-dev
|
7d208f286865ff58ba5e79299c42b9686cca25cb |
10-May-2014 |
Prerepa Viswanadham <dham@google.com> |
LE: Add API to set scan interval and window (2/4) Delete client_if from scan api's Change-Id: I66e0e17221601cd07ea77cf3d61ad9ce20a603a4
tif_gatt_client.c
|
714078d91aa0ecbe29661aac869dc397d8884042 |
10-May-2014 |
Prerepa Viswanadham <dham@google.com> |
LE: Add API to set scan interval and window (2/4) Delete client_if from scan api's Change-Id: I66e0e17221601cd07ea77cf3d61ad9ce20a603a4
tif_gatt_client.c
|
bea4131cac3214e0ad26ea8258e270448f23f1f3 |
09-May-2014 |
Matthew Xie <mattx@google.com> |
Init variables to fix compiler error Change-Id: Ib41ecc8be53f64f10446b758c54eaf41f2a2e725
tif_hl.c
|
1025687c6679608fe9df918f37011414ffc72b62 |
19-Aug-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
[2/4] Bluetooth: Add support for HFP Client role. Implementation changes in BTA and BTIF layer to support HFP Client role. Change-Id: I9f939c18e8f989a50f298d0b313c5a0959c030a7
luetooth.c
tif_dm.c
tif_hf_client.c
tif_storage.c
tif_util.c
|
3fe1b49071420903cb8e3082ec04e76296352690 |
29-Apr-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
Submitted on behalf of 3rd party copied from external/bluetooth/bluedroid Initial commit for HFP Client Change-Id: I26b7d49b76ab28b019314ddb514e8f46b3bc4772
tif_hf_client.c
|
740def526e757f5ea8f30d9d28d1e7a668dadc42 |
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Eliminate dead code (helped by compiler warnings). I've removed all functions that the compiler decided were unused. Change-Id: I0cbddf874ebd1586abe29b80e8d6390680679542
tif_config.c
tif_dm.c
tif_hh.c
tif_hl.c
tif_media_task.c
tif_sock_rfc.c
tif_storage.c
|
d9e5b3490bf41f912823af920cc616e57e0fec28 |
26-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Update RFCOMM socket code to use list data structure. Change-Id: I70402d8bfaa36b36d3d4b8f3cec98371691e86c9
tif_sock_rfc.c
|
3542d5a93129b6a8026501f87877017173530ae0 |
26-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Update btif_profile_queue to use the list data structure. The profile queue maintains a list of pending connect operations for each profile. If a connect is followed by a disconnect before the queued connect is dispatched, the disconnect will have no effect and the connect will proceed. This code clearly needs to be re-thought; it may be a good idea to abandon the connect queue entirely in the long-run. Change-Id: Ic0e85654abcf7a47f65953edb301eb9524394950
tif_profile_queue.c
|
7e4c60ce7757d935901f53d1f21ecc696aa89979 |
05-Sep-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: On Suspend ignore media task timer event On Recieving Suspend confirmation from remote device, Media task timer reload and tx_timer is made false, hence media task will not be stopped at that instant. Media task timer expires causing buffer to be allocated. Changes done to ensure buffer is allocated only if tx_timer is true. Change-Id: I971a82cccc64ba033475ad532b096862968de942
tif_media_task.c
|
27c81965d8bcf9050b6fa66e004373ca2dea52a1 |
05-May-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
MHF: Route call to correct HS in multi call scenario. - This change makes sure that audio routes back to correct headset in multi call scenario even though the other headset tries to answer or dial. - Ignore setting hf_idx for ATA/BLDN received from HS for a waiting call when an active/held call is already present. Change-Id: I19949471d481bf911fda2222dc6d730d1a821b65
tif_hf.c
|
550b319b217739808fe95c57aa0f422dbf5db9d1 |
29-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Resolve Pairing failure with IPhone When pairing is initiated from the iPhone side, it sets Bonding bit without MITM. We responded to this with No bonding, No MITM. This resulted in JustWorks & Unauthenticated link key. After pairing iPhone initiates a RFCOMM connection. This caused a link key upgrade to be done, which the iPhone rejected, resulting in pairing failure. To resolve this the following enhancements were made 1. If locally initiated pairing always set Bonding bit + MITM 2. If remote initiated a. copy over the bonding bit b. if peer has DisplayYesNo set MITM 3. As a fallback if remote had MITM, enable MITM in our response This forces pairing to use Bonding bit+MITM thus resulting in authenticated combination linkkey Change-Id: I08f16c80821bc822023180d01868614ba41e6d88
tif_dm.c
|
6ef30dba0eb77593c9c6ce5843848961ba12d57b |
06-Jan-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Update local device name immediately Though the function btif_config_set_str requests to save device name immediately, sometimes it doesn't call save device name if the cached changes are more. So calling the "btif_config_save" explicitly to avoid failure cases. Change-Id: I9fb05caf284d6a6feb906f87a4db19896182d2c9
tif_storage.c
|
7fa4fba6f59f97df00aff07dbe8fb21b114b3c2c |
17-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Merge BT 4.1 features The features include: - LE Peripheral Mode - Link Layer topology (LE Central & Peripheral Concurrency) - Dual Mode Topology (Ability to choose LE transport when connecting with other Dual Mode devices) - Fast advertising Interval - Limited Discovery Time Changes - GAP Authentication and Lost Bond - Dual Mode Addressing - Common Profile and Service Error Code - 32 bit UUIDs Change-Id: Ic6701da4cf6aaa390ff2c8816b43157f36b7fb42 Conflicts: stack/btu/btu_hcif.c
luetooth.c
tif_dm.c
tif_gatt_client.c
tif_gatt_server.c
tif_gatt_test.c
tif_gatt_util.c
tif_storage.c
|
3b8b972a8151c081905f3c1273e5d6cdd3401354 |
30-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
fix random crashes in bd2str caused by exceeding string array remove all casts to avoid sign extension of bd address as this may exceed the size of destination str buffer Change-Id: I27dc7e61b52440c6b284b7e9931e6daa66afbf12
tif_util.c
|
90a32530e8b9908f2af64ce98931684fa20c061b |
15-Mar-2014 |
Nitin Srivastava <nitinsr@codeaurora.org> |
Add support for Multi-HFP devices 1. Add multi headset support in stack. 2. Each HS will be associated with unique CB in BTIF and also corresponding SCB in BTA. 3. Upstream event callbacks will be sent to specific HS based on BD_ADDR. 4. Similiarly all commands to BTIF will be for specific HS. Change-Id: I0dc6b1b54f16244b802d818ae60944877a41d020
tif_hf.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
tif_rc.c
|
fc07218666349142c0de3b461921b8cda792aa76 |
27-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
Bluetooth: GAP: Remove bonded device info on Authentication fail Remove bonded device information from the BT-IF layer storage on authentication failure if already bonded with just works model. from QCOM Change-Id: Ia3c1635c446f39b1dbd4cdd0122c2f70cbbc8dd7
tif_dm.c
tif_storage.c
|
f7083df9c30849fabfb2d03ce95701f110a2df99 |
29-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Fix issue of HDP select thread not exiting during BT OFF Change-Id: I52a0a3caff327a7a51e293c431ddbc99db690180
tif_hl.c
|
ad7a6009746430da82ad7d8ee4a4784db7087ae4 |
21-Apr-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
HID: Use dynamic memory while sending data This patch uses dynamic memory allocation while sending HID output data to remote device depending on size of data to be sent. Without this patch fixed size static buffer of 200 bytes was being used for sending data to remote device, which was resulting in crash in case data size to be sent to remote device was greater than 200 bytes. Change-Id: I5ed12422355e88d7ef0391668800d7619ca3b685
tif_hh.c
|
8cd229d4765330b554eedd6919b9f41ca7989e7e |
25-Oct-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
HID: Parse paired hid devices from bluez. This patch adds support for parsing SDP records of paired HID devices from bluez device storage path and store the parsed hid sdp data into bluedroid storage path. Without this patch, it was not possible to have paired HID devices during upgrade from BlueZ to Bluedroid Stack. Change-Id: I7db4a801f3cf9ca46fc0eabfd929e8d7c16b5edb
tif_config_util.cpp
|
dda369e3a6b39c7df25072fc880fbd4903553f5c |
28-Nov-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Try to retrieve CoD from NVRAM if 0 This patch tries to retreive CoD from NVRAM if CoD is 0. This is because in scenarios when airplane mode on/off, inquiry is not performed again on devices shown in Available devices List of UI, so CoD is 0 during SSP information as database of stack is not properly updated since inquiry is not performed again. Without this patch it was observed because of wrong CoD info device icon for HID mouse was changed to Joystick and device is not shown in Paired List. Also some extra debug logs are added in code for better debugging. Change-Id: I14858ccee04728cb4b9cd60d397b79fa6494b842
tif_dm.c
|
ee27b932f65a3c5a0a52067dac8a1be729c7a435 |
13-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
HID: Remove device from nvram on auth failure This patch removed hid pointing device from nvram on authentication failure due to pairing timeout or when wrong passkey is entered. Without this patch it was observed that hid pointing device was always shown in paired list when DUT was restarted after authentication failure. CL from qcom(Hemant Gupta) Change-Id: I69c43d2ed982d5d5abfd5707db90ef4b5c65b34f
tif_dm.c
|
f11d21fa60be8a2cd072968bf5e1bb23ce5caabf |
21-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
HID: Use dynamic memory while sending report This patch uses dynamic memory allocation while sending HID output data to remote device depending on size of data to be sent. Without this patch fixed size static buffer of 200 bytes was being used for sending data to remote device, which was resulting in crash in case data size to be sent to remote device was greater than 200 bytes. CL from qcom(Hemant Gupta) Change-Id: Icc8cd4a4ecfd4bc30cbf848a7c865fcf9308ddf8
tif_hh.c
|
8029dc8f0332d1135aa93e8e5daa46e3eb7b2500 |
21-Apr-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
HID: Update SSR parameters during copy. This patch correctly stores SSR parameters (max latency and min timeout) retrieved from remote device SDP record in NVRAM. Change-Id: I87d8b6181981090df21ab746deac7053a1d0e938
tif_hh.c
|
4186b0ec7e0b7efe17c3b7cb8546ff359e099408 |
07-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Add flow control for PAN. This change reads from the TAP fd only when btpan_cb.flow == 1. The value of this flag changes based on L2CAP congestion events. http://b/13246629 Change-Id: Ic28bf65737dbd74c41b68198fceee58e3bff08d4 Conflicts: btif/src/btif_pan.c
tif_pan.c
|
b203d478f4835f5e35217874a1787e1914328f7c |
21-Nov-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add controller based advertising filter API (2/2) Change-Id: I444654bf19a048d5fcef33f79edbf1cdda3d3b62
tif_core.c
tif_gatt_client.c
tif_gatt_util.c
|
04c45382988247e04d50f8599c5e4501e0934553 |
24-Dec-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: GAP: Send bond none in case of temp pairing Send BOND_NONE in case of temporary device pairing on receiving the authentication complete, so that UI doesn't get stucked in pairing for that device. Change-Id: Ided412ef89d928f958a0052362be145232411c0a
tif_dm.c
|
54db2c249efa91082c5a167a924a527ec73ff38d |
13-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Remove executable bit on source files. Change-Id: Id456478aea626f57fed3479346e8fb4dbd0fafa6
luetooth.c
tif_av.c
tif_media_task.c
tif_util.c
|
4974d81a88dd7ffa1951242dfc830d329f3cf378 |
05-May-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
MHF: Route call to correct HS in multi call scenario. - This change makes sure that audio routes back to correct headset in multi call scenario even though the other headset tries to answer or dial. - Ignore setting hf_idx for ATA/BLDN received from HS for a waiting call when an active/held call is already present. Change-Id: I19949471d481bf911fda2222dc6d730d1a821b65
tif_hf.c
|
d8e742ff26096ed599623285047aca39b9e7a87a |
05-May-2014 |
Matthew Xie <mattx@google.com> |
Merge "fix random crashes in bd2str caused by exceeding string array" into klp-wireless-dev
|
a217ab9a0294a8285641b141efccf7d54b437a33 |
29-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Resolve Pairing failure with IPhone When pairing is initiated from the iPhone side, it sets Bonding bit without MITM. We responded to this with No bonding, No MITM. This resulted in JustWorks & Unauthenticated link key. After pairing iPhone initiates a RFCOMM connection. This caused a link key upgrade to be done, which the iPhone rejected, resulting in pairing failure. To resolve this the following enhancements were made 1. If locally initiated pairing always set Bonding bit + MITM 2. If remote initiated a. copy over the bonding bit b. if peer has DisplayYesNo set MITM 3. As a fallback if remote had MITM, enable MITM in our response This forces pairing to use Bonding bit+MITM thus resulting in authenticated combination linkkey Change-Id: I08f16c80821bc822023180d01868614ba41e6d88
tif_dm.c
|
2a55a6e1955be41227ebe850090c925867d9b98b |
02-May-2014 |
Matthew Xie <mattx@google.com> |
Merge "Fix issue of HDP select thread not exiting during BT OFF" into klp-wireless-dev
|
f5726daa6c720685cbc0e5250a2a5ee6b4860210 |
25-Mar-2014 |
lpoulain <loic.poulain@intel.com> |
Bluedroid: Fix UUID unsigned/signed comparison UUID type was never detected as a 16 bits UUID due to a comparison between signed and unsigned char in uuidType(). Change-Id: I6205ab4c2568f03b4692e0ce8a1dec216f1cdc0e Signed-off-by: lpoulain <loic.poulain@intel.com> Signed-off-by: Yong Yao <yong.yao@intel.com>
tif_gatt_util.c
|
fbf76881316471faf631dc543089efaeaf72df8d |
06-Jan-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Update local device name immediately Though the function btif_config_set_str requests to save device name immediately, sometimes it doesn't call save device name if the cached changes are more. So calling the "btif_config_save" explicitly to avoid failure cases. Change-Id: I9fb05caf284d6a6feb906f87a4db19896182d2c9
tif_storage.c
|
8fe58875ce67c6e1099e7ba2339dcd2b979491b0 |
17-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Merge BT 4.1 features The features include: - LE Peripheral Mode - Link Layer topology (LE Central & Peripheral Concurrency) - Dual Mode Topology (Ability to choose LE transport when connecting with other Dual Mode devices) - Fast advertising Interval - Limited Discovery Time Changes - GAP Authentication and Lost Bond - Dual Mode Addressing - Common Profile and Service Error Code - 32 bit UUIDs Change-Id: Ic6701da4cf6aaa390ff2c8816b43157f36b7fb42
luetooth.c
tif_dm.c
tif_gatt_client.c
tif_gatt_server.c
tif_gatt_test.c
tif_gatt_util.c
tif_storage.c
|
9b4676076ba984de33984276694347797f240a9d |
30-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
fix random crashes in bd2str caused by exceeding string array remove all casts to avoid sign extension of bd address as this may exceed the size of destination str buffer Change-Id: I27dc7e61b52440c6b284b7e9931e6daa66afbf12
tif_util.c
|
2cb90bc58fc075ec2f814ada5ae8f728380566c1 |
15-Mar-2014 |
Nitin Srivastava <nitinsr@codeaurora.org> |
Add support for Multi-HFP devices 1. Add multi headset support in stack. 2. Each HS will be associated with unique CB in BTIF and also corresponding SCB in BTA. 3. Upstream event callbacks will be sent to specific HS based on BD_ADDR. 4. Similiarly all commands to BTIF will be for specific HS. Change-Id: I0dc6b1b54f16244b802d818ae60944877a41d020
tif_hf.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
tif_rc.c
|
a0a1c864abe6076442cd2c9e48d8f65b8d3a3c6e |
29-Apr-2014 |
Bill Yi <byi@google.com> |
Merge commit 'b48f9962d57d9c500bfa8c8dbe65ce04f67918e5' into HEAD
|
a7ea809912e5a945d657957491753260826422f4 |
27-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
Bluetooth: GAP: Remove bonded device info on Authentication fail Remove bonded device information from the BT-IF layer storage on authentication failure if already bonded with just works model. from QCOM Change-Id: Ia3c1635c446f39b1dbd4cdd0122c2f70cbbc8dd7
tif_dm.c
tif_storage.c
|
744ad4713df103183916de11796b0e1e27b5a5d8 |
29-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Fix issue of HDP select thread not exiting during BT OFF Change-Id: I52a0a3caff327a7a51e293c431ddbc99db690180
tif_hl.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
tif_rc.c
|
79eb1a643a2e627e5fb2c9dae1cb6a56a15ff0cf |
21-Apr-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
HID: Use dynamic memory while sending data This patch uses dynamic memory allocation while sending HID output data to remote device depending on size of data to be sent. Without this patch fixed size static buffer of 200 bytes was being used for sending data to remote device, which was resulting in crash in case data size to be sent to remote device was greater than 200 bytes. Change-Id: I5ed12422355e88d7ef0391668800d7619ca3b685
tif_hh.c
|
fbaeb4a7b64a89c08a98b53766e250eb7bad8830 |
25-Oct-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
HID: Parse paired hid devices from bluez. This patch adds support for parsing SDP records of paired HID devices from bluez device storage path and store the parsed hid sdp data into bluedroid storage path. Without this patch, it was not possible to have paired HID devices during upgrade from BlueZ to Bluedroid Stack. Change-Id: I7db4a801f3cf9ca46fc0eabfd929e8d7c16b5edb
tif_config_util.cpp
|
87b7cce18f64b1b5f1cdff81d883a5c8720ead77 |
28-Nov-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Try to retrieve CoD from NVRAM if 0 This patch tries to retreive CoD from NVRAM if CoD is 0. This is because in scenarios when airplane mode on/off, inquiry is not performed again on devices shown in Available devices List of UI, so CoD is 0 during SSP information as database of stack is not properly updated since inquiry is not performed again. Without this patch it was observed because of wrong CoD info device icon for HID mouse was changed to Joystick and device is not shown in Paired List. Also some extra debug logs are added in code for better debugging. Change-Id: I14858ccee04728cb4b9cd60d397b79fa6494b842
tif_dm.c
|
8d2128d5740c8a7282e2336cd9f5901e98d3eb63 |
13-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
HID: Remove device from nvram on auth failure This patch removed hid pointing device from nvram on authentication failure due to pairing timeout or when wrong passkey is entered. Without this patch it was observed that hid pointing device was always shown in paired list when DUT was restarted after authentication failure. CL from qcom(Hemant Gupta) Change-Id: I69c43d2ed982d5d5abfd5707db90ef4b5c65b34f
tif_dm.c
|
45c71b0647cba0f199a8dfd1321c1b59a916cfe5 |
21-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
HID: Use dynamic memory while sending report This patch uses dynamic memory allocation while sending HID output data to remote device depending on size of data to be sent. Without this patch fixed size static buffer of 200 bytes was being used for sending data to remote device, which was resulting in crash in case data size to be sent to remote device was greater than 200 bytes. CL from qcom(Hemant Gupta) Change-Id: Icc8cd4a4ecfd4bc30cbf848a7c865fcf9308ddf8
tif_hh.c
|
4c5f9ef5fa88891f073b38d5e15f2705ed5c235e |
21-Apr-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
HID: Update SSR parameters during copy. This patch correctly stores SSR parameters (max latency and min timeout) retrieved from remote device SDP record in NVRAM. Change-Id: I87d8b6181981090df21ab746deac7053a1d0e938
tif_hh.c
|
33a3ae6aa2334c5df1cd0aadea3597b46a7a59ee |
21-Apr-2014 |
Matthew Xie <mattx@google.com> |
am 72f5ce63: am 4b416130: Merge "Bluetooth: Adding Sniff feature for PAN Profile" * commit '72f5ce63c2dbf31c7cfbb903c687ea71ad29b3ea': Bluetooth: Adding Sniff feature for PAN Profile
|
72f5ce63c2dbf31c7cfbb903c687ea71ad29b3ea |
21-Apr-2014 |
Matthew Xie <mattx@google.com> |
am 4b416130: Merge "Bluetooth: Adding Sniff feature for PAN Profile" * commit '4b41613019829b40e8ca75a87219a415c51ae3a1': Bluetooth: Adding Sniff feature for PAN Profile
|
496765df63a103d46aff536f9e1c094bf58d52b7 |
21-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "Fix GKI exception of calling free on an already freed buffer" into klp-wireless-dev
|
c0f7987d626a70b1a23a28348ece8be69ce61a16 |
25-Feb-2014 |
Zhihai Xu <zhihaixu@google.com> |
Fix GKI exception of calling free on an already freed buffer Various parts of btif_hh.c were creating GKI buffers and keeping references to them and freeing them in odd and unnecessary ways. The buffer is freed by lower levels of the stack once the buffer has been sent to the chip at the l2c layer and shouldn't be freed by btif_hh itself since it's possible to double free, and there could also be race conditions with other threads already processing the buffer while the reference is freed if the API calls are invoked again before the previous invocation was completely processed. Also added a helper routine to simplify buffer creation and initialization. Change-Id: Ia6039983502e2670b2325d90310244edf843b692 Signed-off-by: Mike J. Chen <mjchen@google.com>
tif_hh.c
|
17888ed7fa01bf266e3847b308f4091fd93f719c |
21-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db" into klp-wireless-dev
|
6efaf223753108aa84f55332898340db0c9d5ebf |
27-Jan-2014 |
Zhihai Xu <zhihaixu@google.com> |
bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db Store the ssr_max_latency and ssr_min_tout parameters in the bonding database. Previously these parameters were not stored for HID devices. This caused an inconsistency in sniff behavior between when the HID device was paired and following a reboot of the host. When the HID device is paired the SSR parameters are retrieved from the HID device and are stored in the HID Host's device list. If the host is rebooted then the HID Host's device list is constructed from the bonding database. If the SSR max latency is non-zero then the SSR parameters are sent to the firmware and SSR is used. In the event that the SSR max latency is 0, as it is if the parameters are not found, then SSR is disabled. Bug: 12764547 Change-Id: I63637575fdfcf4cb4ca0ce8dc2e4ccda9cccaf66 Signed-off-by: Adam Hampson <ahampson@google.com>
tif_hh.c
tif_storage.c
|
f4b8f8aa313d3b7d88b683bfe0e5f9eb0a29b3b3 |
07-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Add flow control for PAN. This change reads from the TAP fd only when btpan_cb.flow == 1. The value of this flag changes based on L2CAP congestion events. http://b/13246629 Change-Id: Ic28bf65737dbd74c41b68198fceee58e3bff08d4 Conflicts: btif/src/btif_pan.c
tif_pan.c
|
2d75441cc17236564a431c6a5fc4c9e356fb7294 |
21-Nov-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add controller based advertising filter API (2/2) Change-Id: I444654bf19a048d5fcef33f79edbf1cdda3d3b62
tif_core.c
tif_gatt_client.c
tif_gatt_util.c
|
fd2e0f21623a8e38460c140281500ea1f658f422 |
17-Apr-2014 |
Matthew Xie <mattx@google.com> |
Merge "Bluetooth: GAP: Send bond none in case of temp pairing" into klp-wireless-dev
|
6d4a9e9cbfc0ea3b91b9dd1933d2646065e665cd |
16-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "LE: Add API to configure MTU for a given connection (2/4) This patch from broadcom(andre) bug:13571470 Change-Id: I932905590ee9c40cb67e7d09715c0f8e59d2f662" into klp-wireless-dev
|
9291a71c28b2eedff2c1ad760ebe3b3c1f5a6a29 |
25-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
LE: Add API to configure MTU for a given connection (2/4) This patch from broadcom(andre) bug:13571470 Change-Id: I932905590ee9c40cb67e7d09715c0f8e59d2f662
tif_gatt_client.c
|
3aafefbb0fe4c1577635ddb455c764c8da91860a |
16-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "remove all advertised services in SDP btif_av_init is called twice. Don't need call it in enable. disable EDR ATT SDP record" into klp-wireless-dev
|
d92e3cf7b26fe2dd64e7c27b43428d3cab85e371 |
05-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
remove all advertised services in SDP btif_av_init is called twice. Don't need call it in enable. disable EDR ATT SDP record bug:13558005 Change-Id: Id834697eae150018f9a0382d9c1e6c972e885739
tif_core.c
|
d0f17781e92806065b04aa95a9b9ff9cbe5b2cad |
16-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "Workaround IPHONE problem" into klp-wireless-dev
|
facc510f94c02440e9004f31110463cd1d367221 |
18-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
Workaround IPHONE problem When we send LL_ENC_REQ to iphone early, iphone didn't send LL_ENC_RESPONSE back to us, later the iphone will disconnect from us. The workaround is to send LL_ENC_REQ after receive first ATT read request from iphone, Iphone will be ready at that time by experiment. bug:13417692 Change-Id: Ic42dda36b927df260113771152cff67032b22e5f
tif_gatt_util.c
|
51356020fb8fec90a01eeaa23faaf9d3cb0b6322 |
16-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "treat BTA_BUSY as success to avoid unpair the BLE device" into klp-wireless-dev
|
b9238669b5ad298980d60540e8019c4b90a866b1 |
13-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
treat BTA_BUSY as success to avoid unpair the BLE device when switch from peripheral mode, both server and client will call btif_gatt_check_encrypted_link, the first call will start the encryption. the second call will get callback with BTA_BUSY status, before encryption complete, which cause unpair with the remote device. we shouldnot treat BTA_BUSY as error. bug:13417692 Change-Id: I065432dde2553e8ccee3a14a7b321b85bca8d3ba
tif_gatt_util.c
|
43d8f252240611ad2b67f9587f91058edd9955a0 |
16-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "support peripheral mode feature to connect iphone to android device." into klp-wireless-dev
|
5f72121ddc2f0249e896e19b186a05888bce2331 |
10-Feb-2014 |
Zhihai Xu <zhihaixu@google.com> |
support peripheral mode feature to connect iphone to android device. enable BLE_PERIPHERAL_MODE_SUPPORT flag and fix the bug the discoverability flag is not set in advertisement packet, which cause the central device(iphone) can not find android device during scan. use displayOnly IO cap for dory, so dory can display the pin, and the iphone(central device) will input the pin. bug:12797572 Change-Id: Ie15ea9e340e3692df846399b9a85aa6d2a97eba7
tif_gatt_client.c
|
b820aec7a022231fa30a3493af861db9d9aa625d |
24-Dec-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: GAP: Send bond none in case of temp pairing Send BOND_NONE in case of temporary device pairing on receiving the authentication complete, so that UI doesn't get stucked in pairing for that device. Change-Id: Ided412ef89d928f958a0052362be145232411c0a
tif_dm.c
|
d2ccbbb73c7851d2fa28dc212d2fffc0ad4e5d50 |
13-Apr-2014 |
Sharvil Nanavati <sharvil@google.com> |
Remove executable bit on source files. Change-Id: Id456478aea626f57fed3479346e8fb4dbd0fafa6
luetooth.c
tif_av.c
tif_media_task.c
tif_rc.c
tif_util.c
|
36f43cc4b0ce38007c29d573f251ec594d95b180 |
29-Aug-2013 |
Nitin Shivpure <nshivpur@codeaurora.org> |
Bluetooth: Adding Sniff feature for PAN Profile Sniff feature for PAN profile was not implemented in power manager module of the stack, which was causing higher power consumption after connecting PAN profile, Even though PAN ACL link is idle & there is no data communication between DUT & remote device. Adding sniff feature for PANU role & NAP role to reduce power consumption. Change-Id: Idf568f53a317abd536edf34fbdf1733fdf53b7d0
tif_pan.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
tif_rc.c
|
be9ef59a58c2cf3f8c3cd5a834841cd74965a599 |
08-Apr-2014 |
Matthew Xie <mattx@google.com> |
am 4ec26844: am c7d4ce67: Merge "Bluetooth:GAP: Add NULL check before accessing accept socket" * commit '4ec26844f88e37dda00f1319ce6ab44fa87539f2': Bluetooth:GAP: Add NULL check before accessing accept socket
|
4ec26844f88e37dda00f1319ce6ab44fa87539f2 |
08-Apr-2014 |
Matthew Xie <mattx@google.com> |
am c7d4ce67: Merge "Bluetooth:GAP: Add NULL check before accessing accept socket" * commit 'c7d4ce671ccc74ee05813bef10639fd34e1bf81f': Bluetooth:GAP: Add NULL check before accessing accept socket
|
07410e996c151f12852ab9216deb3cac6293ff17 |
07-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 2f2d9f41: am a0cf8d6f: remove all advertised services in SDP btif_av_init is called twice. Don\'t need call it in enable. disable EDR ATT SDP record * commit '2f2d9f412f7dc999eee87161cb2c30c786523ff2': remove all advertised services in SDP btif_av_init is called twice. Don't need call it in enable. disable EDR ATT SDP record
|
2f2d9f412f7dc999eee87161cb2c30c786523ff2 |
07-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
am a0cf8d6f: remove all advertised services in SDP btif_av_init is called twice. Don\'t need call it in enable. disable EDR ATT SDP record * commit 'a0cf8d6f47fd6709085b9ad2c8626986f7ae7f21': remove all advertised services in SDP btif_av_init is called twice. Don't need call it in enable. disable EDR ATT SDP record
|
a0cf8d6f47fd6709085b9ad2c8626986f7ae7f21 |
05-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
remove all advertised services in SDP btif_av_init is called twice. Don't need call it in enable. disable EDR ATT SDP record bug:13558005 Change-Id: Id834697eae150018f9a0382d9c1e6c972e885739
tif_core.c
|
6c15f743cac323570d7adcb9a2344824221a569f |
02-Apr-2014 |
Mike J. Chen <mjchen@google.com> |
am 4927e67f: am 3576c564: Fix compiler/linker errors when BTA_PAN_INCLUDED is FALSE * commit '4927e67fb8cd3cd09b2607241c3da875f85ed852': Fix compiler/linker errors when BTA_PAN_INCLUDED is FALSE
|
4927e67fb8cd3cd09b2607241c3da875f85ed852 |
02-Apr-2014 |
Mike J. Chen <mjchen@google.com> |
am 3576c564: Fix compiler/linker errors when BTA_PAN_INCLUDED is FALSE * commit '3576c564b33c20b5e2e90fdd3bca7ce24392ca50': Fix compiler/linker errors when BTA_PAN_INCLUDED is FALSE
|
3576c564b33c20b5e2e90fdd3bca7ce24392ca50 |
01-Apr-2014 |
Mike J. Chen <mjchen@google.com> |
Fix compiler/linker errors when BTA_PAN_INCLUDED is FALSE Change-Id: I14acefd66291adc2119daf97bd364b2eecf18d51 Signed-off-by: Mike J. Chen <mjchen@google.com>
tif_pan.c
|
e96ce0e945e210b22bbf6a3869809852c7e1d35e |
06-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
DO NOT MERGE: LE: Add status callback function for LE broadcasts Cherry pick from master Change-Id: If4342050ce1141a9c2111286e7b3cccdc012a91e
tif_gatt_client.c
|
7d3d17fb9e62720b8060b333662e7fa63f231cd3 |
01-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
am a27b6503: am 221b822c: Merge "Workaround IPHONE problem" into klp-modular-dev * commit 'a27b650322c6ad1d5cea2d0b4fcb7815e3176d1e': Workaround IPHONE problem
|
a27b650322c6ad1d5cea2d0b4fcb7815e3176d1e |
01-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 221b822c: Merge "Workaround IPHONE problem" into klp-modular-dev * commit '221b822ce1c42f4a51abc384cf09ca09b6180a9c': Workaround IPHONE problem
|
221b822ce1c42f4a51abc384cf09ca09b6180a9c |
01-Apr-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "Workaround IPHONE problem" into klp-modular-dev
|
5702d5c6197404823f5e594764e2c67cf2416da1 |
18-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
Workaround IPHONE problem When we send LL_ENC_REQ to iphone early, iphone didn't send LL_ENC_RESPONSE back to us, later the iphone will disconnect from us. The workaround is to send LL_ENC_REQ after receive first ATT read request from iphone, Iphone will be ready at that time by experiment. bug:13417692 Change-Id: Ic42dda36b927df260113771152cff67032b22e5f
tif_gatt_util.c
|
3860c0c6ad3c09e094d2254ba44b410f8c3f7203 |
31-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
am d86082bf: am 9b971dc5: Merge "treat BTA_BUSY as success to avoid unpair the BLE device" into klp-modular-dev * commit 'd86082bfabffa25f2af77cc69c590d6e0b14260c': treat BTA_BUSY as success to avoid unpair the BLE device
|
d86082bfabffa25f2af77cc69c590d6e0b14260c |
31-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 9b971dc5: Merge "treat BTA_BUSY as success to avoid unpair the BLE device" into klp-modular-dev * commit '9b971dc52f5933c04e4f49ad99c9949df961afc5': treat BTA_BUSY as success to avoid unpair the BLE device
|
9b971dc52f5933c04e4f49ad99c9949df961afc5 |
31-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "treat BTA_BUSY as success to avoid unpair the BLE device" into klp-modular-dev
|
5a607b4fe2109f9ba602e932fde16f527b7a2139 |
31-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 20222380: am 2011d136: Merge "LE: Add API to configure MTU for a given connection (2/4)" into klp-modular-dev * commit '20222380588aa9a5e9b5e83b653e3c2a744da6aa': LE: Add API to configure MTU for a given connection (2/4)
|
20222380588aa9a5e9b5e83b653e3c2a744da6aa |
31-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 2011d136: Merge "LE: Add API to configure MTU for a given connection (2/4)" into klp-modular-dev * commit '2011d136791ec93c0670edc00e64122415c926a0': LE: Add API to configure MTU for a given connection (2/4)
|
9426d530e9bbc5d3ffae55515388d49185c61325 |
25-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add API to configure MTU for a given connection (2/4) bug:13571470 Change-Id: I932905590ee9c40cb67e7d09715c0f8e59d2f662
tif_gatt_client.c
|
96f50348c6b38ee4ac660fabf4b5676515c542e0 |
20-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
am a4611ac0: DO NOT MERGE: cherrypick from master to fix b/13289050 * commit 'a4611ac05f07360785adcff8640da01a3894e4c5': DO NOT MERGE: cherrypick from master to fix b/13289050
|
64ed24148d570f5a1c8ebeb2f0336b24ecc95b9c |
20-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
am 67020954: am a4611ac0: DO NOT MERGE: cherrypick from master to fix b/13289050 * commit '670209545cbf585165029d8866972ade111785c5': DO NOT MERGE: cherrypick from master to fix b/13289050
|
670209545cbf585165029d8866972ade111785c5 |
20-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
am a4611ac0: DO NOT MERGE: cherrypick from master to fix b/13289050 * commit 'a4611ac05f07360785adcff8640da01a3894e4c5': DO NOT MERGE: cherrypick from master to fix b/13289050
|
a4611ac05f07360785adcff8640da01a3894e4c5 |
06-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
DO NOT MERGE: cherrypick from master to fix b/13289050 LE: Add status callback function for LE broadcasts Change-Id: If4342050ce1141a9c2111286e7b3cccdc012a91e
tif_gatt_client.c
|
487f9e43faeab586967f035e115af8bd63034ace |
06-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add status callback function for LE broadcasts Change-Id: If4342050ce1141a9c2111286e7b3cccdc012a91e
tif_gatt_client.c
|
fc3fba5db90f29b072ebecc231245c8f134b594b |
13-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
treat BTA_BUSY as success to avoid unpair the BLE device when switch from peripheral mode, both server and client will call btif_gatt_check_encrypted_link, the first call will start the encryption. the second call will get callback with BTA_BUSY status, before encryption complete, which cause unpair with the remote device. we shouldnot treat BTA_BUSY as error. bug:13417692 Change-Id: I065432dde2553e8ccee3a14a7b321b85bca8d3ba
tif_gatt_util.c
|
ea5a91bd3223b62712106e4b707301919bc6d32b |
14-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 07ea194a: Merge "DO NOT MERGE use bluetooth HID remote device name as input device name." into klp-dev * commit '07ea194ac2518e98961632c4d1909f0af0809ea9': DO NOT MERGE use bluetooth HID remote device name as input device name.
|
07ea194ac2518e98961632c4d1909f0af0809ea9 |
13-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "DO NOT MERGE use bluetooth HID remote device name as input device name." into klp-dev
|
0d56a323a8ec323d4cf1d35edf4811781b7c781f |
11-Mar-2014 |
Matthew Xie <mattx@google.com> |
am 1d454d1b: am f677f810: Merge "DO NOT MERGE Bluetooth: Cleanup bt_config.xml during BLE Scan" into klp-dev * commit '1d454d1b88846b75bdd70508e51bd2a33211b0f8': DO NOT MERGE Bluetooth: Cleanup bt_config.xml during BLE Scan
|
d9ba1402d356b77c274bdb6e00697512935d9b61 |
11-Mar-2014 |
Narayan Kamath <narayan@google.com> |
am 277ba466: Merge "Various fixes for LP64" * commit '277ba466eb30755d2b158ebed650fd50b5701bee': Various fixes for LP64
|
ad73b9c59961a622a5ec09b22a23a93f4c7bda1b |
06-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
DO NOT MERGE use bluetooth HID remote device name as input device name. bug:12003067 Change-Id: I74e4921047a27ee79fa1e3cd58056fde2958e60f
tif_hh.c
|
1d454d1b88846b75bdd70508e51bd2a33211b0f8 |
11-Mar-2014 |
Matthew Xie <mattx@google.com> |
am f677f810: Merge "DO NOT MERGE Bluetooth: Cleanup bt_config.xml during BLE Scan" into klp-dev * commit 'f677f81068640857f791276c472e34b08d08f3e6': DO NOT MERGE Bluetooth: Cleanup bt_config.xml during BLE Scan
|
14225c9b89c9c45efa4fa069edfc749e6d06bfcb |
11-Mar-2014 |
Matthew Xie <mattx@google.com> |
am 6bc62a36: Merge "Bluetooth: GAP: Update bonded device info immediately on NVRAM" * commit '6bc62a368da0a434a4e01f7bcb3273bd52a07568': Bluetooth: GAP: Update bonded device info immediately on NVRAM
|
5ef95e13f6e494ed586aa740aac41b6e95b836cc |
10-Mar-2014 |
Matthew Xie <mattx@google.com> |
am f677f810: Merge "DO NOT MERGE Bluetooth: Cleanup bt_config.xml during BLE Scan" into klp-dev * commit 'f677f81068640857f791276c472e34b08d08f3e6': DO NOT MERGE Bluetooth: Cleanup bt_config.xml during BLE Scan
|
f677f81068640857f791276c472e34b08d08f3e6 |
10-Mar-2014 |
Matthew Xie <mattx@google.com> |
Merge "DO NOT MERGE Bluetooth: Cleanup bt_config.xml during BLE Scan" into klp-dev
|
a59793fda4f5a3b83a7c989db30f6cf61828dc2f |
10-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 27420a03: Merge "DO NOT MERGE BLE HID device connection failure due to security error." into klp-dev * commit '27420a0327c04ce9407d2fe9138dde7f6dfe94e0': DO NOT MERGE BLE HID device connection failure due to security error.
|
d3e78c06b112fe50959b4e30a5d4f90f8f83e4a3 |
10-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
am ea8acc97: Merge "DO NOT MERGE fix a potential native crash during bluetooth sutdown" into klp-dev * commit 'ea8acc971f7c01427fd239e54344b43ac1a31e1c': DO NOT MERGE fix a potential native crash during bluetooth sutdown
|
9fc2745f361388e8dee879518ee292369e2124f8 |
10-Mar-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 1e0849e9: Merge "DO NOT MERGE the HID device state is out of sync after upair." into klp-dev * commit '1e0849e99bdd716b7e172269cdad1d78b60a7ded': DO NOT MERGE the HID device state is out of sync after upair.
|
b9912730d082c7bca7d94bb9ddac4447cfad362f |
13-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
DO NOT MERGE BLE HID device connection failure due to security error. When HID BLE device start encryption, if some other GATT application already start encryption(but not finished yet) by calling gatt_security_check_start. The HID BLE device will be failed to start encryption, which will cause it to disconnect the BLE HID connection. The solution is to check whether we already started the encryption , If the encryption is already started, wait until the encryption finished, then continue to start security check for BLE HID device. add encrytion complete event to notify all GATT client encryption done. filter the event just for BTA HH LE GATT client. bug:11636246 Change-Id: If58e57c623cc8cfa05208587b010bec68c71306c
tif_gatt_test.c
|
5a79e080ef667e7c623ef46da6086915087c7488 |
26-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
DO NOT MERGE fix a potential native crash during bluetooth sutdown When bluetooth is initialized which call gki_buffer_init, the buffer pool is allocated by GKI_os_malloc which is to call libc malloc function. When bluetooth is cleanup which call GKI_shutdown, the buffer pool will be freed by GKI_os_free which is to call libc free function. So if we access the buffer, after the whole buffer pool is freed, we will get this native crash. if we call cleanup during bluetooth disabling: the state is still BTIF_CORE_STATE_DISABLING, then GKI_shutdown will call before bte_main_disable ( bt_hc_if->cleanup();), which is before userial thread exit. Then we may trigger this native crash. bug:11793775 Change-Id: Ic8ced12848d25f918a28f4d5ba29b803d6ac5bd7
luetooth.c
tif_core.c
|
35f6b7f3f8b483065e9d97c18542286818e02544 |
16-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
DO NOT MERGE the HID device state is out of sync after upair. the HID device state is out of sync between java layer and bluedroid stack after upair. This will cause the HID device can't be connected after repair. YOu can find the following error message E/HidService( 1452): Hid Device not disconnected: 00:15:9E:20:29:41 bug:11718702 Change-Id: I271bb77a2cc205c5a0ef396db86b87902d29966b
tif_hh.c
|
89d4f0a9fcfe66618fb771a5f85bf4e50693ee23 |
08-Mar-2014 |
Andre Eisenbach <andre@broadcom.com> |
am b74fe9e2: DO NOT MERGE LE: Add service UUIDs and data to advertising data * commit 'b74fe9e2c9fc0939f5c18282c985622f20b78d2a': DO NOT MERGE LE: Add service UUIDs and data to advertising data
|
0798eb9cf9259bcfa3b8583d1de2c73456649cf3 |
07-Mar-2014 |
Mike J. Chen <mjchen@google.com> |
am bac0e60f: am 303a1272: am f6918978: Add HID handshake_callback * commit 'bac0e60f37d577e5b1a47ff52c8f2a96142ee4e7': Add HID handshake_callback
|
303a12727c96f6e39c31b0ef6a6017b5ef7972c0 |
07-Mar-2014 |
Mike J. Chen <mjchen@google.com> |
am f6918978: Add HID handshake_callback * commit 'f691897800e086b6caf238ee78d560526e69c67d': Add HID handshake_callback
|
a7bd2a1084569fb7170ebc62b1a2030a6865b797 |
24-Jan-2014 |
Srinu Jella <sjella@codeaurora.org> |
Bluetooth:GAP: Add NULL check before accessing accept socket Add NULL check before accessing accept_rs variable to avoid null pointer exception while referring to invalid memory. Change-Id: Ibc38d1c2fb19eb171cf136c47248ad8828676ac1
tif_sock_rfc.c
|
aefcb184639ff24bf294dfa4f91bd22202d1f93e |
20-Nov-2013 |
Sunny Kapdi <sunnyk@codeaurora.org> |
DO NOT MERGE Bluetooth: Cleanup bt_config.xml during BLE Scan BLE Scan needs to clean up the bt_config.xml periodically so that new entries could be added to bt_config.xml. Also, there is no need to add BLE Random bd_addr to the bt_config.xml Change-Id: I00ba2e50dd39a021099052cb569786f6cb2cc8b9 b/12912008 (cherry picked from commit 377cb1407ee6ee1ff91b15bfa7052abed1023d18) Change-Id: I3fa0286c96782822a8fdac14b05bbb6f98636e50
tif_gatt_client.c
tif_storage.c
|
b74fe9e2c9fc0939f5c18282c985622f20b78d2a |
08-Nov-2013 |
Andre Eisenbach <andre@broadcom.com> |
DO NOT MERGE LE: Add service UUIDs and data to advertising data Add support for UUIDs and custom service data in the advertising and scan response records. Cherry picking ble advertising changes from master to KLP MR2. b/13137996 Change-Id: I6470427ad194871488cc90f3ab384b9ecf326b15
tif_gatt_client.c
|
bbd585e19920a0eaa209057a5c4f97ead9063fee |
05-Mar-2014 |
Mike J. Chen <mjchen@google.com> |
am 8dfc3e29: am 84516150: am be6d58f3: Fix GKI exception of calling free on an already freed buffer * commit '8dfc3e2992456539ee6c740199f543cdb0d5a9d3': Fix GKI exception of calling free on an already freed buffer
|
845161504098dcfdf8874f6ec592642f40b57547 |
05-Mar-2014 |
Mike J. Chen <mjchen@google.com> |
am be6d58f3: Fix GKI exception of calling free on an already freed buffer * commit 'be6d58f35e66b9e57cf4978be68840cbc8ac2fc9': Fix GKI exception of calling free on an already freed buffer
|
f691897800e086b6caf238ee78d560526e69c67d |
25-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Add HID handshake_callback It is called when the equivalent pkt is received from the HID client as a normal response to set_report() and set_protocol_mode(), and for errors for get_report() and get_protocol_mode(). Change-Id: I26ec37348e597f294f83907bbd256c88db5ac2ef Signed-off-by: Mike J. Chen <mjchen@google.com>
tif_hh.c
|
be6d58f35e66b9e57cf4978be68840cbc8ac2fc9 |
25-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Fix GKI exception of calling free on an already freed buffer Various parts of btif_hh.c were creating GKI buffers and keeping references to them and freeing them in odd and unnecessary ways. The buffer is freed by lower levels of the stack once the buffer has been sent to the chip at the l2c layer and shouldn't be freed by btif_hh itself since it's possible to double free, and there could also be race conditions with other threads already processing the buffer while the reference is freed if the API calls are invoked again before the previous invocation was completely processed. Also added a helper routine to simplify buffer creation and initialization. Change-Id: Ia6039983502e2670b2325d90310244edf843b692 Signed-off-by: Mike J. Chen <mjchen@google.com>
tif_hh.c
|
2eda01018250d9253bc54da9f6896d58dba1f601 |
27-Feb-2014 |
Narayan Kamath <narayan@google.com> |
am de34aea5: am 5303f9d3: resolved conflicts for merge of 277ba466 to klp-modular-dev-plus-aosp * commit 'de34aea544cb4222f24e4157b96962b09445e2c5': Various fixes for LP64
|
5303f9d369946f43167b5e2423799d30c4455df1 |
27-Feb-2014 |
Narayan Kamath <narayan@google.com> |
resolved conflicts for merge of 277ba466 to klp-modular-dev-plus-aosp Change-Id: Idc42f72a94c205cfe94feb220651a483cf418e84
|
22c6e505dc65ab3d624e4ccd7c48c95fe2128703 |
12-Feb-2014 |
Kévin PETIT <kevin.petit@arm.com> |
Various fixes for LP64 Changes include - Cast numbers to their proper length before casting to a pointer. - Use intptr_t when pointers are stored as integers. - Eliminate 'implicit declaration' warnings Signed-off-by: Matthew Leach <matthew.leach@arm.com> Signed-off-by: Ashok Bhat <ashok.bhat@arm.com> Signed-off-by: Marcus Oakland <marcus.oakland@arm.com> Signed-off-by: Kévin PETIT <kevin.petit@arm.com> Change-Id: I5664a087c5fbc322baa9178552404dbe9a992359
tif_sock_rfc.c
tif_sock_thread.c
|
0977fc84e0314b7b71668885a433f5ad4b6ec49c |
26-Feb-2014 |
Matthew Xie <mattx@google.com> |
am e736740d: am 5834e63b: am 759280ee: Merge "bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db" into klp-modular-dev * commit 'e736740ded718c76c0007baa97b7f55e69ceb1b1': bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db
|
5834e63bd410d708d8764f69ede256ca0ed98635 |
26-Feb-2014 |
Matthew Xie <mattx@google.com> |
am 759280ee: Merge "bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db" into klp-modular-dev * commit '759280ee1f92945ed7c1c13f5ff8a037fa3bf3e4': bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db
|
759280ee1f92945ed7c1c13f5ff8a037fa3bf3e4 |
26-Feb-2014 |
Matthew Xie <mattx@google.com> |
Merge "bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db" into klp-modular-dev
|
afd4a5740e2193e7ce8dbedb8787b19f7c0016cd |
25-Feb-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 2ac65164: am 75c7597c: am 4fbbe711: Merge "support peripheral mode feature to connect iphone to android device." into klp-modular-dev * commit '2ac6516450336e2ec5ccbbefa0221276ea291695': support peripheral mode feature to connect iphone to android device.
|
75c7597c94a7d8ee5c79b75ccaede02f53dd7c9f |
25-Feb-2014 |
Zhihai Xu <zhihaixu@google.com> |
am 4fbbe711: Merge "support peripheral mode feature to connect iphone to android device." into klp-modular-dev * commit '4fbbe7115dd7c2f8b0df386fad4085f411beeef3': support peripheral mode feature to connect iphone to android device.
|
4fbbe7115dd7c2f8b0df386fad4085f411beeef3 |
25-Feb-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "support peripheral mode feature to connect iphone to android device." into klp-modular-dev
|
602162a13c6ed8abae53aee6deeda48b79f30911 |
10-Feb-2014 |
Zhihai Xu <zhihaixu@google.com> |
support peripheral mode feature to connect iphone to android device. enable BLE_PERIPHERAL_MODE_SUPPORT flag and fix the bug the discoverability flag is not set in advertisement packet, which cause the central device(iphone) can not find android device during scan. use displayOnly IO cap for dory, so dory can display the pin, and the iphone(central device) will input the pin. bug:12797572 Change-Id: Ie15ea9e340e3692df846399b9a85aa6d2a97eba7
tif_gatt_client.c
|
7e6b379268f973752863e333b55e6068373e1664 |
24-Feb-2014 |
Matthew Xie <mattx@google.com> |
am 9d368b68: am 1292dd82: am 6bc62a36: Merge "Bluetooth: GAP: Update bonded device info immediately on NVRAM" * commit '9d368b68841dee6e6f581a3890433dcdc022fbb8': Bluetooth: GAP: Update bonded device info immediately on NVRAM
|
1292dd82812d76c54568796fbdafd1fdadc816eb |
24-Feb-2014 |
Matthew Xie <mattx@google.com> |
am 6bc62a36: Merge "Bluetooth: GAP: Update bonded device info immediately on NVRAM" * commit '6bc62a368da0a434a4e01f7bcb3273bd52a07568': Bluetooth: GAP: Update bonded device info immediately on NVRAM
|
ffc69cc3173ffc190fd77686ae12cf3fa95a5b07 |
22-Feb-2014 |
Matthew Xie <mattx@google.com> |
Merge "Bluetooth: Cleanup bt_config.xml during BLE Scan"
|
377cb1407ee6ee1ff91b15bfa7052abed1023d18 |
20-Nov-2013 |
Sunny Kapdi <sunnyk@codeaurora.org> |
Bluetooth: Cleanup bt_config.xml during BLE Scan BLE Scan needs to clean up the bt_config.xml periodically so that new entries could be added to bt_config.xml. Also, there is no need to add BLE Random bd_addr to the bt_config.xml Change-Id: I00ba2e50dd39a021099052cb569786f6cb2cc8b9 b/12912008
tif_gatt_client.c
tif_storage.c
|
5e08d1ec92555e2cb3d80f1a9a3c746c76ed3e5d |
21-Nov-2013 |
Srinu Jella <sjella@codeaurora.org> |
Bluetooth: GAP: Update bonded device info immediately on NVRAM As the new bt-if config updation have delay in writing items to the NVRAM, some times there is a chance of not updating incase of battery removal happens before the actual write onto NVRAM. As the bonded device info is important data to store, it will update bonded info immediately onto NVRAM. Change-Id: I9699c8225a77d9272420334b4c76b3c1df87e459
tif_storage.c
|
8351ea3d6dcc6c1663d07969c16b2fd9d059ea5b |
15-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
am 0c880603: am 6a342588: am 136e4b1c: Merge "Don\'t send a dummy 0 HID event when connection is closed" into klp-modular-dev * commit '0c880603dba9f9f09523509f19c6808ba8f52e12': Don't send a dummy 0 HID event when connection is closed
|
bf6cab9332f81f7bcd4b3040c2c1edd3062ecb40 |
14-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Don't send a dummy 0 HID event when connection is closed This was put there by Broadcom to try to handle held keys on disconnect, but the best place to do that is in InputManager. There's no guarantee that a report_id 1 is keyboard, and in particular it causes game controllers to get a false joystick move event to 0,0. Bug 12785130 Change-Id: I85fbafa44d927082def3848132344550e8b94bb0 Signed-off-by: Mike J. Chen <mjchen@google.com>
tif_hh.c
|
3a7ff0d45c2086bc990c2fbbdb862e4e962916b7 |
12-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
am e80e4df1: am b45e54f0: Merge "Fix warnings when BLE_INCLUDED is FALSE" into klp-modular-dev * commit 'e80e4df1f9b9b60be37ef8ad854d7b46b9dbfb83': Fix warnings when BLE_INCLUDED is FALSE
|
bf9a8aa26988aedbc161d75f2688641ce59dc001 |
11-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Fix warnings when BLE_INCLUDED is FALSE Change-Id: I27c8ac6d5410159ed6bbef6aca5bf3b9692b0467 Signed-off-by: Mike J. Chen <mjchen@google.com>
luetooth.c
|
85c1751ac78a4b9ae9f2250130000755081905fb |
11-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
am 3d4f5c71: am b83a8234: Merge changes Ifc373f95,I95eb887a,I1e6be2ab,Ia6ea939a,I147d0138, ... into klp-modular-dev * commit '3d4f5c715204c3c5eeb21e351aff73072000f61e': (24 commits) Make all warnings fatal compilation errors Major warnings cleanup Add macro UNUSED() to bt_utils.h Fix unused parameter warning in static function Add "static" to a static function Fix a number of unused parameter warnings in static functions Fix bug with wrong parameter passed to logu Default send_ind_evt should be FALSE Fix warning "implicit declaration of function 'GAP_BleReadPeerPrefConnParams'" Fix unused parameter warnings in static functions by changing prototype Fix some unused parameter warnings in static functions Fix warnings about implicit declaration of bdcmp and bdcpy Fix warning "comparison is always true due to limited range of data type" Fix warning "suggest braces around empty body in an 'if' statement" Fix warning "comparison is always true due to limited range of data type" Add a function prototype for btm_ble_test_command_complete Change argument to return ptr rather than assign to unused local Fix warning "comparison is always true due to limited range of data type" Fix warnings about implicit declarations Fix warning "implicit declaration of function 'bdcmp'" ...
|
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>
luetooth.c
tif_av.c
tif_config.c
tif_core.c
tif_dm.c
tif_gatt_test.c
tif_hf.c
tif_hh.c
tif_hl.c
tif_media_task.c
tif_pan.c
tif_rc.c
tif_sock_rfc.c
|
d8edb46866ca4f2d9ee61330db78d25352cfbf27 |
28-Jan-2014 |
Mike J. Chen <mjchen@google.com> |
am e372d9b5: Merge "Fix HID get_report callback support" into klp-modular-dev * commit 'e372d9b58a288348782d01f534cf6dc81a7934c7': Fix HID get_report callback support
|
b46d9b899f5e28929c8530cb99d023c93e5d5cb8 |
24-Jan-2014 |
Mike J. Chen <mjchen@google.com> |
Fix HID get_report callback support There were multiple bugs in the code for get_report event callback handling: 1) the p_dev lookup was using the wrong argument so was coming up with NULL ptr and passing it through to the callback 2) the BT_HDR * was being passed to the callback instead of a ptr to the payload 3) the size was being passed as a constant BT_HDR_SIZE. It looked like this code was expecting the callback to parse the BT_HDR, but that's an internal bluedroid structure. The callback is defined as receiving the report data and the report data size, which this change now provides. Note that the payload might be NULL if the device returns a HANDSHAKE error msg instead, and so it is valid to pass the callback a NULL payload ptr and a 0 size. Change-Id: I462b5cb5d4c460af085dc6e15f59c778a020a80e Signed-off-by: Mike J. Chen <mjchen@google.com>
tif_hh.c
|
8a82348c04109cb85e3c0b676dd1c7c5cb461c24 |
27-Jan-2014 |
Adam Hampson <ahampson@google.com> |
bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db Store the ssr_max_latency and ssr_min_tout parameters in the bonding database. Previously these parameters were not stored for HID devices. This caused an inconsistency in sniff behavior between when the HID device was paired and following a reboot of the host. When the HID device is paired the SSR parameters are retrieved from the HID device and are stored in the HID Host's device list. If the host is rebooted then the HID Host's device list is constructed from the bonding database. If the SSR max latency is non-zero then the SSR parameters are sent to the firmware and SSR is used. In the event that the SSR max latency is 0, as it is if the parameters are not found, then SSR is disabled. Bug: 12764547 Change-Id: I63637575fdfcf4cb4ca0ce8dc2e4ccda9cccaf66 Signed-off-by: Adam Hampson <ahampson@google.com>
tif_hh.c
tif_storage.c
|
ddcf2f98fe6dbb6a130e77595caa67164185df50 |
16-Jan-2014 |
Zhihai Xu <zhihaixu@google.com> |
Merge "increase the bluetooth task priority when start a2dp."
|
4128e36cd8430dfbed16d364e6ab5265e1642db5 |
08-Jan-2014 |
Zhihai Xu <zhihaixu@google.com> |
increase the bluetooth task priority when start a2dp. change the BT task priority based on audio play state. increase the BT task priority to ANDROID_PRIORITY_URGENT_AUDIO ,when start ad2p audio playing. to better prevent CPU premption by other process/task(UI). restore the BT task priority when stop a2dp audio playing. bug:12082841 Change-Id: I34e8344cffea87f68987149c820cd3e84a4196d1
tif_av.c
|
eeeac99328c23304ab24698331b6600f3b545700 |
08-Nov-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add service UUIDs and data to advertising data Add support for UUIDs and custom service data in the advertising and scan response records. Change-Id: I6470427ad194871488cc90f3ab384b9ecf326b15
tif_gatt_client.c
|
2a2701cdddac0859a95e58aec542742c450145b9 |
16-Sep-2013 |
Kim Schulz <k.schulz@samsung.com> |
Fixes for problems found with coverity analyzer - fixed UNINITIALIZED variable (hdl) in bta_hh_act.c :220 - fixed possible RESOURCE LEAK in btif_config_util.cpp in relation to open_file_map() if file is fd size=0 - fixed possible RESOURCE LEAK in create_socket_server() in uipc:196 (s not closed) - fixed possible OVERRUN in l2c_csm.c, (l2c_csm_config), array "l2cb.fixed_reg" of 4 20-byte elements at element index 60 (byte offset 1200) using index "p_ccb->local_cid - 3" (which evaluates to 60) - fixed possible OVERRUN in btm_pm.c, (btm_pm_reset) array "btm_cb.acl_db" of 7 288-byte elements at element index 7 (byte offset 2016) using index "btm_cb.pm_pend_link" (which evaluates to 7). - fixed possible OVERRUN in btif_storage.c, (btif_storage_add_device_to_autopair_blacklist) array "input_value" of 20 bytes by passing it to a function which accesses it at byte offset 20 using argument "20U". patch set 2: - fixed {} Patch set 3: - fixed review commment in stack/btm/btm_pm.c:379 bug: 10777562 Change-Id: I2a6d57f93acaaf9b25c49a6a29cb60d0e1e3c5d8
tif_config_util.cpp
tif_storage.c
|
41b33913995e5baf53461fe50f836717c2a47db9 |
16-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge " the HID device state is out of sync after upair."
|
03c26931a463dd079bda26bfd19f323743f57f3e |
16-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
the HID device state is out of sync after upair. the HID device state is out of sync between java layer and bluedroid stack after upair. This will cause the HID device can't be connected after repair. YOu can find the following error message E/HidService( 1452): Hid Device not disconnected: 00:15:9E:20:29:41 bug:11718702 Change-Id: I271bb77a2cc205c5a0ef396db86b87902d29966b
tif_hh.c
|
491cc70bac4e6fddd9728a184a58e4907b3beab5 |
16-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "fix a potential native crash during bluetooth sutdown"
|
6c65c2f3a372885a976c14b3ccacd0b5a5fbb8bd |
26-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
fix a potential native crash during bluetooth sutdown When bluetooth is initialized which call gki_buffer_init, the buffer pool is allocated by GKI_os_malloc which is to call libc malloc function. When bluetooth is cleanup which call GKI_shutdown, the buffer pool will be freed by GKI_os_free which is to call libc free function. So if we access the buffer, after the whole buffer pool is freed, we will get this native crash. if we call cleanup during bluetooth disabling: the state is still BTIF_CORE_STATE_DISABLING, then GKI_shutdown will call before bte_main_disable ( bt_hc_if->cleanup();), which is before userial thread exit. Then we may trigger this native crash. bug:11793775 Change-Id: Ic8ced12848d25f918a28f4d5ba29b803d6ac5bd7
luetooth.c
tif_core.c
|
b3724709a0893d5abab42c459776d47f0ec17781 |
16-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "implement flow control to avoid dropping packets in btif_media_task."
|
4aebca4662c280fdc32e0ad3705cae064bfa068d |
19-Sep-2013 |
Zhihai Xu <zhihaixu@google.com> |
implement flow control to avoid dropping packets in btif_media_task. implment flow conrol to save CPU usage and avoid dropping packet in btif_media_task when overflow and cpu preemption happen. when the packet count in the queue is above high watermark, we will stopping adding packets, when the packet count in the queue is below low watermark, we will start adding packets again. bug:8252054 Change-Id: I3b7795dffbe5f2ae455e239a0234533f6cbb4403
tif_media_task.c
|
f507e5ea3fb41303af92b8491e9e925e1ade9326 |
16-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "should return correct length and use shorter poll time for ad2p data"
|
01c686ce0051433d75605ff9ca4c3b7388ce3b6b |
16-Sep-2013 |
Zhihai Xu <zhihaixu@google.com> |
should return correct length and use shorter poll time for ad2p data the default poll timeout(100ms) is too long for a2dp data read, because the a2dp timer pertiod to read data is 20ms. The poll timeout should be far less than a2dp timer pertiod. also when poll timeout happen for read, we should return the data length which we already read instead of 0. bug:8252054 Change-Id: Ifa8587c6b7d127cbbbff76d9e20b630303b6379f
tif_media_task.c
|
f081595669be4242c7e23f850d83d9b876612bec |
11-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "BLE HID device connection failure due to security error."
|
7051db3a486aae771d9b5a81c3546790f86ede34 |
13-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
BLE HID device connection failure due to security error. When HID BLE device start encryption, if some other GATT application already start encryption(but not finished yet) by calling gatt_security_check_start. The HID BLE device will be failed to start encryption, which will cause it to disconnect the BLE HID connection. The solution is to check whether we already started the encryption , If the encryption is already started, wait until the encryption finished, then continue to start security check for BLE HID device. add encrytion complete event to notify all GATT client encryption done. filter the event just for BTA HH LE GATT client. bug:11636246 Change-Id: If58e57c623cc8cfa05208587b010bec68c71306c
tif_gatt_test.c
|
0b93f5ce4df14aa3d3100a8f9609a1c7ea4cdbd9 |
06-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
use bluetooth HID remote device name as input device name. bug:12003067 Change-Id: I74e4921047a27ee79fa1e3cd58056fde2958e60f
tif_hh.c
|
d3f44782195519d97589f2362e5a8879ee7b62ff |
04-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "Pairing with dissapeard HID decive never times out (in UI)"
|
a9eb25c8c01e70613bace21b23a06bd9a10871b1 |
30-Sep-2013 |
Kim Schulz <k.schulz@samsung.com> |
Pairing with dissapeard HID decive never times out (in UI) - added function to notify the UI about failed HID pairing patch set2: - added function header patch set3: - break long line Bug: 10998578 Change-Id: I7314bf07da7ebac7252c6902d987fbca20da2abc
tif_dm.c
tif_hh.c
|
b0a43da3b412f53557125bf352dd9dddfd1a9991 |
24-Sep-2013 |
Kim Schulz <k.schulz@samsung.com> |
memset arguments wrongfully swapped the arguments for one of the memset calls was wrong. Bug: 10907215 Change-Id: Ie00a3a6b829b99fd94659a764b6f0309684d9303
tif_storage.c
|
767b2f98f168f8e4822598cb7b35f10bf586aa8a |
07-Nov-2013 |
Matthew Xie <mattx@google.com> |
am 04e05e9a: Merge "LE: Add devices to the inquiry db before connecting" into klp-dev * commit '04e05e9a39cbed22a099458c35207795a0039043': LE: Add devices to the inquiry db before connecting
|
306bddadeec993013cfed6bf0e41a1a47a69367c |
07-Nov-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add devices to the inquiry db before connecting Ensure that the remote device type is set correctly by reading the device information from non-volatile storage and (re-)adding it to the inquiry database before connecting to a remote GATT device. bug 11573208 Change-Id: Ifa69da3d5871aed5293ea5e611144874b67afe72
tif_gatt_client.c
tif_gatt_server.c
tif_gatt_util.c
|
43fb9ada63dc76542f25d9510ca5f60bd66ef8e4 |
07-Nov-2013 |
Matthew Xie <mattx@google.com> |
am 6088d83d: Merge "whitelist well tested devices for absolute volume feature" into klp-dev * commit '6088d83d6ce30275b15fd0e5955a83f709f03172': whitelist well tested devices for absolute volume feature
|
6088d83d6ce30275b15fd0e5955a83f709f03172 |
07-Nov-2013 |
Matthew Xie <mattx@google.com> |
Merge "whitelist well tested devices for absolute volume feature" into klp-dev
|
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
tif_rc.c
|
7391a6fbda12f838f51ca7a4bd1cc44cb9e0a05c |
06-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
am 29fdb17a: Merge "need to save the BLE HID UUID to NVRAM" into klp-dev * commit '29fdb17a232f45c5550e7fa8d773f87e06ac58f1': need to save the BLE HID UUID to NVRAM
|
d7ee77bf8bb7f009b8088c15dcf5458b6f1fd05d |
06-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
need to save the BLE HID UUID to NVRAM need to save the BLE HID UUID to NVRAM. otherwise we will miss the HID profile setting in device profile list of the BLE HID device after reboot. bug:11541617 Change-Id: I11e1c871768e999ec1f48396018c3be379cc1b7d
tif_dm.c
|
f47598b9d6242435a96be1b6e7d3ffa31463ed88 |
25-Oct-2013 |
Matthew Xie <mattx@google.com> |
am 93449a36: Merge "Blacklist Devices that donot handle absolute volume well" into klp-dev * commit '93449a36de3b17e95f442ebd49614fa30707cbbb': Blacklist Devices that donot handle absolute volume well
|
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
tif_rc.c
|
52d0d8d67b41d81b494c8f3de0eb40bd7ee4e751 |
13-Oct-2013 |
zzy <zhenye@broadcom.com> |
am 031d239b: When rfcomm incoming queue is not empty, waiting for app ready to drain the data * commit '031d239b408618294a5980cb3933e03e185f96cf': When rfcomm incoming queue is not empty, waiting for app ready to drain the data
|
031d239b408618294a5980cb3933e03e185f96cf |
09-Oct-2013 |
zzy <zhenye@broadcom.com> |
When rfcomm incoming queue is not empty, waiting for app ready to drain the data Fixed the issue that rfcomm inbound packets could be out of order when host flow control is activating. bug 11031800 Change-Id: Idc1eb6633bb070f1ab2b33a9751fd7d714764d45
tif_sock_rfc.c
|
0b132028e5f16ca474a920f400dc8a87d49405d7 |
10-Oct-2013 |
Matthew Xie <mattx@google.com> |
am 65b8e0f3: Merge "Remove MMS support from MAP SDP" into klp-dev * commit '65b8e0f360f7fe7be001087c899eebc507115f9d': Remove MMS support from MAP SDP
|
65b8e0f360f7fe7be001087c899eebc507115f9d |
10-Oct-2013 |
Matthew Xie <mattx@google.com> |
Merge "Remove MMS support from MAP SDP" into klp-dev
|
85f334eb26bb2d16741f61c2ea538f6c1f6bec4b |
10-Oct-2013 |
Matthew Xie <mattx@google.com> |
am 6b728e41: Merge "Interleave br/edr device discovery with BLE device scan for some targets" into klp-dev * commit '6b728e412c22549ef51c19315ccf9ab3b7e16885': Interleave br/edr device discovery with BLE device scan for some targets
|
6b728e412c22549ef51c19315ccf9ab3b7e16885 |
10-Oct-2013 |
Matthew Xie <mattx@google.com> |
Merge "Interleave br/edr device discovery with BLE device scan for some targets" into klp-dev
|
7f3e42943b834ff0f556cd5c063a896f54d53167 |
30-Sep-2013 |
Matthew Xie <mattx@google.com> |
Interleave br/edr device discovery with BLE device scan for some targets This change only applies to targets which do not support interleaved scan in controller. bug 8508849 Change-Id: Ia99faf92c942b4b33abfde2708eff25ec9cd5468
tif_dm.c
|
71c1c591dbe9f44e496ea2ff9d974d6ae7bce62f |
10-Oct-2013 |
zzy <zhenye@broadcom.com> |
am 7939ed0c: added filter remove api to control the # of child node for bt_config.xml * commit '7939ed0c9a50c769e9e648a2d7751e0894b485ed': added filter remove api to control the # of child node for bt_config.xml
|
7939ed0c9a50c769e9e648a2d7751e0894b485ed |
28-Sep-2013 |
zzy <zhenye@broadcom.com> |
added filter remove api to control the # of child node for bt_config.xml Bug 10949832 Change-Id: I10589b9d0a0b4b8d7cbf66122c66bb2e99be04a1
tif_config.c
tif_storage.c
|
41d651a95ad63519e28f23f39a5c31c2dd0c8574 |
09-Oct-2013 |
Matthew Xie <mattx@google.com> |
Remove MMS support from MAP SDP When we support MMS in the future. Revert this patch. bug 10296324 Change-Id: I9d65895d6cb55b3967efcddc2c37b3f95ba3ce38
tif_sock_sdp.c
|
0819fa24e289d9f1cc3c4dd75e5dee2b1a8505bf |
05-Oct-2013 |
Zhihai Xu <zhihaixu@google.com> |
am 379743be: Failure to start playback on A2DP sink after connection * commit '379743beded881127703334e1dda2cd327ec651d': Failure to start playback on A2DP sink after connection
|
379743beded881127703334e1dda2cd327ec651d |
29-Sep-2013 |
Zhihai Xu <zhihaixu@google.com> |
Failure to start playback on A2DP sink after connection This is what happen: after Headset is connected, we call start_audio_datapath which will send AVDTP_Start command to Headset, Headset reject it with bad state. Bluedroid stack will ack failure to start_audio_datapath. The next time we write audio data to bluetooth, we will call start_audio_datapath again to send AVDTP_Start command to Headset Headset reject it with bad state again. Bluedroid stack will ack failure to start_audio_datapath. When the third time we call start_audio_datapath, right at that time we receive AVDTP_Start command from Headset. Handle AVDTP_Start command and Handle start_audio_datapath are in two different threads. Handle AVDTP_Start command is in btu_task thread. Handle start_audio_datapath() is in btif_task thread. We have race condition in this case Because when btif_task processed BTIF_AV_START_STREAM_REQ_EVT(triggered by start_audio_datapath), it don't know we receive AVDTP_Start command which is processed in btu_task. btif_task will send a message BTA_AV_API_START_EVT to btu_task, which will be handled by bta_av_do_start. AVDTP_start command from headset is handled by bta_av_start_ok. bta_av_start_ok will send BTA_AV_START_EVT with suspending true to btif_task and send AVDTP_Suspend command to headset to suspend the AVDTP for reconfiguration purpose. in bta_av_do_start, we will check whether the AVDTP is already started, we will know the AVDTP is already start at this time because bta_av_do_start is also running in btu_task. We will send BTA_AV_START_EVT with success to btif_task. In the btif_task, BTA_AV_START_EVT will be processed by btif_av_state_opened_handler: For the first BTA_AV_START_EVT with suspending true sent by bta_av_start_ok, it will ignore it: if ((p_av->start.status == BTA_SUCCESS) && (p_av->start.suspending == TRUE)) return TRUE; For the second BTA_AV_START_EVT with success sent by bta_av_do_start , it will ack success to start_audio_datapath, and change to BTIF_AV_STATE_STARTED/BTAV_AUDIO_STATE_STARTED, after receive success ack from bluedroid stack, we will start send Audio data to bluetooth. At last we received AVDTP_Suspend response accept from Headset, we will send BTA_AV_SUSPEND_EVT to btif_task, which will be handled by btif_av_state_started_handler. It will call btif_a2dp_on_suspended and call audio_state_cb with new audio state BTAV_AUDIO_STATE_STOPPED. so The state between bluedroid stack and audio data path is out of sync. The fix is to send failure message if we know we suspend AVDTP in bta_av_do_start, also make sure we won't miss acknowledgement for pending start if we exit opened state, to avoid audio data path dead lock. bug:10953908 Change-Id: I1704839977324b7c4e234eb843cddf3719e10d2c
tif_av.c
tif_media_task.c
|
3975936fa35873ada869644d0903cb83d7d4a3b9 |
27-Sep-2013 |
Matthew Xie <mattx@android.com> |
am a3c389f3: Merge "Avoid potential buffer overrun in bd2str caused by signed char" * commit 'a3c389f35287c9b1642c6f9a35fd22ff28f47919': Avoid potential buffer overrun in bd2str caused by signed char
|
f2fc54d237a24dc4db307cb56a513a8720809f95 |
02-Jul-2013 |
Chris Dearman <chris.dearman@imgtec.com> |
Avoid potential buffer overrun in bd2str caused by signed char Use uint8_t to avoid sign extension as char's may be signed. As a further safeguard, use snprintf() Change-Id: Icdd4dba9b270bde41547677fa2f98bf215401a23
tif_util.c
|
a30d95acf60f04531923e8ab06d976744697bf51 |
18-Sep-2013 |
Matthew Xie <mattx@google.com> |
Increase default bluetooth name from 15 to 31. bug 7441329 Change-Id: I79d64e77f206268ace06ce0f7b16119f63655bec
tif_dm.c
|
b8ceaa484a09be14263d5f10d022a272f9602378 |
05-Apr-2013 |
Mattias Agren <magren@broadcom.com> |
Set default a2dp sbc encoding quality to high * Increased bitpool to high quality setting (53). * Added rate quality reduction to medium quality for basic rate connections * Enhanced a2dp frame calculation ratio to smooth out frame distrubution * Removed iop scaling patch. Bug 8252054 Change-Id: I20725d0decfe5f820e1c03407889b6272e830aca
tif_av.c
tif_media_task.c
|
003284a0c70b60a7c959ea3bbc023e0fbda26be1 |
14-Sep-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "fix wrong PBAP profile SDP record which may cause some carkit interop problem." into klp-dev
|
d0cbb2ed7abda2ca15e04c10dbf8de9bfc91369a |
14-Sep-2013 |
Zhihai Xu <zhihaixu@google.com> |
fix wrong PBAP profile SDP record which may cause some carkit interop problem. bug:10488422 Change-Id: I8fb4a73a631c84dc812f44593743905f2d2ad108
tif_sock_sdp.c
|
844682e302538e9ebf80c05c0dc37ea28961ff39 |
14-Sep-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "Changed MAP version from 1.0 to 1.1, since this is what was actually implemented" into klp-dev
|
1e5109b5cbf49810abd0c94c413ce07db52caaca |
10-Nov-2012 |
Matthew Xie <mattx@google.com> |
Use product model as default bluetooth name if not defined bug 7441329 Change-Id: I6afe54a8a0c4d1120e96eb808cf9fc4bf5b37fdb
tif_dm.c
|
98139d9ecf9f42bffa26b6840659131b0b3258f0 |
22-Aug-2013 |
Kim Schulz <k.schulz@samsung.com> |
Changed MAP version from 1.0 to 1.1, since this is what was actually implemented Change-Id: If391121ca92f1025bff3a99941afa12da69c3b69 Bug: 10434562
tif_sock_sdp.c
|
c8a9f438cd994a7e69aa7fa957e0b9139bfdb912 |
22-May-2013 |
Priti Aghera <paghera@broadcom.com> |
Incremented buffer size to accomodate default MTU L2CAP Config request was not sent from Bluedroid as the MTU size was higher than the max buffer size for default apdu tx/rx sizes. Incremented the buffer size to accomodate this default MTU size. Also included new datatypes and corresponding tx/rx apdus. This will set the MTU size to that defined in datatype config rather than selecting default value. b/10565872 Change-Id: Id469c836581fb3d020bcb88c381421e0ef965073
tif_hl.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
tif_av.c
tif_rc.c
tif_util.c
|
607e3b79f1731de0d08a2c03d38ae17874bc282d |
16-Aug-2013 |
Matthew Xie <mattx@google.com> |
Place handling of BTA_DM_DISC_BLE_RES_EVT in BLE feature ifdef Without this fix, bluetooth fail to compile for non-BLE platform Change-Id: Ida10c54ab841e0a2bcaeb389a9813dd846db8200
tif_dm.c
|
cb21f0434223a51d94eb4c6b5b62f77f9efa0a83 |
16-Aug-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "LE: Add support for the HID-over-GATT profile (1/3)" into klp-dev
|
2e7fa68bfd9723b7ec7b6b0b128d89f31a2e06ee |
09-Aug-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add support for the HID-over-GATT profile (1/3) bug:8330048 Change-Id: I5727161b0a87700487bee96cdffa8fd169034204
tif_dm.c
|
98497a520010fc996a8ce490665cac6c1439dd2d |
25-Jun-2013 |
John Du <johnldu@google.com> |
Add support for ff/rew Change-Id: I017a7ddc9f7255d84ad8bf3284fefc1b7040900f (cherry picked from commit 342bdf540d8c183d14ec5fb436b73cd979df3a8f)
tif_rc.c
|
5c44e45473e5fc2fa89411ab1add7dbfc979f1f8 |
07-Aug-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add peripheral role support (2/4) Initial stack support for the LE peripheral role. Change-Id: I261d751b43b7020760bff345b472b6f60caa60be
tif_dm.c
tif_gatt_client.c
|
ace8d679f68cfab4c022d00afc7e5daafc74a4fd |
12-Jul-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Check encryption state before starting encryption Previously, the btif layer kept track of when a link was encrypted using an internal list to track encryptino callbacks. This change switches to querying the stack for the actual encryption state, since the btif layer may not receive all encryption related callbacks. Bug: BLTH02382147 Change-Id: I426b87d77e9a18531c2d42733a7e736a73bb116f
tif_gatt_client.c
tif_gatt_server.c
tif_gatt_util.c
|
5f9c140d094ebf4a269cdc6ae083900bf25f7fae |
09-Jul-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add instance ID to descriptors (2/4) If a remote devices offers multiple descriptors with the same UUID, the instance ID is used to differentiate between them. Change-Id: I1f3c284d714719fe9fb9cbb297c70a061c62a96d
tif_gatt_client.c
tif_gatt_util.c
|
6975b4d711142b885af479721cada448952c6b41 |
06-Aug-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: UPF 45 bug fixes This change fixes the following issues: - Second GATT-over-BR/EDR channel cannot be established when there already is an existing GATT-over-BR/EDR channel - If encryption fails for an LE connection due to a missing key, the security state is not being cleared and blocks all further security processing - When DM discovery of an LE Peripheral device fails with a connection timeout, no further discovery requests can be made - GATT service discovery can get into endless loop when duplicate descriptor definitions are found on the remote device - When GATT over BR/EDR fails, BTA does not give a connection callback to the application initiating the connection - BR/EDR connection to remote platform does not generate API callbacks - Stack crash discovered during UPF after remote disconnects - The host is sending HCI disconnect to invalid HCI handle when SMP fails because of a connection timeout - Possible race condition: If a disconnect is immediately followed by a connection complete, the connection complete cannot be processed in the BTA GATT state machine - Write Complete event is not triggered for Prepare Write requests Change-Id: I539cdedd68007818ff4f0d0213cee1c913f72d0f Conflicts: bta/gatt/bta_gatts_act.c
tif_gatt_client.c
tif_gatt_util.c
|
e1202caae4920139ea0cfed5c51f5f76b2dc8bc4 |
15-May-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add GATT disable functions This patch adds required disable functions to the GATT sub-system to properly unregister with the stack. Without the disable functions in place, turning Bluetooth off with a GATT device connected may lead to unexpected behaviour and cause GATT to fail on sub-sequent stack restarts. Change-Id: I7cb80e96109e2c09882991298d0487b506f5ffdd
tif_core.c
tif_gatt.c
|
f052217962d0c06392eb79687820c9469cd6a75a |
29-May-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Fix GKI exception for 0 length values When a remote device responds to a read request with a 0 length value, a GKI exception will occur. This patch checks for 0 length values to avoid the exception and return the correct status to the application requesting the read. Change-Id: Idce61c3d2be7072dafe429ab978763b0ee61aed2
tif_gatt_client.c
|
e4020c28c8a9dc56f927b03a8ca3a17d9401bc1e |
17-May-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add NULL pointer check in deep copy function Adds a NULL pointer check for the GATT read event deep copy function. Change-Id: Ia8d31e851589612009e1038c11b7b113e5367c6d
tif_gatt_client.c
tif_gatt_util.c
|
8444d1e649864c28b0c124bc2d16f7c153f01f14 |
17-Apr-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Deep copy buffers when transfering client context Certain BTA client event types require a deep copy of the request data buffers when transfering context. Shallow copy of the pointers involved may cause a crash when overlapping read and write requests are received. Change-Id: Id59b034d7fdd28087695a0688caff66b4cef4a4d
tif_gatt_client.c
|
181adbef76c194e257639daecb486bfc9a0ad037 |
10-Aug-2013 |
zzy <zhenye@broadcom.com> |
Fixed issue that failed to update rfc credit to peer when host can not handle the incoming packets fast enough Bug 10233699: Bluetooth sockets block indefinitely on read(...)
tif_sock_rfc.c
|
153767ee55e16c45235e590305bdbc0ba952da63 |
19-Jul-2013 |
Matthew Xie <mattx@google.com> |
Bluetooth MAP profile - sms and mms support initial check-in bug:10116530 Change-Id: I3bff487fdc0ee1256afa8d704a2cfa788081208c
tif_sock_sdp.c
|
4420e41159663c904fd55fbb7dd4816129467fb5 |
27-Jul-2013 |
Ajay Dudani <adudani@codeaurora.org> |
Fix check for BTIF_HL_CCH_OP_MDEP_FILTERING in btif_hl_upstreams_evt Change-Id: If080fad6ba4b42944dc5ee8bf1d8f0586dbd05f8
tif_hl.c
|
292d9f5a84da312a13ce3e881cd3df09bc492882 |
26-Jul-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "Add debug menu to enable btsnoop"
|
4c03040fa975cc23ea27b183908b1008bb3231f9 |
26-Jun-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
am 29a69a11: am ec7e2c8e: Do not abort bonding if link disconnects during SDP after Auth cmplt * commit '29a69a1144fc42d3742bacb9acee89a612cbf8b3': Do not abort bonding if link disconnects during SDP after Auth cmplt
|
ec7e2c8e06396101c6b26187995db7c105ed3c3f |
20-Jun-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Do not abort bonding if link disconnects during SDP after Auth cmplt If ACL link gets dropped during service search after bonding, re-attempt service search instead of setting bond state to BOND_NONE Bug 8611134 Change-Id: I77672d9f4feab634b3795a41e0d4e58903b5d275
tif_dm.c
|
390c94dc0f9deee917f52caaf3f8bb9f79aa98b4 |
16-May-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Removed COD check for unbond and UNPAIRED_EVT PC supporting HID Device would not have Peripheral as its MAJOR COD. So COD check for major peripheral device was removed in case of UNBOND and while receiving UNPAIRED_EVT. Additonal checking is done when virtual unplug evt is received to remove bonding only for HID Devic with MAJOR COD as Peripheral or if its a locally initiated VUP. Change-Id: I5343919463e48babc9cd03e05ff92a3f93f6d26d
tif_dm.c
tif_hh.c
|
bad70b1d0071ee9b16a029ff145e8e53038571ff |
05-Jun-2013 |
Zhihai Xu <zhihaixu@google.com> |
Add debug menu to enable btsnoop bug: 8059358 Change-Id: I232f6d47e7fb7e9c4d71c119394fce3e72cd02fc
luetooth.c
tif_core.c
|
194cdc31b949e2a72a53ab8fd4abed162ee00910 |
30-May-2013 |
Kausik Sinnaswamy <kausik@broadcom.com> |
am 67f5817f: am 77d1cb6f: Fix for AV lockup on local and remote start collision * commit '67f5817f1526faa64d3720c2c3d471117c520de8': Fix for AV lockup on local and remote start collision
|
77d1cb6ff904b48ee85c09a06c5e05dd0ed049b9 |
22-May-2013 |
Kausik Sinnaswamy <kausik@broadcom.com> |
Fix for AV lockup on local and remote start collision Bug: 7002859 Change-Id: I6170be864b44011b98e08d7e2599021a3eec70a3
tif_av.c
|
02b14ec482d7eec54bf57f8f18d1f6487dc3df57 |
15-May-2013 |
YK Jeffrey Chao <jechao@broadcom.com> |
am 2fca6e54: am 48ebe2c6: Preload timeout and retry mechanism (1/3) * commit '2fca6e548ff48988e63d3550d807b016192e0a77': Preload timeout and retry mechanism (1/3)
|
48ebe2c6928d8fd4dc97c8adb138c3440714dc89 |
24-Apr-2013 |
YK Jeffrey Chao <jechao@broadcom.com> |
Preload timeout and retry mechanism (1/3) If the Preload process was stuck due to unknown hardware init failure, a 8-second ENABLE_TIMEOUT timeout would be eventually expired in Java layer at AdapterState and attempted to set BT state back to STATE_OFF. However BluetoothManagerService did not handle this case accordingly and led to state mis-matching between Java layer and BTIF at the end. Add a timeout and retry mechanism to manage Preload process. Clean up native space resource and explicitly report STATE_OFF back to Java space when Preload did not go through. bug 7566317 Change-Id: I99a225e524f2b951249618990a2d0a8a39b43ff3
tif_core.c
|
da54571c77cf708d5196be153e8f9794f62a6da7 |
11-May-2013 |
Mattias Agren <magren@broadcom.com> |
am 83ecfd88: am 5fd74f06: Stability fixes for a2dp hal control path * commit '83ecfd882bec4f5761c4114c571b170c5a9376db': Stability fixes for a2dp hal control path
|
5fd74f06caab4324d0ba69df86ad5170c072ec64 |
05-Apr-2013 |
Mattias Agren <magren@broadcom.com> |
Stability fixes for a2dp hal control path Ensure av statemachine is preventing a2dp hal to restart the stream when not ready. This prevents ending up in a scenario where a2dp hal locks up. Code cleanup. bug 7002859 Change-Id: I3f3eeaab4ca185733b8b0042ed2cfa701f76a203
tif_av.c
tif_media_task.c
|
76d041f915e4c14b3fb11bae3c12fcb59f77bef5 |
10-May-2013 |
Matthew Xie <mattx@google.com> |
am e1405531: am e915116a: Merge "Solve compilation problem when BLE/GATT/SMP features are false" into jb-mr2-dev * commit 'e1405531f637a3851371a2a2c624ff3db5e074fa': Solve compilation problem when BLE/GATT/SMP features are false
|
e915116a24142955edbc40a0e380b4828957c762 |
09-May-2013 |
Matthew Xie <mattx@google.com> |
Merge "Solve compilation problem when BLE/GATT/SMP features are false" into jb-mr2-dev
|
fc4b2f1953dbe60464d0f5ef7daaa10001fbc62f |
07-May-2013 |
Matthew Xie <mattx@google.com> |
Solve compilation problem when BLE/GATT/SMP features are false bug 8664724 Change-Id: I582846ccf4b8995f298d8db533488fceb7993ae3
luetooth.c
tif_dm.c
tif_gatt_util.c
tif_storage.c
|
ec5f265762154e5f222e79ae132e58a5b7bc0cd6 |
07-May-2013 |
Kausik Sinnaswamy <kausik@broadcom.com> |
am 91409af5: am 95664a9a: Fix for SDP data structure leak during pairing * commit '91409af50ebd2e7590b8e2463e1d06ac13f00e18': Fix for SDP data structure leak during pairing
|
95664a9acc57b5e51365454f26d2fac0f2e1ecd4 |
03-May-2013 |
Kausik Sinnaswamy <kausik@broadcom.com> |
Fix for SDP data structure leak during pairing During pairing, bluedroid initiates a SDP request to search services. Upon SDP completion, some data structure buffers were not returned to the pool resulting in leak. Bug : 8797456 Change-Id: Ic512fd22ca6b8b748c5b92c02e24016fe785c0b1
tif_dm.c
|
6ded3e4bc35c9878771a59cb8cc75b702c2097fd |
24-Apr-2013 |
Priti Aghera <paghera@broadcom.com> |
am f9020d0d: am f8f30c2c: HDP fix for Single SDP record * commit 'f9020d0de5c8ade5fab86b26979620aac4f67dc9': HDP fix for Single SDP record
|
f8f30c2cecf221b2c3983b72d5a849d799c39dd7 |
03-Apr-2013 |
Priti Aghera <paghera@broadcom.com> |
HDP fix for Single SDP record Modified stack code to support single SDP record for each register app call. bug 8656462 Change-Id: I92570243306d5c1ca8339042eba5733e43fdb72c
tif_hl.c
tif_storage.c
|
8ec01b1006965a2966f116469f4f892382ab4d34 |
18-Apr-2013 |
Matthew Xie <mattx@google.com> |
am c11b7d75: am f5391070: Merge "LE (2/3): Add application ID to connection callback" into jb-mr2-dev * commit 'c11b7d7598516783083970d17d52be0d1d75bcc4': LE (2/3): Add application ID to connection callback
|
f5391070cbb1f3c66db34cef8501f2754cecc1e6 |
18-Apr-2013 |
Matthew Xie <mattx@google.com> |
Merge "LE (2/3): Add application ID to connection callback" into jb-mr2-dev
|
977b854e5121c0ea19ecab6eb2bdb3583f439568 |
10-Apr-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE (2/3): Add application ID to connection callback Bug: 8589393 Change-Id: Ib5c34ce1cddb0e32ad08ac3cbdeaa74cd8514f81
tif_gatt_server.c
|
ad7e70f3c8fa9db7c4a6cd4043597209a93b2ecb |
16-Apr-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
am 52eb4f3d: am 33af35c4: Fix for Nyko playpad * commit '52eb4f3d971d59e8b5f015c870e92a15a591fd55': Fix for Nyko playpad
|
33af35c49731bc8e305c862c8e9f3e42a1ab0dc9 |
10-Apr-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Fix for Nyko playpad Nyko playpad does not cmply with HID Device spec. NYKO gamepad advertises as supporting virtual unplug but when virtual is sent by host it responds with ERR_UNSUPPORTED_REQUEST. Modified BTIF code to start a timer when VUP is issued and fire the timer if peer does not respond. Bug:8055549 Change-Id: I90db956fb243f1a518b00424b103ebf9f0a1b7f0
tif_hh.c
|
b763c76763b655db75bb2ec731f673460e3bdcec |
08-Apr-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
am 2f338f25: BT: JV rfcomm socket sniff support * commit '2f338f25530d2aaab7acf45701c271d10b81d96d': BT: JV rfcomm socket sniff support
|
2f338f25530d2aaab7acf45701c271d10b81d96d |
24-Mar-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
BT: JV rfcomm socket sniff support Bug:8322094 Change-Id: Ib472f39488b685ac396289e65c1da21fdfd93c4c
tif_sock_rfc.c
|
7fe56f58c2a3cf0ac80177aaa890c143cd5fd950 |
29-Mar-2013 |
Priti Aghera <paghera@broadcom.com> |
Save the HID info into storage while adding device Previously HID device info was not saved immediately to NVRAM, thus when device was rebooted sometimes the hid information was missing from NVRAM, thus host does not identify the HID Device bug 8192743 Change-Id: I7ca8b607399e141fa851242e83c1c6d3854384f8
tif_storage.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
tif_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
tif_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
tif_rc.c
|
1f9a190b457f6a0e8effd47998014cb724fdb085 |
21-Mar-2013 |
Zhihai Xu <zhihaixu@google.com> |
Merge "Initial version of Stack for AVRCP 1.3" into jb-mr2-dev
|
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
luetooth.c
tif_av.c
tif_rc.c
tif_util.c
|
ca22ac493ab777199084d87b3c7627e7f27555af |
13-Feb-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE fixes - Null pointer exception check added. An exception occurs at the memcpy in the bta_dm_gatt_disc_result. User removed the battery on Ble device(Smart Nudge) during bonding and connection. This exception occurs sometimes. I used Broadcom LE Explorer to reproduce it. - Fixed disconnect and encryption behaviour Disconnect will now disconnect the physical link immediately when no other application is interested in the device anymore. Also, the connection to a remote device is now dropped if encryption fails. - Deep copy buffers when transfering context Certain BTA server event types require a deep copy of the request data buffers when transfering context. Shallow copy of the pointers involved may cause a crash when overlapping read and write requests are received. - 2nd encryption has not started need to send encryption complete callback when the encryption fail due to link drop without a complete event. Otherwise BTA layer would not be able to clean up the status, and no further encryption can be started. Change-Id: If93e0a188e8779830c8991e4193b96dc95e23e5d
tif_dm.c
tif_gatt_server.c
tif_gatt_util.c
|
ead3cde4bac0c3e32cd31f149093f004eef8ceeb |
06-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Initial version of BLE support for Bluedroid Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
luetooth.c
tif_core.c
tif_dm.c
tif_gatt.c
tif_gatt_client.c
tif_gatt_server.c
tif_gatt_test.c
tif_gatt_util.c
tif_hf.c
tif_hh.c
tif_hl.c
tif_storage.c
tif_util.c
|
e17bf003d4eefdc8525e55894210e9ee494972b8 |
16-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Cancel device search before starting SDP Also update bonding state when acl link goes down during bonding b/8120036 Change-Id: I28e4cb6f35e4c524b7a67281e78a196ba1fce0cb
tif_dm.c
|
ebb1d755818704a662f7ea8ae3cc1b5593d582d8 |
28-Nov-2012 |
Priti Aghera <paghera@broadcom.com> |
Fixed unpair and reconnect issue with certain non-pointing hid devices Hid info would not be removed from storage if COD is NON_KEYBOARD_NON_POINTING. Due to this the device will be added to stack even if it is unpaired and subsequent connections will fail. bug 8055549 Change-Id: Ib493fc165120de3c71398f5fe24b17f31fa5fc3e
tif_dm.c
tif_hh.c
|
45f5f9077c773b9d4533fef13045b5ff77e32e46 |
08-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Resolved partial uipc channel read issue When partial data is read the previously read size wasn't compensated for. Ensure we don't transmit empty a2dp frames in case of underrun Bug 8026551 Change-Id: I4195ed798008378b93343bf7cd266c6e2f11b094
tif_media_task.c
|
d70b7a8ebce5a9646b8baf16a24a6eda88b1a4f6 |
31-Jan-2013 |
Nick Kralevich <nnk@google.com> |
fix too small buffer property_get must be called with a buffer of at least PROPERTY_VALUE_MAX len. The supplied buffer is too small. Fixed. Change-Id: I6c6b3050b30f6aa5ece69888263394e572551aff
tif_dm.c
|
9ac641d0a674333af57b85b367e64cf94dfae291 |
16-Jan-2013 |
Matthew Xie <mattx@google.com> |
fixed rfc resouce leaking and multi-session issue also added more debug messages bug 7486080 Change-Id: Ic21e9d2df5f651b51ea2126a3cac25811808dcfb
tif_sock_rfc.c
|
689d66b6559dcb3a0ad7f6cc33b6129e50910253 |
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot 9fd57cbacd95e89602f430244c35bbc67f08b6d2 Change-Id: Ibc3a4bf4161d286c7cfab89a19c676eb5cc9224f
tif_config.c
tif_config_util.cpp
tif_hh.c
tif_pan.c
tif_sock.c
tif_sock_rfc.c
tif_sock_sdp.c
tif_sock_util.c
tif_storage.c
|
5738f83aeb59361a0a2eda2460113f6dc9194271 |
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
luetooth.c
tif_av.c
tif_config.c
tif_config_util.cpp
tif_core.c
tif_dm.c
tif_hf.c
tif_hh.c
tif_hl.c
tif_media_task.c
tif_pan.c
tif_profile_queue.c
tif_rc.c
tif_sm.c
tif_sock.c
tif_sock_rfc.c
tif_sock_sdp.c
tif_sock_thread.c
tif_sock_util.c
tif_storage.c
tif_util.c
|