I had the same issue after I first did the 3.2 upgrade. After about 24 hours the issue went away. I am guessing there must have been a change of some type with the satellite data in the new version or something akin to that. All seems well now. Whatever you do don't waste your time contacting...