History log of /packages/apps/Bluetooth/src/com/android/bluetooth/hfpclient/connserv/HfpClientConference.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
c4fbd756e2645147470c486ae96f2253f5e13a52 12-Oct-2017 Jack He <siyuanh@google.com> [Script] Fix checkstyle errors (1/2)

Format code using Intellij to conform to CheckStyle requirements

Bug: 63597465
Test: make checkbuild, no manual changes, no functional changes
Change-Id: I70cd2ab8e5e6d5428ab1556658735b0d83f4fb15
/packages/apps/Bluetooth/src/com/android/bluetooth/hfpclient/connserv/HfpClientConference.java
167fd7bb638c43ac5e59f4c3a83037b617e7e336 04-Aug-2017 Joseph Pirozzo <pirozzoj@google.com> HFPClient unhold conference call

Allow a conference call with more than one party to be unheld. Clean up
hfp_enable logic to prevent it from being set twice in a row.

Bug: 63412812
Test: Create a multi party call on a GSM network and hold the phone
call, upon resuming audio is routed properly.

Change-Id: Ib31259eba0bbb171015f26b30a415e0539b3d0ec
/packages/apps/Bluetooth/src/com/android/bluetooth/hfpclient/connserv/HfpClientConference.java
1ec9ba7d555fc54f5b60aeb06fb38cab26f302a0 06-Jul-2016 Sanket Agarwal <sanketa@google.com> HF should wait for AG to change conference

We should always wait for AG to make changes to the call before we show
it to the user so that the UI does not get confusing (inconsistent).
Currently we are not waiting for the conf. call to be
disconnected/established by AG before we show this on our end.

Bug: b/29898872
Change-Id: Ia9198958122e9e539fb6f2a6f08942d3174ae2fc
(cherry picked from commit de8d996c5eb073949210f53b739ef12c2c3054ee)
/packages/apps/Bluetooth/src/com/android/bluetooth/hfpclient/connserv/HfpClientConference.java
ca6e7c65b87c52f5e81b273d7ad979a81b52f991 28-Jun-2016 Sanket Agarwal <sanketa@google.com> Redesign HFP Client call handling

1. Use UUIDs to interact between the upper layers and state machine.
2. Centralized place for managing calls.
3. Mechanism to co-relate outgoing calls with the AT+CLCC reply
4. Get rid of non-ECC hacks (we basically do not support devices not
supporting ECC)

Bug: b/29788044
Change-Id: I497c59583124825fad9be800a7c0a53920e67d4c
(cherry picked from commit 05462fe44531f887fe91ac173ec645e91b236025)
/packages/apps/Bluetooth/src/com/android/bluetooth/hfpclient/connserv/HfpClientConference.java
a9ad98ec1222093baecd70b32611c3a74ba7f2d8 10-Mar-2016 Sanket Agarwal <sanketa@google.com> HFP is exposed via Telecom ConnectionService.

Telecom provides a ConnectionService mechanism where in order to make
calls you only need to provide the right phone account (which can be
queried using a predefined scheme).

This change adds a new middleware called ConnectionService which
provides a translation medium from Bluetooth <-> Telecom. Anyone who
wishes to use HFP HF role can then simply use TelecomManager (and
TelecomManager's InCallService) interfaces.

Bug: b/26757899

Change-Id: I66e47b6ff6330cfd9040a4a6cf4edadac28d63de
/packages/apps/Bluetooth/src/com/android/bluetooth/hfpclient/connserv/HfpClientConference.java