…iles. * commit '3e0d206155efe1ecb1b5da9c7ed4a068ba07c8d9': Let VoiceDialer.apk depend on libsrec_jni and srec data files.
Bug: 6294985 Change-Id: Id361e65e535c7d4b5f373fc3a15144b8de56483a
* commit '8f4d4e3be9391201544704434e6747f6db26c0d6': Voice dialer priority for handling VOICE_COMMAND intents.
Bug: 6334179 Change-Id: Ib301f850bd8ef926567f8a3093bd88d102bacd54
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
* commit 'bb36557e8e39727cd80cc8dd11e6372d4ab17175': Import revised translations. DO NOT MERGE
We currently show error message about "disconnected" status even after voice recognition was successful. This change ignores the event when appropriate. Bug: 5386457 Change-Id: Ie11e43c3dfd0cec718a8a2db0d51560b909d864e
* commit '0d78fc40857027c7c01b13002191ae0e0be98500': Import revised translations. DO NOT MERGE
…E" into ics-mr1 * commit 'bc64e2eb5407d4aa94f8cf1b1e5e48d1eb65a4dc': Import revised translations. DO NOT MERGE