1 result found
12 votesPeter Weil supported this idea ·
An error occurred while saving the comment
1 result found
New and returning users may sign in
Please sign in to leave feedback
No results.Clear search results
I am dedicated to Israel; my son works for the State of Israel and were it not for that, I would have uninstalled long ago.
Today is the 4th in a row of bad information given by the voice on my phone. The first three is identical to this one, but when I complained a week or so later, I was asked the specific routes, the time of the trip, etc. and I just simply was not going to spend the time to describe. Today, I'll try one more time.
By the way, Google has never made these kinds of mistakes.
Today, I used Google from 7011 W. Parmer Lane, Austin, TX to 12608 Lexington St., Manor, TX and got there perfectly on expressways 90% of the trip.
On the way back at approximately 3:55 p.m. CT, February 7, 2018, I used Waze to get back from 12608 Lexington, Manor, TX to 7011 W. Parmer Lane, Austin, TX. Waze advised me to get onto Parmer Lane about a mile from my starting place, which means I would go 20+ miles or so through dozens of stoplights, neighborhoods, etc. That's the same thing I experienced with the first three trips mentioned above.
When I did not get on Parmer Lane, when Waze advised me, just like the three above trips, Waze advised me to get off the freeway at every exit between the starting place and the ending place; advising me to "turn around" and go back to the first exit advised.
Maybe, I'm missing something like the ability to tell Waze to keep me on expressways and toll roads, etc. If I am missing that, then I do not know how to tell Waze.
Last chance, please advise...or, I'm sorry, but I uninstall. My son has experienced the same issues in Austin, TX.