I am running an original MotoDroid, stock rooted 2.2, with the Voice Search app from Google available on the Market.
It used to work... well, perfect. Beyond expectations.
In the past few days it's started acting up. For example, I have a friend named Jeff. I do Voice Search and say "Call Jeff". Voice Search popped up saying "Calling David's Bridal"
This got a surprised reaction out of me, so I cancelled the call before it was made, and Voice Search gave me suggestions of what I wanted. 3 different businesses, none of them being the Jeff in my address book, were shown available to call. "Call Jeff" appeared as an available Google Search.
I tested this with some other contacts that have worked before and got the same crazy wacky results. Clearing cache and data didn't help, neither did rebooting, so I uninstalled and reinstalled the app. It worked correctly at first - but now it's acting up again. If I say a contact's first and last name it works more often, but I used to not have to do that, and I don't know how it's getting such screwed up results.
Has anyone else encountered this? Is there a fix?
It used to work... well, perfect. Beyond expectations.
In the past few days it's started acting up. For example, I have a friend named Jeff. I do Voice Search and say "Call Jeff". Voice Search popped up saying "Calling David's Bridal"
This got a surprised reaction out of me, so I cancelled the call before it was made, and Voice Search gave me suggestions of what I wanted. 3 different businesses, none of them being the Jeff in my address book, were shown available to call. "Call Jeff" appeared as an available Google Search.
I tested this with some other contacts that have worked before and got the same crazy wacky results. Clearing cache and data didn't help, neither did rebooting, so I uninstalled and reinstalled the app. It worked correctly at first - but now it's acting up again. If I say a contact's first and last name it works more often, but I used to not have to do that, and I don't know how it's getting such screwed up results.
Has anyone else encountered this? Is there a fix?