[ubizmo]

I have a Freedom Keychain 2000 GPS puck, and an 8320 Curve. I have been using Nav4all GPS software for spoken turn-by-turn directions, but I have used AmazeGPS in the past.

I have found both Nav4all and AmazeGPS to be very quirky in how long it takes for them to start talking to the Freedom puck. Sometimes it's fast--under a minute; other times it's *very* slow--up to ten minutes. I can't figure out why. When I turn the puck on, the time it takes the bluetooth icon to start blinking varies considerably, and the time it takes to find a satellite also varies. The satellite variation, at least, is to be expected. But that's not what explains the software delay, because sometimes even after it finds the satellite it can take a long time to start talking to the software.

Oddly, with Google Maps, it's always under a minute.

I've tried different orders of operations, such as starting Nav4all first, or starting the puck first, then Nav4all, then exit and restart Nav4all, etc. Nothing gives me consistent results. I do understand that weather conditions can affect the performance of the puck, but it seems odd to me that even after the puck is apparently talking to a satellite, it can still take many minutes to talk to the BB software. And as I say, I had exactly the same behavior with AmazeGPS. I switched because I think Nav4all is, on the whole, a better navigation program. But this quirkiness seems to affect both--though not Google Maps.

I wonder if anyone has discovered any magic to help with this.

[dude33333]

dude i have the same problem, same set up, and..... im in philly too. but it was like this in maine and CT too, so its not the location, but weird. using same programs/puck/8320

[dude33333]

nav4all never finds my gps puck period....