Also remove other bluedroid references.
Change-Id: I349e48e50b0a0a45ca1267a765145299837601d3
extern thread_t *bt_workqueue_thread;
/* trace level */
-/* TODO Bluedroid - Hard-coded trace levels - Needs to be configurable */
+/* TODO Hard-coded trace levels - Needs to be configurable */
UINT8 appl_trace_level = BT_TRACE_LEVEL_WARNING; //APPL_INITIAL_TRACE_LEVEL;
UINT8 btif_trace_level = BT_TRACE_LEVEL_WARNING;
***********************************************************************************/
#define LOG_NDDEBUG 0
-#define LOG_TAG "bt_bluedroid"
+#define LOG_TAG "bt_btif"
#include <stdio.h>
#include <stdlib.h>
*
******************************************************************************/
-/*****************************************************************************
- *
- * Filename: btif_av.c
- *
- * Description: Bluedroid AV implementation
- *
- *****************************************************************************/
-
#include "btif_av.h"
#include <assert.h>
* typically written to the socket in a tight loop, hence we risk the ioctl
* will return the total amount of data in the buffer, which could be
* multiple 64kbyte chunks.
- * UPDATE: As bluedroid cannot handle 64kbyte buffers, the size is reduced
+ * UPDATE: As the stack cannot handle 64kbyte buffers, the size is reduced
* to around 8kbyte - and using malloc for buffer allocation here seems to
* be wrong
* UPDATE: Since we are responsible for freeing the buffer in the
real-time debugging of HCI data with hcidump.
This feature is enabled by setting `BtSnoopLogOutput=true` in `bt_stack.conf`.
-Once it has been enabled and the stack restarted, bluedroid will listen for
+Once it has been enabled and the stack restarted, the stack will listen for
incoming TCP connections on port 8872.
To use this feature with hcidump on a Linux host, you can run:
* audio_a2dp_hw - A2DP audio HAL implementation.
* bta - *Bluetooth Application* - Strange collection of a-lot of things **Deprecate?**
* btcore - *Bluetooth Core* - Bluetooth data type definitions and operations on those data types.
-* btif - *Bluetooth Interface* - Bluedroid JNI interface to Android.
+* btif - *Bluetooth Interface* - JNI interface to Android.
* conf - *Configuration* - Various configuration text files.
* doc - *Documentation* - Stack documentation.
* embdrv - **Deprecated** - Bluetooth SBC Codec.
-* hci - *Host Controller Interface* - Communication protocol with bluetooth chip.
+* hci - *Host Controller Interface* - Communication protocol with Bluetooth chip.
* include - **Deprecated** - System global include files.
* main - *Main stack entrypoint* - Provides HAL for stack access.
* osi - *Operating System Interface* - General resource support for stack.
Log Tags
===
-This document lists all of the log tags used by bluedroid.
+This document lists all of the log tags used by the Bluetooth stack.
* audio_a2dp_hw
-* bluedroid
* BTA_AG_CO:
* bta_sys_main
+* bt_btif
* bt_btif_config
* bt_btif_config_transcode
* bt_classic_peer
Network Ports
===
-This document lists all of the network ports used by bluedroid. It should be
-used as a reference and as a mechanism to avoid port namespace conflicts.
+This document lists all of the network ports used by the bluetooth stack.
+It should be used as a reference and as a mechanism to avoid port
+namespace conflicts.
* TCP 8872 (hci/src/btsnoop_net.c) - read live btsnoop logs
* TCP 8873 (hci/src/hci_inject.c) - inject HCI packets into HCI stream
### Overview
-Power management (PM) in bluedroid is an event-driven state machine, tickled by
-various `bta/sys` events via a callback. The actual state switching calls are
-handled by the BTM HCI interfacing code, with results being posted back to the
-PM code via the BTA workqueue thread.
+Power management (PM) is an event-driven state machine, tickled by various
+`bta/sys` events via a callback. The actual state switching calls are handled
+by the BTM HCI interfacing code, with results being posted back to the PM
+code via the BTA workqueue thread.
Power states are managed per-device, per-profile, so every incoming event
includes a profile ID, app ID, and a `BD_ADDR`.
Properties
===
-This document describes all of the Android properties used by bluedroid.
+This document describes all of the Android properties used by the Bluetooth
+stack.
Please keep the following list in alphabetical order.
#define BTA_EIR_SERVER_NUM_CUSTOM_UUID 8
#endif
-/* CHLD override for bluedroid */
+/* CHLD override */
#ifndef BTA_AG_CHLD_VAL_ECC
#define BTA_AG_CHLD_VAL_ECC "(0,1,1x,2,2x,3)"
#endif
int64_t TIMER_INTERVAL_FOR_WAKELOCK_IN_MS = 3000;
static const clockid_t CLOCK_ID = CLOCK_BOOTTIME;
static const clockid_t CLOCK_ID_ALARM = CLOCK_BOOTTIME_ALARM;
-static const char *WAKE_LOCK_ID = "bluedroid_timer";
+static const char *WAKE_LOCK_ID = "bluetooth_timer";
static const char *WAKE_LOCK_PATH = "/sys/power/wake_lock";
static const char *WAKE_UNLOCK_PATH = "/sys/power/wake_unlock";
static ssize_t locked_id_len = -1;
include $(CLEAR_VARS)
LOCAL_MODULE_TAGS := optional
-LOCAL_MODULE := gtest_net_test_bluedroid
+LOCAL_MODULE := gtest_net_test_bluetooth
LOCAL_C_INCLUDES += \
$(LOCAL_PATH)/../../
include $(CLEAR_VARS)
LOCAL_MODULE_TAGS := optional
-LOCAL_MODULE := net_test_bluedroid
+LOCAL_MODULE := net_test_bluetooth
LOCAL_C_INCLUDES += \
$(LOCAL_PATH)/../../