GitLab

Remove the link key if encryption fails due to missing key or
authentication error. When a remote device loses the bond, all
HOGP services cached should be discarded and all client configuration
descriptors needs to be re-enabled. This will ensure successful
re-connection.

Bug: 15022622
Change-Id: Ie1730830c0cbbc294e2cd579d7dca69d16cf8218

ACL link up notifaction was not sent after LE read remote features was successful.
Thus, total ACL link up count was not updated. Included a link up notification
after LE read remote features is successfull.

Bug: 17410697
Change-Id: I41fc640e76fa99354cb63d9b0b3031582178c057

Bug: 17401266
Change-Id: I5f36e13b3ccb327f191db33123fff98858f07c5f

To avoid premature connection notification to app, always wait for
LE read remote feature complete with success before the connection
event is sent to application.
bug 17326529

Change-Id: Id731bf02e8d5d5a68db12e0478b8eb74723eb95d

Send Set_Random_Address when privacy is enabled. If Set_Random_Address
is not sent to controller, Connection request will be sent with host
address as all 0's

Bug: 17386986
Change-Id: I59877e52bf76a56696800ff0e75487c633adde3c

A previous changed introduced an error in the timer tick calculation
when removing a timer. This could lead to timers expiring sooner than
expected.

Bug: 17390240
Change-Id: Id3291aaf492a7178782e6f804dad71387c3c9382

Change-Id: I5e3d164898563478ddf5d21197e682600f8cc33f

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

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

Bug: 10773872
Change-Id: I7f5b5f976ee7fa522e02b9ee4369b8f152b15cfb

If the vendor library is unable to open the UART,
the passed in file descriptor array is unchanged.
This array was uninitialized stack memory which
may miss the illegal fd check and barrel ahead
forking a userial read thread causing FD_SET
problems should the uninitialized stack memory be
bogus fds outside the processes boundaries.
Verify that the vendor library was actually opening
exactly one uart.

Bug: 16651586

Change-Id: I24e700cdb0b0f3ed107f56b94b5b535abba66806

To avoid trun off BT failed, stack have to send out BTA_DM_DISABLE_EVT
even disconnect ACL failed during turning of BT procedire. Trigger
bta_dm_disable_timer_cback() again after 1.5 sec.

Bug: 17158327

Change-Id: I096d535603faf7b302febea7cfff7a3364d4b048
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>

Determine the transport to use for BTM_ReadRSSI based on the
device type of the remote device.

Bug: 16694076
Change-Id: I5a591f9d629547b63a750cefd7feb72899922595
Signed-off-by: Thomas.TT_Lin <Thomas.TT_Lin@htc.com>

There is no remote device type info wgeb OOB pairing LE
devices. Add device type according to transport.

Bug: 17156993
Change-Id: I29182ca13f801f8a7f2c3a95969d6ae23312dd7e

Stack changes for handling the API call sequence changes. Please refer buganizer for more details on the API sequence changes

Bug:16850169
Change-Id: Iabef8247a290d163c1fe03cb853d12678b559664

Corrected the byte position for HCI Command
- Set Batch Scan Param sub cmd

bug 17182636

Change-Id: I45045a6e548ed2539d5e43695725883ca1e4ed7a

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

Change-Id: I997f5f9395af6c5da0403dc496317b2bad1683e6

Fix potential bug where stale timer list entry causes endless loops in
BTU task. Also added return parameter to GKI_remove_from_timer_list() to
allow breaking out of the BTU timer task look in case the timer list
becomes corrupted.

Bug: 16897789
Change-Id: Ic70cf4346efbb063bbb952ebe7c2f7d0bf395493

Terminate strings before parsing to values.

Might be related to:
bug: 16877287

Change-Id: I0c46861229a90f37e266bd06bcba9ac78e3fc155
Signed-off-by: Casper Bonde <c.bonde@samsung.com>

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

* commit '390d5386':
  Bluetooth: Restarting PM timer during incoming rfcomm data.

Change-Id: Ia4ecf38de8a017f5624ab7b32f8ac398de15dee4

Change-Id: I00951bb14384be4fdc946410f1082963af8ad569

am 212ffc1d: (-s ours) am 39277ce1: enhance the "invalid rfc slot id" log to include the caller\'s name

* commit '212ffc1d':
  enhance the "invalid rfc slot id" log to include the caller's name

* commit 'e68188f8':
  Bluetooth: Restarting PM timer during incoming rfcomm data.

    
During incoming rfcomm data, we were setting the pm mode to
active, thereby stopping timer and never restarting it again.
So it was never going to sniff , if the last packet is incoming
packet. Therefore add change to restart the PM timer during incoming
data.

Bug:17044698
Change-Id: I4396bb2f267b12cb92a944c15609ddeaa13288ad