motorola droid voice search is down - 2/2/10
Tuesday, February 02, 2010apparently, every single motorola droid in the u.s. is effected by some evil voice search demon. to be serious for a second, this is actually true. as of this morning around 7:30AM, voice search on motorola droid devices has stopped working.
if you open the app and say a voice command, you get nothing. no recognition, no response, no results.
the issue has been brought to the highest levels at verizon as far as we know, but there is no timetable on a fix.
stay tuned! we'll keep this post rolling as we have new info. and if your droid returns to correct functionality, please let us know!
update 8:33am (2/2):
voice search is now recognizing voice commands but stalling during processing. "cancel" is required to get out of the app.
update 9:26am (2/2):
still down. verizon rep confirms it is a "program issue." whatever the hell that means. we also have users reporting now that they have never lost the voice search service.
if you leave a comment with your location and whether or not your voice search is working, that would be fantastic.
update 10:09am (2/2):
some users reporting that their voice search has been fixed. i'm in oregon and still definitely dead.
update 10:25am (2/2):
and voice search is officially back. bam.
update 4:19pm (2/2):
jumped the gun on everyone having their service back. getting reports through comments now that nebraska and california are still without voice search.
update 4:23pm (2/2):
just tested mine and voice search is now force closing.
update 7:49pm (2/2):
force closes continue and reports are coming in from all over the u.s. it looked initially like a west coast issue, but that theory has now been squashed. once we have an update reporting some sort of change, we'll be back.
stay patient everyone. let's just hope they are testing before the 2.1 release. (fingers crossed!)
18 comments
Working fine here.
ReplyDeleteReally? I'm still getting nothing
ReplyDeleteMind if I ask where you live?
mine still works as well.
ReplyDeletestill down in california
ReplyDeleteStill down in Omaha,NE
ReplyDeletestill down in chicago
ReplyDeleteMine was working a few hours ago, but now gettting force closes. I am in New York.
ReplyDeleteStill not working in AZ
ReplyDeletemine voice search is down. it is 5:00 on 2/2/10 in Washington, just across the river from Portland, OR.
ReplyDeleteWell, it appears to be going down everywhere again. That better mean OTA tomorrow with voice-to-text for us as a reward. :)
ReplyDeleteI live in Arizona and my wife and I are both having problems. We receive an "unexpected error"
ReplyDeleteTampa Florida...not working, force close
ReplyDeleteFC in Las Cruces, NM
ReplyDelete11:00 p.m. in Pa, still not working
ReplyDelete1125ATL no go in the droideepoo v search that I constantly boasted....
ReplyDelete11:55 PM MST. It's working again in Las Cruces, NM.
ReplyDeleteWorking in Omaha,NE
ReplyDeleteI depend on it for finding places to eat while driving, a lot better than GPS. I didn't know how much I use it till it was gone.
mine works just fine. michigan
ReplyDelete