de8d996c5eb073949210f53b739ef12c2c3054ee |
|
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 a0aa296e1311cbc72ba0ef18c434f68b60c8f935)
/packages/apps/Bluetooth/src/com/android/bluetooth/hfpclient/connserv/HfpClientConference.java
|
05462fe44531f887fe91ac173ec645e91b236025 |
|
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 184038a1db6482eeb4e54f834b286ea70ea030d9)
/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
|