It's not overclocked, but i have NITDroid installed, and actually waze there as well. Maybe that messes things up. Also, i installed some qt components things earlier, but i don't remember the details any more. Is it possible that it causes these? I also have CSSU. The google map locations of course are not exact, i just tried to find the approximate position based on landmarks and names. So, if you try to check the coordinates for some systematic error, you won't find it... It is set to metric, but i didn't set it, it set itself based on the language i guess. Just out of curiosity, i tried the search in NITDroid waze, and it seems to work ok there as well. -sc