Help The Contact Does Not Exist

[Althius]

When attempting to "voice search dial" (touching the microphone) it gives me a "did you mean" and then a contact (usually what I meant) and when I touch it I get a message that says "the contact does not exist". I've only seen a few other people online mentioning this, and I didn't get any hits searching for it here.

No solutions anywhere. I have my contacts 'synch'ed with my gmail account.

Aside from this I love my new Droid! Any help would be greatly appreciated.

 

[Sticks]

Check your spelling in the contact.

 

[Althius]

Spelling is exactly the same, and it does this for any/all contacts.

 

[Sticks]

Wish I could help you. All my contacts were transferred from another phone (PITA) and my Gmail contacts don't show up in my phone contacts, they only show up in some other application that I do not use all that much.

 

[Althius]

Still no answer, and I can't find any other answer. Maybe I'll have to go back to the Verizon store and see if they know.

Still, if anyone else has an answer... let me know!

 

[BottledHate]

probably not your answer... but contacts with numbers from facebook don't work under voice search dialing... i have to create a contact for them through google, then merge again with facebook before they show in voice search.

i have not had any problems with taping on the suggestions under 'did you mean...'

Maybe you have duplicate contact entries on your google account?

 

[Althius]

Still doesn't work for me. Even if I create brand new contacts.

 

[jcsbomber]

Getting the same problem here with one (of 2) of my Droids... Weird???

Removed the FB contact sync, still a problem - but only from "voice" search...

Me: "Call Jesse xxx"

Droid: "Jesse xxx / Add Number"

Me: CLICK on "Jesse xxx"

Droid: "The contact does not exist"

but it's fine if I dial through Contacts, or just look them up with the keyboard...

???

 

[CougFan]

I am having the exact same problem. My coworker and I got a Droid at the same time. His works fine. Mine does not.

 

[johnlgalt]

CougFan, are both of those the same hard rev? (look for a code under the battery, should be a number like 38-52 then 09 or 01-02 then 10

 

[CougFan]

John,

Yes, the are both the same hard rev: 49/09

 

[CougFan]

So I went to the Verizon store and handed them my phone. The lady turned it around and took the battery out without powering down the phone. I asked "doesn't that hurt the phone". She said that is actually the preferred way of taking out the battery. WE then powered up the phone and she asked me to show her the problem. When I tried it, the problem was fixed. Anyway, if you are having the problem that I described above, try removing the battery without powering down the phone. It is called a "soft reset" and it fixed my phone. The funny thing is that earlier in the day, I had powered down the phone with the power button, but that did not fix it. It must be something with removing the battery while the phone is still on. Sorry for the rambling, but I thought someone might be able to use this info to help them. Good luck. -John

 

[johnlgalt]

Actually, if you never removed the battery before that, then that could have been an issue as well - for *some* reason even if you power off the phone, it is more like in a sleep state than actually powered off. battery removal is the only true power off.

 

[darth_cholo]

So I went to the Verizon store and handed them my phone. The lady turned it around and took the battery out without powering down the phone. I asked "doesn't that hurt the phone". She said that is actually the preferred way of taking out the battery. WE then powered up the phone and she asked me to show her the problem. When I tried it, the problem was fixed. Anyway, if you are having the problem that I described above, try removing the battery without powering down the phone. It is called a "soft reset" and it fixed my phone. The funny thing is that earlier in the day, I had powered down the phone with the power button, but that did not fix it. It must be something with removing the battery while the phone is still on. Sorry for the rambling, but I thought someone might be able to use this info to help them. Good luck. -John

i wasn't getting "contact doesn't exist" instead i was getting a correct contact match except it would never show her mobile phone as an option. it would show work and home, but not mobile. sometimes it would sometimes it wouldn't. It was an exchange contact. removed it and readded the contact, didn't work.

the only thing that worked was a battery pull. dont know why but thanks for the tip!

 

[Rhinestone]

i wasn't getting "contact doesn't exist" instead i was getting a correct contact match except it would never show her mobile phone as an option. it would show work and home, but not mobile. sometimes it would sometimes it wouldn't. It was an exchange contact. removed it and readded the contact, didn't work.

the only thing that worked was a battery pull. dont know why but thanks for the tip!

I dont know why either but this worked for me.
I was having just ONE of my contacts not being recognised properly by the messaging app. It would not associate the number that came with the message and resolve it against my saved contact. All the info was identical. Because of this it would not show the Caller ID pic I had saved in the contact details. This was really annoying and bugged me for a whole week.

I spent ages searching for a solution, deleted all my contacts and added them again via sync. deleted all messages. still the issue was not resolved. Eventually I stumbled across this thread and thought it could not be as simple as pulling the battery but its solved the issue.

BTW This issue occurred after my Orange UK OTA update for Android 2.3 on my Desire HD

Thanks peeps