From 38f1b7d112b3f6dc317ae46527ad48403a8e1124 Mon Sep 17 00:00:00 2001 From: Tyler Gunn Date: Wed, 7 Mar 2018 18:19:50 +0000 Subject: [PATCH] Ensure start of call properties are propagated to RemoteConnection. Some properties were not being propagated to a RemoteConnection when a Connection is first created. This can cause problems where the Connection Manager is not aware of these property changes, especially if they never change again during the lifetime of a call. The extras set when a Connection is first created using the RemoteConnectionService API would not be propagated to the RemoteConnection. This means that Telephony RAT reporting would never happen if the radio technology never changes during a call. Bug: 72811636 Test: Manual Change-Id: Ia523cee477a39c221953cda68c29579cb5f6ed76 Merged-In: 06a96eab13992b7eb36435f2b145756993aed575 (cherry picked from commit 06a96eab13992b7eb36435f2b145756993aed575) --- telecomm/java/android/telecom/RemoteConnectionService.java | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/telecomm/java/android/telecom/RemoteConnectionService.java b/telecomm/java/android/telecom/RemoteConnectionService.java index 59ce590858ee8..bb4b483de3268 100644 --- a/telecomm/java/android/telecom/RemoteConnectionService.java +++ b/telecomm/java/android/telecom/RemoteConnectionService.java @@ -93,6 +93,10 @@ final class RemoteConnectionService { // failure on the providing end, so immediately mark it destroyed connection.setDestroyed(); } + connection.setStatusHints(parcel.getStatusHints()); + connection.setIsVoipAudioMode(parcel.getIsVoipAudioMode()); + connection.setRingbackRequested(parcel.isRingbackRequested()); + connection.putExtras(parcel.getExtras()); } }