History log of /frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsPullCall.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
3de018282cd7dae66d4dfff41303e81419d2004d 20-Jul-2016 Tyler Gunn <tgunn@google.com> Handle failure to pull an external call.

Look for two expected call fail causes which can occur if an external
call is being pulled, and the pulled ImsPhoneConnection disconnects.
These call fail causes are a signal that the call pull has failed.

We use this to trigger a callback which causes the TelephonyConnection to
swap the ImsPhoneConnection out for the ImsExternalConnection.

Bug: 29906222
Change-Id: I22e570ffd578ef5e474d6abaf5d89378bd17996c
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsPullCall.java
93da8529345711fd1a5617f3c8b15c0921eececb 15-Apr-2016 Tyler Gunn <tgunn@google.com> Wire up IMS framework APIs and call pull.

1. Wired up the IMS framework APIs so that the modem can inform us of new
dialog event package changes.
2. Wired up the call pull API so that calls to it make it down to an
ImsExternalConnection.
3. In ImsExternalCallTracker, listen to the call pull requests on the
external connections, and use this to trigger the actual pull of the call,
which is essentially a dial with an extra specified (per QCOM).
I abstracted away the idea of pulling the call using the ImsPullCall
interface, which ImsPhoneCallTracker implements.

Bug: 27458894
Change-Id: Idd20a95c2993b29dcd0a7e6c71fb6232cff88736
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/ImsPullCall.java