I'm in Tampa with a Altell based phone and actually have been connecting fairly consistantly as of late. Not perfect but something......
To clarify some confusion over
GPS issues:
Cell phones use much lower-powered GPS chips and antennas than the Magellan/Tom-Tom/Garmin flavor of GPS systems. My wife's Tom-Tom also never has an issue locking in Sarasota.
Specifically, the Droid uses a Texas Instruments NaviLink chip optimized specifically for 3g phones with low power consumption, reduced size, and light weight. The TI website even mentions this chip's support for aGPS.
While I agree the issue is network related, I do not believe it is a Big-Brother issue, but an aGPS connectivity issue. Verizon has no control over the dialog between a GPS chip and a satellite!!
PS I have no idea why low-powered GPS chips have issues in SW FL, but there is definitely a pattern.
And once again, as others have mentioned, there are other factors clouding the issue: Faulty GPS chips, the need for occasional chip resets, initial lock issues, etc.
actually....
as it turns out...
the droid HAS to talk to the tower to authenticate it's ability to use the gps data
that's why GPS STATUS shows that my phone SEES every satellite available, but can NEVER MAKE THE HANDSHAKE to utilize their data
a little known.... an never-admitted fact
how i know?
because every single verizon-based gps phone in the tampa bay area works.....
and every single alltel-based one doesn't