| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
BT core spec 5.3 promotes the usage of inclusive languages.
This CL replaces some terms with the more appropriate counterparts,
such as "central", "peripheral", and "accept list".
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds SPDX License Identifier and removes the license text.
-------------------------------------
License COUNT
-------------------------------------
Apache-2.0 : 80
LGPL-2.1-or-later : 42
GPL-2.0-or-later : 9
License: Apache-2.0
android/bluetoothd-wrapper.c
android/tester-hidhost.c
android/tester-map-client.c
android/hal-audio-aptx.c
android/hal-audio.c
android/hal-handsfree-client.c
android/tester-gatt.c
android/hal-pan.c
android/hal-socket.c
android/tester-hdp.c
android/tester-pan.c
android/tester-avrcp.c
android/hal-a2dp-sink.c
android/hal-gatt.c
android/hal-avrcp.c
android/tester-a2dp.c
android/hal-audio.h
android/hal-bluetooth.c
android/tester-socket.c
android/hal-health.c
android/hal-a2dp.c
android/hal-ipc.c
android/hal-avrcp-ctrl.c
android/hal-sco.c
android/hal-ipc.h
android/tester-main.c
android/hal-audio-sbc.c
android/hal-utils.c
android/hal-map-client.c
android/hal-handsfree.c
android/hal-log.h
android/hal.h
android/hal-utils.h
android/tester-bluetooth.c
android/hal-hidhost.c
android/audio_utils/resampler.h
android/audio_utils/resampler.c
android/system/audio.h
android/hardware/bt_sock.h
android/hardware/bt_gatt_client.h
android/hardware/bt_hh.h
android/hardware/bluetooth.h
android/hardware/hardware.h
android/hardware/bt_hf_client.h
android/hardware/bt_rc.h
android/hardware/bt_hf.h
android/hardware/bt_pan.h
android/hardware/bt_gatt_types.h
android/hardware/hardware.c
android/hardware/audio_effect.h
android/hardware/audio.h
android/hardware/bt_gatt_server.h
android/hardware/bt_gatt.h
android/hardware/bt_hl.h
android/hardware/bt_mce.h
android/hardware/bt_av.h
android/client/if-hh.c
android/client/if-sco.c
android/client/pollhandler.h
android/client/haltest.c
android/client/tabcompletion.c
android/client/if-hf-client.c
android/client/history.h
android/client/if-audio.c
android/client/terminal.h
android/client/if-av.c
android/client/if-main.h
android/client/if-av-sink.c
android/client/terminal.c
android/client/if-mce.c
android/client/if-hf.c
android/client/pollhandler.c
android/client/if-sock.c
android/client/if-rc-ctrl.c
android/client/if-rc.c
android/client/history.c
android/client/if-pan.c
android/client/if-gatt.c
android/client/if-bt.c
android/client/if-hl.c
License: LGPL-2.1-or-later
android/sco.h
android/socket.c
android/tester-main.h
android/hidhost.h
android/map-client.h
android/utils.h
android/hal-msg.h
android/health.h
android/avrcp-lib.c
android/bluetoothd-snoop.c
android/a2dp.c
android/bluetooth.h
android/a2dp-sink.c
android/handsfree-client.c
android/audio-msg.h
android/main.c
android/pan.c
android/ipc-tester.c
android/health.c
android/socket.h
android/handsfree.h
android/avrcp-lib.h
android/a2dp-sink.h
android/system-emulator.c
android/gatt.c
android/avrcp.h
android/pan.h
android/test-ipc.c
android/hidhost.c
android/a2dp.h
android/avrcp.c
android/sco-msg.h
android/bluetooth.c
android/map-client.c
android/handsfree-client.h
android/ipc.c
android/handsfree.c
android/gatt.h
android/ipc.h
android/ipc-common.h
android/compat/wordexp.h
android/cutils/properties.h
License: GPL-2.0-or-later
android/avdtp.h
android/avctp.c
android/avdtptest.c
android/sco.c
android/log.c
android/avdtp.c
android/avctp.h
android/compat/readline/history.h
android/compat/readline/readline.h
|
| |
|
|
|
|
|
|
|
| |
This is required for custom advertising data.
The HAL entry points related to multiadvertising are now implemented
and map to the mgmnt "add advertising" operation.
|
|
|
|
|
| |
Use the mgmnt "advinfo" operation to obtain the number of advertising
instances supported by the kernel.
|
|
|
|
| |
Key loading is not supported for LE only devices.
|
|
|
|
|
| |
This removes dead code due to memory allocation with new0 not being
able to fail.
|
|
|
|
|
|
| |
GATT code should always use bt_get_id_addr() when directly dealing with
remote address. This is to make sure that proper address and type is
used.
|
|
|
|
|
| |
This allows to get information if CSRK is authenticated or not.
For client it is don't care if CSRK is authenticated or not.
|
|
|
|
| |
This adds support for storing information if CSRK is authenticated.
|
|
|
|
| |
Any permanently stored key is indication of device being bonded.
|
|
|
|
|
| |
The 'master' parameter was renamed to 'type' and now has two new
possible values.
|
|
|
|
|
|
|
|
|
|
| |
Current code works fine for controllers supporting BR/EDR secure
connections.
We want to have LE Secure connection enabled also for controllers which
does not support BR/EDR secure connections. For this we need to set
secure connection in the kernel just after LE is enabled (if requested
on register)
|
|
|
|
| |
Add service class UUID instead of profile UUID to UUIDs list.
|
|
|
|
| |
This allow for dynamic MPS configuration ie fixing MPS on tablets.
|
|
|
|
|
|
| |
Track if ACL is connected and response corretly to get_connection_state
call. This seems to be used by some application to query for device
connection state.
|
| |
|
|
|
|
|
|
|
| |
If device that was previously seen only over LE connected over
BR/EDR it's type was not properly updated to dual mode.
This was affecting PTS TC_DM_BON_BV_01_C test.
|
|
|
|
|
|
| |
Some modules like GATT might be interested in information about ongoing
bonding on device. It can be useful e.g. to take decision if GATT can do
service search or should wait until bonding is done.
|
|
|
|
|
|
|
| |
Some modules might be interested in fact that device has been bonded.
This patch allows to register for that event
Note that callback is called only on success bonding.
|
| |
|
| |
|
|
|
|
|
|
| |
GATT is interested in advertising event type i.e if it is connectable
or not. It is because GATT does not want to trigger connection to
devices doing non-connectable advertising. This patch add such support.
|
|
|
|
|
|
|
| |
Android is interested in all of the Scan Responses. Also the ones which
are set as non discoverable. It is in order to support
Observer\Broadcaster mode. Therefore discoverable flag can be removed
from the device found callback. This patch does it.
|
| |
|
|
|
|
|
| |
LE Features is new property added in Android Lollipop. Framework is
expecting to get those features on bluetooth start.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Add parameter to create_bond following new bluetooth.h HAL, transport is
defined in bluedroid include/bt_types.h. Bluetooth daemon shall check
transport parameter and make needed decisions, by default parameter is
unknown and this is the way bluedroid manage it itself.
|
|
|
|
|
| |
Set A2DP-SRC_AVRCP-TG instead of A2DP-SNK_AVRCP-CT_DUN-DT bit.
It was affecting TC_SDP_CTH_SD_BV_01_I PTS test case.
|
|
|
|
|
| |
With this patch, gatt can set any value to each local/remote signed
counter. It is need by next patch.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Unpaired callback list for profiles needs to be set to NULL while
unregistering bluetooth. Other profiles may try to unregister and remove
its unpair cb, this cause invalid read callback list.
|
|
|
|
|
|
|
| |
When device is paired but no-bonded, Android GUI keep incorrect bonds
state after ACL disconnect. This patch fixes that
This patch also moved device_is_paired() up in the file
|
|
|
|
|
| |
This patch makes sure that any bond state changes of remote device is
corretly distributed to Android framework.
|
|
|
|
| |
When sending "fake" bonding" we should use SUCCESS status
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
As it turns out it is possible that kernel send to user space mgmt
events related to pairing before device connected event.
In such case BfA was dropping such event because he does not know
device.
With this patch, if device is not in the cache, BfA will create it.
Issue triggered by test: "Bluetooth Accept Bond - Just Works - Success"
|
|
|
|
|
|
| |
This patch adds tracking if device is in white list or not.
This is in order to make sure that we call mgmt inteface only when
neccessary
|
|
|
|
|
|
| |
GATT, HID, HOG, might be interested in the fact that some device has
been unpaired in order to clear cache or similar. This patch adds means
to register and unregister callback for unpaired event.
|
|
|
|
|
| |
With this patch Android framework will be notified about bonded device
which initiated bonding and used just works association model.
|
|
|
|
|
|
| |
This patch refactor a bit select_device_bearer function so we can get
debug log out of it. This log might be very useful in dual mode devices
scenarios
|
|
|
|
| |
With this patch correct bdaddr type is used in ssp pairing scenario
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far BfA updates android bond state after link key(s) are
distributed. With LE pairing it might happen that no keys are
distributed e.g remote device has Initiator Key Distribution and
Responder Key Distribution set to 0. In such case link is encrypted
with STK and after its disconnected, pairing needs to be done again.
With this patch Android will get update about pairing complete just
after BfA gets pairing complete from the kernel. It solve issue withnot
updated Android settings application, which is hanging on "Pairing", in
case when no keys are distributed.
However, bacause Android does not see the difference between bonded /
paired devices and because Android does not allow to update its bond
state if FSM it is not in 'pending' state, BfA updates Android with
BONDED state on pair_complete with success. This is how we are doing
so far for bonding and non-bonding pairing.
Note: BfA will update its bonded state after link key(s) are
distribiuted.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If device is dual mode and can be seen on both LE and BREDR, then
bdaddr_type in device struct keeps LE address type of that device.
During discovery, we should take current bdaddr_type to decide about
passing that device up to application or not. Using dev->braddr_type might
be misleading
This patch fix scenario when remote device is known as LE device and
recently has been found on inquiry seesion as DUAL mode device. In such
case, based on braddr_type and eir flags we could incorectly skip
new device notification for Android framework.
|
| |
|
|
|
|
| |
protos gets allocated and needs to be freed
|