bta_jv_sm_execute() function

* Function btu_hcif_send_cmd * Description This function is called to send commands to the Host Controller. * Returns void

* Function l2c_link_check_send_pkts * Description This function is called to check if it can send packets * to the Host Controller. It may be passed the address of * a packet to send. * Returns void

* Function L2CA_DataWrite * Description Higher layers call this function to write data. * Returns L2CAP_DW_SUCCESS, if data accepted, else FALSE * L2CAP_DW_CONGESTED, if data accepted and the channel is congested * L2CAP_DW_FAILED, if error

* Function AVCT_MsgReq * Description Send an AVCTP message to a peer device. In calling * AVCT_MsgReq(), the application should keep track of the * congestion state of AVCTP as communicated with events * AVCT_CONG_IND_EVT and AVCT_UNCONG_IND_EVT. If the * application calls AVCT_MsgReq() when AVCTP is congested * the message may be discarded. The application may make its * first call to AVCT_MsgReq() after it receives an * AVCT_CONNECT_CFM_EVT or AVCT_CONNECT_IND_EVT on control channel or * AVCT_BROWSE_CONN_CFM_EVT or AVCT_BROWSE_CONN_IND_EVT on browsing channel. * p_msg->layer_specific must be set to * AVCT_DATA_CTRL for control channel traffic; * AVCT_DATA_BROWSE for for browse channel traffic. * Returns AVCT_SUCCESS if successful, otherwise error.

* Function attp_send_sr_msg * Description This function sends the server response or indication message * to client. * Parameter p_tcb: pointer to the connecton control block. * p_msg: pointer to message parameters structure. * Returns GATT_SUCCESS if successfully sent; otherwise error code.

* Function rfc_send_buf_uih * Description This function sends UIH frame.

* Function rfc_check_send_cmd * Description This function is called to send an RFCOMM command message * or to handle the RFCOMM command message queue. * Returns void

* Function bta_hh_snd_write_dev

* Function AVRC_BldCommand * Description This function builds the given AVRCP command to the given * GKI buffer * Returns AVRC_STS_NO_ERROR, if the command is built successfully * Otherwise, the error code.

* Function l2cu_set_acl_hci_header * Description Set HCI handle for ACL packet * Returns None

* Function AVRC_BldResponse * Description This function builds the given AVRCP response to the given * GKI buffer * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function BTA_AvMetaCmd * Description Send a Metadata/Advanced Control command. The message contained * in p_pkt can be composed with AVRC utility functions. * This function can only be used if AV is enabled with feature * BTA_AV_FEAT_METADATA. * This message is sent only when the peer supports the TG role. 8 The only command makes sense right now is the absolute volume command. * Returns void

* Function l2c_fcr_clone_buf * Description This function allocates and copies requested part of a buffer * at a new-offset. * Returns pointer to new buffer

* Function bte_main_hci_send * Description BTE MAIN API - This function is called by the upper stack to * send an HCI message. The function displays a protocol trace * message (if enabled), and then calls the 'transmit' function * associated with the currently selected HCI transport * Returns None

* Function l2c_link_send_to_lower * Description This function queues the buffer for HCI transmission * Returns TRUE for success, FALSE for fail

* Function OBEX_GetNextHeader * Description Get next header pointer from a packet * Returns Pointer to start address of a header, NULL if no more header * or failed

* Function avdt_msg_send * Description Send, and if necessary fragment the next message. * Returns Congested state; TRUE if CCB congested, FALSE if not.

* Function avdt_ad_write_req * Description This function is called by a CCB or SCB to send data to a * transport channel. It looks up the LCID of the channel * based on the type, CCB, and SCB (if present). Then it * passes the data to L2CA_DataWrite(). * Returns AVDT_AD_SUCCESS, if data accepted, else FALSE * AVDT_AD_CONGESTED, if data accepted and the channel is congested * AVDT_AD_FAILED, if error

* Function avrc_get_data_ptr * Description Gets a pointer to the data payload in the packet. * Returns A pointer to the data payload.

* Function L2CA_SendFixedChnlData * Description Write data on a fixed channel. * Parameters: Fixed CID * BD Address of remote * Pointer to buffer of type BT_HDR * Return value L2CAP_DW_SUCCESS, if data accepted * L2CAP_DW_FAILED, if error

* Function attp_send_msg_to_l2cap * Description Send message to L2CAP.

* Function l2c_enqueue_peer_data * Description Enqueues data destined for the peer in the ccb. Handles * FCR segmentation and checks for congestion. * Returns void

* Function AVRC_MsgReq * Description This function is used to send the AVRCP byte stream in p_pkt * down to AVCTP. * It is expected that p_pkt->offset is at least AVCT_MSG_OFFSET * p_pkt->layer_specific is AVCT_DATA_CTRL or AVCT_DATA_BROWSE * p_pkt->event is AVRC_OP_VENDOR, AVRC_OP_PASS_THRU or AVRC_OP_BROWSE * The above BT_HDR settings are set by the AVRC_Bld* functions. * Returns AVRC_SUCCESS if successful. * AVRC_BAD_HANDLE if handle is invalid.

* Function BTA_AvMetaRsp * Description Send a Metadata/Advanced Control response. The message contained * in p_pkt can be composed with AVRC utility functions. * This function can only be used if AV is enabled with feature * BTA_AV_FEAT_METADATA. * Returns void

* Function OBEX_AppendHeaderRaw * Description Append a header to specific packet, packet can be request * or response, data not include 2 byte length prefixed * Returns OBEX_SUCCESS if successful, otherwise failed

* Function OBEX_ParseResponse * Description Parse a request response packet * Returns OBEX_SUCCESS if successful, otherwise failed

* Function AVDT_WriteReqOpt * Description Send a media packet to the peer device. The stream must * be started before this function is called. Also, this * function can only be called if the stream is a SRC * When AVDTP has sent the media packet and is ready for the * next packet, an AVDT_WRITE_CFM_EVT is sent to the * application via the control callback. The application must * wait for the AVDT_WRITE_CFM_EVT before it makes the next * call to AVDT_WriteReq(). If the applications calls * AVDT_WriteReq() before it receives the event the packet * will not be sent. The application may make its first call * to AVDT_WriteReq() after it receives an AVDT_START_CFM_EVT * or AVDT_START_IND_EVT. * The application passes the packet using the BT_HDR structure * This structure is described in section 2.1. The offset * field must be equal to or greater than AVDT_MEDIA_OFFSET * (if NO_RTP is specified, L2CAP_MIN_OFFSET can be used) * This allows enough space in the buffer for the L2CAP and * AVDTP headers. * The memory pointed to by p_pkt must be a GKI buffer * allocated by the application. This buffer will be freed * by the protocol stack; the application must not free * this buffer. * The opt parameter allows passing specific options like: * - NO_RTP : do not add the RTP header to buffer * Returns AVDT_SUCCESS if successful, otherwise error.

* Function gatt_cmd_enq * Description Enqueue this command. * Returns None.

* Function btm_acl_paging * Description send a paging command or queue it in btm_cb

* Function l2c_fcr_proc_pdu * Description This function is the entry point for processing of a * received PDU when in flow control and/or retransmission modes. * Returns -

* Function l2c_data_write * Description API functions call this function to write data. * Returns L2CAP_DW_SUCCESS, if data accepted, else FALSE * L2CAP_DW_CONGESTED, if data accepted and the channel is congested * L2CAP_DW_FAILED, if error

* Function l2c_rcv_acl_data * Description This function is called from the HCI Interface when an ACL * data packet is received. * Returns void

* Function rfc_send_test * Description This function sends Test frame.

* Function RFCOMM_DataReq * Description This function is called by the user app to send data buffer

* Function do_sar_reassembly * Description Process SAR bits and re-assemble frame * Returns TRUE if all OK, else FALSE

* Function process_i_frame * Description Process an I frame * Returns -

* Function prepare_I_frame * Description This function sets the FCR variables in an I-frame that is * about to be sent to HCI for transmission. This may be the * first time the I-frame is sent, or a retransmission * Returns -

* Function bta_av_stream_data_cback * Description This is the AVDTP callback function for stream events. * Returns void

* Function OBEX_CheckFinalBit * Description Check whether a packet had set the final bit * Returns TRUE if final bit set, otherwise, false

* Function OBEX_SendPacket * Description Send a packet to peer OBEX server or client, once call * this function, the ownership of pkt is lost, do not free * or modify the pkt any more * Returns OBEX_SUCCESS if successful, otherwise failed

* Function avrc_copy_packet * Description Copies an AVRC packet to a new buffer. In the new buffer, * the payload offset is at least AVCT_MSG_OFFSET octets. * Returns The buffer with the copied data.

* Function port_write * Description This function when a data packet is received from the apper * layer task. * Parameters: p_port - pointer to address of port control block * p_buf - pointer to address of buffer with data,

* Function HID_HostWriteDev * Description This function is called when the host has a report to send. * report_id: is only used on GET_REPORT transaction if is specified. * only valid when it's a non-zero value. * Returns void

* Function BTM_WriteEIR * Description This function is called to write EIR data to controller. * Parameters p_buff - allocated HCI command buffer including extended * inquriry response * fec_required - FEC is required or not * Returns BTM_SUCCESS - if successful * BTM_MODE_UNSUPPORTED - if local device cannot support it

* Function btu_hcif_process_event * Description This function is called when an event is received from * the Host Controller. * Returns void

* Function gatt_le_data_ind * Description This function is called when data is received from L2CAP. * if we are the originator of the connection, we are the ATT * client, and the received message is queued up for the client. * If we are the destination of the connection, we are the ATT * server, so the message is passed to the server processing * function. * Returns void

SMP_INCLUDED == TRUE * Function gatt_verify_signature * Description This function start to verify the sign data when receiving * the data from peer device. * Returns

* Function gatts_db_read_attr_value_by_type * Description Query attribute value by attribute type. * Parameter p_db: pointer to the attribute database. * p_rsp: Read By type response data. * s_handle: starting handle of the range we are looking for. * e_handle: ending handle of the range we are looking for. * type: Attribute type. * mtu: MTU. * sec_flag: current link security status. * key_size: encryption key size. * Returns Status of the operation.

* Function bta_dm_sm_execute * Description State machine event handling function for DM * Returns void

* Function bta_dm_search_sm_execute * Description State machine event handling function for DM * Returns void

* Function btm_route_sco_data * Description Route received SCO data. * Returns void

* Function bta_sys_sm_execute * Description State machine event handling function for DM * Returns void

* Function bta_gattc_hdl_event * Description GATT client main event handling function. * Returns BOOLEAN

* Function l2c_link_segments_xmitted * Description This function is called from the HCI Interface when an ACL * data packet segment is transmitted. * Returns void

* Function bta_gatts_hdl_event * Description BTA GATT server main event handling function. * Returns void

Extended Inquiry Response Commands ***

* Function gatt_le_data_ind * Description This function is called when data is received from L2CAP. * if we are the originator of the connection, we are the ATT * client, and the received message is queued up for the client. * If we are the destination of the connection, we are the ATT * server, so the message is passed to the server processing * function. * Returns void

* Function rfc_process_mx_message * Description This function processes UIH frames received on the * multiplexer control channel.

* Function rfc_parse_data * Description This function processes data packet received from L2CAP

* Function PORT_DataInd * Description This function is called from the RFCOMM layer when data * buffer is received from the peer.

* Function rfc_process_test * Description This function handles Test frame. If this is a command * reply to it. Otherwise pass response to the user.

* Function smp_data_received * Description This function is called when data is received from L2CAP on * SMP channel. * Returns void

* Function smp_send_msg_to_L2CAP * Description Send message to L2CAP.

* Function bta_sdp_sm_execute * Description State machine event handling function for SDP search * Returns void

* Function sdp_server_handle_client_req * Description This is the main dispatcher of the SDP server. It is called * when any data is received from L2CAP, and dispatches the * request to the appropriate handler. * Returns void

* Function sdp_disc_server_rsp * Description This function is called when there is a response from * the server. * Returns void

* Function process_s_frame * Description Process an S frame * Returns -

* Function process_stream_frame * Description This function processes frames in streaming mode * Returns -

* Function l2c_fcr_tx_get_fcs * Description This function computes the CRC for a frame to be TXed. * Returns CRC

* Function l2c_fcr_rx_get_fcs * Description This function computes the CRC for a received frame. * Returns CRC

* Function sdp_data_ind * Description This function is called when data is received from L2CAP. * if we are the originator of the connection, we are the SDP * client, and the received message is queued up for the client. * If we are the destination of the connection, we are the SDP * server, so the message is passed to the server processing * function. * Returns void

* Function smp_br_data_received * Description This function is called when data is received from L2CAP on * SMP BR channel. * Returns void

* Function bta_av_dup_audio_buf * Description dup the audio data to the q_info.a2d of other audio channels * Returns void

* Function bta_av_hdl_event * Description Advanced audio/video main event handling function. * Returns BOOLEAN

* Function OBEX_AppendHeaderSRM * Description Append a Single Response Mode header * Returns OBEX_SUCCESS if successful, otherwise failed

* Function OBEX_AppendHeaderSRMP * Description Append a Single Response Mode Parameters header * Returns OBEX_SUCCESS if successful, otherwise failed

* Function OBEX_CheckContinueResponse * Description Check whether a packet is continue response * Returns TRUE if continue response, otherwise, false

* Function OBEX_BuildRequest * Description Build a request packet with opcode and additional info, * packet can free by osi_free * Returns OBEX_SUCCESS if successful, otherwise failed

* Function bta_av_sbc_bld_hdr * Description This function builds the packet header for MPF1. * Returns void

* Function btc_a2dp_sink_enque_buf * Description This function is called by the av_co to fill A2DP Sink Queue * Returns size of the queue

* Function btc_a2dp_source_audio_feeding_init * Description Initialize the audio path according to the feeding format * Returns void

* Function btc_a2dp_source_enc_update * Description Update encoding task * Returns void

* Function btc_a2dp_source_enc_init * Description Initialize encoding task * Returns void

* Function avdt_msg_ind * Description This function is called by the adaption layer when an * incoming message is received on the signaling channel. * It parses the message and sends an event to the appropriate * SCB or CCB for the message. * Returns Nothing.

* Function avdt_ad_tc_data_ind * Description This function is called by the L2CAP interface layer when * incoming data is received from L2CAP. It looks up the CCB * or SCB for the channel and routes the data accordingly. * Returns Nothing.

* Function avct_l2c_data_ind_cback * Description This is the L2CAP data indication callback function. * Returns void

* Function avdt_l2c_data_ind_cback * Description This is the L2CAP data indication callback function. * Returns void

* Global data * Function avrc_bld_next_cmd * Description This function builds the Request Continue or Abort command. * Returns AVRC_STS_NO_ERROR, if the command is built successfully * Otherwise, the error code.

* Function avrc_bld_app_setting_text_rsp * Description This function builds the Get Application Settings Attribute Text * or Get Application Settings Value Text response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_next_rsp * Description This function builds the Request Continue or Abort * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

Function bta_hd_hdl_event Description HID device main event handling function. Returns void

Function bta_hd_cback Description BTA HD callback function Returns void

Function hidd_l2cif_data_ind Description Handler incoming data on L2CAP channel Returns void

* Function Declarations * Function bta_jv_co_rfc_data * Description This function is called by JV to send data to the java glue * code when the RX data path is configured to use a call-out * Returns void

* Function gap_data_ind * Description This function is called when data is received from L2CAP. * Returns void

* Function RFCOMM_BufDataInd * Description This is a callback function called by L2CAP when * data RFCOMM frame is received. Parse the frames, check * the checksum and dispatch event to multiplexer or port * state machine depending on the frame destination.

* Function rfc_port_uplink_data * Description This function handles uplink information data frame.

* Function bta_ag_hdl_event * Description Data gateway main event handling function. * Returns BOOLEAN

* Function bta_hf_client_hdl_event * Description Data HF Client main event handling function. * Returns BOOLEAN

* Function BTA_HhSetReport * Description send SET_REPORT to device. * Parameter dev_handle: device handle * r_type: report type, could be BTA_HH_RPTT_OUTPUT or * BTA_HH_RPTT_FEATURE. * Returns void

* Function BTA_HhSendData * Description This function send DATA transaction to HID device. * Parameter dev_handle: device handle * dev_bda: remote device address * p_data: data to be sent in the DATA transaction; or * the data to be write into the Output Report of a LE HID * device. The report is identified the report ID which is * the value of the byte (UINT8 *)(p_buf + 1) + p_buf->offset. * p_data->layer_specific needs to be set to the report type, * it can be OUTPUT report, or FEATURE report. * Returns void

* Static Function * Function bta_hh_cback * Description BTA HH callback function. * Returns void

* Function bta_hh_hdl_event * Description HID host main event handling function. * Returns void

* Function hidh_conn_snd_data * Description This function is sends out data. * Returns tHID_STATUS

* Function hidh_l2cif_data_ind * Description This function is called when data is received from L2CAP. * if we are the originator of the connection, we are the SDP * client, and the received message is queued up for the client. * If we are the destination of the connection, we are the SDP * server, so the message is passed to the server processing * function. * Returns void

* Function BTM_WriteScoData * Description This function write SCO data to a specified instance. The data * to be written p_buf needs to carry an offset of * HCI_SCO_PREAMBLE_SIZE bytes, and the data length can not * exceed BTM_SCO_DATA_SIZE_MAX bytes, whose default value is set * to 60 and is configurable. Data longer than the maximum bytes * will be truncated. * Returns BTM_SUCCESS: data write is successful * BTM_ILLEGAL_VALUE: SCO data contains illegal offset value. * BTM_SCO_BAD_LENGTH: SCO data length exceeds the max SCO packet * size. * BTM_NO_RESOURCES: no resources. * BTM_UNKNOWN_ADDR: unknown SCO connection handle, or SCO is not * routed via HCI.

* Function AVDT_WriteReq * Description Send a media packet to the peer device. The stream must * be started before this function is called. Also, this * function can only be called if the stream is a SRC. * When AVDTP has sent the media packet and is ready for the * next packet, an AVDT_WRITE_CFM_EVT is sent to the * application via the control callback. The application must * wait for the AVDT_WRITE_CFM_EVT before it makes the next * call to AVDT_WriteReq(). If the applications calls * AVDT_WriteReq() before it receives the event the packet * will not be sent. The application may make its first call * to AVDT_WriteReq() after it receives an AVDT_START_CFM_EVT * or AVDT_START_IND_EVT. * The application passes the packet using the BT_HDR structure. * This structure is described in section 2.1. The offset * field must be equal to or greater than AVDT_MEDIA_OFFSET. * This allows enough space in the buffer for the L2CAP and * AVDTP headers. * The memory pointed to by p_pkt must be a GKI buffer * allocated by the application. This buffer will be freed * by the protocol stack; the application must not free * this buffer. * Returns AVDT_SUCCESS if successful, otherwise error.

CLASSIC_BT_INCLUDED == TRUE * Function L2CA_DataWriteEx * Description Higher layers call this function to write data with extended * flags. * flags : L2CAP_FLUSHABLE_CH_BASED * L2CAP_FLUSHABLE_PKT * L2CAP_NON_FLUSHABLE_PKT * Returns L2CAP_DW_SUCCESS, if data accepted, else FALSE * L2CAP_DW_CONGESTED, if data accepted and the channel is congested * L2CAP_DW_FAILED, if error

* Function GAP_ConnBTRead * Description GKI buffer aware applications will call this function after * receiving an GAP_EVT_RXDATA event to process the incoming * data buffer. * Returns BT_PASS - data read * GAP_ERR_BAD_HANDLE - invalid handle * GAP_NO_DATA_AVAIL - no data available

* Function GAP_ConnBTWrite * Description GKI buffer aware applications can call this function to write data * by passing a pointer to the GKI buffer of data. * Returns BT_PASS - data read * GAP_ERR_BAD_HANDLE - invalid handle * GAP_ERR_BAD_STATE - connection not established * GAP_INVALID_BUF_OFFSET - buffer offset is invalid

* Function PORT_Read * Description This function returns the pointer to the buffer received * from the peer device. Normally application will call this * function after receiving PORT_EVT_RXCHAR event. * Application calling this function is responsible to free * buffer returned. * Parameters: handle - Handle returned in the RFCOMM_CreateConnection * callback. * pp_buf - pointer to address of buffer with data,

* Function PORT_Write * Description This function to send BT buffer to the peer device. * Application should not free the buffer. * Parameters: handle - Handle returned in the RFCOMM_CreateConnection * p_buf - pointer to the buffer with data,

* Function btu_hcif_command_complete_evt * Description Process event HCI_COMMAND_COMPLETE_EVT * Returns void

* Function btu_hcif_command_status_evt * Description Process event HCI_COMMAND_STATUS_EVT * Returns void

* Function attp_cl_send_cmd * Description Send a ATT command or enqueue it. * Returns GATT_SUCCESS if command sent * GATT_CONGESTED if command sent but channel congested * GATT_CMD_STARTED if command queue up in GATT * GATT_ERROR if command sending failure

* Function gatt_build_primary_service_rsp * Description Primamry service request processed internally. Theretically * only deal with ReadByTypeVAlue and ReadByGroupType. * Returns void

* Function gatt_build_find_info_rsp * Description fill the find information response information in the given * buffer. * Returns TRUE: if data filled successfully. * FALSE: packet full, or format mismatch.

* Function L2CA_Echo * Description Higher layers call this function to send an echo request * with application-specific data. * Returns TRUE if echo request sent, else FALSE.

* Function OBEX_BuildResponse * Description Build a response packet with opcode and response and additional * info, packet can by free by osi_free * Returns OBEX_SUCCESS if successful, otherwise failed

* Function OBEX_AppendHeader * Description Append a header to specific packet, packet can be request * or response, the format of header must be valid * Returns OBEX_SUCCESS if successful, otherwise failed

* Function OBEX_GetPacketFreeSpace * Description Get the current free space of a packet, use this to check * if a packet can hold a header * Returns Current free space of a packet, in bytes

* Function OBEX_GetPacketLength * Description Get the current packet length * Returns Current packet length, in bytes

* Function OBEX_ParseRequest * Description Parse a request packet * Returns OBEX_SUCCESS if successful, otherwise failed

* Function avct_lcb_msg_asmbl * Description Reassemble incoming message. * Returns Pointer to reassembled message; NULL if no message * available.

* Function avdt_msg_asmbl * Description Reassemble incoming message. * Returns Pointer to reassembled message; NULL if no message * available.

* Function avrc_proc_vendor_command * Description This function processes received vendor command. * Returns if not NULL, the response to send right away.

* Function avrc_msg_cback * Description This is the callback function used by AVCTP to report * received AV control messages. * Returns Nothing.

* Function avrc_proc_far_msg * Description This function processes metadata fragmenation * and reassembly * Returns 0, to report the message with msg_cback .

* the following commands are introduced in AVRCP 1.4 * Function avrc_bld_set_abs_volume_cmd * Description This function builds the Set Absolute Volume command. * Returns AVRC_STS_NO_ERROR, if the command is built successfully * Otherwise, the error code.

* Function avrc_bld_vol_change_notfn * Description This function builds the register notification for volume change. * Returns AVRC_STS_NO_ERROR, if the command is built successfully * Otherwise, the error code.

* Function avrc_bld_set_player_value_cmd * Description This function builds the Set Player Application Value command. * Returns AVRC_STS_NO_ERROR, if the command is built successfully * Otherwise, the error code.

* Function avrc_bld_get_element_attr_cmd * Description This function builds the Get Element Attribute command. * Returns AVRC_STS_NO_ERROR, if the command is built successfully * Otherwise, the error code.

* Function avrc_bld_notify_rsp * Description This function builds the Notification response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_set_app_setting_value_rsp * Description This function builds the Set Application Setting Value * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_get_cur_app_setting_value_rsp * Description This function builds the Get Current Application Setting Value * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_get_app_setting_attr_text_rsp * Description This function builds the Get Application Setting Attribute Text * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_get_app_setting_value_text_rsp * Description This function builds the Get Application Setting Value Text * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_inform_charset_rsp * Description This function builds the Inform Displayable Character Set * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_inform_battery_status_rsp * Description This function builds the Inform Battery Status * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_get_elem_attrs_rsp * Description This function builds the Get Element Attributes * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_get_play_status_rsp * Description This function builds the Get Play Status * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_group_navigation_rsp * Description This function builds the Group Navigation * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_set_absolute_volume_rsp * Description This function builds the Set Absolute Volume command * response * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_rejected_rsp * Description This function builds the General Response response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Global data * Function avrc_bld_get_capability_rsp * Description This function builds the Get Capability response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_list_app_settings_attr_rsp * Description This function builds the List Application Settings Attribute * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function avrc_bld_list_app_settings_values_rsp * Description This function builds the List Application Setting Values * response. * Returns AVRC_STS_NO_ERROR, if the response is built successfully * Otherwise, the error code.

* Function obex_tl_l2cap_send_data * Description Start the process of establishing a L2CAP connection * Returns OBEX_TL_SUCCESS, if data accepted * OBEX_TL_CONGESTED, if data accepted and the channel is congested * OBEX_TL_FAILED, if error

* Function obex_tl_l2cap_buf_data_ind * Description This is a callback function called by L2CAP when * data frame is received.

* Function L2CA_UcdDataWrite * Description Send UCD to remote device * Parameters: PSM * BD Address of remote * Pointer to buffer of type BT_HDR * flags : L2CAP_FLUSHABLE_CH_BASED * L2CAP_FLUSHABLE_PKT * L2CAP_NON_FLUSHABLE_PKT * Return value L2CAP_DW_SUCCESS, if data accepted * L2CAP_DW_FAILED, if error

* Function SDP_WriteData * Description This function sends data to the connected SDP server. * Returns TRUE if data is sent, FALSE if failed.