I recently upgraded Google Maps from v.2.x.x to v.3.2.1 and have noticed a significant drop in performance - the app is very sluggish when locating your position as well as searching. I kept a copy of v2 on the PC and rolled it back and found it to be much faster. I was wondering if anyone else has noticed the same thing or not as it may lead me to believe that the hardware in the 8330 may not be fast enough to handle this app as would a newer Tour with a faster processor.

Just curious.

The newer versions have LBS (Location Based services), which makes your location visible to other subscribing users which may account for the extra processing time.

The new version suffers from Spinning Clock frustrations too, and for no apparent reason. Even when doing nothing, or nothing of consequence, it will start spinning the clock and make you wait for anywhere from 10 - 30+ seconds. It's made using the app incredibly frustrating to the point of making it almost useless, because you never know when you can depend on it for a quick location fix or search. Google really needs to look into this - if the Tour can't handle the app, the app has problems!

If the Tour (which has a faster processor and more memory than the 8330) is having trouble with it, I will need to keep this rolled back to v.2.x.x. Question is, where does one complain to Google so the developers can get the appropriate feedback? Yet another question....

Thanks for your input!

only time i have problem with google is when phone is freshly reloaded and google runs for first time. curve 8330 sprint