From 31f0e0bd2510732249be5bded744cbb37015b8c3 Mon Sep 17 00:00:00 2001 From: Tyler Gunn Date: Tue, 13 Feb 2018 08:39:45 -0800 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: I658aab10b1fb89ca29c39338febcc76e9f50d8f4 --- 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()); } }