diff options
author | Eric Erfanian <erfanian@google.com> | 2017-06-19 17:28:33 -0700 |
---|---|---|
committer | Eric Erfanian <erfanian@google.com> | 2017-06-19 17:28:33 -0700 |
commit | 2d6bc36921c4a41b17bc1870c133ee42f1388b51 (patch) | |
tree | ccf7310c8466dbc94a5646969613db81833c1ddd /java/com/android/dialer/logging/dialer_impression.proto | |
parent | ecc0957193e971e8f94f39efdbb37b0e4ed4f988 (diff) |
Add "Simulator" for Enriched Calling
An annoying part of development on enriched calling is that it was
difficult to determine what sessions were in memory. We have a
number of bugs related to incorrect sessions being shown, and knowing
exactly what sessions are available in memory can help debug them.
This CL adds a "Simulator" for enriched calling. This is more of a debug
tool than a simulator since it doesn't yet support adding a new enriched
calling session.
To allow the simulator to view all of the sessions in memory, a new
EnrichedCallManager API was introduced: getAllSessionsView. This API was
designed in a way to prevent abuse, so it returns a list of string
representations of the sessions. Just returning the full list of
sessions would have allowed clients to bypass the getSession logic and
examine sessions that shouldn't be available.
Also in this change:
* Integrate changes to form a base for future copybara imports.
Test: TH
PiperOrigin-RevId: 159445010
Change-Id: Ie8fc35d817a4e3b0eac37e0c34a6592060c43b23
Diffstat (limited to 'java/com/android/dialer/logging/dialer_impression.proto')
-rw-r--r-- | java/com/android/dialer/logging/dialer_impression.proto | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/java/com/android/dialer/logging/dialer_impression.proto b/java/com/android/dialer/logging/dialer_impression.proto index ba8d92249..4e96a5073 100644 --- a/java/com/android/dialer/logging/dialer_impression.proto +++ b/java/com/android/dialer/logging/dialer_impression.proto @@ -6,6 +6,7 @@ option java_multiple_files = true; option optimize_for = LITE_RUNTIME; + message DialerImpression { // Event enums to be used for Impression Logging in Dialer. // It's perfectly acceptable for this enum to be large @@ -48,6 +49,7 @@ message DialerImpression { // This happens when the user had initially blocked a number and also claimed the number was // spam and had now proceeded to undo that. REPORT_AS_NOT_SPAM_VIA_UNBLOCK_NUMBER = 1009 + ; // A number that was identified as spam and the user proceeded to block it. However this @@ -63,10 +65,12 @@ message DialerImpression { // the number via call log. This is for case where the user wants to block a number and also // report it as spam REPORT_CALL_AS_SPAM_VIA_CALL_LOG_BLOCK_REPORT_SPAM_SENT_VIA_BLOCK_NUMBER_DIALOG = 1011 + ; // User made it to the last step and actually blocked the number USER_ACTION_BLOCKED_NUMBER = 1012 + ; // User made it to the last step and actually unblocked the number @@ -89,16 +93,19 @@ message DialerImpression { // User added the number to contacts from the after call notification SPAM_AFTER_CALL_NOTIFICATION_ADD_TO_CONTACTS = 1019 + ; // User marked the number as spam on the after call notification flow SPAM_AFTER_CALL_NOTIFICATION_MARKED_NUMBER_AS_SPAM = 1020 + ; SPAM_AFTER_CALL_NOTIFICATION_MARKED_NUMBER_AS_NOT_SPAM_AND_BLOCKED = 1021; // User reported the number as not spam SPAM_AFTER_CALL_NOTIFICATION_REPORT_NUMBER_AS_NOT_SPAM = 1022 + ; // User dismissed the spam notification @@ -120,6 +127,7 @@ message DialerImpression { // able to stitch different types of events if they make sense e.g user pressed a speaker button // and we want to associate that to a call event USER_PARTICIPATED_IN_A_CALL = 1028 + ; // Incoming call is a spam call @@ -152,44 +160,54 @@ message DialerImpression { // User deleted a call log entry USER_DELETED_CALL_LOG_ITEM = 1048 + ; // User tapped on "Send a message" CALL_LOG_SEND_MESSAGE = 1049 + ; // User tapped on "Add to contact" CALL_LOG_ADD_TO_CONTACT = 1050 + ; // User tapped on "Create new contact" CALL_LOG_CREATE_NEW_CONTACT = 1051 + ; // User deleted an entry from the voicemail tab VOICEMAIL_DELETE_ENTRY = 1052 + ; // Voicemail call log entry was expanded. Could be either if the user tapped the voicemail // call log entry or pressed the play button when the voicemail call log entry was not expanded VOICEMAIL_EXPAND_ENTRY = 1053 + ; // The play button for voicemail call log entry was tapped directly (i.e when the voicemail // call log entry was not expanded and the playbutton was tapped) VOICEMAIL_PLAY_AUDIO_DIRECTLY= 1054 + ; // The play button after expanding the voicemail call log entry was tapped VOICEMAIL_PLAY_AUDIO_AFTER_EXPANDING_ENTRY= 1055 + ; // Incoming call was rejected from the notifications REJECT_INCOMING_CALL_FROM_NOTIFICATION= 1056 + ; // Incoming call was rejected from the answer screen including rejecting via sms and talkback REJECT_INCOMING_CALL_FROM_ANSWER_SCREEN= 1057 + ; // User tapped block and spam buttons in context menu, same as buttons in @@ -362,14 +380,19 @@ message DialerImpression { EMERGENCY_LAUNCHED_MAP = 1173; VIDEO_CALL_UPGRADE_REQUESTED = 1174 + ; VIDEO_CALL_REQUEST_ACCEPTED = 1175 + ; VIDEO_CALL_REQUEST_ACCEPTED_AS_AUDIO = 1176 + ; VIDEO_CALL_REQUEST_DECLINED = 1177 + ; VIDEO_CALL_REQUEST_RECEIVED = 1178 + ; RCS_VIDEO_SHARE_UPGRADE_REQUESTED = 1179; |