| 9250e5fa9987c3ab80e11e1955657055f5866539 |
|
01-Oct-2014 |
Yorke Lee <yorkelee@google.com> |
Add ability to add sim-initiated MO call to UI (3/4)
Pipe an unknown call through CallsManager via various new APIs like
onSuccessfulUnknownCall, onFailedUnknownCall, etc. These are the unknown call's
equivalent of onSuccessfulOutgoingCall and onFailedOutgoingCall.
Only the TelephonyConnectionService is allowed to call this hidden new API
in Telecom.
Also add the ability for TestConnectionService to test this API (although the
check for TelephonyConnectionService must be disabled at build time first).
Bug: 16852844
Change-Id: I5dfdfc1bd4675f6b300a4a55a3098582f9d715a2
/packages/services/Telecomm/src/com/android/server/telecom/ConnectionServiceWrapper.java
|
| 60ccd779d1448675ad42caa537348c2bcae186c2 |
|
30-Sep-2014 |
Ihab Awad <ihab@google.com> |
Refine implementation of GSM conferences (2/3)
Bug: 17684223
Change-Id: I7a274de891b7efc2a781a16ce7596bf5cd3ea6ff
/packages/services/Telecomm/src/com/android/server/telecom/ConnectionServiceWrapper.java
|
| 0b66e1c8102c09e0d6e0d4bf0d717dccfc65c4d0 |
|
24-Sep-2014 |
Sailesh Nepal <sail@google.com> |
Don't create conferences with invalid calls
When a remote conference was created
ConnectionServiceWrapper would actually create 2
conferences. One for the remote connection service with no
valid calls one for the real connection service with valid
calls.
When the conference was destroyed the remove call on the
remote connection serivce would trigger a unbind causing
android.telecom.ConnectionService to end call connections
for that service.
Fix was to ensure that we only create conferences with
valid calls.
Bug: 17632595
Change-Id: I3f339120dde8eb07ee7e40a26d3a37f1dbd1409e
/packages/services/Telecomm/src/com/android/server/telecom/ConnectionServiceWrapper.java
|
| 91d43cf9c985cc5a83795f256ef5c46ebb8fbdc1 |
|
17-Sep-2014 |
Tyler Gunn <tgunn@google.com> |
Preparatory work to move Telecom to system service.
- Removed use of TelecomApp.getInstance() as context.
- Refactored singleton logic and initialization to support being
performed from a SystemService.
- Note: You will see some commented out references to
"import com.android.internal.R"; these must uncommented when the code
is moved to a system service.
- You will also notice in PhoneAccountRegistrar.java a comment block with:
"UNCOMMENT_FOR_MOVE_TO_SYSTEM_SERVICE"
The code in that comment block will replace the existing file path
code.
These were added as a convenience so that I can run a simple sed script
to make the required changes to the code in an automated manner once it
is moved to its new location.
Bug: 17364651
Change-Id: I8e80e9cffc481b688c10a2bca0b59f5ccf8e0fb2
/packages/services/Telecomm/src/com/android/server/telecom/ConnectionServiceWrapper.java
|
| b3c4b285b747c58bfa58e2c58e09cdfb2c2b03b8 |
|
17-Sep-2014 |
Nancy Chen <nancychen@google.com> |
Merge "Remove ability to enable/disable phoneaccounts (3/6)" into lmp-dev
|
| 309198ec4d8b2738cf955316ea7a2f9418929fd1 |
|
16-Sep-2014 |
Nancy Chen <nancychen@google.com> |
Remove ability to enable/disable phoneaccounts (3/6)
Enabling/disabling of phone accounts was only used for SIP accounts and
is no longer necessary for the purpose it was put in.
- Remove all references to enabling/disabling phone accounts
+ Rename getEnabledPhoneAccounts to getCallCapablePhoneAccounts
Bug: 17510811
Change-Id: I5e8a59fe2aaac2563fe4bf97138975e30b45aa3c
/packages/services/Telecomm/src/com/android/server/telecom/ConnectionServiceWrapper.java
|
| 701dc006ac11625b55d872f1639107b028933895 |
|
12-Sep-2014 |
Andrew Lee <anwlee@google.com> |
Use telecomm DiconnectCause in services/Telecomm.
+ Some of this is straightforward replacing the old disconnect cause
code/message with the new DisconnectCause object.
+ Replace codes in some instances; most maps straightforwardly to the
newer generic set of disconnect causes.
+ InCallToneMonitor can no longer rely on the specific telephony
DisconnectCauses. Now, instead, they map from a tone (which is
specified on the new telecomm DisconnectCauses) to the type of tone
which should be played in InCall. Most of these are just taking
unique matches from InCallTonePlayer. It is a little redundant, as
the conversion just flips, but it seemed like the easiest way to
accomplish this given current constraints.
+ Behavior is unchanged, but now DisconnectCause.OUT_OF_SERVICE
will invoke InCallTonePlayer.TONE_CDMA_DROP.
+ Now play TONE_PROP_PROMPT regardless of whether there is precisely
one remaining call; this is because we can't distinguish between
telephony DisconnectCause.ERROR_UNSPECIFIED/NORMAL/LOCAL. I figured
this would be a relatively minor change in scenario, and it wouldn't
hurt for a tone to be played even in a disconnect in that scenario.
Bug: 17329632
Change-Id: I85767d424bcfd59b3929819c9c6de46fc4a8629e
/packages/services/Telecomm/src/com/android/server/telecom/ConnectionServiceWrapper.java
|
| 7cc70b4f0ad1064a4a0dce6056ad82b205887160 |
|
13-Sep-2014 |
Tyler Gunn <tgunn@google.com> |
Renaming Telecomm to Telecom.
- Changing package from android.telecomm to android.telecom
- Changing package from com.android.telecomm to
com.android.server.telecomm.
- Renaming TelecommManager to TelecomManager.
Bug: 17364651
Change-Id: Ib7b20ba6348948afb391450b4eef8919261f3272
/packages/services/Telecomm/src/com/android/server/telecom/ConnectionServiceWrapper.java
|