Asus EEE Transformer never gets a GPS fix unless I reboot it I have an Asus EEE Transformer (not the prime) that has unreliable GPS performance. I usually just fire up Google Maps in my car and use the navigation but the tablet always gets stuck with "Searching for GPS". This can go on for over 30 minutes in which the tablet either won't get a signal at all, or might get one every once in a while, update the map, and then go back to "Searching for GPS".

I have tried the following things:


Done the same navigation with my Nexus One in the same car and it has no problem receiving a signal right away and finding it's location so I'm pretty sure it's not environmental conditions.
I tether the Transformer to my Nexus One for internet so at first I thought using the "Use wireless networks" for location was just trying to get the location from the phone but toggling the option on or off doesn't seem to make it work worse or better one way or the other.
The amazon reviews don't seem to indicate an overwhelming problem with the Transformer with GPS.
I have tried the tips in this forum thread on the transformer forums.
I've tried installing GPSfix and using that tool but it doesn't seem to help.
Android version is 3.2.1, GPS version is 5.5.8, and Build # is: HTK.US_epad-8.6.5.19-20111107


So far the only reliable means to get the GPS working seems to be to shutdown the tablet and fire it up again, at which point the GPS and Google Navigation works right away, which leads me to believe that it's a software or configuration problem rather than a hardware issue.
It definitely is a software configuration. There are 2 possible reasons for this problem:


Servers its contacting - When Google Maps on your tablet/phone contacts the GPS satellites, its done through a special set of servers. Sometimes, the manufacturer might have set the system to connect to a set of particularly busy servers. It has been shown that connecting to other servers with lower traffic can give dramatically faster lock on times.
Possible bug in the initial configuration - when the manufacturer was setting up the initial build configuration, an unintended bug could have been introduced.


The solution to both can be done I believe through a simple fix in the gps.conf file but that would require root access. When I was running the stock firmware on my Asus Transformer, I was having the same problem. Now I am running a Custom ROM and I have no troubles with lock on in Google Maps.