From 6c100246049a48edad26a7e6bb11f6aefc086339 Mon Sep 17 00:00:00 2001 From: Tyler Gunn Date: Mon, 9 Jan 2023 11:23:18 -0800 Subject: [PATCH] Update API docs for Call#putExtras. Make it clear how extras propagation between an InCallService and ConnectionService works. Fixes: 264892325 Test: Added new CTS test to verify this behavior end to end. Change-Id: I561f15cd886711101f2129e26b7fae1f12c5dd11 --- telecomm/java/android/telecom/Call.java | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/telecomm/java/android/telecom/Call.java b/telecomm/java/android/telecom/Call.java index bbdc8907275ee..95c90612748c6 100644 --- a/telecomm/java/android/telecom/Call.java +++ b/telecomm/java/android/telecom/Call.java @@ -2123,6 +2123,14 @@ public final class Call { *

* No assumptions should be made as to how an In-Call UI or service will handle these * extras. Keys should be fully qualified (e.g., com.example.MY_EXTRA) to avoid conflicts. + *

+ * Extras added using this method will be made available to the {@link ConnectionService} + * associated with this {@link Call} and notified via + * {@link Connection#onExtrasChanged(Bundle)}. + *

+ * Extras added using this method will also be available to other running {@link InCallService}s + * and notified via {@link Call.Callback#onDetailsChanged(Call, Details)}. The extras can be + * accessed via {@link Details#getExtras()}. * * @param extras The extras to add. */