Build 25

[Steve Punter]

Although this was brought up originally in late August, I hadn't actually seen a case where the route would not be spoken when turn-by-turn directions were requested. However, recently, it DID happen to me and it gave me a repeatable set of circumstances that allowed me to step through the code and find out what had actually gone wrong.

Much to my surprise, I found a bug that (as far as I could tell) had been there since I'd first developed the turn-by-turn algorithms. However, the error only occurred under a certain set of circumstances, and somehow, in the well over 100 rides I'd done using turn-by-turn directions, this had never happened to me. I also hadn't received any other reports of it until just recently.

The good news is that Build 25 should fix this problem once and for all, and probably clean up a few other odd turn-by-turn related issued. This is because the error occurs in an algorithm that computes the closest POINT to your present location. When it fails at the beginning, the entire turn-by-turn engine is crippled, but if it occurred from time to time throughout a ride, it might simply cause faulty information that could result in many different kinds of bad behavior. While I can't be certain, it could be the cause of some of the never-ending repeating of the same spoken information.

So, if you haven't updated yet, get Build 25 now.