Adding code to use the async voicemail transcription API

We have observed ~40% error rate with the synchronous transcription service and
suspect that it is at least partly due to the fact that the synchronous API requires that
we maintain a network connection to the server for up to several minutes.

This cl allows us to also use the asynchronous transcription API which will eliminate
the need for long lived network connections.  The client will still block until
the transcription is complete but this will be on a background thread and shouldn't
affect performance.

Also adding more impression logging for the new async API errors.

Bug: 37340510
Test: manual and updated unit tests
PiperOrigin-RevId: 165320593
Change-Id: Icf0e0b38d3a584fa679968592f91db0c42a6f1ee

1 files changed, 12 insertions, 0 deletions

diff --git a/java/com/android/dialer/logging/dialer_impression.proto b/java/com/android/dialer/logging/dialer_impression.proto
index de38ff359..b02c82b57 100644
--- a/java/com/android/dialer/logging/dialer_impression.proto
+++ b/java/com/android/dialer/logging/dialer_impression.proto
@@ -504,5 +504,17 @@ message DialerImpression {
     // notifications is very high and the system may suppress future
     // notifications.
     HIGH_GLOBAL_NOTIFICATION_COUNT_REACHED = 1249;
+
+    // More impressions for interactions with the voicemail transcription server
+    VVM_TRANSCRIPTION_REQUEST_SENT_ASYNC = 1250;
+    VVM_TRANSCRIPTION_VOICEMAIL_RECEIVED = 1251;
+    VVM_TRANSCRIPTION_VOICEMAIL_FORMAT_NOT_SUPPORTED = 1252;
+    VVM_TRANSCRIPTION_VOICEMAIL_INVALID_DATA = 1253;
+    VVM_TRANSCRIPTION_VOICEMAIL_UPLOAD_FAILED = 1254;
+    VVM_TRANSCRIPTION_RESPONSE_LANGUAGE_NOT_SUPPORTED = 1255;
+    VVM_TRANSCRIPTION_RESPONSE_NO_SPEECH_DETECTED = 1256;
+    VVM_TRANSCRIPTION_RESPONSE_EXPIRED = 1257;
+    VVM_TRANSCRIPTION_RESPONSE_TOO_MANY_ERRORS = 1258;
+    VVM_TRANSCRIPTION_POLLING_TIMEOUT = 1259;
   }
 }