diff options
Diffstat (limited to 'java/com/android/incallui/videotech/ims/ImsVideoCallCallback.java')
-rw-r--r-- | java/com/android/incallui/videotech/ims/ImsVideoCallCallback.java | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/java/com/android/incallui/videotech/ims/ImsVideoCallCallback.java b/java/com/android/incallui/videotech/ims/ImsVideoCallCallback.java index 17c2e6518..b83929304 100644 --- a/java/com/android/incallui/videotech/ims/ImsVideoCallCallback.java +++ b/java/com/android/incallui/videotech/ims/ImsVideoCallCallback.java @@ -161,6 +161,13 @@ public class ImsVideoCallCallback extends VideoCall.Callback { } } + // In the vendor code rx_pause and rx_resume get triggered when the video player starts or stops + // playing the incoming video stream. For the case where you're resuming a held call, its + // definitely a good signal to use to know that the video is resuming (though the video state + // should change to indicate its not paused in this case as well). However, keep in mind you'll + // get these signals as well on carriers that don't support the video pause signalling (like TMO) + // so you want to ensure you don't send sessionModifyRequests with pause/resume based on these + // signals. Also, its technically possible to have a pause/resume if the video signal degrades. @Override public void onCallSessionEvent(int event) { switch (event) { |