| 85a421c6d6bf1fdbbee134d99c1a7450b00ce8fc |
|
28-Nov-2011 |
Daisuke Miyakawa <dmiyakawa@google.com> |
Recognize phone numbers without supported types
Currently VoiceDialer cannot show a candidate when it has a type
the recognition engine cannot recognize. For example if a
contact has one phone number with the type CUSTOM, VoiceDialer
never shows the person as a candidate even when a user ask so
("Call XXX").
This change prepares "fallback" phone number id and use it when
there's no other available ids with recognizable types, to support
the case above.
TESTED:
- Have a contact (say "Ada" here) with several phone numbers one
of which must have a custom type which isn't supported by
VoiceDialer ("CUSTOM"). Say "Call Ada" and see if that custom
phone number appears as another entry ("Call Ada")
- Try "Call Ada at home" or other voice command and see they work
as before.
Bug: 5585945
Change-Id: Idd0e539209cd14e786007e8ce0b121c165994c5a
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|
| d3694c0511a27f1fb44fa2760ee0d4562ffe1066 |
|
08-Apr-2011 |
Joe Onorato <joeo@google.com> |
Remove the deprecated things from Config.java. These havent been working since before 1.0.
Change-Id: I097f48d9eec969553b34765a48ed652ea16c1a98
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|
| e5258ff473c778362d612389db79b740e9c35911 |
|
02-Apr-2010 |
Martin Hibdon <mah@android.com> |
Fix a problem with voicedialing on brand new phones
The code in VoiceContact runs a query to get all phones
from the contacts provider. It expects these phones
to be grouped by the person the phone is associated with,
but it actually sorts by LastContactedTime.
The comment indicates that this is done so that in case
there are too many contacts to fit into the grammar, at
least the most recently contacted will be the first ones
entered. These are probably the most likely ones to be
contacted again.
Normally, this works correctly. LastContactedTime is
actually a column on the Person table, so all phones
for a single person would have the same LastContactedTime,
and ties in this value are unlikely. However, when one gets
a new phone, or wipes data from an existing one, and
then imports contacts, all of them will have a LastContactedTime
of zero. Since they all tie, the order they come back from in
the query is totally undefined, and can't be expected to
group multiple phones for the same person together.
This breaks an assumption, and results in multiple grammar
entries for the same person, each of which contains a single
phone number, rather than the intention, which is one row
per person, with all valid phone numbers for that person.
So on a new phone, sometimes saying something like
"call john smith" will result in only a single method
of calling that person, even if john smith has multiple
phones.
Now, the sorting is done on both LastContactedTime and
DisplayName, so in case of ties in LastContactedTime,
same names should still be grouped together.
Also, make VoiceDialerActivity and BluetoothVoiceDialerActivity
use a new API to acquire and abandon Audio Focus. This
is an improved way of turning other media playback while
voice dialing, and allowing it to turn back on when finished.
Also correct some minor spelling errors.
Change-Id: Icc71bcf104bf2c02fdd8c03aa2749640561248e7
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|
| 8c7aac011e578450a6837ed4ba55b1167c17bf46 |
|
13-Mar-2010 |
Martin Hibdon <mah@android.com> |
Now the BTVoiceDialer waits for TTS utterances to complete before moving on
When the BluetoothVoiceDialer is about to place a call, it uses Text To Speech
to indicate which contact is about to call. Prior to this change, it would
just place the call after waiting a few seconds, which did not always line up
with the end of the TTS utterance. Now it waits for the utterance to complete.
Similarly, when it is about to exit it says "goodbye" to let the user know
it's exiting, and it now waits for that utterance to complete before exiting.
Fix a bug in VoiceContacts that caused it to skip the first row
returned by that phone query. This meant that the first person/phone
would not be entered into the RecognizerEngine, and therefore was
impossible to call from the VoiceDialer.
Change-Id: I4150f652d8df9bdc4ce54d573426bba64d13ad27
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|
| 0183a55431caad22e504cea07b76f182822bb3af |
|
19-Sep-2009 |
Dmitri Plotnikov <dplotnikov@google.com> |
[Issue 2117288] Upgrading Voice Dialer to new contacts API
Change-Id: Ibf4b24d9c7327003a4f06d354f15c98b660128fe
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|
| 538879a6f24ff7305e66d719e751b5d612029bf3 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|
| f3557ca3ea7b0b927e592a0a7055b05f3b8b5cfb |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|
| 95d8bae6aa7e8127c1d08d63d37ca35a4fe27f83 |
|
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|
| 22464da53983813d22e37d9656e8cbd7809e9ebf |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/packages/apps/VoiceDialer/src/com/android/voicedialer/VoiceContact.java
|