From fe39efa9b15bbb89b01fca72763e49c508640139 Mon Sep 17 00:00:00 2001 From: Tyler Gunn Date: Fri, 2 Feb 2018 13:18:02 -0800 Subject: Add InCallService docs to state prerequisites for be being a dialer app. The InCallService documentation does not clearly state that an app which wants to become the default dialer app also needs to handle the DIAL intent. This change updates the documentation to make this clear. Test: Built documentation and verified its contents. Bug: 72857373 Change-Id: I738a8475df37035a0a7f4ad1639df76d967f81dc --- telecomm/java/android/telecom/InCallService.java | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/telecomm/java/android/telecom/InCallService.java b/telecomm/java/android/telecom/InCallService.java index fcf04c9a7eef..af65c65a48b7 100644 --- a/telecomm/java/android/telecom/InCallService.java +++ b/telecomm/java/android/telecom/InCallService.java @@ -60,6 +60,26 @@ import java.util.List; * * } * + *

+ * In addition to implementing the {@link InCallService} API, you must also declare an activity in + * your manifest which handles the {@link Intent#ACTION_DIAL} intent. The example below illustrates + * how this is done: + *

+ * {@code
+ * 
+ *      
+ *           
+ *           
+ *      
+ * 
+ * }
+ * 
+ *

+ * When a user installs your application and runs it for the first time, you should prompt the user + * to see if they would like your application to be the new default phone app. See the + * {@link TelecomManager#ACTION_CHANGE_DEFAULT_DIALER} intent documentation for more information on + * how to do this. */ public abstract class InCallService extends Service { -- cgit v1.2.3-59-g8ed1b