diff options
| author | zachh <zachh@google.com> | 2017-08-16 12:42:37 -0700 |
|---|---|---|
| committer | Eric Erfanian <erfanian@google.com> | 2017-08-30 14:19:48 +0000 |
| commit | 780a361bb4416d1b3e34ed8bb3dab213070fcd17 (patch) | |
| tree | a69f15cd01acde8a4903dc5b83d9131aead94733 /java/com/android/voicemail/impl/transcribe/TranscriptionDbHelper.java | |
| parent | 24dbc840985b12a8e61e6e190e8508c72d58bcae (diff) | |
Init PhoneNumberFormattingTextWatcher on background thread.
A strict violation was being caused by calling this on the main thread:
android.telephony.PhoneNumberFormattingTextWatcher.<init>(PhoneNumberFormattingTextWatcher.java:71)
We now initialize the watcher on a background thread and pass it back to the main thread to be attached to the textview.
Behavior before: Dialpad fragment would fail to appear until libphonenumber finished (verified by adding sleep and observing)
Behavior after: Dialpad fragment loads immediately, but formatting is not enabled until libphonenumber finishes reading metadata. When adding sleeps, I could type "4084" before init finished and it would remain unformatted. When init finished I could type another character like "6" and the text view would be correctly updated to "408-46".
Bug: 64716944
Test: manual
PiperOrigin-RevId: 165480191
Change-Id: Ie1136a5a0e0b7ed66d4882e96c5830ca1e7523f0
Diffstat (limited to 'java/com/android/voicemail/impl/transcribe/TranscriptionDbHelper.java')
0 files changed, 0 insertions, 0 deletions