diff options
author | Tyler Gunn <tgunn@google.com> | 2018-03-02 15:45:51 -0800 |
---|---|---|
committer | Tyler Gunn <tgunn@google.com> | 2018-03-02 15:45:51 -0800 |
commit | 9d12773b51eb409ae0424e162957da87c033cbfa (patch) | |
tree | 9cfb773d7db9d2a228ad78a29812e48206483fad /telecomm/java/android/telecom/TelecomManager.java | |
parent | d7187c90d0c5000800daa99ebd8ec2e5e8aaf33f (diff) |
API Documentation and Constant cleanup.
1. Update handover API docs for clarity.
2. Added an unknown value per API review comments.
3. Renamed HANDOVER_FAILURE_DEST_USER_REJECTED to
HANDOVER_FAILURE_USER_REJECTED
3. Removed the HANDOVER_FAILURE_DEST_INVALID_PERM constant since it isn't
used (methods which deal with permissions throw security exceptions).
Test: Make doc and verify documentation.
Change-Id: Id21d6b4c83d5c773ab38d78eb6b1886a1ac4dadf
Fixes: 73751004
Fixes: 73750515
Fixes: 73750817
Diffstat (limited to 'telecomm/java/android/telecom/TelecomManager.java')
-rw-r--r-- | telecomm/java/android/telecom/TelecomManager.java | 24 |
1 files changed, 21 insertions, 3 deletions
diff --git a/telecomm/java/android/telecom/TelecomManager.java b/telecomm/java/android/telecom/TelecomManager.java index 7e897453ab59..fe29f3a1ced2 100644 --- a/telecomm/java/android/telecom/TelecomManager.java +++ b/telecomm/java/android/telecom/TelecomManager.java @@ -1786,8 +1786,25 @@ public class TelecomManager { } /** - * Called from the recipient side of a handover to indicate a desire to accept the handover - * of an ongoing call to another {@link ConnectionService} identified by + * Called by an app to indicate that it wishes to accept the handover of an ongoing call to a + * {@link PhoneAccountHandle} it defines. + * <p> + * A call handover is the process where an ongoing call is transferred from one app (i.e. + * {@link ConnectionService} to another app. The user could, for example, choose to continue a + * mobile network call in a video calling app. The mobile network call via the Telephony stack + * is referred to as the source of the handover, and the video calling app is referred to as the + * destination. + * <p> + * When considering a handover scenario the <em>initiating</em> device is where a user initiated + * the handover process (e.g. by calling {@link android.telecom.Call#handoverTo( + * PhoneAccountHandle, int, Bundle)}, and the other device is considered the <em>receiving</em> + * device. + * <p> + * For a full discussion of the handover process and the APIs involved, see + * {@link android.telecom.Call#handoverTo(PhoneAccountHandle, int, Bundle)}. + * <p> + * This method is called from the <em>receiving</em> side of a handover to indicate a desire to + * accept the handover of an ongoing call to another {@link ConnectionService} identified by * {@link PhoneAccountHandle} destAcct. For managed {@link ConnectionService}s, the specified * {@link PhoneAccountHandle} must have been registered with {@link #registerPhoneAccount} and * the user must have enabled the corresponding {@link PhoneAccount}. This can be checked using @@ -1811,7 +1828,8 @@ public class TelecomManager { * @param videoState Video state after the handover. * @param destAcct The {@link PhoneAccountHandle} registered to the calling package. */ - public void acceptHandover(Uri srcAddr, int videoState, PhoneAccountHandle destAcct) { + public void acceptHandover(Uri srcAddr, @VideoProfile.VideoState int videoState, + PhoneAccountHandle destAcct) { try { if (isServiceConnected()) { getTelecomService().acceptHandover(srcAddr, videoState, destAcct); |