9e030fde05352ec4385d7baf6cc2af89e95e039c |
|
25-Jun-2017 |
Jakub Pawlowski <jpawlowski@google.com> |
Rename bt_bdaddr_t into RawAddress (3/3) Test: compilation test Change-Id: I4571721a0c6165a66450ee157a53d8d15bfc45d0
/system/bt/bta/hf_client/bta_hf_client_int.h
|
c752e135d66f80c0b2efc35292ab8ddfd8227d61 |
|
16-Jun-2017 |
Jakub Pawlowski <jpawlowski@google.com> |
Replace BT_ADDR with bd_addr_t in bta_sys related code Test: compilation test Change-Id: Idab6e9c03621c5540b4a3a7fa537dff71a25ce3f
/system/bt/bta/hf_client/bta_hf_client_int.h
|
744eeca761b6d52d4e5fbbfa49c2d2adde0e6981 |
|
16-Jun-2017 |
Jakub Pawlowski <jpawlowski@google.com> |
Replace BD_ADDR with bt_bdaddr_t in hf client related code Test: compilation test Change-Id: Iee6b07b6a919e5d061a04cb3d919166661e673e8
/system/bt/bta/hf_client/bta_hf_client_int.h
|
d3ae18b3b3c65e38bbce5e3bf2882f4e050077dd |
|
08-Jun-2017 |
Jack He <siyuanh@google.com> |
eSCO: Limit number of retries after mSBC connection failure * When peer device supports mSBC and codec negotiation, Fluoride stack will try to do the following when establishing a eSCO/SCO connection: 1) Negotiate to mSBC by sending +BCS:2 2) Try establishing eSCO/SCO connection using mSBC T2 settings 3) If that failed, downgrade to mSBC T1 settings and retry 4) If that failed, re-negotiate codec to CVSD, by sending +BCS:1 5) Retry using CVSD S4 (HFP 1.7 and above) or S3 settings 6) If this failed stop trying and report failure to upper stack * Retry is achieved by: * Retry is only possible when inuse_codec = BTA_AG_CODEC_MSBC * Set codec_msbc_settings to BTA_AG_SCO_MSBC_SETTINGS_T1 when T2 failed to connect in step 3 above * Set codec_fallback to true when T1 failed so that CVSD is used in step 4 above * Retry stop is achieved by: * Set inuse_codec = BTA_AG_CODEC_CVSD * Set codec_msbc_settings back to BTA_AG_SCO_MSBC_SETTINGS_T2 * Set codec_fallback to false and codec_updated to true so that the stack is ready for the next application triggerred SCO connection attempt * Removed retry_with_sco_only as both Setup Synchronous Connection Command (0x0028) and Enhanced Setup Synchronous Connection Command (0x003D) fall back to SCO connection if eSCO is not supported. See page 858/2772 and 895/2772 of BT4.2 specification document * Besides both code paths are the same for retry_with_sco_only after eSCO changes went in Bug: 62426841 Test: make, HFP regression, testplans/91406 Change-Id: I205311c55e8763c48b6eb43c27f242927384036e
/system/bt/bta/hf_client/bta_hf_client_int.h
|
bd3ae7cbf195caf91693046147b34d25b6317485 |
|
07-Dec-2016 |
Sanket Agarwal <sanketa@google.com> |
Write unit test for bta/btif HF client role Also fix a bug discovered by unit tests: bdcmp returns 0 on success hence use negation Bug: b/30984220 Test: Unit test Change-Id: I37f7c71c5dd809e4df3d8c2c79906a74c2b19d34
/system/bt/bta/hf_client/bta_hf_client_int.h
|
5eccd90936d606e0070872b247fd3462e9c9c19b |
|
01-Dec-2016 |
Sanket Agarwal <sanketa@google.com> |
Implement multiple control blocks for HF Client in BTA/BTIF Test: Manual test for multiple incoming/outgoing HF connections Bug: b/30984220 Change-Id: If66cad7c9bbc92051ebb7efb2b352c10e7514af3
/system/bt/bta/hf_client/bta_hf_client_int.h
|
bdcfc045f9d21afc1510cdad4fddd97a93c26477 |
|
01-Dec-2016 |
Sanket Agarwal <sanketa@google.com> |
BTA HF Client should use dynamic control block Most of the functions in bta_hf_client_at.cc are currently using a static field for passing callbacks to BTIF layer. In order to support multi device we need to make the functions have a parameter which denotes the device. In order to pass all the required information we choose to pass the control block for the device instead. Bug: b/30984220 Test: Manual regression test Change-Id: Iac692d7e28df3955ddbd28707c323c41714bd86a
/system/bt/bta/hf_client/bta_hf_client_int.h
|
cd1fd07f1306e08fe048682dd5918987e579f937 |
|
09-Nov-2016 |
Myles Watson <mylesgw@google.com> |
bta: Apply clang-format clang-format -i --style=file bta/*/* (twice) Test: mma -j32 Change-Id: Ib118b1dfb6a34f9a5bfe153d65841e9041165264
/system/bt/bta/hf_client/bta_hf_client_int.h
|
8af480e24549ba51a3f6858d9d9af504715e0bea |
|
09-Nov-2016 |
Myles Watson <mylesgw@google.com> |
bta: Remove double asterisks in comments Double asterisks at the beginning of the line sed -i s,"^[*][*]"," *", bta/*/* Double asterisks after a space sed -i s,"^ [*][*]\([^*]\)"," *\1", bta/*/* sed -i s,"^ [*][*]$"," *", bta/*/* Test: mma -j32 Change-Id: Ib83b802c7000176683b4e7f24d1255b3c2c6c01c
/system/bt/bta/hf_client/bta_hf_client_int.h
|
e9e58ced195ec2c983c7723c9cbdabd45eb0f2fd |
|
17-Jun-2016 |
Marie Janssen <jamuraa@google.com> |
bta: use standard types Use standard types everywhere. Use standard style for #if statements: - #if (VAR_NAME == TRUE) - #if (VAR_NAME1 == TRUE && VAR_NAME2 == TRUE) Use __func__ instead of __FUNCTION__ Fix some debug statements to use __func__ Change-Id: Ib86de4de9f14529ecaa4f71597260e3b5785360b
/system/bt/bta/hf_client/bta_hf_client_int.h
|
78bcff79e1b1f0efce436b33bdd6da88745bfc8a |
|
05-Dec-2015 |
Pavlin Radoslavov <pavlin@google.com> |
Refactor the Bluetooth timers * Updated the alarm API: - Existing API alarm_new() is modified to take an alarm name as an argument. - New API alarm_new_periodic() is used to create a periodic alarm. - Added new API alarm_is_scheduled() to test whether an alarm is scheduled. - Existing API alarm_set_periodic() is removed: a periodic alarm is created by alarm_new_periodic(). - Added new API alarm_set_on_queue() to set an alarm whose callback is executed on a specific queue. - Added new API alarm_register_processing_queue() and alarm_unregister_processing_queue() to register/unregister a queue and the corresponding thread for alarm processing. - Added corresponding unit tests. * Updated the alarm internals: - Added alarm_info_t for collecting alarm-related information and statistics. - Collect and store alarm-related statistics into alarm_info_t per alarm. - Include the alarm-related statistics and info into the native dumpsys output for Bluetooth. - Once an alarm expires, the alarm execution is scheduled for processing on another internal alarm-specific thread, not on the thread that is maintaining the alarms. - Implemented callback execution ordering guarantee among timers on the same thread with exactly same timeout values. * Refactor some of the usage of alarm_set() and simplify the code by using alarm_set_on_queue() instead. * Removed the non_repeating timers wrapper, and use directly the alarm mechanism / API. * Refactored all timer_entry_t timers and replaced them with alarm_t timers: - Replaced the btu_start_timer() / btu_stop_timer() / btu_start_quick_timer() / btu_stop_quick_timer() / btu_oneshot_alarm() mechanism with alarm_set_on_queue() and alarm_cancel() - Removed the whole mechanism around the BTU_TTYPE_* timers. * Fixed a bug when processing the GATT indication confirmation timer expiration (timer tGATT_TCB.conf_timer: b/26610829). * Renamed and/or split misc. timeout functions, fields, and timers * Renamed time-related constants and changed the values from seconds to milliseconds * Replaced timer tAVDT_CCB.timer_entry with three mutually exclusive timers: idle_ccb_timer, ret_ccb_timer, rsp_ccb_timer The reason we are using three timers, is because in the original code function avdt_ccb_chk_timer() used the timer type in its logic: it would stop the timer only if the type is "idle". * Removed btm_ble_timeout() and replaced it with multiple timeout callback functions (per timer) * Fix the actual value of the global constant BT_1SEC_TIMEOUT and rename it to BT_1SEC_TIMEOUT_MS * Removed btu_cb and associated timers and events, because they are never used. * Removed unused timers, functions, struct and declarations that are not used / needed. Bug: 26611369 Bug: 26610829 Change-Id: I812c8c31710a5daefc58b01fcf35c353768f390f
/system/bt/bta/hf_client/bta_hf_client_int.h
|
9f1c9ad85759c7663e3bbc494f8e75b2f107da67 |
|
28-Sep-2015 |
Pavlin Radoslavov <pavlin@google.com> |
GKI cleanup - Moved struct TIMER_LIST_ENT to OSI * Moved struct TIMER_LIST_ENT to file osi/include/non_repeating_timer.h and renamed it to timer_entry_t NOTE: This is a short-term solution. timer_entry_t should be removed, and its usage everywhere should be replaced by struct non_repeating_timer_t . * Renamed TIMER_CBACK to timer_callback_t * Renamed TIMER_PARAM_TYPE to timer_param_t Change-Id: I9ca830718bf900195f9c0a513a97f6995322693b
/system/bt/bta/hf_client/bta_hf_client_int.h
|
41d4a266ceca77bb09ab1bf5c04c30d15f3ded3a |
|
19-Aug-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Add support for HFP Client role. Implementation changes in BTA and BTIF layer to support HFP Client role. Change-Id: I9f939c18e8f989a50f298d0b313c5a0959c030a7
/system/bt/bta/hf_client/bta_hf_client_int.h
|