| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Blacklist the device if it's rejected the role switch for
max number of times.Same is added to the iot_devlist.conf
file.
- Maximum number of failed (BTM_MAX_SW_ROLE_FAILED_ATTEMPTS)
attempts set to 3 and it is configurable.
- Same blacklisted device is referred by the BTM module when
any other module like profile is requesting for role switch
and BTM module returns BTM_REPEATED_ATTEMPTS as the switch
role status.
- There is option to retry for role switch even though the
device is blacklisted and it can be controlled by feature
flag BTM_SAFE_REATTEMPT_ROLE_SWITCH. And by default it is
enabled.
CRs-Fixed: 831542
Change-Id: I570e1539578e60901794941ca46f0722e368a954
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- write btsnoop from external process
- adjust the gmt offset to match with logcat logs
- avoid btsnoop file write if btsnoop client is connected
- limit the block of snoop write to 10 ms and drop the packet
- memcpy and issue single write to eliminate multiple I/O
- enable snoop by default on userdebug build
- option to override snoop config for userdebug build
Change-Id: I13749dc348baf88af57e3ebec1ec7acd5e999c04
|
| |
|
|
|
|
|
|
|
|
| |
This patch adds support to enable logging for hid host's and client's
stack components dynamically. Also some logs for host and cleint
are added under verbose logging level which would help in latency
measurements.
Change-Id: I06de0ea89b8f5e40466519fe60aead6497b6cf11
CRs-Fixed: 608230
|
| |
|
|
|
|
|
|
|
| |
As per Specification, Device providers should configure the
vendor ID as the Company Identifier provided by the Bluetooth
SIG. Hence Changing vendor ID as QTI for Device ID Profile.
Change-Id: I852113d2849ea4fd0725396fc92f320101aab0d0
CRs-Fixed: 547495
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A case, where 3 remote device (PANU role) is connected with DUT (NAP role).
the one remote (PANU role) send BNEP_COMPRESSED_ETHERNET_DEST_ONLY
packet to DUT (NAP role), which is for another remote device (PANU role).
So DUT (NAP role) forwards this packet to another remote device (PANU role).
As same pbuf is used across the L2CAP/BNEP/PAN layer since reception from
L2CAP to writing on L2CAP CID of another PANU. Sometimes buffer (p_buf) gets
corrupted, when required buffer size is greater than actual buffer size,
while rebuilding the Bnep header.
Using bnep_write instead of bnep_writeBuf to solve the buffer corruption
issue, which allocates the new buffer & append data into it.
This patch also add TRC_BNEP & TRC_PAN into conf file.
Bug: 22028876
Change-Id: I125cab6d3da0f8126605bc7e9f764a27ee72fb1f
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added support for exposing L2CAP to Java such that OBEX over L2CAP
is made possible.
Added support to create SDP records as a seperate step.(as opposed to
creating a SDP record when a BluetoothSocket is created).
This allows both a RFCOMM channel and a L2CAP PSM to be included in a
SDP record. (Additionally the content of the SDP record is set by the
profile in Java, in stead of beeing hardcoded in the socket layer.)
This completes the L2CAP channel exposure to Java.
Change-Id: Iaf68a07d910145cdd33e940d73cd680f79164100
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Currently a stack restart or device reboot will overwrite existing snoop
logs when the stack restarts. This patch adds a new configuration file
parameter "BtSnoopSaveLog" that, if enabled, will cause an existing
snoop log to be renamed to "<snoop_file_name>.last" before a new snoop
log is created.
This will allow for easier debugging of crashes that involve a reboot or
stack restart.
Change-Id: I4f56204d31a6bf2e96058938e8616eb6dee7360b
|
| |
|
|
| |
Change-Id: Iba77c9924c1f4fe926a7e59653b80e9d836c4fc5
|
| |
|
|
|
|
| |
bug 10904063
Change-Id: Ia14f00eb45ff8ba1d7df73db575aff552af7677a
|
| |
|
|
| |
Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
|
| |
|
|
| |
Change-Id: Ibc3a4bf4161d286c7cfab89a19c676eb5cc9224f
|
|
|
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
|
