trick

1. Quote from JVCMobile.com : Text-to-Speech (English/Spanish/French/German/Italian/Dutch/Portuguese/Dannish/Swedish/Russian) Coverage: United States, Alaska, Hawaii, Canada, Puerto Rico, and U.S. Virgin Islands 2. I know. It wasn't the volume that was the problem. It was the TTS' failure to convert the traffic warning into intelligable english. 3. See my example posted above - both units were set to "fastest" rather than "shortest". In fact, even this logic is followed imprecisely. I have another example where the unit calculated a shorter route, where the trip would have been fa

"Traffic" - it comes with lifetime subscription to the TMS traffic service in the UK and comes with a seperate ariel lead (which plugs into the USB port).

Sounds like the opposite situation to me! Not good. It's a Nuvi 360T. Getting off topic for a moment - I had a 660 previously which *did* route better than the 360. But the 660 had a hardware fault and was replaced after 6 weeks.

Actually, I'm saying that the JVC calculates longer routes. Here's a route that I had to travel frequently over the last couple of months as I was working in the area... Nuvi 360T route = 10.1 miles : JVC Route = 11.3 miles : Real-life is about 30 mins extra on journey for this route, as it has high congestion for most of the day from Claygate > Tolworth, a long 20mph zone, and lots of stops for lights, crossings etc. Funnily enough, Google agrees with JVC about the best route. All I can say from experience is that the Nuvi route is the best.

1 - The navteq/teleatlas maps are just two different databases. I would assume that the system interprets the data within the database in the same way when navigating, maybe with tweaks for Left Hand Drive vs RHD. No idea why JVC decided to use 2 different suppliers, as Navteq are just as good (if not better) as TeleAtlas over here. IMO, the problem with TTS is (a) that the software cannot deal with complicated junctions and ( is not smart enough to handle roads which are not completely straight. Obviously the map database will play a part too, but it's not like these two map providers ar

OK, been using this unit more and getting more and more disappointed with the navigation. The Sat Nav is complete rubbish. I've had to resort back to my old Nuvi for guidance. Finding a POI without a postcode is stupidly restrictive. I've emailed a list of bugs to JVC : 1. The speed pulse is showing speeds that are 125% of the actual speed 2. When a GPS signal is lost, the unit gets very confused and shows the car driving off the road into fields or other roads that were nearby when the signal was lost. It keeps trying to recalculate and gives (very) incorrect guidance until i

Installed my NX7000 (UK version) into my Audi TT-S last week, full write-up with pictures is here on the TT-Talk forum (apologies if linking is a problem). Had a Kenwood DNX-5220BT in there previously but IMO this is a better unit. I think that the AV quality and funtionality of the JVC is top notch, but that the SatNav is a disappointment and really only good for occasional use. (But then how often do you really use your SatNav anyway?) EDIT : Forgot to mention. You can connect a reversing cam and external AV to the unit for back seat viewing (comes with a remote too!). The