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: 06a96eab (cherry picked from commit 06a96eab)
Loading
Please register or sign in to comment