Random VR Failures?

**Sponsor**

by **whobedaplaya** on Sun Nov 01, 2009 6:57 pm

Was wondering if anyone else is experiencing random VR failures to recognize commands?
Sometimes it'll understand all my commands just fine (play the album, browse the artist, call #####, find the nearest _____, etc.) and sometimes it's intelligence just takes a dump.

by **KraziJoe** on Tue Nov 03, 2009 10:46 pm

Yup...I can usually tell when it is, because she says WHAT WAS IT.
Very weird behavior...Pisses me off sometimes how long it takes the VR engine to start up

by **VBLUE42** on Wed Nov 04, 2009 3:24 am

I am seeing the same issue as well. It hasn't failed on directions yet, but it has failed for contacts and ipod. It appears to be boot related and weather you let the unit sit for a few seconds after boot. I will be testing this theory further.

by **DrRob** on Sat Nov 07, 2009 8:17 am

I just got my z110 last week and have been having the same problem. I'll frequently have to power off the system and turn it back on in order for the VR to work properly for making phone calls. It seems that the word "Call" becomes unrecognizable during these failures. Also, as another posted noted, it will say "was was that" during these times... I'm pretty sure this is the only time I hear it used that specific phrase. It is highly annoying that VR is so temperamental on such a high end system. This is arguably one of the best head units on the market.... it seems like they could have put a little more work into beta testing this VR software. Also, as far a recognizing the thing I say, it is pretty weak. For example, no matter how hard I try or how clear I speak, I cannot get it to recognize the word chase (as in Chase Bank). It insists on pulling up all of the nearest Chili's when I say "find the nearst Chase Bank". This is but one example of many. Overall I am very satisfied, but the VR is pretty much useless to me until they patch it.

by **whobedaplaya** on Sun Nov 08, 2009 3:59 am

Thank God! I thought it was dem gremlins at it again, especially since the Z110BT is installed in a Lincoln LS, which can be an eccentric car at times (but I love it! :mrgreen:

) And you guys hit the nail right on the head - I always get "what was that?" responses during the failures. One other annoying issue is that sometimes instead of playing an album, it displays the songs on the album instead and of course the HU is no longer in VR mode - you have to manually select the first song to start off the album.

by **whobedaplaya** on Sun Nov 08, 2009 4:01 am

This is actually my first double-DIN NAV/multimedia HU. I know it's a case of cest la vie, but it's still annoying to have to be Pioneer's (or any other manufacturer's really) butt-buddy after forking over so much scratch :evil:

by **DrRob** on Thu Nov 12, 2009 10:19 am

I'm not sure if this workaround has been posted elsewhere, but I stumbled across it today. It seems the VR for making phone calls is either functioning or not, and is boot dependent as was pointed out in a previous post. The failure appears to be that it loses the ability to recognize the word "Call". However, rather than rebooting the system, if you go to mode>phone>sync contacts (then click cancel if you have an iphone), it will briefly cycle and when the buttons come back up the VR will work again. Certainly not a fix, but it takes slightly less time than completely restarting the unit.

by **whobedaplaya** on Fri Nov 13, 2009 6:29 pm

I've noticed that if I hit the OK on the agreement screen as soon as possible, VR seems to function normally. If you let it sit, that's when things start getting wonky. This is somewhat annoying given that the agreement screen does NOT come up by default if you did not shutdown with the nav screen active (as it is in my case when I am just driving around town - I usually shut it down on either the iPod or XM screens). You have to toggle over to nav mode, hit OK and then let the VR engine start up and idle for a few seconds before beginning to use it.

by **VBLUE42** on Fri Nov 13, 2009 7:48 pm

I just did some pretty thourgh testing on this based on the idea posted above and I think I've got it narrowed down. The short answer to this is, you must hit the "OK" button before BT connects or voice calling will fail. Now, after several starts and restarts I have concluded that you must hit the "OK" button, wait for the BT to connect, and then proceed to use the voice control. In my testing I also verified, at least with my unit, that after you hit the "OK" button, you must wait about 30 seconds before hitting the the voice button or the voice sysetem will completly fail to work at all and the unit will have to be rebooted in order to clear the problem. So, hit the "OK" button, let BT connect, (which takes about 30 seconds by the way) and the voice call system should work flaulessly. Please feel free to add your findings if theynare different. The results I got may be specific to my unit only. Thanks to WHOBEDAPLAYA for the tip above.

by **DrRob** on Sun Nov 15, 2009 1:23 am

After reading the above two posts I tried this and it worked for me as well. Now I just have to remember to hit OK when it is hidden behind another screen

Thanks guys!

by **whobedaplaya** on Wed Nov 18, 2009 6:15 am

Glad I could help contribute

Also thanks to VBLU for further testing!