[G1 Android Development] Brut.all:
@MrPendulum, @Trepid!ty, @zabatman

I have added "continue on turn left on" to my TODO - should be easy to fix :-)

Yeah and you are first, who answered my questions/doubts :-) Still I believe this is a problem somewhere between Samsung devices and GM itself, not my mod. I don't see, how my modifications might cause such problems and there are a lot of results if you ask Google about "samsung spica google maps GPS", e.g.: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=25e7a46ad6eaeea5 . Seems Droid users are experiencing same problems.

If someone will report that he lives in USA/UK, he can navigate using original maps, but my mod doesn't work, I will look into it. Until then it's Google's problem, not mine, sorry.

BTW if I would have a friend with Galaxy/Droid phone, I would look into this problem anyway. But I don't have one, so this would be extremaly hard to debug.

Firstly, you have answered a guy, who have asked about "continue on turn left on" issue and, as you know, this will be easy to fix. General directions interpretation is another story. Actually first of these things is on TODO list now, second in Limits section ;-)

Secondly: problem with directions isn't real-time. I do all modifications at the point of navi response from servers and since then navi works as usual. So even if it would be resources consuming task, this would mean, that user have to wait a second or two more on "Getting driving directions" screen and then mod would need no RAM and no CPU.

Thirdly: we don't want to add some superinterpreters, use 1K characters long regexes, self-learning neural network or something like that. If there is a way to modify these directions accurately and reliably using many simple rules, indexOf() calls, etc. as I did in turn symbols fix, then this will be enough and won't take too much resources. These devices can run Quake 3 with all these rockets flying around, god damnit, so why they wouldn't be able to parse few strings?

This is exactly how I do it right now ;-) I have a onNaviResponse() hook and there I add some missing things, turn symbols, voice guidance, etc.

These things really don't have too much in common. The reason why we have this navigation hack is that Google gave us quite similar Directions feature. If he didn't, then there would be no navigation outside US/UK. There is no general answer on how to use some service outside the permitted area.

http://xdaforums.com/showthread.php?p=6219226#post6219226

Yesterday I got and idea, how to fix this problem with external apps targetting original GM. I don't know yet, whether this is possible, but if so, then we will be able to fix this for all apps at once and even for non-rooted phones.

What do you mean exactly? That TTS read non-English street names as they would be in English? Yeah, if there will be no other way, then I will add such switch.

This isn't that easy. Mobile GM uses mobilemaps.clients.google.com for all requests (maps, navigation, latitude, Buzz, etc.) and some custom, binary protocol on top of HTTP. You would have to write your own client and that won't be too easy, because we don't have an API (actually I would be able to write that client, but I'm not so bored to do it ;-) ).